Method and device for establishing user plane connection, and storage medium

Abstract

The invention provides a method and device for establishing user plane connection and a storage medium, and the method comprises the steps: transmitting a first request message related to a PDU session to a first network element of a core network, the first request message being also used for initiating user plane positioning; receiving a response message sent by the first network element, and determining a PDU session for user plane positioning, the response message comprising user plane information; and establishing a user plane connection with a second network element of the core network through the PDU session based on the user plane information, the user plane connection being used for user plane positioning. According to the method and the device, the user plane connection and the user plane positioning can be simultaneously initiated through the first request message related to the PDU session, so that the availability and the reliability of the user plane positioning are improved while signaling resources are saved.

Description

Method, device and storage medium for establishing user plane connection Technical Field

[0001] The present disclosure relates to the field of communications, and in particular to a method and device for establishing a user plane connection, and a storage medium. Background Art

[0002] Currently, user plane positioning can provide more efficient communication overload, a single session can handle multiple transactions, and supports multiple positioning methods for terminals.

[0003] Summary of the Invention

[0004] The prerequisite for user plane positioning is to establish a user plane connection between the terminal and the functional device corresponding to the core network. However, the message used to initiate user plane positioning is not applicable to initiating a user plane connection, resulting in the inability to establish a user plane connection for user plane positioning.

[0005] Embodiments of the present disclosure provide a method, apparatus, and storage medium for establishing a user plane connection.

[0006] According to a first aspect of an embodiment of the present disclosure, a method for establishing a user plane connection is provided, the method being performed by a terminal and including:

[0007] Sending a first request message related to a protocol data unit (PDU) session to a first network element of a core network, where the first request message is also used to initiate user plane positioning;

[0008] receiving a response message sent by the first network element, determining a PDU session for user plane positioning, the response message including user plane information;

[0009] Based on the user plane information, a user plane connection is established with a second network element of a core network through the PDU session, where the user plane connection is used for user plane positioning.

[0010] According to a second aspect of an embodiment of the present disclosure, a method for establishing a user plane connection is provided, the method being performed by a first network element of a core network, including:

[0011] receiving a first request message related to a protocol data unit (PDU) session sent by a terminal, where the first request message is also used to initiate user plane positioning;

[0012] A response message including user plane information is sent to the terminal, so that the terminal determines the PDU session for user plane positioning based on the response message, and then establishes a user plane connection with the second network element of the core network through the PDU session based on the user plane information, and the user plane connection is used for user plane positioning.

[0013] According to a third aspect of an embodiment of the present disclosure, a method for establishing a user plane connection is provided, where the method is performed by a third network element of a core network, including:

[0014] receiving a second request message related to the PDU session sent by a second network element of the core network;

[0015] Based on the second request message, a fourth network element of the core network is selected for the terminal, where the fourth network element is used to implement a user plane function.

[0016] According to a fourth aspect of an embodiment of the present disclosure, a terminal is provided, comprising:

[0017] a transceiver module configured to send a first request message related to a protocol data unit (PDU) session to a first network element of a core network, wherein the first request message is further used to initiate user plane positioning;

[0018] a processing module configured to receive a response message sent by the first network element and determine a PDU session for user plane positioning, wherein the response message includes user plane information;

[0019] The processing module is further configured to establish a user plane connection with a second network element of the core network through the PDU session based on the user plane information, where the user plane connection is used for user plane positioning.

[0020] According to a fifth aspect of an embodiment of the present disclosure, a first network element of a core network is provided, the first network element including:

[0021] a transceiver module configured to receive a first request message related to a protocol data unit (PDU) session sent by a terminal, wherein the first request message is also used to initiate user plane positioning;

[0022] The transceiver module is also configured to send a response message including user plane information to the terminal, so that after the terminal determines the PDU session for user plane positioning based on the response message, the terminal establishes a user plane connection with the second network element of the core network through the PDU session based on the user plane information, and the user plane connection is used for user plane positioning.

[0023] According to a sixth aspect of an embodiment of the present disclosure, a third network element of a core network is provided, the third network element including:

[0024] a transceiver module configured to receive a second request message related to the PDU session sent by a second network element of the core network;

[0025] The processing module is configured to select a fourth network element of the core network for the terminal based on the second request message, where the fourth network element is used to implement a user plane function.

[0026] According to a seventh aspect of an embodiment of the present disclosure, a terminal is provided, including:

[0027] one or more processors;

[0028] The terminal is used to execute the method for establishing a user plane connection described in any one of the first aspects.

[0029] According to an eighth aspect of an embodiment of the present disclosure, a first network element of a core network is provided, including:

[0030] one or more processors;

[0031] The first network element is used to execute the method for establishing a user plane connection as described in any one of the second aspects.

[0032] According to a ninth aspect of an embodiment of the present disclosure, a third network element of a core network is provided, including:

[0033] one or more processors;

[0034] The first network element is used to execute the method for establishing a user plane connection as described in any one of the third aspects.

[0035] According to a tenth aspect of an embodiment of the present disclosure, a core network device is provided, including:

[0036] A first network element, wherein the first network element is configured to implement the method for establishing a user plane connection according to any one of the second aspects;

[0037] a second network element, the second network element being configured to send user plane information to the first network element;

[0038] A third network element, the third network element being configured to implement the method for establishing a user plane connection as described in any one of the third aspects;

[0039] The fourth network element is used to implement user plane functions.

[0040] According to the eleventh aspect of an embodiment of the present disclosure, a communication system is provided, comprising a terminal and a core network device, wherein the terminal is configured to implement the method for establishing a user plane connection as described in any one of the first aspect, and the core network device is configured to implement the method for establishing a user plane connection as described in any one of the second aspect and the third aspect.

[0041] According to the twelfth aspect of an embodiment of the present disclosure, a storage medium is provided, which stores instructions. When the instructions are executed on a communication device, the communication device executes the method for establishing a user plane connection as described in any one of the first aspect, the second aspect or the third aspect.

[0042] The embodiment of the present disclosure can simultaneously initiate user plane connection and user plane positioning through a first request message related to a PDU session, thereby saving signaling resources and improving the availability and reliability of user plane positioning.

[0043] It is to be understood that the foregoing general description and the following detailed description are exemplary and explanatory only and are not restrictive of the disclosure. BRIEF DESCRIPTION OF THE DRAWINGS

[0044] The accompanying drawings, which are incorporated in and constitute a part of this specification, illustrate embodiments consistent with the invention and, together with the description, serve to explain the principles of the invention.

[0045] FIG1 is an exemplary schematic diagram of the architecture of a communication system provided according to an embodiment of the present disclosure.

[0046] FIG2 is an exemplary interaction diagram of a method for establishing a user plane connection according to an embodiment of the present disclosure.

[0047] FIG3 is an exemplary interaction diagram of a method for establishing a user plane connection according to an embodiment of the present disclosure.

[0048] FIG4A is a schematic diagram of an exemplary interaction of a method for establishing a user plane connection according to an embodiment of the present disclosure.

[0049] FIG4B is a schematic diagram of an exemplary interaction of a method for establishing a user plane connection according to an embodiment of the present disclosure.

[0050] FIG5 is an exemplary interaction diagram of a method for establishing a user plane connection according to an embodiment of the present disclosure.

[0051] FIG6A is a schematic diagram of an exemplary interaction of a method for establishing a user plane connection according to an embodiment of the present disclosure.

[0052] FIG6B is a schematic diagram of an exemplary interaction of a method for establishing a user plane connection according to an embodiment of the present disclosure.

[0053] FIG7A is a schematic diagram of an exemplary interaction of an apparatus for establishing a user plane connection according to an embodiment of the present disclosure.

[0054] FIG7B is a schematic diagram of an exemplary interaction of an apparatus for establishing a user plane connection according to an embodiment of the present disclosure.

[0055] FIG7C is a schematic diagram of an exemplary interaction of an apparatus for establishing a user plane connection according to an embodiment of the present disclosure.

[0056] FIG7D is a schematic diagram of an exemplary interaction of an apparatus for establishing a user plane connection according to an embodiment of the present disclosure.

[0057] FIG7E is a schematic diagram of an exemplary interaction of an apparatus for establishing a user plane connection according to an embodiment of the present disclosure.

[0058] FIG8A is a schematic diagram of an exemplary interaction of a communication device according to an embodiment of the present disclosure.

[0059] FIG8B is an exemplary interaction diagram of a chip provided according to an embodiment of the present disclosure. DETAILED DESCRIPTION

[0060] Exemplary embodiments will be described in detail herein, with examples illustrated in the accompanying drawings. In the following description, when referring to the drawings, like numbers in different figures represent like or similar elements unless otherwise indicated. The embodiments described in the following exemplary embodiments are not intended to represent all possible embodiments consistent with the present invention. Rather, they are merely examples of apparatus and methods consistent with certain aspects of the present invention, as detailed in the appended claims.

[0061] The terms used in this disclosure are for the purpose of describing specific embodiments only and are not intended to limit the disclosure. As used in this disclosure and the appended claims, the singular forms "a," "an," "the," and "the" are intended to include the plural forms, unless the context clearly indicates otherwise. It should also be understood that the term "and / or" as used herein refers to and encompasses any and all possible combinations of at least one of the associated listed items.

[0062] It should be understood that although the terms first, second, third, etc. may be used in this disclosure to describe various messages, these messages should not be limited to these terms. These terms are only used to distinguish messages of the same type from each other. For example, a first message may also be referred to as a second message, and similarly, a second message may be referred to as a first message without departing from the scope of this disclosure. Depending on the context, the word "if" as used herein may be interpreted as "at the time of" or "when" or "in response to determining."

[0063] The embodiments of the present disclosure provide a method, an apparatus, and a storage medium for establishing a user plane connection.

[0064] In a first aspect, an embodiment of the present disclosure provides a method for establishing a user plane connection, the method being executed by a terminal and comprising:

[0065] Sending a first request message related to a protocol data unit (PDU) session to a first network element of a core network, where the first request message is also used to initiate user plane positioning;

[0066] receiving a response message sent by the first network element, determining a PDU session for user plane positioning, the response message including user plane information;

[0067] Based on the user plane information, a user plane connection is established with a second network element of a core network through the PDU session, where the user plane connection is used for user plane positioning.

[0068] In the above embodiment, the terminal can simultaneously initiate user plane connection and user plane positioning through the first request message related to the PDU session, which saves signaling resources and improves the availability and reliability of user plane positioning.

[0069] In conjunction with some embodiments of the first aspect, in some embodiments, the first request message is an uplink non-access layer transmission (UL NAS TRANSPORT) message;

[0070] The response message is a downlink non-access layer transport (DL NAS TRANSPORT) message.

[0071] In the above embodiment, the terminal can reuse the uplink non-access layer transmission message to simultaneously initiate user plane connection and user plane positioning, and receive the downlink non-access layer transmission message returned by the first network element of the core network, thereby expanding the application scenarios of the non-access layer transmission message and having high availability.

[0072] In conjunction with some embodiments of the first aspect, in some embodiments, the first request message includes any one or more of the following:

[0073] PDU Session Establishment Request message;

[0074] PDU Session Modification Request message.

[0075] In the above embodiment, the terminal can reuse the PDU session establishment request message or the PDU session modification request message, and initiate user plane positioning to the first network element of the core network while initiating the PDU session establishment request or the PDU session modification request. By reusing existing messages, the complexity of modifying the protocol is reduced and the availability is high.

[0076] In conjunction with some embodiments of the first aspect, in some embodiments, the first request message includes at least one of the following:

[0077] A request type parameter, where the type value of the request type parameter is used to indicate a user plane positioning request, and the user plane positioning request is used to request initiation of the user plane positioning;

[0078] A first parameter, the first parameter is used to indicate the user plane positioning request;

[0079] a user plane positioning information container (user plane positioning information container) and an information element (IE) containing first additional information, wherein the user plane positioning information container and the first additional information are used to indicate the user plane positioning request;

[0080] A first payload container (payload container), where the first payload container is used to indicate the user plane positioning request.

[0081] In the above embodiment, the terminal can use a variety of methods to enable the first request message related to the PDU session to initiate user plane positioning, which is simple to implement and has high availability.

[0082] In conjunction with some embodiments of the first aspect, in some embodiments, receiving a response message sent by the first network element includes:

[0083] receiving a first response message sent by the first network element, where the first response message includes the user plane information; and

[0084] Receive a second response message sent by the first network element, where the second response message includes PDU session response information.

[0085] In the above embodiment, the terminal can obtain user plane information and a PDU session response message from the core network side through different response messages, so as to determine the PDU session used for user plane positioning based on the PDU session response message. Then, based on the user plane information, the terminal can establish a user plane connection with the second network element of the core network through the PDU session, and the user plane connection is used for user plane positioning. This achieves the purpose of simultaneously initiating a user plane connection and user plane positioning through the first request message, saving signaling resources and improving the availability and reliability of user plane positioning.

[0086] In combination with some embodiments of the first aspect, in some embodiments, receiving a response message sent by the first network element and determining a PDU session for user plane positioning includes:

[0087] The first response message and the second response message are received, and the PDU session for user plane positioning is determined.

[0088] In the above embodiment, the terminal needs to wait for another response message sent by the first network element when receiving the first response message or the second response message from the first network element side of the core network, and then determine the PDU session when receiving the first response message and the second response message to ensure the reliability of establishing the user plane connection.

[0089] In combination with some embodiments of the first aspect, in some embodiments, receiving a response message sent by the first network element and determining a PDU session for user plane positioning includes:

[0090] Receive a third response message sent by the first network element, where the third response message includes the user plane information and PDU session response information.

[0091] In the above embodiment, the terminal can receive a third response message from the first network element side of the core network, and obtain user plane information and PDU session response message from it. There is no need for the first network element to send multiple response messages, thus saving signaling resources.

[0092] In a second aspect, an embodiment of the present disclosure provides a method for establishing a user plane connection, the method being performed by a first network element of a core network, including:

[0093] receiving a first request message related to a protocol data unit (PDU) session sent by a terminal, where the first request message is also used to initiate user plane positioning;

[0094] A response message including user plane information is sent to the terminal, so that the terminal determines the PDU session used for the user plane positioning based on the response message, and then establishes a user plane connection with the second network element of the core network through the PDU session based on the user plane information, and the user plane connection is used for user plane positioning.

[0095] In the above embodiment, after receiving a first request message related to a PDU session sent by a terminal, the first network element of the core network can send a response message including user plane information to the terminal. This response message can be used by the terminal to determine a PDU session for user plane positioning, and based on the user plane information included in the response message, select a second network element of the core network, and establish a user plane connection with the selected second network element of the core network through the PDU session. The user plane connection is used for user plane positioning. This achieves the purpose of simultaneously initiating a user plane connection and user plane positioning through the first request message related to the PDU session, saving signaling resources and improving the availability and reliability of user plane positioning.

[0096] In conjunction with some embodiments of the second aspect, in some embodiments, the first request message is an uplink non-access layer transmission message;

[0097] The response message is a downlink non-access layer transmission message.

[0098] In conjunction with some embodiments of the second aspect, in some embodiments, the first request message includes any one or more of the following:

[0099] PDU session establishment request message;

[0100] PDU Session Modification Request message.

[0101] In conjunction with some embodiments of the second aspect, in some embodiments, the first request message includes at least one of the following:

[0102] A request type parameter, where the type value of the request type parameter is used to indicate a user plane positioning request, and the user plane positioning request is used to request initiation of the user plane positioning;

[0103] A first parameter, the first parameter is used to indicate the user plane positioning request;

[0104] An information element containing a user plane positioning information container and first additional information, wherein the user plane positioning information container and the first additional information are used to indicate the user plane positioning request;

[0105] A first payload container, where the first payload container is used to indicate the user plane positioning request.

[0106] In conjunction with some embodiments of the second aspect, in some embodiments, the method further includes:

[0107] Selecting, based on the first request message, the second network element and the third network element of the core network for the terminal respectively;

[0108] Receive the user plane information sent by the second network element, and receive PDU session response information sent by the third network element.

[0109] In the above embodiment, the first network element of the core network can select a second network element and a third network element for the terminal based on the first request message sent by the terminal. The second network element can provide user plane information to the terminal, and the third network element can respond to the PDU session. This achieves the purpose of simultaneously initiating a PDU session user plane connection and user plane positioning via the first request message related to the PDU session, saving signaling resources while improving the availability and reliability of user plane positioning.

[0110] In conjunction with some embodiments of the second aspect, in some embodiments, selecting the second network element and the third network element of the core network for the terminal based on the first request message includes:

[0111] After selecting the second network element for the terminal, the third network element is selected for the terminal based on the first request message and the selected second network element.

[0112] In the above embodiment, if the first network element of the core network first selects the second network element for the terminal, then based on the first request message and the selected second network element, the third network element is selected for the terminal, thereby improving the reliability of selecting the third network element.

[0113] In conjunction with some embodiments of the second aspect, in some embodiments, the method further includes:

[0114] Send a second request message related to the PDU session to the selected third network element.

[0115] In the above embodiment, after the first network element selects a third network element for the terminal, it can send a second request message related to the PDU session to the selected third network element to obtain the PDU session response information returned by the third network element, so that the terminal can determine the PDU session for user plane connection with high availability.

[0116] In conjunction with some embodiments of the second aspect, in some embodiments, the second request message is any one or more of the following:

[0117] PDU session create session management context request (Nsmf_PDUSession_CreateSMContext) message;

[0118] PDU session update session management context request (Nsmf_PDUSession_UpdateSMContext) message.

[0119] In the above embodiment, the first network element can reuse the existing PDU session creation session management context request message or PDU session update session management context request message to establish a PDU session or modify the PDU session between the terminal and the third network element, with minimal changes to the protocol and high availability.

[0120] In conjunction with some embodiments of the second aspect, in some embodiments, the second request message includes:

[0121] Related information of the second network element.

[0122] In the above embodiment, if the first network element of the core network first selects the second network element for the terminal, when the first network element selects the third network element and sends a second request message to the selected third network element, it may include relevant information of the second network element previously selected for the terminal, thereby improving the reliability of creating or modifying the PDU session.

[0123] In conjunction with some embodiments of the second aspect, in some embodiments, selecting the second network element and the third network element of the core network for the terminal based on the first request message includes:

[0124] After selecting the third network element for the terminal, the second network element is selected for the terminal based on the first request message and the selected third network element.

[0125] In the above embodiment, if the first network element of the core network first selects a third network element for the terminal, then based on the first request message and the selected third network element, the second network element is selected for the terminal, thereby improving the reliability of selecting the second network element.

[0126] In conjunction with some embodiments of the second aspect, in some embodiments, the method further includes:

[0127] A third request message is sent to the selected second network element, where the third request message is used to request establishment of a user plane connection.

[0128] In the above embodiment, after the first network element selects the second network element for the terminal, it may send a third request message to the selected second network element to determine user plane information for the terminal, thereby improving the reliability of establishing the user plane connection.

[0129] In conjunction with some embodiments of the second aspect, in some embodiments, the third request message includes:

[0130] Relevant information of the third network element.

[0131] In the above embodiment, if the first network element of the core network first selects a third network element for the terminal, when the first network element selects a second network element and sends a third request message to the selected second network element, it may include relevant information of the third network element previously selected for the terminal, thereby improving the reliability of establishing the user plane connection.

[0132] In conjunction with some embodiments of the second aspect, in some embodiments, sending a response message to the terminal includes:

[0133] receiving the user plane information sent by the second network element, and sending a first response message to the terminal, where the first response message includes the user plane information; and

[0134] Receive the PDU session response information sent by the third network element, and send a second response message to the terminal, where the second response message includes the PDU session response information.

[0135] In conjunction with some embodiments of the second aspect, in some embodiments, sending a response message to the terminal includes:

[0136] Receive the user plane information sent by the second network element and the PDU session response information sent by the third network element, and send a third response message to the terminal, wherein the third response message includes the user plane information and the PDU session response information.

[0137] In a third aspect, an embodiment of the present disclosure provides a method for establishing a user plane connection, the method being performed by a third network element of a core network, including:

[0138] receiving a second request message related to the PDU session sent by a second network element of the core network;

[0139] Based on the second request message, a fourth network element of the core network is selected for the terminal, where the fourth network element is used to implement a user plane function.

[0140] In the above embodiment, after receiving the second request message related to the PDU session sent by the second network element, the third network element of the core network can select a fourth network element of the core network for the terminal based on the second request message. The fourth network element is used to implement user plane functions. This improves the reliability of establishing the user plane connection.

[0141] In conjunction with some embodiments of the third aspect, in some embodiments, the second request message is any one or more of the following:

[0142] PDU session create SM context request message;

[0143] PDU Session Update SM Context Request message.

[0144] In conjunction with some embodiments of the third aspect, in some embodiments, the second request message includes:

[0145] Related information of the second network element.

[0146] In a fourth aspect, an embodiment of the present disclosure provides a terminal, comprising:

[0147] a transceiver module configured to send a first request message related to a protocol data unit (PDU) session to a first network element of a core network, wherein the first request message is further used to initiate user plane positioning;

[0148] a processing module configured to receive a response message sent by the first network element and determine a PDU session for user plane positioning, wherein the response message includes user plane information;

[0149] The processing module is further configured to establish a user plane connection with a second network element of the core network through the PDU session based on the user plane information, where the user plane connection is used for user plane positioning.

[0150] In a fifth aspect, an embodiment of the present disclosure provides a first network element of a core network, where the first network element includes:

[0151] a transceiver module configured to receive a first request message related to a protocol data unit (PDU) session sent by a terminal, wherein the first request message is also used to initiate user plane positioning;

[0152] The transceiver module is also configured to send a response message including user plane information to the terminal, so that the terminal determines the PDU session used for the user plane positioning based on the response message, and then establishes a user plane connection with the second network element of the core network through the PDU session based on the user plane information, and the user plane connection is used for user plane positioning.

[0153] In a sixth aspect, an embodiment of the present disclosure provides a third network element of a core network, the third network element including:

[0154] a transceiver module configured to receive a second request message related to the PDU session sent by a second network element of the core network;

[0155] The processing module is configured to select a fourth network element of the core network for the terminal based on the second request message, where the fourth network element is used to implement a user plane function.

[0156] In a seventh aspect, an embodiment of the present disclosure provides a terminal, including:

[0157] one or more processors;

[0158] The terminal is used to execute the method for establishing a user plane connection described in any one of the first aspects.

[0159] In an eighth aspect, an embodiment of the present disclosure provides a first network element of a core network, including:

[0160] one or more processors;

[0161] The first network element is used to execute the method for establishing a user plane connection as described in any one of the second aspects.

[0162] In a ninth aspect, an embodiment of the present disclosure provides a third network element of a core network, including:

[0163] one or more processors;

[0164] The first network element is used to execute the method for establishing a user plane connection as described in any one of the third aspects.

[0165] In a tenth aspect, an embodiment of the present disclosure provides a core network device, including:

[0166] A first network element, wherein the first network element is configured to implement the method for establishing a user plane connection according to any one of the second aspects;

[0167] a second network element, the second network element being configured to send user plane information to the first network element;

[0168] A third network element, the third network element being configured to implement the method for establishing a user plane connection according to any one of the third aspects;

[0169] The fourth network element is used to implement user plane functions.

[0170] In the eleventh aspect, an embodiment of the present disclosure proposes a communication system, including a terminal and a core network device, wherein the terminal is configured to implement the method for establishing a user plane connection described in any one of the first aspect, and the core network device is configured to implement the method for establishing a user plane connection described in any one of the second aspect or the third aspect.

[0171] In the twelfth aspect, an embodiment of the present disclosure proposes a storage medium, which stores instructions. When the instructions are executed on a communication device, the communication device executes the method for establishing a user plane connection as described in any one of the first, second or third aspects of the claim.

[0172] It is understandable that the above-mentioned terminal, access network device, first network element, second network element, core network device, communication system, storage medium, and computer program are all used to execute the method proposed in the embodiment of the present disclosure. Therefore, the beneficial effects that can be achieved can refer to the beneficial effects of the corresponding method and will not be repeated here.

[0173] The present disclosure provides a method, apparatus, and storage medium for establishing a user plane connection. In some embodiments, the terms "method for establishing a user plane connection" and "information processing method" and "communication method" are interchangeable; "apparatus for establishing a user plane connection" and "information processing apparatus" and "communication apparatus" are interchangeable; and "information processing system" and "communication system" are interchangeable.

[0174] The embodiments of the present disclosure are not exhaustive and are merely illustrative of some embodiments, and are not intended to be a specific limitation on the scope of protection of the present disclosure. In the absence of contradiction, each step in a certain embodiment can be implemented as an independent embodiment, and the steps can be arbitrarily combined. For example, a solution after removing some steps in a certain embodiment can also be implemented as an independent embodiment, and the order of the steps in a certain embodiment can be arbitrarily exchanged. In addition, the optional implementation methods in a certain embodiment can be arbitrarily combined; in addition, the embodiments can be arbitrarily combined. For example, some or all steps of different embodiments can be arbitrarily combined, and a certain embodiment can be arbitrarily combined with the optional implementation methods of other embodiments.

[0175] In each embodiment of the present disclosure, unless otherwise specified or provided for by logic, the terms and / or descriptions between the embodiments are consistent and can be referenced by each other. The technical features in different embodiments can be combined to form a new embodiment based on their inherent logical relationships.

[0176] The terms used in the embodiments of the present disclosure are only for the purpose of describing specific embodiments and are not intended to limit the present disclosure.

[0177] In the embodiments of the present disclosure, unless otherwise specified, elements expressed in the singular, such as "a", "an", "the", "above", "said", "the", "the", etc., may mean "one and only one", or "one or more", "at least one", etc. For example, when using articles such as "a", "an", "the" in English in translation, the noun following the article may be understood as a singular expression or a plural expression.

[0178] In the embodiments of the present disclosure, “plurality” refers to two or more.

[0179] In some embodiments, the terms "at least one," "one or more," "a plurality of," "multiple," etc. may be used interchangeably.

[0180] In some embodiments, descriptions such as "at least one of A and B," "A and / or B," "A in one case, B in another case," or "in response to one case A, in response to another case B" may include the following technical solutions depending on the situation: in some embodiments, A (A is executed independently of B); in some embodiments, B (B is executed independently of A); in some embodiments, execution is selected from A and B (A and B are selectively executed); and in some embodiments, A and B (both A and B are executed). The above is also applicable when there are more branches such as A, B, and C.

[0181] In some embodiments, "A or B" and other descriptions may include the following technical solutions depending on the situation: in some embodiments, A (A is executed independently of B); in some embodiments, B (B is executed independently of A); in some embodiments, execution is selected from A and B (A and B are selectively executed). The above is also applicable when there are more branches such as A, B, C, etc.

[0182] The prefixes such as "first" and "second" in the embodiments of the present disclosure are only used to distinguish different description objects and do not constitute any restriction on the position, order, priority, quantity or content of the description objects. For the statement of the description object, please refer to the description in the context of the claims or embodiments, and no unnecessary restriction should be constituted due to the use of prefixes. For example, if the description object is a "field", the ordinal number before the "field" in the "first field" and the "second field" does not limit the position or order between the "fields". "First" and "second" do not limit whether the "fields" they modify are in the same message, nor do they limit the order of the "first field" and the "second field". For another example, if the description object is a "level", the ordinal number before the "level" in the "first level" and the "second level" does not limit the priority between the "levels". For another example, the number of description objects is not limited by the ordinal number and can be one or more. Taking "first device" as an example, the number of "devices" can be one or more. In addition, the objects modified by different prefixes can be the same or different. For example, if the description object is "device", then the "first device" and the "second device" can be the same device or different devices, and their types can be the same or different; for another example, if the description object is "information", then the "first information" and the "second information" can be the same information or different information, and their contents can be the same or different.

[0183] In some embodiments, “including A,” “comprising A,” “used to indicate A,” and “carrying A” can be interpreted as directly carrying A or indirectly indicating A.

[0184] In some embodiments, terms such as "in response to...", "in response to determining...", "in the case of...", "at the time of...", "when...", "if...", "if...", etc. can be used interchangeably.

[0185] In some embodiments, devices and equipment can be interpreted as physical or virtual, and their names are not limited to the names recorded in the embodiments. In some cases, they can also be understood as "equipment", "device", "circuit", "network element", "node", "function", "unit", "section", "system", "network", "entity", "subject", etc.

[0186] In some embodiments, "network" can be interpreted as devices included in the network, such as access network equipment, core network equipment, etc.

[0187] In some embodiments, "access network device (AN device)" may also be referred to as "radio access network device (RAN device)", "base station (BS)", "radio base station", "fixed station", and in some embodiments may also be understood as "node", "access point", "transmission point (TP)", "reception point (RP)", "transmission and / or reception point (TRP)" "panel", "antenna panel", "antenna array", "cell", "macro cell", "small cell", "femto cell", "pico cell", "sector", "cell group", "serving cell", "carrier", "component carrier", "bandwidth part (BWP)", etc.

[0188] In some embodiments, "terminal" or "terminal device" may be referred to as "user equipment (UE)", "user terminal" "mobile station (MS)", "mobile terminal (MT)", subscriber station, mobile unit, subscriber unit, wireless unit, remote unit, mobile device, wireless device, wireless communication device, remote device, mobile subscriber station, access terminal, mobile terminal, wireless terminal, remote terminal, handset, user agent, mobile client, client, etc.

[0189] In some embodiments, obtaining data, information, etc. may comply with the laws and regulations of the country where the data is obtained.

[0190] In some embodiments, data, information, etc. may be obtained with the user's consent.

[0191] In addition, each element, each row, or each column in the table of the embodiment of the present disclosure can be implemented as an independent embodiment, and the combination of any elements, any rows, and any columns can also be implemented as an independent embodiment.

[0192] FIG1 is a schematic diagram showing the architecture of a communication system according to an embodiment of the present disclosure.

[0193] As shown in FIG1 , a communication system 100 includes a terminal 101 , an access network device 102 , and a core network device 103 .

[0194] In some embodiments, the terminal 101 includes, for example, a mobile phone, a wearable device, an Internet of Things device, a car with communication function, a smart car, a tablet computer, a computer with wireless transceiver function, a virtual reality (VR) terminal device, an augmented reality (AR) terminal device, a wireless terminal device in industrial control, a wireless terminal device in self-driving, a wireless terminal device in remote medical surgery, a wireless terminal device in a smart grid, a wireless terminal device in transportation safety, a wireless terminal device in a smart city, and at least one of a wireless terminal device in a smart home, but is not limited thereto.

[0195] In some embodiments, the access network device 102 is, for example, a node or device that accesses a terminal to a wireless network. The access network device may include an evolved NodeB (eNB), a next generation evolved NodeB (ng-eNB), a next generation NodeB (gNB), a node B (NB), a home node B (HNB), a home evolved nodeB (HeNB), a wireless backhaul device, a radio network controller (RNC), a base station controller (BSC), a base transceiver station (BTS), a base band unit (BBU), a mobile switching center, a base station in a 6G communication system, an open base station (Open RAN), a cloud base station (Cloud RAN), a base station in other communication systems, and at least one of an access node in a Wi-Fi system, but is not limited thereto.

[0196] In some embodiments, the technical solution of the present disclosure can be applied to the Open RAN architecture. In this case, the interfaces between or within the access network devices involved in the embodiments of the present disclosure can be transformed into internal interfaces of the Open RAN, and the processes and information interactions between these internal interfaces can be implemented through software or programs.

[0197] In some embodiments, the access network device 102 can be composed of a centralized unit (CU) and a distributed unit (DU), where the CU can also be called a control unit. The CU-DU structure can be used to split the protocol layer of the access network device, with the functions of some protocol layers centrally controlled by the CU, and the functions of the remaining part or all of the protocol layers distributed in the DU, which is centrally controlled by the CU, but is not limited to this.

[0198] In some embodiments, the core network device 103 may be a single device including a first network element 1031, a second network element 1032, a third network element 1033, a fourth network element 1034, etc., or may be a plurality of devices or a device group including all or part of the first network element 1031, the second network element 1032, the third network element 1033, the fourth network element 1034, etc. The network element may be virtual or physical. The core network may include, for example, at least one of an evolved packet core (EPC), a 5G core network (5GCN), and a next generation core (NGC).

[0199] In some embodiments, the first network element 1031 is, for example, an authentication management function (AMF).

[0200] In some embodiments, the first network element 1031 is used for registration management, connection management, accessibility management, mobility management, and various functions related to security and access management and authorization.

[0201] In some embodiments, the second network element 1032 is, for example, a location management function (LMF).

[0202] In some embodiments, the second network element 1032 is used to perform positioning management on the terminal.

[0203] In some embodiments, the third network element 1033 is, for example, a session management function (SMF).

[0204] In some embodiments, the third network element 1033 is used to update and delete a protocol data unit (PDU) session, etc.

[0205] In some embodiments, the fourth network element 1034 is, for example, a user plane function (UPF).

[0206] In some embodiments, the fourth network element 1034 is used for routing and forwarding user plane data packets.

[0207] In some embodiments, the first network element 1031 , the second network element 1032 , the third network element 1033 , and the fourth network element 1034 may be independent of the core network device 103 .

[0208] In some embodiments, at least one of the first network element 1031 , the second network element 1032 , the third network element 1033 , and the fourth network element 1034 may be part of the core network device 103 .

[0209] In some embodiments, the terminal 101 is connected to each network element of the core network device 103 through the access network device 102.

[0210] It can be understood that the communication system described in the embodiment of the present disclosure is for the purpose of more clearly illustrating the technical solution of the embodiment of the present disclosure, and does not constitute a limitation on the technical solution proposed in the embodiment of the present disclosure. Ordinary technicians in this field can know that with the evolution of the system architecture and the emergence of new business scenarios, the technical solution proposed in the embodiment of the present disclosure is also applicable to similar technical problems.

[0211] The following embodiments of the present disclosure may be applied to the communication system 100 shown in FIG1 , or a portion thereof, but are not limited thereto. The entities shown in FIG1 are illustrative only. The communication system may include all or part of the entities shown in FIG1 , or may include other entities outside of FIG1 . The number and form of the entities are arbitrary, and the entities may be physical or virtual. The connection relationships between the entities are illustrative only. The entities may be connected or disconnected, and the connection may be in any manner, including direct or indirect, wired or wireless.

[0212] The embodiments of the present disclosure can be applied to Long Term Evolution (LTE), LTE-Advanced (LTE-A), LTE-Beyond (LTE-B), SUPER 3G, IMT-Advanced, 4th generation mobile communication system (4G), 5th generation mobile communication system (5G), 5G new radio (NR), future radio access (FRA), new radio access technology (RAT), new radio (NR), new radio access (NX), future generation radio access (FX), Global System for Mobile communications (GSM (registered trademark)), CDMA2000, Ultra Mobile Broadband (UMB), IEEE 802.11 (Wi-Fi (registered trademark)), IEEE 802.16 (WiMAX (registered trademark)), IEEE 802.20, Ultra-WideBand (UWB), Bluetooth (registered trademark), Public Land Mobile Network (PLMN) networks, systems utilizing other communication methods, and next-generation systems based on these. Furthermore, a combination of multiple systems (for example, a combination of LTE or LTE-A with 5G) may also be used.

[0213] FIG2 is an interactive diagram of a method for establishing a user plane connection according to an embodiment of the present disclosure. As shown in FIG2 , an embodiment of the present disclosure relates to a method for establishing a user plane connection, the method comprising:

[0214] Step S2101: Terminal 101 sends a first request message to the first network element 1031 of the core network.

[0215] In some embodiments, the first network element 1031 receives a first request message.

[0216] In some embodiments, the first network element 1031 is an AMF.

[0217] In some embodiments, the first request message is associated with a protocol data unit (PDU) session and is used to initiate user plane positioning.

[0218] In some embodiments, the first request message is used to initiate a user plane connection and initiate a user plane positioning.

[0219] In some embodiments, the name of the first request message is not limited, and it can be, for example, a message to initiate user plane connection and initiate user plane positioning, a first message, etc.

[0220] In some embodiments, the first request message may be a non-access stratum (NAS) message, specifically an uplink non-access stratum transmission message.

[0221] In some embodiments, the first request message includes a PDU Session Establishment Request message.

[0222] In some embodiments, the first request message includes a PDU Session Modification Request message.

[0223] In some embodiments, the first request message includes a PDU session establishment request message, which includes but is not limited to at least one of the following parameters: single network slice selection assistance information (S-NSSAI); data network name (DNN) requested by the terminal; PDU session identifier; request type; old PDU session identifier; N1SM container; port management information container.

[0224] The N1SM container carries a PDU session establishment request.

[0225] In some embodiments, the first request message includes a PDU session modification request message, which includes but is not limited to at least one of the following parameters: PDU session identifier; terminal integrity protection maximum data rate; request type; old PDU session identifier; N1SM container; port management information container.

[0226] The N1SM container carries the PDU session modification request.

[0227] In some embodiments, the first request message includes a PDU session establishment request message or a PDU session modification request message, and the first request message is used to initiate a user plane connection.

[0228] In order to use the first request message to initiate user plane positioning, the request type parameter may be reused, and a new type value may be defined for the request type parameter. The type value is used to indicate a user plane positioning request.

[0229] In one example, the user plane location request is used to request initiation of the user plane location. In some embodiments, the first request message includes a PDU session establishment request message or a PDU session modification request message, and the first request message is used to initiate a user plane connection.

[0230] In order to use the first request message to initiate user plane positioning, a new parameter in the message may be defined, and the value of the parameter indicates the user plane positioning request.

[0231] In an example, the user plane positioning request is used to request to initiate the user plane positioning.

[0232] Exemplarily, the parameter may be the first parameter in the present disclosure, and the present disclosure does not limit the name of the parameter.

[0233] That is, the terminal adds the first parameter to the first request message, and the first parameter is used to indicate the user plane positioning request.

[0234] In some embodiments, the first request message includes a PDU session establishment request message or a PDU session modification request message, and the first request message is used to initiate a user plane connection.

[0235] In order to use the first request message to initiate user plane positioning, the existing user plane positioning information container may be reused and a new information element may be added.

[0236] The user plane positioning information container and the first additional information are used together to indicate a user plane positioning request.

[0237] In an example, the user plane positioning request is used to request to initiate the user plane positioning.

[0238] In an embodiment of the present disclosure, in the user plane positioning information container, the payload container type information element can be set to the user plane positioning information container, and the payload container information element can be set to the user plane positioning information container, and the user plane positioning request can be indicated by the first additional information.

[0239] In some embodiments, the first request message is a PDU session establishment request message or a PDU session modification request message, and the first request message is used to initiate a user plane connection.

[0240] In order to use the first request message to initiate user plane positioning, a new payload container may be added. Exemplarily, the payload container may be called a first payload container or other names, such as a user plane positioning request container, which is not limited in this disclosure.

[0241] In one example, the terminal indicates a user plane positioning request by including the first payload container in a first request message.

[0242] In an example, the user plane positioning request is used to request to initiate the user plane positioning.

[0243] In one example, the terminal includes the first payload container in the first request message and sets the bit value corresponding to the first payload container to an arbitrary value (the value is an invalid value, that is, not used to indicate any valid information), for example, to 1, thereby initiating a user plane positioning request.

[0244] In one example, the terminal includes the first payload container in the first request message and sets the bit value corresponding to the first payload container to a specified value, thereby initiating a user plane positioning request.

[0245] The above description is merely an exemplary description, and solutions in which the terminal initiates user plane connection and user plane positioning through the first request message should all fall within the protection scope of the present disclosure.

[0246] In some embodiments, the names of information, etc. are not limited to the names described in the embodiments, and terms such as "information", "message", "signal", "signaling", "report", "configuration", "indication", "instruction", "command", "channel", "parameter", "domain", "field", "symbol", "symbol", "codeword", "codebook", "codeword", "codepoint", "bit", "data", "program", and "chip" can be used interchangeably.

[0247] In some embodiments, the terms "uplink", "uplink", "physical uplink", etc. can be used interchangeably.

[0248] In some embodiments, the terms "radio", "wireless", "radio access network (RAN)", "access network (AN)", "RAN-based" and the like may be used interchangeably.

[0249] In some embodiments, terms such as "send", "transmit", "report", "download", "transmit", "bidirectional transmission", "send and / or receive" can be used interchangeably.

[0250] In some embodiments, terms such as "certain", "preset", "preset", "setting", "indicated", "a certain", "any", and "first" can be interchangeable. "Specific A", "preset A", "preset A", "setting A", "indicated A", "a certain A", "any A", and "first A" can be interpreted as A pre-specified in a protocol, etc., or as A obtained through setting, configuration, or indication, etc., or as specific A, a certain A, any A, or first A, etc., but not limited to this.

[0251] In step S2102 , the first network element 1031 of the core network selects a second network element 1032 for the terminal based on the first request message.

[0252] In some embodiments, if the first request message is used to indicate initiation of user plane positioning, the first network element 1031 selects the second network element 1032 for user plane positioning for the terminal 101 if it is determined that the terminal 101 has subscribed to the user plane positioning function authorized for the terminal.

[0253] In some embodiments, the second network element 1032 is a LMF.

[0254] Step S2103 , the first network element 1031 sends a third request message to the second network element 1032 .

[0255] In some embodiments, the second network element 1032 receives the third request message.

[0256] In some embodiments, the third request message may be used to request establishment of a user plane connection.

[0257] In some embodiments, the third request message may be a positioning user plane configuration request (Nmmf_Location_UPConfig Request) message.

[0258] Step S2104 : The second network element 1032 sends user plane information to the first network element 1031 .

[0259] In some optional embodiments, the first network element 1031 receives the user plane information.

[0260] In some optional embodiments, the user plane information is relevant information used for the terminal 101 to establish a user plane connection with the second network element 1032.

[0261] In some optional embodiments, the user plane information includes but is not limited to relevant information of the second network element 1032.

[0262] Exemplarily, the relevant information of the second network element 1032 includes but is not limited to at least one of the following: the Internet Protocol (IP) address of the second network element 1032, the fully qualified domain name (FQDN) of the second network element 1032, the identifier of the second network element 1032 (for example, the physical address of the second network element 1032, etc.), the service area of ​​the second network element 1032, etc.

[0263] In some embodiments, the second network element 1032 agrees to use the user plane for positioning, and a user plane connection has not been established between the terminal and the second network element 1032 . The second network element 1032 may send user plane information to the first network element 1031 .

[0264] In some embodiments, the second network element 1032 sends an N1N2 transfer (Namf_Communication_N1N2Message Transfer) message to the first network element 1031, which includes the user plane information.

[0265] In some embodiments, the user plane information is included in a user plane positioning information container.

[0266] Step S2105 , the first network element 1031 sends a first response message to the terminal 101 .

[0267] In some embodiments, step S2105 is an optional execution step.

[0268] In some optional embodiments, the first response message includes the user plane information.

[0269] In some optional embodiments, the first response message may be a downlink non-transport layer transmission message.

[0270] In some optional embodiments, the terminal 101 receives the first response message, but the terminal 101 does not perform any action and needs to wait for the second response message sent by the first network element 1031.

[0271] Step S2106: The first network element 1031 selects a third network element 1033 for the terminal 101 based on the first request message.

[0272] In some embodiments, the third network element 1033 is an SMF.

[0273] In some embodiments, the first network element 1031 first executes the above steps S2102 to S2105, and the first network element 1031 can select the third network element 1033 for the terminal based on the first request message and the selected second network element 1032.

[0274] That is, the first network element 1031 may consider the second network element 1032 previously selected for the terminal 101 when selecting the third network element 1033 .

[0275] In some embodiments, if the first request message is used to initiate user plane positioning, the first network element 1031 stores the association relationship between the S-NSSAI, DNN, PDU session identifier, the third network element 1033 identifier and the PDU session access type.

[0276] Step S2107 : The first network element 1031 sends a second request message related to the PDU session to the third network element 1033 .

[0277] In some embodiments, the third network element 1033 receives the second request message.

[0278] In some embodiments, the second request message may be a PDU session create session management context request message.

[0279] In some embodiments, the second request message may be a PDU session update session management context request message.

[0280] In some embodiments, the first request message includes a PDU session establishment request message, and accordingly, the second request message may be a PDU session create session management context request message, or a PDU session update session management context request message.

[0281] In some embodiments, the first request message includes a PDU session modification request message, and accordingly, the second request message may be a PDU session update SM context request message.

[0282] In some embodiments, the second request message includes the N1SM container in the first request message.

[0283] In some embodiments, if the first network element 1031 does not have an association relationship between the PDU session identifier provided by the terminal 101 and the SMF, the second request message is a PDU session creation session management context request message.

[0284] In some embodiments, if the first network element 1031 has an association relationship between the PDU session identifier provided by the terminal 101 and the SMF, the second request message is a PDU session update session management context request message.

[0285] In some embodiments, the first network element 1031 first executes the above steps S2102 to S2105, and the second request message sent by the first network element 1031 to the third network element 1033 may include relevant information of the second network element 1032.

[0286] In some embodiments, the relevant information of the second network element 1032 includes but is not limited to at least one of the following: the IP address of the second network element 1032, the FQDN of the second network element 1032, the identifier of the second network element 1032 (for example, the physical address of the second network element 1032, etc.), the service area of ​​the second network element 1032, etc.

[0287] In some embodiments, the third network element 1033 stores the relevant information of the second network element 1032 in the second request message.

[0288] Step S2107 - 1 : The third network element 1033 selects a fourth network element 1034 of the core network for the terminal 101 based on the second request message.

[0289] In some embodiments, the fourth network element 1034 is a UPF.

[0290] The fourth network element 1034 may provide user plane functions for the terminal 101. Exemplarily, the fourth network element 1034 is used for routing and forwarding service data of the terminal 101, identifying data and services, and executing actions and policies.

[0291] Exemplarily, the fourth network element 1034 may interact with the third network element 1033 via the N4 interface, and be controlled and managed by the third network element 1033 , and perform service flow processing of the terminal 101 according to the policy issued by the third network element 1033 .

[0292] In some optional embodiments, the third network element 1033 determines PDU session response information.

[0293] In some embodiments, the terminal 101, the first network element 1031, the third network element 1033, and the fourth network element 1034 may perform some steps of the PDU session establishment process, thereby allowing the third network element 1033 to determine the PDU session response information.

[0294] In some embodiments, the terminal 101, the first network element 1031, the third network element 1033, and the fourth network element 1034 may perform some steps of the PDU session modification process, thereby allowing the third network element 1033 to determine the PDU session response information.

[0295] In some embodiments, the PDU session response information includes PDU session establishment acceptance confirmation information.

[0296] In some embodiments, the PDU session response information includes a PDU session modification command (PDU Session Modification Command).

[0297] Step S2108 , the third network element 1033 sends PDU session response information to the first network element 1031 .

[0298] In some embodiments, the first network element 1031 receives PDU session response information.

[0299] Step S2109 : The first network element 1031 sends a second response message or a third response message to the terminal 101 .

[0300] In some embodiments, if the aforementioned step S2105 is executed, the first network element 1031 sends a second response message to the terminal 101.

[0301] In some embodiments, terminal 101 receives a second response message.

[0302] In some embodiments, the second response message includes PDU session response information.

[0303] In some embodiments, if the aforementioned step S2105 is not performed, the first network element 1031 sends a third response message to the terminal 101.

[0304] In some embodiments, terminal 101 receives a third response message.

[0305] In some embodiments, the third response message includes user plane information and PDU session response information.

[0306] Step S2110 , the terminal 101 determines a PDU session for user plane positioning.

[0307] In some embodiments, the terminal 101 , the first network element 1031 , the third network element 1033 , and the fourth network element 1034 may perform the remaining steps of the PDU session establishment process, thereby allowing the terminal 101 to determine the PDU session for user plane positioning.

[0308] In some embodiments, the above steps S2102 to S2105 may be performed first, and then the above steps S2106 to S2110 may be performed.

[0309] Accordingly, the first network element 1031 selects the third network element 1033 for the terminal 101 based on the first request message and the selected second network element 1032. The second request message sent by the first network element 1031 to the third network element 1033 includes relevant information of the second network element 1032.

[0310] In some embodiments, the relevant information of the second network element 1032 includes but is not limited to at least one of the following: the IP address of the second network element 1032, the FQDN of the second network element 1032, the identifier of the second network element 1032 (for example, the physical address of the second network element 1032, etc.), the service area of ​​the second network element 1032, etc.

[0311] In some embodiments, the above steps S2106 to S2110 may be performed first, and then the above steps S2102 to S2105 may be performed.

[0312] Accordingly, the first network element 1031 selects the second network element 1032 for the terminal 101 based on the first request message and the selected third network element 1033. The third request message sent by the first network element 1031 to the second network element 1032 includes relevant information of the third network element 1033.

[0313] In some embodiments, the relevant information of the third network element 1033 includes but is not limited to at least one of the following: the IP address of the third network element 1033, the FQDN of the third network element 1033, the identifier of the third network element 1033 (for example, the physical address of the third network element 1033, etc.), the service area of ​​the third network element 1033, etc.

[0314] Step S2111: The terminal 101 establishes a user plane connection with the second network element 1032 of the core network through the PDU session based on the user plane information.

[0315] In some embodiments, the user plane connection is used for user plane positioning.

[0316] Step S2112 : The second network element 1032 sends a response message to the first network element 1031 . The response message is used to indicate that a user plane connection has been established between the terminal 101 and the second network element 1032 .

[0317] In some embodiments, the first network element 1031 receives the response message.

[0318] In some embodiments, the response message may be a positioning user plane configuration response (Nmmf_Location_UPConfig Response) message.

[0319] Step S2113: The first network element 1031 stores the user plane positioning connection context.

[0320] In some embodiments, the first network element 1031 stores the user plane positioning connection context as a part of the terminal context.

[0321] Step S2114 : Transmitting a positioning message between the terminal 101 and the second network element 1032 .

[0322] In some embodiments, the second network element 1032 receives a positioning request message from the first network element 1031 .

[0323] In some embodiments, the positioning request message is used by the second network element 1032 to determine whether to perform user plane positioning using a user plane connection, or when the terminal 101 determines whether to perform user plane positioning using a user plane connection, the terminal 101 and the second network element 1032 transmit a positioning request message, such as an LTE Positioning Protocol (LPP) message, which is used to perform user plane positioning, terminal service positioning, and transmission of auxiliary data, etc.

[0324] In some embodiments, a supplementary service event report (Supplementary Services Event Report) message from the terminal 101 may be transmitted to the second network element 1032 via the established user plane connection.

[0325] In some embodiments, the above process is also applicable to establishing a user plane connection with other 5G network functions outside the second network element 1032, such as sensing functions. The user plane positioning information can be sensing information, and the user plane position establishment can be user plane sensing establishment. This disclosure does not limit this.

[0326] In some embodiments, the method for establishing a user plane connection involved in the embodiments of the present disclosure may include at least one of steps S2101 to S2114. For example, step S2101 may be implemented as an independent embodiment, step S2109 may be implemented as an independent embodiment, steps S2105+S2109 may be implemented as an independent embodiment, steps S2102 to S2105 may be implemented as an independent embodiment, steps S2106 to S2110 may be implemented as an independent embodiment, and steps S2102 to S2110 may be implemented as an independent embodiment, but are not limited thereto.

[0327] In some embodiments, steps S2102 to S2105 and steps S2106 to S2110 may be executed in an interchanged order or simultaneously.

[0328] In some embodiments, steps S2102 to S2114 are optional, and one or more of these steps may be omitted or replaced in different embodiments.

[0329] In some embodiments, steps S2101 to S2114 are optional, and one or more of these steps may be omitted or replaced in different embodiments.

[0330] In the above embodiment, the user plane connection and user plane positioning can be initiated simultaneously through the first request message related to the PDU session, which saves signaling resources and improves the availability and reliability of user plane positioning.

[0331] FIG3 is a flow chart of a method for establishing a user plane connection according to an embodiment of the present disclosure. As shown in FIG3 , an embodiment of the present disclosure relates to a method for establishing a user plane connection, which can be performed by terminal 101, and includes:

[0332] Step S3101: Send a first request message.

[0333] In some embodiments, the terminal 101 sends the first request message to the first network element 1031 of the core network.

[0334] In some embodiments, the first request message is related to a protocol data unit (PDU) session, and the first request message is further used to initiate user plane positioning.

[0335] Optionally, the first network element 1031 receives the first request message.

[0336] Optionally, the first network element 1031 is an AMF.

[0337] In some embodiments, the first request message is an uplink non-access stratum transmission message.

[0338] In some embodiments, the first request message comprises a PDU session establishment request message.

[0339] In some embodiments, the first request message comprises a PDU session modification request message.

[0340] In some embodiments, the first request message includes a PDU session establishment request message, which includes but is not limited to at least one of the following parameters: single network slice selection assistance information; data network name requested by the terminal; PDU session identifier; request type; old PDU session identifier; N1SM container; port management information container.

[0341] The N1SM container carries a PDU session establishment request.

[0342] In some embodiments, the first request message includes a PDU session modification request message, which includes but is not limited to at least one of the following parameters: PDU session identifier; terminal integrity protection maximum data rate; request type; old PDU session identifier; N1SM container; port management information container.

[0343] The N1SM container carries the PDU session modification request.

[0344] In some embodiments, the first request message includes a PDU session establishment request message or a PDU session modification request message, and the first request message is used to initiate a user plane connection.

[0345] In order to use the first request message to initiate user plane positioning, the request type parameter may be reused, and a new type value may be defined for the request type parameter. The type value is used to indicate a user plane positioning request.

[0346] In an example, the user plane positioning request is used to request to initiate the user plane positioning.

[0347] In some embodiments, the first request message includes a PDU session establishment request message or a PDU session modification request message, and the first request message is used to initiate a user plane connection.

[0348] In order to use the first request message to initiate user plane positioning, a new parameter in a message may be defined, and the parameter is used to indicate the user plane positioning request.

[0349] Exemplarily, the parameter may be the first parameter in the present disclosure, and the present disclosure does not limit the name of the parameter.

[0350] That is, the terminal adds a first parameter to the first request message, and the first parameter is used to indicate a user plane positioning request. In one example, the user plane positioning request is used to request to initiate the user plane positioning.

[0351] In some embodiments, the first request message includes a PDU session establishment request message or a PDU session modification request message, and the first request message is used to initiate a user plane connection.

[0352] In order to use the first request message to initiate user plane positioning, the existing user plane positioning information container may be reused and a new information element may be added.

[0353] The user plane positioning information container and the first additional information are used together to indicate a user plane positioning request. In an example, the user plane positioning request is used to request to initiate the user plane positioning.

[0354] In an embodiment of the present disclosure, in the user plane positioning information container, the payload container type information element can be set to the user plane positioning information container, and the payload container information element can be set to the user plane positioning information payload, and the user plane positioning request can be indicated by the first additional information.

[0355] In some embodiments, the first request message is a PDU session establishment request message or a PDU session modification request message, and the first request message is used to initiate a user plane connection.

[0356] In order to use the first request message to initiate user plane positioning, a new payload container may be added. Exemplarily, the payload container may be called a first payload container or other names, such as a user plane positioning request container, which is not limited in this disclosure.

[0357] In one example, the terminal indicates a user plane positioning request by including the first payload container in a first request message.

[0358] In an example, the user plane positioning request is used to request to initiate the user plane positioning.

[0359] In one example, the terminal includes the first payload container in the first request message and sets the bit value corresponding to the first payload container to an arbitrary value (the value is an invalid value, that is, not used to indicate any valid information), for example, to 1, thereby indicating a user plane positioning request.

[0360] In an example, the terminal includes the first payload container in the first request message, and sets the bit value corresponding to the first payload container to a specified value, thereby indicating a user plane positioning request.

[0361] The above description is merely an exemplary description, and solutions in which the terminal initiates user plane connection and user plane positioning through the first request message should all fall within the protection scope of the present disclosure.

[0362] The optional implementation of step S3101 can refer to the optional implementation of step S2101 in Figure 2 and other related parts in the embodiment involved in Figure 2, which will not be repeated here.

[0363] Step S3102, obtain a response message.

[0364] In some embodiments, the terminal 101 receives a response message sent by the first network element of the core network, but is not limited thereto and may also receive a response message sent by other entities.

[0365] In some embodiments, terminal 101 obtains a response message specified by the protocol.

[0366] In some embodiments, terminal 101 obtains a response message from upper layer(s).

[0367] In some embodiments, terminal 101 performs processing to obtain a response message.

[0368] In some embodiments, step S3102 is omitted, and the terminal 101 autonomously implements the function indicated by the response message, or the above function is default or acquiescent.

[0369] The optional implementation of step S3102 can refer to the optional implementation of steps S2105 and S2109 in Figure 2, and other related parts in the embodiment involved in Figure 2, which will not be repeated here.

[0370] Step S3103: Determine the PDU session.

[0371] In some embodiments, the PDU session is used for user plane positioning.

[0372] The optional implementation of step S3103 can refer to the optional implementation of step S2110 in Figure 2 and other related parts in the embodiment involved in Figure 2, which will not be repeated here.

[0373] Step S3104: Establish a user plane connection.

[0374] The optional implementation of step S3104 can refer to the optional implementation of step S2111 in Figure 2 and other related parts in the embodiment involved in Figure 2, which will not be repeated here.

[0375] The communication method involved in the embodiments of the present disclosure may include at least one of steps S3101 to S3104. For example, step S3101 may be implemented as an independent embodiment, step S3102 may be implemented as an independent embodiment, steps S3103 and S3104 may be implemented as independent embodiments, and steps S3101 to S3104 may be implemented as independent embodiments, but are not limited thereto.

[0376] In some embodiments, steps S3102 to S3104 are optional, and one or more of these steps may be omitted or replaced in different embodiments.

[0377] In some embodiments, steps S3101 and S3103 to S3104 are optional, and one or more of these steps may be omitted or replaced in different embodiments.

[0378] In the above embodiment, the terminal can simultaneously initiate user plane connection and user plane positioning through the first request message related to the PDU session, which saves signaling resources and improves the availability and reliability of user plane positioning.

[0379] FIG4A is a flow chart of a method for establishing a user plane connection according to an embodiment of the present disclosure. As shown in FIG4A , the embodiment of the present disclosure relates to a method for establishing a user plane connection, which can be performed by a first network element 1031 of a core network. The method includes:

[0380] Step S4101: Obtain a first request message.

[0381] In some embodiments, the first network element 1031 of the core network receives a first request message sent by the terminal 101, but is not limited to this. It can also receive a first request message sent by other entities, such as a first request message sent by the terminal 101 through the access network device 102.

[0382] In some embodiments, the first network element 1031 obtains a first request message specified by the protocol.

[0383] In some embodiments, the first network element 1031 performs processing to obtain a first request message.

[0384] In some embodiments, step S4101 is omitted, and the first network element 1031 autonomously implements the function indicated by the response message, or the above function is default or by default.

[0385] The optional implementation of step S4101 can refer to the optional implementation of step S2101 in Figure 2 and other related parts in the embodiment involved in Figure 2, which will not be repeated here.

[0386] Step S4102, sending a response message.

[0387] In some embodiments, the first network element 1031 returns a response message to the terminal.

[0388] In some embodiments, optional implementations of step S4102 can refer to the optional implementations of steps S2105 and S2109 in FIG2 , and other related parts in the embodiments involved in FIG2 , which will not be repeated here.

[0389] In some embodiments, the first network element 1031 selects the second network element 1032 for the terminal.

[0390] The optional implementation of this step can refer to the optional implementation of step S2102 in Figure 2 and other related parts in the embodiment involved in Figure 2, which will not be repeated here.

[0391] In some embodiments, the first network element 1031 sends a third request message to the selected second network element 1032 .

[0392] The optional implementation of this step can refer to the optional implementation of step S2103 in Figure 2 and other related parts in the embodiment involved in Figure 2, which will not be repeated here.

[0393] In some embodiments, the first network element 1031 receives user plane information sent by the second network element 1032 .

[0394] Optional implementations of this step can be found in the optional implementations of step S2104 in Figure 2 and other related parts in the embodiment involved in Figure 2, which will not be described in detail here. In some embodiments, the first network element 1031 selects the third network element 1033 for the terminal.

[0395] The optional implementation of this step can refer to the optional implementation of step S2106 in Figure 2 and other related parts in the embodiment involved in Figure 2, which will not be repeated here.

[0396] In some embodiments, the first network element 1031 sends a second request message to the selected third network element 1033 .

[0397] The optional implementation of this step can refer to the optional implementation of step S2107 in Figure 2 and other related parts in the embodiment involved in Figure 2, which will not be repeated here.

[0398] In some embodiments, the first network element 1031 receives PDU session response information sent by the third network element 1033 .

[0399] The optional implementation of this step can refer to the optional implementation of step S2108 in Figure 2 and other related parts in the embodiment involved in Figure 2, which will not be repeated here.

[0400] In some optional embodiments, the first network element 1031 receives a response message sent by the second network element 1032. Optional implementations of this step can be found in the optional implementations of step S2112 in FIG2 and other related parts in the embodiment involved in FIG2 , which will not be described in detail here.

[0401] In some optional embodiments, the first network element 1031 stores the user plane positioning connection context.

[0402] The optional implementation of this step can refer to the optional implementation of step S2113 in Figure 2 and other related parts in the embodiment involved in Figure 2, which will not be repeated here.

[0403] In some optional embodiments, the first network element 1031 sends a positioning request message to the second network element 1032 .

[0404] The optional implementation of this step can refer to the optional implementation of step S2114 in Figure 2 and other related parts in the embodiment involved in Figure 2, which will not be repeated here.

[0405] The communication method involved in the embodiment of the present disclosure may include at least one of steps S4101 to S4102. For example, step S4101 may be implemented as an independent embodiment, and step S4102 may be implemented as an independent embodiment, but the present invention is not limited thereto.

[0406] In some embodiments, step S4102 is optional, and one or more of these steps may be omitted or replaced in different embodiments.

[0407] In some embodiments, step S4101 is optional, and one or more of these steps may be omitted or replaced in different embodiments.

[0408] In the above embodiment, after receiving a first request message related to a PDU session sent by a terminal, the first network element of the core network can send a response message including user plane information to the terminal. This response message can be used by the terminal to determine the PDU session for user plane positioning, and based on the user plane information included in the response message, establish a user plane connection with the second network element of the core network via the PDU session. The user plane connection is used for user plane positioning. This achieves the purpose of simultaneously initiating a user plane connection and user plane positioning via the first request message related to the PDU session, saving signaling resources and improving the availability and reliability of user plane positioning.

[0409] FIG4B is a flow chart of a method for establishing a user plane connection according to an embodiment of the present disclosure. As shown in FIG4B , the embodiment of the present disclosure relates to a method for establishing a user plane connection, which can be performed by a third network element 1033 of the core network. The method includes:

[0410] Step S4201: Obtain a second request message.

[0411] In some embodiments, the third network element 1033 of the core network receives the second request message sent by the first network element 1031, but is not limited thereto and may also receive the second request message sent by other entities.

[0412] In some embodiments, the third network element 1033 obtains a second request message specified by the protocol.

[0413] In some embodiments, the third network element 1033 performs processing to obtain the second request message.

[0414] In some embodiments, step S4201 is omitted, and the third network element 1033 autonomously implements the function indicated by the response message, or the above function is default or by default.

[0415] The optional implementation of step S4201 can refer to the optional implementation of step S2107 in Figure 2 and other related parts in the embodiment involved in Figure 2, which will not be repeated here.

[0416] In some embodiments, the third network element 1033 stores the relevant information of the second network element 1032 in the second request message.

[0417] In some embodiments, the relevant information of the second network element 1032 includes but is not limited to at least one of the following: the IP address of the second network element 1032, the FQDN of the second network element 1032, the identifier of the second network element 1032 (for example, the physical address of the second network element 1032, etc.), the service area of ​​the second network element 1032, etc.

[0418] Step S4202, select the fourth network element 1034.

[0419] In some optional embodiments, the third network element selects the fourth network element 1034 for the terminal based on the second request message.

[0420] In some optional embodiments, the fourth network element 1034 is used to implement user plane functions.

[0421] In some optional embodiments, the fourth network element 1034 is a UPF.

[0422] The optional implementation of step S4202 can be found in other related parts of the embodiment involved in Figure 2, and will not be repeated here.

[0423] The communication method involved in the embodiment of the present disclosure may include at least one of steps S5101 to S5102. For example, step S4201 may be implemented as an independent embodiment, and step S5102 may be implemented as an independent embodiment, but the present invention is not limited thereto.

[0424] In some embodiments, step S4202 is optional, and one or more of these steps may be omitted or replaced in different embodiments.

[0425] In some embodiments, step S4201 is optional, and one or more of these steps may be omitted or replaced in different embodiments.

[0426] In some embodiments, step S4201 and step S4202 are optional, and one or more of these steps may be omitted or replaced in different embodiments.

[0427] In the above embodiment, after receiving the second request message related to the PDU session sent by the second network element, the third network element of the core network can retain the second request message and, based on the second request message, select a fourth network element of the core network for the terminal, the fourth network element being configured to implement user plane functions. This improves the reliability of establishing a user plane connection.

[0428] Figure 5 is an interactive diagram of a method for establishing a user plane connection according to an embodiment of the present disclosure. As shown in Figure 5, an embodiment of the present disclosure relates to a method for establishing a user plane connection, the method comprising:

[0429] Step S5101: The first network element 1031 obtains a first request message.

[0430] The optional implementation of step S5101 can refer to the optional implementation of step S2101 in Figure 2 and other related parts in the embodiment involved in Figure 2, which will not be repeated here.

[0431] Step S5102 , the first network element 1031 selects the second network element 1032 .

[0432] The optional implementation of step S5102 can refer to the optional implementation of step S2102 in Figure 2 and other related parts in the embodiment involved in Figure 2, which will not be repeated here.

[0433] Step S5103 , the first network element 1031 sends a third request message to the second network element 1032 .

[0434] The optional implementation of step S5103 can refer to the optional implementation of step S2103 in Figure 2 and other related parts in the embodiment involved in Figure 2, which will not be repeated here.

[0435] Step S5104 : The second network element 1032 sends user plane information to the first network element 1031 .

[0436] The optional implementation of step S5104 can refer to the optional implementation of step S2104 in Figure 2 and other related parts in the embodiment involved in Figure 2, which will not be repeated here.

[0437] Step S5105 , the first network element 1031 selects the third network element 1033 .

[0438] The optional implementation of step S5105 can refer to the optional implementation of step S2106 in Figure 2 and other related parts in the embodiment involved in Figure 2, which will not be repeated here.

[0439] Step S5106 , the first network element 1031 sends a second request message related to the PDU session to the third network element 1033 .

[0440] The optional implementation of step S5106 can refer to the optional implementation of step S2107 in Figure 2 and other related parts in the embodiment involved in Figure 2, which will not be repeated here.

[0441] Step S5107 , the third network element 1033 selects the fourth network element 1034 .

[0442] Step S5108 , the third network element 1033 sends PDU session response information to the first network element 1031 .

[0443] The optional implementation of step S5108 can refer to the optional implementation of step S2108 in Figure 2 and other related parts in the embodiment involved in Figure 2, which will not be repeated here.

[0444] In the above embodiment, the various network elements of the core network can interact through the above process to determine the PDU session response information and user plane information, and return them to the terminal, thereby achieving the purpose of determining the PDU session for establishing user plane positioning and the user plane information for establishing a user plane connection for the terminal based on the first request message, which is simple to implement and has high availability.

[0445] FIG6A is a flow chart of a method for establishing a user plane connection according to an embodiment of the present disclosure. As shown in FIG6A , an embodiment of the present disclosure relates to a method for establishing a user plane connection, the method comprising:

[0446] Step S6101: Terminal 101 initiates a user plane connection.

[0447] In some embodiments, if the terminal 101 decides to prepare a user plane connection for an upcoming positioning request, the terminal 101 may send a user plane establishment request to the first network element 1031, such as the AMF, via an uplink non-access layer transmission message.

[0448] In step S6102 , the first network element 1031 selects the second network element 1032 .

[0449] In some embodiments, when determining that the terminal 101 has subscribed to a user plane positioning function authorized for the terminal, the first network element 1031 selects a second network element 1032 for user plane positioning for the terminal 101 .

[0450] Step S6103 : The first network element 1031 sends a positioning user plane configuration request message to the second network element 1032 .

[0451] In some embodiments, the positioning user plane configuration request message is used to request establishment of a user plane connection for location services.

[0452] Step S6104 : The second network element 1032 sends user plane information to the first network element 1031 .

[0453] In some embodiments, if the second network element 1032 agrees to use the user plane for positioning and a user plane connection has not been established between the terminal and the second network element 1032 , the second network element 1032 may send user plane information to the first network element 1031 .

[0454] In some embodiments, the user plane information includes user plane location information and security information of the second network element.

[0455] Among them, the user plane positioning information of the second network element includes but is not limited to: the IP address of the second network element 1032, the FQDN of the second network element 1032, the identifier of the second network element 1032 (for example, the physical address of the second network element 1032, etc.), the service area of ​​the second network element 1032, etc.

[0456] Step S6105 : The first network element 1031 sends user plane information to the terminal 101 .

[0457] In some embodiments, the first network element 1031 sends a downlink NAS transmission message to the terminal 101, which includes user plane information.

[0458] Step S6106 : The terminal 101 establishes a user plane connection with the second network element 1032 .

[0459] Step S6107 , the second network element 1032 sends a response message to the first network element 1031 .

[0460] In some embodiments, the response message is used to inform the first network element 1031 that a user plane connection has been established.

[0461] Step S6108: The first network element 1031 stores the user plane positioning connection context.

[0462] Step S6109 : Transmitting a positioning message between the terminal 101 and the second network element 1032 .

[0463] In the above embodiment, a user plane positioning request may be initiated to the first network element 1031 via an uplink non-access layer transmission message, which is simple to implement and has high availability.

[0464] Considering that in the embodiment of Figure 6A, a user plane positioning request is initiated to the first network element 1031 through an uplink non-access layer transmission message, the user plane positioning process will be opaque to the first network element 1031. In addition, there may be a lack of a PDU session for user plane positioning. The present disclosure provides another method for establishing a user plane connection.

[0465] FIG6B is a flow chart of a method for establishing a user plane connection according to an embodiment of the present disclosure. As shown in FIG6B , an embodiment of the present disclosure relates to a method for establishing a user plane connection, the method comprising:

[0466] In some embodiments, the terminal 101 sends a user plane positioning request to the first network element 1031, indicating that the terminal 101 decides to use the user plane connection for the upcoming positioning request. The uplink positioning initiation may be carried by an uplink non-access stratum transmission message.

[0467] In some embodiments, the following is an example of using an uplink non-access layer transport message to carry user plane positioning initiation, and the N1SM container is also included in the PDU session establishment request message and the PDU session modification request message included in the SMF. If the PDU session can be used for user plane positioning, the N1SM container is not required. If the terminal 101 does not have a PDU session, a PDU session establishment request (case 1a) can be used. If there is an existing PDU session but there is no PDU session suitable for using plane positioning, a PDU session establishment request message or a PDU session modification request (case 1b) message can be used.

[0468] In step S6201a, the terminal 101 sends a PDU session establishment request message to the first network element 1031.

[0469] From the terminal 101 to the first network element 1031: uplink non-access layer transmission message (S-NSSAI, DNN requested by UE, PDU session ID, request type, old PDU session ID, N1SM container (PDU session establishment request), [port management information container]).

[0470] Case a: New type value of an existing parameter: The new type of "request type" can represent "user plane positioning initial request".

[0471] Case b: A new parameter in the NAS message, such as the terminal 101 request indication or the user plane positioning indication, may have a specific value that indicates the start of user plane positioning.

[0472] Case c: New information of an existing payload container, such as a user plane positioning information container, sets the payload container type information element to "user plane positioning information container"; sets the payload container information element to the user plane positioning information payload; and sets the additional information information element to "user plane information initiation".

[0473] Case d: New payload container value, for example, user plane location information initiation container, sets the payload container type information element to "user plane location information initiation container"; sets the payload container IE to user plane location information initiation payload.

[0474] If no existing PDU session exists, Terminal 101 also needs to trigger PDU session establishment in an uplink non-access stratum transmission message (N1SM container (PDU Session Establishment Request, [Port Management Information Container])) so that First Network Element 1031 can select Second Network Element 1032 for user plane positioning and Third Network Element 1033 for PDU session establishment. To establish a new PDU session, Terminal 101 generates a new PDU Session ID.

[0475] Step S6201b: The terminal 101 sends a PDU session modification request message to the first network element 1031.

[0476] In S6201b, from the terminal 101 to the first network element 1031: uplink non-access layer transmission message (PDU session ID, UE integrity protection maximum data rate, [port management information container], request type, N1SM container (PDU session modification request)).

[0477] To indicate "user plane positioning enabled", the above cases a, b, c and d may be used.

[0478] If Terminal 101 decides to modify an existing PDU Session, Terminal 101 also needs to trigger a PDU Session Modification in an uplink non-access stratum transmission message. The N1SM container (PDU Session Modification Request) should be included in the uplink non-access stratum transmission message so that First Network Element 1031 can select Second Network Element 1032 for user plane location and forward the container to Third Network Element 1033.

[0479] Step S6202 : If user plane positioning initiation is indicated in the uplink non-access layer transmission message, and the terminal is authorized to use user plane positioning based on terminal subscription, the first network element 1031 selects the second network element 1032 capable of establishing a user plane session for positioning with the terminal 101 .

[0480] Step S6203 : The first network element 1031 sends a positioning user plane configuration request message to the second network element 1032 to request establishment of a user plane connection for location service.

[0481] In step S6204, if the second network element 1032 accepts user plane positioning and no user plane connection is established between the terminal 101 and the second network element 1032, the second network element 1032 sends user plane information to the first network element 1031 to instruct the terminal to accept and use the user plane for positioning. The user plane information includes the user plane positioning address of the second network element 1032 and security-related information.

[0482] Step S6205 (optional), when the first network element 1031 receives the user plane information (contained in the "user plane positioning information container") from the second network element 1032 in step S6204, the first network element 1031 can forward it directly to the terminal 101 through the downlink non-access layer transmission message, and the terminal 101 needs to wait for a response from the third network element 1033 (this means that the terminal 101 will not be triggered to start the subsequent step S6211), and send the user plane positioning information and PDU session establishment acceptance information or PDU session modification command together (step S6205 can be merged into step S6209).

[0483] If step S6205 is executed and step S6209 is also executed, the terminal needs to wait for the response of the third network element 1033 in step S6209.

[0484] In step S6206, the first network element 1031 selects the third network element 1033. The first network element 1031 may consider the information of the user plane location indication received in step S6201 and the second network element 1032 selected in step S6202.

[0485] If the request type indicates "user plane positioning initial request", the first network element 1031 stores the association of the S-NSSAI, DNN, PDU session ID, the third network element 1033 identifier, and the access type of the PDU session.

[0486] In step S6207 , the first network element 1031 sends a PDU session create session management context request message or a PDU session update session management context request message to the third network element 1033 , including the N1SM container received in step S6201 .

[0487] If the first network element 1031 does not have an association with the third network element 1033 for the PDU session identifier provided by the terminal, the first network element 1031 invokes a PDU session create session management context request. If the first network element 1031 already has an association with the third network element 1033 for the PDU session identifier provided by the terminal, the first network element 1031 invokes a PDU session update session management context request.

[0488] In step S6208 , the terminal 101 , the first network element 1031 , the third network element 1033 , and the fourth network element 1034 execute part of the steps of the PDU session establishment process or part of the steps of the PDU session modification process.

[0489] In some embodiments, the terminal 101, the first network element 1031, the third network element 1033, and the fourth network element 1034 may perform a portion of the PDU session establishment steps, which may be used to determine PDU session response information for the terminal 101. Specifically, the PDU session establishment steps are performed, and when the PDU session acceptance information is determined, the PDU session establishment process is suspended. The subsequent step S6209 is then executed.

[0490] In some embodiments, the terminal 101, the first network element 1031, the third network element 1033, and the fourth network element 1034 may perform some steps of PDU session modification, which may be used to determine PDU session response information for the terminal 101. Specifically, the steps of PDU session modification are performed. When the PDU session modification command is determined, the PDU session modification process is suspended, and the subsequent step S6209 is continued.

[0491] In step S6209, if step S6205 is not executed, the first network element 1031 is waiting for a response from the third network element 1033, and the user plane location information in the user plane location information container and the PDU session establishment acceptance information or PDU session modification command in the N1SM container are both included in the downlink non-access layer transmission message and sent to the terminal 101. The terminal 101 does not need to wait and can execute the remaining procedures.

[0492] In step S6210, the terminal 101, the first network element 1031, the third network element 1033, and the fourth network element 1034 perform the remaining procedures of the PDU session establishment or PDU session modification procedure. After this step, the terminal 101 has an appropriate PDU session for user plane positioning.

[0493] In some embodiments, in step S2108, the terminal 101, the first network element 1031, the third network element 1033 and the fourth network element 1034 perform some steps of establishing the PDU session. In this step, the subsequent steps of establishing the PDU session can be continued to determine the PDU session for the terminal 101.

[0494] In some embodiments, in step S2108, the terminal 101, the first network element 1031, the third network element 1033 and the fourth network element 1034 perform some steps of PDU session modification. In this step, the subsequent steps of PDU session modification can be continued to determine the PDU session for the terminal 101.

[0495] Note: The order of steps S6202-S6205 and steps S6206-S6210 can be changed.

[0496] Step S6211: Using the PDU session, the terminal 101 establishes a user plane connection with the second network element 1032.

[0497] Step S6212 : The second network element 1032 responds to the first network element 1031 that the user plane connection between the terminal 101 and the second network element 1032 has been established.

[0498] Step S6213: The first network element 1031 stores the user plane connection context as part of the terminal context.

[0499] Step S6214: After establishing the user plane connection, if the second network element 1032 determines to use the user plane connection for positioning after receiving the positioning request from the first network element 1031, or if the terminal 101 determines to use the user plane connection for positioning, LTE positioning protocol messages are transmitted between the terminal 101 and the second network element 1032 for terminal-based positioning, terminal-assisted positioning, and delivery of assistance data. Additional service event report messages from the terminal may also be transmitted to the second network element 1032 via the established user plane connection.

[0500] In the embodiment of the present disclosure, user plane connection and user plane positioning can be initiated simultaneously through the first request message related to the PDU session, which saves signaling resources and improves the availability and reliability of user plane positioning.

[0501] The embodiments of the present disclosure further provide an apparatus for implementing any of the above methods. For example, an apparatus is provided, comprising units or modules for implementing each step performed by a terminal in any of the above methods. For another example, another apparatus is provided, comprising units or modules for implementing each step performed by a network device (e.g., a core network function node, a core network device, etc.) in any of the above methods.

[0502] It should be understood that the division of the various units or modules in the above device is merely a division of logical functions. In actual implementation, they may be fully or partially integrated into a physical entity, or they may be physically separated. In addition, the units or modules in the device may be implemented in the form of a processor calling software: for example, the device includes a processor, the processor is connected to a memory, and the memory stores instructions. The processor calls the instructions stored in the memory to implement any of the above methods or implement the functions of the various units or modules of the above device, wherein the processor is, for example, a general-purpose processor, such as a central processing unit (CPU) or a microprocessor, and the memory is a memory within the device or a memory outside the device. Alternatively, the units or modules in the device can be implemented in the form of hardware circuits, and the functions of some or all of the units or modules can be realized by designing the hardware circuits. The above-mentioned hardware circuits can be understood as one or more processors; for example, in one implementation, the above-mentioned hardware circuit is an application-specific integrated circuit (ASIC), and the functions of some or all of the above units or modules are realized by designing the logical relationship of the components in the circuit; for example, in another implementation, the above-mentioned hardware circuit can be realized by a programmable logic device (PLD). Taking a field programmable gate array (FPGA) as an example, it can include a large number of logic gate circuits, and the connection relationship between the logic gate circuits is configured by a configuration file, thereby realizing the functions of some or all of the above units or modules. All units or modules of the above devices can be implemented in the form of software called by the processor, or in the form of hardware circuits, or in part by software called by the processor, and the rest by hardware circuits.

[0503] In the embodiments of the present disclosure, the processor is a circuit with signal processing capabilities. In one implementation, the processor can be a circuit with instruction reading and execution capabilities, such as a central processing unit (CPU), a microprocessor, a graphics processing unit (GPU) (which can be understood as a microprocessor), or a digital signal processor (DSP). In another implementation, the processor can implement certain functions through the logical relationship of the hardware circuit. The logical relationship of the above-mentioned hardware circuit is fixed or reconfigurable. For example, the processor is a hardware circuit implemented by an application-specific integrated circuit (ASIC) or a programmable logic device (PLD), such as an FPGA. In a reconfigurable hardware circuit, the process of the processor loading a configuration document and implementing the hardware circuit configuration can be understood as the process of the processor loading instructions to implement the functions of some or all of the above units or modules. In addition, it can also be a hardware circuit designed for artificial intelligence, which can be understood as an ASIC, such as a neural network processing unit (NPU), a tensor processing unit (TPU), a deep learning processing unit (DPU), etc.

[0504] FIG7A is a schematic diagram of the structure of a terminal according to an embodiment of the present disclosure. As shown in FIG7A , a terminal 7100 may include at least one of a transceiver module 7101 and a processing module 7102 .

[0505] In some embodiments, the transceiver module 7101 is used to send a first request message related to a protocol data unit (PDU) session to a first network element of a core network, where the first request message is also used to initiate user plane positioning.

[0506] In some embodiments, the processing module 7102 is configured to receive a response message sent by the first network element and determine a PDU session for user plane positioning, wherein the response message includes user plane information.

[0507] In some embodiments, the processing module 7102 is further configured to establish a user plane connection with a second network element of the core network through the PDU session based on the user plane information, where the user plane connection is used for user plane positioning.

[0508] Optionally, the above-mentioned transceiver module 7101 is used to execute at least one of the communication steps such as sending and / or receiving performed by the terminal 101 in any of the above methods (for example, step S2101, step S2105, step S2109, but not limited to these), which will not be repeated here.

[0509] Optionally, the processing module 7102 is used to execute at least one of the other steps (such as step S2110, step S2111, step S2114, but not limited thereto) performed by the terminal 101 in any of the above methods, which will not be repeated here.

[0510] FIG7B is a schematic diagram of the structure of a first network element proposed in an embodiment of the present disclosure. As shown in FIG7B , the first network element 7200 may include: a transceiver module 7201 .

[0511] In some embodiments, the transceiver module 7201 is used to receive a first request message related to a protocol data unit (PDU) session sent by a terminal, where the first request message is also used to initiate user plane positioning.

[0512] In some embodiments, the above-mentioned transceiver module 7201 is also configured to send a response message including user plane information to the terminal, so that the terminal determines the PDU session for user plane positioning based on the response message, and then establishes a user plane connection with the second network element of the core network through the PDU session based on the user plane information, and the user plane connection is used for user plane positioning.

[0513] Optionally, the above-mentioned transceiver module 7201 is used to execute at least one of the communication steps such as sending and / or receiving performed by the first network element 1031 in any of the above methods (for example, step S2101, step S2103, step S2104, step S2105, step S2107, step S2109, step S2112, but not limited to these), which are not repeated here.

[0514] Optionally, the first network element 7200 may include a processing module 7202 (not shown in Figure 7B), and the processing module 7202 is used to execute at least one of the other steps (for example, step S2110, step S2112, step S2111, step S2113, step S2114, S2116, step S2118, but not limited to these) performed by the first network element 1031 in any of the above methods, which are not repeated here.

[0515] FIG7C is a schematic diagram of the structure of a second network element according to an embodiment of the present disclosure. As shown in FIG7C , the second network element 7300 may include at least one of a transceiver module 7301 and a processing module 7302 .

[0516] Optionally, the above-mentioned transceiver module 7301 is used to execute at least one of the communication steps such as sending and / or receiving performed by the second network element 1032 in any of the above methods (for example, step S2103, step S2104, step S2112, step S2114, but not limited to these), which will not be repeated here.

[0517] Optionally, the above-mentioned processing module 7302 is used to execute at least one of the other steps (such as step S2111, but not limited to this) performed by the second network element 1032 in any of the above methods, which will not be repeated here.

[0518] FIG7D is a schematic diagram of the structure of a third network element proposed in an embodiment of the present disclosure. As shown in FIG7D , the third network element 7400 may include: at least one of a transceiver module 7401 and a processing module 7402 .

[0519] In some embodiments, the transceiver module 7401 is configured to receive a second request message related to a PDU session sent by a second network element of the core network.

[0520] In some embodiments, the processing module 7402 is configured to select a fourth network element of the core network for the terminal based on the second request message, where the fourth network element is used to implement a user plane function.

[0521] Optionally, the above-mentioned transceiver module 7401 is used to execute at least one of the communication steps such as sending and / or receiving performed by the third network element 1033 in any of the above methods (for example, step S2107, but not limited to this), which will not be repeated here.

[0522] Optionally, the above-mentioned processing module 7402 is used to execute at least one of the other steps (such as step S2108, step S2110, step S2111, step S2114, but not limited to these) performed by the third network element 1033 in any of the above methods, which are not repeated here.

[0523] FIG7E is a schematic diagram of the structure of a fourth network element proposed in an embodiment of the present disclosure. As shown in FIG7E , the fourth network element 7500 may include: at least one of a transceiver module 7501 and a processing module 7502 .

[0524] Optionally, the above-mentioned transceiver module 7501 is used to execute at least one of the communication steps such as sending and / or receiving performed by the fourth network element 7500 in any of the above methods (for example, communicating with the first network element or terminal to provide user plane function-related information, but not limited to this), which will not be repeated here.

[0525] Optionally, the above-mentioned processing module 7502 is used to execute at least one of the other steps performed by the fourth network element 7500 in any of the above methods (such as providing user plane functions for the terminal, but not limited to this), which will not be repeated here.

[0526] In some embodiments, the transceiver module may include a transmitting module and / or a receiving module, and the transmitting module and the receiving module may be separate or integrated. Optionally, the transceiver module may be interchangeable with the transceiver.

[0527] In some embodiments, the processing module can be a single module or can include multiple submodules. Optionally, the multiple submodules respectively execute all or part of the steps required to be executed by the processing module. Optionally, the processing module can be interchangeable with the processor.

[0528] Figure 8A is a schematic diagram of the structure of a communication device 8100 proposed in an embodiment of the present disclosure. Communication device 8100 can be a network device (e.g., a core network device), a terminal (e.g., a user equipment), a chip, a chip system, or a processor that supports a core network device in implementing any of the above methods, or a chip, a chip system, or a processor that supports a terminal in implementing any of the above methods. Communication device 8100 can be used to implement the methods described in the above method embodiments. For details, please refer to the description of the above method embodiments.

[0529] As shown in Figure 8A, the communication device 8100 includes one or more processors 8101. The processor 8101 can be a general-purpose processor or a dedicated processor, for example, a baseband processor or a central processing unit. The baseband processor can be used to process communication protocols and communication data, and the central processing unit can be used to control the communication device (such as a base station, a baseband chip, a terminal device, a terminal device chip, a DU or a CU, etc.), execute programs, and process program data. The communication device 8100 is used to perform any of the above methods.

[0530] In some embodiments, the communication device 8100 further includes one or more memories 8102 for storing instructions. Optionally, all or part of the memories 8102 may be located outside the communication device 8100.

[0531] In some embodiments, the communication device 8100 further includes one or more transceivers 8103. When the communication device 8100 includes one or more transceivers 8103, the transceiver 8103 performs at least one of the communication steps such as sending and / or receiving in the above method (for example, step S2101, step S2103, step S2104, step S2105, step S2107, step S2109, step S2112, but not limited thereto), and the processor 8101 performs at least one of the other steps (step S2102, step S2106, step S2108, step S2110, step S2112, step S2111, step S2113, step S2114, but not limited thereto).

[0532] In some embodiments, a transceiver may include a receiver and / or a transmitter. The receiver and transmitter may be separate or integrated. Optionally, the terms transceiver, transceiver unit, transceiver, and transceiver circuit may be used interchangeably; the terms transmitter, transmitting unit, transmitter, and transmitting circuit may be used interchangeably; and the terms receiver, receiving unit, receiver, and receiving circuit may be used interchangeably.

[0533] In some embodiments, the communication device 8100 may include one or more interface circuits 8104. Optionally, the interface circuit 8104 is connected to the memory 8102. The interface circuit 8104 may be configured to receive signals from the memory 8102 or other devices, and may be configured to send signals to the memory 8102 or other devices. For example, the interface circuit 8104 may read instructions stored in the memory 8102 and send the instructions to the processor 8101.

[0534] The communication device 8100 described in the above embodiment may be a network device or a terminal, but the scope of the communication device 8100 described in the present disclosure is not limited thereto, and the structure of the communication device 8100 may not be limited by FIG. 8A. The communication device may be an independent device or may be part of a larger device. For example, the communication device may be: 1) an independent integrated circuit IC, or a chip, or a chip system or subsystem; (2) a collection of one or more ICs, optionally, the above IC collection may also include a storage component for storing data or programs; (3) an ASIC, such as a modem; (4) a module that can be embedded in other devices; (5) a receiver, a terminal device, an intelligent terminal device, a cellular phone, a wireless device, a handheld device, a mobile unit, an in-vehicle device, a network device, a cloud device, an artificial intelligence device, etc.; (6) others, etc.

[0535] FIG8B is a schematic diagram of the structure of a chip 8200 according to an embodiment of the present disclosure. If the communication device 8200 can be a chip or a chip system, please refer to the schematic diagram of the structure of the chip 8200 shown in FIG8B , but the present disclosure is not limited thereto.

[0536] The chip 8200 includes one or more processors 8201 , and the chip 8200 is configured to execute any of the above methods.

[0537] In some embodiments, chip 8200 further includes one or more interface circuits 8202. Optionally, interface circuit 8202 is connected to memory 8203. Interface circuit 8202 can be used to receive signals from memory 8203 or other devices, or to send signals to memory 8203 or other devices. For example, interface circuit 8202 can read instructions stored in memory 8203 and send the instructions to processor 8201.

[0538] In some embodiments, the interface circuit 8202 executes at least one of the communication steps such as sending and / or receiving in the above method (for example, step S2101, step S2103, step S2104, step S2105, step S2107, step S2109, step S2112, but not limited to these), and the processor 8201 executes at least one of the other steps (step S2102, step S2106, step S2108, step S2110, step S2112, step S2111, step S2113, step S2114, but not limited to these).

[0539] In some embodiments, terms such as interface circuit, interface, transceiver pin, and transceiver may be used interchangeably.

[0540] In some embodiments, the chip 8200 further includes one or more memories 8203 for storing instructions. Alternatively, all or part of the memories 8203 may be outside the chip 8200.

[0541] The present disclosure also proposes a storage medium having instructions stored thereon, which, when executed on the communication device 8100, causes the communication device 8100 to execute any of the above methods. Optionally, the storage medium is an electronic storage medium. Optionally, the storage medium is a computer-readable storage medium, but is not limited thereto, and may also be a storage medium readable by other devices. Optionally, the storage medium may be a non-transitory storage medium, but is not limited thereto, and may also be a temporary storage medium.

[0542] The present disclosure also provides a program product, which, when executed by the communication device 8100, enables the communication device 8100 to perform any of the above methods. Optionally, the program product is a computer program product.

[0543] The present disclosure also proposes a computer program, which, when executed on a computer, causes the computer to perform any one of the above methods.

[0544] Other embodiments of the present disclosure will readily occur to those skilled in the art after considering the specification and practicing the invention disclosed herein. This disclosure is intended to cover any variations, uses, or adaptations of the present disclosure that follow the general principles of the present disclosure and include common knowledge or customary techniques in the art not disclosed herein. The description and examples are to be considered as exemplary only, with the true scope and spirit of the present disclosure being indicated by the following claims.

[0545] It should be understood that the present disclosure is not limited to the exact structures that have been described above and shown in the drawings, and that various modifications and changes can be made without departing from the scope thereof. The scope of the present disclosure is limited only by the appended claims.

Claims

1. A method for establishing a user plane connection, characterized in that: The method is executed by a terminal, and includes: Sending a first request message related to a protocol data unit (PDU) session to a first network element of a core network, wherein the first request message is also used to initiate user plane positioning; receiving a response message sent by the first network element, and determining a PDU session for positioning the user plane, wherein the response message includes user plane information; Based on the user plane information, a user plane connection is established with a second network element of a core network through the PDU session, where the user plane connection is used for the user plane positioning.

2. The method according to claim 1, characterized in that The first request message is an uplink non-access layer transmission message; The response message is a downlink non-access layer transmission message.

3. The method according to claim 1 or 2, characterized in that: The first request message includes any one or more of the following: PDU session establishment request message; PDU Session Modification Request message.

4. The method according to any one of claims 1 to 3, characterized in that: The first request message includes at least one of the following: A request type parameter, wherein the type value of the request type parameter is used to indicate a user plane positioning request, and the user plane positioning request is used to request to initiate the user plane positioning; A first parameter, where the first parameter is used to indicate the user plane positioning request; An information element where a user plane positioning information container and first additional information are located, wherein the user plane positioning information container and the first additional information are used to indicate the user plane positioning request; A first payload container, where the first payload container is used to indicate the user plane positioning request.

5. The method according to any one of claims 1 to 4, characterized in that: Receiving a response message sent by the first network element, including: receiving a first response message sent by the first network element, where the first response message includes the user plane information; and, A second response message sent by the first network element is received, where the second response message includes PDU session response information.

6. The method according to claim 5, characterized in that The receiving a response message sent by the first network element and determining a PDU session for the user plane positioning includes: The first response message and the second response message are received, and the PDU session used for the user plane positioning is determined.

7. The method according to any one of claims 1 to 4, characterized in that: Receiving a response message sent by the first network element, including: Receive a third response message sent by the first network element, where the third response message includes the user plane information and the PDU session response information.

8. A method for establishing a user plane connection, characterized in that: The method is performed by a first network element of a core network, and includes: A first request message related to a protocol data unit (PDU) session sent by a receiving terminal, wherein the first request message is also used to initiate user plane positioning; A response message including user plane information is sent to the terminal, so that the terminal determines the PDU session used for the user plane positioning based on the response message, and then establishes a user plane connection with the second network element of the core network through the PDU session based on the user plane information, and the user plane connection is used for the user plane positioning.

9. The method according to claim 8, characterized in that The first request message is an uplink non-access layer transmission message; The response message is a downlink non-access layer transmission message.

10. The method according to claim 8 or 9, characterized in that: The first request message includes any one or more of the following: PDU session establishment request message; PDU Session Modification Request message.

11. The method according to any one of claims 8 to 10, characterized in that: The first request message includes at least one of the following: A request type parameter, wherein the type value of the request type parameter is used to indicate a user plane positioning request, and the user plane positioning request is used to request to initiate the user plane positioning; A first parameter, where the first parameter is used to indicate the user plane positioning request; An information element where a user plane positioning information container and first additional information are located, wherein the user plane positioning information container and the first additional information are used to indicate the user plane positioning request; A first payload container, where the first payload container is used to indicate the user plane positioning request.

12. The method according to any one of claims 8 to 11, characterized in that: The method further comprises: Based on the first request message, respectively select the second network element and the third network element of the core network for the terminal; Receive the user plane information sent by the second network element, and receive the PDU session response information sent by the third network element.

13. The method according to claim 12, characterized in that The selecting, based on the first request message, the second network element and the third network element of the core network for the terminal respectively includes: After selecting the second network element for the terminal, the third network element is selected for the terminal based on the first request message and the selected second network element.

14. The method according to claim 13, characterized in that The method further comprises: Sending a second request message related to the PDU session to the selected third network element.

15. The method according to claim 14, characterized in that The second request message is any one or more of the following: PDU session create session management context request message; PDU session update session management context request message.

16. The method according to claim 14 or 15, characterized in that The second request message includes: Relevant information of the second network element.

17. The method according to claim 12, characterized in that The selecting, based on the first request message, the second network element and the third network element of the core network for the terminal respectively includes: After selecting the third network element for the terminal, the second network element is selected for the terminal based on the first request message and the selected third network element.

18. The method according to claim 17, characterized in that The method further comprises: A third request message is sent to the selected second network element, where the third request message is used to request establishment of a user plane connection.

19. The method according to claim 17 or 18, characterized in that The third request message includes: Relevant information of the third network element.

20. The method according to any one of claims 12 to 19, characterized in that: The sending a response message to the terminal includes: receiving the user plane information sent by the second network element, sending a first response message to the terminal, wherein the first response message includes the user plane information; and, Receive the PDU session response information sent by the third network element, and send a second response message to the terminal, where the second response message includes the PDU session response information.

21. The method according to any one of claims 12 to 19, characterized in that: The sending a response message to the terminal includes: Receive the user plane information sent by the second network element and receive the PDU session response information sent by the third network element, and send a third response message to the terminal, wherein the third response message includes the user plane information and the PDU session response information.

22. A method for establishing a user plane connection, characterized in that: The method is performed by a third network element of the core network, and includes: Receiving a second request message related to the PDU session sent by a second network element of the core network; Based on the second request message, a fourth network element of the core network is selected for the terminal, where the fourth network element is used to implement a user plane function.

23. The method according to claim 22, characterized in that The second request message is any one or more of the following: PDU session create session management context request message; PDU session update session management context request message.

24. The method according to claim 22 or 23, characterized in that The second request message includes: Relevant information of the second network element.

25. A terminal, characterized in that: The terminal comprises: A transceiver module, configured to send a first request message related to a protocol data unit (PDU) session to a first network element of a core network, wherein the first request message is also used to initiate user plane positioning; A processing module is configured to receive a response message sent by the first network element and determine a PDU session for positioning the user plane, wherein the response message includes user plane information; The processing module is further configured to establish a user plane connection with a second network element of the core network through the PDU session based on the user plane information, and the user plane connection is used for the user plane positioning.

26. A first network element of a core network, characterized in that: The first network element includes: A transceiver module, configured to receive a first request message related to a protocol data unit (PDU) session sent by a terminal, wherein the first request message is also used to initiate user plane positioning; The transceiver module is further configured to send a response message including user plane information to the terminal, so that the terminal determines the PDU session for the user plane positioning based on the response message, and then sends the PDU session based on the user plane information to the terminal. The session establishes a user plane connection with a second network element of the core network, where the user plane connection is used for the user plane positioning.

27. A third network element of a core network, characterized in that: The third network element includes: A transceiver module, configured to receive a second request message related to the PDU session sent by a second network element of the core network; The processing module is configured to select a fourth network element of the core network for the terminal based on the second request message, and the fourth network element is used to implement the user plane function.

28. A terminal, characterized in that: include: one or more processors; The terminal is used to execute the method for establishing a user plane connection according to any one of claims 1 to 7.

29. A first network element of a core network, characterized in that: include: one or more processors; The first network element is used to execute the method for establishing a user plane connection according to any one of claims 8 to 21.

30. A third network element of a core network, characterized in that: include: one or more processors; The third network element is used to execute the method for establishing a user plane connection according to any one of claims 22 to 24.

31. A core network device, characterized in that: include: A first network element, wherein the first network element is configured to implement the method for establishing a user plane connection according to any one of claims 8 to 18; a second network element, the second network element being configured to send user plane information to the first network element; A third network element, wherein the third network element is configured to implement the method for establishing a user plane connection according to any one of claims 22 to 24; A fourth network element, wherein the fourth network element is used to implement a user plane function.

32. A communication system, characterized in that: It includes a terminal and a core network device, wherein the terminal is configured to implement the method for establishing a user plane connection described in any one of claims 1-7, and the core network device is configured to implement the method for establishing a user plane connection described in any one of claims 8-24.

33. A storage medium storing instructions, characterized in that: When the instruction is executed on a communication device, the communication device is caused to execute the method for establishing a user plane connection according to any one of claims 1-7 or 8-24.

Images