WO2023165481A1

WO2023165481A1 - Network fault processing method, terminal, access network device, and core network device

Info

Publication number: WO2023165481A1
Application number: PCT/CN2023/078818
Authority: WO
Inventors: 韩鲁峰; 吴晓波
Original assignee: 维沃移动通信有限公司
Priority date: 2022-03-04
Filing date: 2023-02-28
Publication date: 2023-09-07
Also published as: CN116744346A

Abstract

The present application belongs to the technical field of communications. Disclosed are a network fault processing method, a terminal, an access network device, and a core network device. The network fault processing method in the embodiments of the present application comprises: when it is determined that a first network function entity in a first network has a fault, a terminal executing at least one of the following operations: updating a network selection priority corresponding to the first network, wherein the network selection priority corresponding to the first network is lower than a network selection priority corresponding to a second network, and/or the network selection priority corresponding to the first network is lower than a network selection priority corresponding to the first network when the fault has not occurred; and sending a first request message to an access network device, wherein the first request message is used for instructing the access network device to communicate with a target network function entity in the second network, and the target network function entity in the second network has the same network function with the first network function entity in the first network.

Description

Network fault handling method, terminal, access network equipment and core network equipment

Cross References to Related Applications

This application claims the priority of the Chinese patent application with the application number 202210211070.6 filed on March 4, 2022, and the title of the invention is "Network fault processing method, terminal, access network equipment and core network equipment", which is by reference All are incorporated into this application.

technical field

The present application belongs to the technical field of communication, and in particular relates to a network failure processing method, terminal, access network equipment and core network equipment.

Background technique

The existing mobile communication system may have more than one operator in a specific country and region, and each operator is distinguished from each other by the operator's identification Public Land Mobile Network (Public Land Mobile Network, PLMN); usually the terminal passes the PLMN Get service.

In related technologies, when a network function fails, the terminal cannot obtain network services. For example, when the PLMN, such as the network function of the Home Public Land Mobile Network (HPLMN), fails but the cell is available, the terminal will try to register with the cell of the PLMN, resulting in the failure of the registration, which further causes the terminal to fail to obtain normal information. network service.

Contents of the invention

Embodiments of the present application provide a network failure processing method, a terminal, an access network device, and a core network device, which can solve the problem that the terminal cannot obtain normal network services.

In the first aspect, a method for handling network faults is provided, including:

In a case where it is determined that the first network functional entity of the first network fails, the terminal performs at least one of the following operations:

Updating the network selection priority corresponding to the first network; the network selection priority corresponding to the first network is lower than the network selection priority corresponding to the second network, and/or, the network selection priority corresponding to the first network The level is lower than the network selection priority corresponding to the first network when no failure occurs;

The terminal sends a first request message to the access network device; the first request message is used to instruct the access network device to communicate with the target network function entity of the second network; the target network function entity of the second network communicates with the target network function entity The first network function entities in the first network have the same network function.

In the second aspect, a method for handling network faults is provided, including:

When it is determined that the first network functional entity of the first network fails, the access network device communicates with the target network functional entity of the second network; the target network functional entity of the second network communicates with the target network functional entity of the first network The first network function entity has the same network function.

In the third aspect, a method for handling network faults is provided, including:

The core network device receives the second request message sent by the access network device; the second request message is sent by the access network device when it is determined that the first network functional entity of the first network fails;

In the case that the core network device is a non-faulty network function entity in the first network, the core network device communicates with a second network function entity of a second network; the second network function entity communicates with the first network function entity a first network functional entity of a network has the same network function;

In the case where the core network device is a target network functional entity in the second network, the core network device communicates with an unfaulted network functional entity in the first network, or, the core network device communicates with the The third network function entity in the second network communicates; the third network function entity has the same network function as the non-faulty network function entity in the first network.

In a fourth aspect, a device for processing network faults is provided, including: a first updating module and/or a first sending module;

When it is determined that the first network functional entity of the first network fails, the first update module is configured to update the network selection priority corresponding to the first network; the network selection priority corresponding to the first network is lower than the network selection priority corresponding to the second network, and/or, the network selection priority corresponding to the first network is lower than the network selection priority corresponding to the first network when no failure occurs;

The first sending module is configured to send a first request message to the access network device; the first request message is used to instruct the access network device to communicate with a target network function entity of the second network; the second The target network functional entity of the network has the same network function as the first network functional entity in the first network.

In the fifth aspect, a device for processing network faults is provided, including:

The first communication module is configured to communicate with the target network function entity of the second network when it is determined that the first network function entity of the first network fails; the target network function entity of the second network communicates with the first network function entity The first network function entities in the network have the same network function.

In a sixth aspect, a device for processing network faults is provided, including:

The first receiving module is configured to receive a second request message sent by the access network device; the second request message is sent by the access network device when it is determined that the first network functional entity of the first network fails ;

A second communication module, configured to communicate with a second network function entity of a second network when the core network device is a non-faulty network function entity in the first network; the second network function entity communicates with the network function entity The first network functional entity of the first network has the same network function;

A third communication module, configured to communicate with an unfaulted network functional entity in the first network when the core network device is a target network functional entity in the second network, or, communicate with the core network device and The third network function entity in the second network communicates; the third network function entity has the same network function as the non-faulty network function entity in the first network.

In a seventh aspect, there is provided a terminal, the terminal includes a processor and a memory, the memory stores programs or instructions that can run on the processor, and when the programs or instructions are executed by the processor, the following steps are implemented: The steps of the method in one aspect.

According to an eighth aspect, a terminal is provided, including a processor and a communication interface. When it is determined that a first network functional entity of the first network fails, the processor is configured to update the option corresponding to the first network. Network priority; the network selection priority corresponding to the first network is lower than the network selection priority corresponding to the second network, and/or, the network selection priority corresponding to the first network is lower than the network selection priority corresponding to the first network The corresponding network selection priority when no failure occurs; the communication interface is used to send the first A request message; the first request message is used to instruct the access network device to communicate with the target network function entity of the second network; the target network function entity of the second network communicates with the first network in the first network Functional entities have the same network functions.

In a ninth aspect, an access network device is provided, the access network device includes a processor and a memory, the memory stores programs or instructions that can run on the processor, and the programs or instructions are processed by the processor implement the steps of the method for handling network faults as described in the second aspect when executed by the controller.

In a tenth aspect, an access network device is provided, including a processor and a communication interface, wherein the communication interface is used to communicate with a second network when it is determined that the first network functional entity of the first network fails. The target network function entity communicates; the target network function entity of the second network has the same network function as the first network function entity in the first network.

In an eleventh aspect, a core network device is provided, the core network device includes a processor and a memory, the memory stores programs or instructions that can run on the processor, and the programs or instructions are executed by the processor During execution, the steps of the method for handling network faults as described in the third aspect are realized.

In a twelfth aspect, a core network device is provided, including a processor and a communication interface, wherein the communication interface is used to receive a second request message sent by the access network device; the second request message is the sent by the network access device when it is determined that the first network functional entity of the first network fails;

In the case that the core network device is a non-faulty network functional entity in the first network, it communicates with a second network functional entity of the second network; the second network functional entity communicates with the first network functional entity of the first network The network functional entity has the same network function;

If the core network device is a target network function entity in the second network, communicate with an unfaulted network function entity in the first network, or, the core network device communicates with a target network function entity in the second network. Three network function entities communicate; the third network function entity has the same network function as the non-faulty network function entity in the first network.

A thirteenth aspect provides a system for processing network faults, including at least two of a terminal, an access network device, and a core network device, the terminal can be used to perform the steps of the method described in the first aspect, the The above access network equipment can be used to execute the steps of the method as described in the second aspect, the core The network device can be used to perform the steps of the method as described in the third aspect.

A fourteenth aspect provides a readable storage medium, on which a program or an instruction is stored, and when the program or instruction is executed by a processor, the steps of the method as described in the first aspect are implemented, or The steps of the method described in the second aspect, or the steps of implementing the method described in the third aspect.

In a fifteenth aspect, there is provided a chip, the chip includes a processor and a communication interface, the communication interface is coupled to the processor, and the processor is used to run a program or an instruction to implement the method described in the first aspect method, or implement the steps of the method as described in the second aspect, or implement the steps of the method as described in the third aspect.

In a sixteenth aspect, a computer program/program product is provided, the computer program/program product is stored in a storage medium, and the computer program/program product is executed by at least one processor to implement the The steps of the method, or realize the steps of the method described in the second aspect, or realize the steps of the method described in the third aspect.

In this embodiment of the present application, when it is determined that the first network functional entity of the first network fails, the terminal updates the network selection priority corresponding to the first network, and/or, the terminal sends an instruction to the access network device The first request message communicated between the access network device and the target network function entity of the second network, and the target network function entity of the second network replaces the failed first network function entity in the first network, so that the terminal can obtain the normal network function entity Serve.

Description of drawings

FIG. 1 is a block diagram of a wireless communication system applicable to an embodiment of the present application;

FIG. 2 is one of the schematic flow charts of the method for processing a network failure provided in the embodiment of the present application;

Fig. 3 is the second schematic flow diagram of the method for processing network faults provided by the embodiment of the present application;

Fig. 4 is the third schematic flow diagram of the method for handling network faults provided by the embodiment of the present application;

FIG. 5 is a fourth schematic flow diagram of a method for processing a network failure provided in an embodiment of the present application;

FIG. 6 is a fifth schematic flow diagram of a method for processing a network fault provided in an embodiment of the present application;

FIG. 7 is a sixth schematic flow diagram of a method for handling a network failure provided in an embodiment of the present application;

FIG. 8 is one of the schematic diagrams of scenarios of a method for handling a network failure provided in an embodiment of the present application;

FIG. 9 is the second schematic diagram of the scene of the method for handling network faults provided by the embodiment of the present application;

FIG. 10 is a seventh schematic flow diagram of a method for handling a network failure provided in an embodiment of the present application;

FIG. 11 is the eighth schematic flow diagram of the method for handling network faults provided by the embodiment of the present application;

Fig. 12 is the third schematic diagram of the scene of the method for handling network faults provided by the embodiment of the present application;

FIG. 13 is one of the interaction diagrams of the method for processing network faults provided by the embodiment of the present application;

FIG. 14 is a fourth schematic diagram of a scene of a method for handling a network fault provided by an embodiment of the present application;

FIG. 15 is the second interaction diagram of the method for handling network faults provided by the embodiment of the present application;

Fig. 16 is the fifth schematic diagram of the scene of the method for handling network faults provided by the embodiment of the present application;

Fig. 17 is the third interaction diagram of the method for handling network faults provided by the embodiment of the present application;

Fig. 18 is the sixth schematic diagram of the scene of the method for handling network faults provided by the embodiment of the present application;

FIG. 19 is the fourth interaction diagram of the method for handling network faults provided by the embodiment of the present application;

Fig. 20 is the seventh schematic diagram of the scene of the method for handling network faults provided by the embodiment of the present application;

Fig. 21 is the fifth interaction diagram of the method for handling network faults provided by the embodiment of the present application;

Fig. 22 is the eighth schematic diagram of the scene of the method for handling network faults provided by the embodiment of the present application;

FIG. 23 is the sixth interaction diagram of the method for handling network faults provided by the embodiment of the present application;

FIG. 24 is one of the structural schematic diagrams of the network failure processing device provided by the embodiment of the present application;

Fig. 25 is the second structural schematic diagram of the network failure processing device provided by the embodiment of the present application;

Fig. 26 is the third schematic structural diagram of the network failure processing device provided by the embodiment of the present application;

Fig. 27 is a schematic structural diagram of a communication device provided by an embodiment of the present application;

FIG. 28 is a schematic diagram of a hardware structure of a terminal according to an embodiment of the present application;

FIG. 29 is one of the schematic diagrams of the hardware structure of the network side device according to the embodiment of the present application;

FIG. 30 is a second schematic diagram of a hardware structure of a network side device according to an embodiment of the present application.

Detailed ways

The technical solutions in the embodiments of the present application will be clearly described below in conjunction with the drawings in the embodiments of the present application. Obviously, the described embodiments are part of the embodiments of the present application, but not all of them. Based on the embodiments in this application, all other implementations obtained by those of ordinary skill in the art For example, all belong to the protection scope of this application.

The terms "first", "second" and the like in the specification and claims of the present application are used to distinguish similar objects, and are not used to describe a specific sequence or sequence. It is to be understood that the terms so used are interchangeable under appropriate circumstances such that the embodiments of the application are capable of operation in sequences other than those illustrated or described herein and that "first" and "second" distinguish objects. It is usually one category, and the number of objects is not limited. For example, there may be one or more first objects. In addition, "and/or" in the description and claims means at least one of the connected objects, and the character "/" generally means that the related objects are an "or" relationship.

It is worth pointing out that the technology described in the embodiment of this application is not limited to the Long Term Evolution (Long Term Evolution, LTE)/LTE-Advanced (LTE-Advanced, LTE-A) system, and can also be used in other wireless communication systems, such as code Code Division Multiple Access (CDMA), Time Division Multiple Access (TDMA), Frequency Division Multiple Access (FDMA), Orthogonal Frequency Division Multiple Access, OFDMA), Single-carrier Frequency Division Multiple Access (Single-carrier Frequency Division Multiple Access, SC-FDMA) and other systems. The terms "system" and "network" in the embodiments of the present application are often used interchangeably, and the described technology can be used for the above-mentioned system and radio technology, and can also be used for other systems and radio technologies. The following description describes the New Radio (NR) system for illustrative purposes, and uses NR terminology in most of the following descriptions, but these techniques can also be applied to applications other than NR system applications, such as the 6th generation (6 ^th Generation, 6G) communication system.

FIG. 1 is a block diagram of a wireless communication system to which an embodiment of the present application is applicable. The wireless communication system includes a terminal 11 and a network side device 12 . Wherein, the terminal 11 can be a mobile phone, a tablet computer (Tablet Personal Computer), a laptop computer (Laptop Computer) or a notebook computer, a personal digital assistant (Personal Digital Assistant, PDA), a palmtop computer, a netbook, a super mobile personal computer (ultra-mobile personal computer, UMPC), mobile Internet device (Mobile Internet Device, MID), augmented reality (augmented reality, AR) / virtual reality (virtual reality, VR) equipment, robot, wearable device (Wearable Device) , Vehicle Equipment (VUE), Pedestrian terminal equipment (PUE), smart home (household equipment with wireless communication functions, such as refrigerators, TVs, washing machines or furniture, etc.), game consoles, personal computers (personal computers, PCs), teller machines or self-service machines and other terminal-side equipment, can Wearable devices include: smart watches, smart bracelets, smart headphones, smart glasses, smart jewelry (smart bracelets, smart bracelets, smart rings, smart necklaces, smart anklets, smart anklets, etc.), smart wristbands, smart clothing, etc. . It should be noted that, the embodiment of the present application does not limit the specific type of the terminal 11 . The network side device 12 may include an access network device or a core network device, wherein the access network device 12 may also be called a radio access network device, a radio access network (Radio Access Network, RAN), a radio access network function, or Wireless access network unit. The access network device 12 may include a base station, a WLAN access point, or a WiFi node, etc., and the base station may be called a node B, an evolved node B (eNB), an access point, a base transceiver station (Base Transceiver Station, BTS), a radio Base station, radio transceiver, Basic Service Set (BSS), Extended Service Set (ESS), Home Node B, Home Evolved Node B, Transmitting Receiving Point (TRP) or all As long as the same technical effect is achieved, the base station is not limited to a specific technical vocabulary. It should be noted that in this embodiment of the application, only the base station in the NR system is used as an example for introduction, and The specific type of the base station is not limited. The core network equipment may include but not limited to at least one of the following: core network node, core network function, mobility management entity (Mobility Management Entity, MME), access mobility management function (Access and Mobility Management Function, AMF), session management function (Session Management Function, SMF), user plane function (User Plane Function, UPF), policy control function (Policy Control Function, PCF), policy and charging rules function unit (Policy and Charging Rules Function, PCRF), edge application service Discovery function (Edge Application Server Discovery Function, EASDF), unified data management (Unified Data Management, UDM), unified data storage (Unified Data Repository, UDR), home subscriber server (Home Subscriber Server, HSS), centralized network configuration ( Centralized network confguration, CNC), network storage function (Network Repository Function, NRF), network exposure function (Network Exposure Function, NEF), local NEF (Local NEF, or L-NEF), binding support function (Binding Support Function, BSF), Application Function (Application Function, AF), etc. It should be noted that, in the embodiment of the present application, only the core network equipment in the NR system is used as an example for introduction, and the specific type of the core network equipment is not limited.

The method for handling network faults provided by the embodiments of the present application will be described in detail below through some embodiments and application scenarios with reference to the accompanying drawings.

The network failure processing method provided by the embodiment of the present application can be applied to the scenario where the network functional entity of the network fails and the access network equipment of the network does not fail. The first request message communicated between the device and the target network function entity of the second network, and the target network function entity of the second network replaces the failed first network function entity in the first network, so that the terminal can obtain normal network services.

Fig. 2 is one of the schematic flow charts of the method for processing a network failure provided in the embodiment of the present application. As shown in Fig. 2, the method includes the following steps:

Step 201. When it is determined that the first network functional entity of the first network fails, the terminal performs at least one of the following operations: update the network selection priority corresponding to the first network; the network selection priority corresponding to the first network is lower than The network selection priority corresponding to the second network, and/or, the network selection priority corresponding to the first network is lower than the network selection priority corresponding to the first network when no failure occurs;

Send a first request message to the access network device; the first request message is used to instruct the access network device to communicate with the target network functional entity of the second network; the target network functional entity of the second network communicates with the first network in the first network Functional entities have the same network functions.

Wherein, the access network device may be an access network device shared by the first network and the second network, or may be an access network device corresponding to the first network that is not shared with the second network, or may be an access network device of the second network Corresponding access network equipment that is not shared with the first network; the first network functional entity may be a failed network functional entity such as AMF, SMF, or UPF, and when the first network functional entity is AMF, the target network functional entity The entity is also an AMF; when the first network function entity is an SMF, the target network function entity is also an SMF.

For example, in the case that the first network functional entity of the first network fails, the terminal updates the network selection priority corresponding to the first network. The specific update method may be to maintain a list, in which Add a network that lowers the priority of network selection; for example, if the first network is HPLMN and the second network is Visited Public Land Mobile Network (VPLMN), when both HPLMN and VPLMN are available networks, the terminal can use HPLMN is added to the list to reduce the network selection priority corresponding to HPLMN, so that the network selection priority corresponding to VPLMN is higher than that corresponding to HPLMN, and it can also make the network selection priority corresponding to HPLMN lower than HPLMN. The network selection priority corresponding to the fault.

For example, when the first network functional entity of the first network fails, the terminal sends to the access network device a first request message for instructing the access network device to communicate with the target network functional entity of the second network, and then When the network access device receives the first request message, it communicates with the target network function entity of the second network; the target network function entity of the second network provides the terminal with the same network function as that of the first network function entity in the first network network service.

It should be noted that this application does not limit the type of the first network functional entity that fails in the first network, and it may be other faulty network functional entities in the first network besides AMF, SMF or UPF.

It should be noted that the network functional entities included in the first network may be integrated on one device or independent devices; the network functional entities included in the second network may be integrated on one device or independent equipment, which is not limited in this application.

In the network failure processing method provided by the embodiment of the present application, when the first network functional entity of the first network fails, the terminal updates the network selection priority corresponding to the first network, and/or, the terminal sends a report to the access network device sending a first request message for instructing the access network device to communicate with the target network function entity of the second network, and the target network function entity of the second network replaces the failed first network function entity in the first network, so that the terminal can Get normal network services.

Fig. 3 is the second schematic flow diagram of the network failure processing method provided by the embodiment of the present application. As shown in Fig. 3, before performing step 201, the method further includes the following steps:

Step 202, the terminal receives a failure notification about the first network, and determines that a first network functional entity of the first network fails.

Wherein, the fault notification includes at least one of the following items: the first Indication information; second indication information used to indicate a faulty network function entity in the first network; third indication information used to indicate a non-faulty network function entity in the first network, and the faulty network function entity includes the first network A functional entity, the non-faulty network functional entity does not include the first network functional entity.

The first request message includes at least one of the following items: first indication information used to indicate that the first network fails; second indication information used to indicate a failed network function entity in the first network; The third indication information of the faulty network function entity, the faulty network function entity includes the first network function entity, and the non-faulty network function entity does not include the first network function entity.

Wherein, the non-faulty network functional entity in the first network may be an emergency service or a short message service.

For example, the terminal may receive a fault notification of the first network sent by an unfaulted network functional entity in the first network, where the unfaulted network functional entity may be an AMF, SMF, UPF, or a location management function (Location Management Function, LMF), etc. ; The failure notification of the first network sent by the access network device in the first network may also be received, which is not limited in this application.

Optionally, the failure notification may be carried by a Non-access stratum (Non-access stratum, NAS) message or a Radio Resource Control (Radio Resource Control, RRC) message, wherein the NAS message may be a de-registration message, and in the de-registration message Add the reason that the first network fails; the NAS message can also be a terminal configuration update (UE configuration update, UCU) message; optionally, add the reason that the first network fails in the UCU message; the RRC message can be a broadcast message or The RRC reconfiguration message carries the network identifier of the first network in the broadcast message, and indicates the failure, the cause value of the failure, and the like in the RRC reconfiguration message.

Optionally, the first request message is used to request registration to the second network, or the first request message is used to request to obtain service data.

For example, in the case that the failure notification of the first network includes first indication information for indicating that a failure occurs in the first network, when the terminal receives the failure notification of the first network, it determines that the failure occurs in the first network. A request message carries first indication information for indicating that the first network fails.

For example, when the failure notification of the first network includes first indication information indicating that the first network has failed and second indication information indicating the faulty network function entity in the first network, the terminal receives the second indication information When a failure notification of a network is made, based on the first indication information and the second indication information, the network function entity of the specific failure in the first network is determined, for example, it is determined that the first network cannot provide normal services or emergency services, etc., in the first request message The first indication information used to indicate that the first network fails and the second indication information used to indicate the failed network function entity in the first network may be carried.

For example, when the fault notification of the first network includes the first indication information used to indicate that the first network has failed and the third indication information used to indicate the unfaulted network functional entity in the first network, the terminal receives When the first network is notified of a failure, based on the first indication information and the third indication information, it is determined that there is no faulty network function entity in the first network, and the first request message may carry the first indication information used to indicate that the first network has failed. and the third indication information used to indicate the non-faulty network functional entity in the first network, so that the access network device can determine the faulty network functional entity in the first network based on the first indication information and the third indication information.

It should be noted that, when the terminal receives the failure notification about the first network, it can also send the failure notification about the first network to the application program of the terminal, or display the failure notification about the first network, so that the user can know the failure notification about the first network. The working status of the network.

It should be noted that the step for the terminal to update the network selection priority corresponding to the first network may be performed after step 202, or may be performed directly when the terminal fails to obtain normal services through the first network for a preset number of times. Not limited.

In the network failure processing method provided in the embodiment of the present application, when the terminal receives the failure notification about the first network, it sends the first message for instructing the access network device to communicate with the target network functional entity of the second network to the access network device. A request message facilitates the access network device to communicate with the target network function entity of the second network based on the first request message, so that the terminal can still obtain normal network services when the first network fails.

Optionally, the access network device includes an access network device shared by the first network and the second network, or includes an access network device corresponding to the first network that is not shared with the second network, or includes an access network device corresponding to the second network An access network device that is not shared with the first network.

For example, in the case that the access network equipment includes the access network equipment shared by the first network and the second network, when the terminal receives the fault notification for the first network, the first request message sent to the access network equipment Carry the first indication information used to indicate that the first network fails; or, the first request message carries the first indication information used to indicate the failure of the first network and the first indication information used to indicate the faulty network function entity in the first network The second indication information; or, the first request message carries the first indication information used to indicate that the first network has a fault and the third indication information used to indicate that a network function entity in the first network is not faulty.

It should be noted that, in the case that the access network equipment includes the access network equipment shared by the first network and the second network, the terminal may also report to the access network equipment without receiving the failure notification about the first network. sending the first request message, if the first request message does not indicate that the first network is faulty, the access network device, when detecting the first network fault or receiving a fault notification about the first network, communicates with the second network Target network functional entity communication.

In the case that the access network equipment includes the access network equipment corresponding to the first network and not shared with the second network, when the terminal receives a failure notification about the first network, the first request message sent to the access network equipment Carry the first indication information used to indicate that the first network fails; or, the first request message carries the first indication information used to indicate the failure of the first network and the first indication information used to indicate the faulty network function entity in the first network The second indication information; or, the first request message carries the first indication information used to indicate that the first network has a fault and the third indication information used to indicate that a network function entity in the first network is not faulty.

It should be noted that, in the case that the access network equipment includes the access network equipment corresponding to the first network that is not shared with the second network, the terminal may also try to pass through the When the first network fails to obtain normal network services for a preset number of times, it is considered that the first network has failed, and at this time, a first request message is sent to the access network device, and the first request message may carry information indicating that the first network has failed. The first indication of the .

In the case where the access network device includes an access network device corresponding to the second network that is not shared with the first network, when the terminal receives a failure notification for the first network, and updates the network selection priority corresponding to the first network, Make the network selection priority corresponding to the first network lower than the network selection priority corresponding to the second network Afterwards, the first request message sent to the access network device, the first request message carries the first indication information used to indicate that the first network has failed; or, the first request message carries the first indication information used to indicate that the first network has failed The first indication information of the fault and the second indication information used to indicate the faulty network functional entity in the first network; or, the first request message carries the first indication information used to indicate that the first network has failed and the second indication information used to indicate A third indication information of an unfaulted network functional entity in the network.

Fig. 4 is the third schematic flow diagram of the network failure processing method provided by the embodiment of the present application. As shown in Fig. 4, after step 201 is performed, the method further includes the following steps 203 and 204:

Step 203, the terminal receives a failure recovery notification about the first network.

For example, the terminal may receive a failure recovery notification of the first network sent by an unfaulted network functional entity in the first network, where the unfaulted network functional entity may be AMF, SMF, UPF, or LMF, etc.; The failure recovery notification of the first network sent by the access network device, which is not limited in this application.

Step 204, the terminal updates the network selection priority corresponding to the first network; the network selection priority corresponding to the first network is higher than the network selection priority corresponding to the second network, and/or, the network selection priority corresponding to the first network is restored is the network selection priority corresponding to the first network when no fault occurs.

For example, when the terminal receives a failure recovery notification for the first network, it can update the network selection priority corresponding to the first network. The specific update method can be to add the first network with lower network selection priority to the list Delete and restore the network selection priority corresponding to the first network, so that the network selection priority corresponding to the first network is higher than the network selection priority corresponding to the second network, and the network selection priority corresponding to the first network can also be restored to the first network selection priority A network selection priority corresponding to the network when no fault occurs.

In the network failure processing method provided by the embodiment of the present application, when the terminal receives the failure recovery notification about the first network, it can update the network selection priority corresponding to the first network, so that the network selection priority corresponding to the first network is higher than that of the first network. The network selection priority corresponding to the second network is convenient for the terminal to access the first network to obtain normal services and reduce the occupation of resources of the second network.

Optionally, FIG. 5 is a fourth schematic flow diagram of a network failure processing method provided in the embodiment of the present application. As shown in FIG. 5 , after performing step 201, the method further includes the following step 205:

Step 205, the terminal receives the response message sent by the access network device; the response message is based on the second It is determined by the processing result fed back by the target network functional entity in the network.

For example, the content of the response message is determined based on the specific service requested by the terminal; for example, when the service requested by the terminal is a registration service, the response message is the registration result; when the service requested by the terminal is a positioning service, the response message is a positioning service. result.

When the service requested by the terminal is a registration service, if the AMF of the first network fails, the terminal needs to access the AMF of the second network through the access network equipment, and the AMF is used to perform at least one of the following: Communication with the Authentication Server Function (AUSF) of the network; communication with the Unified Data Management (UDM) of the first network; communication with the Policy Control Function (PCF) of the first network; communication with the Policy Control Function (PCF) of the first network; SMF communication of the first network.

Among them, the communication with the AUSF of the first network is specifically: first select the AUSF function of the first network, then interact the AMF of the second network with the AUSF of the first network, and perform the authentication process; the communication with the UDM of the first network is specifically as follows : First select the UDM function of the first network, then interact the AMF of the second network with the UDM of the first network to perform the authentication process; communicate with the PCF of the first network specifically: first select the PCF function of the first network, and then set The AMF of the second network interacts with the PCF of the first network to obtain policy (policy) information; the communication with the SMF of the first network is specifically: first determine the SMF of the first network, and then connect the AMF of the second network with the first network The SMF interaction, the specific interaction is, for example, notifying the SMF of the first network of subsequent processing and signaling of the target terminal.

It should be noted that the above interaction may be the direct interaction between the AMF of the second network and the unfaulted network functional entity in the first network; it may also be forwarded by other network functional entities, for example, for the sake of network security, through a security agent to Forward.

It should be noted that, in other signaling processes other than the registration process, for example, during the establishment of a protocol data unit (Protocol Data Unit, PDU) session (SESSION), the AMF of the second network may select the SMF of the first network, Create, update or delete the PDU SESSION context in the SMF of the first network.

In the network failure processing method provided by the embodiment of the present application, when the first network functional entity of the first network fails, the terminal can receive the information sent by the access network device based on the second network. The response message determined by the processing result fed back by the target network functional entity ensures that the terminal can obtain normal network services when the first network functional entity of the first network fails.

Fig. 6 is the fifth schematic flow diagram of the method for processing a network failure provided in the embodiment of the present application. As shown in Fig. 6, the method includes the following steps:

Step 701: When it is determined that the first network functional entity of the first network fails, the access network device communicates with the target network functional entity of the second network; the target network functional entity of the second network communicates with the first network functional entity of the first network A network function entity has the same network function.

Wherein, the access network device may be an access network device shared by the first network and the second network, or an access network device corresponding to the first network that is not shared with the second network, or an access network device corresponding to the second network. Access network equipment that is not shared with the first network; the first network functional entity may be a faulty network functional entity such as AMF, SMF, or UPF, and when the first network functional entity is AMF, the target network functional entity is also AMF ; When the first network functional entity is an SMF, the target network functional entity is also an SMF.

For example, when the first network functional entity of the first network fails, the access network device communicates with the target network functional entity of the second network; through the target network functional entity of the second network, the terminal provides The network service of the same network function in the first network function entity.

In the network failure processing method provided by the embodiment of the present application, when the first network functional entity of the first network fails, the access network device communicates with the target network functional entity of the second network, and the target network of the second network The functional entity replaces the failed first network functional entity in the first network, so that the terminal can obtain normal network services.

Fig. 7 is the sixth schematic flow diagram of the method for processing network faults provided by the embodiment of the present application. As shown in Fig. 7, before performing step 701, the method further includes the following steps:

Step 702, the access network device receives the first request message sent by the terminal.

Wherein, the first request message is sent by the terminal when the first network function entity of the first network fails. The first request message is used to request registration to the second network, or the first request message is used to request to obtain service data.

Optionally, when the access network device receives the first request message sent by the terminal, the access The communication between the network device and the target network functional entity of the second network may be specifically implemented in the following manner:

The access network device communicates with the target network function entity of the second network based on the first request message.

For example, when the first network functional entity of the first network fails, the access network device receives the first request sent by the terminal for instructing the access network device to communicate with the target network functional entity of the second network When receiving a message, the access network device communicates with the target network function entity of the second network; the target network function entity of the second network provides the terminal with network services having the same network function as the first network function entity in the first network.

In the network failure processing method provided by the embodiment of the present application, when the first network functional entity of the first network fails, the terminal sends a first request message to the access network device, and the access network device sends the first request message based on the first request message and The target network functional entity of the second network communicates, and the target network functional entity of the second network replaces the failed first network functional entity in the first network, so that the terminal can obtain normal network services.

Optionally, the access network device may directly communicate with the target network function entity of the second network based on the first request message, or the access network device may communicate with the target network function entity of the second network through the unfaulted network function entity of the first network based on the first request message. The target network functional entities of the two networks communicate.

For example, FIG. 8 is one of the scene schematic diagrams of the network failure processing method provided by the embodiment of the present application. As shown in FIG. 8, the target network functional entity includes an AMF. The device directly communicates with the AMF of the second network based on the first request message; for another example, FIG. 9 is a second schematic diagram of the scene of the network fault handling method provided by the embodiment of the present application. As shown in FIG. 9 , the target network functional entity includes except A network function entity (Network Function, NF) other than the AMF, such as NF1, when NF1 fails and the AMF of the first network does not fail, the access network device passes the AMF of the first network based on the first request message Communicate with NF1 of the second network.

In the network fault handling method provided by the embodiment of the present application, the access network device can directly communicate with the target network functional entity of the second network, or communicate with the target network functional entity of the second network through the non-faulty network functional entity of the first network communication.

Optionally, the access network device includes an access network device shared by the first network and the second network.

In the case where the access network device includes the access network device shared by the first network and the second network, the communication between the access network device and the target network function entity of the second network based on the first request message can be specifically implemented in the following ways :

In the first manner, when the access network device detects a failure of the first network, the access network device communicates with the target network function entity of the second network based on the first request message.

For example, the first network and the second network share one access network device. When the access network device detects a failure of the first network, if it receives the first When the first request message indicates information, the access network device communicates with the target network function entity of the second network.

In the second way, when the access network device receives the fault notification about the first network, the access network device communicates with the target network function entity of the second network based on the first request message.

Wherein, the failure notification is carried by a non-access stratum NAS message or a radio resource control RRC message.

For example, the first network and the second network share one access network device. When the access network device receives a failure notification about the first network, if it receives a packet sent by the terminal to indicate that the first network has failed When receiving the first request message of the first indication information, the access network device communicates with the target network function entity of the second network.

In a third manner, the first request message carries a failure notification about the first network, and the access network device communicates with the target network function entity of the second network based on the failure notification about the first network.

Exemplarily, the first network and the second network share one access network device, and when the access network device receives the first request message carrying the fault notification about the first network, the access network device and the target network of the second network Functional entity communication.

In the network failure processing method provided in the embodiment of the present application, when the access network equipment includes the access network equipment shared by the first network and the second network, the access network equipment detects that the first network fails, or, After receiving a failure notification about the first network, or receiving a failure notification about the first network carried in the first request message sent by the terminal, it may communicate with the target network function entity of the second network, so that the terminal can obtain to normal web services.

Optionally, the access network device includes an access network device corresponding to the first network that is not shared with the second network or an access network device corresponding to the second network that is not shared with the first network.

In the case where the access network equipment includes access network equipment corresponding to the first network that is not shared with the second network or access network equipment corresponding to the second network that is not shared with the first network, the access network equipment and the second network The target network functional entity communication of the network can be realized in the following ways:

In the first way, the access network device communicates with the target network functional entity of the second network based on the configuration information; the configuration information is used to indicate to communicate with the target network functional entity of the second network when the first network fails.

For example, when the access network device does not receive the first request message sent by the terminal, when the access network device detects that the first network fails, it may Communication; for example, notification of terminal signaling or changes in data transmission paths, etc.

In the second manner, the access network device communicates with the target network function entity of the second network based on the received fault notification sent by the non-faulty network function entity in the first network.

For example, when the access network device does not receive the first request message sent by the terminal, when the access network device receives the fault notification sent by the non-faulty network functional entity in the first network, it communicates with the Target network functional entity communication.

In the network failure processing method provided in the embodiment of the present application, the access network device includes an access network device corresponding to the first network that is not shared with the second network, or includes an access network device corresponding to the second network that is not shared with the second network In the case of the access network device shared by the first network, the access network device may communicate with the target network functional entity of the second network based on the configuration information, or upon receiving a fault notification about the first network, This enables the terminal to obtain normal network services.

When the access network device includes an access network device corresponding to the first network that is not shared with the second network or an access network device corresponding to the second network that is not shared with the first network, accessing The communication between the network device and the target network function entity of the second network based on the first request message may be implemented in the following ways:

In the first way, the access network device is based on the first request message and configuration information and the second network's target The target network function entity communicates; the configuration information is used to indicate to communicate with the target network function entity of the second network when the first network fails.

For example, when the access network device receives the first request message sent by the terminal, the access network device may communicate with the target network function entity of the second network based on the first request message and the configuration information.

In the second way, the access network device communicates with the target network function entity of the second network based on the first request message and the received fault notification sent by the unfaulted network function entity in the first network.

For example, when the access network device receives the first request message sent by the terminal, the access network device may, based on the first request message and communicating with the target network function entity of the second network with the received fault notification sent by the non-faulty network function entity in the first network.

In a third way, the first request message carries a failure notification about the first network; the access network device communicates with the target network function entity of the second network based on the failure notification about the first network.

For example, when the access network device receives the first request message sent by the terminal, if the first request message carries a fault notification about the first network, the access network device, based on the fault notification about the first network, Communicating with a target network functional entity of the second network.

In the network failure processing method provided in the embodiment of the present application, the access network device includes an access network device corresponding to the first network that is not shared with the second network, or includes an access network device corresponding to the second network that is not shared with the second network In the case of the access network device shared by the first network, the access network device may be based on the configuration information and the first request message, or based on receiving a fault notification about the first network and the first request message, or based on receiving The received first request message sent by the terminal communicates with the target network function entity of the second network, so that the terminal can obtain normal network services.

Optionally, the failure notification includes at least one of the following: first indication information used to indicate that a failure occurs in the first network; second indication information used to indicate a failed network function entity in the first network; The third indication information of a non-faulty network function entity, where the faulty network function entity includes the first network function entity, and the non-faulty network function entity does not include the first network function entity.

Optionally, the first request message includes at least one of the following items: first indication information used to indicate that the first network fails; second indication information used to indicate a faulty network function entity in the first network; Third indication information of a non-faulty network function entity in the network, the faulty network function entity includes the first network function entity, and the non-faulty network function entity does not include the first network function entity.

Optionally, FIG. 10 is a seventh schematic flow diagram of a network failure processing method provided in the embodiment of the present application. As shown in FIG. 10 , after step 701 is performed, the method further includes the following steps:

Step 703, the access network device receives a response message sent by the target network function entity in the second network; the response message is determined based on the processing result fed back by the target network function entity in the second network.

Step 704, the access network device sends a response message to the terminal.

For example, when the target network function entity in the second network obtains the response message, it may send the response message to the access network device, and the access network device sends the response message to the terminal, so that the terminal obtains normal services; the response message The content is determined based on the specific service requested by the terminal; for example, when the service requested by the terminal is a registration service, the response message is the registration result; when the service requested by the terminal is a positioning service, the response message is the positioning result.

When the service requested by the terminal is a registration service, if the AMF of the first network fails, the terminal needs to access the AMF of the second network through the access network equipment, and the AMF is used to perform at least one of the following: Communication with AUSF of the network; communication with UDM of the first network; communication with PCF of the first network; communication with SMF of the first network.

In the network failure processing method provided in the embodiment of the present application, when the first network functional entity of the first network fails, the access network device can send the processing result based on the feedback of the target network functional entity in the second network to the terminal A certain response message, so as to ensure that the terminal can obtain normal network services when the first network functional entity of the first network fails.

Optionally, the communication between the access network device and the target network function entity of the second network based on the first request message may be implemented in the following manner:

The access network device obtains the second request message based on the first request message; the access network device sends the core network The device sends a second request message; the second request message is used to indicate communication with the target network function entity of the second network.

For example, when receiving the first request message sent by the terminal, the access network device may obtain a second request message sent to the core network device based on the first request message, where the second request message is used to indicate the connection with the second network Target network functional entity communication.

Optionally, the method also includes the following steps:

The access network device sends a failure recovery notification about the first network to the terminal.

For example, when the access network device detects the failure recovery of the first network or receives the failure recovery notification about the first network, it sends the failure recovery notification about the first network to the terminal, so that the terminal accesses the first network.

In the network failure processing method provided in the embodiment of the present application, when the access network device detects the failure recovery of the first network or receives a failure recovery notification about the first network, it sends a failure recovery notification about the first network to the terminal, It is convenient for the terminal to update the network selection priority corresponding to the first network when receiving the failure recovery notification about the first network, and subsequently the terminal obtains normal network services through the first network, reducing the occupation of resources of the second network.

Fig. 11 is the eighth schematic flow diagram of the method for processing network faults provided by the embodiment of the present application. As shown in Fig. 11, the method includes the following steps:

Step 1201, the core network device receives the second request message sent by the access network device.

Wherein, the second request message is sent by the access network device when it is determined that the first network function entity of the first network fails.

Step 1202, in the case that the core network device is an unfaulted network functional entity in the first network, the core network device communicates with the second network functional entity of the second network; the second network functional entity communicates with the first network functional entity of the first network Entities have the same network capabilities.

As an example, in the case that the core network device is a non-failure network functional entity in the first network, it is explained that the access network device can communicate with the non-failure network function entity in the first network, and then the non-failure network function entity in the first network can The entity communicates with a second network function entity in the second network.

It should be noted that this application does not limit the number of second network functional entities of the second network, Which second network functional entities in the second network the core network device specifically communicates with needs to be determined based on the service requested by the terminal.

Step 1203, if the core network device is the target network functional entity in the second network, the core network device communicates with the unfaulted network functional entity in the first network, or, the core network device communicates with the third network functional entity in the second network Communication; the third network function entity has the same network function as the non-faulty network function entity in the first network.

For example, in the case that the core network device is the target network functional entity in the second network, it means that the access network device cannot communicate with the faulty network functional entity in the first network, and the access network device needs to directly communicate with the target network functional entity in the second network. The network function entity communicates, and then the target network function entity in the second network communicates with the third network function entity in the second network, or communicates with the unfaulted network function entity in the first network.

It should be noted that this application does not limit the number of third network functional entities in the second network or the number of non-faulty network functional entities in the first network, and it needs to be determined based on the service requested by the terminal. Which third network functional entities in the first network communicate with, or communicate with which non-faulty network functional entities in the first network.

In the network failure processing method provided by the embodiment of the present application, when the first network functional entity of the first network fails, the target network functional entity of the second network replaces the failed first network functional entity of the first network , so that the terminal can obtain normal network services; in addition, when the first network functional entity of the first network fails, since only the target network functional entity in the second network assists the first network in providing services, the second network The impact of other network functional entities in the network is small; and in the case that the core network device is the target network functional entity in the second network, the core network device can communicate with the unfaulted network functional entity in the first network, making full use of the first The resources of the non-faulty network functional entities in the network avoid the waste of network resources.

Optionally, the method also includes the following steps:

In the case that the core network device is the target network functional entity in the second network, the core network device receives the fault notification sent by the non-faulty network functional entity in the first network.

The failure notification includes at least one of the following: a first indication message used to indicate that the first network has failed information; second indication information used to indicate a faulty network function entity in the first network; third indication information used to indicate a non-faulty network function entity in the first network, and the faulty network function entity includes the first network function entity, the non-faulty network function entity does not include the first network function entity.

In the network fault processing method provided by the embodiment of the present application, when the core network device is the target network functional entity in the second network, the core network device can receive the fault notification sent by the unfailed network functional entity in the first network, which is convenient for the core The network device determines the unfaulted network functional entity in the first network based on the fault notification, and communicates with the unfaulted network functional entity in the first network.

Optionally, the access network device includes an access network device shared by the first network and the second network, or the access network device includes an access network device corresponding to the first network that is not shared with the second network, or the access network device The device includes an access network device corresponding to the second network that is not shared with the first network.

In addition, when the service requested by the terminal is a registration service, if the AMF of the first network fails, the terminal needs to access the AMF of the second network through the access network equipment, and the AMF is used to perform at least one of the following: The AUSF of the first network communicates; communicates with the UDM of the first network; communicates with the PCF of the first network; communicates with the SMF of the first network.

Figure 12 is the third schematic diagram of the scene of the network failure processing method provided by the embodiment of the present application, which is applied to terminals, access network equipment and core network equipment. The first network is represented by PLMN D, and the second network is represented by PLMN A. PLMN The AMF of D breaks down, and the access network equipment includes the access network equipment corresponding to the first network that is not shared with the second network, such as base station 1; the core network equipment includes the AMF in PLMN A; correspondingly, Fig. 13 is the implementation of the present application One of the interactive diagrams of the processing method for the network failure provided by the example, as shown in Figure 13, the method includes the following steps:

Step 1401, when the AMF of PLMND D fails, the terminal receives a failure notification about PLMND D.

Wherein, the fault notification includes at least one of the following: first indication information used to indicate that PLMN D has failed; second indication information used to indicate a faulty AMF in PLMN D; The third indication information of the non-faulty network functional entity in D.

Step 1402, the terminal sends a first request message to base station 1.

Wherein, the first request message is used to indicate that base station 1 communicates with the AMF of PLMN A; the first request message includes at least one of the following items: the first indication information used to indicate that PLMN D fails; used to indicate the failure AMF in PLMN D The second indication information; the third indication information used to indicate the non-faulty network function entity in the PLMND.

Step 1403, base station 1 communicates with the AMF of PLMN A based on the first request message.

Step 1404, the AMF of PLMN A communicates with other network functional entities of PLMN A, or, the AMF of PLMN A communicates with the unfaulted network functional entities of PLMN D, and obtains a response message.

Exemplarily, other network function entities of PLMN A have the same network function as the non-failure network function entities in PLMN D, as shown in Figure 12, other network function entities may include NF1 and NF2; correspondingly, the non-failure network function entities in PLMN D Entities may also include NF1 and NF2, wherein, the communication between the AMF of PLMN A and the NF1 and NF2 of PLMN A is represented by a dotted line, and the communication between the AMF of PLMN A and the NF1 and NF2 of PLMN D is represented by a solid line.

It should be noted that based on the different services requested by the terminal, other network functional entities in PLMN A that communicate with the AMF of PLMN A or the non-faulty network functional entities in PLMN D are also different, and the AMF with PLMN D can be selected based on actual needs. The non-faulty network functional entity in the communicating PLMN A or the non-faulty network functional entity in the PLMN D is not limited in this application.

Step 1405, the AMF of PLMN A sends the response message to base station 1.

Step 1406, base station 1 sends a response message to the terminal.

In the network failure processing method provided by the embodiment of the present application, when the AMF of PLMN D fails, the terminal sends to the base station 1 corresponding to PLMN D a first request message for instructing base station 1 to communicate with the AMF of PLMN A, and the The AMF of PLMN A replaces the failed AMF of PLMN D, so that the terminal can obtain normal network services. In addition, since only the AMF in PLMN A assists PLMN D in providing services, it has little impact on other network functional entities in PLMN A; and when the core network device is the AMF in PLMN A, the core network device can communicate with PLMN D The non-faulty network function entity communication in the medium, fully utilizes the non-faulty network in the PLMN D resources of functional entities, avoiding the waste of network resources.

Figure 14 is the fourth schematic diagram of the scene of the network failure processing method provided by the embodiment of the present application, which is applied to terminals, access network equipment and core network equipment. The first network is represented by PLMN D, and the second network is represented by PLMN A. PLMN NF1 of D fails, and the access network equipment includes the access network equipment corresponding to the first network that is not shared with the second network, such as base station 1; the core network equipment includes the unfailed network functional entity in PLMN D, such as the network functional entity AMF Correspondingly, FIG. 15 is the second interaction diagram of the method for handling network faults provided by the embodiment of the present application. As shown in FIG. 15 , the method includes the following steps:

Step 1601. When NF1 of PLMND fails, the terminal receives a failure notification about PLMND.

Wherein, the failure notification includes at least one of the following: first indication information used to indicate failure of PLMN D; second indication information used to indicate failure NF1 in PLMN D; 3. Instructions.

Step 1602, the terminal sends a first request message to base station 1.

Wherein, the first request message is used to indicate that the base station 1 communicates with the NF1 of the PLMN A; the first request message includes at least one of the following items: the first indication information used to indicate the failure of the PLMN D; used to indicate the fault NF1 in the PLMN D The second indication information; the third indication information used to indicate the non-faulty network function entity in the PLMND.

Step 1603, base station 1 communicates with the AMF of PLMND D based on the first request message.

Step 1604, AMF of PLMN D communicates with NF1 of PLMN A, and obtains a response message.

It should be noted that based on the different services requested by the terminal, the non-faulty network function entities in PLMN A communicating with the AMF of PLMN D are also different. Specifically, the non-faulty network function entities in PLMN A communicating with the AMF of PLMN D can be selected based on actual needs. The network function entity is not limited in this application.

Step 1605, the AMF of PLMND D sends the response message to base station 1.

Step 1606, base station 1 sends a response message to the terminal.

According to the network failure processing method provided in the embodiment of this application, a failure occurs in NF1 of PLMN D In the case of , the terminal sends a first request message to base station 1 corresponding to PLMN D to instruct base station 1 to communicate with NF1 of PLMN A, base station 1 communicates with AMF of PLMN D based on the first request message, and AMF of PLMN D communicates with PLMN A The NF1 of A communicates; the NF1 of PLMN A replaces the failed NF1 of PLMN D, so that the terminal can obtain normal network services. In addition, since only NF1 in PLMN A assists PLMN D in providing services, it has little impact on other network functional entities in PLMN A.

Figure 16 is the fifth schematic diagram of the scene of the network failure processing method provided by the embodiment of the present application, which is applied to terminals, access network equipment and core network equipment. The first network is represented by PLMN D, and the second network is represented by PLMN A. PLMN The AMF of D fails, and the access network equipment includes the access network equipment corresponding to the second network that is not shared with the first network, such as base station 2; the core network equipment includes the AMF in PLMN A, correspondingly, Figure 17 is the implementation of the present application The third interaction diagram of the network failure processing method provided by the example, as shown in Figure 17, the method includes the following steps:

Step 1801, when the AMF of PLMND D fails, the terminal receives a failure notification about PLMND D.

Wherein, the fault notification includes at least one of the following: first indication information used to indicate that PLMN D has failed; second indication information used to indicate a faulty AMF in PLMN D; second indication information used to indicate an unfaulted network function entity in PLMN D 3. Instructions.

Step 1802, the terminal updates the network selection priority corresponding to the PLMND.

Wherein, the network selection priority corresponding to PLMN D is lower than the network selection priority corresponding to PLMN A, and/or, the network selection priority corresponding to PLMN D is lower than the network selection priority corresponding to PLMN D when no failure occurs.

Step 1803, the terminal sends a first request message to the base station 2.

Wherein, the first request message is used to indicate that the base station 2 communicates with the AMF of the PLMN A; the first request message includes at least one of the following items: the first indication information used to indicate that the PLMN D fails; used to indicate the failure AMF in the PLMN D The second indication information; the third indication information used to indicate the non-faulty network function entity in the PLMND.

Step 1804, base station 2 communicates with the AMF of PLMN A based on the first request message.

Step 1805, the AMF of PLMN A communicates with other network functional entities of PLMN A, or, the AMF of PLMN A communicates with the unfaulted network functional entities of PLMN D, and obtains a response message.

Exemplarily, other network function entities of PLMN A have the same network function as the non-failure network function entities in PLMN D, as shown in Figure 16, other network function entities may include NF1 and NF2; correspondingly, the non-failure network function entities in PLMN D Entities may also include NF1 and NF2; wherein, the communication between the AMF of PLMN A and the NF1 and NF2 of PLMN A is represented by a dotted line, and the communication between the AMF of PLMN A and the NF1 and NF2 of PLMN D is represented by a solid line.

Step 1806, the AMF of PLMN A sends the response message to base station 2.

Step 1807, base station 2 sends a response message to the terminal.

In the network failure processing method provided by the embodiment of the present application, when the AMF of PLMN D fails, the terminal lowers the network selection priority corresponding to PLMN D, and sends a message to the base station 2 corresponding to PLMN A to indicate that base station 2 and PLMN A The first request message of the AMF communication of PLMN A replaces the failed AMF in PLMN D by the AMF of PLMN A, so that the terminal can obtain normal network services. In addition, since only the AMF in PLMN A assists PLMN D in providing services, it has little impact on other network functional entities in PLMN A; and when the core network device is the AMF in PLMN A, the core network device can communicate with PLMN D The communication between non-faulty network functional entities in PLMND fully utilizes the resources of non-faulty network functional entities in PLMND to avoid the waste of network resources.

Figure 18 is the sixth schematic diagram of the scene of the network failure processing method provided by the embodiment of the present application, which is applied to terminals, access network equipment and core network equipment. The first network is represented by PLMN D, and the second network is represented by PLMN A. PLMN NF1 of D fails, and the access network equipment includes the access network equipment corresponding to the second network that is not shared with the first network, such as base station 2; the core network equipment includes the unfailed network functional entity in PLMN D, such as the network functional entity AMF , correspondingly, FIG. 19 is the fourth interaction diagram of the network failure processing method provided by the embodiment of the present application. As shown in FIG. 19 , the method includes Include the following steps:

Step 2001, when NF1 of PLMND fails, the terminal receives a failure notification about PLMND.

Step 2002, the terminal updates the network selection priority corresponding to the PLMND.

Step 2003, the terminal sends a first request message to the base station 2.

Wherein, the first request message is used to indicate that the base station 2 communicates with the NF1 of the PLMN A; the first request message includes at least one of the following items: the first indication information used to indicate the failure of the PLMN D; used to indicate the fault NF1 in the PLMN D The second indication information; the third indication information used to indicate the non-faulty network function entity in the PLMND.

Step 2004, base station 2 communicates with the AMF of PLMND D based on the first request message.

Step 2005, AMF of PLMN D communicates with NF1 of PLMN A, and obtains a response message.

Step 2006, AMF of PLMND D sends a response message to base station 2.

Step 2007, base station 2 sends a response message to the terminal.

According to the network failure processing method provided by the embodiment of the present application, when NF1 of PLMN D fails, the terminal lowers the network selection priority corresponding to PLMN D, and sends a message to base station 2 corresponding to PLMN A to indicate that base station 2 and PLMN The first request message communicated by NF1 of A, base station 2 communicates with the AMF of PLMN D based on the first request message, and the AMF of PLMN D communicates with NF1 of PLMN A Communication: The NF1 of PLMN A replaces the failed NF1 of PLMN D, so that the terminal can obtain normal network services. In addition, since only NF1 in PLMN A assists PLMN D in providing services, it has little impact on other network functional entities in PLMN A.

Figure 20 is the seventh schematic diagram of the scene of the network failure processing method provided by the embodiment of the present application, which is applied to terminals, access network equipment and core network equipment. The first network is represented by PLMN D, and the second network is represented by PLMN A. PLMN The AMF of D fails, and the access network equipment includes the access network equipment shared by the first network and the second network, such as a shared base station; the core network equipment includes the AMF in PLMN A, and correspondingly, Figure 21 is provided by the embodiment of the present application The fifth interaction diagram of the method for handling network faults, as shown in Figure 21, the method includes the following steps:

Step 2201, when the AMF of PLMND D fails, the terminal receives a failure notification about PLMND D.

Step 2202, the terminal sends a first request message to the shared base station.

Wherein, the first request message is used to indicate that the shared base station communicates with the AMF of PLMN A; the first request message includes at least one of the following items: the first indication information used to indicate the failure of PLMN D; used to indicate the failure AMF in PLMN D The second indication information; the third indication information used to indicate the non-faulty network function entity in the PLMND.

It should be noted that, before performing step 2202, the terminal may also update the network selection priority corresponding to PLMN D, so that the network selection priority corresponding to PLMN D is lower than the network selection priority corresponding to PLMN A, and/or, PLMN D The corresponding network selection priority is lower than the corresponding network selection priority of PLMND when no fault occurs.

Step 2203, the shared base station communicates with the AMF of PLMN A based on the first request message.

It should be noted that, when the terminal updates the network selection priority corresponding to PLMN D, the first request message sent by the terminal to the shared base station carries a failure notice about PLMN D, so that the shared base station can communicate with the PLMN D based on the failure notice about PLMN D. AMF communication of PLMN A.

Step 2204, the AMF of PLMN A communicates with other network functional entities of PLMN A, or, the AMF of PLMN A communicates with the unfaulted network functional entities of PLMN D, and obtains a response message.

Exemplarily, other network function entities of PLMN A have the same network functions as the non-failure network function entities in PLMN D, as shown in Figure 20, other network function entities may include NF1 and NF2; correspondingly, the non-failure network function entities in PLMN D Entities may also include NF1 and NF2.

It should be noted that based on the different services requested by the terminal, other network functional entities in PLMN A that communicate with the AMF of PLMN A or the non-faulty network functional entities in PLMN D are also different, and the AMF with PLMN D can be selected based on actual needs. The non-failure network function entity in the communicating PLMN A or the non-failure network function entity in the PLMN D is not limited in this application.

Step 2205, AMF of PLMN A sends a response message to the shared base station.

Step 2206, the shared base station sends a response message to the terminal.

In the method for processing a network failure provided in the embodiment of the present application, when the AMF of PLMN D fails, the terminal sends a first request message for instructing the shared base station to communicate with the AMF of PLMN A to the shared base station of PLMN D and PLMN A , the failed AMF in PLMN D is replaced by the AMF of PLMN A, so that the terminal can obtain normal network services. In addition, since only the AMF in PLMN A assists PLMN D in providing services, it has little impact on other network functional entities in PLMN A; and when the core network device is the AMF in PLMN A, the core network device can communicate with PLMN D The communication between non-faulty network functional entities in PLMND fully utilizes the resources of non-faulty network functional entities in PLMND to avoid the waste of network resources.

Figure 22 is the eighth schematic diagram of the network failure processing method provided by the embodiment of the present application, which is applied to terminals, access network equipment, and core network equipment. The first network is represented by PLMN D, and the second network is represented by PLMN A. PLMN NF1 of D fails, and the access network equipment includes the access network equipment corresponding to the first network that is not shared with the second network, such as a shared base station; the core network equipment includes the unfailed network functional entity in PLMN D, such as the network functional entity AMF Correspondingly, FIG. 23 is the sixth interaction diagram of the network failure processing method provided by the embodiment of the present application. As shown in FIG. 23, the method includes the following steps:

Step 2401, when NF1 of PLMN D fails, the terminal receives information about PLMN D's failure notification.

Step 2402, the terminal sends a first request message to the shared base station.

Wherein, the first request message is used to indicate that the shared base station communicates with the NF1 of PLMN A; the first request message includes at least one of the following items: the first indication information used to indicate the failure of PLMN D; used to indicate the failure of NF1 in PLMN D The second indication information; the third indication information used to indicate the non-faulty network function entity in the PLMND.

It should be noted that, before performing step 2402, the terminal may also update the network selection priority corresponding to PLMN D, so that the network selection priority corresponding to PLMN D is lower than the network selection priority corresponding to PLMN A, and/or, PLMN D The corresponding network selection priority is lower than the corresponding network selection priority of PLMND when no fault occurs.

Step 2403, the shared base station communicates with the AMF of the PLMND based on the first request message.

It should be noted that, when the terminal updates the network selection priority corresponding to the PLMND, the first request message sent by the terminal to the shared base station carries a failure notification about the PLMND, so that the shared base station can communicate with the PLMND based on the failure notification about the PLMND. AMF communication of PLMN A.

Step 2404, AMF of PLMN D communicates with NF1 of PLMN A, and obtains a response message.

Step 2405, the AMF of PLMND D sends the response message to the shared base station.

Step 2406, the shared base station sends a response message to the terminal.

In the network failure processing method provided by the embodiment of the present application, when NF1 of PLMN D fails, the shared base station of terminal PLMN D and PLMN A sends a first request message for instructing the shared base station to communicate with NF1 of PLMN A, The shared base station communicates with the PLMN based on the first request message The AMF of D communicates, and the AMF of PLMN D communicates with the NF1 of PLMN A; the NF1 of PLMN A replaces the failed NF1 of PLMN D, so that the terminal can obtain normal network services. In addition, since only NF1 in PLMN A assists PLMN D in providing services, it has little impact on other network functional entities in PLMN A.

The method for processing a network fault provided in the embodiment of the present application may be executed by a device for processing a network fault. In the embodiment of the present application, the method for processing a network fault performed by the device for processing a network fault is taken as an example to describe the device for processing a network fault provided in the embodiment of the present application.

Fig. 24 is one of the schematic structural diagrams of the network fault processing device provided by the embodiment of the present application. As shown in Fig. 24, the network fault processing device 2500 is applied to the terminal and includes: a first update module 2501 and/or a first sending module;

When it is determined that the first network functional entity of the first network fails, the first update module 2501 is configured to update the network selection priority corresponding to the first network; the network selection priority corresponding to the first network is lower than the network selection priority corresponding to the second network, and/or, the network selection priority corresponding to the first network is lower than the network selection priority corresponding to the first network when no failure occurs;

In the network failure processing device provided in the embodiment of the present application, when it is determined that the first network functional entity of the first network fails, the terminal updates the network selection priority corresponding to the first network, and/or, the terminal reports to the access network The device sends a first request message for instructing the access network device to communicate with the target network function entity of the second network, and the target network function entity of the second network replaces the failed first network function entity in the first network, so that the terminal Able to obtain normal network services.

Optionally, the device 2500 for processing network faults further includes:

The second receiving module is configured to receive a fault notification about the first network, and determine that a fault occurs in the first network functional entity of the first network;

The fault notification includes at least one of the following: a first Indication information; second indication information used to indicate a faulty network function entity in the first network; third indication information used to indicate a non-failure network function entity in the first network, and the faulty network function entity includes For the first network function entity, the non-faulty network function entity does not include the first network function entity.

Optionally, the first request message includes at least one of the following: first indication information used to indicate that a fault occurs in the first network; second indication information used to indicate a faulty network function entity in the first network information; third indication information used to indicate a non-failure network function entity in the first network, the faulty network function entity includes the first network function entity, and the non-failure network function entity does not include the first network function entity Network Functional Entity.

Optionally, the access network device includes an access network device shared by the first network and the second network, or includes an access network corresponding to the first network that is not shared with the second network network equipment, or include access network equipment corresponding to the second network that is not shared with the first network.

Optionally, the device 2500 for processing network faults further includes:

A third receiving module, configured to receive a fault recovery notification about the first network;

The second update module is configured to update the network selection priority corresponding to the first network; the network selection priority corresponding to the first network is higher than the network selection priority corresponding to the second network, and/or, the The network selection priority corresponding to the first network is restored to the network selection priority corresponding to the first network when no failure occurs.

Optionally, the device 2500 for processing network faults further includes:

The fourth receiving module is configured to receive a response message sent by the access network device; the response message is determined based on a processing result fed back by the target network function entity in the second network.

Optionally, the failure notification is carried by a non-access stratum NAS message or a radio resource control RRC message.

Fig. 25 is the second structural schematic diagram of the network fault processing device provided by the embodiment of the present application. As shown in Fig. 25, the network fault processing device 2600 is applied to access network equipment, including:

The first communication module 2601 is configured to communicate with the target network function entity of the second network when it is determined that the first network function entity of the first network fails; the target network function entity of the second network communicates with the first network function entity The first network function entities in a network have the same network function.

In the network failure processing device provided in the embodiment of the present application, when the first network functional entity of the first network fails, the access network device communicates with the target network functional entity of the second network, and the target network of the second network The functional entity replaces the failed first network functional entity in the first network, so that the terminal can obtain normal network services.

Optionally, the device 2600 for processing network faults further includes:

The fifth receiving module 2602 is configured to receive a first request message sent by the terminal; the first request message is sent by the terminal when the first network functional entity of the first network fails;

The first communication module 2601 is specifically used for:

communicating with a target network function entity of the second network based on the first request message.

Optionally, the first communication module 2601 is specifically configured to:

communicating with the target network function entity of the second network via the surviving network function entity of the first network based on the first request message.

Optionally, the access network device includes an access network device shared by the first network and the second network; the first communication module 2601 is specifically configured to:

communicating with a target network function entity of the second network based on the first request message in a case where the access network device detects a failure of the first network;

Or, in a case where the access network device receives a fault notification about the first network, communicate with a target network function entity of the second network based on the first request message; or,

The first request message carries a fault notification about the first network;

Communicating with a target network function entity of the second network based on the failure notification regarding the first network.

Optionally, the access network device includes an access network device corresponding to the first network that is not shared with the second network or an access network device corresponding to the second network that is not shared with the first network network equipment; the first communication module 2601 is specifically used for:

communicating with a target network functional entity of the second network based on configuration information; the configuration information is used to indicate communication with a target network functional entity of the second network when a failure occurs in the first network; or,

Communicating with the target network function entity of the second network based on the received fault notification sent by the non-faulty network function entity in the first network.

Optionally, the access network device includes an access network device corresponding to the first network that is not shared with the second network, or includes an interface corresponding to the second network that is not shared with the first network A network access device; the first communication module 2601 is specifically used for:

communicating with a target network function entity of the second network based on the first request message, comprising:

communicating with a target network functional entity of the second network based on the first request message and configuration information; the configuration information is used to indicate to communicate with the target network functional entity of the second network when a failure occurs in the first network; or,

communicating with a target network function entity of the second network based on the first request message and the received failure notification sent by the non-faulty network function entity in the first network; or,

The first request message carries a fault notification about the first network;

Optionally, the failure notification includes at least one of the following: first indication information used to indicate that a failure occurs in the first network; second indication information used to indicate a failed network functional entity in the first network; In the third indication information indicating a non-faulty network function entity in the first network, the faulty network function entity includes the first network function entity, and the non-faulty network function entity does not include the first network function entity .

Optionally, the device 2600 for processing network faults further includes:

The sixth receiving module is configured to receive a response message sent by the target network functional entity in the second network; the response message is determined based on a processing result fed back by the target network functional entity in the second network;

The second sending module is configured to send the response message to the terminal.

Optionally, the first communication module 2601 is specifically configured to:

Obtaining a second request message based on the first request message, and sending the second request message to the core network device; the second request message is used to indicate communication with a target network function entity of the second network.

Optionally, the device 2600 for processing network faults further includes:

A third sending module, configured to send a failure recovery notification about the first network to the terminal.

Fig. 26 is the third schematic structural diagram of the network fault processing device provided by the embodiment of the present application. As shown in Fig. 26, the network fault processing device 2700 is applied to core network equipment, including:

The first receiving module 2701 is configured to receive a second request message sent by the access network device; the second request message is sent by the access network device when it is determined that the first network functional entity of the first network fails of;

The second communication module 2702 is configured to communicate with a second network function entity of the second network when the core network device is a non-faulty network function entity in the first network; the second network function entity communicates with the second network function entity The first network function entities of the first network have the same network function;

The third communication module 2703 is configured to communicate with an unfaulted network functional entity in the first network when the core network device is a target network functional entity in the second network, or the core network device Communicating with a third network function entity in the second network; the third network function entity has the same network function as the unfaulted network function entity in the first network.

The device for processing network faults provided in this application is sent by the first network function entity of the first network to In the event of a failure, the target network functional entity of the second network replaces the failed first network functional entity in the first network, so that the terminal can obtain normal network services; in addition, the first network functional entity of the first network In the event of a failure, since only the target network functional entity in the second network assists the first network in providing services, the impact on other network functional entities in the second network is small; and the core network device is the target network function entity in the second network In the case of a network functional entity, the core network device can communicate with the non-faulty network functional entity in the first network, fully using the resources of the non-faulty network functional entity in the first network, and avoiding waste of network resources.

Optionally, the device 2700 for processing network faults further includes:

A seventh receiving module, configured to receive a fault notification sent by an unfaulted network functional entity in the first network when the core network device is a target network functional entity in the second network;

The fault notification includes at least one of the following: first indication information for indicating that a fault occurs in the first network; second indication information for indicating a faulty network function entity in the first network; The third indication information of a non-failure network function entity in the first network, the faulty network function entity includes the first network function entity, and the non-failure network function entity does not include the first network function entity.

The apparatus for processing a network fault in the embodiment of the present application may be an electronic device, such as an electronic device with an operating system, or a component in the electronic device, such as an integrated circuit or a chip. The electronic device may be a terminal, or other devices other than the terminal. Exemplarily, the terminal may include, but not limited to, the types of terminal 11 listed above, and other devices may be servers, Network Attached Storage (NAS), etc., which are not specifically limited in this embodiment of the present application.

The device for processing network faults provided by the embodiments of the present application can implement the various processes implemented by the method embodiments in FIG. 2 to FIG. 23 and achieve the same technical effect. To avoid repetition, details are not repeated here.

Optionally, as shown in FIG. 27 , this embodiment of the present application further provides a communication device 2800, including a processor 2801 and a memory 2802. The memory 2802 stores The running program or instruction, for example, when the communication device 2800 is a terminal, when the program or instruction is executed by the processor 2801, implements the various steps in the above embodiment of the method for handling network faults, and can achieve the same technical effect. When the communication device 2800 is a network-side device, when the program or instruction is executed by the processor 2801, the steps of the above-mentioned network fault processing method embodiment can be achieved, and the same technical effect can be achieved. To avoid repetition, details are not repeated here.

The embodiment of the present application also provides a terminal, including a processor and a communication interface, wherein:

When it is determined that the first network functional entity of the first network fails, the processor is configured to update the network selection priority corresponding to the first network; the network selection priority corresponding to the first network is lower than that corresponding to the second network network selection priority, and/or, the network selection priority corresponding to the first network is lower than the network selection priority corresponding to the first network when no failure occurs; the communication interface is used to send to the access network device A first request message; the first request message is used to instruct the access network device to communicate with the target network function entity of the second network; the target network function entity of the second network communicates with the first network function entity in the first network A network function entity has the same network function.

This terminal embodiment corresponds to the above-mentioned terminal-side method embodiment, and each implementation process and implementation mode of the above-mentioned method embodiment can be applied to this terminal embodiment, and can achieve the same technical effect. Specifically, FIG. 28 is a schematic diagram of a hardware structure of a terminal implementing an embodiment of the present application.

The terminal 2900 includes, but is not limited to: a radio frequency unit 2901, a network module 2902, an audio output unit 2903, an input unit 2904, a sensor 2905, a display unit 2906, a user input unit 2907, an interface unit 2908, a memory 2909, and a processor 2910. At least some parts.

Those skilled in the art can understand that the terminal 2900 may also include a power supply (such as a battery) for supplying power to various components, and the power supply may be logically connected to the processor 2910 through the power management system, so as to manage charging, discharging, and power consumption through the power management system. Management and other functions. The terminal structure shown in FIG. 28 does not constitute a limitation on the terminal. The terminal may include more or fewer components than shown in the figure, or combine some components, or arrange different components, which will not be repeated here.

It should be understood that, in this embodiment of the present application, the input unit 2904 may include a graphics processing unit (Graphics Processing Unit, GPU) 29041 and a microphone 29042, and the graphics processor 29041 is used in the video capture mode or image capture mode by the image capture device ( such as a camera) obtained static The image data of the dynamic picture or video is processed. The display unit 2906 may include a display panel 29061, and the display panel 29061 may be configured in the form of a liquid crystal display, an organic light emitting diode, or the like. The user input unit 2907 includes at least one of a touch panel 29071 and other input devices 29072 . Touch panel 29071, also called touch screen. The touch panel 29071 can include two parts: a touch detection device and a touch controller. Other input devices 29072 may include, but are not limited to, physical keyboards, function keys (such as volume control buttons, switch buttons, etc.), trackballs, mice, and joysticks, which will not be repeated here.

In the embodiment of the present application, the radio frequency unit 2901 may transmit the downlink data from the network side device to the processor 2910 for processing after receiving it; in addition, the radio frequency unit 2901 may send uplink data to the network side device. Generally, the radio frequency unit 2901 includes, but is not limited to, an antenna, an amplifier, a transceiver, a coupler, a low noise amplifier, a duplexer, and the like.

The memory 2909 can be used to store software programs or instructions as well as various data. The memory 2909 may mainly include a first storage area for storing programs or instructions and a second storage area for storing data, wherein the first storage area may store an operating system, an application program or instructions required by at least one function (such as a sound playing function, image playback function, etc.), etc. Furthermore, memory 2909 may include volatile memory or nonvolatile memory, or, memory 2909 may include both volatile and nonvolatile memory. Wherein, the non-volatile memory may be a read-only memory (Read-Only Memory, ROM), a programmable read-only memory (Programmable ROM, PROM), an erasable programmable read-only memory (Erasable PROM, EPROM), an electronically programmable Erase Programmable Read-Only Memory (Electrically EPROM, EEPROM) or Flash. Volatile memory can be random access memory (Random Access Memory, RAM), static random access memory (Static RAM, SRAM), dynamic random access memory (Dynamic RAM, DRAM), synchronous dynamic random access memory (Synchronous DRAM, SDRAM), double data rate synchronous dynamic random access memory (Double Data Rate SDRAM, DDRSDRAM), enhanced synchronous dynamic random access memory (Enhanced SDRAM, ESDRAM), synchronous connection dynamic random access memory (Synch link DRAM , SLDRAM) and Direct Memory Bus Random Access Memory (Direct Rambus RAM, DRRAM). The memory 2909 in the embodiment of the present application includes but is not limited to these and any other suitable types of memory.

The processor 2910 may include one or more processing units; optionally, the processor 2910 integrates an application processor and a modem processor, wherein the application processor mainly processes operations related to the operating system, user interface, and application programs, etc., Modem processors mainly process wireless communication signals, such as baseband processors. It can be understood that the foregoing modem processor may not be integrated into the processor 2910 .

Wherein, when it is determined that the first network functional entity of the first network fails, the processor 2910 is configured to update the network selection priority corresponding to the first network; the network selection priority corresponding to the first network is low The network selection priority corresponding to the second network, and/or, the network selection priority corresponding to the first network is lower than the network selection priority corresponding to the first network when no failure occurs;

The radio frequency unit 2901 is configured to send a first request message to the access network device; the first request message is used to instruct the access network device to communicate with the target network function entity of the second network; the target network function entity of the second network The network function entity has the same network function as the first network function entity in the first network.

In the above embodiment, when it is determined that the first network functional entity of the first network fails, the terminal updates the network selection priority corresponding to the first network, and/or, the terminal sends a message indicating access to the access network device The first request message communicated between the network device and the target network functional entity of the second network, and the target network functional entity of the second network replaces the failed first network functional entity in the first network, so that the terminal can obtain normal network services.

Optionally, the radio frequency unit 2901 is further configured to receive a failure notification about the first network, and determine that a failure occurs to a first network function entity of the first network;

Optionally, the first request message includes at least one of the following: first indication information used to indicate that a failure occurs in the first network; information used to indicate a failed network function entity in the first network second indication information; third indication information for indicating a non-faulty network function entity in the first network, the faulty network function entity includes the first network function entity, and the non-faulty network function entity does not include all The first network functional entity.

In the above embodiment, when the terminal receives the failure notification about the first network, it sends the first request message to the access network device to instruct the access network device to communicate with the target network functional entity of the second network, so as to facilitate access The network device communicates with the target network function entity of the second network based on the first request message, so that the terminal can still obtain normal network services when the first network fails.

Optionally, the radio frequency unit 2901 is further configured to receive a fault recovery notification about the first network;

The processor 2910 is further configured to update the network selection priority corresponding to the first network; the network selection priority corresponding to the first network is higher than the network selection priority corresponding to the second network, and/or, the The network selection priority corresponding to the first network is restored to the network selection priority corresponding to the first network when no failure occurs.

In the above embodiment, when the terminal receives the failure recovery notification about the first network, it may update the network selection priority corresponding to the first network, so that the network selection priority corresponding to the first network is higher than the network selection priority corresponding to the second network. Priority, which is convenient for terminals to access the first network to obtain normal services and reduce the occupation of resources on the second network.

Optionally, the radio frequency unit 2901 is further configured to receive a response message sent by the access network device; the response message is determined based on a processing result fed back by the target network function entity in the second network.

In the above embodiment, when the first network functional entity of the first network fails, the terminal may receive a response message sent by the access network device based on the processing result fed back by the target network functional entity in the second network, so that It is ensured that the terminal can obtain normal network services when the first network functional entity of the first network fails.

Optionally, the first request message is used to request to register with the second network, or, the first A request message is used to request to acquire service data.

The embodiment of the present application also provides a network-side device. Optionally, the network-side device may be an access network device, including a processor and a communication interface, and the communication interface is used to determine that a failure occurs in the first network functional entity of the first network. In the case of , communicate with the target network function entity of the second network; the target network function entity of the second network has the same network function as the first network function entity in the first network.

The network-side device embodiment corresponds to the above-mentioned network-side device method embodiment, and each implementation process and implementation mode of the above-mentioned method embodiment can be applied to this network-side device embodiment, and can achieve the same technical effect.

Specifically, the embodiment of the present application also provides a network side device. As shown in FIG. 29 , the network side device 3000 includes: an antenna 3001 , a radio frequency device 3002 , a baseband device 3003 , a processor 3004 and a memory 3005 . The antenna 3001 is connected to the radio frequency device 3002 . In the uplink direction, the radio frequency device 3002 receives information through the antenna 3001, and sends the received information to the baseband device 3003 for processing. In the downlink direction, the baseband device 3003 processes the information to be sent and sends it to the radio frequency device 3002, and the radio frequency device 3002 processes the received information and sends it out through the antenna 3001.

The method performed by the network side device in the above embodiments may be implemented in the baseband device 3003, where the baseband device 3003 includes a baseband processor.

The baseband device 3003 may include, for example, at least one baseband board, on which a plurality of chips are arranged, as shown in FIG. The program executes the network device operations shown in the above method embodiments.

The network side device may also include a network interface 3006, such as a common public radio interface (common public radio interface, CPRI).

Specifically, the network side device 3000 in the embodiment of the present invention further includes: instructions or programs stored in the memory 3005 and executable on the processor 3004, and the processor 3004 calls the The instruction or program executes the method executed by each module shown in Figure 25, and achieves the same technical effect. In order to avoid repetition, it is not repeated here.

The embodiment of the present application also provides a network side device. Optionally, the network side device may be a core network device, including a processor and a communication interface, and the communication interface is used to receive the second request message sent by the access network device; The second request message is sent by the access network device when it is determined that the first network functional entity of the first network fails;

Specifically, the embodiment of the present application also provides a network side device. As shown in FIG. 30 , the network side device 3100 includes: a processor 3101 , a network interface 3102 and a memory 3103 . Wherein, the network interface 3102 is, for example, a common public radio interface (common public radio interface, CPRI).

Specifically, the network-side device 3100 in this embodiment of the present invention further includes: instructions or programs stored in the memory 3103 and operable on the processor 3101, and the processor 3101 calls the instructions or programs in the memory 3103 to execute the various programs shown in FIG. The method of module execution achieves the same technical effect, so in order to avoid repetition, it is not repeated here.

The embodiment of the present application also provides a readable storage medium. The readable storage medium stores a program or an instruction. When the program or instruction is executed by the processor, each process in the above embodiment of the network fault handling method is implemented, and can To achieve the same technical effect, in order to avoid repetition, no more details are given here.

Wherein, the processor is the processor in the terminal described in the foregoing embodiments. The readable memory The storage medium includes a computer-readable storage medium, such as a computer read-only memory ROM, a random access memory RAM, a magnetic disk or an optical disk, and the like.

The embodiment of the present application further provides a chip, the chip includes a processor and a communication interface, the communication interface is coupled to the processor, and the processor is used to run programs or instructions to implement the above-mentioned network fault processing method Each process of the example, and can achieve the same technical effect, in order to avoid repetition, will not repeat them here.

It should be understood that the chip mentioned in the embodiment of the present application may also be called a system-on-chip, a system-on-chip, a system-on-a-chip, or a system-on-a-chip.

An embodiment of the present application further provides a computer program/program product, the computer program/program product is stored in a storage medium, and the computer program/program product is executed by at least one processor to implement the above-mentioned network fault processing method The various processes of the embodiment can achieve the same technical effect, so in order to avoid repetition, details are not repeated here.

The embodiment of the present application also provides a network fault processing system, including: at least two of a terminal, an access network device, and a core network device, and the terminal can be used to perform the steps of the above-mentioned network fault processing method The access network device may be configured to execute the steps of the above method for handling network faults, and the core network device may be configured to execute the steps of the above method for processing network faults.

It should be noted that, in this document, the term "comprising", "comprising" or any other variation thereof is intended to cover a non-exclusive inclusion such that a process, method, article or apparatus comprising a set of elements includes not only those elements, It also includes other elements not expressly listed, or elements inherent in the process, method, article, or device. Without further limitations, an element defined by the phrase "comprising a ..." does not preclude the presence of additional identical elements in the process, method, article, or apparatus comprising that element. In addition, it should be pointed out that the scope of the methods and devices in the embodiments of the present application is not limited to performing functions in the order shown or discussed, and may also include performing functions in a substantially simultaneous manner or in reverse order according to the functions involved. Functions are performed, for example, the described methods may be performed in an order different from that described, and various steps may also be added, omitted, or combined. Additionally, features described with reference to certain examples may be implemented in other examples combination.

Through the description of the above embodiments, those skilled in the art can clearly understand that the methods of the above embodiments can be implemented by means of software plus a necessary general-purpose hardware platform, and of course also by hardware, but in many cases the former is better implementation. Based on such an understanding, the technical solution of the present application can be embodied in the form of computer software products, which are stored in a storage medium (such as ROM/RAM, magnetic disk, etc.) , CD-ROM), including several instructions to make a terminal (which may be a mobile phone, a computer, a server, an air conditioner, or a network device, etc.) execute the methods described in the various embodiments of the present application.

The embodiments of the present application have been described above in conjunction with the accompanying drawings, but the present application is not limited to the above-mentioned specific implementations. The above-mentioned specific implementations are only illustrative and not restrictive. Those of ordinary skill in the art will Under the inspiration of this application, without departing from the purpose of this application and the scope of protection of the claims, many forms can also be made, all of which belong to the protection of this application.

Claims

A method for handling network faults, comprising:

In a case where it is determined that the first network functional entity of the first network fails, the terminal performs at least one of the following operations:

Updating the network selection priority corresponding to the first network; the network selection priority corresponding to the first network is lower than the network selection priority corresponding to the second network, and/or, the network selection priority corresponding to the first network The level is lower than the network selection priority corresponding to the first network when no failure occurs;

Sending a first request message to the access network device; the first request message is used to instruct the access network device to communicate with the target network function entity of the second network; the target network function entity of the second network communicates with the first The first network function entities in the network have the same network function.
The method for processing a network failure according to claim 1, wherein the method further comprises:

The terminal receives a failure notification about the first network, and determines that a first network functional entity of the first network fails;

The fault notification includes at least one of the following: first indication information for indicating that a fault occurs in the first network; second indication information for indicating a faulty network function entity in the first network; The third indication information of a non-failure network function entity in the first network, the faulty network function entity includes the first network function entity, and the non-failure network function entity does not include the first network function entity.
The method for processing a network failure according to claim 1 or 2, wherein the first request message includes at least one of the following items: first indication information used to indicate that the first network fails; second indication information of a faulty network functional entity in the first network; third indication information for indicating a non-faulty network functional entity in the first network, where the faulty network functional entity includes the first network functional entity, The non-faulty network function entity does not include the first network function entity.
The method for processing a network fault according to claim 1 or 2, wherein the access network device includes an access network device shared by the first network and the second network, or includes the first network A network corresponds to an access network device that is not shared with the second network, or includes an access network device corresponding to the second network that is not shared with the first network.
The method for processing network faults according to claim 1 or 2, wherein, after the terminal updates the network selection priority corresponding to the first network, the method further includes:

receiving, by the terminal, a failure recovery notification on the first network;

The terminal updates the network selection priority corresponding to the first network; the network selection priority corresponding to the first network is higher than the network selection priority corresponding to the second network, and/or, the first network The corresponding network selection priority is restored to the network selection priority corresponding to the first network when no failure occurs.
The method for processing a network fault according to claim 1 or 2, wherein, after the terminal sends the first request message to the access network device, the method further comprises:

The terminal receives the response message sent by the access network device; the response message is determined based on a processing result fed back by the target network function entity in the second network.
The method for processing a network failure according to claim 1 or 2, wherein the first request message is used to request registration to the second network, or the first request message is used to request to obtain service data.
The method for processing a network failure according to claim 2, wherein the failure notification is carried by a Non-Access Stratum (NAS) message or a Radio Resource Control (RRC) message.
A method for handling network faults, comprising:

When it is determined that the first network functional entity of the first network fails, the access network device communicates with the target network functional entity of the second network; the target network functional entity of the second network communicates with the target network functional entity of the first network The first network function entity has the same network function.
The method for processing a network failure according to claim 9, wherein, before the access network device communicates with the target network function entity of the second network, the method further comprises:

The access network device receives a first request message sent by a terminal; the first request message is sent by the terminal when a first network functional entity of the first network fails;

The access network device communicates with the target network function entity of the second network, including:

The access network device based on the first request message and the target network function of the second network Physical communication.
The method for processing a network fault according to claim 10, wherein the communication between the access network device and the target network function entity of the second network based on the first request message includes:

The access network device communicates with the target network function entity of the second network through the non-faulty network function entity of the first network based on the first request message.
The method for processing a network fault according to claim 10, wherein the access network device includes an access network device shared by the first network and the second network;

The access network device communicating with the target network function entity of the second network based on the first request message includes:

In a case where the access network device detects a failure of the first network, the access network device communicates with a target network function entity of the second network based on the first request message;

Or, in a case where the access network device receives a fault notification about the first network, the access network device communicates with a target network function entity of the second network based on the first request message; or,

The first request message carries a fault notification about the first network;

The access network device communicating with the target network function entity of the second network based on the first request message includes:

The access network device communicates with a target network function entity of the second network based on the failure notification about the first network.
The method for processing a network fault according to claim 9 or 10, wherein the access network device includes an access network device corresponding to the first network that is not shared with the second network or the second network Corresponding access network equipment that is not shared with the first network;

The access network device communicates with the target network function entity of the second network, including:

The access network device communicates with the target network functional entity of the second network based on the configuration information; the configuration information is used to indicate to communicate with the target network functional entity of the second network when the first network fails ;or,

The access network device sends an unfailed network function entity in the first network based on the received Communicating with the target network function entity of the second network for the fault notification.
The method for handling network faults according to claim 10, wherein the access network device includes an access network device corresponding to the first network that is not shared with the second network, or includes the second network An access network device corresponding to the network that is not shared with the first network;

The access network device communicating with the target network function entity of the second network based on the first request message includes:

The access network device communicates with the target network function entity of the second network based on the first request message and configuration information; the configuration information is used to indicate the connection with the second network when the first network fails. Target Network Functional Entity Communications; or,

The access network device communicates with the target network function entity of the second network based on the first request message and the received fault notification sent by the non-faulty network function entity in the first network; or,

The first request message carries a fault notification about the first network;

The access network device communicates with a target network function entity of the second network based on the failure notification about the first network.
The method for processing a network fault according to any one of claims 12-14, wherein the fault notification includes at least one of the following: first indication information for indicating that the first network has a fault; second indication information of a faulty network functional entity in the first network; third indication information for indicating a non-faulty network functional entity in the first network, where the faulty network functional entity includes the first network functional entity, The non-faulty network function entity does not include the first network function entity.
The method for processing a network failure according to any one of claims 10-14, wherein the first request message includes at least one of the following: first indication information used to indicate that the first network has failed; The second indication information of the faulty network function entity in the first network; the third indication information used to indicate the non-faulty network function entity in the first network, the faulty network function entity includes the first network function entity , the non-faulty network function entity does not include the first network function entity.
The method for processing network faults according to any one of claims 9-14, wherein, in the After the access network device communicates with the target network function entity of the second network, the method further includes:

The access network device receives a response message sent by the target network function entity in the second network; the response message is determined based on a processing result fed back by the target network function entity in the second network;

The access network device sends the response message to the terminal.
The method for processing a network fault according to any one of claims 10-14, wherein the access network device communicates with the target network function entity of the second network based on the first request message, comprising:

obtaining, by the access network device, a second request message based on the first request message;

The access network device sends the second request message to the core network device; the second request message is used to indicate communication with the target network function entity of the second network.
The method for processing a network failure according to any one of claims 9-14, wherein the method further comprises:

The access network device sends a failure recovery notification about the first network to the terminal.
The method for processing a network failure according to any one of claims 10-14, wherein the first request message is used to request registration to the second network, or the first request message is used to request to obtain service data.
The method for processing a network failure according to any one of claims 12-14, wherein the failure notification is carried in a Non-Access Stratum (NAS) message or a Radio Resource Control (RRC) message.
A method for handling network faults, comprising:

The core network device receives the second request message sent by the access network device; the second request message is sent by the access network device when it is determined that the first network functional entity of the first network fails;

In the case that the core network device is a non-faulty network function entity in the first network, the core network device communicates with a second network function entity of a second network; the second network function entity communicates with the first network function entity a first network functional entity of a network having the same network function;

In the case where the core network device is a target network functional entity in the second network, the core network device communicates with an unfaulted network functional entity in the first network, or, the core network device communicates with the The third network functional entity in the second network communicates; the third network functional entity communicates with the The non-faulty network function entities in the first network have the same network function.
The method for processing network faults according to claim 22, wherein the method further comprises:

In the case where the core network device is a target network functional entity in the second network, the core network device receives a fault notification sent by an unfaulted network functional entity in the first network;

The fault notification includes at least one of the following: first indication information for indicating that a fault occurs in the first network; second indication information for indicating a faulty network function entity in the first network; The third indication information of a non-failure network function entity in the first network, the faulty network function entity includes the first network function entity, and the non-failure network function entity does not include the first network function entity.
The method for processing a network fault according to claim 22 or 23, wherein the access network device includes an access network device shared by the first network and the second network, or includes the first network The corresponding access network device not shared with the second network, or includes the access network device corresponding to the second network not shared with the first network.
The method for processing a network failure according to claim 23, wherein the failure notification is carried by a Non-Access Stratum NAS message or a Radio Resource Control (RRC) message.
A device for processing network faults, comprising: a first update module and/or a first sending module;

When it is determined that the first network functional entity of the first network fails, the first update module is configured to update the network selection priority corresponding to the first network; the network selection priority corresponding to the first network is lower than the network selection priority corresponding to the second network, and/or, the network selection priority corresponding to the first network is lower than the network selection priority corresponding to the first network when no failure occurs;

The first sending module is configured to send a first request message to the access network device; the first request message is used to instruct the access network device to communicate with a target network function entity of the second network; the second The target network functional entity of the network has the same network function as the first network functional entity in the first network.
A device for processing network faults, comprising:

The first communication module is configured to determine that the first network functional entity of the first network fails In this case, communicate with the target network function entity of the second network; the target network function entity of the second network has the same network function as the first network function entity in the first network.
A device for processing network faults, comprising:

The first receiving module is configured to receive a second request message sent by the access network device; the second request message is sent by the access network device when it is determined that the first network functional entity of the first network fails ;

The second communication module is configured to communicate with a second network function entity of the second network when the core network device is a non-faulty network function entity in the first network; the second network function entity communicates with the first network function entity a first network functional entity of a network having the same network function;

A third communication module, configured to communicate with an unfaulted network functional entity in the first network when the core network device is a target network functional entity in the second network, or, communicate with the core network device and The third network function entity in the second network communicates; the third network function entity has the same network function as the non-faulty network function entity in the first network.
A terminal, including a processor and a memory, the memory stores programs or instructions that can be run on the processor, and when the programs or instructions are executed by the processor, it implements any one of claims 1 to 8 Steps in the method for handling network faults described above.
An access network device, comprising a processor and a memory, the memory stores programs or instructions that can run on the processor, and when the programs or instructions are executed by the processor, any of claims 9 to 21 can be implemented. A step in the method for handling a network failure.
A core network device, comprising a processor and a memory, the memory stores programs or instructions that can run on the processor, and when the programs or instructions are executed by the processor, any one of claims 22 to 25 can be realized. Steps in the method for dealing with network faults described in item.
A readable storage medium, on which a program or instruction is stored, and when the program or instruction is executed by a processor, the network failure processing method according to any one of claims 1-8 is realized, or the The method for handling network faults according to any one of claims 9 to 21, or the steps for implementing the method for processing network faults according to any one of claims 22 to 25.