User plane connection management method and device and computer readable storage medium

Abstract

The embodiment of the invention provides a user plane connection management method and device and a computer readable storage medium. The method comprises the following steps: receiving user plane migration information in a user plane connection migration process; and determining that the first user plane connection with the first NF is migrated to the second user plane connection with the second NF according to the user plane migration information. According to the method, the reliability of service session operation after user plane connection migration is ensured.

Description

User plane connection management methods, devices, and computer-readable storage media Technical Field

[0001] This application relates to the field of communication technology, and in particular to a user plane connection management method, device, and computer-readable storage medium. Background Technology

[0002] In current and future communication networks, a trend is that terminals can communicate directly with the network functions (NFs) of the core network through the user plane. That is, control plane signaling between the terminal and the NF can be carried in user plane data packets.

[0003] For NFs of the same type, a terminal can simultaneously establish user plane connections with multiple NFs of the same type. As shown in Figure 1, a terminal can have user plane connections with NF1 and NF2 simultaneously. At least one service session (e.g., S1, S2, S3) is running on the user plane connection between the terminal and NF1, and at least one service session (e.g., T1, T2) is also running on the user plane connection between the terminal and NF2. At some point, the network needs to migrate services from the serving terminal's NF2 to NF3. How to perform this user plane connection migration is a technical problem that urgently needs to be solved by those skilled in the art. Summary of the Invention

[0004] This application provides a user plane connection management method, device, and computer-readable storage medium.

[0005] In a first aspect, embodiments of this application provide a user plane connection management method, applied to a first communication node, comprising:

[0006] During the user plane connection migration process, receive user plane migration information;

[0007] Based on the user plane migration information, it is determined that the first user plane connection with the first NF is migrated to the second user plane connection with the second NF.

[0008] Secondly, embodiments of this application provide a user plane connection management method, applied to a second communication node, comprising:

[0009] During the user plane connection migration process, user plane migration information is sent to the first communication node;

[0010] The user plane migration information is used to notify the first communication node that the first user plane connection with the first NF has been migrated to the second user plane connection with the second NF.

[0011] Thirdly, embodiments of this application provide a communication device, including: a memory and a processor, wherein the memory stores a computer program, and the processor executes the computer program to implement the steps of the user plane connection management method provided in the first or second aspect.

[0012] Fourthly, embodiments of this application provide a computer-readable storage medium storing a computer program that, when executed by a processor, implements the steps of the user plane connection management method provided in the first or second aspect.

[0013] Further details regarding the above embodiments and other aspects of this application, as well as their implementations, are provided in the accompanying drawings, detailed description, and claims. Attached Figure Description

[0014] Figure 1 is a schematic diagram of a traditional user plane connection variation;

[0015] Figure 2 is a schematic diagram of a wireless communication system provided in an embodiment of this application;

[0016] Figure 3 is a schematic diagram of another structure of the wireless communication system provided in an embodiment of this application;

[0017] Figure 4 is a flowchart illustrating a user plane connection management method provided in an embodiment of this application.

[0018] Figure 5 is another flowchart illustrating the user plane connection management method provided in an embodiment of this application;

[0019] Figure 6 is a schematic flowchart of another user plane connection management method provided in an embodiment of this application;

[0020] Figure 7 is a schematic flowchart of another user plane connection management method provided in an embodiment of this application;

[0021] Figure 8 is a schematic flowchart of another user plane connection management method provided in an embodiment of this application;

[0022] Figure 9 is a schematic flowchart of another user plane connection management method provided in an embodiment of this application;

[0023] Figure 10 is a schematic diagram of a user plane connection management device provided in an embodiment of this application;

[0024] Figure 11 is a schematic diagram of another structure of the user plane connection management device provided in an embodiment of this application;

[0025] Figure 12 is a schematic diagram of a communication device provided in an embodiment of this application. Detailed Implementation

[0026] It should be understood that the specific embodiments described herein are merely illustrative and not intended to limit the scope of this application. The embodiments of this application will be described in detail below with reference to the accompanying drawings.

[0027] The user plane connection management method provided in this application can be applied to various wireless communication systems. For example, the wireless communication system may be a fifth-generation (5G) communication system, a 3GPP-related communication system, a sixth-generation (6G) communication system, and a future evolution communication system or a system integrating multiple systems, etc. This application does not limit this.

[0028] For example, taking a 5G communication system as an example, the logical structure of a 5G communication system can be as shown in Figure 2. In this system, the terminal equipment (User Equipment, UE) wirelessly accesses and connects to the Radio Access Network (RAN) based on the air interface (Uu). It then connects to the control plane network elements (such as the Access and Mobility Management Function (AMF)) and user plane network elements (such as the User Plane Function (UPF)) within the core network through the RAN. Furthermore, it connects to the remote data network (such as the Data Network) through the user plane network elements, thereby realizing the transmission and interaction of end-to-end user service data. In addition, the core network of a 5G communication system also includes the following NFs: Authentication Server Function (AUSF) (not shown in Figure 2), Unified Data Management (UDM), Session Management Function (SMF), Policy Control Function (PCF), Network Exposure Function (NEF), Access and User Plane Function (AUPF), and Application Function (AF).

[0029] The AMF provides the following functions: registration management, connection management, reachability and mobility management, access authentication, and access authorization. The AMF is a Non-Access Stratum (NAS) secure terminal that relays SMNAS between the UE and the SMF.

[0030] SMF provides the following functions: session management (such as session establishment, modification and release), UE IP address allocation and management (including optional authorization functions), selection and control of user plane functions, and downlink data notification, etc.

[0031] UPF provides the following functions: anchor point for mobility within / between Radio Access Technology (RAT), packet routing and forwarding, traffic usage reporting, Quality of Service (QoS) processing on the user plane, downlink packet buffering, and downlink data notification triggering.

[0032] The UDM provides the following functions: managing UE subscriptions, which include data for mobility management (e.g., restricted areas) and session management. Subscription data also includes slice selection parameters, which are used by the AMF to select the appropriate SMF. The AMF and SMF obtain subscription data from the UDM, which is stored in the Unified Data Repository (UDR). The UDM retrieves class data from the UDR upon receiving a request from the AMF or SMF.

[0033] PCF provides the following functions: supports a unified policy framework to manage network behavior, provides policy rules to control plane functions, thereby enabling the front end to access subscription information related to policy decisions in the UDR.

[0034] The NEF is an optional deployment used to exchange information between the 5G core network (5G core, 5GC) and external third parties. In this case, the AF can store application information in the UDR through the NEF.

[0035] LMF is used to manage the overall coordination and scheduling of resources required for UE positioning, and to calculate or verify the final location.

[0036] The AF / AS (Application Server) provides services to the UE through the 5G system.

[0037] AUPF typically works in conjunction with UPF to support the routing and forwarding of user data, ensuring that user data can be transmitted efficiently in the network.

[0038] The 5G system is divided into a control plane and a user plane. The control plane is mainly responsible for signaling interaction and service processing, such as user authentication, session management, mobility management, subscription management, and policy and charging control (PCC). The UE accesses the AMF via NAS signaling. The 5GC adopts a service-based architecture (SBA), and the 5GC's NF interacts through the SBI (Service-based interface). The AMF can interact with the base station through the N2 interface.

[0039] NAS signaling is a key protocol in 5G systems used for registration management, session management, mobility management, and security control between the UE and the core network. With the development of 5G network protocols, NAS signaling has also encountered many problems:

[0040] Adding new features to the UE requires expanding the NAS messages so that the UE can exchange the necessary UE-side information with the network via NAS messages. As the functionality has increased, the NAS messages have become exceptionally large.

[0041] NAS messages are too complex. NAS interactions involve multiple NFs in the core network (such as AMF, SMF, PCF, UDM, etc.), which leads to complex signaling processes, increased interaction frequency, and increased network load.

[0042] The signaling overhead is high, which affects network efficiency.

[0043] AMF may become a single point of bottleneck.

[0044] Therefore, in current and future wireless communication systems, a trend is that the UE can communicate directly with the NF of the core network through the user plane. That is, the control plane signaling between the UE and the NF of the core network can be carried in the user plane data packet.

[0045] For example, as shown in Figure 3, NFs within the core network can interact using SBI, and UEs and NFs in the core network, such as LMFs, Sensing Functions (SFs), and Artificial Intelligence Functions (AIs), can interact via user plane signaling.

[0046] For the same type of NF, a terminal can establish user plane connections with multiple NFs of the same type simultaneously. Taking LMF as an example, each LMF supports different positioning capabilities, service areas, or positioning types. When a UE has multiple positioning requests, different LMFs may be providing services to the UE simultaneously. Similarly, each SF supports different sensing types, sensing methods, or service areas, or even for load balancing reasons. When a UE has multiple sensing requests, different SFs may be serving the UE simultaneously.

[0047] Therefore, at the same time, a UE may establish user plane connections with multiple NFs of the same type simultaneously. On each UE-NF user plane connection, multiple service requests may be running. Each service request is identified / distinguished by its session ID, transaction ID, or service ID. For example, continuing to refer to Figure 1, a UE may have user plane connections with NF1 and NF2 simultaneously. On the user plane connection between the terminal and NF1, at least one service session (e.g., S1, S2, S3) is running, and on the user plane connection between the terminal and NF2, at least one service session (e.g., T1, T2) is also running. At some point, the network needs to migrate services from the serving terminal's NF2 to NF3. After the UE establishes a user plane connection with NF3, the UE cannot know which user plane connection's service session was migrated to the newly established NF3 user plane connection. Therefore, the technical solution provided in this application aims to solve the above-mentioned technical problem.

[0048] Figure 4 is a flowchart illustrating a user plane connection management method provided in an embodiment of this application. The method is applied to a first communication node; exemplarily, the first communication node can be a terminal device, and the second communication node can be an NF in the core network. As shown in Figure 4, the method includes:

[0049] S401. During the user plane connection migration process, receive user plane migration information.

[0050] S402. Based on the user plane migration information, determine that the first user plane connection with the first NF is migrated to the second user plane connection with the second NF.

[0051] Specifically, user plane migration information is used to represent information related to user plane connection migration. During the user plane connection migration process, the second communication node can send user plane migration information to the first communication node, notifying the first communication node that the first user plane connection with the first NF has been migrated to the second user plane connection with the second NF. The first communication node receives the user plane migration information and, based on it, determines that the first user plane connection with the first NF has been migrated to the second user plane connection with the second NF. In other words, the first communication node learns from the user plane migration information sent by the second communication node that the service sessions running on the first user plane connection have been migrated to the second user plane connection. Taking the example in Figure 1, during the process of migrating a service from NF2 to NF3, the second communication node notifies the first communication node through user plane migration information that the service sessions on the user plane connection with NF2 have been migrated to the user plane connection with NF3. Then, the first communication node subsequently runs service sessions T1 and T2 on the user plane connection with NF3.

[0052] Optionally, the user plane migration information may include migration indication information, which is used to notify the first communication node that the user plane connection has been migrated.

[0053] In this embodiment, during the user plane connection migration process, the first communication node receives user plane migration information sent by the second communication node. Through the user plane migration information, it can be determined which existing user plane connection has been migrated to the newly established user plane connection, thereby ensuring the reliability of the service session operation.

[0054] Optionally, the first communication node receiving user plane migration information includes receiving a first user plane connection identifier sent by the second NF. The first user plane connection identifier may include: the address information of the first NF, the fully qualified domain name (FQDN) of the first NF, the callback Uniform Resource Identifier (callback URI) of the first NF, a string containing the name information of the first NF, or a single string.

[0055] Optionally, the first communication node determines, based on the user plane migration information, that the first user plane connection with the first NF has been migrated to the second user plane connection with the second NF, including: the first communication node determines, based on the first user plane connection identifier sent by the second NF, that the first user plane connection with the first NF has been migrated to the second user plane connection with the second NF.

[0056] In one example, during the user plane connection migration process, the second NF can send the first user plane connection identifier to the first communication node. The first communication node can determine that the first user plane connection with the first NF has been migrated to the second user plane connection with the second NF based on the first user plane connection identifier sent by the second NF and the first user plane connection identifier used when establishing the first user plane connection.

[0057] Optionally, the first communication node receiving user plane migration information includes: receiving the address information of the first NF sent by the second NF.

[0058] Optionally, the first communication node determines, based on user plane migration information, that the first user plane connection with the first NF has been migrated to the second user plane connection with the second NF, including: determining, based on the address information of the first NF sent by the second NF, that the first user plane connection with the first NF has been migrated to the second user plane connection with the second NF.

[0059] Specifically, during the user plane connection migration process, the second NF can send the address information of the first NF to the first communication node. The first communication node determines, based on the address information of the first NF sent by the second NF and the address information of the first NF used when establishing the first user plane connection, that the first user plane connection with the first NF has been migrated to the second user plane connection with the second NF.

[0060] Optionally, the first communication node receiving user plane migration information includes: receiving second NF information sent by the first NF and second NF information sent by the second target NF.

[0061] The second NF information may include one of the following: the address information of the second NF, the FQDN of the second NF, the callback URI of the second NF, a string containing the name information of the second NF, or a simple string.

[0062] Optionally, receiving the second NF information sent by the first NF may include: receiving the second NF information and the address information of the first NF sent by the first NF through the control plane; or, receiving the second NF information sent by the first NF through the first user plane connection.

[0063] Specifically, the first NF can send second NF information through the control plane. That is, the first NF sends the second NF information to the first communication node through the Connection Management Function (CMF). When sending the second NF information through the control plane, the first NF also needs to send the address information of the first NF used when establishing the first user plane connection with the first communication node, so that the first communication node can determine that the second NF information sent through the control plane was sent by the first NF. In other words, the first communication node can receive the second NF information and the address information of the first NF sent by the first NF through the control plane.

[0064] Alternatively, the first communication node can receive the second NF information sent by the first NF through the first user plane connection. The user plane migration process may include the release process of the first user plane connection and the establishment process of the second user plane connection. Optionally, the first NF may send the second NF information to the first communication node during the release process of the first user plane connection; that is, the first NF may send the second NF information to the first communication node before the first user plane connection is released, or it may send the second NF information during the release process of the first user plane connection. Sending the second NF information during the release process of the first user plane connection can reduce signaling interaction.

[0065] Optionally, the first communication node determines, based on user plane migration information, that the first user plane connection with the first NF has been migrated to the second user plane connection with the second NF, including: determining, based on the second NF information sent by the first NF and the second NF information sent by the second NF, that the first user plane connection with the first NF has been migrated to the second user plane connection with the second NF.

[0066] Optionally, the method further includes: during the user plane connection establishment process, the first communication node receives the user plane connection identifier sent by the NF.

[0067] The user plane connection identifier may include: the address information of the NF, the FQDN of the NF, the callback URI of the NF, a string containing the name information of the NF, or a string.

[0068] During the establishment of a user plane connection between an NF and the first communication node, the NF can send a user plane connection identifier to the first communication node, which then receives the identifier. For example, during the establishment of the first user plane connection, the first NF sends its first user plane connection identifier to the first communication node, which receives it. Subsequently, during the migration of services from the first NF to the second NF, the first NF can send its first user plane connection identifier to the second NF, which in turn sends it to the first communication node. The first communication node can then determine, based on the identifier sent by the second NF, that the service session running on the first user plane connection has been migrated to the second user plane connection with the second NF.

[0069] Optionally, during the establishment of the second user plane connection, if the first communication node only receives the second user plane connection identifier, the first communication node determines that the user plane connection has not been migrated and this is simply the establishment of the second user plane connection; if the first communication node receives both the second user plane connection identifier and the first user plane connection identifier, the first communication node determines that the user plane connection has been migrated according to the first user plane connection identifier, and the first user plane connection has been migrated to the second user plane connection.

[0070] Figure 5 is another flowchart illustrating the user plane connection management method provided in this application embodiment. This method is applied to a second communication node. For example, the first communication node can be a terminal device, and the second communication node can be an NF in the core network. As shown in Figure 5, the method includes:

[0071] S501. During the user plane connection migration process, the second communication node sends user plane migration information to the first communication node.

[0072] The user plane migration information is used to represent information related to user plane connection migration. During the user plane connection migration process, the second communication node can send the user plane migration information to the first communication node, notifying the first communication node that the first user plane connection with the first NF has been migrated to the second user plane connection with the second NF. Thus, after receiving the user plane migration information, the first communication node determines, based on the user plane migration information, that the first user plane connection with the first NF has been migrated to the second user plane connection with the second NF. In other words, the first communication node learns from the user plane migration information sent by the second communication node that the service sessions running on the first user plane connection have been migrated to the second user plane connection. Taking the example in Figure 1, during the migration of a service from NF2 to NF3, the second communication node notifies the first communication node via the user plane migration information that the service sessions on the user plane connection with NF2 have been migrated to the user plane connection with NF3. Then, the first communication node subsequently runs service sessions T1 and T2 on the user plane connection with NF3.

[0073] Optionally, the second communication node sends user plane migration information to the first communication node, including: the second NF sending a first user plane connection identifier to the first communication node; or, the second NF sending the address information of the first NF to the first communication node; or, the first NF sending second NF information to the first communication node and the second NF sending second NF information to the first communication node.

[0074] Optionally, the first NF sending the second NF information to the first communication node may include: the first NF sending the second NF information to the first communication node through the control plane, that is, the first NF sending the second NF information to the first communication node through the CMF; or, the first NF sending the second NF information to the first communication node through the first user plane connection.

[0075] Optionally, when the first NF sends the second NF information to the first communication node through the control plane, it also needs to carry the address information of the first NF used when establishing the first user plane connection with the first communication node, so that the first communication node knows that the second NF information sent through the control plane was sent by the first NF.

[0076] Optionally, the first NF sending the second NF information to the first communication node through the first user plane connection may include: the first NF sending the second NF information to the first communication node during the release of the first user plane connection. That is, the first NF can send the second NF information to the first communication node before the first user plane connection is released, or it can send the second NF information during the release of the first user plane connection. Sending the second NF information during the release of the first user plane connection can reduce signaling interaction.

[0077] Optionally, the method further includes: the second NF sending second NF information to the first NF; or, the first NF sending a first user plane connection identifier to the second NF; or, the first NF sending the address information of the first NF to the second NF.

[0078] Optionally, during the user plane migration process, the second NF can send second NF information to the first NF, and the first NF sends the second NF information to the first communication node. During the establishment of the second user plane connection, the second NF also sends the second NF information to the first communication node. Based on the second NF information sent by the first NF and the second NF sent by the second NF, the first communication node determines that the user plane connection has been migrated and that the first user plane connection has been migrated to the second user plane connection.

[0079] Optionally, during the user plane migration process, the first NF can send the first user plane connection identifier to the second NF. The second NF sends the first user plane connection identifier to the first communication node during the establishment of the second user plane connection. The first communication node determines that the user plane connection has been migrated based on the first user plane connection identifier sent by the second NF and the first user plane connection identifier used when establishing the first user plane connection, and the first user plane connection is migrated to the second user plane connection.

[0080] Optionally, during the user plane migration process, the first NF can send the address information of the first NF used when establishing the first user plane connection to the second NF. The second NF sends the address information of the first NF to the first communication node during the establishment of the second user plane connection. The first communication node determines that the user plane connection has been migrated based on the address information of the first NF sent by the second NF and the first user plane connection identifier used when establishing the first user plane connection, and the first user plane connection is migrated to the second user plane connection.

[0081] Optionally, during the user plane connection establishment process, the second communication node sends a user plane connection identifier to the first communication node. For example, taking the second communication node as the first NF, during the first user plane connection establishment process, the first NF can send a first user plane connection identifier to the first communication node. The first communication node receives the first user plane connection identifier sent by the first NF. Subsequently, during the migration of services from the first NF to the second NF, the second NF can send the first user plane connection identifier to the first communication node. The first communication node can then determine, based on the first user plane connection identifier sent by the second NF, that the service session running on the first user plane connection has been migrated to the second user plane connection.

[0082] Below are some exemplary embodiments to explain the user plane connection management method provided in the above embodiments of this application. These exemplary embodiments can be executed individually or in combination. In the following exemplary embodiments, the first communication node is denoted as UE, and the second communication node is denoted as NF.

[0083] In a first exemplary embodiment, a user plane connection establishment process is provided. When an NF decides to establish a user plane connection with a UE, the NF sends the user plane connection identifier to the UE, and the UE receives the user plane connection identifier. Optionally, the user plane connection identifier may include one of the following information: the NF's address information, the NF's FQDN, the NF's callback URI, a string containing NF name information, or a string. Specifically, as shown in Figure 6, the user plane connection establishment process includes:

[0084] S601 and NF decide to conduct signaling interaction with the UE through the user plane.

[0085] S602 and NF send user plane information to CMF.

[0086] The user plane information may include the address information of the NF (e.g., the IP address or FQDN of the NF), the Binding ID, and the user plane connection identifier. The user plane connection identifier can be one of the following: the address information of the NF, the FQDN of the NF, the callback URI of the NF, a string containing NF name information, or a plain string. Only the user plane connection identifier is shown in the figure; other user plane information is not shown.

[0087] The NF sends user plane information to the CMF through the Namf_communication_N1N2MessageTransfer service operation. The CMF can be an AMF, an independent NF, or a RAN node. For example, in a 5G communication system, the CMF can be an AMF; in a 6G communication system, the CMF can be an AMF, an independent NF, or a RAN node.

[0088] S603 and CMF send the received user plane information to the UE.

[0089] Among them, CMF can send NF user plane information to UE through NAS messages.

[0090] S604. The UE establishes a user plane connection with the NF based on the NF's address information.

[0091] For example, the UE uses the address information of the NF to establish a Transport Layer Security over Transmission Control Protocol (TLS over TCP) connection or a secure Quick User Datagram Protocol Internet Connection (QUIC) connection.

[0092] S605, UE and NF are connected and bound.

[0093] On the established secure connection, the UE sends a connection binding request to the NF, which carries a Binding ID. After receiving the Binding ID, the NF confirms the successful binding to the UE and releases the Binding ID for use by other UEs.

[0094] S606, the UE confirms the successful establishment of the user plane connection by controlling the NF.

[0095] The UE sends a user plane connection establishment success message to the NF via the CMF.

[0096] In a second exemplary embodiment, a user plane connection migration process is provided. In this example, the first NF sends a first user plane connection identifier to the second NF. During the establishment of the second user plane connection, the second NF sends the first user plane connection identifier to the UE. The UE learns from the first user plane connection identifier sent by the second NF that the first user plane connection with the first NF has been migrated to the second user plane connection with the second NF. That is, the service session running on the first user plane connection is migrated to the second user plane connection, and subsequently, the aforementioned service session runs on the second user plane connection. Specifically, as shown in Figure 7, the user plane connection migration process may include:

[0097] S701, UE and the first NF have established a first user plane connection and are exchanging control signaling through the first user plane connection.

[0098] S702, CMF determines that NF needs to be migrated from the first NF to the second NF, and CMF sends a user plane change request to the first NF.

[0099] The user-plane change request may include information about the second NF, such as the second NF ID or the second NF instance ID.

[0100] The aforementioned CMF can be an AMF, an independent NF, or a RAN node. For example, in a 5G communication system, the CMF can be an AMF; in a 6G communication system, the CMF can be an AMF, an independent NF, or a RAN node.

[0101] Optionally, there are many reasons that can trigger NF migration, such as a change in the UE's location, load balancing, or other reasons. These will not be listed in this embodiment.

[0102] S703. After the first NF receives the user plane change request from the CMF, if the user plane change request does not contain information about the second NF, the first NF can select the second NF according to the corresponding rules, such as through local configuration or through NRF.

[0103] S704, the first NF sends a migration request to the second NF.

[0104] The migration request includes the UE's context, CMF address, and the first user plane connection identifier between the UE and the first NF.

[0105] Optionally, the first user plane connection identifier can be one of the following: the address information of the first NF, the FQDN of the first NF, the callback URI of the first NF, a string containing the name information of the first NF, or a string.

[0106] S705, the second NF sends a migration request response to the first NF.

[0107] S706, the first NF sends a response to the user plane change request to the CMF.

[0108] S707, first NF release and UE's first user plane connection.

[0109] S708, the second NF sends the second user plane information to the CMF.

[0110] The second user plane information may include the address information of the second NF, the Binding ID, and the first user plane connection identifier between the UE and the first NF. Optionally, the second user plane information may also include: the second user plane connection identifier between the UE and the second NF and migration indication information. The migration indication information is used to indicate that a user plane connection migration has occurred; that is, the establishment of the second user plane connection is a user plane migration event.

[0111] Optionally, if the second user plane information does not include a second user plane connection identifier, the second user plane connection between the UE and the second NF can use the first user plane connection identifier.

[0112] Optionally, the second user plane connection identifier can be one of the following: the address information of the second NF, the FQDN of the second NF, the callback URI of the second NF, a string containing the name information of the second NF, or a string.

[0113] Optionally, the second NF sends the second user plane information to the CMF via the Namf_communication_N1N2MessageTransfer service operation. The CMF can be an AMF, an independent NF, or a RAN node. For example, in a 5G communication system, the CMF can be an AMF; in a 6G communication system, the CMF can be an AMF, an independent NF, or a RAN node.

[0114] It should be noted that S705 and S708 can occur simultaneously, without strict order restrictions.

[0115] S709 and CMF send the received second user plane information to the UE.

[0116] Among them, the CMF can send the second user plane information of the second NF to the UE through NAS messages.

[0117] S710, the UE establishes and binds a second user plane connection based on the address information of the second NF and the second NF.

[0118] The specific process of S710 can be referred to the description of S604-S605 in the first exemplary embodiment, and will not be repeated in this example.

[0119] S711. The UE determines, based on the received first user plane connection identifier, that the first user plane connection with the first NF has been migrated to the second user plane connection with the second NF.

[0120] S712, the UE confirms the successful establishment of the second user plane connection by controlling the second NF.

[0121] The UE sends a second user plane connection establishment success message to the second NF via the CMF.

[0122] In a third exemplary embodiment, a user plane connection migration process is provided. In this example, the second NF sends its second NF information to the first NF, and the first NF sends its second NF information to the UE. During the establishment of the second user plane connection between the second NF and the UE, the second NF also sends its second NF information to the UE. Based on the second NF information sent by the first NF and the second NF itself, the UE determines that the first user plane connection with the first NF is migrated to the second user plane connection with the second NF. That is, the service sessions running on the first user plane connection are migrated to the second user plane connection, and subsequently, the aforementioned service sessions run on the second user plane connection. Specifically, as shown in Figure 8, the user plane connection migration process may include:

[0123] S801, UE and the first NF have established a first user plane connection and are exchanging control signaling through the first user plane connection.

[0124] S802, CMF determines that NF needs to be migrated from the first NF to the second NF, and CMF sends a user plane change request to the first NF.

[0125] The user-plane change request may include information about the second NF, such as the second NF ID or the second NF instance ID.

[0126] The aforementioned CMF can be an AMF, an independent NF, or a RAN node. For example, in a 5G communication system, the CMF can be an AMF; in a 6G communication system, the CMF can be an AMF, an independent NF, or a RAN node.

[0127] Optionally, the reason for triggering NF migration may be a change in the UE's location, a load balancing issue, or other reasons.

[0128] S803. After the first NF receives the user plane change request from the CMF, if the user plane change request does not contain information about the second NF, the first NF can select the second NF according to the corresponding rules, such as by local configuration or by NRF.

[0129] S804, the first NF sends a migration request to the second NF.

[0130] The migration request includes the UE's context and CMF address.

[0131] S805, the second NF sends a migration request response to the first NF.

[0132] The migration request response includes second NF information. This second NF information can be: the address information of the second NF, the FQDN of the second NF, the callback URI of the second NF, a string containing the name information of the second NF, or a single string.

[0133] S806, the first NF sends a response to the user plane change request to the CMF.

[0134] S807, the first NF sends the second NF information to the UE.

[0135] Specifically, the first NF can send the second NF information to the UE via the control plane, that is, the first NF sends the second NF information to the UE via the CMF. Alternatively, the first NF can send the second NF information to the UE via a first user plane connection with the UE.

[0136] Optionally, when the second NF sends its information to the UE via the control plane, it may also need to carry the address information of the first NF that was sent to the UE when the UE established a user plane connection with the first NF, so that the UE knows that the second NF information sent via the control plane was sent by the first NF. Optionally, the first NF may also send migration indication information to the UE to notify the first communication node that the user plane connection has been migrated.

[0137] S808, first NF release and UE's first user plane connection.

[0138] Optionally, if the first NF sends the second NF information to the UE through the user plane, the first NF can send the second NF information to the UE during the first user plane connection release process.

[0139] S809, the second NF sends the second user plane information to the CMF.

[0140] The second user plane information includes the address information of the second NF, the Binding ID, and the second NF information (the same as the second NF information sent to the first NF in S805). Here, if the second NF information is the address information of the second NF, then the second user plane information includes the address information of the second NF and the Binding ID. If the second NF information is other than the address information of the second NF, then the second user plane information includes the address information of the second NF, the Binding ID, and the second NF information (the address information of the non-second NF).

[0141] Optionally, the second NF sends the second user plane information to the CMF via the Namf_communication_N1N2MessageTransfer service operation. The CMF can be an AMF, an independent NF, or a RAN node. For example, in a 5G communication system, the CMF can be an AMF; in a 6G communication system, the CMF can be an AMF, an independent NF, or a RAN node.

[0142] It should be noted that S805 and S809 can occur simultaneously, without strict order restrictions.

[0143] S810 and CMF send the received second user plane information to the UE.

[0144] Among them, the CMF can send the second user plane information of the second NF to the UE through NAS messages.

[0145] S811, The UE establishes and binds a second user plane connection based on the address information of the second NF and the second NF.

[0146] The specific process of S811 can be referred to the description of S604-S605 in the first exemplary embodiment, and will not be repeated in this example.

[0147] S812, The UE determines, based on the second NF information sent by the second NF and the second NF information sent by the first NF, that the first user plane connection with the first NF has been migrated to the second user plane connection with the second NF.

[0148] Optionally, when the first NF sends the second NF information to the UE through the control plane, the first NF may also send the address information of the first NF used when the first user plane connection was established through the control plane. The UE determines that the first user plane connection with the first NF has been migrated to the second user plane connection with the second NF based on the second NF information sent by the second NF, the second NF information sent by the first NF, and the address information of the first NF.

[0149] S813, the UE confirms the successful establishment of the second user plane connection by controlling the second NF.

[0150] The UE sends a second user plane connection establishment success message to the second NF via the CMF.

[0151] In a fourth exemplary embodiment, a user plane connection migration process is provided. In this example, the first NF sends its address information to the second NF. During the establishment of the second user plane connection, the second NF sends the address information of the first NF to the UE. The UE learns from the address information of the first NF sent by the second NF that the first user plane connection with the first NF has been migrated to the second user plane connection with the second NF. That is, the service session running on the first user plane connection is migrated to the second user plane connection, and subsequently, the aforementioned service session runs on the second user plane connection. Specifically, as shown in Figure 9, the user plane connection migration process may include:

[0152] S901, UE and the first NF have established a first user plane connection and are exchanging control signaling through the first user plane connection.

[0153] S902, CMF determines that NF needs to be migrated from the first NF to the second NF, and CMF sends a user plane change request to the first NF.

[0154] The user-plane change request may include information about the second NF, such as the second NF ID or the second NF instance ID.

[0155] The aforementioned CMF can be an AMF, an independent NF, or a RAN node. For example, in a 5G communication system, the CMF can be an AMF; in a 6G communication system, the CMF can be an AMF, an independent NF, or a RAN node.

[0156] Optionally, the reason for triggering NF migration may be a change in the UE's location, a load balancing issue, or other reasons.

[0157] S903. After the first NF receives the user plane change request from the CMF, if the user plane change request does not contain information about the second NF, the first NF can select the second NF according to the corresponding rules, such as by local configuration or by NRF.

[0158] S904, the first NF sends a migration request to the second NF.

[0159] The migration request includes the UE's context, CMF address, and the address information of the first NF sent to the UE when the first user plane connection is established.

[0160] S905, the second NF sends a migration request response to the first NF.

[0161] S906, the first NF sends a response to the user plane change request to the CMF.

[0162] S907, First NF Release and UE First User Plane Connection.

[0163] S908, the second NF sends the second user plane information to the CMF.

[0164] The second user plane information may include the address information of the second NF, the Binding ID, and the address information of the first NF (which is the same as the address information of the first NF in S904). Optionally, the second user plane information may also include: a second user plane connection identifier between the UE and the second NF and migration indication information. The migration indication information is used to indicate that a user plane connection migration has occurred, i.e., the establishment of the second user plane connection is a user plane migration event.

[0165] Optionally, if the second user plane information does not include a second user plane connection identifier, the second user plane connection between the UE and the second NF can use the first user plane connection identifier.

[0166] Optionally, the second user plane connection identifier can be one of the following: the address information of the second NF, the FQDN of the second NF, the callback URI of the second NF, a string containing the name information of the second NF, or a string.

[0167] Optionally, the second NF sends the second user plane information to the CMF via the Namf_communication_N1N2MessageTransfer service operation. The CMF can be an AMF, an independent NF, or a RAN node. For example, in a 5G communication system, the CMF can be an AMF; in a 6G communication system, the CMF can be an AMF, an independent NF, or a RAN node.

[0168] It should be noted that S905 and S908 can occur simultaneously, without strict order restrictions.

[0169] S909 and CMF send the received second user plane information to the UE.

[0170] Among them, the CMF can send the second user plane information of the second NF to the UE through NAS messages.

[0171] S910, the UE establishes and binds a second user plane connection based on the address information of the second NF and the second NF.

[0172] The specific process of S910 can be referred to the description of S604-S605 in the first exemplary embodiment, and will not be repeated in this example.

[0173] S911. The UE determines, based on the address information of the first NF sent by the second NF, that the first user plane connection with the first NF has been migrated to the second user plane connection with the second NF.

[0174] S912, the UE confirms the successful establishment of the second user plane connection by controlling the second NF.

[0175] The UE sends a second user plane connection establishment success message to the second NF via the CMF.

[0176] Figure 10 is a schematic diagram of a user plane connection management device provided in an embodiment of this application. The device is integrated into a first communication node. As shown in Figure 10, the device may include a receiving module 1001 and a processing module 1002.

[0177] Specifically, the receiving module 1001 is used to receive user plane migration information during the user plane connection migration process;

[0178] The processing module 1002 is used to determine, based on the user plane migration information, that a first user plane connection with a first network function NF is migrated to a second user plane connection with a second NF.

[0179] Based on the above embodiments, optionally, the receiving module 1001 is specifically used to receive the first user plane connection identifier sent by the second NF;

[0180] The processing module 1002 is specifically used to determine, based on the first user plane connection identifier sent by the second NF, that the first user plane connection with the first NF has been migrated to the second user plane connection with the second NF.

[0181] Based on the above embodiments, optionally, the receiving module 1001 is specifically used to receive the address information of the first NF sent by the second NF;

[0182] The processing module 1002 is specifically used to determine, based on the address information of the first NF sent by the second NF, that the first user plane connection with the first NF has been migrated to the second user plane connection with the second NF.

[0183] Based on the above embodiments, optionally, the receiving module 1001 is specifically used to receive the second NF information sent by the first NF and the second NF information sent by the second NF;

[0184] The processing module 1002 is specifically used to determine, based on the second NF information sent by the first NF and the second NF information sent by the second NF, that the first user plane connection with the first NF is migrated to the second user plane connection with the second NF.

[0185] Based on the above embodiments, optionally, the receiving module 1001 is specifically used to receive the second NF information and the address information of the first NF sent by the first NF through the control plane; or, to receive the second NF information sent by the first NF through the first user plane connection.

[0186] Based on the above embodiments, optionally, the receiving module 1001 is specifically used to receive the second NF information sent by the first NF during the first user plane connection release process.

[0187] Optionally, based on the above embodiments, the user plane migration information includes: migration instruction information.

[0188] Based on the above embodiments, optionally, the first user plane connection identifier includes: the address information of the first NF, the fully qualified domain name of the first NF, the callback Uniform Resource Identifier of the first NF, a string containing the name information of the first NF, or a simple string.

[0189] Optionally, based on the above embodiments, the receiving module 1001 is further configured to receive the user plane connection identifier sent by the NF during the user plane connection establishment process.

[0190] Figure 11 is a schematic diagram of another structure of the user plane connection management device provided in an embodiment of this application. The device is integrated into the second communication node. As shown in Figure 11, the device may include: a sending module 1101.

[0191] Specifically, the sending module 1101 is used to send user plane migration information to the first communication node during the user plane connection migration process;

[0192] The user plane migration information is used to notify the first communication node that the first user plane connection with the first NF has been migrated to the second user plane connection with the second NF.

[0193] Based on the above embodiments, optionally, the sending module 1101 in the second NF is further configured to send a first user plane connection identifier to the first communication node; or, the sending module 1101 in the second NF is further configured to send the address information of the first NF to the first communication node; or, the sending module 1101 in the first NF is further configured to send second NF information to the first communication node and the sending module 1101 in the second NF sends second NF information to the first communication node.

[0194] Based on the above embodiments, optionally, the sending module 1101 in the first NF is further configured to send second NF information to the first communication node through control; or, the sending module 1101 in the first NF is further configured to send second NF information to the first communication node through the first user plane connection.

[0195] Optionally, based on the above embodiments, the sending module 1101 in the first NF is further configured to send second NF information to the first communication node during the first user plane connection release process.

[0196] Based on the above embodiments, optionally, the sending module 1101 in the second NF is further configured to send second NF information to the first NF; or, the sending module 1101 in the first NF is further configured to send a first user plane connection identifier to the second NF; or, the sending module 1101 in the first NF is further configured to send the address information of the first NF to the second NF.

[0197] Optionally, in the process of establishing a user plane connection, the sending module 1101 is also used to send a user plane connection identifier to the first communication node.

[0198] In one embodiment, the internal structure diagram of the communication device described above can be as shown in Figure 12. Optionally, the communication device can be a first communication node or a second communication node provided in any of the above embodiments. The communication device includes a processor, a memory, a network interface, and a database connected via a system bus. The processor of the communication device provides computing and control capabilities. The memory of the communication device includes a non-volatile storage medium and internal memory. The non-volatile storage medium stores an operating system, computer programs, and a database. The internal memory provides an environment for the operation of the operating system and computer programs in the non-volatile storage medium. The database of the communication device stores data generated during user plane connection management. The network interface of the communication device is used to communicate with external terminals via a network connection. When the computer program is executed by the processor, it implements a user plane connection management method.

[0199] Those skilled in the art will understand that the structure shown in Figure 12 is merely a block diagram of a portion of the structure related to the present application and does not constitute a limitation on the communication device to which the present application is applied. Specific communication devices may include more or fewer components than those shown in the figure, or combine certain components, or have different component arrangements.

[0200] This application also provides a computer-readable storage medium storing a computer program that, when executed by a processor, implements the steps of the user plane connection management method provided in any of the above embodiments.

[0201] The computer storage medium in this application embodiment can be any combination of one or more computer-readable media. The computer-readable medium can be a computer-readable signal medium or a computer-readable storage medium. For example, a computer-readable storage medium can be, but is not limited to, an electrical, magnetic, optical, electromagnetic, infrared, or semiconductor system, apparatus, or device, or any combination thereof. Computer-readable storage media include (a non-exhaustive list): electrical connections having one or more wires, portable computer disks, hard disks, random access memory (RAM), read-only memory (ROM), electrically erasable, programmable read-only memory (EPROM), flash memory, optical fiber, portable compact disc read-only memory (CD-ROM), optical storage devices, magnetic storage devices, or any suitable combination thereof. In this application, the computer-readable storage medium can be any tangible medium containing or storing a program that can be used by or in conjunction with an instruction execution system, apparatus, or device.

[0202] Computer-readable signal media may include data signals propagated in baseband or as part of a carrier wave, the data signals carrying computer-readable program code. Such propagated data signals may take various forms, including but not limited to electromagnetic signals, optical signals, or any suitable combination thereof. Computer-readable signal media may also be any computer-readable medium other than computer-readable storage media, which can send, propagate, or transmit programs for use by or in conjunction with an instruction execution system, apparatus, or device.

[0203] Program code contained on a computer-readable medium may be transmitted using any suitable medium, including but not limited to wireless, wire, optical fiber, radio frequency (RF), or any suitable combination thereof.

[0204] Computer program code for performing the operations of this disclosure can be written in one or more programming languages ​​or a combination of programming languages, including object-oriented programming languages ​​(such as Java, Smalltalk, C++, Ruby, and Go) and conventional procedural programming languages ​​(such as the "C" language or similar programming languages). The program code can be executed entirely on the user's computer, partially on the user's computer, as a standalone software package, partially on the user's computer and partially on a remote computer, or entirely on a remote computer or server. In cases involving remote computers, the remote computer can be connected to the user's computer via any type of network (including a Local Area Network (LAN) or a Wide Area Network (WAN)), or it can be connected to an external computer (e.g., via the Internet using an Internet service provider).

[0205] Those skilled in the art will understand that the term user terminal encompasses any suitable type of wireless user equipment, such as mobile phones, portable data processing devices, portable web browsers, or vehicle-mounted mobile stations.

[0206] Generally, the various embodiments of this application can be implemented in hardware or dedicated circuitry, software, logic, or any combination thereof. For example, some aspects can be implemented in hardware, while others can be implemented in firmware or software that can be executed by a controller, microprocessor, or other computing device, although this application is not limited thereto.

[0207] Embodiments of this application can be implemented by executing computer program instructions through the data processor of a mobile device, for example, in a processor entity, or through hardware, or through a combination of software and hardware. The computer program instructions can be assembly instructions, Instruction Set Architecture (ISA) instructions, machine instructions, machine-dependent instructions, microcode, firmware instructions, status setting data, or source code or object code written in any combination of one or more programming languages.

[0208] Any block diagram of logical flow in the accompanying drawings of this application may represent program steps, or may represent interconnected logic circuits, modules, and functions, or may represent a combination of program steps and logic circuits, modules, and functions. The computer program may be stored in memory. The memory may be of any type suitable to the local technical environment and may be implemented using any suitable data storage technology, such as, but not limited to, read-only memory (ROM), random access memory (RAM), optical storage devices and systems (Digital Multifunction Discs, DVDs, or CDs), etc. Computer-readable media may include non-transitory storage media. The data processor may be of any type suitable to the local technical environment, such as, but not limited to, general-purpose computers, special-purpose computers, microprocessors, digital signal processors (DSPs), application-specific integrated circuits (ASICs), field-programmable gate arrays (FPGAs), and processors based on multi-core processor architectures.

Claims

1. A user plane connection management method, characterized in that, Applied to a first communication node, the method includes: receiving user plane migration information during the user plane connection migration process; and determining, based on the user plane migration information, that a first user plane connection with a first network function NF is migrated to a second user plane connection with a second NF.

2. The method according to claim 1, characterized in that, The step of receiving user plane migration information includes: receiving a first user plane connection identifier sent by a second NF; the step of determining, based on the user plane migration information, that the first user plane connection with the first NF has been migrated to a second user plane connection with the second NF includes: determining, based on the first user plane connection identifier sent by the second NF, that the first user plane connection with the first NF has been migrated to a second user plane connection with the second NF.

3. The method according to claim 1, characterized in that, The step of receiving user plane migration information includes: receiving address information of the first NF sent by the second NF; the step of determining, based on the user plane migration information, that the first user plane connection with the first NF has been migrated to the second user plane connection with the second NF includes: determining, based on the address information of the first NF sent by the second NF, that the first user plane connection with the first NF has been migrated to the second user plane connection with the second NF.

4. The method according to claim 1, characterized in that, The step of receiving user plane migration information includes: receiving second NF information sent by a first NF and second NF information sent by a second label NF; the step of determining, based on the user plane migration information, that the first user plane connection with the first NF has been migrated to the second user plane connection with the second NF includes: determining, based on the second NF information sent by the first NF and the second label NF information sent by the second NF, that the first user plane connection with the first NF has been migrated to the second user plane connection with the second NF.

5. The method according to claim 4, characterized in that, Receiving the second NF information sent by the first NF includes: receiving the second NF information and the address information of the first NF sent by the first NF through the control plane; or, receiving the second NF information sent by the first NF through the first user plane connection.

6. The method according to claim 5, characterized in that, Receiving the second NF information sent by the first NF through the first user plane connection includes: receiving the second NF information sent by the first NF during the release of the first user plane connection.

7. The method according to any one of claims 1 to 6, characterized in that, The user plane migration information includes: migration indication information, which is used to indicate that the user plane connection has migrated.

8. The method according to any one of claims 1 to 6, characterized in that, The first user plane connection identifier includes: the address information of the first NF, the fully qualified domain name of the first NF, the callback Uniform Resource Identifier of the first NF, a string containing the name information of the first NF, or a string.

9. The method according to any one of claims 1 to 6, characterized in that, Also includes: During the user plane connection establishment process, receive the user plane connection identifier sent by NF.

10. A user plane connection management method, characterized in that, The method is applied to a second communication node and includes: during the user plane connection migration process, sending user plane migration information to a first communication node; wherein the user plane migration information is used to notify the first communication node that the first user plane connection with the first NF has been migrated to the second user plane connection with the second NF.

11. The method according to claim 10, characterized in that, Sending user plane migration information to the first communication node includes: the second NF sending a first user plane connection identifier to the first communication node; or, the second NF sending the address information of the first NF to the first communication node; or, the first NF sending second NF information to the first communication node and the second NF sending second NF information to the first communication node.

12. The method according to claim 11, characterized in that, The first NF sends second NF information to the first communication node, including: the first NF sending second NF information to the first communication node through a control plane; or, the first NF sending second NF information to the first communication node through the first user plane connection.

13. The method according to claim 12, characterized in that, The first NF sends second NF information to the first communication node through the first user plane connection, including: the first NF sending second NF information to the first communication node during the release of the first user plane connection.

14. The method according to claim 11, characterized in that, Also includes: The second NF sends second NF information to the first NF; or, the first NF sends the first user plane connection identifier to the second NF; or, the first NF sends the address information of the first NF to the second NF.

15. The method according to any one of claims 10 to 14, characterized in that, Also includes: During the user plane connection establishment process, a user plane connection identifier is sent to the first communication node.

16. A communication device, characterized in that, include: A memory and a processor, the memory storing a computer program, the processor executing the computer program to implement the steps of the method according to any one of claims 1-15.

17. A computer-readable storage medium, characterized in that, The storage medium stores a computer program that, when executed by a processor, implements the steps of the method according to any one of claims 1-15.

Images