WO2020063876A1 - Ue迁移方法、装置、系统及存储介质 - Google Patents

Ue迁移方法、装置、系统及存储介质 Download PDF

Info

Publication number
WO2020063876A1
WO2020063876A1 PCT/CN2019/108574 CN2019108574W WO2020063876A1 WO 2020063876 A1 WO2020063876 A1 WO 2020063876A1 CN 2019108574 W CN2019108574 W CN 2019108574W WO 2020063876 A1 WO2020063876 A1 WO 2020063876A1
Authority
WO
WIPO (PCT)
Prior art keywords
smf
standby
active
information
upf
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Ceased
Application number
PCT/CN2019/108574
Other languages
English (en)
French (fr)
Chinese (zh)
Inventor
梁爽
李志军
朱进国
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
ZTE Corp
Original Assignee
ZTE Corp
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by ZTE Corp filed Critical ZTE Corp
Priority to EP19866085.4A priority Critical patent/EP3860189B8/en
Priority to JP2021517185A priority patent/JP7438202B2/ja
Priority to ES19866085T priority patent/ES2965860T3/es
Priority to KR1020217009128A priority patent/KR102889893B1/ko
Priority to CA3114150A priority patent/CA3114150C/en
Priority to BR112021005801-0A priority patent/BR112021005801A2/pt
Publication of WO2020063876A1 publication Critical patent/WO2020063876A1/zh
Priority to US17/214,581 priority patent/US12052588B2/en
Anticipated expiration legal-status Critical
Ceased legal-status Critical Current

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W76/00—Connection management
    • H04W76/10—Connection setup
    • H04W76/19—Connection re-establishment
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W24/00—Supervisory, monitoring or testing arrangements
    • H04W24/04—Arrangements for maintaining operational condition
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W76/00—Connection management
    • H04W76/10—Connection setup
    • H04W76/18—Management of setup rejection or failure
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W80/00—Wireless network protocols or protocol adaptations to wireless operation
    • H04W80/08—Upper layer protocols
    • H04W80/10—Upper layer protocols adapted for application session management, e.g. SIP [Session Initiation Protocol]
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W76/00—Connection management
    • H04W76/20—Manipulation of established connections
    • H04W76/25—Maintenance of established connections

Definitions

  • the embodiments of the present application relate to, but are not limited to, the field of communications, for example, to but not limited to a UE migration method, device, system, and storage medium.
  • 5G systems include the wireless subsystem 5GRAN (5G Radio Access Network, 5G Wireless Access system), 5G core network subsystem 5GC (5G Core, 5G core network).
  • 5GRAN 5G Radio Access Network, 5G Wireless Access system
  • 5G core network subsystem 5GC 5G Core, 5G core network
  • FIG. 1 is a schematic diagram of the architecture of a 5G system, which is composed of several NF (Network Function).
  • the 5G wireless subsystem part mainly includes NR (New Radio).
  • the 5G core network subsystem includes UDM (Unified Data Management), AMF (Access Management Function), SMF (Session Management Function), and UPF (User Plane Function, User plane function), PCF (Policy Control Function), of which: UDM (Unified Data Management): unified data management function, is a permanent storage place for user contracted data, located in the home network of the user contract;
  • AMF Access management Function
  • Access management function Access management function, which manages the needs of users to access the network, and is responsible for terminal-to-network NAS layer (Non-Access Stratum, non-access layer) signaling management, user mobility management, and other functions;
  • SMF Session Management Function
  • Session management function manages user's PDU (Packet Data Unit) sessions, QoS (Quality of Service) flows
  • PCF Policy Control Function: Policy control function, responsible for providing various levels of policy rules for AMF and SMF.
  • DN Data Network
  • AF Application Function
  • a solution is to wait for the UE to initiate an uplink data transmission, then detect the failure of the SMF, and then resume the PDU session.
  • the recovery of the PDU cannot be triggered, so the delivery of the downlink data will fail.
  • the UE migration method, device, system, and storage medium provided in the embodiments of the present application can avoid a situation in which a PDU session is invalidated when an SMF fails in the related art, and the uplink and downlink data of the UE cannot be normally delivered.
  • An embodiment of the present application provides a UE migration method, including: a network function NF acquiring a link state between the NF and an active session management function SMF; the NF is an NF for establishing signaling interaction with the active SMF; The NF sends an SMF failure notification message to the standby SMF when it is determined that the active SMF fails.
  • the SMF failure notification message is used to trigger the standby SMF to migrate the UE on the active SMF to the standby SMF itself.
  • An embodiment of the present application further provides a UE migration method, including: the standby SMF receives an SMF failure notification message sent by the NF when it determines that the active SMF is faulty; the NF establishes a signaling interaction with the active SMF. NF; the standby SMF migrates the UE on the active SMF to itself.
  • An embodiment of the present application further provides a UE migration method, including: NF acquiring a link state between the NF and an active SMF; NF is an NF for establishing signaling interaction with the active SMF; When the SMF fails, the SMF failure notification message is sent to the standby SMF; when the standby SMF receives the SMF failure notification message, the UE on the active SMF is migrated to itself.
  • An embodiment of the present application further provides a user equipment UE migration apparatus, which is applied to an NF that generates signaling interaction with an SMF, and includes: an acquisition module configured to acquire a link state between the NF and an active SMF; and a sending module Is set to send an SMF failure notification message to the standby SMF when it is determined that the active SMF has failed; the SMF failure notification message is used to trigger the standby SMF to migrate the UE on the active SMF to itself.
  • An embodiment of the present application further provides a user equipment UE migration apparatus, which is applied to a standby SMF, and includes: a receiving module configured to receive an SMF failure notification message sent by the NF when it is determined that the primary SMF fails; NF is The active SMF establishes a signaling interaction NF; a migration module is configured to migrate a UE on the active SMF to itself.
  • An embodiment of the present application further provides a user equipment UE migration system, including: a NF and a standby SMF; the NF is an NF that generates signaling interaction with the SMF; and the NF is configured to perform a link state between the NF and the active SMF.
  • the NF determines that the active SMF fails, the SMF failure notification message sent by the NF migrates the UE on the active SMF to itself.
  • An embodiment of the present application further provides a NF, including a first processor, a first memory, and a first communication bus; the first communication bus is configured to implement connection and communication between the first processor and the first memory The first processor is configured to execute one or more programs stored in the first memory to implement the steps of the UE migration method applied to NF as described above.
  • An embodiment of the present application further provides a backup SMF, including a second processor, a second memory, and a second communication bus; the second communication bus is configured to implement connection and communication between the second processor and the second memory The second processor is configured to execute one or more programs stored in the second memory to implement the steps of the UE migration method applied to the standby SMF as described above.
  • An embodiment of the present application further provides a user equipment UE migration system, including a third processor, a third memory, and a third communication bus; the third communication bus is configured to implement a connection between the third processor and the third memory
  • the third processor is configured to execute one or more programs stored in the third memory, so as to implement the steps of the UE migration method applied to the system as described above.
  • An embodiment of the present application further provides a computer-readable storage medium, where the computer-readable storage medium stores one or more programs, and the one or more programs can be executed by one or more processors to implement the foregoing.
  • the steps of any of the UE migration methods are not limited to:
  • FIG. 1 is a schematic architecture diagram of a 5G system in related technologies
  • FIG. 2 is a schematic diagram of a stateless design that supports different types of NFs provided by the UDSF provided by this application;
  • FIG. 3 is a schematic flowchart of a UE registering to a 5G network in the related art
  • FIG. 4 is a schematic flowchart of creating a PDU session after a UE registers with a 5G network in the related art
  • FIG. 5 is a schematic flowchart of a UE migration method applied to a NF side according to Embodiment 1 of the present application;
  • FIG. 6 is a flowchart of obtaining a link status between the UPF and the active SMF through heartbeat detection according to the first embodiment of the present application;
  • FIG. 7 is a schematic flowchart of obtaining a link state between the non-UPF NF and the active SMF through heartbeat detection according to the first embodiment of the present application;
  • FIG. 8 is a schematic flowchart of obtaining backup SMF information by a UPF according to Embodiment 1 of the present application.
  • FIG. 9 is a schematic flowchart of obtaining backup SMF information by a NF according to Embodiment 1 of the present application.
  • FIG. 10 is a schematic flowchart of a UE migration method applied to a standby SMF side according to Embodiment 2 of the present application;
  • FIG. 11 is a schematic flowchart of a NF triggering a UE migration to a standby SMF after learning that a primary SMF fails according to Embodiment 2 of the present application;
  • FIG. 12 is a schematic flowchart of another NF triggering UE migration to a standby SMF after learning that the primary SMF fails, according to Embodiment 2 of the present application; FIG.
  • FIG. 13 is a schematic flowchart of another NF triggering UE migration to a standby SMF after learning that the primary SMF fails according to Embodiment 2 of the present application;
  • FIG. 14 is a schematic flowchart of a UE migration method applied to a system according to Embodiment 3 of the present application;
  • FIG. 15 is a schematic structural diagram of a UE migration system according to Embodiment 4 of the present application.
  • FIG. 16 is a schematic structural diagram of a UE migration apparatus applied to a NF according to Embodiment 4 of the present application;
  • FIG. 17 is a schematic structural diagram of a UE migration apparatus applied to a standby SMF according to Embodiment 4 of the present application;
  • FIG. 18 is a schematic structural diagram of a NF according to Embodiment 5 of the present application.
  • FIG. 19 is a schematic structural diagram of a standby SMF according to Embodiment 5 of the present application.
  • FIG. 20 is a schematic structural diagram of a UE migration system according to Embodiment 5 of the present application.
  • 5G networks support NF's stateless design.
  • Stateless design means that the same type of NF serving the UE, such as AMF, can be replaced in the two processes before and after.
  • the context information of the UE needs to be stored in the UDSF (Unstructured Data Storage Function).
  • the same type of NF such as AMF
  • different types of NFs cannot mutually access UE context information on the UDSF.
  • Figure 2 illustrates the stateless design of UDSF supporting different types of NF, such as AMF, SMF, UDM, PCF. Different types of NFs use different interfaces to access the UE context on the UDSF.
  • the stateless design based on NF provides a capability. When a certain NF fails, the same NF can take over the process of the failed NF based on the UE context on the UDSF.
  • the UE registers with the 5G network and initiates the related processes of PDU session creation to the 5G network. After these processes, the UE can obtain packet data services from the 5G network.
  • FIG. 3 is a schematic flowchart of a UE registering to a 5G network, including steps 301 to 314.
  • step 301 the UE sends a registration request (Registration Request) to the gNB.
  • step 302 the gNB selects an appropriate AMF according to the conditions.
  • step 303 the gNB forwards the registration request of the UE to the AMF.
  • step 304 if the UE does not provide SUCI (Subscription, Concealed, Identifier, Encrypted Signing Identifier), the AMF sends an Identification Request (Identification Request) to the UE.
  • SUCI Subscriber Identity
  • Identifier Request Encrypted Signing Identifier
  • step 305 the UE returns the requested SUCI to the AMF in response to the identity request.
  • the AMF selects a suitable AUSF (Authentication Server Function) for the UE to perform an authentication operation.
  • AUSF Authentication Server Function
  • step 307 the AUSF initiates an identity authentication and authentication process for the UE.
  • step 308 the AMF selects a suitable UDM for the UE.
  • step 309 the AMF initiates AMF registration with the UDM, and the UDM receives the AMF registration and registers the AMF information for the UE service.
  • the AMF sends a subscription request to the UDM to obtain a mobility management related subscription of the UE.
  • the UDM receives the request from the AMF and sends related contract data to the AMF.
  • step 311 the AMF selects a suitable PCF for the UE.
  • step 312 the AMF sends a mobility policy request to the PCF.
  • the PCF receives the AMF request and returns mobility policy data (AM Policy) to the AMF.
  • AM Policy mobility policy data
  • step 313 the AMF returns a Registration Accept Response to the UE.
  • step 314 after receiving the registration reception response from the AMF, the UE sends a registration reception message (Registration Complete) to the AMF.
  • a registration reception message (Registration Complete)
  • FIG. 4 is a schematic flowchart of the process of initiating the creation of a PDU session after the UE registers with the 5G network, including steps 401 to 416.
  • step 401 the UE sends a PDU session establishment request (PDU Session Establishment Request) to the AMF.
  • PDU Session Establishment Request PDU Session Establishment Request
  • the AMF selects an appropriate SMF for the UE according to the PDU session establishment request of the UE, for example, according to the DNN (Data Network Name) requested by the UE.
  • DNN Data Network Name
  • step 403 the AMF sends a Create SMContext Request to the SMF.
  • step 404 the SMF initiates a session subscription data acquisition process to the UDM, and the UDM returns the session subscription data of the UE to the SMF.
  • step 405 the SMF returns a SM session context response (Create SMContext Response) to the AMF.
  • SM session context response Create SMContext Response
  • step 406 the SMF selects a suitable PCF. If the AMF provides the PCF selected by the AMF in the foregoing step, the SMF uses the PCF.
  • the SMF sends a session policy request to the PCF.
  • the PCF receives the SMF request and returns session policy data (SM Policy) to the SMF.
  • SM Policy session policy data
  • step 408 the SMF selects an appropriate UPF according to the information such as DNN and UE location.
  • step 409 the SMF sends an N4 session establishment request (N4 Session Establishment Request) to the UPF.
  • N4 Session Establishment Request N4 Session Establishment Request
  • the UPF responds to the SMF request to establish an N4 session, and returns an N4 session establishment response (S4) to the SMF.
  • step 410 after the N4 session is successfully established, the SMF sends an N1 / N2 Message Transfer Request (N1 / N2Message Transfer) to the AMF, which carries the context information of the PDU session, such as the created QoS flow list, and the uplink F-assigned by the UPF. TEID, etc.
  • N1 / N2 Message Transfer Request N1 / N2Message Transfer
  • the AMF sends an N2 PDU Session Request (N2) PDU Session Request message to the gNB.
  • N2 PDU Session Request N2 PDU Session Request
  • the AMF carries a NAS message to be sent to the UE by the AMF. Part of the PDU session context sent to the UE.
  • the gNB sends a radio resource setup (AN Resource Setup) request to the UE, and establishes a suitable radio bearer for the UE according to the PDU session information provided by the AMF.
  • AN Resource Setup AN Resource Setup
  • the gNB returns an N2 interface PDU Session Receive (N2) PDU Session Receive message to the AMF, which carries the N3 interface resources allocated by the gNB, such as the F-TEID of the gNB.
  • N2 interface PDU Session Receive N2 interface PDU Session Receive
  • step 414 the AMF sends an Update SM Session Context Request (Update SMContext Request) to the SMF to update the remote F-TEID of the UPF on the N3 interface, that is, the F-TEID of the gNB on the UPF.
  • Update SM Session Context Request Update SMContext Request
  • step 415 the SMF sends an N4 session update request (N4 Session Update Request) to the UPF, updates the F-TEID of the gNB on the N3 interface, and the UPF returns an N4 session update response to the SMF.
  • N4 Session Update Request N4 Session Update Request
  • step 416 the SMF returns an update SMContext context response (UpdateSMContextResponse) to the AMF.
  • update SMContext context response UpdateSMContextResponse
  • this embodiment of the present application provides a user equipment UE migration method, and the UE migration method provided by this embodiment is applied to The network function NF, as shown in FIG. 5, includes steps S501 and S502.
  • step S501 the NF acquires a link state between itself and the active SMF; the NF is an NF that establishes signaling interaction with the SMF.
  • NF and SMF Due to the need for message flow interaction, NF and SMF generate message flow interaction.
  • the types of NF include non-SMF NFs such as AMF, UDM, UPF, and PCF.
  • the main SMF is the SMF that currently generates signaling interactions with the NF.
  • the state of the link between the NF and the active SMF is detected, and whether the active SMF is faulty is determined by acquiring whether the link is interrupted.
  • the NF is a user plane function UPF.
  • the methods by which the UPF obtains the link status between itself and the active SMF include, but are not limited to, the following two methods:
  • Method 1 The UPF acquires the link status between the UPF and the active SMF by detecting the N4 signaling transmission status when the N4 signaling message is sent to the active SMF.
  • the N4 signaling message sent by the UPF to the SMF such as the notification of the arrival of downlink data.
  • the UPF can sense the link interruption.
  • Method 2 The UPF obtains the link status between the UPF and the active SMF according to the heartbeat detection between the UPF and the active SMF after the N4 connection with the active SMF is established.
  • a heartbeat-like keep-alive mechanism that is, a detection message is sent periodically to determine the link status.
  • the flowchart shown in FIG. 6 is a flowchart of obtaining the link status between the UPF and the active SMF through heartbeat detection provided in this embodiment, which includes steps 601 to 612.
  • step 601 the AMF receives a request to create a PDU session.
  • the request for creating a PDU session may come from the UE.
  • step 602 the AMF selects an appropriate SMF for the UE as the active SMF, and sends a request for creating an SM session context to the active SMF.
  • step 603 the active SMF returns a response to create an SM session to the AMF.
  • step 604 the master SMF selects a suitable UPF.
  • step 605 the active SMF sends an N4 connection establishment request to the UPF to establish a connection between the active SMF and the UPF.
  • the N4 connection establishment request may carry an SMF instance ID (SMF instance ID).
  • the UPF receives an N4 connection establishment request, establishes an N4 connection with the active SMF, and returns an N4 connection establishment response.
  • step 607 the active SMF sends an N4 session establishment request to the UPF to establish an N4 session for the UE.
  • the N4 session establishment request may carry an SMF instantiation identifier.
  • the primary SMF may provide the UPF with its own SMF instantiation identifier when establishing an N4 connection to the UPF or when establishing an N4 session with the UPF, which is not limited here.
  • the N4 session establishment request may further carry a Connection Set ID (CSID).
  • the CSID can associate several N4 sessions of several UEs together, and can be taken over by another SMF in the event of a failure.
  • step 608 after the UPF establishes the N4 session, it returns an N4 session establishment response to the active SMF.
  • step 609 the active SMF continues to create a PDU session.
  • the subsequent process steps of creating a PDU session here include: the primary SMF sends an N1 / N2 message transmission request to the AMF; the AMF sends an N2 interface PDU session request to the gNB; the gNB sends a wireless resource establishment request to the UE; after the wireless resource is created, The gNB returns an N2 interface PDU session reception message to the AMF; the AMF sends an update SM session context request to the active SMF; the active SMF sends an N4 session update request to the UPF; the active SMF returns an update SM session context response to the AMF.
  • step 610 after the active SMF and the UPF establish an N4 connection, a periodic heartbeat detection is initiated between the active SMF and the UPF.
  • the heartbeat detection between the primary SMF and the UPF can be the primary SMF sends an N4 heartbeat request to the UPF, the UPF returns an N4 heartbeat response, or the UPF sends an N4 heartbeat request to the primary SMF, and the primary SMF returns an N4 heartbeat response.
  • the heartbeat detection between the active SMF and the UPF can be performed as long as any step after the establishment of the N4 connection in step 606 is not limited to the step of creating a PDU session in step 609.
  • step 611 when the active SMF fails, the active SMF cannot respond to the heartbeat request of the UPF.
  • step 612 the UPF determines that the link with the active SMF is down.
  • the heartbeat detection between the UPF and the active SMF fails. After multiple failed heartbeat detections, the UPF can determine that the link between the two is interrupted and determine that the active SMF has failed.
  • a flowchart of obtaining a link state between the non-UPF NF and the active SMF through heartbeat detection includes steps 701 to 706.
  • step 701 the non-UPF NF and the active SMF generate a message flow interaction.
  • step 702 the non-UPF NF sends a heartbeat request message to the active SMF.
  • step 703 the active SMF returns a heartbeat response message to the non-UPF NF consumer.
  • step 704 when there is still a process interaction between the non-UPF NF and the active SMF, the non-UPF NF periodically sends a heartbeat request to the active SMF.
  • step 705 when the active SMF fails, the active SMF cannot respond to the heartbeat request of the non-UPF NF.
  • step 706 the link between the non-UPF NF and the active SMF is interrupted.
  • the non-UPF NF may determine that the link between the two is interrupted and determine that the primary SMF has failed.
  • step 502 the NF sends an SMF failure notification message to the standby SMF when it is determined that the active SMF has failed; the SMF failure notification message is used to trigger the standby SMF to migrate the UE on the active SMF to itself.
  • the NF When the NF detects a failure of the active SMF, it can send an SMF failure notification message to the standby SMF, trigger the standby SMF to replace the failed SMF, and take over the UE on the failed SMF.
  • the method before sending the SMF failure notification message to the standby SMF, the method further includes: the NF obtains the standby SMF information of the active SMF; so that the NF sends the SMF failure notification message to the standby SMF according to the standby SMF information.
  • the backup SMF information includes at least one of the following: a group identification of the backup SMF, an instantiation identification of the backup SMF, an SMF failure indication callback address of the backup SMF, N4 interface information of the backup SMF, an SMF node identification of the backup SMF, and a backup SMF identification Correspondence with segment index ID.
  • the SMF group ID is used to identify a group of SMFs with the same or similar characteristics. SMFs belonging to the same group are backed up to each other.
  • an SMF group identifier can be set, and the NRF can query other SMFs with the same SMF group identifier as the backup SMF according to the SMF group identifier.
  • SMF instance ID (SMF instance ID) is used to uniquely identify a specified SMF.
  • SMF instance ID is used to uniquely identify a specified SMF.
  • the backup SMF information in the SMF configuration parameters of the active SMF several SMF instantiation identifiers of the backup SMF can be specified, and the NRF can definitely select one as the backup SMF according to the SMF instantiation identifiers of the backup SMF.
  • the SMF fault indication callback address of the standby SMF is used by the standby SMF to receive the SMF fault indication.
  • the SMF fault indication callback address can be configured in the SMF configuration parameters or in the backup SMF information of the SMF configuration parameters. When the SMF fault indication callback address is configured in the SMF configuration parameters, it indicates the SMF fault indication callback address of the SMF itself; when the SMF fault indication callback address is configured in the backup SMF information of the SMF configuration parameters, it means that the backup SMF information is passed.
  • the SMF failure indication callback address specifies the SMF's standby SMF.
  • the N4 interface information of the standby SMF is used to establish the N4 connection, and may include the following information: the IP address of the N4 interface (IP address for N4 association), and the port of the N4 interface (Port N4 association).
  • the correspondence between the standby SMF identifier and the segment index ID is used to indicate the standby SMF corresponding to the UE context information on the primary SMF of the segment index. Considering that when an SMF fails, a large amount of data needs to be transferred to the standby SMF suddenly. May cause errors, so an SMF can index the stored UE context information and determine an index ID. This index ID is used to instruct a part of the information to be transferred to a standby SMF and another part of the information to another A standby SMF.
  • the primary SMF sends an N4 connection establishment request to the UPF, it can send the correspondence between the standby SMF identifier and the segment index ID to the UPF.
  • the primary SMF sends the corresponding The segment index ID is sent to the UPF.
  • the UPF can determine which backup MF to recover data from according to the above-mentioned correspondence.
  • the SMF identifier here can be one of the following: SMF instance identifier, SMF node identifier.
  • the UPF obtains an N4 connection establishment request when receiving an N4 connection establishment request, or an N4 connection update request, or an N4 session establishment request, or an N4 session update request sent by a master SMF.
  • FIG. 8 is a schematic flowchart of a method for obtaining backup SMF information provided by the UPF according to this embodiment. The above-mentioned several acquisition methods are shown through processes A and B, including steps A801, A802, and B801-B805.
  • the process A is to obtain backup SMF information when it is established through the N4 interface.
  • step A801 the master SMF sends an N4 connection establishment request to the UPF, and the N4 connection establishment request carries backup SMF information.
  • the SMF in this step, can also carry its own identification information, which can be one or a combination of the following: SMF node identification (SMF node ID), SMF instance identification (SMF instance ID).
  • SMF node ID SMF node identification
  • SMF instance ID SMF instance ID
  • the UPF receives the N4 connection establishment request of the SMF, and returns an N4 connection establishment response (N4 Association Establishment Response) to the SMF according to the N4 connection establishment request.
  • N4 connection establishment response N4 Association Establishment Response
  • the UPF When the UPF receives the N4 connection establishment request of the SMF, it obtains the backup SMF information. It should be noted that the backup SMF information can also be updated later. If it is an update, it can be issued through an N4 connection update request, which carries the identification or index information of the backup SMF in the same manner as when it was established.
  • process B is the acquisition of standby SMF information triggered by the establishment of a session-level message.
  • step B801 the AMF sends an SM context creation request to the active SMF.
  • step B802 the master SMF receives the SM context creation request from the AMF, and returns a SM context creation response to the AMF.
  • step B803 the master SMF selects a suitable UPF for the UE.
  • step B804 the primary SMF sends an N4 session establishment request to the UPF, and the N4 session establishment request carries backup SMF information.
  • step B805 the UPF receives the N4 session establishment request of the active SMF, establishes an N4 session according to the request, and returns an N4 session establishment response to the active SMF.
  • the information of the backup SMF may also be updated in the future. If it is updated, it may also be sent in the subsequent PDU session establishment or update message, and the UPF will also update it.
  • non-SMF NFs including AMF, UDM, UPF, and PCF are obtained from the NF storage function NRF.
  • the NRF is registered by the active SMF when it receives the NF registration request from the active SMF.
  • Backup SMF information First, the primary SMF sends an NF registration request to the NRF, which carries SMF configuration parameters. It should be noted that the SMF also carries one or a combination of the following information: SMF group ID (SMF Set ID), standby SMF list, and standby SMF list.
  • SMF group ID SMF Set ID
  • standby SMF list standby SMF list
  • Each SMF contains its SMF instance ID (SMF instance ID); then, the NRF receives and processes the NF registration request of the SMF, and returns an NF registration response to the SMF, so that the primary SMF registers the backup SMF information with the NRF.
  • SMF instance ID SMF instance ID
  • FIG. 9 is a schematic flowchart of the process of obtaining backup SMF information by the NF provided by this embodiment.
  • the processes of registering the backup SMF information on the NRF and the process of obtaining the backup SMF information by the NF are illustrated by processes A and B, respectively.
  • step A901 the active SMF sends a NF registration request to the NRF, carrying the backup SMF configuration parameters, and the backup SMF configuration parameters include the backup SMF information.
  • the active SMF also carries one or a combination of the following information: the SMF group identifier and the standby SMF list.
  • the standby SMF list contains its SMF instantiation identifier.
  • step A902 the NRF receives and processes the NF registration request of the SMF, and returns a NF registration response to the SMF.
  • steps B901 to B902 are performed to obtain a list of alternative standby SMFs from the NRF.
  • steps B903 to B904 are performed to obtain the configuration parameters of the SMF from the NRF.
  • step B901 the NF sends a NF discovery request to the NRF, specifies the NF type as SMF, provides a DNN that requires SMF support, and other necessary information.
  • the NF may further specify an SMF group identifier, and requires the NRF to return a backup SMF list with the same SMF group identifier.
  • the NRF searches for a suitable backup SMF according to the NF's NF discovery request, and returns an NF discovery response to the NF.
  • the NF discovery response includes a list of candidate SMFs and configuration parameters for each SMF.
  • step B903 the NF sends a NF discovery request to the NRF, specifies the NF type as SMF, and provides a backup SMF identifier.
  • the SMF identifier may be one of the following: an SMF instance identifier, and an SMF node identifier.
  • step B904 the NRF obtains the configuration parameters of the designated backup SMF according to the NF discovery request of the NF, and returns an NF discovery response to the NF; the NF discovery response includes the SMF configuration parameters of the requested SMF.
  • the SMF configuration parameters include backup SMF information of the SMF.
  • the configuration parameters When there are multiple corresponding standby SMFs in an active SMF, the configuration parameters also include corresponding segment index IDs.
  • the NF can obtain the SMF configuration parameters of the active SMF from the NRF, and obtain the backup SMF information from the SMF configuration parameters. If the backup SMF information only contains the instantiation ID of the backup SMF, the NF can further obtain other information of the backup SMF from the NRF, such as: SMF failure indication callback address, N4 interface information of the backup SMF, and the node ID of the backup SMF. FQDN or IP address.
  • the SMF failure notification message includes at least one of the following: an SMF instantiation identifier of the primary SMF, an SMF node identifier of the primary SMF, an SMF failure indication of the primary SMF, and a UE migration range indication.
  • the UE migration range indication includes, for example, any of the following: all UEs, UEs in a specified range, and UEs in a random range.
  • all UEs instruct the standby SMF to migrate all UEs from the failed active SMF to the standby SMF; UEs in a specified range instruct the standby SMF to migrate a specific range of UEs from the active SMF to the standby SMF; and a random range UEs do not specify a specific UE range, and the standby SMF migrates all or part of the UEs from the active SMF to the standby SMF according to the local policy or the UDSF decision.
  • the NF obtains the link status between the NF and the active SMF.
  • the NF is the NF that establishes signaling interaction with the SMF.
  • the NF sends an SMF failure notification message to the standby SMF to trigger the standby SMF to migrate the UE on the active SMF to itself, which can effectively avoid the failure of the PDU session caused by the SMF failure, which will cause the uplink and downlink data of the UE. Cases where normal delivery is not possible; and, this application also provides a method for batch recovery of UEs on a failed SMF to a standby SMF, which can effectively save the overall time for SMF failure recovery.
  • this embodiment of the present application provides a UE migration method and a UE migration method provided in this embodiment. Apply to the standby SMF side, as shown in Figure 10, including:
  • step S1001 the standby SMF receives the SMF failure notification message sent by the NF when it is determined that the active SMF has failed; the NF is the NF that establishes signaling interaction with the SMF.
  • the active SMF is the SMF that currently generates signaling interactions with the NF.
  • the NF detects that the active SMF is a failed SMF, it sends an SMF failure notification message to the standby SMF, and triggers the standby SMF to replace the failed SMF. And take over the UE on the failed SMF.
  • the types of NF include non-SMF NFs such as AMF, UDM, UPF, PCF.
  • the SMF fault notification message includes fault indication information, and the fault indication information is used to indicate to the standby SMF that the active SMF has failed; or, the SMF fault notification message is a serviced message and the serviced message is used for the standby When the SMF finds the context information of the UE indicated by the service-oriented message, it determines that the active SMF fails.
  • the UPF selects one or more standby SMFs, it sends fault indication information to the standby SMF in the following ways:
  • the UPF uses the SMF instantiation identifier to obtain the configuration parameters of the SMF from the NRF.
  • the SMF configuration parameters include a callback address for receiving an SMF fault indication, or information for establishing an N4 interface.
  • the UPF uses the method b) to send fault indication information to the SMF.
  • the UPF uses method c) to send fault indication information to the SMF.
  • the UPF sends a notification message to the callback address, carrying the fault indication information.
  • the UPF establishes an N4 connection to the standby SMF, and sends a N4 interface notification message to the standby SMF with a fault indication information.
  • the UPF may transfer the context to different standby SMFs according to different division principles, that is, the message may also carry the index ID in the foregoing embodiment.
  • the standby SMF can obtain data from the UDSF according to the index ID provided by the UPF. If the UPF does not provide an index ID to the standby SMF, the standby SMF may also go to the UDSF to obtain the context according to the local configuration of the index ID configured for the failed SMF.
  • the standby SMF After the SMF failure indication sent by the UPF, the standby SMF queries the UDSF for the context stored by the failed primary SMF.
  • the standby SMF provides the UDSF with identification information of the failed SMF. When there are multiple standby SMFs, for example, an index ID may be provided.
  • the UDSF provides the standby SMF with the context information of the failed active SMF. If UDSF is not deployed, the standby SMF can also be restored based on the configuration backup information.
  • the fault indication is a serviced NF
  • other NFs other than the SMF obtain the information of the standby NRF through NRF query, and then send a request to the standby NRF, which carries the relevant identifier of the terminal.
  • the standby SMF does not have the terminal's information locally, and then goes to the local storage or UDSF query to obtain the terminal's context. Based on this, it is determined that the active SMF has failed and takes over the subsequent processes of the terminal.
  • the NF may be a UPF.
  • the SMF failure notification message sent may include but is not limited to the following two methods:
  • Method 1 The standby SMF receives the SMF failure notification message sent by the SMF failure indication callback address of the standby SMF when it is determined that the primary SMF fails.
  • Method 2 The standby SMF receives the SMF failure notification message sent by the UPF through the N4 interface of the standby SMF when it is determined that the active SMF fails.
  • the UPF uses the SMF instantiated identifier to obtain the configuration parameters of the SMF from the NRF.
  • the SMF configuration parameters include a callback address for receiving an SMF failure indication or information for establishing an N4 interface, so that the UPF sends an SMF failure notification message to the callback address or the N4 interface.
  • the SMF failure notification message may include at least one of the following: an SMF instantiation identifier of the active SMF, an SMF node identifier of the active SMF, an SMF failure indication of the active SMF, and a UE migration range indication.
  • step S1002 the standby SMF migrates the UE on the active SMF to itself.
  • the standby SMF migrates the UE on the primary SMF to the standby SMF itself including but not limited to the following two methods:
  • Method 1 The standby SMF obtains the context information of the UE on the active SMF from the unstructured data storage function UDSF; the standby SMF updates the SMF information on the NF according to the context information, and migrates the UE from the active SMF to itself; where , NF is a non-SMF NF that generates signaling interaction with the SMF. That is, if there is a UDSF in the network, the SMF dynamically stores data on the UDSF, and when a failure occurs, the standby SMF goes to the UDSF to obtain the context.
  • UDSF unstructured data storage function
  • Method 2 The standby SMF obtains the context information of the UE on the active SMF from the active SMF information dynamically backed up in the local storage; the standby SMF updates the SMF information on the NF according to the context information, and migrates the UE from the active SMF. To itself; where NF is a non-SMF NF that generates signaling interactions with the SMF. That is, if there is no UDSF in the network, the SMF dynamically backs up the data to the standby SMF. When a failure occurs, the standby SMF directly enables the local storage context for recovery.
  • the standby SMF determines the UE to be migrated on the active SMF according to the UE migration range indication carried in the SMF failure notification message; the standby SMF migrates the determined UE to itself. If the UE migration range is set to all UEs, the standby SMF migrates all UEs on the active SMF to itself; if the UE migration range is set to UEs in the specified range, the standby SMF migrates the specified UEs on the active SMF to itself ; If the UE migration range is set to an unspecified range, the standby SMF migrates a randomly determined UE to itself according to a local policy, which may be all or part of the UE.
  • a local policy which may be all or part of the UE.
  • the NF may transfer the context to different standby SMFs according to different division principles.
  • the SMF failure notification message sent by the NF received by the standby SMF carries the information in the foregoing embodiment.
  • the standby SMF can go to the UDSF to obtain the context information according to the index ID provided by the UPF.
  • the standby SMF may also obtain the context information from the UDSF according to the segment index ID configured locally for the failed primary SMF.
  • the backup SMF migrates the UE on the primary SMF also includes but is not limited to the following three ways:
  • Method 1 The standby SMF is based on a single UE, and the SMF information on the NF is updated according to the context information of the UE.
  • updating the SMF information on the NF according to the context information of the UE includes at least one of the following:
  • the standby SMF sends the user plane function UPF according to the context information of the UE.
  • the SM policy update request includes SMF replacement instruction, main SMF information.
  • SMF replacement instruction main SMF information.
  • FIG. 11 a flowchart of triggering UE migration to a standby SMF by a NF provided by this embodiment after learning that the primary SMF is faulty includes steps 1101 to 1114.
  • step 1101 when the NF detects a failure of the active SMF, it notifies the standby SMF to take over the UE of the failed SMF.
  • the NF may detect the failure of the primary SMF according to the method in the first embodiment, and then the NF obtains the backup SMF information from the SMF profile (SMF profile).
  • SMF profile SMF profile
  • the NF sends an SMF failure notification message to the standby SMF; it is used to trigger the standby SMF to replace the active SMF and take over all or part of the UEs under the active SMF.
  • the SMF fault notification message carries the SMF instantiation identifier of the replaced SMF.
  • it may also carry an SMF replacement indication, a UE migration range indication, and a NF replacement reason.
  • the UE migration range The indication may be one of the following: all UEs, UEs in a specified range, random range; the reason for NF replacement may be SMF failure.
  • step 1103 the standby SMF returns an SMF failure notification response to the NF.
  • step 1104 the standby SMF queries the UDSF for the UE context information of the failed active SMF.
  • the standby SMF queries the UDSF for the UE context information of the active SMF in the following way:
  • the standby SMF obtains all UE context information under the active SMF from the UDSF.
  • the standby SMF provides the UE range to the UDSF, and obtains the UE context information of the specified range under the faulty active SMF from the UDSF.
  • the standby SMF uses the local strategy, or according to the UDSF strategy, obtains all or part of the UE context information under the failed active SMF from the UDSF.
  • the UE context information obtained by the standby SMF from the UDSF includes one or a combination of the following information: PDU session context, N4 session context, UDM registration information, AMF information, and PCF information.
  • step 1105 according to the request of the standby SMF, the UDSF returns the requested UE context information list of the failed active SMF to the standby SMF.
  • the standby SMF obtains UE context information of each UE, including PDU session context, N4 session context, UDM registration information, AMF information, PCF information, and so on.
  • step 1106 the backup SMF absolutely updates SMF information on other NFs for each UE.
  • the standby SMF obtains the UE context information of each UE from the obtained UE context information list of the failed SMF, and restores the N4 session of the SMF and the UPF according to the UE context information (steps 1107 to 1108), and updates the SMF on the UDM SMF registration information (steps 1109 to 1110), update the SMF information on the AMF (steps 1111 to 1112), and update the SMF information on the PCF (steps 1013 to 1014).
  • step 1107 the standby SMF decides to update the N4 session of the UE on the UPF.
  • the standby SMF Before the SMF initiates an N4 session update request to the UPF, the standby SMF first establishes an N4 connection with the UPF.
  • step 1108 the standby SMF sends an N4 session update request to the UPF, instructing the UPF to update the SMF information of the N4 session, and the UPF returns an N4 session update response to the standby SMF.
  • the standby SMF when the standby SMF sends an N4 session update request, it carries the following information: SMF replacement instruction, original SMF information (old SMF information), the original SMF information may include one or a combination of the following information: SMF node identification (SMF node ID), SMF instance ID (SMF instance ID); In addition, it can also carry the target SMF information (new SMF info), the target SMF information can include one or a combination of the following information: SMF node ID (SMF node ID), SMF instance SMF (Instance ID).
  • SMF node ID SMF node ID
  • SMF instance ID SMF instance ID
  • step 1109 the standby SMF decides to update the SMF registration information on the UDM.
  • step 1110 the standby SMF sends an SMF registration update request to the UDM, instructing the UDM to update the SMF registration information, and the UDM returns an SMF registration update response to the standby SMF.
  • the standby SMF carries the following information when sending the SMF registration update request: UE identification (such as SUPI), SMF replacement instruction, and original SMF information (old SMF info); in addition, it can also carry the target SMF information (new SMF info).
  • step 1111 the standby SMF decides to update the SMF information on the AMF.
  • step 1112 the standby SMF sends an SM session status notification request to the AMF, instructing the AMF to update the SMF information, and the AMF returns an SM session status notification response to the standby SMF.
  • the standby SMF may also carry the following information when sending the SM session status notification request: UE identification (such as SUPI), SMF replacement indication, and original SMF information (old SMF information); in addition, it may also carry target SMF information (new SMF info).
  • UE identification such as SUPI
  • SMF replacement indication such as SMF
  • original SMF information old SMF information
  • target SMF information new SMF info
  • step 1113 the standby SMF decides to update the SMF information on the PCF.
  • step 1114 the standby SMF sends an SM policy update request to the PCF, instructing the PCF to update the SMF information, and the PCF returns an SM policy update response to the standby SMF.
  • the standby SMF may also carry the following information when sending the SM session policy update request: UE identification (such as SUPI), SMF replacement indication, original SMF information (old SMF information); in addition, it may also carry target SMF information (new SMF info).
  • UE identification such as SUPI
  • SMF replacement indication such as SMF
  • original SMF information old SMF information
  • target SMF information new SMF info
  • Method 2 The backup SMF uses a single NF as a unit, and the SMF information on the NF is updated according to the context information of the UE.
  • updating the SMF information on the NF according to the context information of the UE includes at least one of the following: the standby SMF sends the NF to each UPF according to the context information of the UE A replacement request to update the SMF information on the UPF; the NF replacement request includes an SMF replacement indication and the primary SMF information; the standby SMF sends a NF replacement request to each UDM according to the context information of the UE to update the SMF information on the UDM; Among them, the NF replacement request includes an SMF replacement instruction and the primary SMF information; the standby SMF sends an NF replacement request to each AMF according to the UE's context information to update the SMF information on the AMF; among them, the NF replacement request includes the SMF replacement instruction, the primary SMF information is used; the standby SMF sends an NF replacement request to each PCF according to the context information of the UE to update the SMF information
  • Steps 1201 to 1205 are the same as steps 1101 to 1105 in the embodiment corresponding to FIG. 11, and details are not described herein again.
  • the backup SMF absolutely updates SMF information on other NFs for each NF; that is, the backup SMF lists the UPF, UDM, AMF, and PCF associated with the SMF from the UE context information of the faulty SMF obtained. And so on, sending NF replacement requests to each of the UPF, UDM, AMF, and PCF.
  • step 1206 for each UPF, the standby SMF decides to update the SMF information on the UPF.
  • step 1207 the standby SMF sends a NF replacement request to the UPF, instructing the UPF to update the SMF information, and the UPF returns a NF replacement response to the standby SMF.
  • step 1208 for each UDM, the standby SMF decides to update the SMF information on the UDM.
  • step 1209 the standby SMF sends a NF replacement request to the UDM, instructing the UDM to update the SMF information, and the UDM returns a NF replacement response to the standby SMF.
  • step 1210 for each AMF, the standby SMF decides to update the SMF information on the AMF.
  • step 1211 the standby SMF sends an NF replacement request to the AMF, instructing the AMF to update the SMF information, and the AMF returns an NF replacement response to the standby SMF.
  • step 1212 for each PCF, the standby SMF decides to update the SMF information on the PCF.
  • step 1213 the standby SMF sends a NF replacement request to the PCF, instructing the PCF to update the SMF information, and the PCF returns a NF replacement response to the standby SMF.
  • the standby SMF may carry the following information when sending the NF replacement request: the SMF replacement instruction and the original SMF information; in one embodiment, the standby SMF may also carry the following information: target SMF information . It should be noted that both the original SMF information and the target SMF information include corresponding SMF instantiation identifiers.
  • Method 3 The standby SMF is based on a single UE, and the packet data unit PDU session is updated according to the context information of the UE, so that the SMF information on the NF is updated.
  • the standby SMF when the standby SMF is based on a single UE, the standby SMF sends an N1 / N2 message transmission request to the AMF according to the context information of the UE.
  • the N1 / N2 message transmission request includes a PDU session update request, and
  • the AMF is caused to send a PDU session update request to the UE to update the PDU session.
  • FIG. 13 another flowchart of the NF provided in this embodiment is to trigger UE migration to the standby SMF after learning that the primary SMF is faulty, including steps 1301 to 1309.
  • Steps 1301 to 1305 are the same as steps 1101 to 1105 in the embodiment corresponding to FIG. 11, and details are not described herein again.
  • step 1306 the backup SMF absolutely initiates a PDU session update process for each UE.
  • the standby SMF obtains the UE context information of each UE from the obtained UE context information list of the failed active SMF, and uses the UE context information to initiate a PDU session update process.
  • step 1307 the standby SMF sends a N1 / N2 message transmission request to the AMF, which carries a PDU session update request.
  • the backup SMF may carry the following information: the SMF replacement instruction and the original SMF information; in one embodiment, the standby SMF may also carry the following information: the target SMF information. It should be noted that both the original SMF information and the target SMF information include corresponding SMF instantiation identifiers.
  • step 1308 the AMF sends a PDU session update request to the UE.
  • step 1309 the PDU session update is continued to be performed, so that the sessions or information associations between SMF and UPF, SMF and UDM, SMF and AMF, SMF and PCF are updated, that is, the original information on UPF, UDM, AMF, and PCF.
  • SMF failed active SMF
  • SMF standby SMF
  • the standby SMF receives the SMF failure notification message sent by the NF that established the signaling interaction with the SMF when it determines that the active SMF has failed.
  • the indication of the SMF fault notification message migrates the UE on the active SMF to itself, which can effectively avoid the failure of the PDU session caused by the SMF fault, which will cause the uplink and downlink data of the UE to fail to be delivered normally; and this application also provides a A method for batch recovery of UEs on a failed SMF to a standby SMF can effectively save the overall time of SMF failure recovery.
  • this embodiment of the present application provides a UE migration method.
  • the UE migration method provided in this embodiment is applied to include The system side of NF and standby SMF, as shown in Figure 14, includes:
  • step 1401 the NF obtains a link state between itself and the active SMF; the NF is an NF that establishes signaling interaction with the SMF.
  • the types of NF include non-SMF NFs such as AMF, UDM, UPF, and PCF.
  • the active SMF is the SMF that currently generates signaling interactions with the NF.
  • the state of the link between the NF and the active SMF is detected, and whether the active SMF is faulty is determined by acquiring whether the link is interrupted.
  • the NF is a user plane function UPF.
  • the way that the UPF obtains the link status between itself and the active AMF includes, but is not limited to, the following two methods:
  • Method 1 The UPF acquires the link status between the UPF and the active SMF by detecting the N4 signaling transmission status when the N4 signaling message is sent to the active SMF.
  • the N4 signaling message sent by the UPF to the SMF such as the notification of the arrival of downlink data.
  • the UPF can sense the link interruption.
  • Method 2 The UPF obtains the link status between the UPF and the active SMF according to the heartbeat detection between the UPF and the active SMF after the N4 connection with the active SMF is established.
  • a heartbeat-like keep-alive mechanism that is, a detection message is sent periodically to determine the link status.
  • the non-UPF NF detects the non-UPF.
  • the heartbeat detection or signaling interaction response between the UPF NF and the active SMF is used to obtain the link status between the non-UPF NF and the active SMF, so as to determine whether the active SMF is faulty.
  • step 1402 the NF sends an SMF failure notification message to the standby SMF when it is determined that the active SMF fails.
  • the NF When the NF detects a failure of the active SMF, it can send an SMF failure notification message to the standby SMF, trigger the standby SMF to replace the failed SMF, and take over the UE on the failed SMF.
  • the NF is UPF
  • the UPF determines that the primary SMF fails, it sends an SMF failure notification message to the standby SMF through the SMF failure indication callback address of the standby SMF; in another embodiment, In the embodiment, the UPF may also send an SMF failure notification message to the standby SMF through the N4 interface information of the standby SMF when it is determined that the active SMF fails.
  • sending the SMF failure notification message to the standby SMF includes: the NF obtains the standby SMF information of the active SMF; the NF sends an SMF failure notification message to the standby SMF according to the standby SMF information.
  • the backup SMF information includes at least one of the following: a group identification of the backup SMF, an instantiation identification of the backup SMF, an SMF failure indication callback address of the backup SMF, N4 interface information of the backup SMF, an SMF node identification of the backup SMF, and a backup SMF identification Correspondence with segment index ID.
  • the correspondence between the standby SMF identifier and the segment index ID is used to indicate the standby SMF corresponding to the UE context information on the primary SMF of the segment index. Considering that when one SMF fails, a large number of sudden transfers are required. Data to the standby SMF may cause errors, so an SMF can index the stored UE context information and determine an index ID. This index ID is used to indicate that a part of the information is transferred to a standby SMF, and another Part of the information is transferred to another standby SMF.
  • the primary SMF sends an N4 connection establishment request to the UPF, it can carry the correspondence between the standby SMF identifier and the segment index ID to the UPF.
  • the primary The SMF sends the corresponding segment index ID to the UPF.
  • the UPF can determine which backup MF to recover data from according to the above-mentioned correspondence.
  • the SMF identifier here can be one of the following: SMF instance identifier , SMF node identification.
  • the UPF obtains the N4 connection establishment request when receiving an N4 connection establishment request, or an N4 connection update request, or an N4 session establishment request, or an N4 session update request sent by the master SMF. Or the N4 connection update request, or the N4 session establishment request, or the standby SMF information carried in the N4 session update request.
  • non-SMF NFs including AMF, UDM, UPF, PCF, and other NMFs are obtained from the NF storage function NRF.
  • the NRF receives a NF registration request from the active SMF, the active SMF is registered in the Spare SMF information on the NRF.
  • the SMF failure notification message includes at least one of the following: an SMF instantiation identifier of the primary SMF, an SMF node identifier of the primary SMF, an SMF failure indication of the primary SMF, and a UE migration range indication.
  • the UE migration range indication includes, for example, any of the following: all UEs, UEs in a specified range, and UEs in a random range.
  • all UEs instruct the standby SMF to migrate all UEs from the failed active SMF to the standby SMF; UEs in a specified range instruct the standby SMF to migrate a specific range of UEs from the active SMF to the standby SMF; and a random range UEs do not specify a specific UE range, and the standby SMF migrates all or part of the UEs from the active SMF to the standby SMF according to the local policy or the UDSF decision.
  • step 1403 when receiving the SMF fault notification message, the standby SMF migrates the UE on the active SMF to itself.
  • the standby SMF migrates the UE on the active SMF to the standby SMF itself including but not limited to the following two methods:
  • Method 1 The standby SMF obtains the context information of the UE on the active SMF from the unstructured data storage function UDSF; the standby SMF updates the SMF information on the NF according to the context information, and migrates the UE from the active SMF to itself; where , NF is a non-SMF NF that generates signaling interaction with the SMF.
  • Method 2 The standby SMF obtains the context information of the UE on the active SMF from the active SMF information dynamically backed up in the local storage; the standby SMF updates the SMF information on the NF according to the context information, and migrates the UE from the active SMF. To itself; where NF is a non-SMF NF that generates signaling interactions with the SMF.
  • the backup SMF migrates the UE on the primary SMF also includes but is not limited to the following three ways:
  • Method 1 The standby SMF is based on a single UE, and the SMF information on the NF is updated according to the context information of the UE.
  • updating the SMF information on the NF according to the context information of the UE includes at least one of the following:
  • the standby SMF sends the user plane function UPF according to the context information of the UE.
  • the SM policy update request includes SMF replacement instruction, main SMF information.
  • Method 2 The backup SMF uses a single NF as a unit, and the SMF information on the NF is updated according to the context information of the UE.
  • updating the SMF information on the NF according to the context information of the UE includes at least one of the following: the standby SMF sends the NF to each UPF according to the context information of the UE A replacement request to update the SMF information on the UPF; the NF replacement request includes an SMF replacement indication and the primary SMF information; the standby SMF sends a NF replacement request to each UDM according to the context information of the UE to update the SMF information on the UDM; Among them, the NF replacement request includes an SMF replacement instruction and the primary SMF information; the standby SMF sends an NF replacement request to each AMF according to the UE's context information to update the SMF information on the AMF; among them, the NF replacement request includes the SMF replacement instruction, the primary SMF information is used; the standby SMF sends an NF replacement request to each PCF according to the context information of the UE to update the SMF information
  • Method 3 The standby SMF is based on a single UE, and the packet data unit PDU session is updated according to the context information of the UE, so that the SMF information on the NF is updated.
  • the standby SMF when the standby SMF is based on a single UE, the standby SMF sends an N1 / N2 message transmission request to the AMF according to the context information of the UE.
  • the N1 / N2 message transmission request includes a PDU session update request, and
  • the AMF is caused to send a PDU session update request to the UE to update the PDU session.
  • the NF that establishes signaling interaction with the SMF obtains the link status between itself and the active SMF.
  • the standby SMF migrates the UE on the active SMF to itself according to the received SMF failure notification message, which can effectively avoid the failure of the PDU session caused by the SMF failure, which will cause the UE to go up and down.
  • this application also provides a method for batch recovery of UEs on the failed SMF to the standby SMF, which can effectively save the overall time of SMF failure recovery.
  • Embodiment 4 is a diagrammatic representation of Embodiment 4:
  • FIG. 15 is a schematic structural diagram of a user equipment UE migration system according to this embodiment.
  • the user equipment UE migration system includes NF 1501 and standby SMF 1502.
  • NF 1501 is an NF that generates signaling interaction with SMF, and is used to determine the primary The SMF fails, and the SMF failure notification message is sent to the standby SMF 1502; the SMF failure notification message is used to trigger the standby SMF 1502 to migrate the UE on the active SMF to itself; the standby SMF 1502 is used to receive the NF1501 in determining When the active SMF fails, the SMF failure notification message is sent, and the UE on the active SMF is migrated to itself.
  • FIG. 16 is a user equipment UE migration apparatus applied to an NF that generates signaling interaction with SMF according to an embodiment of the present application, including: an obtaining module 1601 and a sending module 1602.
  • the obtaining module 1601 is configured to obtain a link state between the NF and the active SMF.
  • the sending module 1602 is configured to send an SMF failure notification message to the standby SMF when it is determined that the active SMF fails, and the SMF failure notification message is used to trigger the standby SMF to migrate the UE on the active SMF to itself.
  • the type of NF includes non-SMF NFs such as AMF, UDM, UPF, and PCF.
  • the active SMF is the SMF that currently generates signaling interactions with the NF.
  • the obtaining module 1601 detects the link status between the NF and the active SMF, and determines whether the active SMF is faulty by acquiring whether the link is interrupted.
  • the NF is a user plane function UPF.
  • the acquisition module 1601 acquires the link status between the UPF itself and the active AMF, including but not limited to the following two methods:
  • the acquisition module 1601 acquires the link status between the UPF and the active SMF by detecting the N4 signaling transmission status when the UPF sends an N4 signaling message to the active SMF.
  • the N4 signaling message sent by the UPF to the SMF such as the notification of the arrival of downlink data.
  • the obtaining module 1601 can sense the link interruption.
  • the obtaining module 1601 obtains the link status between the UPF and the active SMF according to the heartbeat detection between the UPF and the active SMF after the N4 connection with the active SMF is established.
  • a heartbeat-like keep-alive mechanism that is, a detection message is sent periodically to determine the link status.
  • the non-UPF NF acquires module 1601 after establishing signaling interaction with the active SMF.
  • the link status between the non-UPF NF and the active SMF is obtained to determine whether the active SMF is faulty.
  • the sending module 1602 When the sending module 1602 detects a failure of the active SMF, it may send an SMF failure notification message to the standby SMF, trigger the standby SMF to replace the failed SMF, and take over the UE on the failed SMF. It should be noted that when the NF is UPF, in one embodiment, when determining that the primary SMF fails, the sending module 1602 sends an SMF failure notification message to the standby SMF through the SMF failure indication callback address of the standby SMF; In an implementation manner, the sending module 1602 may also send an SMF fault notification message to the standby SMF through the N4 interface information of the standby SMF when it is determined that the active SMF fails.
  • the sending module 1602 is further configured to obtain backup SMF information of the active SMF, and send an SMF fault notification message to the backup SMF according to the backup SMF information.
  • the backup SMF information includes at least one of the following: a group identification of the backup SMF, an instantiation identification of the backup SMF, an SMF failure indication callback address of the backup SMF, N4 interface information of the backup SMF, an SMF node identification of the backup SMF, and a backup SMF identification Correspondence with segment index ID.
  • the correspondence between the standby SMF identifier and the segment index ID is used to indicate the standby SMF corresponding to the UE context information on the primary SMF of the segment index. Considering that when one SMF fails, a large number of sudden transfers are required. Data to the standby SMF may cause errors, so an SMF can index the stored UE context information and determine an index ID. This index ID is used to indicate that a part of the information is transferred to a standby SMF, and another Part of the information is transferred to another standby SMF.
  • the primary SMF sends an N4 connection establishment request to the UPF, it can carry the correspondence between the standby SMF identifier and the segment index ID to the UPF.
  • the primary The SMF sends the corresponding segment index ID to the UPF.
  • the UPF can determine which backup MF to recover data from according to the above-mentioned correspondence.
  • the SMF identifier here can be one of the following: SMF instance identifier , SMF node identification.
  • the sending module 1602 obtains an N4 connection establishment request, or an N4 connection update request, or an N4 session establishment request, or an N4 session update sent by the receiving master SMF.
  • the backup SMF information carried in the request message is sent, and then an SMF fault notification message is sent to the backup SMF according to the backup SMF information.
  • the sending module 1602 may also obtain the backup SMF information registered by the active SMF on the NRF when the NRF receives the NF registration request of the active SMF from the NF storage function NRF, and then according to the standby SMF The message sends an SMF failure notification message to the standby SMF.
  • the SMF failure notification message includes at least one of the following: an SMF instantiation identifier of the primary SMF, an SMF node identifier of the primary SMF, an SMF failure indication of the primary SMF, and a UE migration range indication.
  • the UE migration range indication includes, for example, any of the following: all UEs, UEs in a specified range, and UEs in a random range.
  • FIG. 17 is a user equipment UE migration apparatus applied to a standby SMF according to an embodiment of the present application, including: a receiving module 1701 and a migration module 1702.
  • the receiving module 1701 is configured to receive an SMF failure notification message sent by the NF when it is determined that the active SMF fails, and the NF is an NF that establishes signaling interaction with the SMF.
  • the migration module 1702 is configured to migrate a UE on the active SMF to itself.
  • the active SMF is the SMF that currently generates signaling interactions with the NF.
  • the NF detects that the active SMF is a failed SMF, it sends an SMF failure notification message to the standby SMF, and instructs the standby SMF to replace the failed SMF. And take over the UE on the failed SMF.
  • the migration module 1702 migrates the UE on the primary SMF to the standby SMF itself including but not limited to the following two methods:
  • the migration module 1702 obtains the context information of the UE on the primary SMF from the unstructured data storage function UDSF, and then updates the SMF information on the NF according to the context information, and migrates the UE from the primary SMF to the standby SMF itself. That is, if there is a UDSF in the network, the SMF dynamically stores data on the UDSF. When a failure occurs, the migration module 1702 goes to the UDSF to obtain the context.
  • the migration module 1702 obtains the context information of the UE on the master SMF from the master SMF information dynamically backed up in the local storage, and then updates the SMF information on the NF according to the context information, and migrates the UE from the master SMF.
  • the standby SMF itself; that is, if the UDSF does not exist in the network, the SMF dynamically backs up data to the standby SMF, and when a failure occurs, the migration module 1702 directly enables the context of the standby SMF's local storage for recovery.
  • the migration module 1702 determines the UE on the active SMF according to the UE migration range indication in the SMF fault notification message; the migration module 1702 migrates the determined UE to the standby SMF itself. If the UE migration range is set to all UEs, the migration module 1702 migrates all UEs on the active SMF to the standby SMF itself; if the UE migration range is set to UEs in the specified range, the migration module 1702 migrates the specified UEs on the active SMF. Migrate to the standby SMF itself; if the UE migration range is set to an unspecified range, the migration module 1702 migrates the randomly determined UE to the standby SMF itself according to the local policy, which may be all or part of the UE.
  • the migration module 1702 migrates the UE on the active SMF also includes but is not limited to the following three ways:
  • the migration module 1702 uses a single UE as a unit, and updates the SMF information on the NF according to the context information of the UE.
  • updating the SMF information on the NF according to the context information of the UE includes at least one of the following: the migration module 1702 provides a user plane function according to the context information of the UE.
  • the UPF sends an N4 session update request to update the SMF information on the UPF.
  • the N4 session update request includes an SMF replacement indication and the primary SMF information.
  • the migration module 1702 sends an SMF registration update request to the unified data management function UDM according to the context information of the UE.
  • the migration module 1702 sends an SM session state update request to the access management function AMF according to the context information of the UE to update the AMF
  • the SM session state update request includes an SMF replacement instruction and the main SMF information.
  • the migration module 1702 sends an SM policy update request to the policy control function PCF according to the context information of the UE to update the SMF information on the PCF.
  • the SM policy update request includes an SMF replacement instruction and active SMF information.
  • Method 2 The migration module 1702 uses a single NF as a unit, and updates the SMF information on the NF according to the context information of the UE.
  • updating the SMF information on the NF according to the context information of the UE includes at least one of the following: the migration module 1702 sends each UPF according to the context information of the UE. Send a NF replacement request to update the SMF information on the UPF.
  • the NF replacement request includes the SMF replacement indication and the main SMF information.
  • the migration module 1702 sends a NF replacement request to each UDM according to the context information of the UE to update the UMF.
  • the NF replacement request includes the SMF replacement instruction and the main SMF information
  • the migration module 1702 sends a NF replacement request to each AMF according to the context information of the UE to update the SMF information on the AMF
  • the NF replacement request includes the SMF The replacement instruction and the main SMF information
  • the migration module 1702 sends an NF replacement request to each PCF according to the context information of the UE to update the SMF information on the PCF
  • the NF replacement request includes the SMF replacement instruction and the main SMF information.
  • Method 3 The migration module 1702 uses a single UE as a unit, and updates the packet data unit PDU session according to the context information of the UE, so that the SMF information on the NF is updated.
  • the migration module 1702 when the migration module 1702 uses a single UE as a unit, the migration module 1702 sends an N1 / N2 message transmission request to the AMF according to the context information of the UE, and the N1 / N2 message transmission request includes a PDU session update request To enable the AMF to send a PDU session update request to the UE to update the PDU session.
  • the NF that establishes signaling interaction with the SMF acquires the link status between itself and the active SMF.
  • the NF determines the active SMF
  • the NF sends an SMF failure notification message to the standby SMF.
  • the standby SMF migrates the UE on the active SMF to itself according to the received SMF failure notification message, which can effectively avoid the failure of the PDU session caused by the SMF failure, and then the UE.
  • a situation where uplink and downlink data cannot be delivered normally; and, this application also provides a method for batch recovery of UEs on a failed SMF to a standby SMF, which can effectively save the overall time of SMF failure recovery.
  • Embodiment 5 is a diagrammatic representation of Embodiment 5:
  • An embodiment of the present application further provides a NF.
  • a NF As shown in FIG. 18, it includes a first processor 1801, a first memory 1802, and a first communication bus 1803.
  • the first communication bus 1803 is used to implement the first processor.
  • the connection and communication between 1801 and the first memory 1802; the first processor 1801 is configured to execute one or more computer programs stored in the first memory 1802, so as to implement the user equipment UE applied to the NF side in the first embodiment. At least one step in the migration method.
  • An embodiment of the present application further provides a backup SMF.
  • FIG. 19 it includes a second processor 1901, a second memory 1902, and a second communication bus 1903.
  • the second communication bus 1903 is used to implement a second process. Connection and communication between the processor 1901 and the second memory 1902; the second processor 1901 is configured to execute one or more computer programs stored in the second memory 1902, so as to implement the user applied to the standby SMF side in the second embodiment described above At least one step in a device UE migration method.
  • An embodiment of the present application further provides a user equipment UE migration system, as shown in FIG. 20, which includes a third processor 2001, a third memory 2002, and a third communication bus 2003, where the third communication bus 2003 is used to implement The connection and communication between the third processor 2001 and the third memory 2002; the third processor 2001 is configured to execute one or more computer programs stored in the third memory 2002, so as to implement the application including the NF in the third embodiment. And at least one step in a method for user equipment UE migration on the system side of the backup SMF.
  • Embodiments of the present application also provide a computer-readable storage medium included in any method or technology for storing information such as computer-readable instructions, data structures, computer program modules, or other data. Implemented volatile or non-volatile, removable or non-removable media.
  • Computer-readable storage media include, but are not limited to, RAM (Random Access Memory), ROM (Read-Only Memory, Read-Only Memory), EEPROM (Electrically Erasable, Programmable, Read-Only Memory) ), Flash memory or other memory technology, CD-ROM (Compact Disc Read-Only Memory), digital versatile disk (DVD) or other optical disk storage, magnetic box, magnetic tape, disk storage or other magnetic storage devices, Or any other medium that can be used to store desired information and can be accessed by a computer.
  • RAM Random Access Memory
  • ROM Read-Only Memory
  • Read-Only Memory Read-Only Memory
  • EEPROM Electrically Erasable, Programmable, Read-Only Memory
  • Flash memory or other memory technology
  • CD-ROM Compact Disc Read-Only Memory
  • DVD digital versatile disk
  • the computer-readable storage medium in this embodiment may be used to store one or more computer programs, and the stored one or more computer programs may be executed by a processor to implement the foregoing first embodiment, and / or the second embodiment, and And / or at least one step of the user equipment UE migration method in Embodiment 3.
  • This embodiment also provides a computer program, which can be distributed on a computer-readable medium and executed by a computable device to implement the first embodiment, and / or the second embodiment, and / or the third embodiment. At least one step of the user equipment UE migration method in; and in some cases, at least one step shown or described may be performed in an order different from that described in the above embodiments.
  • This embodiment also provides a computer program product including a computer-readable device, where the computer-readable device stores the computer program as shown above.
  • the computer-readable device in this embodiment may include a computer-readable storage medium as shown above.
  • a communication medium typically contains computer-readable instructions, data structures, computer program modules, or other data in a modulated data signal such as a carrier wave or other transmission mechanism, and may include any information delivery medium. Therefore, this application is not limited to any specific combination of hardware and software.

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Mobile Radio Communication Systems (AREA)
  • Hardware Redundancy (AREA)
  • Telephonic Communication Services (AREA)
PCT/CN2019/108574 2018-09-27 2019-09-27 Ue迁移方法、装置、系统及存储介质 Ceased WO2020063876A1 (zh)

Priority Applications (7)

Application Number Priority Date Filing Date Title
EP19866085.4A EP3860189B8 (en) 2018-09-27 2019-09-27 Ue migration method, apparatus, system, and storage medium
JP2021517185A JP7438202B2 (ja) 2018-09-27 2019-09-27 Ｕｅ移行方法、装置、システム、および記憶媒体
ES19866085T ES2965860T3 (es) 2018-09-27 2019-09-27 Método, aparato, sistema de migración de UE y medio de almacenamiento
KR1020217009128A KR102889893B1 (ko) 2018-09-27 2019-09-27 Ue 마이그레이션 방법, 장치, 시스템 및 저장 매체
CA3114150A CA3114150C (en) 2018-09-27 2019-09-27 Ue migration method, apparatus, system, and storage medium
BR112021005801-0A BR112021005801A2 (pt) 2018-09-27 2019-09-27 método de migração de ue, aparelho, sistema, e meio de armazenagem
US17/214,581 US12052588B2 (en) 2018-09-27 2021-03-26 UE migration method, apparatus, system, and storage medium

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN201811134224.6 2018-09-27
CN201811134224.6A CN110536330B (zh) 2018-09-27 2018-09-27 一种ue迁移方法、装置、系统及存储介质

Related Child Applications (1)

Application Number Title Priority Date Filing Date
US17/214,581 Continuation US12052588B2 (en) 2018-09-27 2021-03-26 UE migration method, apparatus, system, and storage medium

Publications (1)

Publication Number Publication Date
WO2020063876A1 true WO2020063876A1 (zh) 2020-04-02

Family

ID=68657424

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2019/108574 Ceased WO2020063876A1 (zh) 2018-09-27 2019-09-27 Ue迁移方法、装置、系统及存储介质

Country Status (8)

Country Link
US (1) US12052588B2 (https=)
EP (1) EP3860189B8 (https=)
JP (1) JP7438202B2 (https=)
KR (1) KR102889893B1 (https=)
CN (2) CN110536330B (https=)
BR (1) BR112021005801A2 (https=)
ES (1) ES2965860T3 (https=)
WO (1) WO2020063876A1 (https=)

Cited By (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN115915220A (zh) * 2021-09-30 2023-04-04 中国移动通信有限公司研究院 一种异常处理方法、设备及存储介质
JP2023538534A (ja) * 2020-08-10 2023-09-08 サムスン エレクトロニクス カンパニー リミテッド 無線通信システムの安定性を高める方法及び装置
JP2024521821A (ja) * 2021-05-28 2024-06-04 オラクル・インターナショナル・コーポレイション コアネットワークにおいてネットワーク機能（ｎｆ）高可用性（ｈａ）トポロジ情報を配布するための方法、システム、およびコンピュータ可読媒体
JP2025501040A (ja) * 2021-12-30 2025-01-17 中興通訊股▲ふん▼有限公司 セッション管理機能障害および再選択後のセッション更新のための方法

Families Citing this family (32)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US11778522B2 (en) * 2019-02-18 2023-10-03 Telefonaktiebolaget Lm Ericsson (Publ) Methods and apparatuses for transferring restoration context data
WO2021063767A1 (en) * 2019-10-01 2021-04-08 Nokia Technologies Oy Apparatus, method, and computer program
CN113825111A (zh) 2020-06-19 2021-12-21 中兴通讯股份有限公司 上报用量的方法、网络功能实体和存储介质
CN113852981A (zh) * 2020-06-28 2021-12-28 中兴通讯股份有限公司 用于nf的故障处理方法、网络系统及介质
CN113950058B (zh) * 2020-07-17 2025-05-16 华为技术有限公司 通信方法和装置
EP4165901B1 (en) * 2020-07-23 2026-04-15 ZTE Corporation Data forwarding for user equipment with data transmission
EP4189864B1 (en) * 2020-07-31 2024-12-18 Telefonaktiebolaget LM Ericsson (publ) Network functionality (nf) aware service provision based on service communication proxy (scp)
US11784872B1 (en) 2021-05-07 2023-10-10 T-Mobile Usa, Inc. Suppressing messages to an out-of-service server
US11843503B1 (en) * 2021-05-07 2023-12-12 T-Mobile Usa, Inc. Providing out-of-service notifications regarding a server
CN113163513B (zh) * 2021-05-11 2022-07-12 中国联合网络通信集团有限公司 接入方法及装置
EP4397127A4 (en) * 2021-08-31 2025-04-23 Nokia Solutions and Networks Oy COMMUNICATION IN AN INTEGRATED ACCESS AND BACKHAUL NETWORK
CN115915222A (zh) * 2021-09-30 2023-04-04 中兴通讯股份有限公司 容灾方法、装置、系统及可读存储介质
CN116095722B (zh) * 2021-11-08 2025-12-09 中国移动通信有限公司研究院 网元管理方法、装置、相关设备及存储介质
US20250031265A1 (en) * 2021-12-03 2025-01-23 Telefonaktiebolaget Lm Ericsson (Publ) Method and apparatus for context resumption
CN116847387A (zh) * 2022-03-22 2023-10-03 华为技术有限公司 一种通信方法和通信装置
US20250220565A1 (en) * 2022-03-28 2025-07-03 Lenovo (Singapore) Pte Limited Replacement of an untrusted network function
US20250211634A1 (en) 2022-03-29 2025-06-26 Telefonaktiebolaget Lm Ericsson (Publ) Method and apparatus for processing smf set mismatch
US12309737B2 (en) 2022-04-20 2025-05-20 T-Mobile Usa, Inc. Transition from backup SMF to primary SMF
CN116980942A (zh) * 2022-04-24 2023-10-31 中国电信股份有限公司 网络容灾方法、容灾核心网设备和通信系统
US20250286781A1 (en) * 2022-05-25 2025-09-11 Samsung Electronics Co., Ltd. Method and apparatus for data transmission in service-based architecture in wireless communication systems
US12457573B2 (en) * 2022-08-18 2025-10-28 T-Mobile Innovations Llc Session management function (SMF) outage protection in a wireless communication network
KR20250085761A (ko) * 2022-10-05 2025-06-12 엘지전자 주식회사 5g 무선통신시스템에서 코어 네트워크 장애 문제를 극복하기 위한 코어 네트워크 동작 방법
CN116347467B (zh) * 2023-03-03 2023-12-15 广州爱浦路网络技术有限公司 5g网络中udr进行用户数据管理方法及系统
US20240407025A1 (en) * 2023-05-31 2024-12-05 Dish Wireless L.L.C. System And Method To Reduce Network Function Interruptions In A Service-Based Architecture
US12549433B2 (en) 2023-05-31 2026-02-10 Boost SubscriberCo L.L.C. System and method to reduce network function interruptions in a service-based architecture
US12348355B2 (en) * 2023-05-31 2025-07-01 Dish Wireless L.L.C. System and method to reduce database interruptions in a service-based architecture
WO2024249190A1 (en) * 2023-05-31 2024-12-05 Dish Wireless L.L.C. System and method to reduce network function interruptions in a service-based architecture
WO2025005673A1 (ko) * 2023-06-27 2025-01-02 삼성전자 주식회사 무선 통신 시스템에서 사용자 평면 기능 서비스의 가입 및 트래픽 처리 방법 및 장치
CN119729563A (zh) * 2023-09-28 2025-03-28 华为技术有限公司 通信方法、装置及系统
WO2025170288A1 (ko) * 2024-02-05 2025-08-14 엘지전자 주식회사 이중화 네트워크 코어 통신망에서 코어 네트워크 장애 처리 방법 및 장치
US20250254686A1 (en) * 2024-02-06 2025-08-07 Dell Products L.P. Packet-discarding-aware configured grant pattern adaptation
US12542708B2 (en) * 2024-05-09 2026-02-03 Verizon Patent And Licensing Inc. Systems and methods for priority-aware network function restoration in a wireless network

Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN105577408A (zh) * 2014-09-25 2016-05-11 中兴通讯股份有限公司 一种vnfm容灾保护的方法、装置和nfvo
CN106664216A (zh) * 2015-06-30 2017-05-10 华为技术有限公司 一种切换vnf的方法和装置
WO2018137866A1 (en) * 2017-01-30 2018-08-02 Telefonaktiebolaget Lm Ericsson (Publ) Security anchor function in 5g systems

Family Cites Families (9)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN104284359B (zh) * 2014-06-17 2018-10-02 南京邮电大学 一种epc网络下跨地区容灾系统及控制方法
CN106332149A (zh) * 2015-06-25 2017-01-11 中兴通讯股份有限公司 Sgw故障的通信状态恢复方法及系统、mme、sgw
US11228949B2 (en) * 2017-01-06 2022-01-18 Samsung Electronics Co., Ltd. Intra-RAT handover for next generation system
CN108347727B (zh) * 2017-01-24 2023-04-07 中兴通讯股份有限公司 一种数据传输方法及装置
CN112492573A (zh) * 2017-02-21 2021-03-12 华为技术有限公司 一种选择会话管理功能实体的方法、装置和系统
CN107018542A (zh) * 2017-03-27 2017-08-04 中兴通讯股份有限公司 网络系统中状态信息的处理方法、装置及存储介质
CN111034238B (zh) * 2017-08-14 2023-06-06 瑞典爱立信有限公司 获得关于电信网络中的订户的用户订阅数据的方法
CN112534776B (zh) * 2018-08-09 2023-10-20 诺基亚技术有限公司 用于在网络环境中检测网络功能失败和重启的方法及装置
WO2020030292A1 (en) * 2018-08-10 2020-02-13 Nokia Technologies Oy Downlink signaling to user equipment in non-3gpp idle state

Patent Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN105577408A (zh) * 2014-09-25 2016-05-11 中兴通讯股份有限公司 一种vnfm容灾保护的方法、装置和nfvo
CN106664216A (zh) * 2015-06-30 2017-05-10 华为技术有限公司 一种切换vnf的方法和装置
WO2018137866A1 (en) * 2017-01-30 2018-08-02 Telefonaktiebolaget Lm Ericsson (Publ) Security anchor function in 5g systems

Non-Patent Citations (1)

* Cited by examiner, † Cited by third party
Title
NOKIA: "GUTI unique across AMFs in an AMF SET", 3GPP TSG-SA WG2 MEETING #126 S 2-182963, 2 March 2018 (2018-03-02), XP051408859 *

Cited By (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
JP2023538534A (ja) * 2020-08-10 2023-09-08 サムスン エレクトロニクス カンパニー リミテッド 無線通信システムの安定性を高める方法及び装置
JP7794523B2 (ja) 2020-08-10 2026-01-06 サムスン エレクトロニクス カンパニー リミテッド 無線通信システムの安定性を高める方法及び装置
JP2024521821A (ja) * 2021-05-28 2024-06-04 オラクル・インターナショナル・コーポレイション コアネットワークにおいてネットワーク機能（ｎｆ）高可用性（ｈａ）トポロジ情報を配布するための方法、システム、およびコンピュータ可読媒体
CN115915220A (zh) * 2021-09-30 2023-04-04 中国移动通信有限公司研究院 一种异常处理方法、设备及存储介质
JP2025501040A (ja) * 2021-12-30 2025-01-17 中興通訊股▲ふん▼有限公司 セッション管理機能障害および再選択後のセッション更新のための方法

Also Published As

Publication number Publication date
ES2965860T3 (es) 2024-04-17
CN110536330A (zh) 2019-12-03
EP3860189A4 (en) 2022-06-29
EP3860189B1 (en) 2023-11-08
JP7438202B2 (ja) 2024-02-26
EP3860189A1 (en) 2021-08-04
US12052588B2 (en) 2024-07-30
CA3114150A1 (en) 2020-04-02
KR102889893B1 (ko) 2025-11-21
EP3860189B8 (en) 2023-12-13
US20220014944A1 (en) 2022-01-13
CN116669083A (zh) 2023-08-29
JP2022502926A (ja) 2022-01-11
BR112021005801A2 (pt) 2021-06-29
KR20210064231A (ko) 2021-06-02
CN110536330B (zh) 2023-06-23

Similar Documents

Publication Publication Date Title
WO2020063876A1 (zh) Ue迁移方法、装置、系统及存储介质
US11711869B2 (en) Message and system for application function influence on traffic routing
CN110958718B (zh) 一种pdu会话重建方法、装置、系统及存储介质
CN110958719B (zh) Ue迁移方法、nrf、备用smf、系统及存储介质
CN103583063B (zh) 用于地理冗余网关处的故障恢复的系统和方法
US11343686B2 (en) Systems and methods for call session control function failover using dynamic routing techniques
CN109995844B (zh) 一种控制面资源迁移的实现方法、装置及网络功能实体
WO2012071695A1 (zh) 节点故障处理方法、系统及相关设备
CN115915220A (zh) 一种异常处理方法、设备及存储介质
CN108696902A (zh) 一种网络设备负载均衡的方法及装置
CA3114150C (en) Ue migration method, apparatus, system, and storage medium
CN118160371A (zh) 用于无线网络中核心网节点重新分配的方法、设备和系统
JP7721670B2 (ja) 通信障害を防ぐ方法
WO2011054270A1 (zh) 一种实现位置区域更新的方法及系统
EP4710544A1 (en) Method and apparatus for selecting an edge application server for a ue while taking into account mobility of the ue
CN118234053A (zh) 语音业务的建立方法、网络设备及存储介质

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 19866085

Country of ref document: EP

Kind code of ref document: A1

ENP Entry into the national phase

Ref document number: 3114150

Country of ref document: CA

ENP Entry into the national phase

Ref document number: 2021517185

Country of ref document: JP

Kind code of ref document: A

Ref document number: 20217009128

Country of ref document: KR

Kind code of ref document: A

NENP Non-entry into the national phase

Ref country code: DE

REG Reference to national code

Ref country code: BR

Ref legal event code: B01A

Ref document number: 112021005801

Country of ref document: BR

ENP Entry into the national phase

Ref document number: 2019866085

Country of ref document: EP

Effective date: 20210428

ENP Entry into the national phase

Ref document number: 112021005801

Country of ref document: BR

Kind code of ref document: A2

Effective date: 20210325