A fault processing method and device and a storage medium

Abstract

The application provides a fault processing method and device and a storage medium, relates to the technical field of communication, and is used for solving the technical problem that general technology cannot quickly process network faults. The fault processing method comprises the following steps: acquiring a fault area of a fault network; acquiring operation information of a base station corresponding to a target operation subject in the fault area and not having a network fault; and when the operation information of the base station corresponding to the target operation subject meets preset bearing conditions, sharing network resources corresponding to the target operation subject by the base station corresponding to the target operation subject to user equipment in the fault area.

Description

Technical Field

[0001] This application relates to the field of communication technology, and in particular to a fault handling method, apparatus and storage medium. Background Technology

[0002] Telecommunication operators may experience network outages due to force majeure events such as road construction and building demolition during routine operations, which may lead to network failures.

[0003] Currently, resolving network failures typically involves procedures such as fault reporting, on-site troubleshooting, and fiber optic resuscitation. The common network failure resolution methods have a long recovery time (usually around 6 hours), impacting not only the normal use of user equipment but also the robustness of the mobile network and the operator's related traffic revenue. Summary of the Invention

[0004] This application provides a fault handling method, apparatus, and storage medium to solve the technical problem of low fault handling efficiency in general technologies.

[0005] To achieve the above objectives, this application adopts the following technical solution:

[0006] Firstly, a fault handling method is provided, comprising: acquiring the fault area of ​​the faulty network; acquiring the operation information of the base station corresponding to the target operator within the fault area where no network fault has occurred; and when the operation information of the base station corresponding to the target operator meets the preset bearing conditions, sharing the network resources corresponding to the target operator with the user equipment within the fault area through the base station corresponding to the target operator.

[0007] Optionally, sharing network resources corresponding to the target operator with user equipment in the fault area via the base station corresponding to the target operator includes: obtaining base station parameter configuration information of the faulty network corresponding to the faulty operator, and generating a first script based on the base station parameter configuration information; the first script is used to instruct the base station corresponding to the target operator to configure base station parameters corresponding to the base station parameter configuration information; obtaining network parameter configuration information of the faulty operator within a preset time period, and generating a second script based on the network parameter configuration information and operating information; the second script is used to instruct the base station corresponding to the target operator to configure network parameters corresponding to the network parameter configuration information; sending a sharing instruction message including the first script and the second script to the target network management device corresponding to the target operator, so that the target network management device executes the first script and the second script; the sharing instruction message is used to instruct the target network management device to control the base station corresponding to the target operator to share the network resources corresponding to the target operator with user equipment in the fault area.

[0008] Optionally, the operation information includes operation status and operation load; after obtaining the operation information of the base station corresponding to the target operator that has not experienced network failure within the fault area, it further includes: when the operation status is normal and the operation load is less than the first preset load, determining that the operation information of the base station corresponding to the target operator meets the preset bearing conditions; when the operation status is abnormal and / or the operation load is greater than or equal to the first preset load, determining that the operation information of the base station corresponding to the target operator does not meet the preset bearing conditions.

[0009] Optionally, when the operating status is normal, the operating load is less than the first preset load, and the operating load is greater than the second preset load, the network resources corresponding to the target operator are shared with user equipment in the fault area through the base station corresponding to the target operator, including: determining the number of shared resource blocks (RBs) based on the operating load; the second preset load is greater than 0 and less than the first preset load; and sharing the network resources corresponding to the number of RBs with user equipment in the fault area through the base station corresponding to the target operator.

[0010] Optionally, the fault handling method further includes: receiving a fault recovery message; the fault recovery message is used to indicate the fault recovery of the faulty network; sending a sharing end message to the target network management device corresponding to the target operator, so that the target network management device executes a sharing rollback script; the sharing rollback script is used to instruct the target network management device to control the base station corresponding to the target operator not to share the network resources corresponding to the target operator with user equipment in the faulty area.

[0011] In a second aspect, a fault handling device is provided, comprising: an acquisition unit and a processing unit; the acquisition unit is used to acquire the fault area of ​​the faulty network; the acquisition unit is also used to acquire the operation information of the base station corresponding to the target operator within the fault area where no network fault has occurred; the processing unit is used to share the network resources corresponding to the target operator with the user equipment within the fault area through the base station corresponding to the target operator when the operation information of the base station corresponding to the target operator meets the preset bearing conditions.

[0012] Optionally, the processing unit is specifically configured to: obtain base station parameter configuration information corresponding to the faulty operator of the faulty network, and generate a first script based on the base station parameter configuration information; the first script is used to instruct the base station corresponding to the target operator to configure the base station parameters corresponding to the base station parameter configuration information; obtain network parameter configuration information of the faulty operator within a preset time period, and generate a second script based on the network parameter configuration information and operating information; the second script is used to instruct the base station corresponding to the target operator to configure the network parameters corresponding to the network parameter configuration information; send a shared instruction message including the first script and the second script to the target network management device corresponding to the target operator, so that the target network management device executes the first script and the second script; the shared instruction message is used to instruct the target network management device to control the base station corresponding to the target operator to share the network resources corresponding to the target operator with user equipment in the faulty area.

[0013] Optionally, the operation information includes operation status and operation load; the processing unit is further configured to determine that the operation information of the base station corresponding to the target operator meets the preset bearing conditions when the operation status is normal and the operation load is less than the first preset load; the processing unit is further configured to determine that the operation information of the base station corresponding to the target operator does not meet the preset bearing conditions when the operation status is abnormal and / or the operation load is greater than or equal to the first preset load.

[0014] Optionally, when the operating state is normal, the operating load is less than the first preset load, and the operating load is greater than the second preset load, the processing unit is specifically used to: determine the number of shared resource blocks (RBs) based on the operating load; the second preset load is greater than 0 and less than the first preset load; and share network resources corresponding to the number of RBs with user equipment in the fault area through the base station corresponding to the target operator.

[0015] Optionally, the fault handling device further includes: a receiving unit and a sending unit; the receiving unit is used to receive a fault recovery message; the fault recovery message is used to indicate the fault recovery of the faulty network; the sending unit is used to send a sharing end message to the target network management device corresponding to the target operator, so that the target network management device executes a sharing rollback script; the sharing rollback script is used to instruct the target network management device to control the base station corresponding to the target operator not to share the network resources corresponding to the target operator with user equipment in the faulty area.

[0016] Thirdly, a fault handling apparatus is provided, including a memory and a processor; the memory is used to store computer execution instructions, and the processor is connected to the memory via a bus; when the fault handling apparatus is running, the processor executes the computer execution instructions stored in the memory to cause the fault handling apparatus to perform the fault handling method described in the first aspect.

[0017] The fault handling device can be a network device or a part of a network device, such as a chip system within the network device. The chip system supports the network device in implementing the functions involved in the first aspect and any of its possible implementations, such as acquiring, determining, and transmitting data and / or information involved in the aforementioned fault handling method. The chip system includes a chip, but may also include other discrete devices or circuit structures.

[0018] Fourthly, a computer-readable storage medium is provided, comprising computer-executable instructions that, when executed on a computer, cause the computer to perform the fault handling method described in the first aspect.

[0019] Fifthly, a computer program product is also provided, which includes computer instructions that, when executed on a fault handling device, cause the fault handling device to perform the fault handling method as described in the first aspect above.

[0020] It should be noted that the aforementioned computer instructions may be stored, in whole or in part, on a computer-readable storage medium. This computer-readable storage medium may be packaged together with the processor of the fault handling device, or it may be packaged separately from the processor of the fault handling device; this application does not limit this.

[0021] The descriptions of the second, third, fourth, and fifth aspects of this application can be referenced to the detailed description of the first aspect.

[0022] In the embodiments of this application, the names of the aforementioned fault handling devices do not limit the devices or functional modules themselves. In actual implementation, these devices or functional modules may appear under other names. For example, the receiving unit may also be called a receiving module, receiver, etc. As long as the functions of each device or functional module are similar to those of this application, they fall within the scope of the claims of this application and their equivalents.

[0023] The technical solution provided in this application brings at least the following beneficial effects:

[0024] Based on any of the above, this application provides a fault handling method that can obtain the fault area of ​​a faulty network and the operating information of the base station corresponding to the target operator within the fault area, where no network fault has occurred. Subsequently, when the operating information of the base station corresponding to the target operator meets preset carrying conditions, the network resources corresponding to the target operator can be shared with user equipment within the fault area through the base station corresponding to the target operator.

[0025] In this way, when a network in a certain area fails, network resources can be provided to user equipment through the base stations of other operators in the same area that are not experiencing any failures. This eliminates the need to wait for the faulty network to be repaired and does not affect the normal use of user equipment, thus improving the efficiency of fault handling.

[0026] The beneficial effects of the first, second, third, fourth, and fifth aspects of this application can all be referred to in the analysis of the above-mentioned beneficial effects, and will not be repeated here. Attached Figure Description

[0027] Figure 1 This is a schematic diagram illustrating an application scenario of a fault handling system provided in an embodiment of this application;

[0028] Figure 2 A schematic diagram of the hardware structure of a fault handling device provided in an embodiment of this application. Figure 1 ;

[0029] Figure 3 A schematic diagram of the hardware structure of a fault handling device provided in an embodiment of this application. Figure 2 ;

[0030] Figure 4 A flowchart illustrating a fault handling method provided in this application embodiment. Figure 1 ;

[0031] Figure 5 A flowchart illustrating a fault handling method provided in this application embodiment. Figure 2 ;

[0032] Figure 6 A flowchart illustrating a fault handling method provided in this application embodiment. Figure 3 ;

[0033] Figure 7 A flowchart illustrating a fault handling method provided in this application embodiment. Figure 4 ;

[0034] Figure 8 A flowchart illustrating a fault handling method provided in this application embodiment. Figure 5 ;

[0035] Figure 9 This is a schematic diagram of the structure of a fault handling device provided in an embodiment of this application. Detailed Implementation

[0036] The technical solutions of the embodiments of this application will be clearly and completely described below with reference to the accompanying drawings. Obviously, the described embodiments are only some embodiments of this application, and not all embodiments. Based on the embodiments of this application, all other embodiments obtained by those skilled in the art without creative effort are within the scope of protection of this application.

[0037] It should be noted that in the embodiments of this application, the words "exemplary" or "for example" are used to indicate examples, illustrations, or explanations. Any embodiment or design scheme described as "exemplary" or "for example" in the embodiments of this application should not be construed as being more preferred or advantageous than other embodiments or design schemes. Specifically, the use of the words "exemplary" or "for example" is intended to present the relevant concepts in a specific manner.

[0038] To facilitate a clear description of the technical solutions of the embodiments of this application, the terms "first" and "second" are used in the embodiments of this application to distinguish the same or similar items with essentially the same function and effect. Those skilled in the art can understand that the terms "first" and "second" are not intended to limit the quantity or execution order.

[0039] As described in the background section, network failures typically require procedures such as fault reporting, on-site troubleshooting, and fiber optic resuscitation to resolve the issue. Common network failure resolution methods have a long recovery time (usually around 6 hours), impacting not only the normal use of user equipment but also the robustness of the mobile network and the operator's related traffic revenue.

[0040] To address the aforementioned issues, this application provides a fault handling method that can acquire the faulty area of ​​a faulty network and the operational information of the base station corresponding to the target operator within the faulty area, where no network fault has occurred. Subsequently, when the operational information of the base station corresponding to the target operator meets preset carrying conditions, the network resources corresponding to the target operator can be shared with user equipment within the faulty area through the base station corresponding to the target operator.

[0041] In this way, when a network in a certain area fails, network resources can be provided to user equipment through the base stations of other operators in the same area that are not experiencing any failures. This eliminates the need to wait for the faulty network to be repaired and does not affect the normal use of user equipment, thus improving the efficiency of fault handling.

[0042] This fault handling method is applicable to fault handling systems. Figure 1 One structure of this fault handling system is shown. For example... Figure 1As shown, the fault handling system includes: a first network management server 101, a second network management server 102, a first base station 103, a second base station 104, and a fault handling device 105.

[0043] The fault handling device 105 is communicatively connected to the first network management server 101 and the second network management server 102.

[0044] The first network management server 101 and the second network management server 102 are two network management servers corresponding to different operating entities. That is, the first network management server 101 is the network management server corresponding to the first operating entity, and the second network management server 102 is the network management server corresponding to the second operating entity.

[0045] The first base station 103 is communicatively connected to the first network management server 101, meaning that the first base station 103 is a base station under the communication network corresponding to the first operating entity. The second base station 104 is communicatively connected to the second network management server 102, meaning that the second base station 104 is a base station under the communication network corresponding to the second operating entity.

[0046] For example, the first operating entity is China Unicom, and the second operating entity is China Telecom. Correspondingly, the first network management server 101 is the network management server corresponding to China Unicom, and the second network management server 102 is the network management server corresponding to China Telecom. The first base station 103 is a base station under the China Unicom communication network. The second base station 104 is a base station under the China Telecom communication network.

[0047] In this embodiment of the application, the network area covered by the first base station 103 is the same as the network area covered by the second base station 104.

[0048] In this way, when the communication network corresponding to the first operator fails within the network area, the fault handling device 105 can share the network resources corresponding to the second operator with the user equipment within the network area through the second base station 104.

[0049] Correspondingly, when the communication network corresponding to the second operator fails, the fault handling device 105 can share the network resources corresponding to the first operator with the user equipment in the network area through the first base station 103.

[0050] The first network management server 101 and the second network management server 102 mentioned above are mainly used to monitor each node device in their corresponding communication network, such as organizing the information of each node device and the data transmitted.

[0051] The aforementioned first base station 103 and second base station 104 can be wireless communication base stations or base station controllers, etc. In the embodiments of this application, the base station can be a base station (BTS) in Global System for Mobile Communication (GSM), a base station (node ​​B) in Code Division Multiple Access (CDMA), a base station (eNB) in Internet of Things (IoT) or Narrowband-Internet of Things (NB-IoT), a base station in a future 5G mobile communication network, or a base station in a future evolved public land mobile network (PLMN). The embodiments of this application do not impose any limitations on this.

[0052] The physical device of the aforementioned fault handling device 105 can be a server, a terminal, or other types of electronic equipment, and this application embodiment does not limit it in this way.

[0053] Optionally, the aforementioned terminal may be a device that provides voice and / or data connectivity to a user, a handheld device with wireless connectivity, or other processing device connected to a wireless modem. The wireless terminal may communicate with one or more core networks via a radio access network (RAN). The wireless terminal may be a mobile terminal, such as a mobile phone (or "cellular" phone) and a computer with a mobile terminal, or a portable, pocket-sized, handheld, computer-embedded, or vehicle-mounted mobile device that exchanges voice and / or data with the radio access network, such as a mobile phone, tablet computer, laptop computer, netbook, or personal digital assistant (PDA).

[0054] Optionally, the server mentioned above can be one of the servers in a server cluster (composed of multiple servers), a chip in the server, a system-on-a-chip in the server, or a virtual machine (VM) deployed on a physical machine. This application embodiment does not limit this.

[0055] The basic hardware structure of the fault handling device 105 includes: Figure 2 or Figure 3The fault handling device shown includes the following components. Figure 2 and Figure 3 Taking the fault handling device shown as an example, the hardware structure of the fault handling device 105 will be introduced.

[0056] like Figure 2 The diagram shown is a hardware structure schematic of a fault handling device provided in an embodiment of this application. The fault handling device includes a processor 21, a memory 22, a communication interface 23, and a bus 24. The processor 21, memory 22, and communication interface 23 are connected via the bus 24.

[0057] Processor 21 is the control center of the fault handling device. It can be a single processor or a collective term for multiple processing elements. For example, processor 21 can be a general-purpose central processing unit (CPU) or other general-purpose processors. Among them, the general-purpose processor can be a microprocessor or any conventional processor.

[0058] As one embodiment, processor 21 may include one or more CPUs, for example Figure 2 CPU 0 and CPU 1 are shown in the diagram.

[0059] The memory 22 may be a read-only memory (ROM) or other type of static storage device capable of storing static information and instructions, random access memory (RAM) or other type of dynamic storage device capable of storing information and instructions, or electrically erasable programmable read-only memory (EEPROM), disk storage media or other magnetic storage devices, or any other medium capable of carrying or storing desired program code in the form of instructions or data structures and accessible by a computer, but is not limited thereto.

[0060] In one possible implementation, the memory 22 can exist independently of the processor 21. The memory 22 can be connected to the processor 21 via a bus 24 and is used to store instructions or program code. When the processor 21 calls and executes the instructions or program code stored in the memory 22, it can implement the fault handling method provided in the following embodiments of this application.

[0061] In this embodiment, the software programs stored in the memory 22 of the fault handling device 105 are different, so the functions implemented by the fault handling device 105 are different. The functions performed by each device will be described with reference to the following flowchart.

[0062] In another possible implementation, the memory 22 can also be integrated with the processor 21.

[0063] Communication interface 23 is used for the fault handling device to connect with other devices via a communication network, such as Ethernet, wireless access network, wireless local area network (WLAN), etc. Communication interface 23 may include a receiving unit for receiving data and a sending unit for sending data.

[0064] Bus 24 can be an industry standard architecture (ISA) bus, a peripheral component interconnect (PCI) bus, or an extended industry standard architecture (EISA) bus, etc. This bus can be divided into address bus, data bus, control bus, etc. For ease of representation, Figure 2 The bus is represented by a single thick line, but this does not mean that there is only one bus or one type of bus.

[0065] Figure 3 Another hardware structure of the fault handling device in an embodiment of this application is shown. For example... Figure 3 As shown, the fault handling device may include a processor 31 and a communication interface 32. The processor 31 is coupled to the communication interface 32.

[0066] The functions of processor 31 can be referred to in the description of processor 21 above. In addition, processor 31 also has a storage function, and can perform the functions of memory 22 mentioned above.

[0067] The communication interface 32 is used to provide data to the processor 31. The communication interface 32 can be an internal interface of the fault handling device or an external interface of the fault handling device (equivalent to communication interface 23).

[0068] It should be pointed out that, Figure 2 (or Figure 3 The structure shown in the diagram does not constitute a limitation on the fault handling device, except... Figure 2 (or Figure 3 In addition to the components shown in the diagram, the fault handling device may include more or fewer components than shown, or combine certain components, or have different component arrangements.

[0069] The fault handling method provided in the embodiments of this application will be described in detail below with reference to the accompanying drawings.

[0070] The fault handling method provided in the embodiments of this application is applied to Figure 1 The fault handling device 105 in the fault handling system shown is, for example Figure 4 As shown, the fault handling method provided in this application embodiment includes:

[0071] S401, The fault handling equipment obtains the fault area of ​​the faulty network.

[0072] Specifically, when a network fails at a certain point, the fault handling device can use the network management server corresponding to that network (which can be a wireless data management network management server) to determine the fault area related to the fault point.

[0073] Optionally, the fault handling equipment can obtain the base stations related to the fault point through the network management server corresponding to the network, and then determine the fault area related to the fault point based on the coverage of the base stations.

[0074] Alternatively, the fault handling device can obtain the network device topology relationship related to the fault point through the network management server corresponding to the network, and then determine the fault area affected by the fault point based on the network device topology relationship.

[0075] In one feasible approach, the fault handling device can also obtain the service carrying capacity of the fault point through the network management server corresponding to the network (which may be a data transmission network management server), and then determine whether the fault area is an important trunk line based on the service carrying capacity.

[0076] When the fault area is a non-critical trunk line, the fault handling equipment can send a fault message to the maintenance personnel and wait for them to repair the fault point.

[0077] When the faulty area is an important trunk line, the fault handling equipment can provide network resources to user equipment through the base stations of other non-faulty operators within the faulty area. This eliminates the need to wait for the faulty network to be repaired and does not affect the normal use of user equipment, thus improving the efficiency of fault handling.

[0078] S402. The fault handling equipment obtains the operating information of the base station corresponding to the target operator within the fault area where no network fault has occurred.

[0079] Specifically, after obtaining the faulty area of ​​the faulty network, in order to ensure the service experience of user equipment in the faulty area, the fault handling equipment can obtain the operation information of the base station corresponding to the target operator in the faulty area that has not experienced network failure.

[0080] In one feasible approach, the fault handling device can obtain the operating information of the base station corresponding to the target operator that has not experienced a network failure from the network management server corresponding to the target operator within the fault area.

[0081] For example, when the faulty network is a China Unicom communication network, the fault handling equipment can obtain the operating information of the corresponding base station of the telecommunications operator through the network management server of the telecommunications operator.

[0082] S403. When the operating information of the base station corresponding to the target operator meets the preset bearing conditions, the fault handling equipment shares the network resources corresponding to the target operator with the user equipment in the fault area through the base station corresponding to the target operator.

[0083] Specifically, after obtaining the operating information of the base station corresponding to the target operator that has not experienced network failure within the fault area, the fault handling equipment needs to determine whether the operating information of the base station corresponding to the target operator meets the preset bearing conditions.

[0084] Optionally, the fault handling device can determine whether the operating information of the base station corresponding to the target operator meets the preset bearing conditions based on the operating status of the base station corresponding to the target operator that has not experienced a network failure; it can also determine whether the operating information of the base station corresponding to the target operator meets the preset bearing conditions based on the operating load (e.g., wireless resource utilization) of the base station corresponding to the target operator that has not experienced a network failure; or it can determine whether the operating information of the base station corresponding to the target operator meets the preset bearing conditions based on the operating status and operating load of the base station corresponding to the target operator that has not experienced a network failure. This application embodiment does not limit this.

[0085] In one feasible approach, the faulty network party can be referred to as the sharing party, and the non-faulty party can be referred to as the contractor. When the fault handling device shares the contractor's network resources with the sharing party's user equipment through the contractor's base station, the fault handling device can send an instruction message to the contractor's network management server, instructing the contractor to share the network resources with the sharing party's user equipment.

[0086] In this way, when a network in a certain area fails, network resources can be provided to user equipment through the base stations of other operators in the same area that are not experiencing any failures. This eliminates the need to wait for the faulty network to be repaired and does not affect the normal use of user equipment, thus improving the efficiency of fault handling.

[0087] In some embodiments, combined Figure 4 ,like Figure 5 As shown, in S403 above, the method by which the fault handling equipment shares the network resources corresponding to the target operator with user equipment in the fault area through the base station corresponding to the target operator specifically includes:

[0088] S501, The fault handling equipment obtains the base station parameter configuration information corresponding to the faulty operator of the faulty network, and generates a first script based on the base station parameter configuration information.

[0089] The first script is used to instruct the base station parameters corresponding to the base station configuration and base station parameter configuration information of the target operator.

[0090] Specifically, since the base station corresponding to the target operator usually transmits services through the base station parameters corresponding to the target operator, when the base station corresponding to the target operator needs to share the network resources corresponding to the target operator with user equipment in the fault area, the base station corresponding to the target operator needs to configure the base station parameters corresponding to the faulty operator.

[0091] In this situation, the fault handling equipment can obtain the base station parameter configuration information corresponding to the faulty operator of the faulty network, and generate the first script based on the base station parameter configuration information through Robotic Process Automation (RPA) technology.

[0092] Optionally, the above base station parameter configuration information may include: base station name, base station cell identifier, Public Land Mobile Network (PLMN), base station Internet Protocol (IP) address, etc.

[0093] For example, when a China Unicom network failure occurs, the fault handling device can obtain the base station parameter configuration information of the China Unicom network and generate a first script based on the base station parameter configuration information of the China Unicom network. This first script is used to instruct the telecommunications base station to configure base station parameters corresponding to the base station parameter configuration information of the China Unicom network.

[0094] S502. The fault handling equipment obtains the network parameter configuration information of the faulty operating entity within a preset time period, and generates a second script based on the network parameter configuration information and operating information.

[0095] The second script is used to indicate the network parameters corresponding to the base station configuration and network parameter configuration information of the target operator.

[0096] Specifically, since the base station corresponding to the target operator usually transmits services through the network parameters corresponding to the target operator, when the base station corresponding to the target operator needs to share the network resources corresponding to the target operator with the user equipment in the fault area, the base station corresponding to the target operator needs to configure the network parameters corresponding to the faulty operator.

[0097] In this situation, the fault handling equipment can obtain the network parameter configuration information corresponding to the faulty operator of the faulty network, and generate a second script based on the network parameter configuration information through RPA technology.

[0098] Optionally, the above network parameter configuration information may include: network personalization parameters, network element backup parameters, etc.

[0099] For example, network personalization parameters could be: Circuit Switched Fallback (CSFB) in the main urban area needs to fall back to the 3rd Generation (3G) mobile communication network, while CSFB in rural areas needs to fall back to the 2nd Generation (2G) mobile communication network, etc.

[0100] Optionally, the preset time period can be any time period before the current time.

[0101] For example, when the Unicom network fails, the fault handling device can obtain the network parameter configuration information of the Unicom network from the previous day and generate a second script based on the network parameter configuration information of the Unicom network.

[0102] The second script is used to instruct the telecommunications base station to configure the network parameters corresponding to the network parameter configuration information of the Unicom network.

[0103] S503, the fault handling device sends a shared instruction message, including a first script and a second script, to the target network management device corresponding to the target operating entity, so that the target network management device executes the first script and the second script.

[0104] Among them, the sharing instruction message is used to instruct the target network management equipment to control the base station corresponding to the target operator to share the network resources corresponding to the target operator with the user equipment in the fault area.

[0105] Specifically, after generating the first script and the second script, the fault handling device can send a sharing instruction message, including the first script and the second script, to the target network management device corresponding to the target operator, instructing the target network management device to execute the first script and the second script. In this way, the target network management device can control the base station corresponding to the target operator to share the network resources corresponding to the target operator with user equipment within the fault area. In one possible implementation, the fault handling device can also import the first script and the second script into the target network management device via RPA technology, so that the target network management device can execute the first script and the second script.

[0106] In some embodiments, operational information includes operational status and operational load. (Combined with...) Figure 4 ,like Figure 6As shown, after the fault processing device obtains the operating information of the base station corresponding to the target operator in the fault area where no network fault has occurred, it also includes: S601, when the operating status is normal and the operating load is less than the first preset load, the fault processing device determines that the operating information of the base station corresponding to the target operator meets the preset bearing conditions.

[0107] Specifically, when the operating status is normal, it indicates that the base station corresponding to the target operator is operating normally. When the operating load is less than the first preset load, it indicates that the base station corresponding to the target operator can carry other services without affecting the services already being carried. In this case, the fault handling equipment determines that the operating information of the base station corresponding to the target operator meets the preset carrying conditions.

[0108] Optionally, the operating load can be the operating load of the base station corresponding to the target operator during busy hours.

[0109] Optionally, the first preset load can be set according to human needs, such as 85%, but this application embodiment does not limit this.

[0110] S602. When the operating status is abnormal and / or the operating load is greater than or equal to the first preset load, the fault handling equipment determines that the operating information of the base station corresponding to the target operator does not meet the preset bearing conditions.

[0111] Specifically, when the operating status is abnormal, it indicates that the base station corresponding to the target operator is not operating normally. In this case, the base station corresponding to the target operator cannot carry services. Therefore, the fault handling equipment determines that the operating information of the base station corresponding to the target operator does not meet the preset carrying conditions.

[0112] And / or, when the operating load is greater than or equal to the first preset load, it indicates that other services carried by the base station corresponding to the target operator may affect the services currently being carried. In this case, the fault handling equipment determines that the operating information of the base station corresponding to the target operator meets the preset carrying conditions.

[0113] In some embodiments, when the operating state is normal, the operating load is less than a first preset load, and the operating load is greater than a second preset load, combined with Figure 4 ,like Figure 7 As shown, in S403 above, the fault handling equipment shares the network resources corresponding to the target operator with user equipment in the fault area through the base station corresponding to the target operator, including:

[0114] S701. The fault handling equipment determines the number of shared resource blocks (RBs) based on the operating load.

[0115] The second preset load is greater than 0 and less than the first preset load.

[0116] Specifically, when the operating status is normal, the operating load is less than the first preset load, and the operating load is greater than the second preset load, it indicates that the base station corresponding to the target operator can carry other services without affecting the currently carried services, but cannot carry too many services. In this case, the fault handling equipment can determine the number of shared RBs based on the operating load.

[0117] Optionally, the second preset load can be set according to human needs, such as 70%, but this application embodiment does not limit this.

[0118] Optionally, the number of shared RBs is inversely proportional to the operating load; that is, the higher the operating load, the fewer the number of shared RBs. Conversely, the lower the operating load, the more shared RBs.

[0119] For example, when the contractor's peak load is below 70%, the number of shared RBs is not limited. When the contractor's peak load is above 70%, the number of shared RBs is limited to 20, ensuring network availability for the shared party while maintaining user experience for the contractor.

[0120] S702. The fault handling equipment shares network resources corresponding to the number of RBs with user equipment in the fault area through the base station corresponding to the target operator.

[0121] In some embodiments, combined Figure 6 ,like Figure 8 As shown, after the faulty network is restored, the fault handling method also includes:

[0122] S801, The fault handling equipment receives the fault recovery message.

[0123] Among them, the fault recovery message is used to indicate the recovery of the faulty network.

[0124] Specifically, once the faulty network is restored, the network management server of the faulty network can send a fault restoration message to the fault handling equipment.

[0125] S802. The fault handling device sends a sharing termination message to the target network management device corresponding to the target operating entity, so that the target network management device executes the sharing rollback script.

[0126] Among them, the shared rollback script is used to instruct the target network management equipment to control the base station corresponding to the target operator not to share the network resources corresponding to the target operator with user equipment in the fault area.

[0127] Optionally, the shared rollback script can be a rollback script corresponding to the first script and the second script. For example, when the first script is used to change a base station configuration parameter, the shared rollback script is used to restore the changed base station configuration parameter to the original base station configuration parameter. Correspondingly, when the first script is used to change a network configuration parameter, the shared rollback script is used to restore the changed network configuration parameter to the original network configuration parameter. Based on the above example, after fault recovery, if the sharing party's base station is operating normally, the shared rollback script is executed in the contractor's network management system using RPA technology. After clearing out the sharing party's user equipment on the shared carrier using a high-priority blocking method, the sharing function is disabled.

[0128] High-priority blocking refers to clearing out user equipment on the shared carrier only after the user equipment has finished its service.

[0129] The foregoing mainly describes the solutions provided by the embodiments of this application from a methodological perspective. To achieve the above functions, it includes corresponding hardware structures and / or software modules for executing each function. Those skilled in the art should readily recognize that, based on the units and algorithm steps of the examples described in conjunction with the embodiments disclosed herein, this application can be implemented in hardware or a combination of hardware and computer software. Whether a function is executed in hardware or by computer software driving hardware depends on the specific application and design constraints of the technical solution. Those skilled in the art can use different methods to implement the described functions for each specific application, but such implementation should not be considered beyond the scope of this application.

[0130] This application embodiment can divide the fault handling device into functional modules according to the above method example. For example, each function can be divided into a separate functional module, or two or more functions can be integrated into one processing module. The integrated module can be implemented in hardware or as a software functional module. Optionally, the module division in this application embodiment is illustrative and only represents one logical functional division; other division methods may be used in actual implementation.

[0131] like Figure 9 The diagram shown is a structural schematic of a fault handling device provided in an embodiment of this application. This fault handling device can be used to perform... Figures 4-8 The method for handling the fault is shown. Figure 9 The fault handling device shown includes: an acquisition unit 901 and a processing unit 902;

[0132] Acquisition unit 901 is used to acquire the fault area of ​​the faulty network;

[0133] The acquisition unit 901 is also used to acquire the operation information of the base station corresponding to the target operator that has not experienced network failure within the fault area;

[0134] The processing unit 902 is used to share the network resources corresponding to the target operator with user equipment in the fault area through the base station corresponding to the target operator when the operation information of the base station corresponding to the target operator meets the preset bearing conditions.

[0135] Optionally, the processing unit 902 is specifically used for:

[0136] Obtain the base station parameter configuration information corresponding to the faulty operator of the faulty network, and generate a first script based on the base station parameter configuration information; the first script is used to indicate the base station configuration of the target operator and the base station parameters corresponding to the base station parameter configuration information.

[0137] Obtain the network parameter configuration information of the faulty operator within a preset time period, and generate a second script based on the network parameter configuration information and operation information; the second script is used to instruct the target operator to configure the network parameters corresponding to the base station configuration information.

[0138] A sharing instruction message, including a first script and a second script, is sent to the target network management device corresponding to the target operator, so that the target network management device executes the first script and the second script; the sharing instruction message is used to instruct the target network management device to control the base station corresponding to the target operator to share the network resources corresponding to the target operator with the user equipment in the fault area.

[0139] Optionally, the operational information includes operational status and operational load;

[0140] The processing unit 902 is also used to determine that the operating information of the base station corresponding to the target operator meets the preset bearing conditions when the operating state is normal and the operating load is less than the first preset load.

[0141] The processing unit 902 is also used to determine that the operating information of the base station corresponding to the target operator does not meet the preset bearing conditions when the operating state is abnormal and / or the operating load is greater than or equal to the first preset load.

[0142] Optionally, when the operating state is normal, the operating load is less than the first preset load, and the operating load is greater than the second preset load, the processing unit 902 is specifically used for:

[0143] The number of shared resource blocks (RBs) is determined based on the operating load; the second preset load is greater than 0 and less than the first preset load.

[0144] The target operator shares network resources corresponding to the number of base stations (RBs) with user equipment within the fault area through the base station corresponding to the target operator.

[0145] Optionally, the fault handling device further includes: a receiving unit 903 and a transmitting unit 904;

[0146] The receiving unit 903 is used to receive a fault recovery message; the fault recovery message is used to indicate the fault recovery of the faulty network.

[0147] The sending unit 904 is used to send a sharing end message to the target network management device corresponding to the target operator, so that the target network management device executes the sharing rollback script; the sharing rollback script is used to instruct the target network management device to control the base station corresponding to the target operator not to share the network resources corresponding to the target operator with user equipment in the fault area.

[0148] This application also provides a computer-readable storage medium, which includes computer-executable instructions that, when executed on a computer, cause the computer to perform the fault handling method provided in the above embodiments.

[0149] This application also provides a computer program that can be directly loaded into a memory and contains software code. After being loaded and executed by a computer, the computer program can implement the fault handling method provided in the above embodiments.

[0150] Those skilled in the art will recognize that, in one or more of the examples above, the functions described in this application can be implemented using hardware, software, firmware, or any combination thereof. When implemented in software, these functions can be stored in a computer-readable medium or transmitted as one or more instructions or code on a computer-readable medium. Computer-readable media include computer-readable storage media and communication media, wherein communication media include any medium that facilitates the transmission of a computer program from one place to another. Storage media can be any available medium accessible to a general-purpose or special-purpose computer.

[0151] Through the above description of the embodiments, those skilled in the art can clearly understand that, for the sake of convenience and brevity, only the division of the above functional modules is used as an example. In actual applications, the above functions can be assigned to different functional modules as needed, that is, the internal structure of the device can be divided into different functional modules to complete all or part of the functions described above.

[0152] In the several embodiments provided in this application, it should be understood that the disclosed apparatus and methods can be implemented in other ways. For example, the apparatus embodiments described above are merely illustrative; for instance, the division of modules or units is only a logical functional division, and other division methods may exist in actual implementation. For example, multiple units or components may be combined or integrated into another device, or some features may be ignored or not executed. Furthermore, the shown or discussed mutual couplings, direct couplings, or communication connections may be through some interfaces; indirect couplings or communication connections between devices or units may be electrical, mechanical, or other forms. Units described as separate components may or may not be physically separate; components shown as units may be one physical unit or multiple physical units, i.e., they may be located in one place or distributed in multiple different places. Some or all of the units can be selected to achieve the purpose of this embodiment according to actual needs.

[0153] Furthermore, the functional units in the various embodiments of this application can be integrated into one processing unit, or each unit can exist physically separately, or two or more units can be integrated into one unit. The integrated unit can be implemented in hardware or as a software functional unit. If the integrated unit is implemented as a software functional unit and sold or used as an independent product, it can be stored in a readable storage medium. Based on this understanding, the technical solution of the embodiments of this application, in essence, or the part that contributes to the prior art, or all or part of the technical solution, can be embodied in the form of a software product. This software product is stored in a storage medium and includes several instructions to cause a device (which may be a microcontroller, chip, etc.) or processor to execute all or part of the steps of the methods described in the various embodiments of this application. The aforementioned storage medium includes various media capable of storing program code, such as USB flash drives, portable hard drives, ROM, RAM, magnetic disks, or optical disks.

[0154] The above description is merely a specific embodiment of this application, but the scope of protection of this application is not limited thereto. Any variations or substitutions that can be easily conceived by those skilled in the art within the technical scope disclosed in this application should be included within the scope of protection of this application. Therefore, the scope of protection of this application should be determined by the scope of the claims.

Claims

1. A fault handling method, characterized in that, include: Identify the faulty region of the faulty network; Obtain the operational information of the base stations of the target operators within the fault area that have not experienced network failures; The operational information includes operational status and operational load; When the operating status is normal and the operating load is less than the first preset load, it is determined that the operating information of the base station corresponding to the target operator meets the preset bearing conditions. When the operating information of the base station corresponding to the target operator meets the preset bearing conditions, the network resources corresponding to the target operator are shared with the user equipment in the fault area through the base station corresponding to the target operator. The step of sharing the network resources corresponding to the target operator with user equipment in the fault area through the base station corresponding to the target operator includes: The system obtains the base station parameter configuration information corresponding to the faulty operator of the faulty network, and generates a first script based on the base station parameter configuration information using Robotic Process Automation (RPA) technology. The first script is used to instruct the base station corresponding to the target operator to configure the base station parameters corresponding to the base station parameter configuration information. The base station parameter configuration information includes: base station name, base station cell identifier, Public Land Mobile Network (PLMN), and base station Internet Protocol (IP) address. The system obtains the network parameter configuration information of the faulty operator within a preset time period prior to the current moment, and generates a second script based on the network parameter configuration information and the operational information using the RPA technology. The second script is used to instruct the base station corresponding to the target operator to configure network parameters corresponding to the network parameter configuration information. The network parameter configuration information includes: personalized network parameters and network element backup parameters. The personalized network parameters include: circuit-switched fallback (CSFB) in the main urban area needs to fall back to the third-generation mobile communication network, and CSFB in rural areas needs to fall back to the second-generation mobile communication network. A sharing instruction message, including the first script and the second script, is sent to the target network management device corresponding to the target operator, so that the target network management device executes the first script and the second script; the sharing instruction message is used to instruct the target network management device to control the base station corresponding to the target operator to share the network resources corresponding to the target operator with the user equipment in the fault area.

2. The fault handling method according to claim 1, characterized in that, After obtaining the operational information of the base stations corresponding to the target operators within the fault area that have not experienced network failures, the method further includes: When the operating state is abnormal, and / or the operating load is greater than or equal to the first preset load, it is determined that the operating information of the base station corresponding to the target operator does not meet the preset bearing conditions.

3. The fault handling method according to claim 2, characterized in that, When the operating state is normal, the operating load is less than a first preset load, and the operating load is greater than a second preset load, the sharing of network resources corresponding to the target operator with user equipment in the fault area through the base station corresponding to the target operator includes: The number of shared resource blocks (RBs) is determined based on the operating load; the second preset load is greater than 0 and less than the first preset load. The target operator's corresponding base station shares network resources, corresponding to the number of RBs, with user equipment within the fault area.

4. The fault handling method according to claim 1, characterized in that, Also includes: Receive fault recovery message; The fault recovery message is used to indicate the fault recovery of the faulty network; A sharing end message is sent to the target network management device corresponding to the target operator, so that the target network management device executes a sharing rollback script; the sharing rollback script is used to instruct the target network management device to control the base station corresponding to the target operator not to share the network resources corresponding to the target operator with user equipment in the fault area.

5. A fault handling device, characterized in that, include: Acquisition unit and processing unit; The acquisition unit is used to acquire the faulty area of ​​the faulty network; The acquisition unit is further configured to acquire the operating information of the base station corresponding to the target operator that has not experienced network failure within the fault area; the operating information includes operating status and operating load; The processing unit is used to determine that the operating information of the base station corresponding to the target operator meets the preset bearing conditions when the operating state is normal and the operating load is less than the first preset load. The processing unit is configured to share the network resources corresponding to the target operator with the user equipment in the fault area through the base station corresponding to the target operator when the operation information of the base station corresponding to the target operator meets the preset bearing conditions. The processing unit is specifically used for: Obtain the base station parameter configuration information corresponding to the faulty operator of the faulty network, and generate a first script based on the base station parameter configuration information using RPA technology; The first script is used to instruct the target operator to configure the base station parameters corresponding to the base station parameter configuration information; The base station parameter configuration information includes: base station name, base station cell identifier, Public Land Mobile Network (PLMN), and base station Internet Protocol (IP) address. The system obtains the network parameter configuration information of the faulty operator within a preset time period prior to the current moment, and generates a second script based on the network parameter configuration information and the operational information using the RPA technology. The second script is used to instruct the base station corresponding to the target operator to configure network parameters corresponding to the network parameter configuration information. The network parameter configuration information includes: personalized network parameters and network element backup parameters. The personalized network parameters include: circuit-switched fallback (CSFB) in the main urban area needs to fall back to the third-generation mobile communication network, and CSFB in rural areas needs to fall back to the second-generation mobile communication network. A sharing instruction message, including the first script and the second script, is sent to the target network management device corresponding to the target operator, so that the target network management device executes the first script and the second script; the sharing instruction message is used to instruct the target network management device to control the base station corresponding to the target operator to share the network resources corresponding to the target operator with the user equipment in the fault area.

6. The fault handling device according to claim 5, characterized in that, The processing unit is further configured to determine that the operating information of the base station corresponding to the target operator does not meet the preset bearing conditions when the operating state is abnormal and / or the operating load is greater than or equal to the first preset load.

7. The fault handling device according to claim 6, characterized in that, When the operating state is normal, the operating load is less than the first preset load, and the operating load is greater than the second preset load, the processing unit is specifically used for: The number of shared resource blocks (RBs) is determined based on the operating load. The second preset load is greater than 0 and less than the first preset load; The target operator's corresponding base station shares network resources, corresponding to the number of RBs, with user equipment within the fault area.

8. The fault handling device according to claim 5, characterized in that, Also includes: Receiving unit and transmitting unit; The receiving unit is used to receive fault recovery messages; The fault recovery message is used to indicate the fault recovery of the faulty network; The sending unit is used to send a sharing end message to the target network management device corresponding to the target operator, so that the target network management device executes the sharing rollback script; the sharing rollback script is used to instruct the target network management device to control the base station corresponding to the target operator not to share the network resources corresponding to the target operator with user equipment in the fault area.

9. A fault handling device, characterized in that, It includes a memory and a processor; the memory is used to store computer execution instructions, and the processor is connected to the memory via a bus; when the fault handling device is running, the processor executes the computer execution instructions stored in the memory, so that the fault handling device performs the fault handling method as described in any one of claims 1-4.

10. A computer-readable storage medium, characterized in that, The computer-readable storage medium includes computer-executable instructions that, when executed on a computer, cause the computer to perform the fault handling method as described in any one of claims 1-4.

Images