Session processing methods, electronic devices and storage media

By introducing CMF network elements to handle some PDU session tasks, the problem of low processing efficiency of AMF network elements is solved, the functional decomposition and service-oriented architecture of AMF network elements are realized, and the efficiency of PDU session processing and user session experience are improved.

CN123124123APending Publication Date: 2026-11-17ZTE CORP
View PDF 0 Cites 0 Cited by

Patent Information

Application Number
CN202510632622.4
Authority / Receiving Office
CN · China
Patent Type
Applications(China)
Current Assignee / Owner
Filing Date
2025-05-15
Publication Date
2026-11-17

AI Technical Summary

Technical Problem

In the 5G core network architecture, the AMF network element suffers from low PDU session processing efficiency due to handling high-frequency NAS signaling forwarding and complex PDU session state management tasks, which affects the user session experience.

Method used

The connection management function (CMF) network element is introduced to handle some PDU session-related tasks, receive user terminal establishment requests and process PDU sessions, reduce the load on the AMF network element, and realize the functional decomposition and service-oriented approach of the AMF network element.

Benefits of technology

By receiving and processing PDU session establishment tasks through the CMF network element, the load on the AMF network element is reduced, the efficiency of PDU session processing is improved, and the user session experience is enhanced.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN123124123A_ABST
    Figure CN123124123A_ABST
Patent Text Reader

Abstract

This application provides a session processing method, electronic device, and storage medium applied to a Connection Management Function (CMF) network element. The CMF network element can be established based on the functional decomposition of the AMF network element and can handle some PDU session-related tasks. The method includes: receiving an establishment request sent by a user terminal; wherein the establishment request is used to instruct the CMF network element to establish a Protocol Data Unit (PDU) session corresponding to the user terminal. This application uses the CMF network element to receive and process the PDU session establishment task of the user terminal, thereby reducing the load on the AMF network element, enabling the decomposition of the AMF network element, further service-oriented processing, improving the processing efficiency of PDU sessions, and enhancing the user's session experience.
Need to check novelty before this filing date? Find Prior Art

Description

Technical Field

[0001] The embodiments of this application relate to, but are not limited to, the field of communication technology, and in particular to a session processing method, an electronic device, and a storage medium. Background Technology

[0002] In the 5G core network (5GC) architecture, the AMF (Access and Mobility Management Function) network element is one of the core network elements of the control plane, responsible for user terminal (UE) access authentication, mobility management, and the establishment and maintenance of session connections. The AMF network element is a key hub for 5G to achieve flexible access and efficient mobility, fully embodying the service-oriented architecture (SBA), cloud-native, and stateless concepts of the 5G core network.

[0003] In related technologies, the AMF (Access Default Server) network element, as the first network node for user / base station access to the core network, needs to forward a large number of non-access NAS (NAS) messages (such as handover requests and UE context transmissions). The AMF itself is also responsible for managing the Protocol Data Unit (PDU) sessions corresponding to the user terminal, including the full lifecycle maintenance of session establishment, modification, and release, as well as the dynamic allocation of session resources and QoS policy enforcement. This centralized control plane processing mechanism requires the AMF to simultaneously handle high-frequency NAS signaling forwarding and complex PDU session state management tasks. When faced with high-frequency processing demands, this can easily lead to low PDU session processing efficiency, affecting the user's session experience. Summary of the Invention

[0004] This application provides a session processing method, an electronic device, and a storage medium.

[0005] On one hand, embodiments of this application provide a session processing method applied to a connection management function (CMF) network element, the method comprising:

[0006] The system receives an establishment request sent by a user terminal; wherein the establishment request is used to instruct the CMF network element to establish a Protocol Data Unit (PDU) session corresponding to the user terminal.

[0007] On the other hand, embodiments of this application also provide a session processing method applied to an AMF network element, the method comprising:

[0008] Receive context information of the PDU session sent by the CMF network element;

[0009] Store the context information.

[0010] On the other hand, embodiments of this application also provide a session processing method applied to an SMF network element, the method comprising:

[0011] Receive the AMF identifier sent by the CMF network element;

[0012] Based on the AMF identifier, determine the AMF address information of the corresponding AMF network element;

[0013] When downlink data is confirmed to have arrived, a notification message is sent to the AMF network element based on the AMF address information; wherein, the notification message is used to trigger the AMF network element to initiate paging.

[0014] On the other hand, embodiments of this application also provide an electronic device, including: at least one processor; at least one memory for storing at least one program; at least one of the programs is executed by at least one of the processors to perform the session processing method as described above.

[0015] On the other hand, embodiments of this application also provide a computer-readable storage medium storing computer-executable instructions for performing the session processing method as described above.

[0016] On the other hand, embodiments of this application also provide a computer program product, including a computer program or computer instructions, wherein the computer program or computer instructions are stored in a computer-readable storage medium, and a processor of an electronic device reads the computer program or computer instructions from the computer-readable storage medium and executes the computer program or computer instructions, causing the electronic device to perform the session processing method as described above.

[0017] This application provides a session processing method, electronic device, and storage medium applied to a Connection Management Function (CMF) network element. The CMF network element can be established based on the functional decomposition of the AMF network element and can handle some PDU session-related tasks. The method includes: receiving an establishment request sent by a user terminal; wherein the establishment request is used to instruct the CMF network element to establish a Protocol Data Unit (PDU) session corresponding to the user terminal. This application uses the CMF network element to receive and process the PDU session establishment task of the user terminal, thereby reducing the load on the AMF network element, enabling the decomposition of the AMF network element, further service-oriented processing, improving the processing efficiency of PDU sessions, and enhancing the user's session experience. Attached Figure Description

[0018] Figure 1 This diagram illustrates a communication system architecture in the related technologies;

[0019] Figure 2A schematic diagram of a communication system architecture provided in an embodiment of this application is shown;

[0020] Figure 3 A flowchart of a session processing method provided in an embodiment of this application is shown;

[0021] Figure 4 A flowchart of another session processing method provided in an embodiment of this application is shown;

[0022] Figure 5 This illustration shows an interactive diagram of a user terminal during the initial registration process, according to an embodiment of this application.

[0023] Figure 6 This illustration shows an interaction diagram of a user terminal during the PDU session establishment process, according to an embodiment of this application.

[0024] Figure 7 This illustration shows an interaction diagram of a user terminal during the interface release process according to an embodiment of this application;

[0025] Figure 8 This illustration shows an interactive diagram of a user terminal activating a PDU session during connection reconstruction, according to an embodiment of this application.

[0026] Figure 9 This illustration shows an interactive diagram of reconstructing a user terminal's network connection and activating a PDU session via paging, according to an embodiment of this application. Detailed Implementation

[0027] To make the objectives, technical methods, and advantages of this application clearer, the following detailed description is provided in conjunction with the accompanying drawings and embodiments. It should be understood that the specific embodiments described herein are merely illustrative and not intended to limit the scope of this application.

[0028] It should be noted that although the flowchart shows a logical order, in some cases, the steps shown or described may be executed in a different order than that shown in the flowchart. In the description of the specification, claims, and the above-mentioned figures, "multiple" means two or more; "greater than," "less than," and "exceeding" are understood to exclude the stated number; "above," "below," and "within" are understood to include the stated number. The use of terms such as "first" and "second" is merely for distinguishing technical features and should not be construed as indicating or implying relative importance, or implicitly specifying the number of indicated technical features or their sequential relationship. Furthermore, in the description of the specification, claims, and the above-mentioned figures, the various values ​​mentioned (such as first value, second value, etc.) can be flexibly represented as single numeric codes or enumerated type values. These values ​​can clearly guide and control the execution flow and behavior patterns of various functional modules, ensuring the efficiency of decoding or encoding.

[0029] In the 5G core network (5GC) architecture, the AMF (Access and Mobility Management Function) network element is one of the core network elements of the control plane, responsible for user terminal (UE) access authentication, mobility management, and the establishment and maintenance of session connections.

[0030] Specifically, the main functions of the current AMF network element include the following:

[0031] 1. User Registration Management:

[0032] User registration: The AMF network element handles the UE registration process, verifies the UE's identity, and assigns a temporary identifier to it.

[0033] User deregistration: When a UE leaves the network or switches to another access network, the AMF network element is responsible for managing the deregistration process.

[0034] 2. Connection Management:

[0035] Connection establishment and release: The AMF network element is responsible for establishing and releasing the connection between the UE and the network.

[0036] Mobility management in connected mode: When the UE is in a connected state, the AMF network element manages its handover between different base stations.

[0037] 3. Mobility Management:

[0038] Idle Mode Mobility Management: When the UE is in an idle state, the AMF network element tracks its location and determines the most suitable base station for connection.

[0039] Connectivity-mode mobility management: The AMF network element handles mobility events of the UE in connected mode, such as handover between base stations.

[0040] 4. Safety Management:

[0041] Authentication and authorization: The AMF network element is responsible for UE authentication and authorization, ensuring that only legitimate users can access the network.

[0042] Security Context Management: The AMF network element maintains the NAS (Non-Access Stratum) security context for each UE to ensure the integrity and confidentiality of NAS message communication.

[0043] 5. Session Management:

[0044] Session establishment and release: The AMF network element is responsible for establishing, modifying and releasing communication sessions between the UE and the SMF (Session Management Function) network element.

[0045] AMF network elements are key hubs for 5G to achieve flexible access and efficient mobility, and they fully embody the concepts of service-oriented architecture (SBA), cloud-native architecture, and statelessness of the 5G core network.

[0046] In related technologies, the AMF network element is responsible for maintaining the UE's non-access NAS security context. All NAS messages between the UE and the core network (such as registration, authentication, and session management requests) must pass through the AMF network element. Moreover, the AMF network element is the control plane entry point for the base station (gNB) to access the core network. All NAS messages between the base station and the core network (such as handover requests and UE context transmissions) must be forwarded through the AMF network element.

[0047] For example, please refer to Figure 1 , Figure 1 A schematic diagram of a communication system architecture in related technologies is shown. Figure 1 The communication system in the text is a 5G system, and the specific details of its various nodes or network functions are as follows:

[0048] UE (User Equipment): This refers to the user. The UE accesses the RAN through the Uu interface and the AMF network element of the core network through the N1 interface.

[0049] RAN (Radio Access Network): Also known as a wireless base station, it is responsible for resource allocation of the Uu interface and access control of the UE.

[0050] AMF (Access and Mobility Management function): Manages user access to the network and is responsible for UE-to-network NAS (Non-Access Stratum) signaling management, user mobility management, and other functions. Its main functions include user registration management, connection management, mobility management, security management, and session management.

[0051] UDM (Unified Data Management): is the permanent storage location for user subscription data, located within the user's home network.

[0052] SMF (Session Management Function): Manages user PDU (Packet Data Unit) sessions and QoS flows, and formulates packet detection and forwarding rules for UPF network elements; SMF network elements are configured locally, or receive session policy control rules from PCF network elements, and the policy control rules control the data transmission path and QoS policy between UPF network elements and UE.

[0053] UPF (User Plane Function): Based on the rules issued by the SMF network element, it is responsible for functions such as routing and forwarding IP data and non-IP data, and reporting usage.

[0054] PCF (Policy Control Function): Based on user subscriptions, application requirements, and local configuration, it provides session policy rules to SMF network elements. Simultaneously, PCF network elements can also send URSP rules to the UE through AMF network elements, controlling the UE to generate appropriate PDU session parameters according to different application requests.

[0055] NRF (Network Repository Function): Primarily responsible for the registration, discovery, management, and configuration of Network Functions (NFs). By managing NF registration and discovery, NRF elements support the dynamic deployment and optimization of 5G networks, enabling the adjustment of network resources based on real-time demands.

[0056] Data Network: A network that provides services to users through the user plane. Users access the data network through PDU sessions.

[0057] Depend on Figure 1As can be seen, the AMF (Access Default Server) element, as the first network node for user / base station access to the core network, needs to forward a large number of non-access NAS (NAS) messages (such as handover requests and UE context transmissions). The AMF element itself is also responsible for managing the Protocol Data Unit (PDU) sessions corresponding to the user terminal, including the full lifecycle maintenance of session establishment, modification, and release, as well as the dynamic allocation of session resources and the enforcement of QoS policies. This centralized control plane processing mechanism requires the AMF to simultaneously handle high-frequency NAS signaling forwarding and complex PDU session state management tasks. When faced with high-frequency processing demands, this can easily lead to low PDU session processing efficiency, affecting the user's session experience.

[0058] In view of this, embodiments of this application provide a session processing method, an electronic device, and a storage medium, applied to a Connection Management Function (CMF) network element. The CMF network element can be established based on the functional decomposition of the AMF network element and can handle some PDU session-related tasks. The method includes: receiving an establishment request sent by a user terminal; wherein the establishment request is used to instruct the CMF network element to establish a Protocol Data Unit (PDU) session corresponding to the user terminal. This application uses the CMF network element to receive and process the PDU session establishment task of the user terminal, thereby reducing the load on the AMF network element, enabling the decomposition of the AMF network element, further service-oriented processing, improving the processing efficiency of PDU sessions, and enhancing the user's session experience.

[0059] For example, please refer to Figure 2 , Figure 2 A schematic diagram of a communication system architecture provided in an embodiment of this application is shown. (Comparison) Figure 2 and Figure 1 In the communication system architecture provided in this application embodiment, a CMF (Connection Management Function) network element is added, which can be responsible for user access-related tasks (such as idle state, connection state management, NAS security context, etc.); while registration-related tasks (such as user authentication, temporary identifier allocation, mobility management, registration with UDM, etc.) are still retained in the AMF network element. The CMF network element uses a service-oriented interface with other core network elements, a traditional N2 interface (i.e., reusing the 5GN2 interface between the AMF network element and the base station) with the base station, and an N1 interface with the terminal.

[0060] The communication system architecture provided in this application adds a CMF network element and adaptively adjusts the functions of the AMF network element, as follows: The main functions of the CMF network element include idle state and connection state management, NAS security context management, N1 / N2 message forwarding, and session information storage. The main functions of the AMF network element include user authentication, UDM subscription, mobility management, allocation of temporary identifiers, and registration area. Figure 2 The other nodes or network functions shown, their roles and Figure 1 The same nodes or networks have similar functions, so they will not be described in detail here.

[0061] The process of connecting a CMF (Communication Management Function) network element to the communication system mainly includes: After the base station powers on, it initiates an N2 interface establishment procedure with the CMF network element, sending the RAN identifier, the corresponding Tracking Area Identity (TAI) for the RAN, and supported network slice information to the CMF network element. The CMF network element then uses the service interface to register and update its configuration file with the NRF (Network RF) network element. The NRF or CMF network element then sends a notification message to the AMF (Application Management Function) network element, informing it that it can send downlink messages to the base station through the CMF network element's configuration file and corresponding RAN information, including the RAN identifier, the corresponding Tracking Area Identity (TAI), and supported network slice information. Upon receiving this information, the AMF network element knows that it can initiate downlink messages to the base station through the CMF network element.

[0062] Based on the communication system architecture mentioned above, the session processing method provided in the embodiments of this application will be further described below.

[0063] Please refer to Figure 3 , Figure 3 This is a flowchart of a session processing method provided in an embodiment of this application, which is applied to a CMF network element. Figure 3 In this context, the session processing method may include, but is not limited to, step 310.

[0064] Step 310: Receive the establishment request sent by the user terminal; wherein, the establishment request is used to instruct the CMF network element to establish a Protocol Data Unit (PDU) session corresponding to the user terminal.

[0065] The session processing method provided in this application mainly relates to the field of mobile communication technology. It can be applied to CMF network elements. In a wireless communication system, one or more CMF network elements can be set. The method of this application can be applied to any CMF network element.

[0066] In the session processing method provided in this application embodiment, the CMF network element can receive an establishment request sent by a user terminal. The establishment request can be used to establish a PDU session corresponding to the user terminal. The CMF network element can execute the processing task of the PDU session corresponding to the user terminal based on the establishment request.

[0067] In this application embodiment, the specific type of user terminal is not limited. For example, it may include a mobile terminal, an Internet of Things (IoT) device, a fixed wireless access (FWA) terminal, or a dedicated communication device. Among them, the mobile terminal may include, but is not limited to, smartphones, tablets, wearable devices (such as smartwatches, AR / VR glasses), etc.; the IoT device may include, but is not limited to, smart sensors, industrial controllers, vehicle-to-everything (V2X) terminals, smart home devices, etc.; the fixed wireless access (FWA) terminal may include, but is not limited to, CPE (Customer Premises Equipment), 5G routers, etc.; and the dedicated communication device may include, but is not limited to, unmanned aerial vehicles (UAVs), robots, and remote medical terminals.

[0068] For user terminals, they can trigger the generation and sending of PDU session establishment requests according to their own business needs. This application does not limit the specific timing and method of triggering such establishment requests. For example, in some embodiments, the establishment request may be triggered by the user terminal when initially accessing the network, such as when the user terminal powers on or transitions from an idle state to a connected state, and can send a PDU session establishment request to the CMF network element to obtain IP connection or non-IP data transmission capabilities. In some embodiments, the establishment request may be triggered by the user terminal under specific business conditions, such as when the user terminal is performing low-latency, high-reliability services like industrial automation control, remote surgery, or autonomous driving, or when facing business needs involving periodic data reporting. In some embodiments, the establishment request may also be triggered when the user terminal undergoes network handover or needs to resume a session. For example, when the user terminal switches from 4G to 5G (Inter-RAT Handover) or switches between different 5G cells (Intra-5G Handover), it may be necessary to re-establish the PDU session; or, in the case of RRC connection reconstruction or mobility management events (such as TAU / RAU), the user terminal needs to initiate a PDU session establishment request. Of course, it is understood that the specific triggering of the user terminal's establishment request can be implemented according to actual needs, and this application does not impose any restrictions on this.

[0069] It is understood that in this embodiment of the application, the CMF network element is used to receive and process the PDU session establishment task of the user terminal, thereby reducing the load of the AMF network element, enabling the AMF network element to be split and further service-oriented, which is conducive to improving the processing efficiency of PDU sessions and improving the user's session experience.

[0070] In some embodiments, a PDU session is established through a target Session Management Function (SMF) network element, which is determined by a CMF network element based on the establishment request. In the 5G / 6G core network architecture, the establishment of a PDU session relies on a Session Management Function (SMF) network element. In this embodiment, the SMF network element can be dynamically selected by the CMF network element based on the user terminal's (UE) establishment request, and the SMF network element selected by the CMF network element is recorded as the target SMF network element.

[0071] For example, in some embodiments, after receiving a PDU session establishment request from a UE, a CMF network element can select a target SMF network element based on some key parameters, which may include, but are not limited to, the following:

[0072] Network Slice Information (S-NSSAI): If a UE requests a specific slice (eMBB, URLLC, mMTC), the CMF network element must select an SMF network element that supports that slice. Data Network Name (DNN): Different DNNs (e.g., "internet", "enterprise", "ims") may correspond to different SMF pools. UE Subscription Information: Operator policies may restrict certain users to using only specific SMF network elements (e.g., enterprise private network users). Load Balancing: To avoid SMF network element overload, the CMF network element may be dynamically selected based on its current CPU / memory / session count. Geographic Location: In edge computing (MEC) scenarios, the CMF network element must select a local SMF network element close to the UE to reduce latency. Session Type: IPv4 / IPv6 / Ethernet / Unstructured PDU sessions may be handled by different SMF network element instances.

[0073] In some embodiments, the target SMF network element is determined by the CMF network element based on the SMF selection subscription information, which is sent to the CMF network element by the Connection and Mobility Management Function (AMF) network element. In this application embodiment, the CMF network element can also determine the target SMF network element based on the SMF selection subscription information. This information can be obtained by the AMF network element during the user terminal (UE) registration process (or other processes) and forwarded to the CMF network element, serving as a key basis for SMF network element selection. Specifically, during the UE initial registration process or mobility registration process, the AMF network element can obtain the UE's subscription data from the Unified Data Management (UDM) or User Data Storage (UDR), which includes SMF selection subscription information. This SMF selection subscription information may include, but is not limited to: a default SMF list: the default SMF network element instance or SMF network element pool subscribed to by the UE (sorted by priority); operator policies: such as home / visited SMF network element selection rules in roaming scenarios; dedicated SMF network elements for specific network slices (S-NSSAI), etc., which are not limited in this application.

[0074] In some embodiments, the CMF network element may also send a request message to the target SMF network element to establish a PDU session, and the request message may carry the AMF identifier corresponding to the AMF network element.

[0075] In some embodiments, the establishment request carries one of the following information: application information that triggers the PDU session; single network slice selection auxiliary information corresponding to the PDU session; data network name corresponding to the PDU session; session and service continuity mode corresponding to the PDU session; and session identifier assigned to the PDU session by the user terminal. It is understood that, in the embodiments of this application, the establishment request may carry one or more related information to guide CMF and SMF network elements in the dynamic allocation of session resources and policy execution. This information will directly affect core functions such as network slice selection, QoS guarantee, and session routing.

[0076] Specifically, in this embodiment, the application information that triggers the PDU session refers to the application information that the UE can explicitly or implicitly identify to trigger the establishment of the PDU session. This information may include, but is not limited to, the application category (e.g., video stream, VoNR, industrial control), application ID, service type, and traffic characteristics (e.g., low latency, high throughput). Single Network Slice Selection Assistance Information (S-NSSAI) can be used to specify the network slice type requested by the UE (e.g., eMBB, URLLC, mMTC). For example, if S-NSSAI identifies a URLLC slice, the SMF network element needs to select a UPF and transmission path that supports low latency. The Data Network Name (DNN) corresponding to the PDU session is used to identify the external data network that the UE needs to access (e.g., "internet", "ims", "enterprise"). The Session and Service Continuity (SSC) mode corresponding to a PDU session defines the mobility handling method for the PDU session, such as keeping the session anchor point unchanged (UPF does not switch with UE movement), allowing session anchor point switching but requiring reconstruction after interruption, or allowing the session anchor point to be dynamically migrated (e.g., for vehicle-to-everything (V2X) communication). The session identifier assigned by the user terminal to the PDU session is a unique identifier for the PDU session on the user terminal side, which can be used to distinguish different PDU sessions. It is understood that, in the embodiments of this application, the relevant information included in the establishment request is not limited to the types given above, and may also include other information, which this application does not limit.

[0077] In some embodiments, the single network slice selection auxiliary information, data network name, and session and service continuity mode corresponding to the PDU session are determined by the user terminal according to the terminal policy; or the single network slice selection auxiliary information, data network name, and session and service continuity mode corresponding to the PDU session are determined by the CMF network element according to the local policy or the terminal policy, and the terminal policy is sent to the CMF network element through the policy control function PCF network element.

[0078] In some embodiments, the CMF network element can also send the context information of the PDU session to the AMF network element; wherein, the context information includes the session identifier corresponding to the PDU session and the SMF address of the target SMF network element. Thus, when a user terminal needs to switch or reconnect to a CMF network element, the AMF network element can send the stored context information of the PDU session to the newly connected CMF network element, facilitating the CMF network element to quickly restore the PDU session and thereby improving the efficiency of session processing.

[0079] In some embodiments, when a PDU session needs to be rebuilt, the CMF network element can send a service request to the AMF network element and receive context information of all PDU sessions established by the user terminal from the AMF network element. Here, the service request sent by the CMF network element to the AMF network element may carry the user identifier corresponding to the user terminal, so that the AMF network element can determine which user terminal's context information needs to be returned. Then, the AMF network element can send the context information of all PDU sessions established by the user terminal corresponding to the user identifier to the CMF network element, so that the CMF network element can quickly restore the PDU session, thereby improving the efficiency of session processing.

[0080] In some embodiments, when a PDU session needs to be rebuilt, the CMF network element can send a service request to the AMF network element. The service request may carry a list of identifiers for PDU sessions to be activated, including one or more identifiers for these sessions. Then, the CMF network element can receive target context information from the AMF network element, where the target context information is the context information corresponding to the PDU session to be activated. In this embodiment, to further improve the efficiency of the CMF network element in restoring PDU sessions, the CMF network element may carry identifiers for the PDU sessions to be activated when sending the service request. These identifiers may be one or more, forming a corresponding identifier list. After receiving the identifier list, the AMF network element can directly locate the corresponding PDU session (i.e., the PDU session to be activated), thereby obtaining the target context information of these PDU sessions and feeding it back to the CMF network element. This allows the CMF network element to more quickly activate and rebuild PDU sessions.

[0081] In some embodiments, the CMF network element can also receive paging information sent by the AMF network element and perform paging based on the paging information. Paging through the CMF network element can quickly rebuild the PDU session corresponding to the user terminal, enabling the user terminal to enter the connected state.

[0082] In some embodiments, the paging information may carry the registration area of ​​the user terminal determined by the AMF network element. The registration area can be used to indicate the location range for the CMF network element to perform paging. The CMF network element can select the corresponding base station to perform paging based on the registration area, thereby improving the efficiency and accuracy of paging user terminals.

[0083] In some embodiments, the paging information may carry target context information, which is the context information corresponding to the PDU session to be activated. This allows the target context information to be quickly transmitted to the corresponding CMF network element, facilitating faster activation and reconstruction of the PDU session by the CMF network element.

[0084] Please refer to Figure 4 , Figure 4 This is a flowchart of another session processing method provided in an embodiment of this application, which is applied to an AMF network element. Figure 4 In this process, the session processing method may include, but is not limited to, steps 410 to 420.

[0085] Step 410: Receive the context information of the PDU session sent by the CMF network element.

[0086] Step 420: Store context information.

[0087] In this embodiment, the AMF network element can receive and store the context information of the PDU session sent by the CMF network element. Thus, when a user terminal needs to switch to or reconnect to a CMF network element, the AMF network element can send the stored PDU session context information to the newly connected CMF network element, facilitating rapid recovery of the PDU session by the CMF network element and improving session processing efficiency.

[0088] It is understood that, in this embodiment of the application, by splitting the functions of the AMF network element and offloading some processing tasks related to PDU sessions to the CMF network element for processing, the load and complexity of the AMF network element can be reduced, the service level of the AMF network element can be further improved, the efficiency of session processing can be improved, and thus the user's session experience can be improved.

[0089] In some embodiments, a PDU session is triggered by a user terminal and established through a target SMF network element, which is determined by a CMF network element based on the establishment request from the user terminal; the context information includes the session identifier of the PDU session and the SMF address of the target SMF network element.

[0090] In the session processing method provided in this application embodiment, the CMF network element can receive an establishment request sent by a user terminal. The establishment request can be used to establish a PDU session corresponding to the user terminal. The CMF network element can execute the processing task of the PDU session corresponding to the user terminal based on the establishment request.

[0091] For user terminals, they can trigger the generation and sending of PDU session establishment requests according to their own business needs. This application does not limit the specific timing and method of triggering such establishment requests. For example, in some embodiments, the establishment request may be triggered by the user terminal when initially accessing the network, such as when the user terminal powers on or transitions from an idle state to a connected state, and can send a PDU session establishment request to the CMF network element to obtain IP connection or non-IP data transmission capabilities. In some embodiments, the establishment request may be triggered by the user terminal under specific business conditions, such as when the user terminal is performing low-latency, high-reliability services like industrial automation control, remote surgery, or autonomous driving, or when facing business needs involving periodic data reporting. In some embodiments, the establishment request may also be triggered when the user terminal undergoes network handover or needs to resume a session. For example, when the user terminal switches from 4G to 5G (Inter-RAT Handover) or switches between different 5G cells (Intra-5G Handover), it may be necessary to re-establish the PDU session; or, in the case of RRC connection reconstruction or mobility management events (such as TAU / RAU), the user terminal needs to initiate a PDU session establishment request. Of course, it is understood that the specific triggering of the user terminal's establishment request can be implemented according to actual needs, and this application does not impose any restrictions on this.

[0092] In the core network architecture of 5G / 6G, the establishment of PDU sessions relies on the Session Management Function (SMF) network element. In this embodiment, the SMF network element can be dynamically selected by the CMF network element according to the establishment request of the user terminal (UE), and the SMF network element selected by the CMF network element is recorded as the target SMF network element.

[0093] For example, in some embodiments, after receiving a PDU session establishment request from a UE, a CMF network element can select a target SMF network element based on some key parameters, which may include, but are not limited to, the following:

[0094] Network Slice Information (S-NSSAI): If a UE requests a specific slice (eMBB, URLLC, mMTC), the CMF network element must select an SMF network element that supports that slice. Data Network Name (DNN): Different DNNs (e.g., "internet", "enterprise", "ims") may correspond to different SMF pools. UE Subscription Information: Operator policies may restrict certain users to using only specific SMF network elements (e.g., enterprise private network users). Load Balancing: To avoid SMF network element overload, the CMF network element may be dynamically selected based on its current CPU / memory / session count. Geographic Location: In edge computing (MEC) scenarios, the CMF network element must select a local SMF network element close to the UE to reduce latency. Session Type: IPv4 / IPv6 / Ethernet / Unstructured PDU sessions may be handled by different SMF network element instances.

[0095] In some embodiments, the target SMF network element is determined by the CMF network element based on the SMF selection subscription information, which is sent to the CMF network element by the Connection and Mobility Management Function (AMF) network element. In this embodiment, the CMF network element can also determine the target SMF network element based on the SMF selection subscription information. This information can be obtained by the AMF network element during the user terminal (UE) registration process and forwarded to the CMF network element as a key basis for SMF network element selection. Specifically, during the UE initial registration process or mobility registration process, the AMF network element can obtain the UE's subscription data from the Unified Data Management (UDM) or User Data Storage (UDR), which includes SMF selection subscription information. This SMF selection subscription information may include, but is not limited to: a default SMF list: the default SMF network element instance or SMF network element pool subscribed to by the UE (sorted by priority); operator policies: such as home / visited SMF network element selection rules in roaming scenarios; dedicated SMF network elements for specific network slices (S-NSSAI), etc., which are not limited in this application.

[0096] In some embodiments, the context information can be stored locally by the AMF network element or sent by the AMF network element to the Unstructured Data Storage Function (UDSF) network element for storage. This way, when a user terminal needs to switch to or reconnect to a CMF network element, the AMF network element can send the stored context information to the newly connected CMF network element, facilitating the CMF network element's rapid recovery of the PDU session.

[0097] In some embodiments, the AMF network element can receive service requests sent by the CMF network element and then send context information of all PDU sessions established by the user terminal back to the CMF network element. Here, the service request sent by the CMF network element to the AMF network element may carry the user identifier corresponding to the user terminal, so that the AMF network element can determine which user terminal's context information needs to be sent back. Then, the AMF network element can send the context information of all PDU sessions established by the user terminal corresponding to the user identifier to the CMF network element, so that the CMF network element can quickly restore the PDU sessions, thereby improving session processing efficiency.

[0098] In some embodiments, the AMF network element can receive a service request sent by the CMF network element. The service request may carry a list of identifiers for PDU sessions to be activated, including one or more identifiers for these sessions. Then, the AMF network element can query the target context information based on the identifier list. This target context information is the context information corresponding to the PDU session to be activated, and can then send the target context information to the CMF network element. In this embodiment, to further improve the efficiency of the CMF network element in restoring PDU sessions, the CMF network element may carry identifiers for the PDU sessions to be activated when sending the service request. These identifiers may be one or more, forming a corresponding identifier list. After receiving the identifier list, the AMF network element can directly locate the corresponding PDU session (i.e., the PDU session to be activated), thereby obtaining the target context information for these PDU sessions and feeding it back to the CMF network element. This allows the CMF network element to more quickly activate and rebuild PDU sessions.

[0099] In some embodiments, the AMF network element can also send paging information to the CMF network element, whereby the paging information instructs the CMF network element to perform paging. Paging via the CMF network element can quickly rebuild the PDU session corresponding to the user terminal, enabling the user terminal to enter the connected state.

[0100] In some embodiments, the paging information may carry the registration area of ​​the user terminal determined by the AMF network element. The registration area can be used to indicate the location range for the CMF network element to perform paging. The CMF network element can select the corresponding base station to perform paging based on the registration area, thereby improving the efficiency and accuracy of paging user terminals.

[0101] In some embodiments, the paging information may carry target context information, which is the context information corresponding to the PDU session to be activated. This allows the target context information to be quickly transmitted to the corresponding CMF network element, facilitating faster activation and reconstruction of the PDU session by the CMF network element.

[0102] This application embodiment also provides another session processing method, which can be applied to SMF network elements, the method including:

[0103] Receive the AMF identifier sent by the CMF network element;

[0104] Based on the AMF identifier, determine the AMF address information of the corresponding AMF network element;

[0105] When downlink data is confirmed to have arrived, a notification message is sent to the AMF network element based on the AMF address information; the notification message is used to trigger the AMF network element to initiate paging.

[0106] In this embodiment, the SMF network element can receive and store the AMF identifier sent by the CMF network element when establishing a PDU session. Based on the AMF identifier, the AMF address information of the corresponding AMF network element can be determined. In the scenario of reconstructing the PDU session corresponding to the user terminal via paging, when the UPF network element receives downlink data, it notifies the SMF network element that the downlink data has arrived. Upon confirming the arrival of the downlink data, the SMF network element can send a notification message to the AMF network element based on the AMF address information, thereby triggering the AMF network element to perform paging.

[0107] The session processing method provided in this application will be introduced and explained below with reference to some specific application process embodiments.

[0108] Example 1

[0109] Please refer to Figure 5 , Figure 5 This illustration shows an interaction diagram of a user terminal during the initial registration process, as provided in an embodiment of this application. The initial registration process mainly includes the following steps:

[0110] 1. The UE sends a Registration Request to the RAN. This Registration Request is a NAS message. This message carries the SUCI (Subscription Concealed Identifier) ​​or SUPI (Subscription Permanent Identifier) ​​corresponding to the user terminal, which is used to identify the identity of the user terminal.

[0111] 2. The RAN selects a suitable CMF network element. For example, it can randomly determine a CMF network element from all available CMF network elements, or select a default CMF network element, which is pre-configured on the RAN.

[0112] 3. The RAN forwards the UE's registration request (NAS message) to the selected CMF network element; this message carries the user terminal's current access location information.

[0113] 4. After receiving the registration request, the CMF network element creates a user context and then selects an AMF network element. Specifically, the CMF network element can select the AMF network element through the NRF network element, or according to the locally configured AMF network element selection rules. In this embodiment, since the AMF network element does not need to support connection services with the base station, the CMF network element can select an AMF network element that is independent of the current location accessed by the user terminal, thereby reducing the probability of the user moving across AMF network elements.

[0114] 5. The CMF network element forwards the UE's registration request (NAS message) to the selected AMF network element. This message carries the service address of the current CMF network element (this address points to the CMF network element and the user context). When the AMF network element needs to communicate with the terminal / base station subsequently, the target address is set to the service address of the CMF network element. In addition, this message also carries the user terminal's current access location information.

[0115] 6. The AMF network element initiates the authentication process for the UE. During this process, the AMF network element first selects a suitable AUSF (Authentication Server Function) for the UE, and then sends an authentication request to the AUSF. The AUSF then initiates the UE's identity authentication and authorization process. In this process, the network authenticates the user terminal, and the user terminal also authenticates the network. All signaling between the UE and the AMF network element during the authentication process needs to be transmitted through the CMF network element, including both uplink and downlink NAS messages.

[0116] 7. (7a) After successful authentication, the AMF network element initiates a secure mode command to the CMF network element, triggering the establishment of a NAS secure connection between the UE and the CMF network element. This message can be sent to the CMF network element by sending an N1N2 message carrying the secure mode command. (7b) When the CMF network element receives the N1 message from the user terminal and successfully responds with the secure mode command, and the UE successfully encrypts and protects the integrity of the message, and the CMF network element successfully decrypts the message, the CMF network element sends an N1N2 message to the AMF network element to notify it of the successful response with the secure mode command. A service-oriented interface is used between the CMF network element and the AMF network element.

[0117] 8. The CMF network element sends a security mode command to the UE, triggering the UE to generate a NAS security context based on the authentication result of step 6, generate a security mode command response, and then enable NAS security, sending the encrypted and integrity-protected security mode command response to the CMF network element. The CMF network element can generate the NAS security context corresponding to the user terminal locally.

[0118] 9. After the safe mode command is successful, the AMF network element selects a UDM for the UE based on SUPI / SUCI, and then initiates a user subscription information request to the UDM. The UDM sends the user mobility management-related subscription information and session-related information used to select the SMF network element to the AMF network element, such as the user's subscribed S-NSSAI and DNN (Data Network Name).

[0119] 10. The AMF network element initiates an AMF network element registration request to the UDM, carrying the AMF network element identifier of the user's current AMF network element; the UDM saves the AMF network element identifier in the user context, and then returns a registration response to the AMF network element.

[0120] 11. The AMF network element selects the PCF network element to process access and mobility policies, and then establishes an AM policy association with that PCF network element. The AMF network element sends its subscription information and local location to the PCF network element. Simultaneously, the AMF network element sends the CMF network element's service address received in step 5 to the PCF network element. This way, when the PCF network element needs to send AM policies to the UE / base station, the destination address can be directly set to the CMF network element's service address, eliminating the need to go through the AMF network element and reducing the complexity of the AMF network element.

[0121] 12. The AMF network element selects the PCF network element to process the UE policy, and then establishes a UE policy association with the PCF network element. At the same time, the AMF network element sends the CMF network element service address received in step 5 to the PCF network element. In this way, when the PCF network element needs to send the UE policy to the UE / base station, the destination address can be directly set to the service address of the CMF network element, so as not to go through the AMF network element, thus reducing the complexity of the AMF network element.

[0122] 13. After successful user registration, the AMF network element assigns a temporary identifier, such as a Globally Unique Temporary Identifier (GUTI), to the user terminal. Then, it generates a Registration Area (RA) based on the user terminal's current access location information and the location information supported by the base station. Here, the temporary identifier and registration area belong to the second NAS message. The AMF then returns a Registration Accept response to the UE, which carries the assigned GUTI and RA. The GUTI may include an S-TMSI (Serving Temporary Mobile Subscriber Identity), which includes the AMF network element identifier corresponding to the AMF network element and a temporary identifier uniquely identifying the user within the AMF network element. Optionally, in some embodiments, the GUTI may also include the CMF network element identifier, used to identify the CMF network element accessed by the user terminal this time. This response message is sent via the CMF network element's N1N2 message sending service. Meanwhile, the AMF network element carries the user subscription information received in step 9 in the response message, including session-related information for selecting the SMF network element, and the CMF network element can save this subscription information.

[0123] 14. The CMF network element sends a NAS message accepting registration to the UE. This NAS message carries information such as a temporary identifier and registration area.

[0124] 15. The UE saves information such as temporary identifier and registration area, and returns a registration completion message to the CMF network element.

[0125] Understandably, through the initial registration process described above, the user terminal can successfully register in the AMF network element. Furthermore, the CMF network element also stores the user context corresponding to the user terminal, including the NAS security context and session-related information for selecting the SMF network element. The PCF network element and other network elements also learn the service address of the CMF network element. Subsequently, during message transmission, the CMF network element can perform some message transmission and processing tasks on behalf of the AMF network element, thereby reducing the load on the AMF network element, improving session processing efficiency, and enhancing the performance of the communication system.

[0126] As another supplementary implementation, to achieve statelessness, the AMF network element can also save the user context to the UDSF (Unstructured Data Storage Function). Subsequently, the AMF network element can retrieve the user context from the UDSF for service processing as needed. Of course, the AMF network element can also save the user context locally; this application does not impose any restrictions on this.

[0127] Example 2

[0128] Please refer to Figure 6 , Figure 6 This illustration shows an interaction diagram of a user terminal during the PDU session establishment process, as provided in an embodiment of this application. The PDU session establishment process mainly includes the following steps:

[0129] 1. The UE sends a PDU session establishment request to the CMF network element via the RAN. This message carries relevant information about the PDU session, such as application information that triggered the PDU session, the single network slice selection auxiliary information (S-NSSAI) corresponding to the PDU session, the data network name (DNN), the SSC (Session and Service Continuity) mode, and the PDU session identifier assigned by the UE. The UE can determine the S-NSSAI, DNN, and SSC mode that the application triggering the PDU session can use based on the UE policy. Alternatively, the UE can only carry the application information, allowing the CMF network element to determine the S-NSSAI, DNN, and SSC mode defined for the PDU session. This application does not impose any restrictions on this.

[0130] 2. If the UE only carries application information, the CMF network element can generate the S-NSSAI, DNN, and SSC mode information defined for the PDU session based on the application information, local policies, or the UE policy received from the PCF network element. If the CMF network element receives the S-NSSAI, DNN, and SSC mode information defined for the PDU session from the UE, it can directly use this information. The CMF network element selects a suitable SMF network element for the PDU session: Specifically, the CMF network element needs to check whether the SMF selection subscription information allows the S-NSSAI and DNN of the PDU session and select the corresponding SMF network element. Here, the SMF selection subscription information can be sent by the AMF network element to the CMF network element during the registration process.

[0131] 3. The CMF network element sends a Create SMContext Request to the SMF network element. This message carries the S-NSSAI, DNN, and SSC modes of the PDU session, as well as the user terminal's current access system information and location information. Upon receiving this message, the SMF network element directly returns a PDU session establishment response. Optionally, this request message may also carry the AMF identifier information corresponding to the AMF network element currently registered with the user terminal; the SMF network element stores this AMF identifier information locally.

[0132] 4. The SMF network element initiates a session subscription data retrieval request to the UDM, carrying the S-NSSAI and DNN of the PDU session. The UDM returns the UE session subscription data, including the S-NSSAI and DNN, to the SMF.

[0133] 5. The SMF network element selects a PCF network element and initiates a Session Management Policy Association (SMPA) establishment request to that PCF network element, carrying the S-NSSAI and DNN requested by the UE, the current location information of the user terminal, and the access system information of the user terminal. The PCF network element obtains the user's subscription data from the UDR (User Data Repository), generates session policy information (SM Policy) according to the local policy, and then returns the session policy information to the SMF network element.

[0134] 6. The SMF network element selects a suitable UPF network element based on information such as S-NSSAI, DNN, and UE location, and then initiates an N4 Session Establishment Request to that UPF network element. The UPF network element responds to the SMF network element's request, establishes an N4 session, assigns an uplink tunnel identifier to the PDU session, and returns an N4 Session Establishment Response to the SMF network element.

[0135] 7. After the N4 session is successfully established, the SMF network element sends an N1 / N2 message transfer request to the CMF network element. This message carries a NAS (Non-access stratum) message to the UE and an AS (N2 Session Setup) message to the RAN. The NAS message is a PDU Session Establishment Accept message, and the AS message contains the context information of the PDU session, such as the list of created QoS flow configuration information and the PDU session uplink tunnel identifier allocated by the UPF.

[0136] 8. The CMF network element sends an N2 interface PDU Session Request message to the RAN, which carries the NAS and AS messages received from the SMF network element. The RAN sends an RRC (Radio Resource Connection Reconfiguration) procedure to the UE, establishing a suitable radio bearer for the UE based on the PDU session information provided by the SMF network element. Simultaneously, the RAN sends the NAS message to the UE. After creating the radio resources, the RAN returns an N2 interface PDU Session ack message to the CMF network element, carrying the N3 interface resources allocated by the RAN for this PDU session, such as the downlink tunnel identifier.

[0137] 9. The CMF network element sends an Update SMContext Request to the SMF network element to update the RAN tunnel identifier of the UPF network element on the N3 interface.

[0138] 10. The SMF network element sends an N4 Session Update Request to the UPF network element to update the tunnel identifier of the RAN on the N3 interface.

[0139] 11. In step 7, the SMF network element can allocate IP addresses to the terminal via control plane or via user plane. Afterwards, the SMF network element registers with the UDM, and the UDM stores the SMF address of the SMF network element and the user IP address in the user session context corresponding to S-NSSAI and DNN.

[0140] It is understood that during the PDU session establishment process in this embodiment, the CMF network element can directly communicate with the SMF network element to complete the establishment of the user terminal's PDU session; the AMF network element is no longer directly responsible for handling the PDU session establishment task, thereby reducing the load and complexity of the AMF network element, and helping to reduce the latency of PDU session establishment, improve the processing efficiency of PDU sessions, and thus improve user experience and system performance. Furthermore, after the PDU session establishment process, the CMF network element can initiate a user context update request to the AMF network element through an update message, or, as shown in Embodiment 3 below, send the identifier and SMF address information of the PDU session to the AMF network element, which can then store them locally.

[0141] Example 3

[0142] Please refer to Figure 7 , Figure 7 This illustration shows an interaction diagram of a user terminal during the interface release process, as provided in an embodiment of this application. The interface release process mainly includes the following steps:

[0143] 1. When the RAN determines that the N2 interface needs to be released (e.g., due to radio link failure or other reasons), it can initiate an AN interface release request to the CMF network element. Specifically, in some embodiments, the release request may carry the release reason and other information.

[0144] 2. When the CMF network element receives an AN interface release request from the RAN, or when the CMF network element itself determines that it needs to initiate a UE context release, the CMF network element sends a UE context release command to the RAN. The UE context release command corresponds to a user terminal and instructs the release of the connection of the corresponding user terminal.

[0145] 3. If the current RRC connection between the RAN and the user terminal has not been released, the RAN will release the RRC connection of the user terminal.

[0146] 4. The RAN sends a message to the CMF network element indicating that the UE context release is complete;

[0147] 5. The CMF network element sends a UE context release request to the AMF network element through the service interface. This request carries the release reason. If the CMF network element has not yet sent the established PDU session information (PDU session identifier, SMF) to the AMF network element, it sends the aforementioned PDU session information to the AMF network element in this message, which the AMF network element saves upon receipt. After receiving the UE context release request message, the AMF network element deletes the CMF network element's address information from the UE context. Then, the AMF network element returns a UE context release response to the CMF network element.

[0148] 6. For an established PDU session, the CMF network element initiates a PDU session update request to the SMF network element, requesting the SMF network element to delete the address information related to the CMF network element and the user plane information of the base station.

[0149] 7. The SMF network element deletes the address information related to the CMF network element, then initiates an N4 update request to the UPF to delete the user plane information of the base station and requests the UPF network element to enable downlink data caching. After processing, the UPF network element returns a response to the SMF network element.

[0150] In this embodiment, after the interface release process is completed, both the AMF and SMF network elements delete the CMF network element and RAN information corresponding to the user terminal. In the AMF network element, the user terminal's state changes to idle.

[0151] Example 4

[0152] Please refer to Figure 8 , Figure 8 This illustration shows an interactive diagram of a user terminal activating a PDU session during connection reconstruction, as provided in an embodiment of this application. The connection reconstruction process mainly includes the following steps:

[0153] 1. The user terminal initiates a service request to the RAN. This service request is a NAS message and may carry the temporary identifier S-TMSI corresponding to the user terminal. The user terminal is responsible for the integrity protection of this NAS message.

[0154] 2. The RAN selects a suitable CMF network element. For example, it can randomly determine a CMF network element from all available CMF network elements, or select a default CMF network element, which is pre-configured on the RAN.

[0155] 3. The RAN forwards the UE's Service Request to the selected CMF network element;

[0156] 4. After receiving the Service Request, the CMF network element creates a user context, selects an AMF network element based on the S-TMSI, and then sends a Service Request to that AMF network element through the service interface. This request carries the temporary identifier S-TMSI corresponding to the user terminal and the service address of the current CMF network element (this address points to the current CMF network element and the user context). When the AMF network element needs to communicate with the terminal / base station subsequently, the target address is set to the service address of the CMF network element. Optionally, this message may also carry a list of identifiers for PDU sessions to be activated received from the user terminal.

[0157] 5. If the AMF network element decides to accept the Service Request, it sends a UE context establishment message to the CMF network element through the service interface, carrying a NAS Service Accept message. If the AMF network element receives the list of identifiers for PDU sessions to be activated, it sends the saved context information (i.e., target context information) of the PDU sessions to be activated to the CMF network element. This information includes the session identifier of the PDU session to be activated and the SMF address of the target SMF network element corresponding to the PDU session to be activated. If it does not receive the list of identifiers for the PDU sessions to be activated, the AMF network element can send the context information of all saved PDU sessions to the CMF network element, or it can not send any PDU session information to the CMF network element.

[0158] 6. After the CMF network element creates a user session context, it also sends a PDU session update request to the SMF network element corresponding to these PDU sessions to update the CMF address information. If the PDU session needs to be activated, the PDU session update request will also include an instruction to activate the PDU session.

[0159] 7. After receiving the message, if the SMF network element needs to activate the PDU session, it sends an N1 / N2 message transfer request to the CMF network element. This message carries an AS message (N2 Session Setup) to be sent to the RAN. The AS message contains the context information of the PDU session, such as the list of created QoS flow configuration information and the uplink tunnel identifier of the PDU session assigned by the UPF network element.

[0160] 8. The CMF network element sends an N2 interface PDU session request message to the RAN, which carries the AS message received from the SMF network element and the NAS message Service Accept received from the AMF network element. The RAN sends an RRC reconfiguration procedure (Radio Resource Connection Reconfiguration) to the UE, and establishes a suitable radio bearer for the UE based on the PDU session information provided by the SMF network element. At the same time, it forwards the NAS Service Accept message to the UE. After creating the radio resources, the RAN returns an N2 interface PDU session ack message to the CMF network element, which carries the N3 interface resources allocated by the RAN for this PDU session, such as the downlink tunnel identifier.

[0161] 9. The CMF network element sends a user context establishment response to the AMF network element.

[0162] 10. The CMF network element sends an Update SMContextRequest to the SMF network element to update the RAN user plane tunnel identifier of the UPF network element on the N3 interface.

[0163] 11. The SMF network element sends an N4 Session Update Request to the UPF network element to update the user plane tunnel identifier of the RAN on the N3 interface.

[0164] It is understood that, in the connection reconstruction process of this application embodiment, for PDU sessions that need to be activated, the AMF network element can send the stored context information of the PDU session to be activated to the CMF network element. This allows for rapid activation of the PDU session and improves session processing efficiency. After the connection reconstruction process is completed, the user terminal re-enters the connected state and activates the requested PDU session, establishing the air interface and N3 user plane.

[0165] Example 5

[0166] Please refer to Figure 9 , Figure 9 This illustration shows an interactive diagram of reconstructing a user terminal's network connection and activating a PDU session via paging, as provided in an embodiment of this application. The application mainly includes the following process:

[0167] 1. When the UPF network element receives the downlink data, it caches the downlink data and notifies the SMF network element that the downlink data has arrived.

[0168] 2. The UPF network element sends a downlink data arrival notification to the SMF network element, notifying the SMF network element to trigger paging.

[0169] 3. The SMF network element determines the AMF address information of the AMF network element according to the AMF identifier stored in Embodiment 2, and then triggers a downlink paging message to the AMF network element. The message carries a user identifier, such as SUPI, and the identifier of the PDU session to be activated.

[0170] 4. If the AMF network element determines that the user is reachable, it triggers paging of the UE. The AMF network element first selects a CMF network element based on the user's registered area. The AMF network element can be configured locally or obtain information from the NRF network element about which CMF network elements can serve the user's registered area (TAI list).

[0171] 5. Then, the AMF network element sends a paging message to all selected CMF network elements. The paging message carries the user temporary identifier S-TMSI, and optionally, the user's registration area.

[0172] 6. The CMF network element initiates a paging message to the connected base station. If the CMF network element receives the user's registration area, it can further select a base station within the registration area to paging the user based on the user's registration area.

[0173] 7. The base station initiates a paging request to the user terminal, and the paging request carries the S-TMSI.

[0174] 8. After receiving the paging message, the user terminal initiates a Service request procedure to the base station, transitioning the user terminal from the idle state to the connected state. During this process, the AMF network element sends the PDU session context to be activated (including the PDU session identifier and SMF address) to the CMF network element, and then the CMF network element initiates a PDU session update procedure to the corresponding SMF network element.

[0175] Through the above process, the network connection of the user terminal was rebuilt based on paging, and the PDU session for receiving downlink data by the user terminal was activated, establishing the air interface and N3 user plane.

[0176] In this embodiment of the application, an electronic device is also provided, including:

[0177] One or more processors;

[0178] A memory that stores one or more programs, which, when executed by one or more processors, enable the processors to perform actions such as:

[0179] like Figure 3 or Figure 4 Any of the session processing methods shown.

[0180] It is understandable that, such as Figure 3 or Figure 4 The content of any of the session processing method embodiments shown is applicable to the embodiments of this electronic device, and the specific functions implemented by the embodiments of this electronic device are the same as those shown. Figure 3 or Figure 4 The embodiments of any of the session processing methods shown are identical, and the beneficial effects achieved are the same as those described above. Figure 3 or Figure 4 The beneficial effects achieved by any of the illustrated session processing method embodiments are the same.

[0181] This application also discloses a computer-readable storage medium storing a processor-executable program, which, when executed by a processor, is used to implement, for example... Figure 3 or Figure 4 Examples of any of the session processing methods shown.

[0182] It is understandable that, such as Figure 3 or Figure 4 The content of any of the session processing method embodiments shown is applicable to the embodiments of this computer-readable storage medium, and the specific functions implemented by the embodiments of this computer-readable storage medium are the same as those shown. Figure 3 or Figure 4 The embodiments of any of the session processing methods shown are identical, and the beneficial effects achieved are the same as those described above. Figure 3 or Figure 4 The beneficial effects achieved by any of the illustrated session processing method embodiments are the same.

[0183] This application also discloses a computer program product, including a computer program, which, when executed by a processor, implements as follows: Figure 3 or Figure 4 Examples of any of the session processing methods shown.

[0184] It is understandable that, such as Figure 3 or Figure 4 The content of any of the session processing method embodiments shown is applicable to the embodiments of this computer program product, and the specific functions implemented by the embodiments of this computer program product are the same as those shown. Figure 3 or Figure 4 The embodiments of any of the session processing methods shown are identical, and the beneficial effects achieved are the same as those described above. Figure 3 or Figure 4 The beneficial effects achieved by any of the illustrated session processing method embodiments are the same.

[0185] In some alternative embodiments, the functions / operations mentioned in the block diagrams may not occur in the order shown in the operation diagrams. For example, depending on the functions / operations involved, two consecutively shown blocks may actually be executed substantially simultaneously, or the blocks may sometimes be executed in reverse order. Furthermore, the embodiments presented and described in the flowcharts of this application are provided by way of example to provide a more comprehensive understanding of the technology. The disclosed methods are not limited to the operations and logic flows presented herein. Alternative embodiments are contemplated in which the order of various operations is changed and sub-operations described as part of a larger operation are executed independently.

[0186] Furthermore, although this application is described in the context of functional modules, it should be understood that, unless otherwise stated to the contrary, one or more of the functions and / or features may be integrated into a single physical device and / or software module, or one or more functions and / or features may be implemented in a separate physical device or software module. It is also understood that a detailed discussion of the actual implementation of each module is unnecessary for understanding this application. Rather, given the properties, functions, and internal relationships of the various functional modules in the apparatus disclosed herein, the actual implementation of the module will be understood within the scope of conventional technology for an engineer. Therefore, those skilled in the art can implement the application set forth in the claims using ordinary techniques without excessive experimentation. It is also understood that the specific concepts disclosed are merely illustrative and not intended to limit the scope of this application, which is determined by the full scope of the appended claims and their equivalents.

[0187] If a function is implemented as a software functional unit and sold or used as an independent product, it can be stored in a computer-readable storage medium. Based on this understanding, the technical solution of this application, in essence, or the part that contributes to the prior art, or a part of the technical solution, can be embodied in the form of a software product. This computer software product is stored in a storage medium and includes several instructions to cause a computer device (which may be a personal computer, server, or network device, etc.) to execute all or part of the steps of the methods of the various embodiments of this application. The aforementioned storage medium includes various media capable of storing program code, such as USB flash drives, portable hard drives, read-only memory (ROM), random access memory (RAM), magnetic disks, or optical disks.

[0188] The logic and / or steps represented in the flowchart or otherwise described herein, for example, can be considered as a sequenced list of executable instructions for implementing logical functions, and can be embodied in any computer-readable medium for use by, or in conjunction with, an instruction execution system, apparatus, or device (such as a computer-based system, a processor-included system, or other system that can fetch and execute instructions from, an instruction execution system, apparatus, or device). For the purposes of this specification, "computer-readable medium" can be any means that can contain, store, communicate, propagate, or transmit programs for use by, or in conjunction with, an instruction execution system, apparatus, or device.

[0189] More specific examples of computer-readable media (a non-exhaustive list) include: electrical connections (electronic devices) having one or more wires, portable computer disk drives (magnetic devices), random access memory (RAM), read-only memory (ROM), erasable and editable read-only memory (EPROM or flash memory), fiber optic devices, and portable optical disc read-only memory (CDROM). Furthermore, computer-readable media can even be paper or other suitable media on which programs can be printed, because programs can be obtained electronically, for example, by optically scanning the paper or other medium, followed by editing, interpreting, or otherwise processing as necessary, and then stored in computer memory.

[0190] It should be understood that various parts of this application can be implemented using hardware, software, firmware, or a combination thereof. In the above embodiments, multiple steps or methods can be implemented using software or firmware stored in memory and executed by a suitable instruction execution system. For example, if implemented in hardware, as in another embodiment, it can be implemented using any one or a combination of the following techniques known in the art: discrete logic circuits having logic gates for implementing logical functions on data signals, application-specific integrated circuits (ASICs) having suitable combinational logic gates, programmable gate arrays (PGAs), field-programmable gate arrays (FPGAs), etc.

[0191] In the foregoing description of this specification, the references to terms such as "one embodiment," "another embodiment," or "some embodiments," etc., indicate that a specific feature, structure, material, or characteristic described in connection with an embodiment or example is included in at least one embodiment or example of this application. In this specification, the illustrative expressions of the above terms do not necessarily refer to the same embodiment or example. Furthermore, the specific features, structures, materials, or characteristics described may be combined in any suitable manner in one or more embodiments or examples.

[0192] Although embodiments of this application have been shown and described, those skilled in the art will understand that various changes, modifications, substitutions and variations can be made to these embodiments without departing from the principles and spirit of this application, the scope of which is defined by the claims and their equivalents.

[0193] The foregoing has provided a detailed description of the preferred embodiments of this application. However, this application is not limited to these embodiments. Those skilled in the art can make various equivalent modifications or substitutions without departing from the spirit of this application. All such equivalent modifications or substitutions are included within the scope defined by the claims of this application.

[0194] In the description of this specification, the references to terms such as "one embodiment," "another embodiment," or "some embodiments," etc., indicate that a specific feature, structure, material, or characteristic described in connection with an embodiment or example is included in at least one embodiment or example of this application. In this specification, the illustrative expressions of the above terms do not necessarily refer to the same embodiment or example. Furthermore, the specific features, structures, materials, or characteristics described may be combined in any suitable manner in one or more embodiments or examples.

[0195] Although embodiments of this application have been shown and described, those skilled in the art will understand that various changes, modifications, substitutions and variations can be made to these embodiments without departing from the principles and spirit of this application, the scope of which is defined by the claims and their equivalents.

Claims

1. A session processing method, characterized in that, The method, applied to the connection management function (CMF) network element, includes: The system receives an establishment request sent by a user terminal; wherein the establishment request is used to instruct the CMF network element to establish a Protocol Data Unit (PDU) session corresponding to the user terminal.

2. The session processing method according to claim 1, characterized in that, The PDU session is established through the target session management function (SMF) network element, and the target SMF network element is determined by the CMF network element according to the establishment request.

3. The session processing method according to claim 2, characterized in that, The target SMF network element is determined by the CMF network element based on the SMF selection subscription information, which is sent to the CMF network element by the connectivity and mobility management function (AMF) network element.

4. The session processing method according to claim 3, characterized in that, The method further includes: Send a request message to the target SMF network element to establish the PDU session; wherein the request message carries the AMF identifier corresponding to the AMF network element.

5. The session processing method according to claim 1, characterized in that, The request to establish the application carries one of the following information: Application information that triggers the PDU session; The single network slice selection auxiliary information corresponding to the PDU session; The data network name corresponding to the PDU session; The session and service continuity modes corresponding to the PDU session; The user terminal assigns a session identifier to the PDU session.

6. The session processing method according to claim 5, characterized in that, The single network slice selection assistance information, the data network name, and the session and service continuity mode corresponding to the PDU session are determined by the user terminal according to the terminal policy; or the single network slice selection assistance information, the data network name, and the session and service continuity mode corresponding to the PDU session are determined by the CMF network element according to the local policy or the terminal policy, and the terminal policy is sent to the CMF network element through the policy control function PCF network element.

7. The session processing method according to claim 2, characterized in that, The method further includes: Send the context information of the PDU session to the AMF network element; wherein the context information includes the session identifier corresponding to the PDU session and the SMF address of the target SMF network element.

8. The session processing method according to claim 7, characterized in that, The method further includes: Send a service request to the AMF network element; Receive context information of all PDU sessions established by the user terminal from the feedback of the AMF network element.

9. The session processing method according to claim 7, characterized in that, The method further includes: Send a service request to the AMF network element; wherein the service request carries a list of identifiers of PDU sessions to be activated; Receive target context information fed back by the AMF network element; wherein, the target context information is the context information corresponding to the PDU session to be activated.

10. The session processing method according to claim 7, characterized in that, The method further includes: Receive paging information sent by AMF network elements; Paging is performed based on the paging information.

11. The session processing method according to claim 10, characterized in that, The paging information carries the registration area of ​​the user terminal determined by the AMF network element, and the registration area is used to indicate the location range where the CMF network element performs paging.

12. The session processing method according to claim 10, characterized in that, The paging information also carries target context information; wherein, the target context information is the context information corresponding to the PDU session to be activated.

13. A session processing method, characterized in that, Applied to AMF network elements, the method includes: Receive context information of the PDU session sent by the CMF network element; Store the context information.

14. The session processing method according to claim 13, characterized in that, The PDU session is triggered by the user terminal and established through the target SMF network element, which is determined by the CMF network element according to the establishment request of the user terminal; the context information includes the session identifier of the PDU session and the SMF address of the target SMF network element.

15. The session processing method according to claim 14, characterized in that, The target SMF network element is determined by the CMF network element based on the SMF selection subscription information, which is sent by the AMF network element to the CMF network element.

16. The session processing method according to claim 13, characterized in that, The context information is either stored locally by the AMF network element or sent by the AMF network element to the Unstructured Data Storage Function (UDSF) network element for storage.

17. The session processing method according to claim 14, characterized in that, The method further includes: Receive the service request sent by the CMF network element; The context information of all PDU sessions established by the user terminal is fed back to the CMF network element.

18. The session processing method according to claim 14, characterized in that, The method further includes: Receive service requests sent by the CMF network element; wherein the service request carries a list of identifiers for PDU sessions to be activated; Based on the identifier list, query the target context information; wherein, the target context information is the context information corresponding to the PDU session to be activated; The target context information is sent to the CMF network element.

19. The session processing method according to claim 13, characterized in that, The method further includes: Send paging information to the CMF network element; wherein the paging information is used to instruct the CMF network element to perform paging.

20. The session processing method according to claim 19, characterized in that, The paging information carries the registration area of ​​the user terminal determined by the AMF network element, and the registration area is used to indicate the location range where the CMF network element performs paging.

21. The session processing method according to claim 19, characterized in that, The paging information also carries target context information; wherein, the target context information is the context information corresponding to the PDU session to be activated.

22. A session processing method, characterized in that, Applied to SMF network elements, the method includes: Receive the AMF identifier sent by the CMF network element; Based on the AMF identifier, determine the AMF address information of the corresponding AMF network element; When downlink data is confirmed to have arrived, a notification message is sent to the AMF network element based on the AMF address information; wherein, the notification message is used to trigger the AMF network element to initiate paging.

23. An electronic device, characterized in that, include: At least one processor; At least one memory for storing at least one program; The session processing method of any one of claims 1 to 22 is implemented when at least one of the programs is executed by at least one of the processors.

24. A computer-readable storage medium storing computer-executable instructions, characterized in that, The computer-executable instructions are used to execute the session processing method according to any one of claims 1 to 22.

25. A computer program product, comprising a computer program or computer instructions, characterized in that, The computer program or the computer instructions are stored in a computer-readable storage medium. The processor of the electronic device reads the computer program or the computer instructions from the computer-readable storage medium and executes the computer program or the computer instructions, causing the electronic device to perform the session processing method according to any one of claims 1 to 22.