Session processing method, electronic device, and storage medium

Abstract

Embodiments of the present application provide a session processing method, an electronic device, and a storage medium, which are applied to a 5G system and a 6G system. The method comprises: receiving access management function registration requests sent by access management function units corresponding to different users for registration; receiving a session registration request of a first user among the different users that is sent by a session management function unit, and storing session information of the session registration request; feeding back the session information to the access management function unit of at least one other user among the different users; and feeding back the session information to the session management function unit of the at least one other user among the different users. According to the embodiments of the present application, by feeding back session information of a first user to other users, different terminal users can select the same session management function, facilitating achievement of traffic steering and switching between different protocol data unit sessions.

Description

Conversation processing method, electronic device and storage medium Technical Field

[0001] The present application relates to the field of wireless communication technology, and in particular to a session processing method, electronic device, and storage medium. Background Art

[0002] Fifth Generation Mobile Communication Technology (5G) is a new generation of broadband mobile communication technology characterized by high speed, low latency, and large connections. 5G communication facilities are the network infrastructure for realizing human-machine interconnection. When multiple devices access the system, different Protocol Data Unit (PDU) sessions are established. In order to enable traffic diversion and / or switching between different PDU sessions, these PDU sessions need to be selected to the same Session Management Function (SMF), and the SMF can associate these sessions. However, how to establish these associated PDU sessions is currently a problem that needs to be solved. This technical problem also exists in 6G systems. Summary of the Invention

[0003] The embodiments of the present application aim to provide a session processing method, an electronic device, and a storage medium to implement the association establishment of multiple sessions in 5G systems and 6G systems, so that different sessions select the same session management function, and traffic steering and switching between different PDU sessions can be achieved.

[0004] This embodiment of the present application provides a session processing method, which is applied to a unified data management unit. The method includes:

[0005] Receive access management function registration requests sent by access management function units corresponding to different users to register;

[0006] receiving a session registration request from a first user among the different users sent by a session management function unit, and saving session information of the session registration request;

[0007] Feedback the session information to an access management function unit of at least one other user among the different users;

[0008] Feedback the session information to a session management function unit of at least one other user among the different users.

[0009] The present application also provides a session processing method, which is applied to an access management function unit. The method includes:

[0010] Obtaining the network slice selection information and the protocol data unit session information corresponding to the data network name from the unified data management functional unit;

[0011] Obtain a protocol data unit session establishment request from another user, wherein the session establishment request carries the network slice selection information, the data network name, and the protocol data unit session identifier;

[0012] Determining a target session management function unit according to the protocol data unit session information;

[0013] A protocol data unit session creation request is sent to the target session management function unit.

[0014] The present application also provides a session processing method, which is applied to a session management function unit. The method includes:

[0015] receiving a creation request for a second protocol data unit session of another user from the access management function unit, wherein the creation request carries at least network slice selection information and a data network name;

[0016] Requesting the unified data management function unit for the network slice selection information and the user subscription data corresponding to the data network name;

[0017] Acquire the user contract data and the permanent contract identifier of the first user requested by the unified data management function unit;

[0018] determining a session context of a first protocol data unit session according to the permanent user subscription identifier of the first user and the user subscription data;

[0019] The session policy and forwarding policy of the protocol data unit session are updated in the policy control function unit and the user plane function unit respectively according to the saved information of the session context of the first protocol data unit.

[0020] An embodiment of the present application further provides an electronic device, comprising:

[0021] one or more processors;

[0022] a memory for storing one or more programs;

[0023] When the first one or more programs are executed by the one or more processors, the one or more processors implement the session processing method as described in any one of the embodiments of the present application.

[0024] An embodiment of the present application further provides a computer-readable storage medium, wherein the computer-readable storage medium stores one or more programs, and the one or more programs are executed by one or more processors to implement the session processing method as described in any one of the embodiments of the present application.

[0025] It should be understood that the content described in this section is not intended to identify the key or important features of the embodiments of the present application, nor is it intended to limit the scope of the present application. Other features of the present application will become easily understood through the following description. BRIEF DESCRIPTION OF THE DRAWINGS

[0026] In order to more clearly illustrate the technical solutions in the embodiments of the present application, the following briefly introduces the drawings required for use in the description of the embodiments. Obviously, the drawings described below are only some embodiments of the present application. For ordinary technicians in this field, other drawings can be obtained based on these drawings without any creative work.

[0027] FIG1 is a system architecture diagram of a 5G system provided in an embodiment of the present application;

[0028] FIG2 is a flow chart of a session processing method provided in an embodiment of the present application;

[0029] FIG3 is an example diagram of a user registration process provided in an embodiment of the present application;

[0030] FIG4 is an example diagram of a process for creating a user-initiated PDU session provided in an embodiment of the present application;

[0031] FIG5 is a flowchart of another session processing method provided in an embodiment of the present application;

[0032] FIG6 is a flowchart of a session processing method provided in an embodiment of the present application;

[0033] FIG7 is a flowchart of another session processing method provided in an embodiment of the present application;

[0034] FIG8 is a flowchart of another session processing method provided in an embodiment of the present application;

[0035] FIG9 is an example diagram of the relationship between a mobile context and a session context provided in an embodiment of the present application;

[0036] FIG10 is an example diagram of a session processing method provided in an embodiment of the present application;

[0037] FIG11 is an example diagram of another session processing method provided in an embodiment of the present application;

[0038] FIG12 is a structural diagram of a session processing device provided in an embodiment of the present application;

[0039] FIG13 is a schematic structural diagram of another session processing device provided in an embodiment of the present application;

[0040] FIG14 is a schematic structural diagram of another session processing device provided in an embodiment of the present application;

[0041] FIG15 is a schematic structural diagram of an electronic device provided in an embodiment of the present application. DETAILED DESCRIPTION

[0042] It should be understood that the specific implementations described herein are only used to explain the present application and are not used to limit the present application.

[0043] In the subsequent description, suffixes such as "module", "component" or "unit" used to represent elements are only used to facilitate the description of this application and have no specific meaning. Therefore, "module", "component" or "unit" can be used interchangeably.

[0044] The embodiment of the present application is illustrated by taking the 5G system as an example. It is understandable that the same problem may also occur in the 6G system. Figure 1 is a system architecture diagram of a 5G system provided by the embodiment of the present application. In the embodiment of the present application, the 5G system architecture can be composed of terminal equipment (User Equipment, UE), radio access network (Radio Access Network, RAN), access management function (Access and Mobility Management function, AMF), unified data management function (Unified Data Management, UDM), SMF, user plane function (User Plane Function, UPF) and policy control function (Policy Control Function, PCF). Among them, the UE accesses the RAN through the Uu port and accesses the core network access and mobility management function (Access and Mobility Management Function, AMF) through the N1 interface. RAN is responsible for resource allocation of the Uu port and access control of the terminal. The AMF manages user access requirements and is responsible for functions such as terminal-to-network Non-Access Stratum (NAS) signaling and user mobility management. The UDM is the permanent storage location for user subscription data and is located in the user's home network. The SMF manages user PDU sessions and Quality of Service (QoS) flows, and establishes packet inspection and forwarding rules for the UPF. The SMF configures session policy control rules locally or receives them from the PCF. These control rules govern the data transmission path and QoS policy between the UPF and the terminal. Based on the rules issued by the SMF, the UPF is responsible for routing and forwarding Internet Protocol (IP) and non-IP data, as well as usage reporting. The PCF provides the SMF with session policy rules based on user subscriptions, application requirements, and local configuration. The PCF also sends User Equipment Route Selection Policy (URSP) rules to the terminal via the AMF, controlling the terminal's generation of appropriate PDU session parameters based on different application requests.

[0045] FIG2 is a flowchart of a session processing method provided in an embodiment of the present application. The embodiment of the present application can be applied to session processing in a scenario where multiple sessions are selected to the same SMF under a 5G system architecture, and is generally applied to UDM. The method can be executed by a session processing device, which can be implemented in software and / or hardware. Referring to FIG2 , the method provided in an embodiment of the present application specifically includes the following steps:

[0046] Step 110: Receive access management function registration requests sent by access management function units corresponding to different users to perform registration.

[0047] In an embodiment of the present application, different users may correspond to different access management function units (AMFs) respectively, and the UDM may receive access management function registration requests from different access management function units corresponding to different users. The UDM may register the user according to the access management function registration request. The registration may be a registration performed by the terminal of different users in the 5G system after being turned on.

[0048] Step 120: Receive a session registration request from a first user among different users sent by a session management function unit, and save session information of the session registration request.

[0049] The first user may be the user who first registers for a session among the users registered in the UDM, and the first user may select the SMF before other users.

[0050] In an embodiment of the present application, the UDM can receive a session registration request of the first user sent by the session management function unit (SMF), and the UDM can save the session information in the session registration request. The session registration request of the first user can be part of the process of creating a PDU session.

[0051] Step 130: Feedback the session information to the access management function unit of at least one other user among different users.

[0052] In an embodiment of the present application, the UDM can feed back the session information of the first user for session registration to the access management function unit of one or more other users among different users. The one or more other users may be users who select the same SMF as the first user.

[0053] Step 140: Feedback the session information to the session management functional unit of at least one other user among different users.

[0054] In the embodiment of the present application, the UDM may also feed back the session information to the session management functional units of one or more other users.

[0055] In some application embodiments, terminals of different users need to register with the network after powering on. Referring to FIG3 , a user registration process may be shown, which may specifically include the following steps:

[0056] 1. The UE sends a Registration Request to the RAN, which carries the user's encrypted subscription identifier (SUCI) or permanent subscription identifier (SUPI), requested network slice selection information (NSSAI), etc.

[0057] 2. RAN selects the appropriate AMF based on the NSSAI and other information requested by the user.

[0058] 3. RAN forwards the UE's registration request to the selected AMF.

[0059] 4. AMF initiates the authentication process for the UE. During this process, the AMF first selects a suitable authentication server function (AUSF) for the UE, and then initiates an authentication request to the AUSF. Then the AUSF initiates the identity authentication and authentication process for the UE. During this identity authentication and authentication process, the network authenticates the terminal, and the terminal also authenticates the network.

[0060] 5. After the authentication process is successful, the AMF selects the UDM for the UE based on the SUPI and then initiates a user subscription information request to the UDM.

[0061] 6. UDM sends subscription information and session-related information related to user mobility management to AMF, such as Single Network Slice Selection Assistance Information (S-NSSAI) and Data Network Name (DNN).

[0062] 7. AMF initiates an AMF registration request to UDM, carrying the user's current AMF identifier.

[0063] 8. UDM saves the AMF identity in the user context and returns a registration response to AMF.

[0064] 9-10. After the AMF successfully registers, it allocates a 5G Globally Unique Temporary Identifier (5G-GUTI) and the current registration area (RA) to the user, determines the S-NSSAI allowed for the user based on the contract information, and then returns a registration receive response (Registration Accept) to the UE, carrying the 5G-GUTI, RA, and the allowed S-NSSAI.

[0065] 11-12, After receiving the registration acceptance response from AMF, the UE saves the 5G-GUTI and RA, and then sends a registration acceptance message (Registration Complete) to the AMF through RAN.

[0066] In other application embodiments, after the user registers with the 5G system, the UE may initiate a PDU session creation process, and the UDM receiving the first user's session registration request sent by the session management function unit may be part of the PDU session creation process. Referring to FIG. 4 , the PDU session creation process may include the following process:

[0067] 1. The UE sends a PDU Session Establishment Request to the AMF via the RAN. This message carries the S-NSSAI, DNN, session and service continuity (SSC) mode, and the UE-assigned PDU session identifier of the PDU session. The UE determines the S-NSSAI, DNN, and SSC mode that the application can use based on local policy.

[0068] 2. AMF selects an appropriate SMF for the UE based on the UE's PDU session establishment request, such as the S-NSSAI and DNN requested by the UE.

[0069] 3. AMF sends a Create SMContext Request to SMF. The message carries the S-NSSAI, DNN and SSC mode requested by the UE, as well as the user's current access system information and location information.

[0070] 4. SMF initiates a request to the UDM to obtain the session subscription data, carrying the S-NSSAI and DNN requested by the UE.

[0071] 5. UDM returns the UE session subscription data of the S-NSSAI and DNN to SMF.

[0072] 6. SMF returns a Create SM Session Context Response (Create SMContext Response) to AMF.

[0073] 7. The SMF selects a suitable PCF and sends a session policy association creation request to the PCF, carrying the S-NSSAI and DNN requested by the UE, the user's current location information, and the user's access system information.

[0074] 8. The PCF obtains user subscription data from the User Data Repository (UDR), generates session policy information (SM Policy) based on local policies, and then returns the session policy data (SM Policy) to the SMF in response to the received SMF request;

[0075] 9. SMF selects the appropriate UPF based on S-NSSAI, DNN, UE location and other information, and then initiates an N4 Session Establishment Request to the UPF.

[0076] 10. The UPF responds to the SMF's request to establish an N4 session. The UPF allocates an uplink tunnel identifier for the PDU session and returns an N4 Session Establishment Response to the SMF.

[0077] 11. After the N4 session is successfully established, the SMF sends an N1 / N2 message transfer request (N1 / N2Message Transfer) to the AMF. The message carries a non-access stratum message (NAS) sent to the UE and an N2 session setup message (AS) sent to the RAN. The NAS message is the PDU Session Establishment Accept message, and the AS message is the context information of the PDU session, such as the created QoS flow configuration information list and the PDU session uplink tunnel identifier assigned by the UPF.

[0078] 12. The AMF sends an N2 PDU Session Request message to the RAN, which carries the NAS message and AS message received from the SMF.

[0079] 13. RAN sends an RRC reconfiguration process (Radio Resource Connection Reconfiguration) to the UE, establishes a suitable radio bearer for the UE based on the PDU session information provided by the SMF, and at the same time sends a NAS message to the UE.

[0080] 14. After creating the radio resources, the RAN returns an N2 interface PDU session reception (N2 PDU Session ack) message to the AMF, which carries the N3 interface resources allocated by the RAN for the PDU session, such as the downlink tunnel identifier.

[0081] 15-16. AMF sends an Update SMContext Request to SMF to update the RAN tunnel identifier of UPF on the N3 interface.

[0082] 17-18. SMF sends an N4 Session Update Request to UPF to update the tunnel identifier of the RAN on the N3 interface.

[0083] 19-20. The SMF may allocate an IP address to the terminal through the control plane or the user plane in step 11. The SMF then registers with the UDM, which stores the SMF address and the user IP address in the user session context corresponding to the S-NSSAI and DNN.

[0084] FIG5 is a flowchart of another session processing method provided by an embodiment of the present application. The embodiment of the present application is specific based on the above embodiment and is generally applied to UDM. Referring to FIG5 , the method provided by the embodiment of the present application specifically includes the following steps:

[0085] Step 210: Receive an access management function registration request sent by the access management function unit of the corresponding user, wherein the access function registration request at least carries the user's access information.

[0086] In an embodiment of the present application, the UDM may receive an access management function registration request sent by the access management function unit, and the access management function registration request may carry the user's access information.

[0087] Step 220: Save the access information to the user mobility context of the user.

[0088] In the embodiment of the present application, the UDM may save the access information to the user mobility context of the corresponding user. It is understandable that the access information of different users in the UDM may be saved to different user mobility contexts.

[0089] Furthermore, based on the above application embodiment, the access information includes an access management function identifier and a public land mobile network identifier.

[0090] In the embodiment of the present application, the UDM may save information such as the user's access management function identifier and public land mobile network identifier to the user mobility context of the user.

[0091] Step 230: Receive a session registration request from the first user sent by the session management function unit.

[0092] In an embodiment of the present application, the session management function unit may send a session registration request corresponding to the first user to the UDM, where the session registration request is used by the first user to request the creation of a PDU session.

[0093] Step 240: Save the session information of the session registration request in a user session context shared by different users.

[0094] The user session context may be shared by different users within the UDM, and the user session context may store session information related to the PDU session.

[0095] In the embodiment of the present application, the session information corresponding to the session registration request of the first user may be determined, and the session information may be saved in a user session context shared by all users in the UDM.

[0096] Step 250: Determine whether other users have registered with the access management functional units corresponding to other users.

[0097] In an embodiment of the present application, the UDM can determine whether other users within the user group have registered with their respective corresponding access management functional units. The determination can be made by the UDM by determining whether the user mobile context corresponding to each other user stores various corresponding access information. If so, it is determined that the other users have registered with the corresponding access management functional units.

[0098] Step 260: Send a user context modification request message to the access management function units corresponding to other users, wherein the user context modification request message carries at least session information of the first user among different users.

[0099] In an embodiment of the present application, if it is determined that another user has registered with a corresponding access management functional unit, the UDM may send a user context modification request message to the access management functional unit corresponding to the other user, where the user context modification request message includes the session information of the first user. Specifically, the session information of the first user may include one or more of network slice selection information, a data network name, and a session management functional unit address.

[0100] Step 270: Feedback the session information to the session management functional unit of at least one other user among different users.

[0101] In an embodiment of the present application, the UDM may also send the session information of the first user to the session management functional units of other users.

[0102] Based on the above-mentioned application embodiment, the session information includes at least one of the following: network slice selection information, data network name, session management function unit address, protocol data unit session identifier and user Internet Protocol address.

[0103] In some application embodiments, a session signing request message is received from a session management function unit of at least one other user among different users, wherein the session signing request message carries at least the network slice selection information and the data network name of the corresponding session; and the session signing data corresponding to the session signing request message is fed back to the session management function unit.

[0104] In an embodiment of the present application, the session management function unit of other users can send session signing request information to UDM. The session signing request information can carry the network slice selection information and data network name of the session requested to be created by other users. UDM can feedback the session signing data corresponding to the session signing request information to the session management function unit of the above-mentioned other users.

[0105] In some other application embodiments, the further step includes feeding back the permanent subscription identifier of the first user to the session management function unit of at least one other user among different users.

[0106] In some other application embodiments, the method further includes: feeding back the protocol data unit session information of the first user to the session management function unit of at least one other user among different users.

[0107] Specifically, UDM can also feedback the protocol data unit session information of the first user to the session management functional units corresponding to other users. The protocol data unit session information of the first user may include one or more of network slice selection information, data network name, and protocol data unit session identifier.

[0108] FIG6 is a flowchart of a session processing method provided in an embodiment of the present application. The embodiment of the present application can be applied to session processing in a scenario where multiple sessions are selected to the same SMF under a 5G system architecture, and is generally applied to AMF. The method can be executed by a session processing device, which can be implemented in software and / or hardware. Referring to FIG6 , the method provided in an embodiment of the present application specifically includes the following steps:

[0109] Step 310: Obtain the network slice selection information and the protocol data unit session information corresponding to the data network name from the unified data management functional unit.

[0110] In an embodiment of the present application, the unified data management function unit (UDM) can send protocol data unit session information to the AMF. The protocol data unit session information can be determined by the network slice selection information, the data network name and the session management function unit address. It can be understood that the network slice selection information and the data network name can be the network slice selection information, the data network name and the session management function unit address corresponding to the protocol data unit session requested to be created by the first user in the 5G or 6G system.

[0111] Step 320: Obtain a protocol data unit session establishment request from other users, where the session establishment request carries network slice selection information, data network name and protocol data unit session identifier.

[0112] In an embodiment of the present application, AMF can receive a protocol data unit session establishment request sent by other users, and the protocol data unit session establishment request can carry information such as network slice selection information, data network name and protocol data unit session identifier.

[0113] Step 330: Determine the target session management function unit according to the protocol data unit session information.

[0114] Specifically, the AMF can determine, through the received protocol data unit session information sent by other users and the protocol data unit session information of the first user obtained from the unified data management function unit in step 310, that the protocol data unit session requested by the other users can use the session management function unit shared by the first user as the target session management function unit, thereby allowing multiple users to select the same session management function unit.

[0115] Step 340: Send a protocol data unit session creation request to the target session management function unit.

[0116] In an embodiment of the present application, the AMF may send a protocol data unit session creation request to the selected target session management function unit, so that the user equipment corresponding to the AMF may create a protocol data unit within the target session management function unit.

[0117] In some application embodiments, determining a target session management function unit according to protocol data unit session information includes:

[0118] Determine the first protocol data unit session of the first user whose network slice selection information and data network name corresponding to the protocol data unit session information have been created; determine the session management function unit of the first protocol data unit session as the target session management function unit.

[0119] In an embodiment of the present application, AMF can determine the created protocol data unit session as the first protocol data unit session of the first user according to the network slice selection information and data network name corresponding to the protocol data session information, and use the session management function unit that manages the first protocol data unit session as the target session management function unit.

[0120] In some other application embodiments, sending a protocol data unit session creation request to a target session management function unit includes:

[0121] A protocol data unit session creation request is sent to the target session management functional unit, wherein the protocol data unit session creation request carries at least network slice selection information, data network name, user current location information and user access system information.

[0122] In an embodiment of the present application, the AMF may send a protocol data unit session creation request carrying information such as network slice selection information, data network name, user current location information, and user access system information to the target session management function unit, thereby requesting the target session management function unit to create a protocol data unit session for the user terminal corresponding to the AMF. It will be understood that since different terminals can be assigned the same or different protocol data unit session identifiers, the identifiers of the PDU sessions requested to be created by different terminals may be the same or different.

[0123] FIG7 is a flowchart of another session processing method provided by an embodiment of the present application. The embodiment of the present application can be applied to session processing in a scenario where multiple sessions are selected to the same SMF under a 5G system architecture. It is generally applied to SMF. The method can be executed by a session processing device, which can be implemented in software and / or hardware. Referring to FIG7 , the method provided by the embodiment of the present application specifically includes the following steps:

[0124] Step 410: Receive a creation request for a second protocol data unit session of another user from the access management function unit, wherein the creation request carries at least network slice selection information and a data network name.

[0125] In an embodiment of the present application, SMF can receive a creation request for a second protocol data unit session from the access management function unit corresponding to each user, and SMF can create a second protocol data unit session according to the creation request. The creation request can carry network slice selection information and a data network name.

[0126] Step 420: Request the unified data management functional unit for network slice selection information and user subscription data corresponding to the data network name.

[0127] In an embodiment of the present application, SMF can request corresponding contract data from the unified data management functional unit according to the network slice selection information and data network name.

[0128] Step 430: Obtain the user contract data requested by the unified data management function unit feedback, the user permanent contract identifier of the first user, and the first protocol data unit session identifier established by the first user corresponding to the network slice selection information and the data network name.

[0129] The first user may be a user corresponding to the first protocol data unit session, and the user may request to create the first protocol data unit session.

[0130] Specifically, the unified data management function unit can determine the corresponding user contract data according to the permanent contract identifier of the other user, the network slice selection information and the network data name, as well as the user permanent contract identifier of the first user and the session identifier of the first protocol data unit session of the first user stored in association with the above-mentioned network slice selection information, network data name, etc. The unified data management function unit can feed back the above-mentioned user contract data and the user permanent contract identifier of the first user and the first protocol data unit session identifier to the SMF, and the SMF can receive the requested user contract data and the user contract identifier and the first protocol data unit session identifier of the first user.

[0131] Step 440: Determine a session context of the first protocol data unit session of the first user according to the permanent user subscription identifier of the first user and the first protocol data unit session identifier.

[0132] In an embodiment of the present application, the SMF may determine the first protocol data unit session context of the first user according to the first user's permanent subscription identifier and the first protocol data unit session identifier, and use the first protocol data unit session context as the second protocol data unit session context of the other user. It is understandable that the second protocol data unit sessions created by different user requests in the SMF may share the same session context.

[0133] Step 450: Update the session policy and forwarding policy of the protocol data unit session in the policy control function unit and the user plane function unit respectively according to the saved information of the first protocol data unit session context.

[0134] In an embodiment of the present application, saved information may be extracted from the session context, and the session policy and forwarding policy in the policy control function unit and the user plane function unit may be updated respectively according to the saved information.

[0135] Based on the above application embodiment, the SMF can also receive the protocol data unit session information of the first user sent by the unified data management function unit, and determine the user session context corresponding to the first user according to the protocol data unit session information of the first user.

[0136] FIG8 is a flowchart of another session processing method provided in an embodiment of the present application. The embodiment of the present application is a specific embodiment based on the above embodiment. Referring to FIG8 , the method provided in the embodiment of the present application specifically includes the following steps:

[0137] Step 510: Receive a creation request for a second protocol data unit session of another user from the access management function unit, wherein the creation request carries at least network slice selection information and a data network name.

[0138] Step 520: Request the unified data management functional unit for network slice selection information and user subscription data corresponding to the data network name.

[0139] Step 530: Obtain the user contract data requested by the unified data management function unit and the permanent contract identifier of the first user.

[0140] Step 540: Search for the user context of the first user according to the permanent user subscription identifier of the first user.

[0141] In an embodiment of the present application, the SMF may search for the user context corresponding to the first user according to the permanent user subscription identifier of the first user.

[0142] Step 550: Search the first protocol data unit session context corresponding to the network slice selection information and the data network name in the user context of the first user as the session context of the second protocol data unit session.

[0143] Specifically, the corresponding first protocol data unit session context can be searched in the user context of the first user according to the network slice information and the data network name, and the first protocol data unit session context can be used as the session context of the second protocol data unit session.

[0144] Step 560: Extract policy control functional unit information and user plane functional unit information from the session context.

[0145] In an embodiment of the present application, policy control function unit information and user plane function unit information can be extracted in the session context. The policy control function unit information and user plane function unit information can be the aforementioned saved information. The policy control function unit information can be information indicating the policy control function unit, and can include the network address or number of the policy control function unit information, etc., and the user plane function unit information can be indication information indicating the user plane function unit, and can include the network address, user plane function unit number, etc.

[0146] Step 570: Send a session policy association update request to the policy control function unit according to the policy control function unit information to update the access information of the second protocol data unit session in the policy control function unit, and update the session policy according to the updated access information and the local policy of the policy control function unit.

[0147] In an embodiment of the present application, a session policy association update request can be sent to the policy control function unit according to the policy control function unit information, so that the policy control function unit can update the access information of the second protocol data unit according to the session policy association update request, and update the session policy of the policy control function unit according to the updated access information and local policy.

[0148] Step 580: Send an N4 session update request to the user plane function unit according to the user plane function unit information, so that the user plane function unit updates the forwarding strategy by allocating add and add tunnel identifiers to the first protocol data unit.

[0149] In an embodiment of the present application, an N4 session update request can be sent to the user plane function unit corresponding to the user plane function unit information. After receiving the N4 session update request, the user plane function unit can allocate upper and lower tunnel identifiers to the first protocol data unit, thereby realizing the forwarding strategy update of the user plane function unit.

[0150] Figure 9 is an example diagram of the relationship between a mobility context and a session context provided by an embodiment of the present application. In order to ensure that terminals with multiple access modes select the same SMF, it is necessary to save the mobility context and session context of different terminals in the UDM in the embodiment of the present application. Referring to Figure 9, an example of the relationship between the mobility context and session context of two terminals in the UDM is given. The two UEs are identified by SUPI 1 and SUPI2 respectively. The two UEs can register to different AMFs through different public land mobile networks (PLMNs), but only one AMF is allowed to be registered in a PLMN, and the mobility contexts are independent of each other. The session contexts of the two UEs are shared, that is, the UDM can find the PDU session information established by UE / SUPI1 in the UDM according to S-NSSAI+DNN based on UE / SUPI2+S-NSSAI+DNN as input information. The PDU session information includes S-NSSAI, DNN, and corresponding SMF identifiers and user IP addresses.

[0151] In an exemplary embodiment, after UE / SUPI1 establishes a PDU session, because the session context is shared in UDM, UDM needs to send PDU session information to another UE / SUPI2. Referring to FIG. 10 , the process may include the following:

[0152] 1. UE / SUPI1 registers with AMF1 through RAN1. During the registration process, AMF1 registers with UDM. UDM saves the PLMN1 and AMF1 addresses where UE / SUPI1 is registered in the user mobility context.

[0153] Specifically, the registration process may include: the UE / SUPI1 sends a Registration Request to the RAN. This message contains the user's encrypted Subscription Concealed Identifier (SUCI) or Subscription Permanent Identifier (SUPI), requested Network Slice Selection Assistance Information (NSSAI), and other information. The RAN selects an appropriate AMF1 based on the NSSAI and other information requested by the user. The RAN forwards the UE / SUPI1's Registration Request to the selected AMF1. The AMF1 initiates an authentication process for the UE / SUPI1. During this process, the AMF1 first selects an appropriate AUSF for the UE / SUPI1 and then initiates an authentication request to the AUSF. The AUSF then initiates an identity authentication and authorization process for the UE / SUPI1. During this authentication and authorization process, the network authenticates the terminal, and the terminal also authenticates the network. After successful authentication, the AMF1 selects a UDM for the UE based on the SUPI1 and then initiates a user subscription information request to the UDM. UDM sends subscription information and session-related information related to user mobility management, such as S-NSSAI and DNN, to AMF1. AMF1 initiates an AMF registration request to UDM, carrying the AMF identifier of the user's current AMF1. UDM saves the AMF identifier in the user context and then returns a registration response to AMF1. After AMF1 successfully registers, it allocates 5G-GUTI and current RA to the user, determines the S-NSSAI allowed for the user based on the subscription information, and then returns a registration acceptance response (Registration Accept) to UE / SUPI1, carrying 5G-GUTI, RA and allowed S-NSSAI. After receiving the registration acceptance response from AMF1, UE / SUPI1 saves the 5G-GUTI and RA, and then sends a registration acceptance message (Registration Complete) to AMF1 through RAN.

[0154] 2. UE / SUPI2 registers with AMF2 via RAN2. During the registration process, AMF2 registers with the UDM. The UDM stores the PLMN2 and AMF2 address of the UE / SUPI2 in the user mobility context. Refer to the registration process for UE / SUPI1 above. Note that PLMN1 and PLMN2 can be the same PLMN.

[0155] 3. UE / SUPI1 establishes PDU Session 1 through RAN1 / AMF1, with the PDU Session Establishment Request carrying the S-NSSAI and DNN. The PDU Session 1 establishment process may include: UE / SUPI1 sends a PDU Session Establishment Request to AMF1 through RAN1. This message carries the S-NSSAI, DNN, session and SSC mode for PDU Session 1, and the UE-assigned PDU Session Identifier. UE / SUPI1 determines the S-NSSAI, DNN, and SSC mode that can be used by the application based on local policy. AMF1 selects an appropriate SMF for UE / SUPI1 based on the PDU Session Establishment Request for PDU Session 1, such as the UE's requested S-NSSAI and DNN. AMF1 sends a Create SMContext Request to the SMF, carrying the UE / SUPI1's requested S-NSSAI, DNN, and SSC mode, as well as the user's current access system information and location information. SMF initiates a session subscription data acquisition request to UDM, carrying the S-NSSAI and DNN requested by UE / SUPI1. UDM returns the UE session subscription data of the S-NSSAI and DNN to SMF. SMF returns a Create SM Session Context Response (Create SMContext Response) to AMF1. SMF selects a suitable PCF, and then sends a session policy association creation request to the PCF, carrying the S-NSSAI and DNN requested by the UE, the user's current location information, and the user's access system information. PCF obtains the user subscription data from UDR, generates session policy information based on local policies, and then returns the session policy data to SMF in response to the received SMF request; SMF selects a suitable UPF based on information such as S-NSSAI, DNN, and UE location, and then initiates an N4 session establishment request to the UPF. The UPF responds to the SMF's request and establishes an N4 session. The UPF assigns an uplink tunnel identifier to the PDU session and returns an N4 session establishment response to the SMF. After the N4 session is successfully established, the SMF sends an N1 / N2 message transmission request to the AMF1, which carries the NAS message sent to the UE / SUPI1 and the N2 session establishment message AS sent to the RAN. The NAS message is the PDU session acceptance message, and the AS message is the context information of the PDU session, such as the created QoS flow configuration information list and the PDU session uplink tunnel identifier assigned by the UPF. The AMF1 sends an N2 interface PDU session request (N2PDU Session Request) message to the RAN1, which carries the NAS message and AS message received from the SMF.RAN1 sends an RRC reconfiguration procedure to UE / SUPI1, establishes a suitable radio bearer for UE / SUPI1 based on the PDU session information of PDU session 1 provided by the SMF, and sends a NAS message to UE / SUPI1. After establishing the radio resources, RAN1 returns an N2 interface PDU session receive message to AMF1, which carries the N3 interface resources allocated by the RAN for PDU session 1, such as the downlink tunnel identifier. AMF1 sends an Update SM Session Context Request to the SMF to update the UPF's RAN tunnel identifier on the N3 interface. The SMF sends an N4 Session Update Request to the UPF to update the RAN tunnel identifier on the N3 interface.

[0156] 4. SMF registers with UDM, and UDM saves the S-NSSAI, DNN, SMF address, and corresponding user IP address information in the session context.

[0157] 5. UDM returns a registration response to SMF.

[0158] 6. The UDM determines that UE / SUPI2 is registered with AMF2. The UDM sends a User Context Modify Request message to AMF2, which carries the S-NSSAI, DNN, and SMF address information. AMF2 locally stores the S-NSSAI, DNN, and corresponding SMF address information. Optionally, the UDM passes the UE / SUPI1 information to AMF2.

[0159] When PDU Session 1 corresponding to UE / SUPI1 is deleted, UDM needs to send a message to AMF2 requesting AMF to delete S-NSSAI, DNN and the corresponding SMF address information. If AMF2 determines that UE / SUPI2 does not currently have an established PDU Session with S-NSSAI, DNN, it will locally delete the SMF address information. If AMF2 determines that UE / SUPI2 currently has an established PDU Session with S-NSSAI, DNN, it will continue to retain the SMF address information.

[0160] FIG11 is an example diagram of another session processing method provided by an embodiment of the present application. UE / SUPI2 establishes PDU Session 2. AMF2 needs to select the same SMF for PDU Session 2 as the one established by UE / SUPI1 for PDU Session 1. Referring to FIG11 , the method provided by an embodiment of the present application specifically includes the following steps:

[0161] 1. UE / SUPI2 sends a PDU Session Establishment Request to RAN2. This message carries the S-NSSAI and DNN of the PDU session, and the PDU Session ID 2 assigned by UE / SUPI2. Because the PDU Session IDs are assigned by different terminals, PDU Session ID 2 may or may not be the same as PDU Session 1.

[0162] 2. RAN2 forwards the PDU session establishment request to AMF2.

[0163] 3. Based on the session information sent by UDM, AMF2 determines that the user has established PDU session 1 on the S-NSSAI and DNN, so it selects the same SMF as PDU session 1 to request PDU session 2.

[0164] 4.AMF2 sends a Create SMContext Request to SMF. The message carries the S-NSSAI and DNN requested by the UE, PDU session identifier 2, user access system 2 information, and user current location information.

[0165] 5.SMF initiates a session subscription data acquisition request to UDM, carrying the S-NSSAI and DNN requested by the UE.

[0166] 6. UDM returns the UE's session subscription data to SMF, where the session subscription data includes the subscription session information of S-NSSAI and DNN. At the same time, UDM sends the SUPI1 information to SMF. Optionally, UDM also sends the PDU session 1 information (for example, PDU session identifier 1) to SMF.

[0167] 7.SMF returns a Create SM Session Context Response (Create SMContext Response) to AMF2.

[0168] 8. The SMF receives the SUPI1 information from the UDM in step 6 above. Therefore, it finds the user context of SUPI1 based on SUPI1, and then finds the PDU session 1 context established by UE / SUPI1 through S-NSSAI+DNN or PDU session identifier 1 received from the UDM. The context of the PDU session 1 includes the PCF information and UPF information selected by the PDU session 1.

[0169] 9. The SMF sends a session policy association update request to the PCF to update the access information of the PDU session in the PCF, including access system 1 and access system 2. The PCF updates the session policy information (SM Policy) based on the access system information and local policy, and then returns the updated session policy information (SM Policy) to the SMF.

[0170] 10.SMF initiates an N4 Session Modification Request to the UPF.

[0171] 11. The UPF responds to the SMF's request, allocates an uplink tunnel identifier for PDU session 2, and returns an N4 Session Modification Response to the SMF.

[0172] 12. After the N4 session is successfully updated, the SMF sends an N1 / N2 message transfer request (N1 / N2Message Transfer) to the AMF2. The message carries a NAS message (Non-access stratum) sent to the UE and an AS message (N2 Session Setup) sent to the RAN. The NAS message is the PDU Session Establishment Accept message, and the AS message is the context information of the PDU session, such as the created QoS flow list and the uplink tunnel identifier assigned by the UPF to PDU Session 2.

[0173] 13.AMF sends an N2 interface PDU Session Request message to RAN2, which carries the NAS message and AS message received from SMF.

[0174] 14. RAN2 sends an RRC reconfiguration procedure (Radio Resource Connection Reconfiguration) to UE / SUPI2 and establishes an appropriate radio bearer for UE / SUPI2 based on the PDU session information provided by SMF.

[0175] 15. After creating the radio resources, RAN2 returns an N2 interface PDU session reception (N2 PDU Session ack) message to the AMF, which carries the N3 interface resources allocated by RAN2 for the PDU session, such as the downlink tunnel identifier.

[0176] 16-17.AMF2 sends an Update SM Context Request to SMF to update the tunnel identifier of RAN2 on the UPF N3 interface.

[0177] 18-19.SMF sends an N4 Session Update Request to the UPF to update the tunnel identifier of RAN2 on the N3 interface.

[0178] In an embodiment of the present application, the SMF may allocate an IP address to the terminal through the control plane in step 12, or may allocate an IP address to the terminal through the user plane. The IP address may be the same IP address that the SMF allocated to PDU session 1. At this time, because the SMF has already registered with the UDM, the SMF does not need to register with the UDM again. The SMF may also allocate a different IP address to PDU session 2. At this time, the SMF also needs to initiate a registration process with the UDM and bring the address information of PDU session 2 to the UDM for storage.

[0179] In the above embodiments, two different terminals have different SUPIs. For a single user, in the UDM, in addition to sharing the session context, the mobility context is also shared. In step 6, the UDM returns the UE's session subscription data to the SMF without SUPI1. In step 8, the SMF can find the context of PDU Session 1 based on the SUPI and S-NSSAI+DNN and associate PDU Session 1 with PDU Session 2.

[0180] Figure 12 is a schematic diagram of the structure of a session processing device provided in an embodiment of the present application. The device can execute the session processing method provided in any embodiment of the present application and has the corresponding functional modules and beneficial effects of the execution method. The device can be implemented by software and / or hardware and is generally applied to UDM. As shown in Figure 12, the device provided in an embodiment of the present application specifically includes:

[0181] The user registration module 610 is configured to receive access management function registration requests sent by access management function units corresponding to different users to perform registration.

[0182] The session registration module 620 is configured to receive a session registration request from a first user among different users sent by the session management function unit, and save session information of the session registration request.

[0183] The access feedback module 630 is configured to feed back session information to the access management functional unit of at least one other user among different users.

[0184] The session feedback module 640 is configured to feed back session information to a session management functional unit of at least one other user among different users.

[0185] In some application embodiments, the user registration module 610 is specifically configured to: receive an access management function registration request sent by an access management function unit corresponding to a user, wherein the access function registration request carries at least the user's access information;

[0186] The access information is saved in the user mobility context of the user.

[0187] In some application embodiments, the in-device access information includes an access management function identifier and a public land mobile network identifier.

[0188] In some application embodiments, the session registration module 620 includes at least:

[0189] The request receiving unit is configured to receive a session registration request of a first user sent by the session management function unit.

[0190] The session information saving unit is used to save the session information of the session registration request in a user session context shared by different users.

[0191] In some application embodiments, the session information in the session registration module 620 includes at least one of the following: network slice selection information, data network name, session management function unit address, protocol data unit session identifier and user Internet Protocol address.

[0192] In some application embodiments, the access feedback module 630 is specifically used to: determine that other users have registered with the access management functional unit corresponding to the other users; send a user context modification request message to the access management functional unit corresponding to the other users, wherein the user context modification request message carries at least the session information of the first user among different users.

[0193] In some application embodiments, the session information includes at least one of the following: the first user's permanent subscription identifier or device identifier, network slice selection information, data network name, and session management function unit address.

[0194] In some application embodiments, the session feedback module 640 is also specifically used to: receive session signing request information sent by the session management function unit of at least one other user among different users, wherein the session signing request information carries at least the network slice selection information and data network name of the corresponding session; and feedback the session signing data corresponding to the session signing request information to the session management function unit.

[0195] In some other application embodiments, the session feedback module 640 is further specifically configured to: feed back the permanent subscription identifier of the first user to the session management function unit of at least one other user among different users.

[0196] In some other application embodiments, the session feedback module 640 is further specifically configured to: feed back the protocol data unit session information of the first user to the session management function unit of at least one other user among different users.

[0197] Figure 13 is a schematic diagram of the structure of another session processing device provided in an embodiment of the present application. This device can execute the session processing method provided in any embodiment of the present application and has the corresponding functional modules and beneficial effects. This device can be implemented by software and / or hardware and is generally applied to AMF. As shown in Figure 13, the device provided in an embodiment of the present application specifically includes:

[0198] The session channel module 710 is used to obtain the network slice selection information and the protocol data unit session information corresponding to the data network name from the unified data management functional unit.

[0199] The session request module 720 is used to obtain a protocol data unit session establishment request from other users, wherein the session establishment request carries network slice selection information, data network name and protocol data unit session identifier.

[0200] The session management module 730 is configured to determine a target session management function unit according to the protocol data unit session information.

[0201] The session establishing module 740 is configured to send a protocol data unit session creation request to a target session management function unit.

[0202] In some application embodiments, the session management module 730 is specifically configured to: determine a first protocol data unit session of a first user having been created with network slice selection information and a data network name corresponding to the protocol data unit session information;

[0203] A session management function unit of the first protocol data unit session is determined as a target session management function unit.

[0204] In other application embodiments, the session establishment module 740 is specifically used to: send a protocol data unit session creation request to the target session management functional unit, wherein the protocol data unit session creation request carries at least network slice selection information, data network name, user current location information and user access system information.

[0205] Figure 14 is a schematic diagram of the structure of another session processing device provided in an embodiment of the present application. The device can execute the session processing method provided in any embodiment of the present application and has the corresponding functional modules and beneficial effects of the execution method. The device can be implemented by software and / or hardware and is generally applied to SMF. As shown in Figure 14, the device provided in an embodiment of the present application specifically includes:

[0206] The creation request module 810 is used to receive a creation request for a second protocol data unit session of another user from the access management functional unit, wherein the creation request carries at least network slice selection information and a data network name.

[0207] The contract data request module 820 is used to request the network slice selection information and user contract data corresponding to the data network name from the unified data management functional unit.

[0208] The data feedback receiving module 830 is configured to obtain the user contract data requested by the unified data management function unit and the permanent contract identifier of the first user.

[0209] The session context module 840 is configured to determine a session context of the first protocol data unit session according to the permanent user subscription identifier and user subscription data of the first user.

[0210] The session updating module 850 is configured to update the session policy and forwarding policy of the protocol data unit session in the policy control function unit and the user plane function unit respectively according to the saved information of the session context of the first protocol data unit.

[0211] In some application embodiments, the device further includes: an information acquisition module, configured to acquire the protocol data unit session information of the first user sent by the unified data management functional unit, and determine the user session context based on the protocol data unit session information of the first user.

[0212] In some application embodiments, the session context module 840 is specifically used to: search for the user context of the first user according to the user permanent subscription identifier of the first user; search for the first protocol data unit session context corresponding to the network slice selection information and the data network name in the user context of the first user as the session context of the second protocol data unit session.

[0213] In some application embodiments, the session update module 850 is specifically used to: extract policy control function unit information and user plane function unit information in the session context; send a session policy association update request to the policy control function unit according to the policy control function unit information to update the access information of the second protocol data unit session in the policy control function unit, and update the session policy based on the updated access information and the local policy of the policy control function unit; send an N4 session update request to the user plane function unit according to the user plane function unit information, so that the user plane function unit updates the forwarding strategy by allocating upper and lower tunnel identifiers to the first protocol data unit.

[0214] Figure 15 is a structural diagram of an electronic device provided in an embodiment of the present application, which electronic device includes a processor 10 and a memory 11; the number of processors 10 in the electronic device can be one or more, and Figure 15 takes one processor 10 as an example; the processor 10 and the memory 11 in the electronic device can be connected via a bus or other means, and Figure 15 takes connection via a bus as an example.

[0215] The memory 11, as a computer-readable storage medium, can be used to store software programs, computer executable programs, and modules, such as the modules corresponding to the apparatus in the embodiments of the present application (user registration module 610, session registration module 620, access feedback module 630, and session feedback module 640, or session channel module 710, session request module 720, session management module 730, and session establishment module 740, or creation request module 810, contract data request module 820, data feedback receiving module 830, session context module 840, and session update module 850). The processor 10 executes the various functional applications and data processing of the electronic device by running the software programs, instructions, and modules stored in the memory 11, thereby implementing the above-mentioned session processing method.

[0216] The memory 11 may mainly include a program storage area and a data storage area, wherein the program storage area may store an operating system and at least one application required for a function; the data storage area may store data created based on the use of the electronic device, etc. In addition, the memory 11 may include a high-speed random access memory and may also include a non-volatile memory, such as at least one disk storage device, a flash memory device, or other non-volatile solid-state storage device. In some instances, the memory 11 may further include a memory remotely located relative to the processor 10, and these remote memories may be connected to the electronic device via a network. Examples of the above-mentioned network include, but are not limited to, the Internet, an intranet, a local area network, a mobile communication network, and combinations thereof.

[0217] The present application also provides a storage medium containing computer-executable instructions. When the computer-executable instructions are executed by a computer processor, the computer-executable instructions are used to perform a session processing method. The method is applied to a unified data management functional unit and includes:

[0218] Receiving access management function registration requests sent by access management function units corresponding to different users to perform registration;

[0219] receiving a session registration request from a first user among the different users sent by a session management function unit, and saving session information of the session registration request;

[0220] Feedback the session information to an access management function unit of at least one other user among the different users;

[0221] Feedback the session information to a session management function unit of at least one other user among the different users.

[0222] and / or,

[0223] The computer executable instructions are used to perform a session processing method when executed by a computer processor. The method is applied to an access management functional unit and includes:

[0224] Obtaining the network slice selection information and the protocol data unit session information corresponding to the data network name from the unified data management functional unit;

[0225] Obtain a protocol data unit session establishment request from another user, wherein the session establishment request carries the network slice selection information, the data network name, and the protocol data unit session identifier;

[0226] Determining a target session management function unit according to the protocol data unit session information;

[0227] A protocol data unit session creation request is sent to the target session management function unit.

[0228] The computer executable instructions are used to perform a session processing method when executed by a computer processor. The method is applied to a session management functional unit and includes:

[0229] receiving a creation request for a second protocol data unit session of another user from the access management function unit, wherein the creation request carries at least network slice selection information and a data network name;

[0230] Requesting the unified data management function unit for the network slice selection information and the user subscription data corresponding to the data network name;

[0231] Acquire the user contract data and the permanent contract identifier of the first user requested by the unified data management function unit;

[0232] determining a session context of a first protocol data unit session according to the permanent user subscription identifier of the first user and the user subscription data;

[0233] The session policy and forwarding policy of the protocol data unit session are updated in the policy control function unit and the user plane function unit respectively according to the saved information of the session context of the first protocol data unit.

[0234] Through the above description of the implementation methods, those skilled in the art can clearly understand that the present application can be implemented with the help of software and necessary general-purpose hardware, and of course it can also be implemented with hardware, but in many cases the former is a better implementation method. Based on this understanding, the technical solution of the present application, or the part that contributes to the relevant technology, can be embodied in the form of a software product. The computer software product can be stored in a computer-readable storage medium, such as a computer floppy disk, read-only memory (ROM), random access memory (RAM), flash memory (FLASH), hard disk or optical disk, etc., including a number of instructions for enabling a computer device (which can be a personal computer, server, or network device, etc.) to execute the carrier aggregation method described in each embodiment of the present application.

[0235] It is worth noting that in the embodiments of the above-mentioned device, the various units and modules included are only divided according to functional logic, but are not limited to the above-mentioned division, as long as the corresponding functions can be achieved; in addition, the specific names of the functional units are only for the convenience of distinguishing each other, and are not used to limit the scope of protection of this application.

[0236] Those skilled in the art will appreciate that all or some of the steps, devices, and functional modules / units in the methods disclosed above may be implemented as software, firmware, hardware, or appropriate combinations thereof.

[0237] In a hardware implementation, the division between the functional modules / units mentioned in the above description does not necessarily correspond to the division of physical components; for example, a physical component may have multiple functions, or a function or step may be performed by several physical components in cooperation. Some or all of the physical components may be implemented as software executed by a processor, such as a central processing unit, a digital signal processor, or a microprocessor, or implemented as hardware, or implemented as an integrated circuit, such as an application-specific integrated circuit. The corresponding software may be distributed on a computer-readable medium, which may include computer storage media (or non-transitory media) and communication media (or temporary media). As is well known to those skilled in the art, the term computer storage media includes volatile and non-volatile, removable and non-removable media implemented in any method or technology for storing information (such as computer-readable instructions, data structures, program modules or other data). Computer storage media includes, but is not limited to, RAM, ROM, Electrically Erasable Programmable Read-Only Memory (EEPROM), flash memory or other memory technology, Compact Disc Read-Only Memory (CD-ROM), Digital Versatile Disc (DVD) or other optical disk storage, magnetic cassettes, magnetic tape, magnetic disk storage or other magnetic storage devices, or any other medium that can be used to store the desired information and can be accessed by a computer. In addition, it is well known to those skilled in the art that communication media generally embodies computer-readable instructions, data structures, program modules, or other data in a modulated data signal such as a carrier wave or other transport mechanism, and may include any information delivery media.

[0238] The above content describes the preferred embodiments of the present application with reference to the accompanying drawings, and does not limit the scope of the present application. Any modifications, equivalent substitutions, and improvements made by those skilled in the art without departing from the scope and essence of the present application should be within the scope of the present application.

Claims

1. A session processing method, applied to a unified data management functional unit, comprising: Receiving access management function registration requests sent by access management function units corresponding to different users to perform registration; receiving a session registration request from a first user among the different users sent by a session management function unit, and saving session information of the session registration request; Feedback the session information to an access management function unit of at least one other user among the different users; Feedback the session information to a session management function unit of at least one other user among the different users.

2. The method according to claim 1, wherein: The receiving access management function registration requests sent by access management function units corresponding to different users to perform registration at least includes: receiving the access management function registration request sent by the access management function unit corresponding to the user, wherein the access function registration request at least carries the access information of the user; The access information is saved in a user mobility context of the user.

3. The method according to claim 2, wherein: The access information includes an access management function identifier and a public land mobile network identifier.

4. The method according to claim 1, wherein: The receiving, from the session management function unit, a session registration request of the first user among the different users, and storing session information of the session registration request at least includes: receiving the session registration request of the first user sent by the session management function unit; The session information of the session registration request is saved in a user session context shared by the different users.

5. The method according to claim 4, wherein: The session information includes at least one of the following: Network slice selection information, data network name, session management function unit address, protocol data unit session identifier and user Internet Protocol address.

6. The method according to claim 1, wherein: Feedback of the session information to the access management function unit of at least one other user among the different users includes: Determining that the at least one other user has registered with the access management functional unit corresponding to the at least one other user; Send a user context modification request message to the access management function unit corresponding to the at least one other user, wherein the user context modification request message carries at least the session information of the first user among the different users.

7. The method according to claim 6, wherein: The session information includes at least one of the following: The permanent contract identification or device identification of the first user, network slice selection information, data network name, and session management function unit address.

8. The method according to claim 1, wherein: Feedback of session information to a session management function unit of at least one other user among the different users includes: Receiving the session signing request information sent by the session management function unit of at least one other user among the different users, wherein the session signing request information carries at least network slice selection information and a data network name of the corresponding session; Feedback the session signing data corresponding to the session signing request information to the session management function unit of at least one other user among the different users.

9. The method according to claim 8, further comprising: Feedback the permanent subscription identifier of the first user to the session management function unit of at least one other user among the different users.

10. The method according to claim 8, further comprising: Feedback the protocol data unit session information of the first user to the session management function unit of at least one other user among the different users.

11. A session processing method, the method being applied to an access management function unit, the method comprising: Obtaining the network slice selection information and the protocol data unit session information corresponding to the data network name from the unified data management functional unit; Obtain a protocol data unit session establishment request from another user, wherein the session establishment request carries the network slice selection information, the data network name, and the protocol data unit session identifier; Determining a target session management function unit according to the protocol data unit session information; A protocol data unit session creation request is sent to the target session management function unit.

12. The method according to claim 11, wherein: The determining of the target session management function unit according to the protocol data unit session information includes: Determine the first protocol data unit session of the first user created by the network slice selection information and the data network name corresponding to the protocol data unit session information; A session management function unit of the first protocol data unit session is determined as the target session management function unit.

13. The method according to claim 11, wherein: The sending a protocol data unit session creation request to the target session management function unit includes: A protocol data unit session creation request is sent to the target session management functional unit, wherein the protocol data unit session creation request carries at least network slice selection information, data network name, user current location information and user access system information.

14. A session processing method, the method being applied to a session management functional unit, the method comprising: receiving a creation request for a second protocol data unit session of another user from the access management function unit, wherein the creation request carries at least network slice selection information and a data network name; Requesting the unified data management function unit for the network slice selection information and the user subscription data corresponding to the data network name; Acquire the user contract data and the permanent contract identifier of the first user requested by the unified data management function unit; determining a session context of a first protocol data unit session according to the permanent user subscription identifier of the first user and the user subscription data; The session policy and forwarding policy of the first protocol data unit session are updated in the policy control function unit and the user plane function unit respectively according to the saved information of the session context of the first protocol data unit.

15. The method according to claim 14, further comprising: Acquire the protocol data unit session information of the first user sent by the unified data management function unit, and determine a user session context corresponding to the first user according to the protocol data unit session information of the first user.

16. The method according to claim 14, wherein: The determining the session context of the first protocol data unit session according to the permanent user subscription identifier of the first user and the user subscription data includes: searching for the user context of the first user according to the permanent subscription identifier of the first user; The first protocol data unit session context corresponding to the network slice selection information and the data network name is searched in the user context of the first user as the session context of the second protocol data unit session.

17. The method according to claim 14, wherein: The updating of the session policy and forwarding policy of the protocol data unit session in the policy control function unit and the user plane function unit respectively according to the saved information of the session context of the first protocol data unit includes: Extracting policy control function unit information and user plane function unit information in the session context; sending a session policy association update request to the policy control function unit according to the policy control function unit information to update access information of the second protocol data unit session in the policy control function unit, and updating the session policy according to the updated access information and the local policy of the policy control function unit; An N4 session update request is sent to the user plane function unit according to the user plane function unit information, so that the user plane function unit updates the forwarding strategy by allocating upper and lower tunnel identifiers for the first protocol data unit.

18. An electronic device comprising: at least one processor; a memory configured to store at least one program; When the at least one program is executed by the at least one processor, the at least one processor implements the session processing method according to any one of claims 1 to 17.

19. A computer-readable storage medium storing at least one program, wherein the at least one program is executed by at least one processor to implement the session processing method according to any one of claims 1 to 17.

Images