WO2023124635A1 - 信息处理方法、网元、存储介质及程序产品 - Google Patents

信息处理方法、网元、存储介质及程序产品 Download PDF

Info

Publication number
WO2023124635A1
WO2023124635A1 PCT/CN2022/132957 CN2022132957W WO2023124635A1 WO 2023124635 A1 WO2023124635 A1 WO 2023124635A1 CN 2022132957 W CN2022132957 W CN 2022132957W WO 2023124635 A1 WO2023124635 A1 WO 2023124635A1
Authority
WO
WIPO (PCT)
Prior art keywords
session
amf
network element
information
smf
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/CN2022/132957
Other languages
English (en)
French (fr)
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
Publication of WO2023124635A1 publication Critical patent/WO2023124635A1/zh
Anticipated expiration legal-status Critical
Ceased legal-status Critical Current

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W24/00—Supervisory, monitoring or testing arrangements
    • H04W24/02—Arrangements for optimising operational condition
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W24/00—Supervisory, monitoring or testing arrangements
    • H04W24/04—Arrangements for maintaining operational condition

Definitions

  • the present application relates to the technical field of communication, in particular to an information processing method, a network element, a storage medium and a program product.
  • AMF Access and Mobility Management Function
  • the session information between the terminal (User Equipment, UE) and the session management function network element (Session Management Function, SMF) is transparently transmitted by the AMF.
  • the standby AMF needs to send information about the standby AMF to the SMF. Since the AMF interacts with the SMF by updating the session management context message Update SM Context, the related technology will include the standby AMF in the Update SM Context message.
  • the backup AMF cannot notify the SMF of the disaster recovery switchover through the update session management context message, which will cause subsequent Unavailability or discontinuity of business.
  • Embodiments of the present application provide an information processing method, a network element, a computer storage medium, and a computer program product.
  • the embodiment of the present application provides an information processing method, which is applied to the second access and mobility management function network element AMF, and the method includes: after obtaining the message transmission request sent by the session management function network element SMF , and if no update session management context message is sent to the SMF according to the message transmission request, a session update request is sent to the SMF, so that the SMF updates the protocol data unit PDU session according to the session update request information; wherein, the message transmission request is used to enable the second AMF to take over the session of the first AMF; the information in the update protocol data unit session includes information corresponding to the first AMF in the PDU session The information corresponding to the second AMF is updated.
  • the embodiment of the present application also provides an information processing method, which is applied to the session management function network element SMF, and the method includes: sending a message transmission request to the second access and mobility management function network element AMF; receiving A session update request sent by the second AMF, wherein the session update request is sent by the second AMF without sending an update session management context message to the SMF according to the message transmission request; according to the session The update request updates the information in the protocol data unit PDU session; wherein, the message transmission request is used to enable the second AMF to take over the session of the first AMF; the update of the information in the PDU session includes combining the PDU session with the The information corresponding to the first AMF is updated to the information corresponding to the second AMF.
  • the embodiment of the present application further provides a network element, including: a memory, a processor, and a computer program stored in the memory and operable on the processor, and the processor implements the first step when executing the computer program.
  • a network element including: a memory, a processor, and a computer program stored in the memory and operable on the processor, and the processor implements the first step when executing the computer program.
  • the embodiment of the present application further provides a computer-readable storage medium storing computer-executable instructions, and the computer-executable instructions are used to execute the information processing method as described above.
  • the embodiment of the present application further provides a computer program product, including a computer program or a computer instruction, the computer program or the computer instruction is stored in a computer-readable storage medium, and the processor of the computer device reads from the The computer-readable storage medium reads the computer program or the computer instruction, and the processor executes the computer program or the computer instruction, so that the computer device executes the information processing method as described above.
  • FIG. 1 is a schematic diagram of a 5G system architecture provided by an embodiment of the present application.
  • FIG. 2 is a schematic diagram of a system structure in a disaster recovery switching scenario provided by an embodiment of the present application
  • FIG. 3 is a schematic flowchart of an information processing method for carrying standby AMF information provided by an embodiment of the present application
  • FIG. 4 is a schematic flow diagram of an information processing method in the case where the standby AMF does not send an update session management context message to the SMF according to a message transmission request provided by an embodiment of the present application;
  • FIG. 5 is a schematic flowchart of an information processing method provided by an embodiment of the present application.
  • FIG. 6 is a schematic flowchart of an information processing method provided by another embodiment of the present application.
  • FIG. 7 is a schematic structural diagram of session update request information provided by an embodiment of the present application.
  • FIG. 8 is a schematic structural diagram of a network element switching field provided by an embodiment of the present application.
  • Fig. 9 is a flow chart of judging SMF information update provided by one embodiment of the present application.
  • FIG. 10 is a schematic diagram of a network element structure provided by an embodiment of the present application.
  • the AMF since the AMF is the only mobile access point for the terminal, the session information between the terminal (User Equipment, UE) and the session management function network element (Session Management Function, SMF) is transparently transmitted by the AMF, namely When a session is established, AMF creates a session management context on SMF by invoking the service interface provided by SMF, and communicates between SMF and the terminal through the transparent transmission of service messages such as session management context creation and update in AMF.
  • UE User Equipment
  • SMF Session Management Function
  • the SMF needs to find The AMF corresponding to this session is transparently transmitted, therefore, the SMF needs to have real-time and accurate AMF information.
  • UDM Unified Data Management
  • Policy Control Function Policy Control Function
  • PCF Policy Control Function
  • the present application provides an information processing method, a network element, a computer-readable storage medium, and a computer program product.
  • Fig. 1 shows a schematic diagram of a 5G system architecture applicable to the embodiment of the present application, and each part involved in the network architecture will be described separately below.
  • User equipment 110 may include various handheld devices with wireless communication functions, vehicle-mounted devices, wearable devices, computing devices or other processing devices connected to wireless modems, as well as various forms of terminals, mobile stations (Mobile Station, MS) , terminal (terminal), UE, soft terminal, etc. For example, water meters, electricity meters, sensors, etc.
  • Radio Access Network, (R) AN) 120 also known as access network element: used to provide network access functions for authorized user equipment in a specific area, and can Demand, etc. use different quality transmission tunnels.
  • (R)AN can manage wireless resources, provide access services for user equipment, and then complete the forwarding of control signals and user equipment data between user equipment and the core network.
  • (R)AN can also be understood as a base station in a traditional network.
  • User plane network element 130 used for packet routing and forwarding and quality of service (Quality of Service, QoS) processing of user plane data, etc.
  • QoS Quality of Service
  • the user plane network element may be a user plane function (User Plane Function, UPF) network element.
  • UPF User Plane Function
  • the user plane network element may still be a UPF network element, or may have other names, which are not limited in this application.
  • Data network element 140 used to provide a network for transmitting data.
  • the data network element may be a data network (Data Network, DN) network element.
  • the data network element may still be a DN network element, or may have other names, which are not limited in this application.
  • Access management network element 150 mainly used for mobility management and access management, etc., and can be used to implement functions other than session management in the Mobility Management Entity (MME) function, for example, lawful interception and Access authorization/authentication and other functions.
  • MME Mobility Management Entity
  • the access management network element may be an access and mobility management function (Access and Mobility Management Function, AMF).
  • AMF Access and Mobility Management Function
  • the access management network element may still be an AMF, or may have other names, which are not limited in this application.
  • Session management network element 160 mainly used for session management, Internet Protocol (Internet Protocol, IP) address allocation and management of user equipment, selection of endpoints for manageable user plane functions, policy control and charging function interfaces, and downlink data notification wait.
  • Internet Protocol Internet Protocol, IP
  • the session management network element may be a session management function (Session Management Function, SMF) network element.
  • SMF Session Management Function
  • the session management network element may still be an SMF network element, or may have other names, which are not limited in this application.
  • Policy control network element 170 a unified policy framework for guiding network behavior, providing policy rule information and the like for control plane function network elements (such as AMF, SMF network elements, etc.).
  • the policy control network element may be a policy control function (Policy Control Function, PCF) network element.
  • Policy Control Function Policy Control Function
  • the policy control network element may still be a PCF network element, or may have other names, which are not limited in this application.
  • Authentication server 180 used for authentication services, generating keys to implement two-way authentication on user equipment, and supporting a unified authentication framework.
  • the authentication server may be an authentication server function (Authentication Server Function, AUSF) network element.
  • AUSF Authentication Server Function
  • the authentication server functional network element may still be an AUSF network element, or may have other names, which are not limited in this application.
  • Data management network element 190 used for processing user equipment identification, access authentication, registration and mobility management, etc.
  • the data management network element can be a unified data management (Unified Data Management, UDM) network element; in the future communication system, the unified data management network element can still be a UDM network element, or it can also have other names , which is not limited in this application.
  • UDM Unified Data Management
  • Application network element 1100 used for data routing influenced by applications, accessing network opening function network elements, and interacting with policy frameworks for policy control, etc.
  • the application network element may be an application function (Application Function, AF) network element.
  • AF Application Function
  • the application network element may still be an AF network element, or may have other names, which are not limited in this application.
  • Network storage network element used to maintain real-time information of all network function services in the network.
  • the network storage network element may be a network registration function (Network Repository Function, NRF) network element.
  • NRF Network Repository Function
  • the network storage network element may still be an NRF network element, or may have other names, which are not limited in this application.
  • the foregoing network element or function may be a network element in a hardware device, or a software function running on dedicated hardware, or a virtualization function instantiated on a platform (for example, a cloud platform).
  • the access management network element is an AMF network element
  • the data management network element is a UDM network element
  • the session management network element is an SMF network element
  • the user plane network element is a UPF network element.
  • the terminal 110 accesses the network through the access network element 120, and the terminal communicates with the AMF network element 150 through the next generation network (Nextgeneration, N) N1 interface (N1 for short);
  • the access network element 120 communicates with the AMF network element 150 through the N2 interface (abbreviated as N2) communicate with AMF network element 150, communicate with UPF network element 130 through N3 interface (abbreviated as N3);
  • AMF network element 150 communicates with SMF network element 160 through N11 interface (abbreviated as N11), and communicate with UDM through N8 interface (abbreviated as N8)
  • Network element 190 communicates with PCF network element 170 through N15 interface (abbreviated as N15); different AMF network elements 150 communicate through N14 interface (abbreviated as N14);
  • SMF network element 160 communicates with UPF network element through N4 interface (abbreviated as N4)
  • the element 130 communicates with the UDM network element 190 through the N10 interface (N10 for short), and communicates with the
  • the name of the interface between network elements in FIG. 1 is just an example. In various actual implementations, the name of the interface may be another name, which is not limited in this embodiment of the present application.
  • control plane network elements such as AMF network elements, SMF network elements, PCF network elements, or UDM network elements in the 5G network shown in Figure 1 can also use service interfaces to interact.
  • the service interface provided by the AMF network element can be Namf
  • the service interface provided by the SMF network element can be Nsmf
  • the service interface provided by the PCF network element can be Npcf
  • the service interface provided by the UDM network element Can be Nudm etc.
  • 5G system architecture 5G system architecture
  • the access network element, SMF network element, AMF network element, UPF network element, UDM network element, or PCF network element in Figure 1 is just a name, and the name does not constitute a limitation on the device itself.
  • network elements or entities corresponding to access network elements, SMF network elements, AMF network elements, UPF network elements, UDM network elements, or PCF network elements can also have other names.
  • This embodiment of the present application does not limit it.
  • the UPF network element may also be replaced by a UPF or a UPF entity, etc., which will be described in a unified manner here, and will not be described in detail below.
  • the system architecture described in the embodiments of the present application is to illustrate the technical solutions of the embodiments of the present application more clearly, and does not constitute a limitation on the technical solutions provided by the embodiments of the present application.
  • Those skilled in the art know that with the evolution of network topology and For the emergence of new application scenarios, the technical solutions provided by the embodiments of the present application are also applicable to similar technical problems.
  • Figure 2 is a schematic diagram of the system structure under the disaster recovery switching scenario provided by an embodiment of the present application, which describes that the current AMF network element stops working due to equipment failure, power outage, natural disaster, etc., and is operated by the AMF POOL
  • the standby AMF network element takes over the work of its mobility management and access management.
  • the system includes AMF POOL, NRF network element 220, SMF network element 230, UPF network element 240, UDM network element 250, and PCF network element 260.
  • the network storage function network element (Network Repository Function, NRF) 220 finds its failure through heartbeat detection, so it notifies the SMF 230 that the current AMF1211 fails, and then the SMF 230 is performing When doing business, another AMF will be selected from the AMF POOL to take over the PDU session according to the active and standby configuration information of the AMF, that is, the standby AMF2 212 continues the business process of the current session.
  • NRF Network Repository Function
  • the AMF network element When the standby AMF2 212 takes over the current session successfully, the AMF network element must inform the SMF of some key information of the AMF2 212, such as the AMF logo, (Globally Unique AMF Identifier, GUAMI), callback URI, etc., and update the PDU of the SMF In the session context, so that the normal execution of subsequent business processes, and the above process is called disaster recovery switching. Therefore, whether the standby AMF2 212 can notify the SMF of the key information of the standby AMF will solve whether the follow-up business can be normally performed.
  • some key information of the AMF2 212 such as the AMF logo, (Globally Unique AMF Identifier, GUAMI), callback URI, etc.
  • NRF discovers the failure of AMF1 through heartbeat detection, and NRF initiates a heartbeat to AMF1 message, AMF1 has timed out and has not responded; NRF sends a heartbeat message to AMF1 until the heartbeat timeout reaches the maximum number, so NRF considers that AMF1 is down, and the disaster recovery switching process starts.
  • Step S301 The NRF network element that finds the fault notifies the SMF network element that AMF1 is currently faulty and cannot provide services.
  • Step S302 The PCF network element initiates a session update request to the SMF network element, and the SMF network element also sends a session update response to the PCF network element according to the session update request of the PCF network element.
  • Step S303 The SMF finds that AMF1 is faulty, and selects a backup AMF.
  • AMF2 is selected as the standby AMF for subsequent communication.
  • the SMF since the PCF triggers the SMF to update the session and gets a response from the SMF, the SMF initiates an SM policy update process at an appropriate time to obtain a new policy in real time. Subsequently, when SMF sends a N1N2 Message Transfer (N1N2 Message Transfer) request to AMF2, it will carry session update information, so AMF2 responds to the session update request and sends a session update message request to SMF in the subsequent business process.
  • N1N2 Message Transfer N1N2 Message Transfer
  • steps S304 to S309 including the following steps.
  • Step S304 the SMF sends the N1N2 message transmission request, and correspondingly, the AMF2 receives the N1N2 message transmission request from the SMF.
  • Step S305 AMF2 sends a N1N2Transfer response, and correspondingly, the SMF receives the N1N2 message transfer response from AMF2.
  • Step S306 AMF2 pulls the PDU session context.
  • the N1N2 message transmission request carries the PDU session identifier
  • AMF2 can obtain the PDU session context corresponding to the identifier from the database UDSF according to the PDU session identifier, and complete the takeover of the AMF1 session.
  • Step S307 AMF2 sends a session update request (N1N2 update response).
  • Step S308 The update message carries the key information of the standby AMF along with it, and updates to the SMF PDU session context.
  • Step S309 the SMF sends a session update response.
  • the AMF information related to AMF2 will be sent to SMF incidentally through the session update request; after receiving the session update request, SMF parses out the key information related to AMF , and then update the new AMF information to the original SMF PDU session context to complete the whole process of disaster recovery switching.
  • Fig. 4 is a schematic flowchart of an information processing method provided by an embodiment of the present application under the condition that the standby AMF does not send an update session management context message to the SMF. As shown in Figure 4, the following steps are included.
  • Step S401 The NRF network element that finds the fault notifies the SMF network element that the current AMF1 is faulty and cannot provide services.
  • Step S402 The UPF network element initiates paging to the SMF network element, and the SMF network element also sends a paging response according to the paging of the UPF network element.
  • Step S403 The SMF finds that AMF1 is faulty, and selects a backup AMF.
  • AMF2 is selected as the standby AMF for subsequent communication.
  • steps S404 to S407 including the following steps.
  • Step S404 the SMF sends the N1N2 message transmission request, and correspondingly, the AMF2 receives the N1N2 message transmission request from the SMF.
  • Step S405 AMF2 sends a N1N2Transfer response, and correspondingly, the SMF receives the N1N2 message transfer response from AMF2.
  • Step S406 AMF2 pulls the PDU session context.
  • the N1N2 message transmission request carries the PDU session identifier
  • AMF2 can obtain the PDU session context corresponding to the identifier from the database UDSF according to the PDU session identifier, and complete the takeover of the AMF1 session.
  • Step S407 There is no subsequent session update message in this scenario, and the key information of AMF2 cannot be updated to the session context of SMF.
  • an embodiment of the present application proposes an information processing method as shown in FIG. 5 , which includes the following steps as shown in the figure.
  • Step S501 The NRF network element that finds the fault notifies the SMF network element that the current AMF1 is faulty and cannot provide services.
  • Step S502 the PCF network element initiates a session update request to the SMF network element, and the SMF network element also sends a session update response to the PCF network element according to the session update request of the PCF network element.
  • Step S503 The SMF finds that AMF1 is faulty, and reselects a standby AMF.
  • AMF2 is selected as the standby AMF for subsequent communication.
  • the SMF since the PCF triggers the SMF to update the session and gets a response from the SMF, the SMF initiates an SM policy update process at an appropriate time to obtain a new policy in real time.
  • the session update request in this embodiment has a field of network element handover information and a field of target access management information, which can help the SMF quickly determine whether to use The received AMF2 information is updated.
  • steps S504 to S509 including the following steps.
  • Step S504 the SMF sends an N1N2 message transmission request, and correspondingly, AMF2 receives the N1N2 message transmission request from the SMF.
  • Step S505 AMF2 sends a N1N2Transfer response, and correspondingly, the SMF receives the N1N2 message transfer response from AMF2.
  • Step S506 AMF2 pulls the PDU session context.
  • the N1N2 message transmission request carries the PDU session identifier
  • AMF2 can obtain the PDU session context corresponding to the identifier from the database UDSF according to the PDU session identifier, and complete the takeover of the AMF1 session.
  • Step S507 AMF2 sends a session update request.
  • the session update request includes network element handover information and target access management information.
  • the network element switching information is used to identify that the AMF of the service terminal has been switched from the first AMF to the second AMF
  • the target access management information includes the second management information used to identify the identity of the second AMF.
  • the network element switching information is filled by the network element switching field
  • the target access management information is filled by the target access management field, as shown in FIG.
  • the session update request is sent to the SMF for updating the corresponding information in the SMF.
  • the NE switching field includes the following fields: variable name, data type, whether the parameter is required, and cardinality.
  • the network element switching field adopts the structure shown in FIG. 8.
  • the network element switching field includes the variable name RecoveryToBeSwitched, the data type boolean Boolean, whether the parameter needs to be C, and the base is 0..1.
  • the data value is True, it means that the AMF has been switched from the active AMF1 to the standby AMF2 due to the disaster recovery switchover; when the data value is False, it means that the disaster recovery switchover has not occurred, and there is no switchover between the active and standby AMFs.
  • the network element switching information can represent whether a disaster recovery switching has occurred in the AMF. Therefore, its data type is not limited to the Boolean type. Any data type and corresponding data value that can transmit information on whether a disaster recovery switching has occurred can constitute the implementation of this application. Example provided session update request.
  • the network element switching information can be carried by extending the Update SM Context signaling, or by using the original vacant position in the Update SM Context signaling.
  • the target access management field can include AMF identification information, global mobile management network element identification information, and callback unified resource identification information. These information can identify the identity of the standby AMF, ensuring that the SMF can update these information to achieve correct transmission of subsequent service information .
  • the target access management field includes an AMF ID field and a globally unique AMF identifier (Globally Unique AMF Identifier, GUAMI) field.
  • GUAMI Globally Unique AMF Identifier
  • the target access management field can also include AMF network elements The region identifier, the group identifier of the AMF network element, the AMF pointer identifier, etc.
  • Step S508 According to the network element switching information, update the key information field of the standby AMF to the SMF PDU session context.
  • SMF after receiving the session update request sent by AMF2, SMF analyzes the content, obtains the network element switching information and target access management information of AMF2, and according to the above information, updates the session The context is updated.
  • Step S509 The SMF sends a session update response.
  • the information processing method provided by the embodiment of the present application not only transmits AMF2-related information through a redefined session update request, but also defines a new network element handover field to Indicates whether the AMF has been switched, helps the SMF to quickly identify the AMF disaster recovery switchover scenario, facilitates the business processing of the SMF, ensures the normal operation of the business, and guarantees the quality of service.
  • FIG. 6 provides another typical application scenario during disaster recovery switching, as shown in the figure, including the following steps.
  • NRF discovered the failure of AMF1 through heartbeat detection. NRF sent a heartbeat message to AMF1, but AMF1 did not respond after a timeout. NRF sent a heartbeat message to AMF1 until the heartbeat timeout reached the maximum number. Therefore, NRF believed that AMF1 was down, and the disaster recovery switching process started.
  • Step S601 the NRF notifies the SMF AMF1 of failure.
  • Step S602 PCF initiates session release.
  • Step S603 The SMF sends a bearer delete request.
  • the SMF since the PCF instructs session release, the SMF sends a bearer delete request to the UPF.
  • Step S604 The UPF sends a delete bearer response.
  • the UPF upon receiving the bearer delete request sent by the SMF, the UPF sends a bearer delete response to the SMF.
  • Step S605 The SMF finds that the AMF1 is faulty, and reselects a standby AMF.
  • AMF2 is selected as the standby AMF for subsequent communication.
  • Step S606 The SMF sends a N1N2Transfer request.
  • Step S607 AMF sends N1N2Transfer response.
  • the SMF will notify the AMF to release the session, but since the state of the terminal UE is CM-IDLE, that is, the idle state, and the N1N2 message transmission request carries the "skip indicator" field, Therefore, the follow-up AMF2 will not interact with the terminal UE or RAN, which will cause the Update SM Context to not be issued in related technologies.
  • Step S608 AMF fetches PDU session context.
  • the N1N2 message transmission request carries the PDU session identifier
  • AMF2 can obtain the PDU session context corresponding to the identifier from the database UDSF according to the PDU session identifier, and complete the takeover of the AMF1 session.
  • Step S609 AMF sends a session update request.
  • the AMF will send a session update request, and carry the AMF used to identify the service terminal in the session update request.
  • the network element switching information can represent whether a disaster recovery switching has occurred in the AMF. Therefore, its data type is not limited to the Boolean type. Any data type and corresponding data value that can transmit information on whether a disaster recovery switching has occurred can constitute the implementation of this application. Example provided session update request.
  • the network element switching information can be carried by extending the Update SM Context signaling, or by using the original vacant position in the Update SM Context signaling.
  • the target access management field can include AMF identification information, global mobile management network element identification information, and callback unified resource identification information. These information can identify the identity of the standby AMF, ensuring that the SMF can update these information to achieve correct transmission of subsequent service information .
  • the target access management field includes the AMF ID field, the GUAMI field, and the callback URI.
  • Step S610 The SMF saves the key information (callback URI) of the standby AMF to the PDU session context.
  • Step S611 SMF sends a session update response.
  • Step S612 the SMF notifies the AMF to release the session.
  • the SMF uses the latest notification callback URI of AMF2 to send a notification message to AMF2 to release the session, which ensures the continuity of the service.
  • Figure 9 can illustrate the working principle and beneficial effects of the network element switching field. As shown in Figure 9, when the SMF receives the session update request sent by AMF2, it will analyze the network element switching field and its value.
  • the data type of the network element switching field is Boolean.
  • the data value of the network element switching field is 1, it means that the network element switching is True, that is, it is currently a disaster recovery switching scenario, and the AMF serving the terminal has been replaced by the AMF1 Switch to AMF2, so based on this scenario, SMF needs to update the AMF information in the session context it manages to ensure the smooth progress of subsequent services; when it detects that the data value carried in the network element switching field is 0, it means If there is no disaster recovery switchover, the AMF network element does not change, so there is no need to update the AMF information in the session context it manages.
  • the presence of the network element switching field can quickly distinguish the session update request in the embodiment of the present application from the Update SM Context in the related technology, so that SMF can quickly identify whether it is a disaster recovery switching scene at present, which improves the performance of SMF in AMF disaster recovery.
  • Service processing efficiency in switching scenarios ensures service continuity.
  • the network element switching information can represent whether the disaster recovery switchover has occurred in the AMF. Therefore, its data type is not limited to the Boolean type, any data type that can transmit the disaster recovery switchover information and the corresponding data value Both may constitute the session update request provided by the embodiment of the present application.
  • an embodiment of the present application also provides a network element 1000, the network element includes a processor 1010, a memory 1020, a receiver 1030 and a transmitter 1040, the receiver 1030 can receive information sent by other network elements, and the transmitter 1040 can send information to other network elements, and the memory 1020 stores a computer program capable of executing the above information processing method.
  • the method steps S505 to S507 in FIG. 5 and the method steps S607 to S609 in FIG. 6 described above are executed.
  • the method steps S504, S508 to S509 in FIG. 5 and the method steps S606, S610 to S612 in FIG. 6 described above are executed.
  • an embodiment of the present application also provides a computer-readable storage medium, the computer-readable storage medium stores computer-executable instructions, and the computer-executable instructions are executed by a processor or a controller, for example, by the above-mentioned Execution by a processor in the embodiment of the network device can cause the processor to execute the information processing method in the above embodiment, for example, execute the method steps S503 to S509 in FIG. 5 and the method steps S605 to S605 in FIG. 6 described above. S612.
  • an embodiment of the present application also provides a computer program product, including a computer program or a computer instruction, the computer program or the computer instruction is stored in a computer-readable storage medium, and the processor of the computer device reads the computer program from the computer-readable storage medium.
  • a computer program or computer instruction is taken, and the processor executes the computer program or computer instruction, so that the computer device executes the above information processing method, for example, executes the method steps S503 to S509 in FIG. 5 and the method steps in FIG. 6 described above S605 to S612.
  • the embodiment of the present application includes: when the second AMF obtains the message transmission request sent by the session management function network element SMF, and does not send the update session management context message to the SMF according to the message transmission request, the second AMF sends a session update to the SMF Request, so that the SMF updates the information in the protocol data unit PDU session according to the session update request; wherein, the message transmission request is used to make the second AMF take over the session of the first AMF; updating the information in the protocol data unit session includes combining the PDU session with the The information corresponding to the first AMF is updated to the information corresponding to the second AMF.
  • the standby AMF in the scenario of AMF disaster recovery switching, and the standby AMF and SMF do not interact through the update session management context message, the standby AMF can send the message carrying the message corresponding to the standby AMF to the SMF.
  • a session update request for relevant information enables the SMF to complete the information update, thereby ensuring the continuity of subsequent services.
  • Computer storage media includes, but is not limited to, RAM, ROM, EEPROM, flash memory or other memory technology, CD-ROM, digital versatile disk (DVD) or other optical disk storage, magnetic cartridges, tape, magnetic disk storage or other magnetic storage devices, or can Any other medium used to store desired information and which can be accessed by a computer.
  • communication media typically embodies computer readable instructions, data structures, program modules, or other data in a modulated data signal such as a carrier wave or other transport mechanism, and may include any information delivery media .

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Mobile Radio Communication Systems (AREA)
  • Computer And Data Communications (AREA)

Abstract

本申请实施例提供了一种信息处理方法、网元、计算机存储介质及计算机程序产品，该信息处理方法应用于第二接入和移动性管理功能网元AMF，该方法包括：在获取到会话管理功能网元SMF发送的消息传输请求，并且没有根据该消息传输请求向该SMF发送更新会话管理上下文消息的情况下，向该SMF发送会话更新请求，使得该SMF根据该会话更新请求更新协议数据单元PDU会话中的信息。其中，该消息传输请求用于使该第二AMF接管第一AMF的会话；该更新协议数据单元会话中的信息包括将该PDU会话中与该第一AMF对应的信息更新为与该第二AMF对应的信息。

Description

信息处理方法、网元、存储介质及程序产品
相关申请的交叉引用
本申请基于申请号为202111609504.X，申请日为2021年12月27日的中国专利申请提出，并要求该中国专利申请的优先权，该中国专利申请的全部内容在此引入本申请作为参考。
技术领域
本申请涉及通信技术领域，尤其是一种信息处理方法、网元、存储介质及程序产品。
背景技术
在目前的第五代通信技术(5th Generation，5G)的系统架构中，为了防止由于设备故障、停电、自然灾害等原因导致接入和移动性管理功能网元(Access and Mobility Management Function，AMF)网络服务中断情况的发生，相关技术提供了AMF POOL容灾方案，即通过在多个不同地域分别部署多套AMF形成AMF POOL，实现在当前AMF设备不可用时，从AMF POOL中选择备用的AMF设备接管当前业务。
目前，在相关技术中，由于AMF是终端唯一的移动接入点，因此终端(User Equipment，UE)与会话管理功能网元(Session Management Function，SMF)之间的会话信息由AMF透传。在AMF容灾场景下，备用AMF需要向SMF发送备用AMF相关信息，由于AMF会通过更新会话管理上下文消息Update SM Context与SMF进行交互，因此，相关技术中会在Update SM Context消息中顺带备用AMF信息以通知SMF进行了容灾倒换，但是，当备用AMF与SMF之间没有通过更新会话管理上下文消息进行交互时，备用AMF无法通过更新会话管理上下文消息通知SMF进行了容灾倒换，将导致后续业务的不可用或者不连续。
发明内容
以下是对本文详细描述的主题的概述。本概述并非是为了限制权利要求的保护范围。
本申请实施例提供了一种信息处理方法、网元、计算机存储介质及计算机程序产品。
第一方面，本申请实施例提供了一种信息处理方法，应用于第二接入和移动性管理功能网元AMF，所述方法包括：在获取到会话管理功能网元SMF发送的消息传输请求，并且没有根据所述消息传输请求向所述SMF发送更新会话管理上下文消息的情况下，向所述SMF发送会话更新请求，使得所述SMF根据所述会话更新请求更新协议数据单元PDU会话中的信息；其中，所述消息传输请求用于使所述第二AMF接管第一AMF的会话；所述更新协议数据单元会话中的信息包括将所述PDU会话中与所述第一AMF对应的信息更新为与所述第二AMF对应的信息。
第二方面，本申请实施例还提供了一种信息处理方法，应用于会话管理功能网元SMF，所述方法包括：向第二接入和移动性管理功能网元AMF发送消息传输请求；接收所述第二AMF发送的会话更新请求，其中，所述会话更新请求由所述第二AMF没有根据所述消息传输请求向所述SMF发送更新会话管理上下文消息的情况下发送；根据所述会话更新请求更新协议数据单元PDU会话中的信息；其中，所述消息传输请求用于使所述第二AMF接管第一AMF的会话；所述更新PDU会话中的信息包括将所述PDU会话中与所述第一AMF对应的信息更新为与所述第二AMF对应的信息。
第三方面，本申请实施例还提供了一种网元，包括：存储器、处理器及存储在存储器上并可在处理器上运行的计算机程序，所述处理器执行所述计算机程序时实现第一方面所述的信息处理方法，或者实现如上第二方面所述的信息处理方法。
第四方面，本申请实施例还提供了一种计算机可读存储介质，存储有计算机可执行指令，所述计算机可执行指令用于执行如上所述的信息处理方法。
第五方面，本申请实施例还提供了一种计算机程序产品，包括计算机程序或计算机指令，所述计算机程序或所述计算机指令存储在计算机可读存储介质中，计算机设备的处理器从所述计算机可读存储介质读取所述计算机程序或所述计算机指令，所述处理器执行所述计算机程序或所述计算机指令，使得所述计算机设备执行如上所述的信息处理方法。
本申请的其它特征和优点将在随后的说明书中阐述，并且，部分地从说明书中变得显而易见，或者通过实施本申请而了解。本申请的目的和其他优点可通过在说明书、权利要求书以及附图中所特别指出的结构来实现和获得。
附图说明
附图用来提供对本申请技术方案的理解，并且构成说明书的一部分，与本申请的实施例一起用于解释本申请的技术方案，并不构成对本申请技术方案的限制。
图1是本申请一个实施例提供的5G系统架构示意图；
图2是本申请一个实施例提供的容灾倒换场景下的系统结构示意图；
图3是本申请一个实施例提供的随路携带备用AMF信息的信息处理方法的流程示意图；
图4是本申请一个实施例提供的备用AMF没有根据消息传输请求向SMF发送更新会话管理上下文消息的情况下信息处理方法的流程示意图；
图5是本申请一个实施例提供的信息处理方法的流程示意图；
图6是本申请另一个实施例提供的信息处理方法的流程示意图；
图7是本申请一个实施例提供的会话更新请求信息的结构示意图；
图8是本申请一个实施例提供的网元切换字段的结构示意图；
图9是本申请一个实施例提供的SMF信息更新的判断流程图；
图10是本申请一个实施例提供的网元结构示意图。
具体实施方式
为了使本申请的目的、技术方案及优点更加清楚明白，以下结合附图及实施例，对本申请进行详细说明。应当理解，此处所描述的实施例仅用以解释本申请，并不用于限定本申请。
虽然在流程图中示出了逻辑顺序，但是在某些情况下，可以以不同于流程图中的顺序执行所示出或描述的步骤。说明书和权利要求书及上述附图中的术语“第一”、“第二”等是用于区别类似的对象，而不必用于描述特定的顺序或先后次序。
目前，在相关技术中，由于AMF是终端唯一的移动接入点，因此终端(User Equipment，UE)与会话管理功能网元(Session Management Function，SMF)之间的会话信息由AMF透传，即会话在建立时，AMF通过调用SMF提供的服务接口在SMF上创建会话管理上下文，并通过会话管理上下文的创建、更新等服务消息在AMF的透传实现SMF与终端之间的通信。因此，当来自SMF自身或统一数据管理功能网元(Unified Data Management，UDM)、策略控制功能网元(Policy Control Function，PCF)等网元触发SMF对会话进行修改或释放时，就需要SMF找到此会话对应的AMF进行透传，因此，SMF需要具有即时准确的AMF信息。而 在AMF容灾场景下，负责接入和透传的AMF发生变化，而变化的AMF信息如果没有在SMF处得到更新，将导致业务的不可用或者不连续。相关技术中会在更新会话管理上下文Update SM Context消息中顺带备用AMF信息以通知SMF进行了容灾倒换，但是，当AMF与SMF之间没有通过Update SM Context消息进行交互时，备用AMF无法通过更新会话管理上下文消息通知SMF进行了容灾倒换。
基于此，本申请提供了一种信息处理方法、网元、计算机可读存储介质及计算机程序产品。
图1示出了适用于本申请实施例的一种5G系统架构示意图，下面对该网络架构中涉及的各个部分分别进行说明。
用户设备110：可以包括各种具有无线通信功能的手持设备、车载设备、可穿戴设备、计算设备或连接到无线调制解调器的其它处理设备，以及各种形式的终端，移动台(Mobile Station，MS)，终端(terminal)，UE，软终端等。例如，水表、电表、传感器等。
(无线)接入网络(Radio Access Network，(R)AN)120(又称接入网网元)：用于为特定区域的授权用户设备提供入网功能，并能够根据用户设备的级别，业务的需求等使用不同质量的传输隧道。
(R)AN能够管理无线资源，为用户设备提供接入服务，进而完成控制信号和用户设备数据在用户设备和核心网之间的转发，(R)AN也可以理解为传统网络中的基站。
用户面网元130：用于分组路由和转发以及用户面数据的服务质量(Quality of Service，QoS)处理等。
在5G通信系统中，该用户面网元可以是用户面功能(User Plane Function，UPF)网元。在未来通信系统中，用户面网元仍可以是UPF网元，或者，还可以有其它的名称，本申请不做限定。
数据网络网元140：用于提供传输数据的网络。
在5G通信系统中，该数据网络网元可以是数据网络(Data Network，DN)网元。在未来通信系统中，数据网络网元仍可以是DN网元，或者，还可以有其它的名称，本申请不做限定。
接入管理网元150：主要用于移动性管理和接入管理等，可以用于实现移动性管理实体(Mobility Management Entity，MME)功能中除会话管理之外的其它功能，例如，合法监听以及接入授权/鉴权等功能。
在5G通信系统中，该接入管理网元可以是接入和移动性管理功能(Access and Mobility Management Function，AMF)。在未来通信系统中，接入管理网元仍可以是AMF，或者，还可以有其它的名称，本申请不做限定。
会话管理网元160：主要用于会话管理、用户设备的网络互连协议(Internet Protocol，IP)地址分配和管理、选择可管理用户平面功能、策略控制和收费功能接口的终结点以及下行数据通知等。
在5G通信系统中，该会话管理网元可以是会话管理功能(Session Management Function，SMF)网元。在未来通信系统中，会话管理网元仍可以是SMF网元，或者，还可以有其它的名称，本申请不做限定。
策略控制网元170：用于指导网络行为的统一策略框架，为控制面功能网元(例如AMF，SMF网元等)提供策略规则信息等。
在5G通信系统中，该策略控制网元可以是策略控制功能(Policy Control Function，PCF)网元。在未来通信系统中，策略控制网元仍可以是PCF网元，或者，还可以有其它的名称，本申请不做限定。
认证服务器180：用于鉴权服务、产生密钥实现对用户设备的双向鉴权，支持统一的鉴权框架。
在5G通信系统中，该认证服务器可以是认证服务器功能(Authentication Server Function，AUSF)网元。在未来通信系统中，认证服务器功能网元仍可以是AUSF网元，或者，还可以有其它的名称，本申请不做限定。
数据管理网元190：用于处理用户设备标识，接入鉴权，注册以及移动性管理等。
在5G通信系统中，该数据管理网元可以是统一数据管理(Unified Data Management，UDM)网元；在未来通信系统中，统一数据管理仍可以是UDM网元，或者，还可以有其它的名称，本申请不做限定。
应用网元1100：用于进行应用影响的数据路由，接入网络开放功能网元，与策略框架交互进行策略控制等。
在5G通信系统中，该应用网元可以是应用功能(Application Function，AF)网元。在未来通信系统中，应用网元仍可以是AF网元，或者，还可以有其它的名称，本申请不做限定。
网络存储网元：用于维护网络中所有网络功能服务的实时信息。
在5G通信系统中，该网络存储网元可以是网络注册功能(Network Repository Function，NRF)网元。在未来通信系统中，网络存储网元仍可以是NRF网元，或者，还可以有其它的名称，本申请不做限定。
上述网元或者功能既可以是硬件设备中的网络元件，也可以是在专用硬件上运行软件功能，或者是平台(例如，云平台)上实例化的虚拟化功能。为方便说明，本申请后续，以接入管理网元为AMF，数据管理网元为UDM网元，会话管理网元为SMF网元，用户面网元为UPF网元为例进行说明。其中，终端110通过接入网网元120接入网络，并且终端通过下一代网络(Nextgeneration，N)N1接口(简称N1)与AMF网元150通信；接入网网元120通过N2接口(简称N2)与AMF网元150通信，通过N3接口(简称N3)与UPF网元130通信；AMF网元150通过N11接口(简称N11)与SMF网元160通信，通过N8接口(简称N8)与UDM网元190通信，通过N15接口(简称N15)与PCF网元170通信；不同的AMF网元150之间通过N14接口(简称N14)通信；SMF网元160通过N4接口(简称N4)与UPF网元130通信，通过N10接口(简称N10)与UDM网元190通信，通过N7接口(简称N7)与PCF网元170通信；不同的UPF网元130之间通过N9接口(简称N9)通信；UPF网元130通过N6接口(简称N6)接入数据网络网元140。
图1中的各个网元之间的接口名字只是一个示例，在各种实际的实现中接口名字可能为其他名字，本申请实施例对此不作限定。
此外，图1所示的5G网络中的AMF网元、SMF网元、PCF网元或者UDM网元等控制面网元也可以采用服务化接口进行交互。比如，AMF网元对外提供的服务化接口可以为Namf；SMF网元对外提供的服务化接口可以为Nsmf；PCF网元对外提供的服务化接口可以为Npcf；UDM网元对外提供的服务化接口可以为Nudm等。相关描述可以参考23501标准中的5G系统架构(5G system architecture)图，在此不予赘述。
图1中的接入网网元、SMF网元、AMF网元、UPF网元、UDM网元或者PCF网元等仅是一个名字，名字对设备本身不构成限定。在5G网络以及未来其它的网络中，接入网网元、SMF网元、AMF网元、UPF网元、UDM网元或者PCF网元等所对应的网元或实体也可以是其他的名字，本申请实施例对此不作限定。例如，该UPF网元还有可能被替换为UPF或者UPF实体等，在此进行统一说明，以下不再赘述。
本申请实施例描述的系统架构是为了更加清楚的说明本申请实施例的技术方案，并不构成对于本申请实施例提供的技术方案的限定，本领域技术人员可知，随着网络拓扑的演变和新应用场景的出现，本申请实施例提供的技术方案对于类似的技术问题，同样适用。
基于上述系统架构，下面提出本申请的信息处理方法的各个实施例。
如图2所示，图2是本申请一个实施例提供的容灾倒换场景下的系统结构示意图，描述了在当前AMF网元由于设备故障、停电、自然灾害等停止工作，而由AMF POOL中的备用AMF网元接替其移动性管理和接入管理的工作。
如图所示，系统包括AMF POOL、NRF网元220、SMF网元230、UPF网元240、UDM网元250、PCF网元260。
在一个实施方式中，当前AMF1 211在发生故障后，网络仓储功能网元(Network Repository Function，NRF)220通过心跳检测发现了其故障，因此通知SMF 230当前AMF1211发生故障，随后，SMF 230在进行业务时会根据AMF的主备配置信息从AMF POOL选择另一个AMF接管PDU会话，即备用AMF2 212继续当前会话的业务流程。当备用AMF2 212接管当前会话成功后，AMF网元必须将该AMF2 212的一些关键信息，例如AMF标识、(Globally Unique AMF Identifier，GUAMI)、回调URI等的变化告知SMF，并更新到SMF的PDU会话上下文中，以便后续业务流程的正常执行，而以上过程称之为容灾倒换。因此，备用AMF2 212是否能够将备用AMF的关键信息通知给SMF，将解决了后续业务是否能够正常执行。
为了更加详细地说明容灾倒换的步骤及相关技术中的信息处理方法，提供如图3所示的实施例，如图3所示，NRF通过心跳检测发现了AMF1的故障，NRF向AMF1发起心跳消息，AMF1超时未响应；NRF向AMF1发起心跳消息，直到心跳超时达到最大次数，因此NRF认为AMF1宕机，容灾倒换流程开启。
步骤S301：发现故障的NRF网元通知SMF网元，当前AMF1发生故障，无法提供服务。
步骤S302：PCF网元向SMF网元发起了会话更新请求，且SMF网元根据PCF网元的会话更新请求，也发送了会话更新响应给PCF网元。
步骤S303：SMF发现AMF1故障，并进行备用AMF的选取。
在当前实施例中，选择了AMF2作为备用AMF进行后续通信。
在当前这种业务场景下，由于PCF触发SMF进行会话更新，且得到了SMF的响应，因此，SMF在适当时机发起SM策略更新过程以实时获取新的策略。随后，SMF在向AMF2发送N1N2消息传输(N1N2 Message Transfer)请求时，会携带有会话更新的信息，因此AMF2响应该会话更新请求，在后续的业务流程中发送会话更新消息请求给SMF。
以上场景通过步骤S304至S309得以体现，包括以下步骤。
步骤S304：SMF发送N1N2消息传输请求，相应的，AMF2接收来自SMF的N1N2消息传输请求。
步骤S305：AMF2发送N1N2Transfer响应，相应的，SMF接收来自AMF2的N1N2消息传 输响应。
步骤S306：AMF2拉取PDU会话上下文。
在当前实施例中，N1N2消息传输请求中携带有PDU会话标识，AMF2能够根据PDU会话标识，从数据库UDSF获取标识对应的PDU会话上下文，完成对AMF1会话的接管。
步骤S307：AMF2发送会话更新请求(N1N2更新响应)。
步骤S308：更新消息随路携带备用AMF的关键信息，更新到SMF PDU会话上下文。
步骤S309：SMF发送会话更新响应。
在当前实施例中，由于AMF2主动发送了会话更新请求，因此与AMF2相关的AMF信息将通过会话更新请求，顺带被发送给SMF；SMF在接收到会话更新请求后，解析出AMF相关的关键信息，再将这些新的AMF信息更新到原有的SMF PDU会话上下文中，完成容灾倒换的全流程。
在图3对应的实施例中，由于当前流程在AMF发生容灾倒换后，后续有Update SM Context信令交互时，就通过后继信令顺带将上述备用AMF关键信息通知SMF更新上下文，实现了信息的顺利交互，保证后续业务得以连续。
图4本申请一个实施例提供的备用AMF没有向SMF发送更新会话管理上下文消息的情况下信息处理方法的流程示意图。如图4所示，包括以下步骤。
步骤S401：发现故障的NRF网元通知SMF网元，当前AMF1发生故障，无法提供服务。
步骤S402：UPF网元向SMF网元发起了寻呼，且SMF网元根据UPF网元的寻呼，也发送了寻呼响应。
步骤S403：SMF发现AMF1故障，并进行备用AMF的选取。
在当前实施例中，选择了AMF2作为备用AMF进行后续通信。
在当前这种业务场景下，由于并未有网元触发SMF进行会话更新，因此，后续就不会存在AMF与SMF之间的Update SM Context进行信息交互，即在AMF接收到SMF发送的消息传输请求后，没有根据此消息传输请求，而对应发送更新会话管理上下文消息的会话更新请求。
以上场景通过步骤S404至S407得以体现，包括以下步骤。
步骤S404：SMF发送N1N2消息传输请求，相应的，AMF2接收来自SMF的N1N2消息传输请求。
步骤S405：AMF2发送N1N2Transfer响应，相应的，SMF接收来自AMF2的N1N2消息传输响应。
步骤S406：AMF2拉取PDU会话上下文。
在当前实施例中，N1N2消息传输请求中携带有PDU会话标识，AMF2能够根据PDU会话标识，从数据库UDSF获取标识对应的PDU会话上下文，完成对AMF1会话的接管。
步骤S407：此场景后续没有会话更新消息，AMF2的关键信息无法更新到SMF的会话上下文。
在当前实施例中，由于SMF没有获取到最新的AMF相关信息，因此也没有办法通过Update SM Context更新会话上下文以维护正确的会话管理信令路径，导致后续业务的不连续。
为了解决上述实施例产生的问题，本申请一实施例提出了图5所示的信息处理方法，如图所示，包括以下步骤。
步骤S501：发现故障的NRF网元通知SMF网元，当前AMF1发生故障，无法提供服务。
步骤S502：PCF网元向SMF网元发起了会话更新请求，且SMF网元根据PCF网元的会话更新请求，也发送了会话更新响应给PCF网元。
步骤S503：SMF发现AMF1故障，并进行备用AMF重选。
在当前实施例中，选择了AMF2作为备用AMF进行后续通信。
在当前这种业务场景下，由于PCF触发SMF进行会话更新，且得到了SMF的响应，因此，SMF在适当时机发起SM策略更新过程以实时获取新的策略。相比于图3实施例中利用更新消息随路携带AMF2信息实现信息更新，本实施例的会话更新请求具有网元切换信息的字段与目标接入管理信息字段，能够帮助SMF快速判断是否要根据接收到的AMF2信息进行更新。
以上场景通过步骤S504至S509得以体现，包括以下步骤。
步骤S504：SMF发送N1N2消息传输请求，相应的，AMF2接收来自SMF的N1N2消息传输请求。
步骤S505：AMF2发送N1N2Transfer响应，相应的，SMF接收来自AMF2的N1N2消息传输响应。
步骤S506：AMF2拉取PDU会话上下文。
在当前实施例中，N1N2消息传输请求中携带有PDU会话标识，AMF2能够根据PDU会话标识，从数据库UDSF获取标识对应的PDU会话上下文，完成对AMF1会话的接管。
步骤S507：AMF2发送会话更新请求。
在一些实施例中，会话更新请求包括网元切换信息与目标接入管理信息。其中，网元切换信息用于标识服务终端的AMF已由第一AMF切换为第二AMF，目标接入管理信息包括用于标识第二AMF的身份的第二管理信息。
在一些实施例中，网元切换信息由网元切换字段填充，目标接入管理信息由目标接入管理字段填充，如图7所示，同时携带有网元切换字段和目标接入管理字段的会话更新请求被发送给SMF，用于SMF中对应信息的更新。
网元切换字段包含以下字段：变量名称、数据类型、参数是否需要以及基数。
在图5对应的实施例中，网元切换字段采用如图8所示的结构，如图所示，网元切换字段包含变量名称RecoveryToBeSwitched，数据类型boolean布尔型，参数是否需要为C，基数为0..1。当数据值为True时，即表示因为容灾倒换，AMF已由主用AMF1切换为备用AMF2；当数据值为False时，即表示容灾倒换没有发生，主备AMF之间没有发生切换。
网元切换信息是能够表征AMF是否发生了容灾倒换，因此，其数据类型不限于采用布尔型，任何能够传递是否发生容灾倒换信息的数据类型及对应的数据取值均可以构成本申请实施例提供的会话更新请求。
网元切换信息可以通过对Update SM Context信令扩展后携带，或者，利用Update SM Context信令中原有的空余位置携带。
目标接入管理字段为可以包括AMF标识信息、全球移动管理网元标识信息、回调统一资源标识信息，这些信息可以标识备用AMF的身份，保证SMF可以通过更新这些信息来实现后续业务信息的正确发送。
在图5对应的实施例中，目标接入管理字段包含了AMF ID字段与全局唯一AMF标识(Globally Unique AMF Identifier，GUAMI)字段。
在网络中有多个AMF，但是网络能够支持的AMF组标识和AMF指针不足，这时需要在不 同的区域复用AMF组标识和AMF指针，因此，目标接入管理字段也可以包括AMF网元所在区域标识、AMF网元所在组标识、AMF指针标识等。
步骤S508：根据网元切换信息，更新备用AMF的关键信息字段到SMF PDU会话上下文。
在图5对应的实施例中，SMF接收AMF2发送的会话更新请求后，对其中的内容进行解析，得到AMF2的网元切换信息与目标接入管理信息，并根据上述信息，对自身管理的会话上下文进行更新。
步骤S509：SMF发送会话更新响应。
区别于图3实施例中采用更新消息随路携带AMF2的相关信息，本申请实施例提供的信息处理方法不仅通过重新定义的会话更新请求传递AMF2相关信息，更通过定义全新网元切换字段，来指示AMF是否发生了切换，帮助SMF快速识别AMF容灾倒换场景，方便SMF的业务处理，保证业务能够正常运行，保证了服务质量。
图6提供了容灾倒换时的另一种典型应用场景，如图所示，包括以下步骤。
NRF通过心跳检测发现了AMF1的故障，NRF向AMF1发起心跳消息，AMF1超时未响应；NRF向AMF1发起心跳消息，直到心跳超时达到最大次数，因此NRF认为AMF1宕机，容灾倒换流程开启。
步骤S601：NRF通知SMF AMF1故障。
步骤S602：PCF发起会话释放。
步骤S603：SMF发送删除承载请求。
在本实施例中，由于PCF指示会话释放，因此SMF向UPF发送删除承载请求。
步骤S604：UPF发送删除承载响应。
在本实施例中，接收到SMF发送的删除承载请求，UPF发送删除承载响应给SMF。
步骤S605：SMF发现AMF1故障，进行备用AMF重选。
在本实施例中，选择了AMF2作为备用AMF进行后续通信。
步骤S606：SMF发送N1N2Transfer请求。
步骤S607：AMF发送N1N2Transfer响应。
由于本实施例中，PCF触发了会话释放，因此SMF会通知AMF进行会话释放，但是由于终端UE的状态为CM-IDLE，即空闲状态，且N1N2消息传输请求中携带有“skip indicator”字段，因此后续AMF2不会与终端UE或者RAN有交互的流程，就会导致相关技术中，Update SM Context不会发出。
步骤S608：AMF拉取PDU会话上下文。
在本实施例中，N1N2消息传输请求中携带有PDU会话标识，AMF2能够根据PDU会话标识，从数据库UDSF获取标识对应的PDU会话上下文，完成对AMF1会话的接管。
步骤S609：AMF发送会话更新请求。
区别于相关技术中没有发出的Update SM Context消息，本申请实施例提供的信息处理方法中，AMF会发出会话更新请求，并在会话更新请求中携带用于标识服务终端的AMF已由第一AMF切换为第二AMF的网元切换信息，以及，用于标识第二AMF的身份的目标接入管理信息。
网元切换信息是能够表征AMF是否发生了容灾倒换，因此，其数据类型不限于采用布尔型，任何能够传递是否发生容灾倒换信息的数据类型及对应的数据取值均可以构成本申请实 施例提供的会话更新请求。
网元切换信息可以通过对Update SM Context信令扩展后携带，或者，利用Update SM Context信令中原有的空余位置携带。
目标接入管理字段为可以包括AMF标识信息、全球移动管理网元标识信息、回调统一资源标识信息，这些信息可以标识备用AMF的身份，保证SMF可以通过更新这些信息来实现后续业务信息的正确发送。
在图6对应的实施例中，目标接入管理字段包含了AMF ID字段、GUAMI字段以及回调统一资源标识信息callback URI。
步骤S610：SMF将备用AMF的关键信息(回调URI)保存到PDU会话上下文。
步骤S611：SMF发送会话更新响应。
步骤S612：SMF通知AMF释放会话。
在本实施例中，SMF使用最新的AMF2的通知回调URI发送通知消息给AMF2释放会话，保证了业务的连续性。
图9能够说明网元切换字段的工作原理与有益效果，如图9所示，SMF在收到AMF2发送的会话更新请求时，会解析得到其中网元切换字段及其数值。
在一些实施例中，网元切换字段的数据类型为布尔型，当检测到其数据值为1时，表示网元切换为True，即当前为容灾倒换场景，服务于终端的AMF已经由AMF1切换为AMF2，因此基于此场景，SMF需要对其管理的会话上下文中的AMF信息进行更新，以保证后续业务的顺利进行；当检测到网元切换字段中携带的数据值为0时，则表示没有发生容灾倒换，那么AMF网元没有发生变化，因此无需对其管理的会话上下文中的AMF信息进行更新。网元切换字段的存在能够将本申请实施例中的会话更新请求与相关技术中的Update SM Context快速区分开，使SMF能够快速识别出当前是否为容灾倒换场景，提高了SMF在AMF容灾倒换场景下的业务处理效率，保证了业务的连续性。
本领域技术人员应当知晓，网元切换信息能够表征AMF是否发生了容灾倒换，因此，其数据类型不限于采用布尔型，任何能够传递是否发生容灾倒换信息的数据类型及对应的数据取值均可以构成本申请实施例提供的会话更新请求。
此外，本申请的一个实施例还提供了一种网元1000，该网元包括处理器1010，存储器1020，接收器1030以及发送器1040，接收器1030能够接收其他网元发送的信息，发送器1040能够发送信息给其他网元，存储器1020上存储有能够执行上述信息处理方法的计算机程序。
在一实施例中，当网元为AMF网元时，执行以上描述的图5中的方法步骤S505至S507，图6中的方法步骤S607至S609。
在一实施例中，当网元为SMF网元时，执行以上描述的图5中的方法步骤S504、S508至S509，图6中的方法步骤S606、S610至S612。
此外，本申请的一个实施例还提供了一种计算机可读存储介质，该计算机可读存储介质存储有计算机可执行指令，该计算机可执行指令被一个处理器或控制器执行，例如，被上述网络设备实施例中的一个处理器执行，可使得上述处理器执行上述实施例中的信息处理方法，例如，执行以上描述的图5中的方法步骤S503至S509、图6中的方法步骤S605至S612。
此外，本申请实施例还提供了一种计算机程序产品，包括计算机程序或计算机指令，计算机程序或所述计算机指令存储在计算机可读存储介质中，计算机设备的处理器从计算机可 读存储介质读取计算机程序或计算机指令，处理器执行所述计算机程序或计算机指令，使得计算机设备执行如上的信息处理方法，例如，执行以上描述的图5中的方法步骤S503至S509、图6中的方法步骤S605至S612。
本申请实施例包括：第二AMF在获取到会话管理功能网元SMF发送的消息传输请求，并且没有根据消息传输请求向SMF发送更新会话管理上下文消息的情况下，第二AMF向SMF发送会话更新请求，使得SMF根据会话更新请求更新协议数据单元PDU会话中的信息；其中，消息传输请求用于使第二AMF接管第一AMF的会话；更新协议数据单元会话中的信息包括将PDU会话中与第一AMF对应的信息更新为与第二AMF对应的信息。
根据本申请实施例提供的方案，能够在AMF容灾切换的场景下，且备用AMF与SMF之间没有通过更新会话管理上下文消息进行交互时，由备用AMF向SMF发送携带有与备用AMF对应的相关信息的会话更新请求，使SMF完成信息更新，从而保证后续业务的连续性。
本领域普通技术人员可以理解，上文中所公开方法中的全部或某些步骤、系统可以被实施为软件、固件、硬件及其适当的组合。某些物理组件或所有物理组件可以被实施为由处理器，如中央处理器、数字信号处理器或微处理器执行的软件，或者被实施为硬件，或者被实施为集成电路，如专用集成电路。这样的软件可以分布在计算机可读介质上，计算机可读介质可以包括计算机存储介质(或非暂时性介质)和通信介质(或暂时性介质)。如本领域普通技术人员公知的，术语计算机存储介质包括在用于存储信息(诸如计算机可读指令、数据结构、程序模块或其他数据)的任何方法或技术中实施的易失性和非易失性、可移除和不可移除介质。计算机存储介质包括但不限于RAM、ROM、EEPROM、闪存或其他存储器技术、CD-ROM、数字多功能盘(DVD)或其他光盘存储、磁盒、磁带、磁盘存储或其他磁存储装置、或者可以用于存储期望的信息并且可以被计算机访问的任何其他的介质。此外，本领域普通技术人员公知的是，通信介质通常包含计算机可读指令、数据结构、程序模块或者诸如载波或其他传输机制之类的调制数据信号中的其他数据，并且可包括任何信息递送介质。
以上是对本申请的若干实施方式进行了说明，但本申请并不局限于上述实施方式，熟悉本领域的技术人员在不违背本申请精神的前提下还可作出种种的等同变形或替换，这些等同的变形或替换均包含在本申请权利要求所限定的范围内。

Claims (12)

  1. 一种信息处理方法，应用于第二接入和移动性管理功能网元AMF，所述方法包括：
    在获取到会话管理功能网元SMF发送的消息传输请求，并且没有根据所述消息传输请求向所述SMF发送更新会话管理上下文消息的情况下，向所述SMF发送会话更新请求，使得所述SMF根据所述会话更新请求更新协议数据单元PDU会话中的信息；
    其中，所述消息传输请求用于使所述第二AMF接管第一AMF的会话；所述更新协议数据单元会话中的信息包括将所述PDU会话中与所述第一AMF对应的信息更新为与所述第二AMF对应的信息。
  2. 根据权利要求1所述的方法，其中，所述向所述SMF发送会话更新请求，包括：
    根据所述消息传输请求，构建会话更新请求，所述会话更新请求包括网元切换信息与目标接入管理信息；其中，所述网元切换信息用于标识服务终端的AMF已由所述第一AMF切换为所述第二AMF；所述目标接入管理信息包括用于标识所述第二AMF的身份的第二管理信息；
    向所述SMF发送包括所述网元切换信息和所述目标接入管理信息的所述会话更新请求。
  3. 根据权利要求2所述的方法，其中，所述会话更新请求包括网元切换字段和目标接入管理字段，所述构建会话更新请求，包括：
    构建所述网元切换字段和所述目标接入管理字段；
    将所述网元切换信息填充到所述网元切换字段；
    将所述目标接入管理信息填充到所述目标接入管理字段；
    根据填充有所述网元切换信息的所述网元切换字段和填充有所述目标接入管理信息的所述目标接入管理字段，得到所述会话更新请求。
  4. 根据权利要求3所述的方法，其中，所述没有根据所述消息传输请求向所述SMF发送更新会话管理上下文消息，包括：
    当检测到终端处于空闲状态，且所述消息传输请求中包括skip indicator字段，确定不根据所述消息传输请求向所述SMF发送更新会话管理上下文消息。
  5. 根据权利要求2至4任一项所述的方法，其中，所述第二管理信息包括AMF标识信息、全球移动管理网元标识信息、回调统一资源标识信息。
  6. 根据权利要求1所述的方法，其中，在获取到会话管理功能网元SMF发送的消息传输请求后，所述方法还包括：
    根据所述消息传输请求，获取第一会话的第一会话标识；所述第一会话为注册在所述第一AMF下，且在切换后被所述第二AMF接管的会话；
    根据所述第一会话标识，从数据库中获取所述第一会话标识对应的第一会话上下文信息；
    根据所述第一会话上下文信息接管所述第一会话。
  7. 一种信息处理方法，应用于会话管理功能网元SMF，所述方法包括：
    向第二接入和移动性管理功能网元AMF发送消息传输请求；
    接收所述第二AMF发送的会话更新请求，其中，所述会话更新请求由所述第二AMF没有根据所述消息传输请求向所述SMF发送更新会话管理上下文消息的情况下发送；
    根据所述会话更新请求更新协议数据单元PDU会话中的信息；
    其中，所述消息传输请求用于使所述第二AMF接管第一AMF的会话；所述更新PDU会话 中的信息包括将所述PDU会话中与所述第一AMF对应的信息更新为与所述第二AMF对应的信息。
  8. 根据权利要求7所述的方法，其中，所述会话更新请求包括网元切换信息与目标接入管理信息；其中，所述网元切换信息用于标识服务终端的AMF已由所述第一AMF切换为所述第二AMF；所述目标接入管理信息包括能够标识所述第二AMF的身份的第二管理信息。
  9. 根据权利要求8所述的方法，其中，所述将所述PDU会话中与所述第一AMF对应的信息更新为与所述第二AMF对应的信息，包括：
    将所述PDU会话中的第一管理信息更新为所述第二管理信息；其中，所述第一管理信息为能够标识所述第一AMF的身份的接入和移动性管理信息。
  10. 根据权利要求8或9所述的方法，其中，所述第二管理信息包括AMF标识信息、全球移动管理网元标识信息、回调统一资源标识信息。
  11. 一种网元，包括：存储器、处理器及存储在存储器上并可在处理器上运行的计算机程序，其中，所述处理器执行所述计算机程序时实现如权利要求1至10中任意一项所述的信息处理方法。
  12. 一种计算机可读存储介质，存储有计算机可执行指令，其中，所述计算机可执行指令用于执行如权利要求1至10中任意一项所述的信息处理方法。
PCT/CN2022/132957 2021-12-27 2022-11-18 信息处理方法、网元、存储介质及程序产品 Ceased WO2023124635A1 (zh)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN202111609504.X 2021-12-27
CN202111609504.XA CN113993147B (zh) 2021-12-27 2021-12-27 信息处理方法、网元、存储介质及程序产品

Publications (1)

Publication Number Publication Date
WO2023124635A1 true WO2023124635A1 (zh) 2023-07-06

Family

ID=79734516

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2022/132957 Ceased WO2023124635A1 (zh) 2021-12-27 2022-11-18 信息处理方法、网元、存储介质及程序产品

Country Status (2)

Country Link
CN (1) CN113993147B (zh)
WO (1) WO2023124635A1 (zh)

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2026051980A1 (zh) * 2024-09-09 2026-03-12 华为技术有限公司 一种通信方法及装置

Families Citing this family (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN113993147B (zh) * 2021-12-27 2022-04-22 中兴通讯股份有限公司 信息处理方法、网元、存储介质及程序产品
CN116193481A (zh) * 2023-02-07 2023-05-30 京信网络系统股份有限公司 一种5g核心网处理方法、装置、设备及介质
CN116744352A (zh) * 2023-06-28 2023-09-12 中国联合网络通信集团有限公司 网络容灾方法、装置及存储介质
CN118972887A (zh) * 2024-09-30 2024-11-15 南京泰通科技股份有限公司 一种5gc异地部署的灾备方法、系统及存储介质

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN108990117A (zh) * 2017-06-01 2018-12-11 华为技术有限公司 一种会话处理方法及相关设备
CN110662213A (zh) * 2018-06-29 2020-01-07 中兴通讯股份有限公司 移动性管理方法、融合amf、基站、新空口和存储介质
WO2020168275A1 (en) * 2019-02-14 2020-08-20 Apple Inc. Registration management in information centric networking for next generation cellular networks
CN113993147A (zh) * 2021-12-27 2022-01-28 中兴通讯股份有限公司 信息处理方法、网元、存储介质及程序产品

Family Cites Families (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN109996345B (zh) * 2017-12-29 2021-03-30 华为技术有限公司 会话建立方法、设备及系统
CN110913437B (zh) * 2018-09-14 2021-01-29 华为技术有限公司 通信方法和网元
CN111417151B (zh) * 2020-03-27 2021-10-08 广州爱浦路网络技术有限公司 一种5g核心网中备份amf的方法及其系统
CN113950058B (zh) * 2020-07-17 2025-05-16 华为技术有限公司 通信方法和装置

Patent Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN108990117A (zh) * 2017-06-01 2018-12-11 华为技术有限公司 一种会话处理方法及相关设备
US20190199802A1 (en) * 2017-06-01 2019-06-27 Huawei Technologies Co.,Ltd. Session processing method and related device
CN110662213A (zh) * 2018-06-29 2020-01-07 中兴通讯股份有限公司 移动性管理方法、融合amf、基站、新空口和存储介质
WO2020168275A1 (en) * 2019-02-14 2020-08-20 Apple Inc. Registration management in information centric networking for next generation cellular networks
CN113993147A (zh) * 2021-12-27 2022-01-28 中兴通讯股份有限公司 信息处理方法、网元、存储介质及程序产品

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2026051980A1 (zh) * 2024-09-09 2026-03-12 华为技术有限公司 一种通信方法及装置

Also Published As

Publication number Publication date
CN113993147B (zh) 2022-04-22
CN113993147A (zh) 2022-01-28

Similar Documents

Publication Publication Date Title
US12015682B2 (en) Service subscription method and system for reporting service change in communication system
EP4191959B1 (en) Method and system for ensuring service level agreement of an application
WO2023124635A1 (zh) 信息处理方法、网元、存储介质及程序产品
US20240422520A1 (en) Event notification method, apparatus and storage medium
US12556612B2 (en) Session establishment method and apparatus
EP3989462A1 (en) Clock drift processing method, network function network elements, and storage medium
US20210337372A1 (en) Methods, Network Function Nodes and Computer Readable Media for Event Subscription Management
WO2020225241A1 (en) Communication network component and method for handling a service request
WO2021147687A1 (zh) 一种通信的方法及装置和系统
WO2020096564A1 (en) Method and system for supporting multiple fully separated network slices
CN120130122A (zh) 智能策略规则更新
CN114071554B (zh) 一种事件通知方法、装置和系统
US20250240700A1 (en) Communication method, apparatus, and system
CN113259924B (zh) 一种私网签约信息更新方法及装置
EP4366344A1 (en) Address service entity selection method and apparatus, and electronic device and readable storage medium
EP4470271B1 (en) Support for simultaneous edge application server (eas) connectivity in application context relocation (acr)
CN114982311A (zh) 数据关闭方法、装置、设备及存储介质
WO2023148124A1 (en) Session management for redundant pdu sessions
US20260095821A1 (en) Methods, network function nodes and computer readable media for event report management
EP4307826A1 (en) Method for safeguarding against communication failure
US20240023182A1 (en) Handling the unknown rrc establishment cause value in nr
WO2026067552A1 (zh) 一种通信方法、装置和系统
WO2022233463A1 (en) Communication network arrangement and method for providing a communication service
CN118695356A (zh) 服务管理方法、装置、核心网网元及终端
CN120786387A (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: 22913893

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 22913893

Country of ref document: EP

Kind code of ref document: A1