CN116723588A

CN116723588A - Fault recovery method and device, electronic equipment and storage medium

Info

Publication number: CN116723588A
Application number: CN202310875642.5A
Authority: CN
Inventors: 胡家元; 李建钊; 李文云; 章锐; 何林
Original assignee: China Telecom Technology Innovation Center; China Telecom Corp Ltd
Current assignee: China Telecom Technology Innovation Center; China Telecom Corp Ltd
Priority date: 2023-07-17
Filing date: 2023-07-17
Publication date: 2023-09-08

Abstract

The application discloses a fault recovery method, a fault recovery device, electronic equipment and a storage medium, and relates to the technical field of communication. The method comprises the following steps: firstly, when the DRA node detects the fault of the PCF node, session information is acquired from the SMF node, wherein the session information comprises a user IP address segment; the DRA node determines PCF information corresponding to the user IP address field according to the user IP address field; and then, the DRA node sends the PCF information to the target PCRF node so that the target PCRF node determines a user policy for establishing a session flow of the user and outputs the user policy to the SMF node for recovering the session establishment flow.

Description

Fault recovery method and device, electronic equipment and storage medium

Technical Field

The present application relates to the field of communications technologies, and in particular, to a fault recovery method, a fault recovery device, an electronic device, and a storage medium.

Background

In the 5th generation (the 5th generation,5G) mobile communication system, when the terminal equipment establishes a session flow, a protocol data unit (Protocol Data Unit, PDU) session request is initiated to an access and mobility management (access and mobility management function, AMF) node; the AMF node sends session information to a session management function (session management function, SMF) according to the PDU session request; the SMF obtains the user policy from the policy control function (policy control function, PCF) node based on the session information such that the session establishment is completed.

However, during the session establishment process, when the PCF node fails, the SMF node cannot acquire the relevant user policy from the PCF node, resulting in a session establishment failure.

Disclosure of Invention

The application provides a fault recovery method, which is used for recovering a session establishment flow when a PCF node fails.

In a first aspect, a fault recovery method is provided, including:

when the DRA node detects the fault of the PCF node, session information is acquired from the SMF node; wherein the session message includes a user IP address field;

the DRA node determines PCF information corresponding to the user IP address segment according to the user IP address segment;

and the DRA node sends the PCF information to a PCRF node so that the target PCRF node determines a user policy for establishing a session flow of the user and outputs the user policy to the SMF node.

Optionally, the DRA node determines PCF information corresponding to the user IP address segment according to the user IP address segment, including:

the DRA node queries in a session binding relation list of the BSF node according to the user IP address segment, and queries PCF information corresponding to the user IP address segment;

the session binding relation list comprises PCF information bound with each user IP address segment.

Optionally, the method further comprises:

when the PCF node is in a normal state, the DRA node determines the session information from the PCF node;

and the DRA node synchronizes the session information to the target PCRF node according to a preset communication rule.

Optionally, the user policy is determined by the target PCRF node according to the PCF information and session information stored by the target PCRF node.

In a second aspect, there is provided a DRX node comprising:

the detection module is used for acquiring session information from the SMF node when the PCF node fails; wherein the session message includes a user IP address field;

the determining module is used for determining PCF information corresponding to the user IP address field according to the user IP address field;

and the sending module is used for sending the PCF information to a PCRF node so that the target PCRF node determines a user policy for establishing a session flow of the user and outputs the user policy to the SMF node.

Optionally, the determining module is specifically configured to:

inquiring in a session binding relation list of the BSF node according to the user IP address segment, and inquiring PCF information corresponding to the user IP address segment;

Optionally, the node further includes a synchronization module; the synchronization module is used for determining the session information from the PCF node when the PCF node is in a normal state; and synchronizing the session information to the target PCRF node according to a preset communication rule.

In a third aspect, there is provided an electronic device comprising:

a memory for storing a computer program; a processor for implementing the method steps of any one of the first aspects when executing a computer program stored on the memory.

In a fourth aspect, there is provided a computer readable storage medium having stored thereon a computer program which, when executed by a processor, implements the method steps of any of the first aspects.

In the embodiment of the application, firstly, when the DRA node detects the fault of the PCF node, session information is acquired from the SMF node, wherein the session information comprises a user IP address field; the DRA node determines PCF information corresponding to the user IP address field according to the user IP address field; and then, the DRA node sends the PCF information to the target PCRF node so that the target PCRF node determines a user policy for establishing a session flow of the user and outputs the user policy to the SMF node. Because the target PCRF node stores the content related to the session establishment of the user, when the PCF node fails, the session establishment flow can be restored through the target PCRF node, so that the failure of the calling and called services is prevented, the user session service is put in, and meanwhile, the additional PCF node does not need to be deployed to sink to the local, thereby reducing the cost.

The technical effects of each of the second to fourth aspects and the technical effects that may be achieved by each aspect are referred to above for the technical effects that may be achieved by the first aspect or each possible aspect in the first aspect, and the detailed description is not repeated here.

Drawings

FIG. 1 is a diagram of a system architecture to which embodiments of the present application are applicable;

FIG. 2 is a flow chart of a fault recovery method according to an embodiment of the present application;

fig. 3 is an interactive flow chart of session information synchronization before failure of a PCF node provided in an embodiment of the present application;

fig. 4 is a schematic structural diagram of a DRA node according to an embodiment of the present application;

fig. 5 is a schematic structural diagram of an electronic device according to an embodiment of the present application.

Detailed Description

In order to make the objects, technical solutions and advantages of the present application more apparent, the present application will be further described in detail with reference to the accompanying drawings. The specific method of operation in the method embodiment may also be applied to the device embodiment or the system embodiment. In the description of the present application, "a plurality of" means "at least two". "and/or", describes an association relationship of an association object, and indicates that there may be three relationships, for example, a and/or B, and may indicate: a exists alone, A and B exist together, and B exists alone. A is connected with B, and can be represented as follows: both cases of direct connection of A and B and connection of A and B through C. In addition, in the description of the present application, the words "first," "second," and the like are used merely for distinguishing between the descriptions and not be construed as indicating or implying a relative importance or order.

(1) A Data Network (DN) may refer to a Network that provides services for a terminal device, where some DNs may provide a Network function for the terminal device, and some DNs may provide a multimedia message function for the terminal device.

(2) The data network name (Data Network Name, DNN) is the name of the PDU session providing connection data network.

(3) Protocol data units (Protocol Data Unit, PDUs) refer to units of data transferred between peer layers, e.g., PDUs of the physical layer of the PDU are data bits, PDUs of the data link layer are data frames, PDUs of the network layer are data packets, PDUs of the transport layer are data segments, and other higher layer PDUs are data.

To facilitate understanding of the embodiments of the present application, a communication system suitable for use in the embodiments of the present application will be described in detail with reference to the communication system shown in fig. 1. Fig. 1 is a schematic diagram of a system architecture to which an embodiment of the present application is applicable, as shown in fig. 1, in a 5G system architecture, a terminal device 101 may communicate with a core network via an access network device 102.

A terminal device may refer to a User Equipment (UE), an access terminal, a subscriber unit, a subscriber station, a mobile station, a remote terminal, a mobile device, a user terminal, a wireless communication device, a user agent, or a user equipment. An access terminal may be a cellular telephone, a cordless telephone, a session initiation protocol (session initiation protocol, SIP) phone, a wireless local loop (wireless local loop, WLL) station, a personal digital assistant (personal digital assistant, PDA), a handheld device with wireless communication capabilities, a computing device or other processing device connected to a wireless modem, an in-vehicle device, a wearable device, a terminal device in a future 5G network, etc. For convenience of description, only 1 terminal device is illustrated in fig. 1, and in an actual network, a plurality of terminal devices may coexist, which is not described herein.

AN Access Network (AN) device, which may also be referred to as a radio access network (radio access network, RAN) device, is hereinafter collectively referred to as AN access network device, and is mainly responsible for providing wireless connection for a terminal device, ensuring reliable transmission of uplink and downlink data of the terminal device, and so on. The access network device may be a next generation base station (gNB), an evolved Node B (eNB), or the like.

The AMF node mainly comprises a terminal point of a wireless access network control plane, a terminal point of non-access signaling, legal interception, access authorization or authentication, mobility management and the like.

The SMF node is mainly responsible for interacting with separate data planes, creating, updating and deleting PDU sessions and managing the session context with user plane functions (user Plane function, UPF), e.g. a suitable UPF node may be selected for the terminal device based on its location information.

The PCF node is mainly responsible for the functions of setting up, releasing, changing, etc. the transmission path of the user plane.

The routing agent (diameter route agent, DRA) node is responsible for signaling destination address translation and conversion, and implements LTE signaling routing, authentication of users, location update, charging management, and the like.

The policy and charging rules function (Policy and Charging Rules Function, PCRF) is the policy and charging control policy decision point for traffic data flows and IP bearer resources.

Session binding support function (Binding Support Function, BSF) nodes implement session binding, storing session binding messages for the terminal device.

User plane functions (user Plane function, UPF) nodes, the main functions including packet routing and forwarding, quality of service (quality of service, qoS) handling of user plane data.

It should be noted that fig. 1 is only an example, and other nodes, such as application function (application function, AF) nodes, etc., may also be included, which are not illustrated one by one.

The network architecture and the service scenario described in the embodiments of the present application are for more clearly describing the technical solution of the embodiments of the present application, and do not constitute a limitation on the technical solution provided by the embodiments of the present application, and those skilled in the art can know that, with the evolution of the network architecture and the appearance of the new service scenario, the technical solution provided by the embodiments of the present application is applicable to similar technical problems.

In order to further explain the technical solution provided by the embodiments of the present application, the following details are described with reference to the accompanying drawings and the detailed description. Although embodiments of the present application provide the method operational steps shown in the following embodiments or figures, more or fewer operational steps may be included in the method, either on a routine or non-inventive basis. In steps where there is logically no necessary causal relationship, the execution order of the steps is not limited to the execution order provided by the embodiments of the present application. The method may be performed sequentially or and in accordance with the method shown in the embodiments or the drawings when the actual process or system is executed.

Fig. 2 is a flowchart of a fault recovery method according to an embodiment of the present application. The flow can be executed by a DRA node (such as the DRA node shown in figure 1) to realize session establishment and ensure the normal communication function of the user when the PCF node fails. As shown in fig. 2, the process includes the steps of:

201: and when the DRA node detects the fault of the PCF node, acquiring a session message from the SMF node.

Optionally, a heartbeat packet may be disposed between the DRA node and the PCF node, and configured to detect whether the PCF node has a fault in real time, where the DRA node determines that the PCF node has a fault when the heartbeat packet between the PCF nodes is lost. The heartbeat packet is a data packet for informing the opposite party of the state at regular time between the DRA node and the PCF node, and the heartbeat packet can be sent according to a certain period, for example, if the DRA node periodically receives the heartbeat packet of the PCF node, the PCF node can be determined that no fault occurs; if the DRA node does not receive the heartbeat packet of the PCF node within the specified time length, the heartbeat packet is considered to be lost, and the PCF node can be determined to be faulty.

In other embodiments, the DRA node detects that the PCF node fails to interact with the SMF node in a message, and confirms that the PCF node fails to interact with the SMF node in a message.

Optionally, the session message is generated when the UE requests to establish a session, and the session message may include a user IP address field, and may further include a UE identifier, a session type, a mobile network node name, information, and the like.

Optionally, when the PCF node is in a normal state, session information initiated by the UE may be synchronized in real time to the PCRF node, so that when the PCF node fails, a session establishment request of the UE may be recovered based on the session information stored in the PCRF node, thereby completing establishment of a voice dedicated carrier, and guaranteeing a communication function of a user.

301: the UE sends a PDU session request to the AMF node via the RAN node.

The Session Request carries a user IP address field and may also carry network slice information, such as single network slice selection assistance information (Single Network Slice Selection Assistance information, S-nsai) for identifying a network slice, DNN information, PDU Session ID, request type (Request type), etc.

302: after the AMF node receives the session request, the AMF node sends session information to the SMF node. The Session information carries a user IP address field, and may further include information such as S-nsai, PDU Session ID, DNN information, AMF ID, access Type (Access Type), and general public user identifier (Generic Public Subs cription Identifier, GPSI).

303: and the SMF node sends a request for acquiring the user policy to the PCF node according to the session information.

The user policy request may include the session information. The step can be that the SMF node selects UPF, acquires the session subscription related data, completes the authorization and authentication of PDU session request, and after successful authentication, the SMF node selects corresponding PCF node to acquire user policy.

304: and the PCF node returns a user policy request response to the SMF node, determines a target PCRF node corresponding to the user IP address segment, and synchronizes the session message to the target PCRF node through the DRA node.

The user policy request response comprises information such as user policy, charging control decision and the like for completing session establishment flow connection.

In this step, the DRA node may synchronize the session information to the target PCRF node according to a preset communication rule.

305: after receiving the user policy request response, the SMF node sends a session establishment receiving message to the AMF node.

306: after receiving the session establishment reception message, the AMF node sends an N2 PDU Session Request message to the RAN node. The N2 PDU Session Request message is used to request creation of an N2 PDU session.

307: the RAN node establishes flow connection with the UE according to the N2 PDU Session Request message.

In the embodiment of the application, the session information can be synchronized to the target PCRF node in real time for storage through the above-mentioned fig. 3, so that under the extreme condition of the complete failure of the PCF node, the relevant session information can be obtained from the target PCRF node, and the user policy is determined, thereby still maintaining the technology of establishing the session communication internet function for the user.

202: and the DRA node determines PCF information corresponding to the user IP address segment according to the user IP address segment.

Optionally, determining the PCF message corresponding to the user address segment may specifically be: and the DRA node inquires PCF information corresponding to the user IP address segment from a session binding relation list of the BSF node according to the user IP address segment. The session binding relationship list includes PCF information bound by each user IP address segment, as shown in table 1, which exemplarily shows the session binding relationship list.

Table 1: session binding relationship list

It should be noted that table 1 is merely an example, and may be extended according to an actual scenario, and embodiments of the present application are not limited herein.

Alternatively, the PCF information may include a PCF ID.

203: the DRA node sends PCF information to the target PCRF node.

Alternatively, the PCF information may be sent to the target PCRF node via an Rx interface request. The Rx interface is an important interface that triggers VoLTE-specific bearer establishment.

Optionally, after the target PCRF node receives the PCF information, the target PCRF node may determine, according to the PCF information and session information stored by the target PCRF node, a user policy for recovering a session flow of the user, and then send the user policy to the SMF node through the Gx interface.

Optionally, after receiving the user policy, the SMF node may send a session establishment reception message to the AMF node; after receiving the session establishment receiving message, the AMF node sends an N2 PDU Session Request message to the RAN node, where the N2 PDU Session Request message is used to request to create an N2 PDU session; the RAN node establishes flow connection with the UE according to the N2 PDU Session Request message, thereby guaranteeing the basic data voice service of the user.

Based on the same technical concept, the embodiment of the application also provides a DRX node, which can realize the fault recovery method flow in the embodiment of the application.

Fig. 4 is a schematic structural diagram of a DRX node according to an embodiment of the present application. The structure comprises: the detection module 401, the determination module 402, the sending module 403, and further may further include a synchronization module 404.

A detection module 401, configured to obtain a session message from a session management function SMF node when a PCF node failure is detected; wherein the session message includes a user IP address field;

a determining module 402, configured to determine PCF information corresponding to the user IP address segment according to the user IP address segment;

and a sending module 403, configured to send the PCF information to a PCRF node, so that the target PCRF node determines a user policy for the user to establish a session flow, and outputs the user policy to the SMF node.

A synchronization module 404, configured to determine, when the PCF node is in a normal state, the session information from the PCF node; and synchronizing the session information to the target PCRF node according to a preset communication rule.

Optionally, the determining module is specifically configured to:

inquiring in a session binding relation list of a session binding support function node BSF node according to the user IP address segment, and inquiring PCF information corresponding to the user IP address segment; the session binding relation list comprises PCF information bound with each user IP address segment.

It should be noted that, the above device provided in the embodiment of the present application can implement all the method steps in the embodiment of the method and achieve the same technical effects, and the details of the same parts and beneficial effects as those of the embodiment of the method in the embodiment are not described here.

Based on the same technical concept, the embodiment of the application also provides electronic equipment, which can realize the function of the fault recovery device.

The embodiment of the present application is not limited to a specific connection medium between the processor 501 and the memory 502, and the processor 501 and the memory 502 are exemplified in fig. 5 by a connection between the processor 501 and the memory 502 through the bus 500. The connection between the other components of bus 500 is shown in bold lines in fig. 5, and is merely illustrative and not limiting. Bus 500 may be divided into an address bus, a data bus, a control bus, etc., and is represented by only one thick line in fig. 5 for ease of illustration, but does not represent only one bus or one type of bus. Alternatively, the processor 501 may be referred to as a controller, and the names are not limited.

In an embodiment of the present application, the memory 502 stores instructions executable by the at least one processor 501, and the at least one processor 501 may perform a fault recovery method as discussed above by executing the instructions stored in the memory 502. The processor 501 may implement the functions of the various modules in the apparatus shown in fig. 4.

The processor 501 is a control center of the device, and various interfaces and lines can be used to connect various parts of the entire control device, and by executing or executing instructions stored in the memory 502 and invoking data stored in the memory 502, various functions of the device and processing data can be performed to monitor the device as a whole.

In one possible design, processor 501 may include one or more processing units, and processor 501 may integrate an application processor and a modem processor, where the application processor primarily processes operating systems, user interfaces, application programs, and the like, and the modem processor primarily processes wireless communications. It will be appreciated that the modem processor described above may not be integrated into the processor 501. In some embodiments, processor 501 and memory 502 may be implemented on the same chip, or they may be implemented separately on separate chips in some embodiments.

The processor 501 may be a general purpose processor such as a Central Processing Unit (CPU), digital signal processor, application specific integrated circuit, field programmable gate array or other programmable logic device, discrete gate or transistor logic device, discrete hardware components, and may implement or perform the methods, steps and logic blocks disclosed in embodiments of the present application. The general purpose processor may be a microprocessor or any conventional processor or the like. The steps of a fault recovery method disclosed in connection with the embodiments of the present application may be directly embodied as execution completion by a hardware processor, or may be executed in combination by hardware and software modules in the processor.

The memory 502, as a non-volatile computer readable storage medium, may be used to store non-volatile software programs, non-volatile computer executable programs, and modules. The Memory 502 may include at least one type of storage medium, and may include, for example, flash Memory, hard disk, multimedia card, card Memory, random access Memory (Random Access Memory, RAM), static random access Memory (Static Random Access Memory, SRAM), programmable Read-Only Memory (Programmable Read Only Memory, PROM), read-Only Memory (ROM), charged erasable programmable Read-Only Memory (Electrically Erasable Programmable Read-Only Memory), magnetic Memory, magnetic disk, optical disk, and the like. Memory 502 is any other medium that can be used to carry or store desired program code in the form of instructions or data structures and that can be accessed by a computer, but is not limited to such. The memory 502 in embodiments of the present application may also be circuitry or any other device capable of performing storage functions for storing program instructions and/or data.

By programming the processor 501, the code corresponding to one of the fault recovery methods described in the previous embodiments may be cured into the chip, thereby enabling the chip to perform one of the fault recovery methods of the embodiment shown in fig. 2 at runtime. How to design and program the processor 501 is a technique well known to those skilled in the art, and will not be described in detail herein.

It should be noted that, the above-mentioned power-on electronic device provided in the embodiment of the present application can implement all the method steps implemented in the above-mentioned method embodiment, and can achieve the same technical effects, and specific details of the same parts and beneficial effects as those of the method embodiment in the present embodiment are not described herein.

The embodiment of the application also provides a computer readable storage medium, wherein the computer readable storage medium stores computer executable instructions for causing a computer to execute a fault recovery method in the above embodiment.

Embodiments of the present application also provide a computer program product which, when invoked by a computer, causes the computer to perform a fault recovery method as in the previous embodiments.

It will be appreciated by those skilled in the art that embodiments of the present application may be provided as a method, system, or computer program product. Accordingly, the present application may take the form of an entirely hardware embodiment, an entirely software embodiment or an embodiment combining software and hardware aspects. Furthermore, the present application may take the form of a computer program product embodied on one or more computer-usable storage media (including, but not limited to, disk storage, CD-ROM, optical storage, and the like) having computer-usable program code embodied therein.

The present application is described with reference to flowchart illustrations and/or block diagrams of methods, apparatus (systems) and computer program products according to the application. It will be understood that each flow and/or block of the flowchart illustrations and/or block diagrams, and combinations of flows and/or blocks in the flowchart illustrations and/or block diagrams, can be implemented by computer program instructions. These computer program instructions may be provided to a processor of a general purpose computer, special purpose computer, embedded processor, or other programmable data processing apparatus to produce a machine, such that the instructions, which execute via the processor of the computer or other programmable data processing apparatus, create means for implementing the functions specified in the flowchart flow or flows and/or block diagram block or blocks.

These computer program instructions may also be stored in a computer-readable memory that can direct a computer or other programmable data processing apparatus to function in a particular manner, such that the instructions stored in the computer-readable memory produce an article of manufacture including instruction means which implement the function specified in the flowchart flow or flows and/or block diagram block or blocks.

These computer program instructions may also be loaded onto a computer or other programmable data processing apparatus to cause a series of operational steps to be performed on the computer or other programmable apparatus to produce a computer implemented process such that the instructions which execute on the computer or other programmable apparatus provide steps for implementing the functions specified in the flowchart flow or flows and/or block diagram block or blocks.

Claims

1. A method of fault recovery comprising:

when the routing agent DRA node detects a policy control function PCF node fault, session information is acquired from a session management function SMF node; wherein the session message includes a user IP address field;

and the DRA node sends the PCF information to a target Policy and Charging Rules Function (PCRF) node so that the target PCRF node determines a user policy for establishing a session flow of a user and outputs the user policy to the SMF node.

2. The method of claim 1 wherein the DRA node determining PCF information corresponding to the segment of user IP addresses from the segment of user IP addresses comprises:

the DRA node inquires from a session binding relation list of a session Binding Support Function (BSF) node according to the user IP address segment, and inquires PCF information corresponding to the user IP address segment;

3. The method of claim 1, wherein the method further comprises:

4. A method according to any of claims 1-3, wherein the subscriber policy is determined by the target PCRF node based on the PCF information and self-stored session information.

5. A routing agent DRX node, comprising:

the detection module is used for acquiring session information from the session management function SMF node when detecting the PCF node fault of the policy control function; wherein the session message includes a user IP address field;

and the sending module is used for sending the PCF information to a target Policy and Charging Rules Function (PCRF) node so that the target PCRF node determines a user policy for establishing a session flow of a user and outputs the user policy to the SMF node.

6. The node of claim 5, wherein the determining module is specifically configured to:

inquiring in a session binding relation list of a session Binding Support Function (BSF) node according to the user IP address field, and inquiring PCF information corresponding to the user IP address field;

7. The node of claim 5, wherein the node further comprises a synchronization module;

the synchronization module is used for determining the session information from the PCF node when the PCF node is in a normal state; and synchronizing the session information to the target PCRF node according to a preset communication rule.

8. The node of any of claims 5-7, wherein the subscriber policy is determined by the target PCRF node based on the PCF information and self-stored session information.

9. An electronic device, comprising:

a memory for storing a computer program;

a processor for carrying out the method steps of any one of claims 1-4 when executing a computer program stored on said memory.

10. A computer-readable storage medium, characterized in that the computer-readable storage medium has stored therein a computer program which, when executed by a processor, implements the method steps of any of claims 1-4.