Session control method, functional entity, electronic device, and storage medium

Abstract

Embodiments of the present application provide a session control method, a functional entity, an electronic device and a storage medium, and relate to the technical field of communication. The method comprises: receiving a first message sent by a session management function entity, and performing access network resource configuration according to access network resource request information; the first message comprises session-related access network resource request information and core network user plane configuration request information; sending the core network user plane configuration request information to a core network user plane function entity, and receiving core network user plane configuration confirmation information replied by the core network user plane function entity according to the core network user plane configuration request information; and sending a second message to the session management function entity, wherein the second message comprises session-related access network resource confirmation information and core network user plane configuration confirmation information. The embodiments of the present application can shorten the time for establishing, modifying or releasing a PDU session using a satellite, and improve the efficiency of PDU session management.

Description

Technical Field

[0001] This application relates to the field of communication technology, and more specifically, to a session control method, a functional entity, an electronic device, and a storage medium. Background Technology

[0002] Fifth-generation mobile communication technology (5G) systems serve various scenarios, aiming to provide ubiquitous mobile network access and high-speed data transmission. Compared to terrestrial mobile communication networks, satellite communication utilizes high, medium, and low-Earth orbit satellites to achieve wide-area or even global coverage. Combining 5G systems with satellite communication technology can further achieve seamless global coverage. Current solutions for integrating satellites into 5G systems include: using satellites as part of the access network equipment (S-gNB) to provide access for user equipment (UE), or deploying some network functions (such as S-gNB and gateways, i.e., user plane functions (S-UPF)) on satellites.

[0003] When both the S-gNB and S-UPF are deployed on satellites, the ground-based Session Management Function (SMF) needs to interact with both the onboard S-UPF (represented by S-UPF) and the onboard S-gNB (represented by S-gNB) at least three times to complete the PDU session establishment process. This requires at least six signaling transmissions between the ground and the satellite, significantly increasing the signaling interaction time required to establish a PDU session. Similarly, the signaling interaction time required for other session management processes (such as PDU session modification and release) is also greatly extended due to the multiple signaling transmissions between the ground and the satellite. When a PDU session involves multiple S-gNBs / S-UPFs (e.g., using S-gNBs / S-UPFs on two satellites to establish a PDU session between two UEs), the number of signaling transmissions between the ground and the satellite will be even greater. It is evident that the existing PDU session management process has high signaling control latency in scenarios using S-gNB and S-UPF, which reduces the efficiency of session management and may even cause session management failure. Summary of the Invention

[0004] This application provides a session control method, functional entity, electronic device, and storage medium that overcomes or at least partially solves the above-mentioned problems.

[0005] Firstly, a session control method is provided, including:

[0006] The system receives a first message from the session management function entity and configures access network resources based on the access network resource request information. The first message includes the session-related access network resource request information and the core network user plane configuration request information.

[0007] Send the core network user plane configuration request information to the core network user plane function entity, and receive the core network user plane configuration confirmation information from the core network user plane function entity based on the core network user plane configuration request information;

[0008] A second message is sent to the session management function entity. The second message includes session-related access network resource confirmation information and core network user plane configuration confirmation information.

[0009] Secondly, a session control method is provided, including:

[0010] Receive a third message sent by the core network user plane function entity. The third message includes session-related access network resource request information. Configure access network resources according to the access network resource request information and generate access network resource confirmation information.

[0011] A fourth message is sent to the core network user plane function entity. The fourth message includes access network resource confirmation information.

[0012] Thirdly, a session control method is provided, including:

[0013] The system receives the first message sent by the session management function entity and performs core network user plane configuration based on the core network user plane configuration request information. The first message includes session-related access network resource request information and core network user plane configuration request information.

[0014] Send access network resource request information to the access network functional entity, and receive access network resource confirmation information from the access network functional entity based on the access network resource request information;

[0015] A second message is sent to the session management function entity. The second message includes session-related access network resource confirmation information and core network user plane configuration confirmation information.

[0016] Fourthly, a session control method is provided, including:

[0017] The system receives the fifth message sent by the access network functional entity and performs core network user plane configuration based on the core network user plane configuration request information. The fifth message includes session-related core network user plane configuration request information.

[0018] A sixth message is sent to the access network functional entity. The sixth message includes core network user plane configuration confirmation information.

[0019] Fifthly, a session control method is provided, including:

[0020] Send a first message to a preset functional entity. The first message includes session-related access network resource request information, core network user plane configuration request information, and indication information.

[0021] Receive a second message sent by a preset functional entity. The second message includes session-related access network resource confirmation information and core network user plane configuration confirmation information.

[0022] The instruction information is used to instruct the preset functional entity to send the core network user plane configuration request information to the first core network user plane functional entity, or to instruct the preset functional entity to send the access network resource request information to the access network functional entity.

[0023] Sixthly, an access network functional entity is provided, including:

[0024] The access-side first message receiving module is used to receive a first message sent by the session management function entity and to configure access network resources according to the access network resource request information; the first message includes the session-related access network resource request information and the core network user plane configuration request information.

[0025] The core configuration forwarding and receiving module is used to send the core network user plane configuration request information to the core network user plane function entity and receive the core network user plane configuration confirmation information replied by the core network user plane function entity according to the core network user plane configuration request information.

[0026] The access-side second message sending module is used to send a second message to the session management function entity. The second message includes access network resource confirmation information and core network user plane configuration confirmation information related to the session.

[0027] Seventhly, an access network functional entity is provided, including:

[0028] The third message receiving module is used to receive a third message sent by the core network user plane function entity, configure access network resources according to the access network resource request information, and generate access network resource confirmation information; the third message includes session-related access network resource request information.

[0029] The fourth message sending module is used to send a fourth message to the core network user plane function entity, the fourth message including access network resource confirmation information.

[0030] Eighthly, a core network user plane functional entity is provided, including:

[0031] The core-side first message receiving module is used to receive the first message sent by the session management function entity and perform core network user plane configuration according to the core network user plane configuration request information; the first message includes session-related access network resource request information and the core network user plane configuration request information.

[0032] The access request forwarding and receiving module is used to send the access network resource request information to the access network functional entity and receive the access network resource confirmation information replied by the access network functional entity based on the access network resource request information;

[0033] The core-side second message receiving module is used to send a second message to the session management function entity. The second message includes access network resource confirmation information and core network user plane configuration confirmation information related to the session.

[0034] Ninthly, a core network user plane functional entity is provided, including:

[0035] The fifth message receiving module is used to receive the fifth message sent by the access network functional entity and perform core network user plane configuration according to the core network user plane configuration request information; the fifth message includes session-related core network user plane configuration request information.

[0036] The sixth message sending module is used to send a sixth message to the access network functional entity, the sixth message including core network user plane configuration confirmation information.

[0037] Tenthly, a session management function entity is provided, including:

[0038] The first message sending module is used to send a first message to a preset functional entity. The first message includes session-related access network resource request information, core network user plane configuration request information, and indication information.

[0039] The second message receiving module is used to receive a second message sent by the preset functional entity. The second message includes the session-related access network resource confirmation information and the core network user plane configuration confirmation information.

[0040] The instruction information is used to instruct the preset functional entity to send the core network user plane configuration request information to the first core network user plane functional entity, or to instruct the preset functional entity to send the access network resource request information to the access network functional entity.

[0041] Eleventhly, a session control device is provided, including a memory, a transceiver, and a processor:

[0042] A memory for storing computer programs; a transceiver for sending and receiving data under the control of the processor; and a processor for reading the computer programs from the memory and executing the session control method described in any one of the first to fifth aspects above.

[0043] In a twelfth aspect, embodiments of this application provide an electronic device including a memory, a processor, and a computer program stored in the memory and executable on the processor, wherein the processor executes the program to implement the steps of the method provided in any one of the first to fifth aspects.

[0044] In a thirteenth aspect, embodiments of this application provide a computer-readable storage medium having a computer program stored thereon that, when executed by a processor, implements the steps of the method provided in any one of the first to fifth aspects.

[0045] In a fourteenth aspect, embodiments of this application provide a computer program that includes computer instructions stored in a computer-readable storage medium. When a processor of a computer device reads the computer instructions from the computer-readable storage medium, the processor executes the computer instructions, causing the computer device to perform steps that implement the method provided in the first aspect.

[0046] The session control method, functional entity, electronic device, and storage medium provided in this application embodiment receive a first message sent by a session management functional entity. This first message includes session-related access network resource request information and core network user plane configuration request information. This avoids the problem of excessive interactions caused by the session management functional entity separately sending access network resource request information and core network user plane configuration request information to the access network functional entity and core network user plane functional entity, respectively, in the prior art. The access network functional entity configures access network resources based on the access network resource request information, obtains access network resource confirmation information, and then sends the core network user plane configuration request information to the core network user plane functional entity. Upon receiving the core network user plane configuration confirmation information, a second message is generated and sent to the session management function entity. Since the second message includes session-related access network resource confirmation information and core network user plane configuration confirmation information, it only needs to interact with the session management function entity once. That is, the confirmation information generated by the two function entities (access network function entity and core network user plane function entity) is sent to the session management function entity together. Overall, compared with the existing technology, the signaling interaction between the ground (SMF) and the satellite (S-gNB, S-UPF or S-gNB / S-UPF) is reduced, thereby shortening the time for establishing, modifying or releasing PDU sessions using the satellite and improving the efficiency of PDU session management. Attached Figure Description

[0047] To more clearly illustrate the technical solutions in the embodiments of this application, the accompanying drawings used in the description of the embodiments of this application will be briefly introduced below.

[0048] Figure 1 A schematic diagram illustrating the process of establishing a 5G session in existing technologies;

[0049] Figure 2 This is a flowchart illustrating the session control method of this application on the access network functional entity side.

[0050] Figure 3 This is a flowchart illustrating the session control method of another embodiment of this application on the access network functional entity side.

[0051] Figure 4 This is a flowchart illustrating the session control method of this application on the user plane functional entity side of the core network.

[0052] Figure 5 This is a flowchart illustrating the session control method of another embodiment of this application on the user plane functional entity side of the core network.

[0053] Figure 6 This is a flowchart illustrating the session control method of this application on the session management function entity side.

[0054] Figure 7 This is an interactive diagram illustrating session management based on a single-satellite S-UPF according to an embodiment of this application.

[0055] Figure 8 This is an interactive diagram illustrating session management based on a single-satellite S-UPF according to an embodiment of this application.

[0056] Figure 9 This is an interactive diagram illustrating session management based on a single satellite's S-gNB / S-UPF, as described in an embodiment of this application.

[0057] Figure 10 This is an interactive diagram illustrating session management based on dual-satellite S-UPF according to an embodiment of this application;

[0058] Figure 11 This is an interactive diagram illustrating session management based on dual-satellite S-gNB / S-UPF according to an embodiment of this application.

[0059] Figure 12 This is a schematic diagram of the structure of the access network functional entity in an embodiment of this application;

[0060] Figure 13 This is a schematic diagram of the structure of an access network functional entity according to another embodiment of this application;

[0061] Figure 14This is a schematic diagram of the core network user plane functional entity in an embodiment of this application;

[0062] Figure 15 This is a schematic diagram of the core network user plane functional entity according to another embodiment of this application;

[0063] Figure 16 This is a schematic diagram of the structure of the session management function entity in an embodiment of this application;

[0064] Figure 17 This is a schematic diagram of the structure of the session control device according to an embodiment of this application;

[0065] Figure 18 This is a schematic diagram of the structure of an electronic device provided in an embodiment of this application. Detailed Implementation

[0066] The embodiments of this application are described in detail below. Examples of the embodiments are shown in the accompanying drawings, wherein the same or similar reference numerals denote the same or similar elements or elements having the same or similar functions throughout. The embodiments described below with reference to the accompanying drawings are exemplary and are only used to explain this application, and should not be construed as limiting this application.

[0067] Those skilled in the art will understand that, unless explicitly stated otherwise, the singular forms “a,” “an,” and “the” used herein may also include the plural forms. It should be further understood that the term “comprising” as used in the specification of this application means the presence of features, integers, steps, operations, elements, and / or components, but does not exclude the presence or addition of one or more other features, integers, steps, operations, elements, components, and / or groups thereof. It should be understood that when we say an element is “connected” or “coupled” to another element, it can be directly connected or coupled to the other element, or there may be intermediate elements. Furthermore, “connected” or “coupled” as used herein can include wireless connections or wireless couplings. The term “and / or” as used herein includes all or any units and all combinations of one or more associated listed items.

[0068] To make the objectives, technical solutions, and advantages of this application clearer, the embodiments of this application will be described in further detail below with reference to the accompanying drawings.

[0069] First, let's introduce and explain several terms used in this application:

[0070] The N1 interface is a Network Access Server (NAS) interface used to send NAS messages. The NAS messages sent are divided into two main categories: a) Mobility management messages, which are messages exchanged between the terminal and the Access and Mobility Management Function (AMF); b) Session management messages, which are messages exchanged between the terminal and the Session Management Function (SMF), Session Management Function (SMSF), and other NFs. It should be noted that session management NAS messages are carried on top of mobility management messages, and other session management messages also need to be forwarded and transparently transmitted through the AMF.

[0071] The N2 interface is used in 4G for the connection between E-NodeB and Mobility Management Entity (MME), and in 5G it is used to connect 5G base stations and the AMF of the core network, using the NG-AP protocol.

[0072] The N4 interface serves as a reference point between the SMF and S-UPF. This interface transmits both control plane and user plane messages. The control plane protocol has been replaced by PFCP, while the user plane protocol remains the same as in 4G, still using the GTP-U protocol.

[0073] The N9 interface, located between the two S-UPFs, is a 5G-encapsulated user plane interface that supports both 3GPP and non-3GPP access. When connecting via 3GPP, it uses the GTP-U protocol, while for non-3GPP connections, it uses other tunneling protocols.

[0074] Current solutions for integrating satellites into 5G systems include: providing UE access as part of the access network equipment (gS-gNB), or deploying some network functions (such as gS-gNB, gateway (i.e., user plane function S-UPF)) on the satellite. Please see [link to relevant documentation]. Figure 1 The figure exemplifies a schematic diagram of the 5G session establishment process in the prior art, as shown in the figure, including:

[0075] 1. The UE sends a PDU session establishment request to the SMF via gS-gNB and AMF.

[0076] 2-3. The SMF selects the S-UPF and sends an N4 session establishment request (based on the N4 interface) to the S-UPF, requesting the S-UPF to allocate CN tunnel information, IP address / prefix, and configure PDU session-related rules for this PDU session. The S-UPF sends the CN tunnel information and other parameters to the SMF via the N4 session establishment response.

[0077] 4. The SMF sends an N1N2 message transmission request (Namf_Communication_N1N2MessageTransfer request, transmitted via the N1 and N2 interfaces) to the AMF. This message carries parameters such as N2 information to be sent to the gS-gNB and N1 information to be sent to the UE (including the PDU session establishment and acceptance message). The N2 information sent to the gS-gNB carries CN tunnel information, QoS parameters (QoSProfile), etc.

[0078] 5. The AMF sends an N2 session request to gS-gNB, which carries the parameters and N1 information mentioned above in the N2 information.

[0079] 6. The gS-gNB configures the radio resources for this PDU session for the UE.

[0080] 7. gS-gNB sends an N2 session response to AMF, which carries gS-gNB tunnel information, accepted and / or rejected QFI, etc.

[0081] 8. The AMF sends a PDU session update request, Nsmf_PDUSession_UpdateSMContext, to the SMF, which carries N2 information (including parameters from the N2 session response).

[0082] 9-10. The SMF sends an N4 session modification request to the S-UPF, which carries the gS-gNB tunnel information. The S-UPF replies with an N4 session modification response.

[0083] 11. The SMF replies to the AMF with the PDU session update Nsmf_PDUSession_UpdateSMContext response.

[0084] 12. Complete other steps for establishing a PDU session, such as the SMF registering the relevant information of the PDU session with the UDM.

[0085] When both gS-gNB and S-UPF are deployed on satellites, the aforementioned PDU session establishment process requires the ground SMF to interact with the onboard S-UPF (represented by S-UPF) and gS-gNB (represented by S-gNB) at least three times to complete the PDU session establishment. This necessitates at least six signaling transmissions between the ground and satellite, significantly increasing the signaling interaction time required to establish a PDU session. Similarly, the signaling interaction time required for other session management processes (such as PDU session modification and release) is also greatly extended due to the multiple signaling transmissions between the ground and satellite. When a PDU session involves multiple S-gNBs / S-UPFs (e.g., using S-gNBs / S-UPFs on two satellites to establish a PDU session between two UEs), the number of signaling transmissions between the ground and satellite will be even greater. Therefore, the existing PDU session management process exhibits high signaling control latency in scenarios using S-gNBs and S-UPFs, reducing session management efficiency and potentially causing session management failures.

[0086] The session control method, apparatus, electronic device, and computer-readable storage medium provided in this application are intended to solve the above-mentioned technical problems of the prior art.

[0087] The technical solution of this application and how the technical solution of this application solves the above-mentioned technical problems are described in detail below with specific embodiments. These specific embodiments can be combined with each other, and the same or similar concepts or processes may not be described again in some embodiments. The embodiments of this application will now be described with reference to the accompanying drawings.

[0088] Please see Figure 2 The figure illustrates, by way of example, a flowchart of the session control method of this application embodiment on the access network functional entity side. It should be understood that the session control of this application embodiment can be accomplished by a core network user plane functional entity (e.g., S-UPF), an access network functional entity (e.g., S-gNB), or a functional entity with both access network and core network user plane functions on a single satellite. Alternatively, it can be accomplished by core network user plane functional entities, access network functional entities, or functional entities with both access network and core network user plane functions on different satellites (hereinafter referred to as S-gNB / S-UPF). As shown in the figure, the method includes:

[0089] S101. Receive the first message sent by the session management function entity, and configure access network resources according to the access network resource request information. The first message includes session-related access network resource request information and core network user plane configuration request information.

[0090] The access network resource request information in this application embodiment may include a request to an access network functional entity or a functional entity with access network functions to request session management, and the core network user plane configuration request information may include a request to a core network user plane functional entity or a core network user plane functional entity to request session management.

[0091] S102. Send the core network user plane configuration request information to the core network user plane function entity, and receive the core network user plane configuration confirmation information from the core network user plane function entity based on the core network user plane configuration request information.

[0092] After the access network function entity receives the first message sent by the session management function entity, it needs to process the access network resource request information, allocate the corresponding access network resources for the PDU session, and generate access network resource confirmation information. In addition, the access network function entity also needs to send the core network user plane configuration request information to the core network user plane function entity, which will then generate and return the core network user plane configuration confirmation information based on the core network user plane configuration request information.

[0093] S103. Send a second message to the session management function entity. The second message includes session-related access network resource confirmation information and core network user plane configuration confirmation information.

[0094] After receiving the core network user plane configuration confirmation information returned by the core network user plane function entity, the access network function entity can construct a second message by combining it with the access network resource confirmation information generated in step S101, and return the second message to the session management function entity.

[0095] The session control method in this embodiment of the application receives a first message sent by a session management function entity. This first message includes session-related access network resource request information and core network user plane configuration request information. This avoids the problem of excessive interactions caused by the session management function entity separately sending access network resource request information and core network user plane configuration request information to the access network function entity and core network user plane function entity, respectively, in the prior art. The access network function entity configures access network resources according to the access network resource request information, obtains access network resource confirmation information, and sends the core network user plane configuration request information to the core network user plane function entity. Upon receiving the core network user plane configuration request information... The second message, which generates the configuration confirmation information, is sent to the session management function entity. Since the second message includes session-related access network resource confirmation information and core network user plane configuration confirmation information, it only needs to interact with the session management function entity once. That is, the confirmation information generated by the two function entities (access network function entity and core network user plane function entity) is sent to the session management function entity together. Overall, compared with the existing technology, the signaling interaction between the ground (SMF) and the satellite (S-gNB, S-UPF or S-gNB / S-UPF) is reduced, thereby shortening the time for establishing, modifying or releasing PDU sessions using the satellite and improving the efficiency of PDU session management.

[0096] Based on the above embodiments, as an optional embodiment, sending the core network user plane configuration request information to the core network user plane function entity includes:

[0097] Send at least one parameter from the access network resource confirmation information and the core network user plane configuration request information to the core network user plane function entity, so as to instruct the core network user plane function entity to reply with the core network user plane configuration confirmation information based on at least one parameter from the access network resource confirmation information and the core network user plane configuration request information.

[0098] Specifically, in this application embodiment, the Quality of Service (QoS) information of the session received or rejected by the access network functional entity and / or the tunnel endpoint information of the session in the access network functional entity can be sent to the core network user plane functional entity in the access network resource confirmation information.

[0099] Please see Figure 3 The figure exemplifies a flowchart of a session control method according to another embodiment of this application on the access network functional entity side. As shown, the method includes:

[0100] S201. Receive the third message sent by the core network user plane function entity, configure access network resources according to the access network resource request information, and generate access network resource confirmation information; the third message includes session-related access network resource request information.

[0101] In this embodiment, the access network function entity does not interact directly with the session management function entity, but interacts with the core network user plane function entity. The access network function entity receives the third message sent by the core network user plane function entity, configures the access network resources according to the access network resource request information included in the third message, and generates access network resource confirmation information after the configuration is completed.

[0102] Specifically, for PDU session establishment, the access network functional entity (ANF) can configure its tunnel endpoint information and the Quality of Service (QoS) information for accepted or rejected sessions. For PDU session modification, the ANF can determine the QoS information for accepted or rejected sessions based on local resources and policies. Furthermore, for PDU session establishment or modification, the ANF initiates an RRC connection reconfiguration to the UE based on parameters such as QFI and QoS profile, enabling the UE to establish or update radio resources for one or more QoS flows for that PDU session.

[0103] For PDU session deletion, the access network functional entity can delete the session information stored in the access network functional entity, including tunnel endpoint information, quality of service (QoS) information, etc., and initiate RRC connection release to the UE so that the UE can release the radio resources of the PDU session.

[0104] S202. Send a fourth message to the core network user plane function entity. The fourth message includes access network resource confirmation information.

[0105] In this embodiment, the access network function entity further generates a fourth message based on the generated access network resource confirmation information and sends the fourth message to the core network user plane function entity. Since in this embodiment, the core network user plane function entity receives the session management function entity, as can be seen from the above embodiments, the core network user plane function entity can generate a second message based on the access network resource confirmation information in the received fourth message and combine it with the core network user plane configuration confirmation information it generates to return to the session management function entity. Compared with the prior art, this reduces the signaling interaction between the ground (SMF) and the satellite (S-gNB, S-UPF or S-gNB / S-UPF), thereby shortening the time for establishing, modifying or releasing PDU sessions using the satellite and improving the efficiency of PDU session management.

[0106] Based on the above embodiments, as an optional embodiment, the third message also includes at least one parameter in the core network user plane configuration confirmation information;

[0107] Configure access network resources based on access network resource request information, including:

[0108] Access network resources are configured based on at least one parameter in the core network user plane configuration confirmation information and access network resource request information.

[0109] Specifically, in this embodiment of the application, the access network functional entity can determine the quality of service (QoS) information of the sessions it accepts or rejects based on the data packet processing rules of the sessions received or rejected by the core network user plane functional entity, and the QoS information of the sessions contained in the access network resource request information. For example, it can determine which QoS flows (i.e., data flows that meet specific QoS requirements) it accepts or rejects. The access network functional entity can also determine the core network address to be sent for the uplink data of the PDU session (i.e., the data sent by the UE to the network) based on the tunnel endpoint information of the preset functional entity in the core network user plane.

[0110] Please see Figure 4 The figure illustrates, for example, a flowchart of the session control method of this application on the user plane functional entity side of the core network. As shown in the figure, the method includes:

[0111] S301. Receive the first message sent by the session management function entity, and perform core network user plane configuration according to the core network user plane configuration request information; the first message includes session-related access network resource request information and core network user plane configuration request information.

[0112] The access network resource request information in this application embodiment may include a request to an access network functional entity or a functional entity with access network functions to request session management, and the core network user plane configuration request information may include a request to a core network user plane functional entity or a core network user plane functional entity to request session management.

[0113] S302. Send the access network resource request information to the access network functional entity and receive the access network resource confirmation information replied by the access network functional entity based on the access network resource request information.

[0114] After the core network user plane function entity receives the first message sent by the session management function entity, it needs to process the core network user plane configuration request information, allocate the corresponding core network user plane resources for the PDU session, and generate core network user plane configuration confirmation information. In addition, the core network user plane function entity also needs to send the access network resource request information to the access network function entity, which will generate and return the access network resource configuration confirmation information based on the access network resource request information.

[0115] S303. Send a second message to the session management function entity. The second message includes session-related access network resource confirmation information and core network user plane configuration confirmation information.

[0116] After receiving the access network resource confirmation information returned by the access network function entity, the core network user plane function entity can construct a second message by combining it with the core network user plane configuration confirmation information generated in step S301, and return the second message to the session management function entity.

[0117] The session control method in this embodiment of the application receives a first message sent by a session management function entity. This first message includes session-related access network resource request information and core network user plane configuration request information. This avoids the problem of excessive interactions caused by the session management function entity separately sending access network resource request information and core network user plane configuration request information to the access network function entity and the core network user plane function entity, respectively, in the prior art. The core network user plane function entity performs core network user plane configuration based on the core network user plane configuration request information, obtains core network user plane configuration confirmation information, and sends the access network resource request information to the access network function entity. Upon receiving the access network resource request information, the method... The network resource confirmation information generates a second message and sends it to the session management function entity. Since the second message includes session-related access network resource confirmation information and core network user plane configuration confirmation information, it only needs to interact with the session management function entity once. That is, the confirmation information generated by the two function entities (access network function entity and core network user plane function entity) is sent to the session management function entity together. Overall, compared with the existing technology, the signaling interaction between the ground (SMF) and the satellite (S-gNB, S-UPF or S-gNB / S-UPF) is reduced, thereby shortening the time for establishing, modifying or releasing PDU sessions using the satellite and improving the efficiency of PDU session management.

[0118] Based on the above embodiments, as an optional embodiment, sending access network resource request information to the access network functional entity includes:

[0119] Send at least one parameter from the core network user plane configuration confirmation information and access network resource request information to the access network function entity, so as to instruct the access network function entity to reply with access network resource confirmation information based on at least one parameter from the core network user plane configuration confirmation information and access network resource request information.

[0120] In this embodiment of the application, the core network user plane function entity sends some parameters from the core network user plane configuration confirmation information and the access network resource request information to the access network function entity together. On the one hand, this reduces the interaction process compared to the prior art, and on the other hand, it enables the access network function entity to obtain access network resource confirmation information that better meets the session requirements based on the parameters in the core network user plane confirmation information.

[0121] Based on the above embodiments, as an optional embodiment, the core network user plane configuration confirmation information includes:

[0122] The rules for handling data packets of sessions that are accepted or rejected by the core network user plane functional entities;

[0123] The session contains tunnel endpoint information for the core network user plane functional entity.

[0124] Please see Figure 5 The figure exemplifies a flowchart of a session control method according to another embodiment of this application on the core network user plane functional entity side. As shown, the method includes:

[0125] S401. Receive the fifth message sent by the access network functional entity, configure the core network user plane according to the core network user plane configuration request information, and generate core network user plane confirmation information; the fifth message includes session-related core network user plane configuration request information.

[0126] In this embodiment of the application, the core network user plane function entity does not interact directly with the session management function entity, but interacts with the access network function entity. The core network user plane function entity receives the fifth message sent by the access network function entity, performs core network user plane resource configuration according to the core network user plane configuration request information included in the fifth message, and generates core network user plane confirmation information after the configuration is completed.

[0127] Specifically, the core network user plane function entity can allocate IP addresses / prefixes and allocate (or update) CN tunnel information based on the packet processing rules (PDR, QER, FAR, and URR) related to the PDU session in the core network user plane configuration request information.

[0128] Furthermore, the core network user plane function entity can also determine the packet processing rules related to the PDU session that are accepted or rejected based on the QFI accepted and / or rejected by the access network function entity.

[0129] The core network user plane function entity determines, based on the access network function entity tunnel information, to send the downlink data (i.e., the data sent from the network to the UE) of the PDU session to the access network address.

[0130] For PDU session modifications, the core network user plane function entity configures or updates the packet processing rules related to the PDU session and / or updates the CN tunnel information based on the core network user plane resource modification request information.

[0131] Furthermore, the core network user plane function entity can also determine the packet processing rules related to the accepted and / or rejected PDU session based on the QFI accepted and / or rejected by the access network function entity. The core network user plane function entity sends the N4 session modification response and / or updated CN tunnel information to the access network function entity. The N4 session modification response carries parameters such as the packet processing rules related to the accepted and / or rejected PDU session and the CN tunnel information.

[0132] For PDU session release, S-UPF learns the packet processing rules and CN tunnel information related to the PDU session to delete it based on the core network user plane resource release request.

[0133] S402. Send a sixth message to the access network functional entity. The sixth message includes core network user plane configuration confirmation information.

[0134] Specifically, the core network user plane function entity sends the core network user plane configuration confirmation information to the access network function entity. This confirmation information carries parameters such as the data packet processing rules related to accepting and / or rejecting the PDU session, and CN tunnel information. It's important to note that the S-gNB tunnel information and CN tunnel information correspond to the access network address and core network address of the N3 tunnel for this PDU session, respectively. The access network function entity determines the core network address to which the uplink data (i.e., data sent by the UE to the network) for this PDU session should be sent based on the CN tunnel information.

[0135] For PDU session modification, the access network functional entity determines the QFI to accept and / or reject based on local resources and policies. The access network functional entity sends the N4 session modification request, the accepted and / or rejected QFI, to the core network user plane functional entity.

[0136] In this embodiment, the core network user plane function entity further generates a sixth message based on the generated core network user plane configuration confirmation information and sends the sixth message to the access network function entity. Since in this embodiment, the access network function entity receives the session management function entity, as can be seen from the above embodiments, the access network function entity can generate a second message based on the core network user plane configuration confirmation information in the received sixth message and combine it with the access network resource confirmation information it generates, and return it to the session management function entity. Compared with the prior art, this reduces the signaling interaction between the ground (SMF) and the satellite (S-gNB, S-UPF, or S-gNB / S-UPF), thereby shortening the time for establishing, modifying, or releasing PDU sessions using the satellite and improving the efficiency of PDU session management.

[0137] Based on the above embodiments, as an optional embodiment, the fifth message also includes information about the second core network user plane functional entity.

[0138] It should be understood that if session control involves core network user plane functional entities of multiple satellites, the second functional entity also needs to forward the core network user plane configuration request information to the core network user plane functional entities of other satellites. Therefore, the fifth message also includes information about the second core network user plane functional entity, such as its address.

[0139] Before sending the fourth message to the access network function entity, it also includes:

[0140] Based on the information from the second core network user plane function entity, the session-related core network user plane configuration request information is sent to the second core network user plane function entity to instruct the second core network user plane function entity to perform core network user plane configuration according to the core network user plane configuration request information.

[0141] For multi-satellite session control scenarios, the fifth message also includes information about the second core network user plane functional entity. The purpose of this is to enable the first core network user plane functional entity to send the core network user plane configuration request information to the second core network user plane functional entity based on the information of the second core network user plane functional entity, so that the second core network user plane functional entity can perform core network user plane configuration based on the core network user plane configuration request information.

[0142] After the first core network user plane function entity forwards the core network user plane configuration request information to the second core network user plane function entity, it further receives the core network user plane configuration confirmation information sent by the second core network user plane function entity. Thus, the core network user plane configuration confirmation information contained in the second message includes the core network user plane configuration confirmation information of both core network user plane function entities.

[0143] Based on the above embodiments, as an optional embodiment, the fifth message includes at least one parameter in the access network resource confirmation information;

[0144] Configure the core network user plane based on the core network user plane configuration request information, including:

[0145] Core network user plane configuration is performed based on at least one parameter in the access network resource confirmation information and the core network user plane configuration request information.

[0146] Access network resource confirmation information includes at least one of the following parameters:

[0147] The Quality of Service (QoS) information of a session received or rejected by an access network functional entity;

[0148] The session's tunnel endpoint information within the access network functional entity;

[0149] Core network user plane configuration is performed based on at least one parameter in the access network resource confirmation information and the core network user plane configuration request information, including:

[0150] Based on the Quality of Service (QoS) information of sessions received or rejected by the access network functional entities, the packet processing rules for sessions received or rejected by the first core network user plane functional entities are determined; and / or,

[0151] The access network address to which the session data packet is sent is determined based on the tunnel endpoint information of the access network functional entity.

[0152] Please see Figure 6 The figure illustrates an exemplary flowchart of the session control method of this application on the session management function entity side. As shown, the method includes:

[0153] S501. Send a first message to a preset functional entity. The first message includes session-related access network resource request information, core network user plane configuration request information, and indication information.

[0154] S502, Receive a second message sent by a preset functional entity, the second message including session-related access network resource confirmation information and core network user plane configuration confirmation information;

[0155] The instruction information is used to instruct the preset functional entity to send the core network user plane configuration request information to the first core network user plane functional entity, or to instruct the preset functional entity to send the access network resource request information to the access network functional entity.

[0156] In other words, the session management function entity in this application embodiment can determine the response instruction information based on the capabilities of the preset function entity. If the preset function entity is the access network function entity, it is instructed to send the core network user plane configuration request information to the first core network user plane function entity. If the preset function entity is the core network user plane function entity, it is instructed to send the access network resource request information to the access network function entity. Then, the preset function entity obtains the access network resource confirmation information and the core network user plane configuration confirmation information, and returns it to the session management function entity.

[0157] The session control method of this application embodiment, by sending a first message including session-related access network resource request information, core network user plane configuration request information, and indication information, instructs the core network user plane configuration request information to be sent to a first core network user plane functional entity, or instructs a preset functional entity to send the access network resource request information to the access network functional entity. This avoids the problem of excessive interaction caused by the session management functional entity sending the access network resource request information and the core network user plane configuration request information to the access network functional entity and the core network user plane functional entity respectively in the prior art. Since the second message includes session-related access network resource confirmation information and core network user plane configuration confirmation information, it only needs to interact with the session management functional entity once, that is, send the confirmation information generated by the two functional entities (access network functional entity and core network user plane functional entity) to the session management functional entity together. Overall, compared with the prior art, it reduces the signaling interaction between the ground (SMF) and the satellite (S-gNB, S-UPF or S-gNB / S-UPF), thereby shortening the time for establishing, modifying or releasing PDU sessions using the satellite and improving the efficiency of PDU session management.

[0158] Based on the above embodiments, as an optional embodiment, before sending the first message to the preset functional entity, at least one of the following actions A to D is performed:

[0159] A. Determine the preset functional entity to support forwarding the core network user plane configuration request information in the first message to the first core network user plane functional entity.

[0160] If it is determined that the preset functional entity supports forwarding the core network user plane configuration request information to the core network user plane functional entity, then when sending the first message to the preset functional entity, the core network user plane configuration request information can be carried in the first message, and the preset functional entity can be instructed to forward the core network user plane configuration request information in the first message to the core network user plane functional entity.

[0161] B. Determine the preset functional entity that supports forwarding the access network resource request information in the first message to the access network functional entity.

[0162] If it is determined that the preset functional entity supports forwarding access network resource request information to the access network functional entity, then when sending the first message to the preset functional entity, the access network resource request information can be carried in the first message, and the preset functional entity can be instructed to forward the access network resource request information in the first message to the access network functional entity.

[0163] C. Determine the preset functional entities that support forwarding the core network user plane configuration request information in the first message to other core network user plane functional entities.

[0164] If it is determined that the preset functional entity supports forwarding the core network user plane configuration request information to other core network user plane functional entities, then when sending the first message to the preset functional entity, the core network user plane configuration request information that needs to be sent to other core network user plane functional entities can be carried in the first message, and the preset functional entity can be instructed to forward the core network user plane configuration request information in the first message to other core network user plane functional entities.

[0165] D. Determine the preset functional entities as functional entities with access network functions and core network user plane functions.

[0166] If the preset functional entity is determined to be a functional entity with access network function and core network user plane function, the preset functional entity can obviously generate the second message based on the first message. Therefore, in the single-satellite session control scenario, there is no need to instruct the preset functional entity to forward some information in the first message. However, in the multi-satellite session control scenario, it is necessary to instruct the preset functional entity to forward the core network user plane configuration request in the first message to other functional entities with access network function and core network user plane function, similar to the above action C.

[0167] Based on the above embodiments, as an optional embodiment, the access network resource request information in this application embodiment includes session-related access network resource establishment, modification, or release request information; the core network user plane configuration request information includes session-related core network user plane resource establishment, modification, or release request information.

[0168] In other words, the embodiments of this application can be applied to three scenarios: session establishment, session modification, and session release. Correspondingly:

[0169] The aforementioned session-related access network resource request information can be access network resource establishment request information, access network resource modification request information, or access network resource release request information. Specifically, the access network resource establishment request information is used to request the access network functional entity to establish access network resources related to the PDU session; the access network resource modification request information is used to request the access network functional entity to modify access network resources related to the PDU session; and the access network resource release request information is used to request the access network functional entity to release access network resources related to the PDU session. Correspondingly, the aforementioned session-related access network resource confirmation information can be access network resource establishment confirmation information, access network resource modification confirmation information, or access network resource release confirmation information.

[0170] The core network user plane configuration request information related to the aforementioned session can be core network user plane resource establishment information, core network user plane resource modification information, or core network user plane resource release information. Specifically, the core network user plane resource establishment information is used to request the core network user plane functional entity to establish core network user plane configuration information related to the PDU session; the core network user plane resource modification information is used to request the core network user plane functional entity to modify the core network user plane configuration information related to the PDU session; and the core network user plane resource release information is used to request the core network user plane functional entity to release the core network user plane configuration information related to the PDU session. Correspondingly, the core network user plane configuration confirmation information related to the aforementioned session can be core network user plane resource establishment confirmation information, core network user plane resource modification confirmation information, or core network user plane resource release confirmation information.

[0171] Please see Figure 7 The figure exemplifies an interactive diagram illustrating session management based on a single-satellite S-UPF according to an embodiment of this application, as shown in the figure, including:

[0172] 1. The UE or network initiates the establishment, modification, or release procedure of the PDU session through the S-gNB. Specifically, the UE sends a request to the SMF to establish, modify, or release the PDU session through the AMF; or, the SMF decides to initiate the establishment, modification, or release procedure of the UE's PDU session based on external triggering or local policies.

[0173] 2. The SMF selects the S-UPF sharing the same satellite as the S-gNB to establish the PDU session. The SMF sends an N1N2 message transmission request (Namf_Communication_N1N2MessageTransfer) or a PDU session update response (Nsmf_PDUSession_UpdateSMContext) to the AMF, which carries:

[0174] -S-UPF identifier or address (e.g., IP address or MAC address) is optional. If not included, N4 information is sent by default to the S-UPF that shares a satellite or address with the S-gNB.

[0175] - The N4 message sent to the S-UPF is used for: 1) requesting the configuration or deletion of Packet Detection Rule (PDR), Quality of Service Enforcement Rule (QER), Forwarding Action Rule (FAR), and Usage Reporting Rule (URR) related to the PDU session in the S-UPF; 2) requesting the allocation or updating of tunnel information; 3) requesting the allocation of IP address / prefix, etc. This N4 message can carry an N4 session establishment request, an N4 session modification request, or an N4 session release request. Specifically: for PDU session establishment, if the PDU session request type is "Initial Request," i.e., initial establishment of a PDU session, then the N4 message carries an N4 session establishment request; otherwise, it carries an N4 session modification request. For PDU session modification, the N4 message carries an N4 session modification request. For PDU session release, the N4 message carries an N4 session release request. The N4 session establishment request includes the PDU Session ID, PDR, QER, FAR, and URR, as well as parameters such as the requested IP address / prefix indication. The N4 session modification request includes the PDU Session ID, updated PDR, QER, FAR, and URR parameters. The N4 session release request includes the PDU Session ID.

[0176] - N2 information sent to the S-gNB is used to establish, modify, or release resources on the S-gNB associated with the PDU session. Specifically, for PDU session establishment or modification, the N2 information carries the PDU session identifier, the identifiers (QFIs) of one or more QoS flows of the PDU session and their corresponding QoS parameters (QoS Profiles), CN tunnel information, etc.; for PDU session release, the N2 information carries the PDU session identifier.

[0177] - N1 information sent to the UE, which includes NAS messages related to the PDU session, namely: PDU session establishment acceptance message, PDU session modification command, or PDU session release command message.

[0178] 3. The AMF sends an N2 PDU session resource establishment, modification or release request message to the S-gNB, which carries the S-UPF identifier or address, N4 information, parameters in the N2 information and N1 information.

[0179] 4-5. The S-gNB sends the N4 session establishment, modification, or release request contained in the N4 information to the S-UPF. Optionally, the S-gNB also sends other parameters to the S-UPF, such as the S-gNB N3 tunnel information, and the accepted and / or rejected QFI (i.e., accepting the establishment or modification of the QFI, and / or rejecting the establishment or modification of the QFI). The S-UPF sends the N4 session response to the S-gNB.

[0180] Specifically:

[0181] For PDU session establishment, the S-gNB allocates S-gNB N3 tunnel information for the PDU session and determines the QFI to be accepted and / or rejected based on local resources and policies. The S-gNB sends the S-gNB N3 tunnel information, the QFI to be accepted and / or rejected, and the N4 session establishment (or modification) request to the S-UPF.

[0182] Based on the N4 session establishment (or modification) request, the S-UPF configures the PDR, QER, FAR, and URR related to the PDU session, allocates IP addresses / prefixes, and allocates (or updates) CN tunnel information. Furthermore, the S-UPF can also determine the accepted and / or rejected PDR, QER, FAR, and URR related to the PDU session based on the QFI accepted and / or rejected by the S-gNB. The S-UPF sends the N4 session establishment (or modification) response to the S-gNB. The N4 session establishment (or modification) response carries parameters such as the accepted and / or rejected PDR, QER, FAR, and URR related to the PDU session, as well as CN tunnel information. Here, the S-gNB tunnel information and CN tunnel information correspond to the access network address and core network address of the N3 tunnel for this PDU session, respectively. Based on the S-gNB tunnel information, the S-UPF determines to send the downlink data (i.e., the data sent by the network to the UE) of the PDU session to the access network address; the S-gNB determines to send the uplink data (i.e., the data sent by the UE to the network) of the PDU session to the core network address based on the CN tunnel information provided by the S-UPF.

[0183] For PDU session modifications, the S-gNB determines the accepted and / or rejected QFIs based on local resources and policies. The S-gNB sends the N4 session modification request, along with the accepted and / or rejected QFIs, to the S-UPF. The S-UPF configures or updates the PDR, QER, FAR, and URR related to the PDU session based on the N4 session modification request, and / or updates the CN tunnel information. Furthermore, the S-UPF can also determine the accepted and / or rejected PDR, QER, FAR, and URR related to the PDU session based on the accepted and / or rejected QFIs from the S-gNB. The S-UPF sends the N4 session modification response and / or updated CN tunnel information to the S-gNB. The N4 session modification response carries parameters such as the accepted and / or rejected PDR, QER, FAR, and URR related to the PDU session, as well as the CN tunnel information.

[0184] - For PDU session release, the S-gNB sends an N4 session release request to the S-UPF. The S-UPF then deletes the PDR, QER, FAR, and URR associated with the PDU session, as well as the CN tunnel information, based on the N4 session release request. The S-UPF then sends an N4 session release response to the S-gNB.

[0185] 6. For PDU session establishment or modification, the S-gNB initiates RRC connection reconfiguration to the UE based on parameters such as QFI and QoS profile in the N2 information, establishing or updating radio resources for one or more QoS flows for the PDU session. For PDU session release, the S-gNB initiates RRC connection release to the UE, releasing the radio resources for the PDU session.

[0186] Furthermore, the S-gNB forwards the N1 information (i.e., the NAS message related to the PDU session in step 2) to the UE.

[0187] 7. The UE sends the N1 response to the S-gNB. The N1 response contains NAS response messages related to the PDU session, namely: PDU session establishment confirmation message, PDU session modification confirmation message, or PDU session release confirmation message.

[0188] 8. The S-gNB sends an N2 PDU session resource establishment, modification or release response to the AMF. This response carries the aforementioned N4 response, N1 response, and N2 related parameters (such as accepted and / or rejected QFI).

[0189] 9. The AMF will forward the N4 response, N1 response and N2 response containing the above-mentioned N2 related parameters received from the S-gNB to the SMF.

[0190] 10. For PDU session establishment or modification, if the SMF needs to update the N4 session of the PDU session with the S-UPF, steps 2-5 and 8-9 can be executed again. The N4 information carries the N4 session modification request, and the S-UPF sends the N4 session modification response to the SMF through the S-gNB and AMF. This completes the PDU session establishment, modification, or release process.

[0191] Please see Figure 8 The figure exemplifies an interactive diagram of session management based on a single-satellite S-UPF according to another embodiment of this application, as shown in the figure, including:

[0192] 1. The UE or network initiates the establishment, modification, or release procedure of the PDU session through the S-gNB. Specifically, the UE sends a request to the SMF to establish, modify, or release the PDU session through the AMF; or, the SMF decides to initiate the establishment, modification, or release procedure of the UE's PDU session based on external triggering or local policies.

[0193] 2. The SMF selects the S-UPF sharing the same satellite as the S-gNB to establish the PDU session. The SMF sends an N1N2 message transmission request (Namf_Communication_N1N2MessageTransfer) or a PDU session update response (Nsmf_PDUSession_UpdateSMContext) to the AMF, which carries:

[0194] -S-UPF identifier or address (e.g., IP address or MAC address) is optional. If not included, N4 information is sent by default to the S-UPF that shares a satellite or address with the S-gNB.

[0195] - The N4 message sent to the S-UPF is used for: 1) requesting the configuration or deletion of Packet Detection Rule (PDR), Quality of Service Enforcement Rule (QER), Forwarding Action Rule (FAR), and Usage Reporting Rule (URR) related to the PDU session in the S-UPF; 2) requesting the allocation or updating of tunnel information; 3) requesting the allocation of IP address / prefix, etc. This N4 message can carry an N4 session establishment request, an N4 session modification request, or an N4 session release request. Specifically: for PDU session establishment, if the PDU session request type is "Initial Request," i.e., initial establishment of a PDU session, then the N4 message carries an N4 session establishment request; otherwise, it carries an N4 session modification request. For PDU session modification, the N4 message carries an N4 session modification request. For PDU session release, the N4 message carries an N4 session release request. The N4 session establishment request includes the PDU Session ID, PDR, QER, FAR, and URR, as well as parameters such as the requested IP address / prefix indication. The N4 session modification request includes the PDU Session ID, updated PDR, QER, FAR, and URR parameters. The N4 session release request includes the PDU Session ID.

[0196] - N2 information sent to the S-gNB is used to establish, modify, or release resources on the S-gNB associated with the PDU session. Specifically, for PDU session establishment or modification, the N2 information carries the PDU session identifier, the identifiers (QFIs) of one or more QoS flows of the PDU session and their corresponding QoS parameters (QoS Profiles), CN tunnel information, etc.; for PDU session release, the N2 information carries the PDU session identifier.

[0197] - N1 information sent to the UE, which includes NAS messages related to the PDU session, namely: PDU session establishment acceptance message, PDU session modification command, or PDU session release command message.

[0198] 3. The AMF sends an N4 session establishment, modification or release request to the S-UPF, which carries N4 information, N2 information and N1 information, and may also carry the S-gNB identifier or address.

[0199] 4. Based on the N4 session establishment (or modification) request, S-UPF configures the packet processing rules (such as PDR, QER, FAR and URR) related to the PDU session, assigns IP address / prefix, and assigns (or updates) CN tunnel information.

[0200] S-UPF sends the N2 PDU session resource establishment, modification, or release request message contained in the N2 information to S-gNB.

[0201] The S-UPF will also send the CN tunnel information assigned (or updated) for this PDU session, and the QFI corresponding to the accept or reject packet processing rules, to the S-gNB.

[0202] Specifically:

[0203] For PDU session establishment, the S-UPF allocates CN tunnel information to the PDU session and determines the packet processing rules for acceptance and / or rejection based on local resources and policies. The S-UPF then sends the CN tunnel information, the QFI corresponding to the packet processing rules for acceptance and / or rejection, and the N2 PDU session resource establishment message to the S-gNB.

[0204] The S-gNB determines the core network address to which the uplink data (i.e., data sent by the UE to the network) of the PDU session will be sent based on the CN tunnel information provided by the S-UPF. The S-gNB allocates access network tunnel information for the PDU session. Based on the QoS flow information and QoS parameters of the PDU session contained in the N2PDU session resource establishment request message, the QFI corresponding to the accept and / or reject packet processing rules provided by the S-UPF, and local resources and policies, the S-gNB determines the accept and / or reject QFI.

[0205] - For PDU session modifications, the S-UPF determines the packet processing rules for acceptance and / or rejection based on local resources and policies. The S-UPF sends the QFI corresponding to the acceptance and / or rejection packet processing rules, along with the N2 PDU session resource modification message, to the S-gNB. The S-gNB determines the QFI for acceptance and / or rejection based on the updated QoS flow information and QoS parameters contained in the N2 PDU session resource modification message, the QFI corresponding to the acceptance and / or rejection packet processing rules provided by the S-UPF, and local resources and policies.

[0206] - For PDU session release, S-UPF sends an N2 PDU session resource creation, modification, or release request message to S-gNB. S-gNB deletes the S-gNB tunnel information associated with the PDU session based on the N2 PDU session resource release request message.

[0207] 5. For PDU session establishment or modification, the S-gNB initiates an RRC connection reconfiguration to the UE, establishing or updating radio resources for one or more QoS flows for the PDU session. For PDU session release, the S-gNB initiates an RRC connection release to the UE, releasing the radio resources for the PDU session.

[0208] Furthermore, the S-gNB forwards the N1 information (i.e., the NAS message related to the PDU session in step 2) to the UE.

[0209] 6. The UE sends the N1 response to the S-gNB. The N1 response contains NAS response messages related to the PDU session, namely: PDU session establishment confirmation message, PDU session modification confirmation message, or PDU session release confirmation message.

[0210] 7. The S-gNB sends an N2 PDU session resource establishment, modification, or release response to the S-UPF, which includes parameters such as the QFI accepted and / or rejected by the S-gNB and the access network tunnel information allocated by the S-gNB.

[0211] 8. The S-UPF sends an N4 response to the AMF, which carries the N2 and N1 responses mentioned above, as well as N4 related parameters (such as the CN tunnel information allocated (or updated) by the UPF, and the packet processing rules for acceptance or rejection).

[0212] 9. The AMF will forward the N4 response received from the S-UPF to the SMF.

[0213] 10. For PDU session establishment or modification, if the SMF needs to update the N4 session of the PDU session with the S-UPF, or request the S-gNB to update the access network resources of the PDU session, steps 2-9 can be executed again to complete the PDU session establishment, modification, or release process.

[0214] Please see Figure 9 The figure exemplifies an interactive diagram illustrating session management based on a single-satellite S-gNB / S-UPF according to an embodiment of this application.

[0215] 1. The UE or network initiates the establishment, modification, or release procedure of the PDU session through the S-gNB / S-UPF. Specifically, the UE sends a request to the SMF to establish, modify, or release the PDU session through the AMF; or, the SMF decides to initiate the establishment, modification, or release procedure of the UE's PDU session based on external triggering or local policies.

[0216] 2. The SMF selects the S-UPF sharing the same satellite as the S-gNB to establish the PDU session. The SMF sends an N1N2 message transmission request (Namf_Communication_N1N2MessageTransfer) or a PDU session update response (Nsmf_PDUSession_UpdateSMContext) to the AMF, which carries:

[0217] - The N2N4 message sent to the S-gNB / S-UPF is used for: 1) requesting the configuration or deletion of PDR, QER, FAR, and URR related to the PDU session in the S-gNB / S-UPF; 2) requesting the allocation of an IP address / prefix; 3) requesting the establishment, modification, or release of resources (e.g., radio resources) related to the PDU session on the S-gNB / S-UPF, etc. Specifically, for PDU session establishment or modification, the N2N4 message carries the following parameters: PDU session identifier, PDR, QER, FAR, and URR, identifiers (QFIs) of one or more QoS flows (QFIs) of the PDU session and their corresponding QoS parameters (QoS Profiles), and an indication of requesting the allocation of an IP address / prefix, etc.; for PDU session release, the N2N4 message carries the PDU session identifier.

[0218] - N1 information sent to the UE, which includes NAS messages related to the PDU session, namely: PDU session establishment acceptance message, PDU session modification command, or PDU session release command message.

[0219] 3. The AMF sends an N2N4 PDU session resource establishment, modification or release request message to the S-gNB / S-UPF, which carries the parameters and N1 information in the N2N4 information mentioned above.

[0220] Based on the N2N4 PDU session resource establishment, modification, or release request message, the S-gNB / S-UPF performs the following operations:

[0221] - For PDU session establishment, the S-gNB / S-UPF configures the PDR, QER, FAR and URR related to the PDU session, assigns IP address / prefix, and establishes resources related to the PDU session on the S-gNB / S-UPF.

[0222] - For PDU session modifications, the S-gNB / S-UPF updates the PDR, QER, FAR, and URR associated with the PDU session and updates the resources associated with the PDU session on the S-gNB / S-UPF.

[0223] - For PDU session release, the S-gNB / S-UPF deletes the PDR, QER, FAR and URR associated with the PDU session, and releases the tunnel information and resources (such as IP address / prefix, radio resources) associated with the PDU session on the S-gNB / S-UPF.

[0224] 4. For PDU session establishment or modification, the S-gNB / S-UPF initiates RRC connection reconfiguration to the UE based on parameters such as QFI and QoS profile in the N2N4 information, so that the UE can establish or update radio resources for one or more QoS flows for the PDU session. For PDU session release, the S-gNB / S-UPF initiates RRC connection release to the UE, so that the UE can release the radio resources for the PDU session.

[0225] Furthermore, the S-gNB / S-UPF forwards the N1 information (i.e., the NAS message related to the PDU session in step 2) to the UE.

[0226] 5. The UE sends the N1 response to the S-gNB / S-UPF. The N1 response contains NAS response messages related to the PDU session, namely: PDU session establishment confirmation message, PDU session modification confirmation message, or PDU session release confirmation message.

[0227] 6. The S-gNB / S-UPF sends an N2N4 PDU session resource establishment, modification, or release response to the AMF. This response carries N2N4 related parameters and the aforementioned N1 response. N2N4 related parameters include: accepted and / or rejected QFI, accepted and / or rejected PDR, QER, FAR, and URR, as well as the assigned IP address / prefix, etc.

[0228] 7. The AMF will forward the N1 response received from the S-gNB / S-UPF and the N2N4 response containing the above-mentioned N2 and N4 related parameters to the SMF.

[0229] 8. For PDU session establishment or modification, if the SMF needs to update the N4 session of the PDU session to the S-gNB / S-UPF, steps 2-3 and 6-7 can be executed again to complete the PDU session establishment, modification, or release process.

[0230] Please see Figure 10 The figure illustrates an exemplary interactive diagram of session management based on dual-satellite S-UPF according to an embodiment of this application.

[0231] 1. UE1 or the network initiates the establishment, modification, or release procedure of PDU session through S-gNB1 on satellite 1 (SAT1). Specifically, UE1 sends a request to SMF to establish, modify, or release PDU session through AMF; or, SMF decides to initiate the establishment, modification, or release procedure of UE1's PDU session based on external triggering or local policy.

[0232] 2. The SMF selects S-UPF1 on SAT1 (i.e., S-UPF1 shares a satellite with S-gNB1) and S-UPF2 on satellite 2 (SAT2) to establish the PDU session. Specifically, S-UPF1 is used to establish an N3 tunnel with S-gNB1, S-UPF2 is used to establish a user plane connection with the data network DN or the peer UE, and an N9 (or N19) tunnel is established between S-UPF1 and S-UPF2, thereby enabling UE1 to communicate with devices in the DN or the peer UE through S-gNB1, S-UPF1, and S-UPF2.

[0233] If there is no inter-satellite transmission link between S-UPF1 and S-UPF2, the SMF requests the network controller to establish an inter-satellite transmission link between S-UPF1 and S-UPF2.

[0234] 3. The SMF sends an N1N2 message transfer request (Namf_Communication_N1N2MessageTransfer) or a PDU session update response (Nsmf_PDUSession_UpdateSMContext) to the AMF, which carries the following information:

[0235] -S-UPF1 identifier or address (e.g., IP address or MAC address) is optional. If not included, N4 information is sent by default to the S-UPF1 that shares a satellite or address with S-gNB1.

[0236] - The N4 message sent to S-UPF1 is used for: 1) requesting the configuration or deletion of PDR, QER, FAR, and URR related to the PDU session in S-UPF1; 2) requesting S-UPF1 to allocate, update, or delete N3 tunnel information; 3) requesting S-UPF1 to allocate, update, or delete N9 (or N19) tunnel information, etc. This N4 message may carry an N4 session establishment request, an N4 session modification request, or an N4 session release request sent to S-UPF1. Specifically: For PDU session establishment, if the PDU session request type is "initial request," i.e., initial establishment of a PDU session, then the N4 message carries an N4 session establishment request sent to S-UPF1; otherwise, it carries an N4 session modification request. For PDU session modification, the N4 message carries an N4 session modification request sent to S-UPF1. For PDU session release, the N4 message carries an N4 session release request sent to S-UPF1. The N4 session establishment request includes parameters such as PDU Session ID, PDR, QER, FAR, and URR, and S-UPF2 identifier or address (e.g., IP address or MAC address). The N4 session modification request includes the PDU Session ID, updated PDR, QER, FAR, and URR parameters. The N4 session release request includes the PDU Session ID.

[0237] -S-UPF2 identifier or address (e.g., IP address or MAC address);

[0238] - The N4 message sent to S-UPF2 is used for: 1) requesting the configuration or deletion of PDR, QER, FAR, and URR related to the PDU session in S-UPF2; 2) requesting S-UPF2 to allocate or update N9 (or N19) tunnel information; 3) requesting S-UPF2 to allocate an IP address / prefix; etc. This N4 message can carry an N4 session establishment request, an N4 session modification request, or an N4 session release request sent to S-UPF2. Specifically: for PDU session establishment, if the PDU session request type is "Initial Request," i.e., initial establishment of a PDU session, then the N4 message carries an N4 session establishment request sent to S-UPF2; otherwise, it carries an N4 session modification request. For PDU session modification, the N4 message carries an N4 session modification request sent to S-UPF2. For PDU session release, the N4 message carries an N4 session release request sent to S-UPF2. The N4 session establishment request includes parameters such as PDU SessionID, PDR, QER, FAR, and URR, requesting the allocation of an IP address / prefix indicator, and S-UPF1 identifier or address (e.g., IP address or MAC address). The N4 session modification request includes the PDU Session ID, updated PDR, QER, FAR, and URR parameters. The N4 session release request includes the PDU Session ID.

[0239] - N2 information sent to S-gNB1 is used to establish, modify, or release resources on S-gNB1 related to the PDU session. Specifically, for PDU session establishment or modification, the N2 information carries the PDU session identifier, the identifiers (QFIs) of one or more QoS flows of the PDU session, and the corresponding QoS parameters (QoS Profiles), etc.; for PDU session release, the N2 information carries the PDU session identifier.

[0240] - N1 information sent to UE1, which includes NAS messages related to PDU sessions, namely: PDU session establishment acceptance message, PDU session modification command, or PDU session release command message.

[0241] 4. The AMF sends an N2 PDU session resource establishment, modification or release request message to S-gNB1, which carries the N4 information sent to S-UPF1, the S-UPF2 identifier or address, the N4 information sent to S-UPF2, the parameters in the N2 information and the N1 information.

[0242] 5. S-gNB1 sends an N4 request to S-UPF1, which includes the following parameters:

[0243] 1) The N4 session establishment, modification, or release requests included in the N4 information sent to S-UPF1 above;

[0244] 2) N4 information sent to S-UPF2;

[0245] 3) Other possible parameters, such as S-gNB N3 tunnel information, and QFI for acceptance and / or rejection.

[0246] Specifically:

[0247] For PDU session establishment, the S-gNB allocates S-gNB N3 tunnel information for the PDU session and determines the accepted and / or rejected QFIs based on local resources and policies. The S-gNB sends the S-gNB N3 tunnel information, the accepted and / or rejected QFIs, and the N4 session establishment (or modification) request to the S-UPF1. The S-UPF1 configures the PDR, QER, FAR, and URR related to the PDU session according to the N4 session establishment (or modification) request, and allocates (or updates) the CN tunnel information. Further, the S-UPF1 can also determine the accepted and / or rejected PDR, QER, FAR, and URR related to the PDU session based on the accepted and / or rejected QFIs of the S-gNB1. Here, the S-gNB tunnel information and CN tunnel information correspond to the access network address and core network address of the N3 tunnel of the PDU session, respectively. Based on the S-gNB1 tunnel information, S-UPF1 determines to send the downlink data (i.e., the data sent by the network to UE1) of the PDU session to the access network address; S-gNB1 determines to send the uplink data (i.e., the data sent by UE1 to the network) of the PDU session to the core network address based on the S-UPF1 tunnel information.

[0248] - For PDU session modifications, the S-gNB determines the accepted and / or rejected QFIs based on local resources and policies. The S-gNB sends the N4 session modification request, the accepted and / or rejected QFIs, to the S-UPF1. The S-UPF1 configures or updates the PDR, QER, FAR, and URR related to the PDU session based on the N4 session modification request, and / or updates the CN tunnel information. Furthermore, the S-UPF1 can also determine the accepted and / or rejected PDR, QER, FAR, and URR related to the PDU session based on the accepted and / or rejected QFIs from the S-gNB1.

[0249] - For PDU session release, S-gNB sends an N4 session release request to S-UPF1. S-UPF1 then deletes the PDR, QER, FAR, and URR associated with the PDU session, as well as the CN tunnel information, based on the N4 session release request.

[0250] 6. S-UPF1 sends a request message to S-UPF2, which includes the following parameters:

[0251] 1) The N4 session establishment, modification, or release requests included in the N4 information sent to S-UPF2;

[0252] 2) Other possible parameters, such as S-UPF1 N9 (or N19) tunnel information, PDR, QER, FAR and URR related to the PDU session that S-UPF1 accepts and / or rejects.

[0253] Specifically:

[0254] For PDU session establishment, S-UPF1 allocates S-UPF1 N9 (or N19) tunnel information for the PDU session and sends the S-UPF1 N9 (or N19) tunnel information, N4 session establishment (or modification) request, and the PDR, QER, FAR, and URR related to the PDU session that S-UPF1 accepts and / or rejects. S-UPF2 configures the PDR, QER, FAR, and URR related to the PDU session according to the N4 session establishment (or modification) request, allocates an IP address / prefix, and allocates S-UPF2 N9 (or N19) tunnel information. Furthermore, S-UPF2 can also determine the PDR, QER, FAR, and URR related to the PDU session that S-UPF2 accepts and / or rejects based on the QFI accepted and / or rejected by S-UPF1. Here, the S-UPF1 N9 (or N19) tunnel information and the S-UPF2 N9 (or N19) tunnel information correspond to the core network addresses of the two endpoints of the N9 (or N19) tunnel between S-UPF1 and S-UPF2 in this PDU session, respectively. S-UPF2 determines to send the downlink data of this PDU session (i.e., the data sent by the peer UE or network to UE1) to this core network address based on the S-UPF1 tunnel information; S-UPF1 determines to send the uplink data of this PDU session (i.e., the data sent by UE1 to the peer UE or network) to this core network address based on the S-UPF2 tunnel information.

[0255] For PDU session modifications, S-UPF1 sends an N4 session modification request, along with the PDR, QER, FAR, and URR associated with the PDU session that S-UPF1 accepts and / or rejects. S-UPF2 configures or updates the PDR, QER, FAR, and URR associated with the PDU session based on the N4 session modification request, and / or the S-UPF2 N9 (or N19) tunnel information. Furthermore, S-UPF2 can also determine the PDR, QER, FAR, and URR associated with the PDU session that S-UPF2 accepts and / or rejects based on the QFIs accepted and / or rejected by S-UPF1.

[0256] - For PDU session release, S-UPF1 sends an N4 session release request to S-UPF2. S-UPF2 deletes the PDR, QER, FAR, and URR associated with the PDU session, as well as the S-UPF2 N9 (or N19) tunnel information, based on the N4 session release request.

[0257] 7. S-UPF2 sends a response message to S-UPF1, which includes the following parameters:

[0258] 1) S-UPF2 N4 session establishment, modification, or release response. The N4 session establishment or modification response carries parameters such as PDR, QER, FAR, and URR related to the PDU session that S-UPF2 accepts and / or rejects, as well as S-UPF2 N9 (or N19) tunnel information.

[0259] 2) Other possible parameters, such as S-UPF2 N9 (or N19) tunnel information.

[0260] 8. S-UPF1 sends a response message to S-gNB1, which includes the following parameters:

[0261] 1) S-UPF1 N4 session establishment, modification, or release response. The N4 session establishment or modification response carries parameters such as PDR, QER, FAR, and URR related to the PDU session accepted and / or rejected by S-UPF1, as well as S-UPF1 N9 (or N19) tunnel information.

[0262] 2) Other possible parameters, such as CN tunnel information, S-UPF1 N9 (or N19) tunnel information.

[0263] 9. For PDU session establishment or modification, S-gNB1 initiates RRC connection reconfiguration to UE1 based on parameters such as QFI and QoS profile in the N2 information, so that UE1 can establish or update radio resources for one or more QoS flows for the PDU session. For PDU session release, S-gNB1 initiates RRC connection release to UE1, so that UE1 can release the radio resources for the PDU session.

[0264] Furthermore, S-gNB1 forwards the N1 information (i.e., the NAS message related to the PDU session in step 3) to UE1.

[0265] 10. UE1 sends the N1 response to S-gNB1. The N1 response contains NAS response messages related to the PDU session, namely: PDU session establishment confirmation message, PDU session modification confirmation message, or PDU session release confirmation message.

[0266] 11. S-gNB1 sends an N2 PDU session resource establishment, modification or release response to AMF. This response carries the N4 response of S-UPF1, the N4 response of S-UPF2, the N1 response, and N2 related parameters (e.g., QFI accepted and / or rejected).

[0267] 12. The AMF will forward the N4 response from S-UPF1, the N4 response from S-UPF2, the N1 response, and the N2 response containing the above-mentioned N2 related parameters received from S-gNB1 to the SMF.

[0268] 13. For PDU session establishment or modification, if the SMF needs to update the N4 session of the PDU session to S-UPF1 and / or S-UPF2, steps 2-8 and 11-12 can be executed again. The N4 information carries the N4 session modification request, and S-UPF1 and / or S-UPF2 send the N4 session modification response to the SMF via S-gNB and AMF. This completes the PDU session establishment, modification, or release process.

[0269] Please see Figure 11 The figure exemplifies an interactive diagram illustrating session management based on dual-satellite S-gNB / S-UPF according to an embodiment of this application.

[0270] 1. UE1 or the network initiates the establishment, modification, or release procedure of PDU session through S-gNB / S-UPF1 on satellite 1 (SAT1). Specifically, UE1 sends a request to SMF to establish, modify, or release PDU session through AMF; or, SMF decides to initiate the establishment, modification, or release procedure of UE1's PDU session based on external triggering or local policy.

[0271] 2. SMF selects S-gNB / S-UPF1 on SAT1 and S-gNB / S-UPF12 on satellite 2 (SAT2) to establish the PDU session.

[0272] If there is no inter-satellite transmission link between S-gNB / S-UPF11 and S-gNB / S-UPF12, the SMF requests the network controller to establish an inter-satellite transmission link between S-gNB / S-UPF11 and S-gNB / S-UPF12.

[0273] 3. The SMF sends an N1N2 message transfer request (Namf_Communication_N1N2MessageTransfer) or a PDU session update response (Nsmf_PDUSession_UpdateSMContext) to the AMF, which carries the following information:

[0274] - The N2N4 message sent to S-gNB1 / S-UPF1 is used for: 1) requesting the configuration or deletion of PDR, QER, FAR, and URR related to the PDU session in S-gNB1 / S-UPF1; 2) requesting the establishment, modification, or release of resources (e.g., radio resources) related to the PDU session on S-gNB1 / S-UPF1; 3) requesting S-gNB1 / S-UPF1 to allocate, update, or delete N9 (or N19) tunnel information, etc. Specifically, for PDU session establishment or modification, the N2N4 message carries the following parameters: PDU session identifier, PDR, QER, FAR, and URR, identifiers (QFI) of one or more QoS flows (QFI) of the PDU session and the corresponding QoS parameters (QoSProfile), identifier or address (e.g., IP address or MAC address) of S-gNB2 / S-UPF2, etc.; for PDU session release, the N2N4 message carries the PDU session identifier.

[0275] -S-gNB2 / S-UPF2 identifier or address (e.g., IP address or MAC address);

[0276] - N2N4 messages sent to S-gNB2 / S-UPF2 are used for: 1) requesting the configuration or deletion of PDR, QER, FAR, and URR related to the PDU session in S-gNB2 / S-UPF2; 2) requesting S-UPF2 to allocate or update N9 (or N19) tunnel information; 3) requesting the allocation of IP address / prefix; 4) requesting the establishment, modification, or release of resources (e.g., radio resources) related to the PDU session on S-gNB2 / S-UPF2, if S-gNB2 / S-UPF2 is connected to the peer UE; etc. Specifically, for the establishment or modification of a PDU session, the N2N4 information may carry the following parameters: PDU session identifier, PDR, QER, FAR and URR, identifiers (QFI) of one or more QoS flows of the PDU session and corresponding QoS parameters (QoS Profile), request for IP address / prefix allocation indication, identifier or address of S-gNB1 / S-UPF1 (e.g., IP address or MAC address), etc.; for the release of a PDU session, the N2N4 information carries the PDU session identifier.

[0277] - N1 information sent to UE1, which includes NAS messages related to PDU sessions, namely: PDU session establishment acceptance message, PDU session modification command, or PDU session release command message.

[0278] 3. The AMF sends an N2N4 request message to S-gNB1 / S-UPF1, which carries the parameters in the N2N4 information sent to S-gNB1 / S-UPF1, the S-gNB2 / S-UPF2 identifier or address, the N2N4 information and N1 information sent to S-gNB2 / S-UPF2.

[0279] 4. Based on the N2N4 request message received from the AMF, S-gNB1 / S-UPF1 performs the following operations:

[0280] - For PDU session establishment, S-gNB1 / S-UPF1 configures the PDR, QER, FAR and URR related to the PDU session, allocates S-gNB1 / S-UPF1 N9 (or N19) tunnel information, and establishes resources related to the PDU session on S-gNB / S-UPF.

[0281] - For PDU session modifications, S-gNB1 / S-UPF1 updates the PDR, QER, FAR and URR related to the PDU session, S-gNB1 / S-UPF1 N9 (or N19) tunnel information, and / or resources related to the PDU session on S-gNB / S-UPF.

[0282] - For PDU session release, S-gNB1 / S-UPF1 deletes the PDR, QER, FAR and URR associated with the PDU session, and releases the tunnel information and resources (such as radio resources) associated with the PDU session on S-gNB1 / S-UPF1.

[0283] S-gNB1 / S-UPF1 sends an N2N4 request message to S-gNB2 / S-UPF2, which carries parameters such as: N2N4 information for S-gNB2 / S-UPF2 carried in the N2N4 request message from AMF, and S-gNB1 / S-UPF1 N9 (or N19) tunnel information (if S-gNB1 / S-UPF1 has allocated or updated this tunnel information).

[0284] 5. Based on the N2N4 request message received from S-gNB1 / S-UPF1, S-gNB2 / S-UPF2 performs the following operations:

[0285] - For PDU session establishment, S-gNB2 / S-UPF2 configures the PDR, QER, FAR, and URR related to the PDU session and allocates S-gNB2 / S-UPF2 N9 (or N19) tunnel information. Furthermore:

[0286] a) If S-gNB2 / S-UPF2 is connected to DN, S-gNB2 / S-UPF2 assigns an IP address / prefix to the PDU session of UE1;

[0287] b) If S-gNB2 / S-UPF2 is connected to the peer UE, S-gNB2 / S-UPF2 establishes radio resources related to the PDU session on S-gNB2 / S-UPF2 according to QFI and the corresponding QoS Profile.

[0288] - For PDU session modifications, the S-gNB2 / S-UPF2 updates the PDR, QER, FAR, and URR related to the PDU session, and / or the S-gNB2 / S-UPF2 N9 (or N19) tunnel information. Furthermore, if the S-gNB2 / S-UPF2 is connected to the peer UE, the S-gNB2 / S-UPF2 updates the radio resources related to the PDU session on the S-gNB2 / S-UPF2 according to the QFI and the corresponding QoS Profile.

[0289] - For PDU session release, S-gNB2 / S-UPF2 deletes the PDR, QER, FAR and URR associated with the PDU session, and releases the tunnel information and resources (such as IP address / prefix or radio resources) associated with the PDU session on S-gNB2 / S-UPF2.

[0290] 6. S-gNB2 / S-UPF2 replies to S-gNB1 / S-UPF2 with an N2N4 response message, which carries:

[0291] 1) N2N4 response information sent to SMF. Specifically, for PDU session establishment or modification, the N2N4 response information may carry the following parameters: PDU session identifier, assigned IP address / prefix indication, accepted or rejected QFI, etc.; for PDU session release, the N2N4 response information carries the PDU session identifier.

[0292] 2) Other possible parameters, such as S-gNB2 / S-UPF2 N9 (or N19) tunnel information.

[0293] 6. For PDU session establishment or modification, S-gNB1 / S-UPF1 initiates RRC connection reconfiguration to UE1 based on parameters such as QFI and QoS profile in the N2N4 information, so that UE1 can establish or update radio resources for one or more QoS flows for the PDU session. For PDU session release, S-gNB1 / S-UPF1 initiates RRC connection release to UE1, so that UE1 can release the radio resources for the PDU session.

[0294] Furthermore, S-gNB1 / S-UPF1 forwards the N1 information (i.e., the NAS message related to the PDU session in step 2) to UE1.

[0295] 7. UE1 sends the N1 response to S-gNB1 / S-UPF1. The N1 response contains NAS response messages related to the PDU session, namely: PDU session establishment confirmation message, PDU session modification confirmation message, or PDU session release confirmation message.

[0296] 8. S-gNB1 / S-UPF1 sends an N2N4 PDU session resource establishment, modification, or release response to the AMF. This response carries the N2N4 related parameters of S-gNB1 / S-UPF1, the N2N4 response information of S-gNB2 / S-UPF2, and the aforementioned N1 response. The N2N4 related parameters of S-gNB1 / S-UPF1 include: QFIs accepted and / or rejected by S-gNB1 / S-UPF1, etc.

[0297] 9. The AMF will forward the N2N4 response information of S-gNB1 / S-UPF1, the N2N4 response information of S-gNB2 / S-UPF2, and the N1 response received from S-gNB1 / S-UPF1 containing the above-mentioned N2N4 related parameters to the SMF.

[0298] 10. For PDU session establishment or modification, if the SMF needs to update the N4 session of the PDU session to S-gNB1 / S-UPF1 and / or S-gNB2 / S-UPF2, steps 2-5 and 8-9 can be executed again to complete the PDU session establishment, modification, or release process.

[0299] This application provides an access network functional entity, such as... Figure 12 As shown, the access network functional entity may include: an access-side first message receiving module 101, a core configuration forwarding receiving module 102, and an access-side second message sending module 103, specifically:

[0300] The access-side first message receiving module 101 is used to receive the first message sent by the session management function entity and configure the access network resources according to the access network resource request information; the first message includes session-related access network resource request information and core network user plane configuration request information.

[0301] The core configuration forwarding and receiving module 102 is used to send core network user plane configuration request information to the core network user plane function entity and receive core network user plane configuration confirmation information from the core network user plane function entity based on the core network user plane configuration request information.

[0302] The access-side second message sending module 103 is used to send a second message to the session management function entity. The second message includes session-related access network resource confirmation information and core network user plane configuration confirmation information.

[0303] The access network functional entity provided in this application embodiment specifically executes the process described in the above method embodiment. For details, please refer to the embodiment of the session control method on the access network functional entity side; further details will not be repeated here. The access network functional entity provided in this application embodiment receives a first message sent by the session management functional entity. This first message includes session-related access network resource request information and core network user plane configuration request information. This avoids the problem of excessive interactions caused by the session management functional entity separately sending access network resource request information and core network user plane configuration request information to the access network functional entity and core network user plane functional entity, respectively, in the prior art. The access network functional entity configures access network resources according to the access network resource request information, obtains access network resource confirmation information, and sends the core network user plane configuration request information to the core network user plane functional entity. Upon receiving the core network user plane configuration request information, the access network functional entity performs access network resource configuration based on the access network resource request information, obtains access network resource confirmation information, and sends the core network user plane configuration request information to the core network user plane functional entity. The user plane configuration confirmation information generates a second message and sends it to the session management function entity. Since the second message includes session-related access network resource confirmation information and core network user plane configuration confirmation information, it only needs to interact with the session management function entity once. That is, the confirmation information generated by the two function entities (access network function entity and core network user plane function entity) is sent to the session management function entity together. Overall, compared with the existing technology, the signaling interaction between the ground (SMF) and the satellite (S-gNB, S-UPF or S-gNB / S-UPF) is reduced, thereby shortening the time for establishing, modifying or releasing PDU sessions using the satellite and improving the efficiency of PDU session management.

[0304] This application provides an access network functional entity, such as... Figure 13 As shown, the access network functional entity may include: a third message receiving module 201 and a fourth message sending module 202, specifically:

[0305] The third message receiving module 201 is used to receive the third message sent by the core network user plane function entity, configure the access network resources according to the access network resource request information, and generate access network resource confirmation information; the third message includes session-related access network resource request information.

[0306] The fourth message sending module 202 is used to send a fourth message to the core network user plane function entity. The fourth message includes access network resource confirmation information.

[0307] The access network functional entity provided in this application embodiment specifically executes the process described in the above method embodiment. For details, please refer to the content of the above-described session control method embodiment on the access network functional entity side, which will not be repeated here. The access network functional entity provided in this application embodiment interacts with the core network user plane functional entity. The access network functional entity receives a third message sent by the core network user plane functional entity, configures access network resources according to the access network resource request information included in the third message, and generates access network resource confirmation information after the configuration is completed. Compared with the prior art, this reduces the signaling interaction between the ground (SMF) and the satellite (S-gNB, S-UPF or S-gNB / S-UPF), thereby shortening the time for establishing, modifying or releasing PDU sessions using the satellite and improving the efficiency of PDU session management.

[0308] This application provides a core network user plane functional entity, such as... Figure 14 As shown, the core network user plane functional entity may include: a core-side first message receiving module 301, an access request forwarding and receiving module 302, and a core-side second message receiving module 303, specifically:

[0309] The core-side first message receiving module 301 is used to receive the first message sent by the session management function entity and perform core network user plane configuration according to the core network user plane configuration request information; the first message includes session-related access network resource request information and core network user plane configuration request information.

[0310] The access request forwarding and receiving module 302 is used to send access network resource request information to the access network functional entity and receive access network resource confirmation information from the access network functional entity based on the access network resource request information.

[0311] The core-side second message receiving module 303 is used to send a second message to the session management function entity. The second message includes session-related access network resource confirmation information and core network user plane configuration confirmation information.

[0312] The core network user plane function entity provided in this application embodiment specifically executes the process described in the above method embodiment. For details, please refer to the embodiment of the session control method on the core network user plane function entity side; further details will not be repeated here. The core network user plane function entity provided in this application embodiment receives a first message sent by the session management function entity. This first message includes session-related access network resource request information and core network user plane configuration request information. This avoids the problem of excessive interactions caused by the session management function entity separately sending access network resource request information and core network user plane configuration request information to the access network function entity and core network user plane function entity, respectively, in the prior art. The core network user plane function entity performs core network user plane configuration based on the core network user plane configuration request information, obtains core network user plane configuration confirmation information, and sends the access network resource request information to the access network function entity. The second message, generated from the access network resource confirmation information, is sent to the session management function entity. Since the second message includes session-related access network resource confirmation information and core network user plane configuration confirmation information, it only needs to interact with the session management function entity once. That is, the confirmation information generated by the two function entities (access network function entity and core network user plane function entity) is sent to the session management function entity together. Overall, compared with the existing technology, the signaling interaction between the ground (SMF) and the satellite (S-gNB, S-UPF or S-gNB / S-UPF) is reduced, thereby shortening the time for establishing, modifying or releasing PDU sessions using the satellite and improving the efficiency of PDU session management.

[0313] This application provides a core network user plane functional entity, such as... Figure 15 As shown, the core network user plane functional entity may include: a fifth message receiving module 401 and a sixth message sending module 402, specifically:

[0314] The fifth message receiving module 401 is used to receive the fifth message sent by the access network functional entity and perform core network user plane configuration according to the core network user plane configuration request information; the fifth message includes session-related core network user plane configuration request information.

[0315] The sixth message sending module 402 is used to send a sixth message to the access network functional entity. The sixth message includes core network user plane configuration confirmation information.

[0316] The core network user plane functional entity provided in this application embodiment specifically executes the process described in the above method embodiment. For details, please refer to the content of the embodiment of the session control method on the core network user plane functional entity side, which will not be repeated here. Compared with the prior art, the core network user plane functional entity provided in this application embodiment reduces the signaling interaction between the ground (SMF) and the satellite (S-gNB, S-UPF, or S-gNB / S-UPF), thereby shortening the time for establishing, modifying, or releasing PDU sessions using the satellite and improving the efficiency of PDU session management.

[0317] This application provides a session management function entity, such as... Figure 16 As shown, the session management function entity may include: a first message sending module 501 and a second message receiving module 502, specifically:

[0318] The first message sending module 501 is used to send a first message to a preset functional entity. The first message includes session-related access network resource request information, core network user plane configuration request information, and indication information.

[0319] The second message receiving module 502 is used to receive a second message sent by a preset functional entity. The second message includes session-related access network resource confirmation information and core network user plane configuration confirmation information.

[0320] The instruction information is used to instruct the preset functional entity to send the core network user plane configuration request information to the first core network user plane functional entity, or to instruct the preset functional entity to send the access network resource request information to the access network functional entity.

[0321] The session management function entity provided in this application embodiment specifically executes the process described in the above method embodiment. For details, please refer to the content of the above-described embodiment of the session control method on the session management function entity side, which will not be repeated here. The session management function entity provided in this application embodiment sends a first message, which includes session-related access network resource request information, core network user plane configuration request information, and indication information. This message instructs the core network user plane configuration request information to be sent to a first core network user plane function entity, or instructs a preset function entity to send the access network resource request information to the access network function entity. This avoids the problem of excessive interactions caused by the session management function entity sending access network resource request information and core network user plane configuration request information to the access network function entity and the core network user plane function entity respectively in the prior art. Since the second message includes session-related access network resource confirmation information and core network user plane configuration confirmation information, it only needs to interact with the session management function entity once, that is, send the confirmation information generated by the two function entities (access network function entity and core network user plane function entity) to the session management function entity together. Overall, compared with the prior art, it reduces the signaling interaction between the ground (SMF) and the satellite (S-gNB, S-UPF or S-gNB / S-UPF), thereby shortening the time for establishing, modifying or releasing PDU sessions using the satellite and improving the efficiency of PDU session management.

[0322] like Figure 17 As shown, embodiments of this application also provide a session control device, including a memory 1020, a transceiver 1040, and a processor 1010;

[0323] Memory 1020 is used to store computer programs;

[0324] Transceiver 1040 is used to receive and send data under the control of processor 1010;

[0325] Processor 1010 is used to read computer programs from memory 1020 and perform the following operations:

[0326] Receive the first message sent by the session management function entity, and configure access network resources according to the access network resource request information; the first message includes session-related access network resource request information and core network user plane configuration request information.

[0327] Send the core network user plane configuration request information to the core network user plane function entity, and receive the core network user plane configuration confirmation information from the core network user plane function entity based on the core network user plane configuration request information;

[0328] A second message is sent to the session management function entity. The second message includes session-related access network resource confirmation information and core network user plane configuration confirmation information.

[0329] Among them, Figure 17 In this embodiment, the bus architecture can include any number of interconnected buses and bridges, specifically linking various circuits of one or more processors 1010 represented by processor 1010 and various circuits of memory 1020 represented by memory 1020. The bus architecture can also link various other circuits such as peripheral devices, voltage regulators, and power management circuits, which are well known in the art and therefore will not be further described in this embodiment. Bus interface 1030 provides an interface. Transceiver 1040 can be multiple elements, including transmitters and receivers, providing units for communicating with various other devices over transmission media, including wireless channels, wired channels, optical fibers, etc. Processor 1010 is responsible for managing the bus architecture and general processing, and memory 1020 can store data used by processor 1010 during operation.

[0330] The processor 1010 can be a central processing unit (CPU), an application-specific integrated circuit (ASIC), a field-programmable gate array (FPGA), or a complex programmable logic device (CPLD). The processor 1010 can also adopt a multi-core architecture.

[0331] The processor 1010 executes any of the methods provided in the embodiments of this application by calling a computer program stored in the memory 1020, according to the obtained executable instructions. The processor 1010 and the memory 1020 may also be physically separated.

[0332] This application provides an electronic device comprising: a memory and a processor; at least one program stored in the memory, which, when executed by the processor, can, compared with the prior art, achieve the following: by sending a first message, the first message including session-related access network resource request information, core network user plane configuration request information, and indication information, instructing the core network user plane configuration request information to be sent to a first core network user plane functional entity, or instructing a preset functional entity to send the access network resource request information to the access network functional entity, thus avoiding the prior art where the session management functional entity separately sends the access network resource request information and the core network user plane configuration request information to the first core network user plane functional entity. The problem of excessive interactions caused by the access network function entity and the core network user plane function entity is addressed by the fact that the second message includes session-related access network resource confirmation information and core network user plane configuration confirmation information. It only needs to interact with the session management function entity once, that is, the confirmation information generated by the two function entities (access network function entity and core network user plane function entity) is sent to the session management function entity together. Compared with the existing technology, this reduces the signaling interaction between the ground (SMF) and the satellite (S-gNB, S-UPF or S-gNB / S-UPF), thereby shortening the time for establishing, modifying or releasing PDU sessions using the satellite and improving the efficiency of PDU session management.

[0333] In one alternative embodiment, an electronic device is provided, such as Figure 18 As shown, Figure 18 The illustrated electronic device 4000 includes a processor 4001 and a memory 4003. The processor 4001 and the memory 4003 are connected, for example, via a bus 4002. Optionally, the electronic device 4000 may also include a transceiver 4004. It should be noted that in practical applications, the transceiver 4004 is not limited to one type, and the structure of this electronic device 4000 does not constitute a limitation on the embodiments of this application.

[0334] Processor 4001 may be a CPU (Central Processing Unit), a general-purpose processor, a DSP (Digital Signal Processor), an ASIC (Application Specific Integrated Circuit), an FPGA (Field Programmable Gate Array), or other programmable logic devices, transistor logic devices, hardware components, or any combination thereof. It can implement or execute the various exemplary logic blocks, modules, and circuits described in conjunction with the disclosure of this application. Processor 4001 may also be a combination that implements computational functions, such as including one or more microprocessor combinations, a combination of a DSP and a microprocessor, etc.

[0335] Bus 4002 may include a pathway for transmitting information between the aforementioned components. Bus 4002 may be a PCI (Peripheral Component Interconnect) bus or an EISA (Extended Industry Standard Architecture) bus, etc. Bus 4002 can be divided into address bus, data bus, control bus, etc. For ease of representation, Figure 18 The bus is represented by a single thick line, but this does not mean that there is only one bus or one type of bus.

[0336] The memory 4003 may be ROM (Read Only Memory) or other types of static storage devices capable of storing static information and instructions, RAM (Random Access Memory) or other types of dynamic storage devices capable of storing information and instructions, or EEPROM (Electrically Erasable Programmable Read Only Memory), CD-ROM (Compact Disc Read Only Memory) or other optical disc storage, optical disc storage (including compressed optical discs, laser discs, optical discs, digital universal optical discs, Blu-ray discs, etc.), magnetic disk storage media or other magnetic storage devices, or any other medium capable of carrying or storing desired program code in the form of instructions or data structures and accessible by a computer, but not limited thereto.

[0337] The memory 4003 stores application code that executes the scheme of this application, and its execution is controlled by the processor 4001. The processor 4001 executes the application code stored in the memory 4003 to implement the content shown in the foregoing method embodiments.

[0338] This application provides a computer-readable storage medium storing a computer program that, when run on a computer, enables the computer to execute the corresponding content in the aforementioned method embodiments. Compared with existing technologies, by sending a first message, which includes session-related access network resource request information, core network user plane configuration request information, and indication information, instructing the core network user plane configuration request information to be sent to the first core network user plane functional entity, or instructing a preset functional entity to send the access network resource request information to the access network functional entity, the problem of excessive interaction caused by the session management functional entity sending the access network resource request information and the core network user plane configuration request information to the access network functional entity and the core network user plane functional entity respectively in existing technologies is avoided. Since the second message includes session-related access network resource confirmation information and core network user plane configuration confirmation information, only one interaction with the session management functional entity is required, that is, the confirmation information generated by the two functional entities (access network functional entity and core network user plane functional entity) is sent to the session management functional entity together. Overall, compared with existing technologies, the signaling interaction between the ground (SMF) and the satellite (S-gNB, S-UPF or S-gNB / S-UPF) is reduced, thereby shortening the time for establishing, modifying or releasing PDU sessions using the satellite and improving the efficiency of PDU session management.

[0339] This application provides a computer program that includes computer instructions stored in a computer-readable storage medium. When a processor of a computer device reads the computer instructions from the computer-readable storage medium, the processor executes the computer instructions, causing the computer device to perform the content shown in the foregoing method embodiments. Compared with existing technologies, by sending a first message, which includes session-related access network resource request information, core network user plane configuration request information, and indication information, instructing the core network user plane configuration request information to be sent to the first core network user plane functional entity, or instructing a preset functional entity to send the access network resource request information to the access network functional entity, the problem of excessive interaction caused by the session management functional entity sending the access network resource request information and the core network user plane configuration request information to the access network functional entity and the core network user plane functional entity respectively in existing technologies is avoided. Since the second message includes session-related access network resource confirmation information and core network user plane configuration confirmation information, only one interaction with the session management functional entity is required, that is, the confirmation information generated by the two functional entities (access network functional entity and core network user plane functional entity) is sent to the session management functional entity together. Overall, compared with existing technologies, the signaling interaction between the ground (SMF) and the satellite (S-gNB, S-UPF or S-gNB / S-UPF) is reduced, thereby shortening the time for establishing, modifying or releasing PDU sessions using the satellite and improving the efficiency of PDU session management.

[0340] It should be understood that although the steps in the flowcharts of the accompanying figures are shown sequentially as indicated by the arrows, these steps are not necessarily executed in the order indicated by the arrows. Unless explicitly stated herein, there is no strict order restriction on the execution of these steps, and they can be executed in other orders. Moreover, at least some steps in the flowcharts of the accompanying figures may include multiple sub-steps or multiple stages. These sub-steps or stages are not necessarily completed at the same time, but can be executed at different times, and their execution order is not necessarily sequential, but can be performed alternately or in turn with other steps or at least some of the sub-steps or stages of other steps.

[0341] The above are only some embodiments of this application. It should be noted that for those skilled in the art, several improvements and modifications can be made without departing from the principle of this application, and these improvements and modifications should also be considered within the scope of protection of this application.

Claims

1. A session control method, characterized in that, include: The system receives a first message from the session management function entity and configures access network resources based on the access network resource request information. The first message includes the session-related access network resource request information and the core network user plane configuration request information. Send the core network user plane configuration request information to the core network user plane function entity, and receive the core network user plane configuration confirmation information from the core network user plane function entity based on the core network user plane configuration request information; A second message is sent to the session management function entity. The second message includes access network resource confirmation information and core network user plane configuration confirmation information related to the session.

2. The session control method according to claim 1, characterized in that, Sending the core network user plane configuration request information to the core network user plane function entity includes: At least one parameter in the access network resource confirmation information and the core network user plane configuration request information are sent to the core network user plane function entity to instruct the core network user plane function entity to reply with the core network user plane configuration confirmation information based on at least one parameter in the access network resource confirmation information and the core network user plane configuration request information.

3. The session control method according to claim 2, characterized in that, The access network resource confirmation information includes at least one of the following parameters: The access network functional entity receives or rejects the Quality of Service (QoS) information of the session; The session is located in the tunnel endpoint information of the access network functional entity.

4. A session control method, characterized in that, include: Receive a third message sent by the core network user plane function entity, the third message including session-related access network resource request information, configure access network resources according to the access network resource request information, and generate access network resource confirmation information; A fourth message is sent to the core network user plane function entity. The fourth message includes the access network resource confirmation information. The access network resource confirmation information is used by the core network user plane function entity to send a second message to the session management function entity. The second message includes the access network resource confirmation information and the core network user plane configuration confirmation information. The third message is sent by the core network user plane function entity after receiving the first message sent by the session management function entity and configuring the core network user plane according to the core network user plane configuration request information. The first message includes the session-related access network resource request information and the core network user plane configuration request information.

5. The session control method according to claim 4, characterized in that, The third message also includes at least one parameter in the core network user plane configuration confirmation information; The step of configuring access network resources based on the access network resource request information includes: Access network resources are configured based on at least one parameter in the core network user plane configuration confirmation information and the access network resource request information.

6. The session control method according to claim 5, characterized in that, The core network user plane configuration confirmation information includes at least one of the following parameters: The data packet processing rules for the session that the core network user plane function entity receives or rejects; The session is located in the tunnel endpoint information of the user plane functional entity in the core network. The step of configuring access network resources based on at least one parameter in the core network user plane configuration confirmation information and the access network resource request information includes: The access network functional entity receives or rejects the Quality of Service (QoS) information of the session based on the packet processing rules of the session received or rejected by the core network user plane functional entity. And / or, The core network address to which the session data packet is sent is determined based on the tunnel endpoint information of the core network user plane functional entity.

7. A session control method, characterized in that, include: Receive the first message sent by the session management function entity, perform core network user plane configuration according to the core network user plane configuration request information, and generate core network user plane configuration confirmation information. The first message includes session-related access network resource request information and the core network user plane configuration request information; The access network resource request information is sent to the access network function entity, and the access network function entity is received in response to the access network resource confirmation information based on the access network resource request information. A second message is sent to the session management function entity. The second message includes access network resource confirmation information and core network user plane configuration confirmation information related to the session.

8. The session control method according to claim 7, characterized in that, Sending the access network resource request information to the access network functional entity includes: At least one parameter in the core network user plane configuration confirmation information and the access network resource request information are sent to the access network function entity to instruct the access network function entity to reply with access network resource confirmation information based on at least one parameter in the core network user plane configuration confirmation information and the access network resource request information.

9. The session control method according to claim 8, characterized in that, The core network user plane configuration confirmation information includes: The rules for handling data packets of the session that the core network user plane functional entity accepts or rejects; The session is based on the tunnel endpoint information of the user plane functional entity in the core network.

10. A session control method, characterized in that, include: The system receives a fifth message from the access network functional entity and performs core network user plane configuration based on the core network user plane configuration request information; the fifth message includes the session-related core network user plane configuration request information. A sixth message is sent to the access network function entity. The sixth message includes core network user plane configuration confirmation information. The core network user plane configuration confirmation information is used by the access network function entity to send a second message to the session management function entity. The second message includes access network resource confirmation information and the core network user plane configuration confirmation information. The fifth message is sent by the access network function entity after receiving the first message sent by the session management function entity and configuring access network resources according to the access network resource request information. The first message includes the session-related access network resource request information and the core network user plane configuration request information.

11. The session control method according to claim 10, characterized in that, The fifth message also includes information about the second core network user plane function entity; Before sending the fourth message to the access network function entity, the method further includes: Based on the information of the second core network user plane function entity, the session-related core network user plane configuration request information is sent to the second core network user plane function entity to instruct the second core network user plane function entity to perform core network user plane configuration according to the core network user plane configuration request information.

12. The session control method according to claim 10, characterized in that, The fifth message includes at least one parameter in the access network resource confirmation information; Configure the core network user plane according to the core network user plane configuration request information, including: Core network user plane configuration is performed based on at least one parameter in the access network resource confirmation information and the core network user plane configuration request information.

13. The session control method according to claim 12, characterized in that, The access network resource confirmation information includes at least one of the following parameters: The access network functional entity receives or rejects the Quality of Service (QoS) information of the session; The session is located in the tunnel endpoint information of the access network functional entity; The core network user plane configuration based on at least one parameter in the access network resource confirmation information and the core network user plane configuration request information includes: Based on the Quality of Service (QoS) information of the session received or rejected by the access network functional entity, the packet processing rules for the session received or rejected by the first core network user plane functional entity are determined; and / or, The access network address to which the session data packet is sent is determined based on the tunnel endpoint information of the access network functional entity.

14. A session control method, characterized in that, include: Send a first message to a preset functional entity. The first message includes session-related access network resource request information, core network user plane configuration request information, and indication information. Receive a second message sent by the preset functional entity, the second message including the session-related access network resource confirmation information and the core network user plane configuration confirmation information; The instruction information is used to instruct the preset functional entity to send the core network user plane configuration request information to the first core network user plane functional entity, or to instruct the preset functional entity to send the access network resource request information to the access network functional entity.

15. The session control method according to claim 14, characterized in that, Before sending the first message to the preset functional entity, the following steps are also included: It is determined that the preset functional entity supports forwarding the core network user plane configuration request information in the first message to the first core network user plane functional entity. It is determined that the preset functional entity supports forwarding the access network resource request information in the first message to the access network functional entity; It is determined that the preset functional entity supports forwarding the core network user plane configuration request information in the first message to other core network user plane functional entities; or, The preset functional entity is determined to be a functional entity with access network functions and core network user plane functions.

16. The session control method according to claim 14 or 15, characterized in that, The access network resource request information includes session-related access network resource establishment, modification, or release request information. The core network user plane configuration request information includes session-related core network user plane resource establishment, modification, or release request information.

17. An access network functional entity, characterized in that, include: The access-side first message receiving module is used to receive a first message sent by the session management function entity and to configure access network resources according to the access network resource request information; the first message includes the session-related access network resource request information and the core network user plane configuration request information. The core configuration forwarding and receiving module is used to send the core network user plane configuration request information to the core network user plane function entity and receive the core network user plane configuration confirmation information replied by the core network user plane function entity according to the core network user plane configuration request information. The access-side second message sending module is used to send a second message to the session management function entity. The second message includes access network resource confirmation information and core network user plane configuration confirmation information related to the session.

18. An access network functional entity, characterized in that, include: The third message receiving module is used to receive a third message sent by the core network user plane function entity, configure access network resources according to access network resource request information, and generate access network resource confirmation information; the third message includes session-related access network resource request information. The fourth message sending module is used to send a fourth message to the core network user plane function entity. The fourth message includes access network resource confirmation information. The access network resource confirmation information is used by the core network user plane function entity to send a second message to the session management function entity. The second message includes the access network resource confirmation information and core network user plane configuration confirmation information. The third message is sent by the core network user plane function entity after receiving the first message sent by the session management function entity and configuring the core network user plane according to the core network user plane configuration request information. The first message includes the session-related access network resource request information and the core network user plane configuration request information.

19. A core network user plane functional entity, characterized in that, include: The core-side first message receiving module is used to receive the first message sent by the session management function entity and perform core network user plane configuration according to the core network user plane configuration request information; the first message includes session-related access network resource request information and the core network user plane configuration request information. The access request forwarding and receiving module is used to send the access network resource request information to the access network functional entity and receive the access network resource confirmation information replied by the access network functional entity based on the access network resource request information. The core-side second message receiving module is used to send a second message to the session management function entity. The second message includes access network resource confirmation information and core network user plane configuration confirmation information related to the session.

20. A core network user plane functional entity, characterized in that, include: The fifth message receiving module is used to receive the fifth message sent by the access network functional entity and perform core network user plane configuration according to the core network user plane configuration request information; the fifth message includes session-related core network user plane configuration request information. The sixth message sending module is used to send a sixth message to the access network function entity. The sixth message includes core network user plane configuration confirmation information. The core network user plane configuration confirmation information is used by the access network function entity to send a second message to the session management function entity. The second message includes access network resource confirmation information and the core network user plane configuration confirmation information. The fifth message is sent by the access network function entity after receiving the first message sent by the session management function entity and configuring access network resources according to the access network resource request information. The first message includes the session-related access network resource request information and the core network user plane configuration request information.

21. A session management function entity, characterized in that, include: The first message sending module is used to send a first message to a preset functional entity. The first message includes session-related access network resource request information, core network user plane configuration request information, and indication information. The second message receiving module is used to receive a second message sent by the preset functional entity. The second message includes the session-related access network resource confirmation information and the core network user plane configuration confirmation information. The instruction information is used to instruct the preset functional entity to send the core network user plane configuration request information to the first core network user plane functional entity, or to instruct the preset functional entity to send the access network resource request information to the access network functional entity.

22. A conversation control device, characterized in that, Includes memory, transceiver, and processor: A memory for storing computer programs; a transceiver for sending and receiving data under the control of the processor; and a processor for reading the computer programs from the memory and executing the session control method as described in any one of claims 1-16.

23. An electronic device comprising a memory, a processor, and a computer program stored in the memory and executable on the processor, characterized in that, When the processor executes the computer program, it implements the steps of the session control method as described in any one of claims 1 to 16.

24. A computer-readable storage medium, characterized in that, The computer-readable storage medium stores computer instructions that cause the computer to perform the steps of the session control method as described in any one of claims 1 to 16.

Images