User plane positioning connection processing method, first network element, second network element, and terminal

Abstract

The present disclosure relates to a user plane positioning connection processing method, a first network element, a second network element, and a terminal. The method comprises: sending a first identifier and a first message to a second network element, the first message being a message related to establishing a user plane connection or a message related to releasing a user plane connection, the first identifier being used to identify first information, and the first information being at least one of the following: the first network element, the user plane connection, and / or a location service session of the first network element with a terminal. In embodiments of the present disclosure, by means of sending a first identifier and a first message to a second network element, the second network element can, on the basis of the first identifier, accurately send a message to a first network element related to the terminal in the process of processing a user plane positioning connection, and may also lay a foundation for identifying, for the first network element and the terminal, an LCS session between the first network element and the terminal.

Description

User plane positioning connection processing method, first network element, second network element and terminal Technical Field

[0001] The present disclosure relates to the field of communication technologies, and in particular to a method for processing a user plane positioning connection, a first network element, a second network element, and a terminal. Background Art

[0002] In the current User Plane Positioning Connection Management (UPP-CM) method, when the Location Management Function (LMF) interacts with the terminal through the Access and Mobility Management Function (AMF), the AMF cannot accurately forward the message to the LMF related to the terminal, and the LMF and UE cannot accurately identify the Location Service Session (LCS Session) between the LMF and the UE.

[0003] Summary of the Invention

[0004] The embodiments of the present disclosure provide a method for processing a user plane positioning connection, a first network element, a second network element, and a terminal.

[0005] According to a first aspect of an embodiment of the present disclosure, a method for processing a user plane positioning connection is provided, which is executed by a first network element. The method includes:

[0006] Sending the first identifier and the first message to the second network element;

[0007] The first message is a message related to establishing a user plane connection or a message related to releasing a user plane connection;

[0008] The first identifier is used to identify first information, and the first information is at least one of the following: the first network element, the user plane connection, and a positioning service session between the first network element and the terminal.

[0009] The embodiment of the present disclosure sends a first identifier and a first message to the second network element, so that the second network element can accurately send the message to the first network element related to the terminal according to the first identifier during the processing of the user plane positioning connection, and also lays the foundation for the first network element and the terminal to identify the LCS session between the first network element and the terminal.

[0010] According to a second aspect of an embodiment of the present disclosure, a method for processing a user plane positioning connection is provided, which is executed by a second network element. The method includes:

[0011] receiving a first identifier and a first message sent by a first network element;

[0012] The first message is a message related to establishing a user plane connection or a message related to releasing a user plane connection;

[0013] The first identifier is used to identify first information, and the first information is at least one of the following: the first network element, the user plane connection, and a positioning service session between the first network element and the terminal.

[0014] According to a third aspect of an embodiment of the present disclosure, a user plane positioning connection method is provided, which is executed by a terminal. The method includes:

[0015] receiving a second identifier and a first message sent by a second network element;

[0016] The first message is a message related to establishing a user plane connection or a message related to releasing a user plane connection;

[0017] The second identifier is determined according to the first identifier sent by the first network element, the first identifier is used to identify the first information, and the second identifier is used to identify the first information in the terminal;

[0018] The first information is at least one of the following: the first network element, the user plane connection, and a positioning service session between the first network element and the terminal.

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

[0020] a transceiver module, configured to send a first identifier and a first message to a second network element;

[0021] The first message is a message related to establishing a user plane connection or a message related to releasing a user plane connection;

[0022] The first identifier is used to identify first information, and the first information is at least one of the following: the first network element, the user plane connection, and a positioning service session between the first network element and the terminal.

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

[0024] a transceiver module, configured to receive a first identifier and a first message sent by a first network element;

[0025] The first message is a message related to establishing a user plane connection or a message related to releasing a user plane connection;

[0026] The first identifier is used to identify first information, and the first information is at least one of the following: the first network element, the user plane connection, and a positioning service session between the first network element and the terminal.

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

[0028] a transceiver module, configured to receive a second identifier and a first message sent by a second network element;

[0029] The first message is a message related to establishing a user plane connection or a message related to releasing a user plane connection;

[0030] The second identifier is determined according to the first identifier sent by the first network element, the first identifier is used to identify the first information, and the second identifier is used to identify the first information in the terminal;

[0031] The first information is at least one of the following: the first network element, the user plane connection, and a positioning service session between the first network element and the terminal.

[0032] According to the seventh aspect of an embodiment of the present disclosure, a communication system is proposed, including a first network element, a second network element and a terminal, the first network element is configured to implement the processing method of the user plane positioning connection described in the first aspect, the second network element is configured to implement the processing method of the user plane positioning connection described in the second aspect, and the terminal is configured to implement the processing method of the user plane positioning connection described in the third aspect.

[0033] According to an eighth aspect of an embodiment of the present disclosure, a storage medium is proposed. When the instruction is executed on a communication device, the communication device executes the method for processing user plane positioning connection as described in the first, second or third aspect. BRIEF DESCRIPTION OF THE DRAWINGS

[0034] In order to more clearly illustrate the technical solutions in the embodiments of the present disclosure, the following drawings required for describing the embodiments are introduced. The following drawings are merely some embodiments of the present disclosure and do not impose specific limitations on the protection scope of the present disclosure.

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

[0036] FIG2 is an interactive schematic diagram of a method for processing a user plane positioning connection according to an embodiment of the present disclosure;

[0037] FIG3A is a schematic flow chart of a method for processing a user plane positioning connection according to an embodiment of the present disclosure;

[0038] FIG3B is a schematic diagram of a process of processing a user plane positioning connection according to an embodiment of the present disclosure;

[0039] FIG3C is a schematic diagram of a process of processing a user plane positioning connection according to an embodiment of the present disclosure;

[0040] FIG3D is a schematic diagram of a process of processing a user plane positioning connection according to an embodiment of the present disclosure;

[0041] FIG3E is a schematic diagram of a process of processing a user plane positioning connection according to an embodiment of the present disclosure;

[0042] FIG4A is a schematic flow chart of a method for processing a user plane positioning connection according to an embodiment of the present disclosure;

[0043] FIG4B is a schematic flow chart of a method for processing a user plane positioning connection according to an embodiment of the present disclosure;

[0044] FIG4C is a schematic diagram of a process of processing a user plane positioning connection according to an embodiment of the present disclosure;

[0045] FIG4D is a schematic diagram of a process of processing a user plane positioning connection according to an embodiment of the present disclosure;

[0046] FIG4E is a schematic diagram of a process of processing a user plane positioning connection according to an embodiment of the present disclosure;

[0047] FIG5A is a schematic flow chart of a method for processing a user plane positioning connection according to an embodiment of the present disclosure;

[0048] FIG5B is a schematic diagram of a process of processing a user plane positioning connection according to an embodiment of the present disclosure;

[0049] FIG5C is a schematic diagram of a process of processing a user plane positioning connection according to an embodiment of the present disclosure;

[0050] FIG5D is a schematic diagram of a process of processing a user plane positioning connection according to an embodiment of the present disclosure;

[0051] FIG6A is an interactive schematic diagram illustrating a method for processing a user plane positioning connection according to an embodiment of the present disclosure;

[0052] FIG6B is an interactive diagram illustrating a method for processing a user plane positioning connection according to an embodiment of the present disclosure;

[0053] FIG6C is an interactive diagram illustrating a method for processing a user plane positioning connection according to an embodiment of the present disclosure;

[0054] FIG6D is an interactive diagram illustrating a method for processing a user plane positioning connection according to an embodiment of the present disclosure;

[0055] FIG7A is a schematic structural diagram of a first network element proposed in an embodiment of the present disclosure;

[0056] FIG7B is a schematic structural diagram of a second network element proposed in an embodiment of the present disclosure;

[0057] FIG7C is a schematic structural diagram of a terminal proposed in an embodiment of the present disclosure;

[0058] FIG8A is a schematic structural diagram of a communication device proposed in an embodiment of the present disclosure;

[0059] FIG8B is a schematic diagram of the structure of the chip proposed in an embodiment of the present disclosure. DETAILED DESCRIPTION

[0060] The embodiments of the present disclosure provide a method for processing a user plane positioning connection, a first network element, a second network element, and a terminal.

[0061] In a first aspect, an embodiment of the present disclosure provides a method for processing a user plane positioning connection, which is executed by a first network element. The method includes:

[0062] Sending the first identifier and the first message to the second network element;

[0063] The first message is a message related to establishing a user plane connection or a message related to releasing a user plane connection;

[0064] The first identifier is used to identify first information, where the first information is at least one of a first network element, a user plane connection, or a positioning service session between the first network element and the terminal.

[0065] The embodiment of the present disclosure sends a first identifier and a first message to the second network element, so that the second network element can accurately send the message to the first network element related to the terminal according to the first identifier during the processing of the user plane positioning connection, and also lays the foundation for the first network element and the terminal to identify the LCS session between the first network element and the terminal.

[0066] In conjunction with some embodiments of the first aspect, in some embodiments, the first identifier is allocated by the first network element to establish a user plane connection for user plane positioning, or,

[0067] The first identifier is allocated by the second network element according to a user plane connection establishment request received from the terminal.

[0068] The first identifier of the embodiment of the present disclosure can be allocated by the first network element or configured by the second network element, which improves the flexibility of allocating the first identifier.

[0069] In some embodiments, the first message related to establishing the user plane connection is at least one of the following:

[0070] User plane connection establishment command message;

[0071] User plane connection establishment response message.

[0072] In the embodiment of the present disclosure, the first message related to establishing a user plane connection is at least one of a user plane connection establishment command message and a user plane connection establishment response message, so that in the process of establishing the user plane connection, the second network element can accurately return the message returned by the terminal to the first network element indicated by the first identifier according to the first identifier, and also lay the foundation for the first network element and the terminal to identify the LCS session between the first network element and the terminal.

[0073] In some embodiments, sending the first identifier and the first message to the second network element includes:

[0074] Determine to establish a user plane connection for user plane positioning, and allocate a first identifier;

[0075] A first identifier and a first message are sent to the second network element, where the first message is a user plane connection establishment command message.

[0076] In the scenario where the network initiates a user plane connection, the embodiment of the present disclosure determines to establish a user plane connection and allocates a first identifier for user plane positioning, and provides a feasible solution for allocating the first identifier.

[0077] In some embodiments, sending the first identifier and the first message to the second network element includes:

[0078] receiving a user plane connection establishment request and a first identifier sent by a second network element, where the first identifier is allocated by the second network element according to the user plane connection establishment request received from the terminal;

[0079] Accept the user plane connection establishment request, determine to establish a user plane connection for user plane positioning, and send a first identifier and a first message to the second network element, where the first message is a user plane connection establishment response message or a user plane connection establishment command message.

[0080] In the scenario where a terminal initiates a user plane connection, the embodiment of the present disclosure determines that the second network element locates the user plane, establishes the user plane connection, and allocates a first identifier, thereby providing a feasible solution for allocating the first identifier.

[0081] In some embodiments, sending the first identifier and the first message to the second network element includes:

[0082] receiving a user plane connection establishment request sent by the second network element, where the user plane connection establishment request is sent by the terminal to the second network element;

[0083] Accepting a user plane connection establishment request, determining to establish a user plane connection for user plane positioning, and allocating a first identifier;

[0084] A first identifier and a first message are sent to the second network element, where the first message is a user plane connection establishment response message or a user plane connection establishment command message.

[0085] In the scenario where a terminal initiates a user plane connection, the embodiment of the present disclosure determines to establish a user plane connection and allocates a first identifier for user plane positioning, and provides a feasible solution for allocating the first identifier.

[0086] In some embodiments, the method further includes sending the first identifier and the first message to the second network element:

[0087] Receive the first identifier and the user plane connection establishment completion message sent by the second network element.

[0088] In the embodiment of the present disclosure, the first network element receives the first identifier and the user plane connection establishment completion message sent by the second network element, so that the first network element can accurately identify the LCS session between the first network element and the terminal.

[0089] In some embodiments, the first message related to releasing the user plane connection is at least one of the following:

[0090] User plane connection release command message;

[0091] User plane connection release response message.

[0092] In the embodiment of the present disclosure, the first message related to releasing the user plane connection is at least one of a user plane connection release command message and a user plane connection release response message, so that in the process of releasing the user plane connection, the second network element can send the first message to the correct terminal according to the first identifier.

[0093] In some embodiments, sending the first identifier and the first message to the second network element includes:

[0094] Determine to release the user plane connection, and send a first identifier and a first message to the second network element, where the first message is a user plane connection release command message.

[0095] The embodiment of the present disclosure is a scenario in which the network initiates the release of a user plane connection. The first network element sends a first identifier and a first message to the second network element, where the first message is a user plane connection release command message, so that in the process of releasing the user plane connection, the second network element can send the first message to the correct terminal according to the first identifier.

[0096] In some embodiments, sending the first identifier and the first message to the second network element includes:

[0097] receiving a user plane connection release request and a first identifier sent by a second network element;

[0098] Accept the user plane connection release request, determine to release the user plane connection, and send a first identifier and a first message to the second network element, where the first message is a user plane connection release response message or a user plane connection release command message.

[0099] The embodiment of the present disclosure is a scenario in which a terminal initiates a user plane connection release. A first network element receives a user plane connection release request and a first identifier sent by a second network element. The first network element can identify an LCS session between the first identifier and the terminal based on the first identifier.

[0100] In some embodiments, the method further includes sending the first identifier and the first message to the second network element:

[0101] Receive the first identifier and the user plane connection release completion message sent by the second network element.

[0102] In the embodiment of the present disclosure, the first network element receives the first identifier and the user plane connection release completion message sent by the second network element, and the first network element can identify the LCS session between the first identifier and the terminal according to the first identifier.

[0103] In a second aspect, an embodiment of the present disclosure provides a method for processing a user plane positioning connection, which is executed by a second network element, and the method includes:

[0104] receiving a first identifier and a first message sent by a first network element;

[0105] The first message is a message related to establishing a user plane connection or a message related to releasing a user plane connection;

[0106] The first identifier is used to identify first information, where the first information is at least one of a first network element, a user plane connection, or a positioning service session between the first network element and the terminal.

[0107] In conjunction with some embodiments of the second aspect, in some embodiments, the first identifier is allocated by the first network element to establish a user plane connection for user plane positioning, or,

[0108] The first identifier is allocated by the second network element according to a user plane connection establishment request received from the terminal.

[0109] In some embodiments, the first message related to establishing the user plane connection is at least one of the following:

[0110] User plane connection establishment command message;

[0111] User plane connection establishment response message.

[0112] In some embodiments, the first message is a user plane connection establishment command message;

[0113] The first identifier and the first message are sent by the first network element to establish a user plane connection for user plane positioning.

[0114] In some embodiments, the first identifier is used to identify the first information in the core network;

[0115] receiving a first identifier and a first message sent by a first network element, and then further comprising:

[0116] Mapping the first identifier to a second identifier, and sending the second identifier and the first message to the terminal, where the second identifier is used to identify the first information in the terminal;

[0117] receiving a second identifier and a user plane connection establishment completion message sent by the terminal;

[0118] The second identifier is mapped to the first identifier, and the first identifier and a user plane connection establishment completion message are sent to the first network element indicated by the first identifier.

[0119] In some embodiments, the first identifier is used to identify the first information in the core network and the terminal;

[0120] receiving a first identifier and a first message sent by a first network element, and then further comprising:

[0121] Using the first identifier as the second identifier, and sending the second identifier and the first message to the terminal;

[0122] receiving a second identifier and a user plane connection establishment completion message sent by the terminal;

[0123] The second identifier is used as the first identifier, and the first identifier and a user plane connection establishment completion message are sent to the first network element indicated by the first identifier.

[0124] In some embodiments, receiving the first identifier and the first message sent by the first network element includes:

[0125] Receiving a user plane connection establishment request sent by a terminal;

[0126] Sending a user plane connection establishment request to the first network element;

[0127] A first identifier and a first message sent by a first network element are received, where the first message is a user plane connection establishment response or a user plane connection establishment command, and the first identifier is allocated by the first network element to establish a user plane connection for user plane positioning.

[0128] In some embodiments, receiving the first identifier and the first message sent by the first network element includes:

[0129] Receiving a user plane connection establishment request sent by a terminal;

[0130] assigning a first identifier;

[0131] Sending a user plane connection establishment request and a first identifier to the first network element;

[0132] A first identifier and a first message sent by a first network element are received, where the first message is a user plane connection establishment response or a user plane connection establishment command.

[0133] In some embodiments, the first identifier is used to identify the first information in the core network;

[0134] receiving a first identifier and a first message sent by a first network element, and then further comprising:

[0135] The first identifier is mapped to a second identifier, and the second identifier and the first message are sent to the terminal, where the second identifier is used to identify the first information in the terminal.

[0136] In some embodiments, the first identifier is used to identify the first information in the core network and the terminal;

[0137] receiving a first identifier and a first message sent by a first network element, and then further comprising:

[0138] The first identifier is used as the second identifier, and the second identifier and the first message are sent to the terminal.

[0139] In some embodiments, the message related to releasing the user plane connection includes at least one of the following:

[0140] User plane connection release command message;

[0141] User plane connection release response message.

[0142] In some embodiments, the first message is a user plane connection release command message;

[0143] The first identifier and the first message are sent after the first network element determines to release the user plane connection.

[0144] In some embodiments, the first identifier is used to identify the first information in the core network;

[0145] receiving a first identifier and a first message sent by a first network element, and then further comprising:

[0146] Mapping the first identifier to a second identifier, and sending the second identifier and the first message to the terminal, where the second identifier is used to identify the first information in the terminal;

[0147] receiving a second identifier and a user plane connection release completion message sent by the terminal;

[0148] The second identifier is mapped to the first identifier, and the first identifier and a user plane connection release completion message are sent to the first network element indicated by the first identifier.

[0149] In some embodiments, the first identifier is used to identify the first information in the core network and the terminal;

[0150] receiving a first identifier and a first message sent by a first network element, and then further comprising:

[0151] Using the first identifier as the second identifier, and sending the second identifier and the first message to the terminal;

[0152] receiving a second identifier and a user plane connection release completion message sent by the terminal;

[0153] The second identifier is used as the first identifier, and the first identifier and a user plane connection release completion message are sent to the first network element indicated by the first identifier.

[0154] In some embodiments, receiving the first identifier and the first message sent by the first network element includes:

[0155] receiving a user plane connection release request and a second identifier sent by a terminal, where the second identifier is used to identify the first information in the terminal;

[0156] Mapping the second identifier to the first identifier, where the first identifier is used to identify the first information in the core network, and sending a user plane connection release request and the first identifier to the first network element indicated by the first identifier;

[0157] A first identifier and a first message sent by a first network element are received, where the first message is a user plane connection release response or a user plane connection release command.

[0158] In some embodiments, receiving the first identifier and the first message sent by the first network element includes:

[0159] Receiving a user plane connection release request and a second identifier sent by the terminal, where the second identifier is used to identify the first information in the core network and the terminal;

[0160] Using the second identifier as the first identifier, sending a user plane connection release request and the first identifier to the first network element indicated by the first identifier;

[0161] A first identifier and a first message sent by a first network element are received, where the first message is a user plane connection release response message or a user plane connection release command message.

[0162] In some embodiments, receiving a first identifier and a first message sent by a first network element further includes:

[0163] Mapping the first identifier to the second identifier;

[0164] The second identifier and the first message are sent to the terminal.

[0165] In some embodiments, receiving a first identifier and a first message sent by a first network element further includes:

[0166] Using the first identifier as the second identifier;

[0167] The second identifier and the first message are sent to the terminal.

[0168] In a third aspect, an embodiment of the present disclosure provides a method for processing a user plane positioning connection, which is executed by a terminal, and the method includes:

[0169] receiving a second identifier and a first message sent by a second network element;

[0170] The first message is a message related to establishing a user plane connection or a message related to releasing a user plane connection;

[0171] The second identifier is determined according to the first identifier sent by the first network element, the first identifier is used to identify the first information, and the second identifier is used to identify the first information in the terminal;

[0172] The first information is at least one of the first network element, the user plane connection, or the positioning service session between the first network element and the terminal.

[0173] In conjunction with some embodiments of the third aspect, in some embodiments,

[0174] The first identifier is allocated by the first network element for establishing a user plane connection for user plane positioning, or

[0175] The first identifier is allocated by the second network element according to a user plane connection establishment request received from the terminal.

[0176] In some embodiments, the first message is a user plane connection establishment command message, and the method further includes:

[0177] Establishing a user plane connection for user plane positioning;

[0178] Send the second identifier and a user plane connection establishment completion message to the second network element.

[0179] In some embodiments, the first message is a user plane connection release command message, and the method further includes:

[0180] Release the user plane connection used for user plane positioning;

[0181] Send the second identifier and a user plane connection release completion message to the second network element.

[0182] In some embodiments, the first message is a user plane connection establishment command or a user plane connection establishment response;

[0183] receiving a second identifier and a first message sent by a second network element, wherein the method further includes:

[0184] Send a user plane connection establishment request to the second network element.

[0185] In some embodiments, the first message is a user plane connection release command or a user plane connection release response;

[0186] receiving a second identifier and a first message sent by a second network element, wherein the method further includes:

[0187] Send a user plane connection release request to the second network element.

[0188] In a fourth aspect, an embodiment of the present disclosure provides a first network element, including:

[0189] a transceiver module, configured to send a first identifier and a first message to a second network element;

[0190] The first message is a message related to establishing a user plane connection or a message related to releasing a user plane connection;

[0191] The first identifier is used to identify first information, where the first information is at least one of a first network element, a user plane connection, or a positioning service session between the first network element and the terminal.

[0192] In a fifth aspect, an embodiment of the present disclosure provides a second network element, including:

[0193] a transceiver module, configured to receive a first identifier and a first message sent by a first network element;

[0194] The first message is a message related to establishing a user plane connection or a message related to releasing a user plane connection;

[0195] The first identifier is used to identify first information, where the first information is at least one of a first network element, a user plane connection, or a positioning service session between the first network element and the terminal.

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

[0197] a transceiver module, configured to receive a second identifier and a first message sent by a second network element;

[0198] The first message is a message related to establishing a user plane connection or a message related to releasing a user plane connection;

[0199] The second identifier is determined according to the first identifier sent by the first network element, the first identifier is used to identify the first information, and the second identifier is used to identify the first information in the terminal;

[0200] The first information is at least one of the first network element, the user plane connection, or the positioning service session between the first network element and the terminal.

[0201] In the seventh aspect, an embodiment of the present disclosure proposes a communication system, which includes: a first network element, a second network element and a terminal; wherein the first network element is configured to execute the method described in the optional implementation manner of the first aspect, the second network element is configured to execute the method described in the optional implementation manner of the second aspect, and the terminal is configured to execute the method described in the optional implementation manner of the third aspect.

[0202] In an eighth 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 described in the optional implementation of the first aspect, the second aspect or the third aspect.

[0203] In a ninth aspect, an embodiment of the present disclosure proposes a program product. When the program product is executed by a communication device, the communication device executes the method described in the optional implementation manner of the first aspect, the second aspect or the third aspect.

[0204] In a tenth aspect, an embodiment of the present disclosure proposes a computer program, which, when executed on a computer, enables the computer to execute the method described in the optional implementation of the first aspect, the second aspect, or the third aspect.

[0205] In an eleventh aspect, an embodiment of the present disclosure provides a chip or a chip system, wherein the chip or chip system includes a processing circuit configured to execute the method described in the optional implementation of the first aspect, the second aspect, or the third aspect.

[0206] It is understandable that the first network element, the second network element, the terminal, the communication system, the storage medium, the program product, the computer program, the chip, or the chip system described above are all used to perform the method proposed in the embodiments of the present disclosure. Therefore, the beneficial effects that can be achieved can refer to the beneficial effects of the corresponding methods and will not be repeated here.

[0207] The present disclosure provides a method for processing a user plane positioning connection, a first network element, a second network element, and a terminal. In some embodiments, the terms "method for processing a user plane positioning connection" and "information processing method" and "communication method" are interchangeable; "device for processing a user plane positioning connection" and "information processing device" and "communication device" are interchangeable; and "information processing system" and "communication system" are interchangeable.

[0208] 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.

[0209] 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.

[0210] 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.

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

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

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

[0214] 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.

[0215] 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.

[0216] 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.

[0217] 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.

[0218] In some embodiments, terms such as "time / frequency" and "time / frequency domain" refer to the time domain and / or the frequency domain.

[0219] 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.

[0220] In some embodiments, terms such as "greater than", "greater than or equal to", "not less than", "more than", "more than or equal to", "not less than", "higher than", "higher than or equal to", "not less than", and "above" can be replaced with each other, and terms such as "less than", "less than or equal to", "not greater than", "less than", "less than or equal to", "not more than", "lower than", "lower than or equal to", "not higher than", and "below" can be replaced with each other.

[0221] In some embodiments, devices, etc. can be interpreted as physical or virtual, and their names are not limited to the names recorded in the embodiments. Terms such as "device", "equipment", "device", "circuit", "network element", "node", "function", "unit", "section", "system", "network", "chip", "chip system", "entity", and "subject" can be used interchangeably.

[0222] In some embodiments, "network" can be interpreted as devices included in the network (eg, access network equipment, core network equipment, etc.).

[0223] In some embodiments, the terms "access network device (AN device)", "radio access network device (RAN device)", "base station (BS)", "radio base station" "fixed station", "node", "access point", "transmission point (TP)", "reception point (RP)", "transmission / 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)" and the like may be used interchangeably.

[0224] In some embodiments, the terms "terminal", "terminal device", "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. can be used interchangeably.

[0225] In some embodiments, the access network device, the core network device, or the network device can be replaced by a terminal. For example, the various embodiments of the present disclosure can also be applied to a structure in which the communication between the access network device, the core network device, or the network device and the terminal is replaced by communication between multiple terminals (for example, device-to-device (D2D), vehicle-to-everything (V2X), etc.). In this case, it is also possible to set the structure in which the terminal has all or part of the functions of the access network device. In addition, terms such as "uplink" and "downlink" can also be replaced by terms corresponding to communication between terminals (for example, "side"). For example, uplink channels, downlink channels, etc. can be replaced by side channels, and uplinks, downlinks, etc. can be replaced by side links.

[0226] In some embodiments, the terminal may be replaced by an access network device, a core network device, or a network device. In this case, the access network device, the core network device, or the network device may have a structure that has all or part of the functions of the terminal.

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

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

[0229] 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.

[0230] FIG1 is a schematic diagram illustrating the architecture of a communication system according to an embodiment of the present disclosure. As shown in FIG1 , a communication system 100 includes a terminal 101 and a network device 102 .

[0231] In some embodiments, the network device 102 may include an access network device and a core network device.

[0232] In some embodiments, the access network device 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.

[0233] 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.

[0234] In some embodiments, the access network device 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.

[0235] In some embodiments, the core network device may be a single device including a first network element 1021 and a second network element 1022, etc., or may be a plurality of devices or a device group including all or part of the first network element 1021 and the second network element 1022, etc. The network elements 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).

[0236] In some embodiments, the first network element 1021 may be, for example, a LMF network element, a sensing function (SF) network element.

[0237] In some embodiments, the second network element 1022 may be, for example, an AMF network element.

[0238] 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.

[0239] 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.

[0240] 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, Device-to-Device (D2D) systems, Machine-to-Machine (M2M) systems, Internet of Things (IoT) systems, Vehicle-to-Everything (V2X), systems utilizing other communication methods, and next-generation systems based on and extending these methods. Furthermore, multiple systems may be combined (for example, a combination of LTE or LTE-A with 5G).

[0241] In some embodiments, the first network element or the terminal may trigger the establishment of a user plane connection. The terminal and the first network element may maintain the established user plane connection. The first network element may modify or terminate the user plane connection established between the terminal and the first network element.

[0242] The first network element can send its user plane information (for example, IP address or fully qualified domain name (FQDN)) to the terminal via the DL NAS TRANSPORT message of the second network element. If the first network element sends its FQDN to the terminal, a DNS server or resolver is used to resolve the IP address of the first network element, such as the edge application server discovery function (EASDF) or the local domain name system (DNS) for address resolution of the local first network element. The terminal uses a user route selection policy (URSP) including protocol data unit (PDU) session parameters related to user plane positioning (for example, a dedicated domain name network (DNN) and single network slice selection assistance information (S-NSSAI)) to establish a PDU session for user plane positioning. The SMF should select a PSA-UPF (located at a central site or a local site) connected to the first network element for the PDU session based on the S-NSSAI, DNN, terminal location information, etc.

[0243] Positioning signaling via the user plane has several advantages, such as:

[0244] It has more efficient communication overload through direct connection from LCS server to terminal;

[0245] It may not require the signaling processing of the gNodeB, AMF, and LMF of the RRC, NG-AP, and HTTP / 2 protocol stack. A single session can handle all transactions;

[0246] There are multiple options available depending on the terminal's support. For example, in the selection of positioning methods, both 3GPP LPP and OMA LPPe are possible.

[0247] In some embodiments, the correlation ID is an internal identifier of the core network and can only be used in the core network, and the routing ID can be used in the terminal.

[0248] In some embodiments, the routing identifier and the association identifier may be different terms for the same identifier. In some embodiments, the term "association identifier" is used for an identifier in a service operation between a first network element and a second network element, while the term "routing identifier" is used for an identifier in a NAS message sent over the N1 reference point between a terminal and the second network element.

[0249] In some embodiments, in a process related to LCS, an association identifier (or routing identifier) ​​is used between a first network element, a second network element, and a terminal to identify the first network element and the LCS session between the first network element and the terminal. For example, when the second network element receives a message and a routing identifier from the terminal, the second network element can map the routing identifier to the association identifier and send the message to the first network element identified by the association identifier.

[0250] In some embodiments, the network-initiated UPP-CM procedure includes:

[0251] The network initiates the establishment of a user plane connection:

[0252] The network sends a user plane connection establishment command message to the terminal;

[0253] The terminal sends a user plane connection establishment completion message to the network;

[0254] The network initiates user plane connection release:

[0255] The network sends a user plane connection release command message to the terminal;

[0256] The terminal sends a user plane connection release completion message to the network;

[0257] The UPP-CM process initiated by the terminal includes:

[0258] The terminal initiates user plane connection establishment:

[0259] The terminal sends a user plane connection establishment request to the network;

[0260] The network sends a user plane connection establishment response message or a user plane connection establishment command message to the terminal;

[0261] The terminal initiates the release of the user plane connection:

[0262] The terminal sends a user plane connection release request to the network;

[0263] The network sends a user plane connection release response message or a user plane connection release command message to the terminal;

[0264] The above UPP-CM message is included in the UPP-CMI container of the UL / DL NAS TRANSPORT message and is transmitted between the UE and LMF through the AMF.

[0265] FIG2 is an interactive diagram of a method for processing a user plane positioning connection according to an embodiment of the present disclosure. As shown in FIG2 , the present disclosure embodiment relates to a method for processing a user plane positioning connection, which is used in a communication system 100. The method includes:

[0266] Step S2101: The first network element 1021 sends a first identifier and a first message to the second network element 1022.

[0267] In some embodiments, the second network element 1022 receives the first identifier and the first message.

[0268] In some embodiments, the first message is a message related to establishing a user plane connection or a message related to releasing a user plane connection.

[0269] In some embodiments, the first message is a user plane connection establishment command message, a user plane connection establishment response message, a user plane connection release command message, or a user plane connection release response message.

[0270] In some embodiments, the first identifier is used to identify the first information, and the first information is at least one of the first network element, the user plane connection, or the positioning service session between the first network element and the terminal.

[0271] In some embodiments, the first identifier can be used only to identify the first information in the core network, and can also be used to identify the first information in the core network and the terminal. It should be understood that if the first identifier is used only to identify the first information in the core network, then if the second network element sends the first identifier to the terminal, the terminal cannot determine the first information identified by the first identifier based on the first identifier. Similarly, if the first identifier can be used to identify the first information in the core network and the terminal, then if the second network element sends the first identifier to the terminal, the terminal can determine the first information identified by the first identifier based on the first identifier.

[0272] In some embodiments, when the first identifier is used to identify the first network element, the first identifier can be the IP address of the first network element, an association identifier, etc. Since both the core network device and the terminal can determine the first network element based on the IP address of the first network element, if the first identifier is the IP address of the first network element, it indicates that the first identifier is used to identify the first network element in the core network and the terminal. However, the association identifier is only used to identify the first network element in the core network, so if the first identifier is an association identifier, it indicates that the first identifier is used to identify the first network element in the core network.

[0273] The first network element of the embodiment of the present disclosure further sends a first identifier for identifying the first information when sending the first message to the second network element, so that the second network element can forward the first message to the first network element related to the terminal and can help the terminal identify the first network element.

[0274] The UPP-CM process of the embodiment of the present disclosure includes establishing a user plane connection and releasing the user plane connection. Since the initiator of the UPP-CM process can be either a network or a terminal, the UPP-CM process of the embodiment of the present application can include four schemes. Step S2101 is described in detail below for different schemes.

[0275] Solution 1: Network initiates user plane connection

[0276] Step S2101 may include: the first network element determines to establish a user plane connection for user plane positioning, allocates a first identifier, and sends the first identifier and a first message to the second network element, where the first message is a user plane connection establishment command message.

[0277] That is, when the user plane connection is initiated by the network, the first identifier in step S2101 is allocated by the first network element.

[0278] In some embodiments, the first network element may call Namf_Communication_N1N2MessageTransfer to the second network element to transmit the user plane connection establishment command message and the first identifier.

[0279] Solution 2: The terminal initiates a user plane connection

[0280] Step S2101 may include:

[0281] Method 1) The terminal sends a user plane connection establishment request to the second network element, the second network element sends a user plane connection establishment request to the first network element, the first network element accepts the user plane connection establishment request, determines to establish a user plane connection for user plane positioning, the first network element assigns a first identifier, and sends the first identifier and a first message to the second network element. The first message is a user plane connection establishment command message or a user plane connection establishment corresponding message.

[0282] Method 2) The terminal sends a user plane connection establishment request to the second network element, the second network element allocates a first identifier, and sends a user plane connection establishment request and the first identifier to the first network element. The first network element accepts the user plane connection establishment request, determines to establish a user plane connection for user plane positioning, and sends the first identifier and the first message to the second network element. The first message is a user plane connection establishment command message or a user plane connection establishment corresponding message.

[0283] That is to say, when the user plane connection is initiated by the terminal, the first identifier can be allocated by the first network element or by the second network element, that is, the first identifier can be allocated by the first network element to establish a user plane connection for user plane positioning, or the first identifier is allocated by the second network element based on the user plane connection establishment request sent by the terminal.

[0284] In some embodiments, the terminal sends the user plane connection establishment request to the second network element specifically:

[0285] The terminal sets the payload container type of the UL NAS TRASPORT message to "UPP-CMI container" and includes the user plane connection establishment request in the payload container in the UL NAS TRASPORT message.

[0286] Solution 3: Network initiates user plane connection release

[0287] Step S2101 may include: the first network element determines to release the user plane connection, and sends a first identifier and a first message to the second network element, where the first message is a user plane connection release command.

[0288] It should be noted that user plane connection release and user plane connection establishment are two relatively independent schemes, that is, whether the network or the terminal initiates the user plane connection, the network can initiate the user plane connection release. Furthermore, in the user plane connection release scheme, the first identifier sent by the first network element to the second network element can be allocated by the first network element during the user plane connection establishment process, or can be allocated by the second network element during the user plane connection establishment process.

[0289] In some embodiments, the first network element may call Namf_Communication_N1N2MessageTransfer to the second network element to transmit the user plane connection release command message and the first identifier.

[0290] Solution 4: The terminal initiates the user plane connection release

[0291] Step S2101 may include: the terminal sends a user plane connection release request and a second identifier to the second network element; the second network element sends a user plane connection release request and a first identifier to the first network element; the first network element accepts the user plane connection release request, determines to release the user plane connection, and sends the first identifier and a first message to the second network element, where the first message is a user plane connection release response message or a user plane connection release command message.

[0292] In some embodiments, the second identifier is used to identify the first information in the terminal.

[0293] In this solution, the first identifier sent by the second network element to the first network element may be allocated by the first network element during the user plane connection establishment process, or may be allocated by the second network element during the user plane connection establishment process.

[0294] In some embodiments, the terminal sends the user plane connection release request and the second identifier to the second network element specifically:

[0295] The terminal sets the payload container type of the UL NAS TRASPORT message to "UPP-CMI container", includes the user plane connection release request in the payload container, includes the second identifier in the additional information in the UL NAS TRASPORT message, and sends a DL NAS TRASPORT message to the second network element.

[0296] Step S2102: The second network element 1022 sends a second identifier and a first message to the terminal 101.

[0297] In some embodiments, terminal 101 receives the second identifier and the first message.

[0298] In some embodiments, the second identifier is used to identify the first information in the terminal. According to the above embodiment, the first identifier in the embodiment of the present disclosure can be used to identify the first information in the core network, or can be used to identify the first information in the core network and the terminal. Therefore, depending on the first identifier, the second network element sends the second identifier and the first message to the terminal in two situations:

[0299] Case 1: The first identifier is used to identify the first information in the core network, the second network element maps the first identifier to a second identifier, the second identifier is used to identify the first information in the terminal, and the second identifier and the first message are sent to the terminal;

[0300] Case 2: The first identifier is used to identify the first information in the core network and the terminal. The second network element uses the first identifier as the second identifier and sends the second identifier and the first message to the terminal.

[0301] The UPP-CM process of the embodiment of the present disclosure includes establishing a user plane connection and releasing the user plane connection. Since the initiator of the UPP-CM process can be either a network or a terminal, the UPP-CM process of the embodiment of the present application can include four schemes. Step S2102 and the subsequent process of step S2102 are described in detail below for different schemes.

[0302] Solution 1: Network initiates user plane connection

[0303] When the second network element receives the first identifier and the user plane connection establishment command message sent by the first network element, the first identifier is used to identify the first information in the core network, and step S2102 is specifically:

[0304] The second network element maps the first identifier to a second identifier, where the second identifier is used to identify the first information in the terminal. The second network element sets the type of the payload container of the DL NAS TRASPORT message to "UPP-CMI container", includes the user plane connection establishment command message in the payload container, includes the second identifier in the additional information of the DL NAS TRASPORT message, and sends the DL NAS TRASPORT message to the terminal.

[0305] Further, after step S2102, the terminal establishes a user plane connection for user plane positioning, sends a second identifier and a user plane connection establishment completion message to the second network element, the second network element maps the second identifier to the first identifier, and sends a user plane connection establishment completion message and the first identifier to the first network element indicated by the first identifier.

[0306] In some embodiments, the terminal sends the second identifier and the user plane connection establishment completion message to the second network element specifically:

[0307] The terminal sets the payload container type of the UL NAS TRASPORT message to "UPP-CMI container", includes the user plane connection establishment complete message in the payload container, includes the second identifier in the additional information of the UL NAS TRASPORT message, and sends the UL NAS TRASPORT message to the second network element.

[0308] In some embodiments, the second network element sends a user plane connection establishment completion message and the first identifier to the first network element indicated by the first identifier, specifically:

[0309] The second network element calls a Namf_Communication_N1MessageNotify message to the first network element indicated by the first identifier, where the message includes a user plane connection establishment completion message and the first identifier.

[0310] When the second network element receives the first identifier and the user plane connection establishment command message sent by the first network element, where the first identifier is used to identify the first information in the core network and the terminal, step S2102 is specifically as follows:

[0311] The second network element uses the first identifier as the second identifier, sets the type of the payload container of the DL NAS TRASPORT message to "UPP-CMI container", includes the user plane connection establishment command message in the payload container, includes the second identifier in the additional information of the DL NAS TRASPORT message, and sends the DL NAS TRASPORT message to the terminal.

[0312] Further, after step S2102, the terminal establishes a user plane connection for user plane positioning, sends a second identifier and a user plane connection establishment completion message to the second network element, the second network element uses the second identifier as the first identifier, and sends a user plane connection establishment completion message and the first identifier to the first network element indicated by the first identifier.

[0313] In some embodiments, the terminal sends the second identifier and the user plane connection establishment completion message to the second network element specifically:

[0314] The terminal sets the payload container type of the UL NAS TRASPORT message to "UPP-CMI container", includes the user plane connection establishment complete message in the payload container, includes the second identifier in the additional information of the UL NAS TRASPORT message, and sends the UL NAS TRASPORT message to the second network element.

[0315] In some embodiments, the second network element sends a user plane connection establishment completion message and the first identifier to the first network element indicated by the first identifier, specifically:

[0316] The second network element calls a Namf_Communication_N1MessageNotify message to the first network element indicated by the first identifier, where the message includes a user plane connection establishment completion message and the first identifier.

[0317] Solution 2: The terminal initiates a user plane connection

[0318] When the second network element receives the first identifier and the user plane connection establishment command message (or the user plane connection establishment response message) sent by the first network element, the first identifier is used to identify the first information in the core network. Step S2102 is specifically as follows:

[0319] The second network element maps the first identifier to a second identifier, where the second identifier is used to identify the first information in the terminal, and sends the second identifier and a user plane connection establishment command message (or a user plane connection establishment response message) to the terminal.

[0320] When the second network element receives the first identifier and the user plane connection establishment command message (or the user plane connection establishment response message) sent by the first network element, the first identifier is used to identify the first information in the core network and the terminal. Step S2102 is specifically:

[0321] The second network element uses the first identifier as the second identifier, and sends the second identifier and a user plane connection establishment command message (or a user plane connection establishment response message) to the terminal.

[0322] Further, after step S2102, the terminal establishes a user plane connection with the first network element.

[0323] Solution 3: Network initiates user plane connection release

[0324] When the second network element receives the first identifier and the user plane connection release command message sent by the first network element, the first identifier is used to identify the first information in the core network, and step S2102 is specifically:

[0325] The second network element maps the first identifier to a second identifier, where the second identifier is used to identify the first information in the terminal. The second network element sets the type of the payload container of the DL NAS TRASPORT message to "UPP-CMI container", includes the user plane connection establishment command message in the payload container, includes the second identifier in the additional information of the DL NAS TRASPORT message, and sends the DL NAS TRASPORT message to the terminal.

[0326] Further, after step S2102, the terminal releases the user plane connection used for user plane positioning, sends a second identifier and a user plane connection release completion message to the second network element, the second network element maps the second identifier to the first identifier, and sends a user plane connection release completion message and the first identifier to the first network element indicated by the first identifier.

[0327] In some embodiments, the terminal sends the second identifier and the user plane connection release completion message to the second network element specifically:

[0328] The terminal sets the payload container type of the UL NAS TRASPORT message to "UPP-CMI container", includes the user plane connection release complete message in the payload container, includes the second identifier in the additional information of the UL NAS TRASPORT message, and sends the UL NAS TRASPORT message to the second network element.

[0329] In some embodiments, the second network element sends a user plane connection release completion message and the first identifier to the first network element indicated by the first identifier, specifically:

[0330] The second network element calls a Namf_Communication_N1MessageNotify message to the first network element indicated by the first identifier, where the message includes a user plane connection release completion message and the first identifier.

[0331] When the second network element receives the first identifier and the user plane connection release command message sent by the first network element, the first identifier is used to identify the first information in the core network and the terminal. Step S2102 is specifically:

[0332] The second network element uses the first identifier as the second identifier, sets the type of the payload container of the DL NAS TRASPORT message to "UPP-CMI container", includes the user plane connection release command message in the payload container, includes the second identifier in the additional information of the DL NAS TRASPORT message, and sends the DL NAS TRASPORT message to the terminal.

[0333] Further, after step S2102, the terminal releases the user plane connection used for user plane positioning, sends a second identifier and a user plane connection establishment completion message to the second network element, the second network element uses the second identifier as the first identifier, and sends a user plane connection release completion message and the first identifier to the first network element indicated by the first identifier.

[0334] In some embodiments, the terminal sends the second identifier and the user plane connection release completion message to the second network element specifically:

[0335] The terminal sets the payload container type of the UL NAS TRASPORT message to "UPP-CMI container", includes the user plane connection release complete message in the payload container, includes the second identifier in the additional information of the UL NAS TRASPORT message, and sends the UL NAS TRASPORT message to the second network element.

[0336] In some embodiments, the second network element sends a user plane connection release completion message and the first identifier to the first network element indicated by the first identifier, specifically:

[0337] The second network element calls a Namf_Communication_N1MessageNotify message to the first network element indicated by the first identifier, where the message includes a user plane connection release completion message and the first identifier.

[0338] Solution 4: The terminal initiates the user plane connection release

[0339] When the second network element receives the first identifier and the user plane connection release command message (or the user plane connection release response message) sent by the first network element, the first identifier is used to identify the first information in the core network. Step S2102 is specifically as follows:

[0340] The second network element maps the first identifier to a second identifier, where the second identifier is used to identify the first information in the terminal, and sends the second identifier and a user plane connection release command message (or a user plane connection release response message) to the terminal.

[0341] When the second network element receives the first identifier and the user plane connection release command message (or the user plane connection release response message) sent by the first network element, the first identifier is used to identify the first information in the core network and the terminal. Step S2102 is specifically:

[0342] The second network element uses the first identifier as the second identifier, and sends the second identifier and a user plane connection release command message (or a user plane connection release response message) to the terminal.

[0343] Further, after step S2102, the terminal releases the user plane connection with the first network element.

[0344] In some embodiments, the processing logic of the second network element may include:

[0345] For UPP-CMI container:

[0346] If the additional information (i.e., the second identifier) ​​included in the additional information IE is included in the UL NAS TRANSPORT message, the payload container type and the content of the UPP-CMI container are sent to the first network element associated with the second identifier included in the additional information IE of the UL NAS TRANSPORT message. Optionally, the second identifier of the additional information IE is converted into the first identifier, and the content of the UPP-CMI container and the first identifier are sent to the first network element associated with the second identifier included in the additional information IE of the UL NAS TRANSPORT message (for example, through a Namf_Communication_N1MessageNotify message).

[0347] If the additional information (i.e., the second identifier) ​​included in the additional information IE is not included in the UL NAS TRANSPORT, operations related to the content of the UPP-CMI container (e.g., first network element selection and / or first identifier allocation) will be performed, and the payload container type and the content of the UPP-CMI container will be sent to the selected first network element. Optionally, the second identifier of the additional information IE will be converted into the first identifier, and at least one of the payload container type, the content of the UPP-CMI container and the first identifier will be sent to the selected first network element (via the Nlmf_Location_UPConfig message).

[0348] The communication method involved in the embodiments of the present disclosure may include at least one of step S2101 and step S2102. For example, step S2101 may be implemented as an independent embodiment, step S2102 may be implemented as an independent embodiment, and steps S2101+S2102 may be implemented as independent embodiments, but are not limited thereto.

[0349] In some embodiments, step S2101 and step S2102 may be executed in an interchanged order or simultaneously.

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

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

[0352] FIG3A is a flow chart of a method for processing a user plane positioning connection according to an embodiment of the present disclosure. As shown in FIG3A , the embodiment of the present disclosure relates to a first network element, and the method includes:

[0353] S3101: Determine to establish a user plane connection for user plane positioning, allocate a first identifier, and send the first identifier and a first message to a second network element, where the first message is a user plane connection establishment command message.

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

[0355] S3102. Receive a first identifier and a user plane connection establishment completion message sent by the second network element.

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

[0357] In some embodiments, step S3101 and step S3102 may be executed in an interchanged order or simultaneously.

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

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

[0360] FIG3B is a flow chart of a method for processing a user plane positioning connection according to an embodiment of the present disclosure. As shown in FIG3B , the embodiment of the present disclosure relates to a first network element, and the method includes:

[0361] S3201: Determine to release the user plane connection, and send a first identifier and a first message to the second network element, where the first message is a user plane connection release command message.

[0362] The optional implementation of step S3201 can refer to step S2101 and step S2102 in Figure 2, the optional implementation of step S3101 and step S3102 in Figure 3A and other related parts in the embodiments involved in Figures 2 and 3A, which will not be repeated here.

[0363] S3202. Receive a first identifier and a user plane connection release completion message sent by the second network element.

[0364] The optional implementation of step S3202 can be found in steps S2101 and S2102 of FIG. 2 , the optional implementation of steps S3101 and S3102 of FIG. 3A , and other related parts in the embodiments involved in FIG. 2 and FIG. 3A , which will not be repeated here.

[0365] In some embodiments, step S3201 and step S3202 may be executed in an interchanged order or simultaneously.

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

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

[0368] FIG3C is a flow chart of a method for processing a user plane positioning connection according to an embodiment of the present disclosure. As shown in FIG3C , the embodiment of the present disclosure relates to a first network element, and the method includes:

[0369] S3301. Receive a user plane connection establishment request and a first identifier sent by a second network element.

[0370] The optional implementation of step S3301 can be found in steps S2101 and S2102 of Figure 2, the optional implementation of steps S3101 and S3102 of Figure 3A, steps S3201 and S3202 of Figure 3B, and other related parts in the embodiments involved in Figures 2, 3A, and 3B, which will not be repeated here.

[0371] S3302: Accept a user plane connection establishment request, determine to establish a user plane connection for user plane positioning, and send a first identifier and a first message to the second network element. The first message is a user plane connection establishment response message or a user plane connection establishment command message.

[0372] The optional implementation of step S3302 can be found in steps S2101 and S2102 of Figure 2, steps S3101 and S3102 of Figure 3A, and the optional implementation of steps S3201 and S3202 of Figure 3B, as well as other related parts in the embodiments involved in Figures 2, 3A and 3B, which will not be repeated here.

[0373] In some embodiments, step S3301 and step S3302 may be executed in an interchanged order or simultaneously.

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

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

[0376] FIG3D is a flow chart of a method for processing a user plane positioning connection according to an embodiment of the present disclosure. As shown in FIG3D , the embodiment of the present disclosure relates to a first network element, and the method includes:

[0377] S3401. Receive a user plane connection establishment request sent by a second network element.

[0378] The optional implementation of step S3401 can be found in steps S2101 and S2102 of Figure 2, the optional implementation of steps S3101 and S3102 of Figure 3A, steps S3201 and S3202 of Figure 3B, steps S3301 and S3302 of Figure 3C, and other related parts in the embodiments involved in Figures 2, 3A, 3B, and 3C, which will not be repeated here.

[0379] S3402. Accept a user plane connection establishment request, determine to establish a user plane connection for user plane positioning, allocate a first identifier, and send the first identifier and a first message to the second network element. The first message is a user plane connection establishment response message or a user plane connection establishment command message.

[0380] For the optional implementation of step S3402, please refer to the optional implementation of steps S2101 and S2102 in Figure 2, steps S3101 and S3102 in Figure 3A, steps S3201 and S3202 in Figure 3B, steps S3301 and S3302 in Figure 3C, and other related parts in the embodiments involved in Figures 2, 3A, 3B and 3C, which will not be repeated here.

[0381] In some embodiments, step S3401 and step S3402 may be executed in an interchanged order or simultaneously.

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

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

[0384] FIG3E is a flow chart of a method for processing a user plane positioning connection according to an embodiment of the present disclosure. As shown in FIG3E , the embodiment of the present disclosure relates to a first network element, and the method includes:

[0385] S3501. Receive a user plane connection release request and a first identifier sent by a second network element.

[0386] For the optional implementation of step S3501, please refer to step S2101 and step S2102 in Figure 2, the optional implementation of steps S3101 and step S3102 in Figure 3A, steps S3201 and step S3202 in Figure 3B, steps S3301 and step S3302 in Figure 3C, steps S3401 and step S3402 in Figure 3D, and other related parts in the embodiments involved in Figures 2, 3A, 3B, 3C and 3D, which will not be repeated here.

[0387] S3502: Accept the user plane connection release request, determine to release the user plane connection, and send a first identifier and a first message to the second network element. The first message is a user plane connection release response message or a user plane connection release command message.

[0388] For the optional implementation of step S3502, please refer to steps S2101 and S2102 in Figure 2, steps S3101 and S3102 in Figure 3A, steps S3201 and S3202 in Figure 3B, steps S3301 and S3302 in Figure 3C, and the optional implementation of steps S3401 and S3402 in Figure 3D, as well as other related parts in the embodiments involved in Figures 2, 3A, 3B, 3C and 3D, which will not be repeated here.

[0389] In some embodiments, step S3501 and step S3502 may be executed in an interchanged order or simultaneously.

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

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

[0392] FIG4A is a flow chart of a method for processing a user plane positioning connection according to an embodiment of the present disclosure. As shown in FIG4A , the embodiment of the present disclosure relates to a second network element, and the method includes:

[0393] S4101. Receive a first identifier and a first message sent by a first network element, where the first message is a user plane connection establishment command message.

[0394] Optional implementations of step S4101 can be found in other related parts of the embodiments involved in FIG. 2 and FIG. 3A to FIG. 3E , and will not be described in detail here.

[0395] S4102. Send a second identifier and a first message to the terminal.

[0396] Optional implementations of step S4102 can be found in other related parts of the embodiments involved in FIG. 2 and FIG. 3A to FIG. 3E , and will not be described in detail here.

[0397] S4103: Receive the second identifier and the user plane connection establishment completion message sent by the terminal.

[0398] Optional implementations of step S4103 may be found in other related parts of the embodiments involved in FIG. 2 and FIG. 3A to FIG. 3E , and will not be described in detail here.

[0399] S4104. Send a first identifier and a user plane connection establishment completion message to the first network element.

[0400] Optional implementations of step S4104 can be found in other related parts of the embodiments involved in FIG. 2 and FIG. 3A to FIG. 3E , and will not be described in detail here.

[0401] In some embodiments, step S4101 and step S4102 may be performed in an interchangeable order or simultaneously. Step S4103 and step S4104 may be performed in an interchangeable order or simultaneously.

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

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

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

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

[0406] FIG4B is a flow chart of a method for processing a user plane positioning connection according to an embodiment of the present disclosure. As shown in FIG4B , the embodiment of the present disclosure relates to a second network element, and the method includes:

[0407] S4201. Receive a first identifier and a first message sent by a first network element, where the first message is a user plane connection release command message.

[0408] Optional implementations of step S4201 can be found in other related parts of the embodiments involved in FIG. 2 , FIG. 3A to FIG. 3E , and FIG. 4A , and will not be described in detail here.

[0409] S4202: Send a second identifier and a first message to the terminal.

[0410] Optional implementations of step S4202 can be found in other related parts of the embodiments involved in FIG. 2 , FIG. 3A to FIG. 3E , and FIG. 4A , and will not be described in detail here.

[0411] S4203: Receive the second identifier and the user plane connection release completion message sent by the terminal.

[0412] Optional implementations of step S4203 may be found in other related parts of the embodiments involved in FIG. 2 , FIG. 3A to FIG. 3E , and FIG. 4A , and will not be described in detail here.

[0413] S4204: Send a first identifier and a user plane connection release completion message to the first network element.

[0414] Optional implementations of step S4204 can be found in other related parts of the embodiments involved in FIG. 2 , FIG. 3A to FIG. 3E , and FIG. 4A , and will not be described in detail here.

[0415] In some embodiments, step S4201 and step S4202 may be performed in an interchangeable order or simultaneously. Step S4203 and step S4204 may be performed in an interchangeable order or simultaneously.

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

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

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

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

[0420] FIG4C is a flow chart of a method for processing a user plane positioning connection according to an embodiment of the present disclosure. As shown in FIG4C , the embodiment of the present disclosure relates to a second network element, and the method includes:

[0421] S4301. Receive a user plane connection establishment request sent by a terminal.

[0422] Optional implementations of step S4301 can be found in other related parts of the embodiments involved in FIG. 2 , FIG. 3A to FIG. 3E , and FIG. 4A to FIG. 4B , and will not be described in detail here.

[0423] S4302: Allocate a first identifier, and send the first identifier and a user plane connection establishment request to the first network element.

[0424] Optional implementations of step S4302 can be found in other related parts of the embodiments involved in FIG. 2 , FIG. 3A to FIG. 3E , and FIG. 4A to FIG. 4B , and will not be described in detail here.

[0425] S4303: Receive a first message and a first identifier sent by a first network element, where the first message is a user plane connection establishment response message or a user plane connection establishment command message.

[0426] Optional implementations of step S4303 may be found in other related parts of the embodiments involved in FIG. 2 , FIG. 3A to FIG. 3E , and FIG. 4A to FIG. 4B , and will not be described in detail here.

[0427] S4304: Send the second identifier and the first message to the terminal.

[0428] Optional implementations of step S4304 can be found in other related parts of the embodiments involved in FIG. 2 , FIG. 3A to FIG. 3E , and FIG. 4A to FIG. 4B , and will not be described in detail here.

[0429] In some embodiments, step S4301 and step S4302 may be performed in an interchangeable order or simultaneously. Step S4303 and step S4304 may be performed in an interchangeable order or simultaneously.

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

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

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

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

[0434] FIG4D is a flow chart of a method for processing a user plane positioning connection according to an embodiment of the present disclosure. As shown in FIG4D , the embodiment of the present disclosure relates to a second network element, and the method includes:

[0435] S4401. Receive a user plane connection establishment request sent by a terminal.

[0436] Optional implementations of step S4401 can be found in other related parts of the embodiments involved in FIG. 2 , FIG. 3A to FIG. 3E , and FIG. 4A to FIG. 4C , and will not be described in detail here.

[0437] S4402. Send a user plane connection establishment request to the first network element.

[0438] Optional implementations of step S4402 can be found in other related parts of the embodiments involved in FIG. 2 , FIG. 3A to FIG. 3E , and FIG. 4A to FIG. 4C , and will not be described in detail here.

[0439] S4403. Receive a first message and a first identifier sent by a first network element, where the first message is a user plane connection establishment response message or a user plane connection establishment command message.

[0440] Optional implementation of step S4403 can refer to Figure 2, Figure 3A ~ Figure 3E, Figure 4A ~ Figure 4C involved in the embodiment of other related parts, not repeated here.

[0441] S4404. Send the second identifier and the first message to the terminal.

[0442] Optional implementations of step S4404 may be found in other related parts of the embodiments involved in FIG. 2 , FIG. 3A to FIG. 3E , and FIG. 4A to FIG. 4C , and will not be described in detail here.

[0443] In some embodiments, step S4401 and step S4402 may be performed in an interchangeable order or simultaneously. Step S4403 and step S4404 may be performed in an interchangeable order or simultaneously.

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

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

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

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

[0448] FIG4E is a flow chart of a method for processing a user plane positioning connection according to an embodiment of the present disclosure. As shown in FIG4E , the embodiment of the present disclosure relates to a second network element, and the method includes:

[0449] S4501. Receive a user plane connection release request and a second identifier sent by a terminal.

[0450] Optional implementations of step S4501 can be found in other related parts of the embodiments involved in FIG. 2 , FIG. 3A to FIG. 3E , and FIG. 4A to FIG. 4D , and will not be described in detail here.

[0451] S4502. Send a user plane connection release request and a first identifier to the first network element.

[0452] Optional implementations of step S4502 can be found in other related parts of the embodiments involved in FIG. 2 , FIG. 3A to FIG. 3E , and FIG. 4A to FIG. 4D , and will not be described in detail here.

[0453] S4503. Receive a first identifier and a first message sent by a first network element, where the first message is a user plane connection release response message or a user plane connection release command message.

[0454] Optional implementations of step S4503 may be found in other related parts of the embodiments involved in FIG. 2 , FIG. 3A to FIG. 3E , and FIG. 4A to FIG. 4D , and will not be described in detail here.

[0455] S4504. Send the second identifier and the first message to the terminal.

[0456] Optional implementations of step S4504 can be found in other related parts of the embodiments involved in FIG. 2 , FIG. 3A to FIG. 3E , and FIG. 4A to FIG. 4D , and will not be described in detail here.

[0457] In some embodiments, step S4501 and step S4502 may be performed in an interchangeable order or simultaneously. Step S4503 and step S4504 may be performed in an interchangeable order or simultaneously.

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

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

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

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

[0462] FIG5A is a flow chart of a method for processing a user plane positioning connection according to an embodiment of the present disclosure. As shown in FIG5A , the embodiment of the present disclosure relates to a terminal, and the method includes:

[0463] S5101. Receive a second identifier and a first message sent by a second network element, where the first message is a user plane connection establishment command message.

[0464] Optional implementations of step S5101 can be found in other related parts of the embodiments involved in FIG. 2 , FIG. 3A to FIG. 3E , and FIG. 4A to FIG. 4E , and will not be described in detail here.

[0465] S5102: Establish a user plane connection.

[0466] Optional implementations of step S5102 can be found in other related parts of the embodiments involved in FIG. 2 , FIG. 3A to FIG. 3E , and FIG. 4A to FIG. 4E , and will not be described in detail here.

[0467] S5103: Send a second identifier and a user plane connection establishment completion message to the second network element.

[0468] Optional implementations of step S5103 may be found in other related parts of the embodiments involved in FIG. 2 , FIG. 3A to FIG. 3E , and FIG. 4A to FIG. 4E , and will not be described in detail here.

[0469] In some embodiments, step S5101 and step S5102 may be performed in an exchanged order or simultaneously. Step S5102 and step S5103 may be performed in an exchanged order or simultaneously.

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

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

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

[0473] FIG5B is a flow chart of a method for processing a user plane positioning connection according to an embodiment of the present disclosure. As shown in FIG5B , the embodiment of the present disclosure relates to a terminal, and the method includes:

[0474] S5201. Receive a second identifier and a first message sent by a second network element, where the first message is a user plane connection release command message.

[0475] Optional implementations of step S5201 can be found in other related parts of the embodiments involved in FIG. 2 , FIG. 3A to FIG. 3E , FIG. 4A to FIG. 4E , and FIG. 5A , and will not be described in detail here.

[0476] S5202. Release the user plane connection.

[0477] Optional implementations of step S5202 may be found in other related parts of the embodiments involved in FIG. 2 , FIG. 3A to FIG. 3E , FIG. 4A to FIG. 4E , and FIG. 5A , and will not be described in detail here.

[0478] S5203: Send a second identifier and a user plane connection release completion message to the second network element.

[0479] Optional implementations of step S5203 may be found in other related parts of the embodiments involved in FIG. 2 , FIG. 3A to FIG. 3E , FIG. 4A to FIG. 4E , and FIG. 5A , and will not be described in detail here.

[0480] In some embodiments, step S5201 and step S5202 may be performed in an interchangeable order or simultaneously. Step S5202 and step S5203 may be performed in an interchangeable order or simultaneously.

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

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

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

[0484] FIG5C is a flow chart of a method for processing a user plane positioning connection according to an embodiment of the present disclosure. As shown in FIG5C , the embodiment of the present disclosure relates to a terminal, and the method includes:

[0485] S5301. Send a user plane connection establishment request to the second network element.

[0486] Optional implementations of step S5301 may be found in other related parts of the embodiments involved in FIG. 2 , FIG. 3A to FIG. 3E , FIG. 4A to FIG. 4E , FIG. 5A and FIG. 5B , and will not be described in detail here.

[0487] S5302: Receive a first message and a second identifier sent by a second network element, where the first message is a user plane connection establishment command message or a user plane connection establishment response message.

[0488] The optional implementation of step S5302 can refer to other related parts of the embodiments involved in Figures 2, 3A to 3E, 4A to 4E, 5A and 5B, and will not be repeated here.

[0489] S5303. Establish a user plane connection with the first network element.

[0490] Optional implementations of step S5303 may be found in other related parts of the embodiments involved in FIG. 2 , FIG. 3A to FIG. 3E , FIG. 4A to FIG. 4E , FIG. 5A and FIG. 5B , and will not be described in detail here.

[0491] In some embodiments, step S5301 and step S5302 may be performed in an interchangeable order or simultaneously. Step S5302 and step S5303 may be performed in an interchangeable order or simultaneously.

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

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

[0494] In some embodiments, step S5303 is optional, and one or more of these steps may be omitted or replaced in different embodiments. FIG5D is a flow chart of a method for processing a user plane positioning connection according to an embodiment of the present disclosure. As shown in FIG5D , the present disclosure embodiment relates to a terminal, and the method includes:

[0495] S5401. Send a user plane connection release request to the second network element.

[0496] Optional implementations of step S5401 can be found in other related parts of the embodiments involved in FIG. 2 , FIG. 3A to FIG. 3E , FIG. 4A to FIG. 4E , and FIG. 5A to FIG. 5C , and will not be described in detail here.

[0497] S5402: Receive a first message and a second identifier sent by a second network element, where the first message is a user plane connection release command message or a user plane connection release response message.

[0498] Optional implementations of step S5402 may be found in other related parts of the embodiments involved in FIG. 2 , FIG. 3A to FIG. 3E , FIG. 4A to FIG. 4E , and FIG. 5A to FIG. 5C , and will not be described in detail here.

[0499] S5403. Release the user plane connection with the first network element.

[0500] Optional implementations of step S5403 may be found in other related parts of the embodiments involved in FIG. 2 , FIG. 3A to FIG. 3E , FIG. 4A to FIG. 4E , and FIG. 5A to FIG. 5C , and will not be described in detail here.

[0501] In some embodiments, step S5401 and step S5402 may be performed in an interchangeable order or simultaneously. Step S5402 and step S5403 may be performed in an interchangeable order or simultaneously.

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

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

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

[0505] FIG6A is an interactive schematic diagram of a method for processing a user plane positioning connection according to an embodiment of the present disclosure, as shown in the figure, including:

[0506] S6101: The first network element determines to establish a user plane connection for user plane positioning, and no user plane connection is established, allocates a first identifier, and calls Namf_Communication_N1N2MessageTransfer to the second network element to transmit a user plane connection establishment command message and the first identifier;

[0507] S6102. The second network element determines the second identifier based on the first identifier, sets the type of the payload container of the DL NAS TRASPORT message to "UPP-CMI container", includes the user plane connection establishment command message in the payload container, includes the second identifier in the additional information of the DL NAS TRASPORT message, and sends the DL NAS TRASPORT message to the terminal;

[0508] S6103: The terminal establishes a user plane connection.

[0509] S6104. The terminal sets the payload container type of the UL NAS TRASPORT message to "UPP-CMI container", includes the user plane connection establishment complete message in the payload container, includes the second identifier in the additional information of the UL NAS TRASPORT message, and sends the UL NAS TRASPORT message to the second network element;

[0510] S6105. The second network element determines the first identifier according to the second identifier, and calls a Namf_Communication_N1MessageNotify message to the first network element indicated by the first identifier. The message includes a user plane connection establishment completion message and the first identifier.

[0511] FIG6B is an interactive schematic diagram of a method for processing a user plane positioning connection according to an embodiment of the present disclosure, as shown in the figure, including:

[0512] S6201. The first network element determines to release the user plane connection and calls Namf_Communication_N1N2MessageTransfer to the second network element to transmit the user plane connection release command message and the first identifier.

[0513] S6202. The second network element determines the second identifier based on the first identifier, sets the type of the payload container of the DL NAS TRASPORT message to "UPP-CMI container", includes the user plane connection release command message in the payload container, includes the second identifier in the additional information of the DL NAS TRASPORT message, and sends the DL NAS TRASPORT message to the terminal;

[0514] S6203: The terminal releases the user plane connection.

[0515] S6204. The terminal sets the payload container type of the UL NAS TRASPORT message to "UPP-CMI container", includes the user plane connection release complete message in the payload container, includes the second identifier in the additional information of the UL NAS TRASPORT message, and sends the UL NAS TRASPORT message to the second network element;

[0516] S6205. The second network element determines the first identifier according to the second identifier, and calls a Namf_Communication_N1MessageNotify message to the first network element indicated by the first identifier. The message includes a user plane connection release completion message and the first identifier.

[0517] FIG6C is an interactive diagram of a method for processing a user plane positioning connection according to an embodiment of the present disclosure, as shown in the figure, including:

[0518] S6301. The terminal sets the payload container type of the UL NAS TRASPORT message to "UPP-CMI container", includes a user plane connection establishment request in the payload container of the UL NAS TRASPORT message, and sends the UL NAS TRASPORT message to the second network element.

[0519] S6302: The second network element selects a first network element capable of user plane positioning and assigns a first identifier. The second network element calls a Namf_Communication_N1MessageNotify message to the selected first network element, where the message includes a user plane connection establishment request message and the first identifier. S6303: The first network element accepts the user plane connection establishment request, determines to establish a user plane connection for user plane positioning, and calls a Namf_Communication_N1N2MessageTransfer message to the second network element to send the first identifier and a first message, where the first message is a user plane connection establishment response message or a user plane connection establishment command message.

[0520] S6304. The second network element determines the second identifier based on the first identifier, sets the payload container type of the DL NAS TRASPORT message to "UPP-CMI container", includes the user plane connection establishment response message or the user plane connection establishment command in the payload container, includes the second identifier in the additional information of the DL NAS TRASPORT message, and sends the DL NAS TRASPORT message to the terminal;

[0521] S6305. The terminal establishes a user plane connection with the first network element.

[0522] It should be noted that, in some embodiments, step S6302 may also be: the second network element selects a first network element capable of user plane positioning, and calls the Namf_Communication_N1MessageNotify message to the selected first network element, which includes a user plane connection establishment request message. Further, step S6302 is: the first network element accepts the user plane connection establishment request, determines to establish a user plane connection for user plane positioning, allocates a first identifier, and calls the Namf_Communication_N1N2MessageTransfer message to transmit the first identifier and the first message, where the first message is a user plane connection establishment response message or a user plane connection establishment command message.

[0523] FIG6D is an interactive schematic diagram of a method for processing a user plane positioning connection according to an embodiment of the present disclosure, as shown in the figure, including:

[0524] S6401. The terminal requests to release the user plane connection. The terminal sets the payload container type of the UL NAS TRASPORT message to "UPP-CMI container", includes the user plane connection release request in the payload container, includes the second identifier in the additional information in the UL NAS TRASPORT message, and sends the UL NAS TRASPORT message to the second network element.

[0525] S6402: The second network element determines the first identifier according to the second identifier, and the second network element calls a Namf_Communication_N1MessageNotify message to indicate the first network element with the first identifier, where the message includes a user plane connection release request message and the first identifier;

[0526] S6403: The first network element receives the released user plane connection and calls Namf_Communication_N1N2MessageTransfer to the second network element to transmit the user plane connection release response message or the user plane connection release command message and the first identifier;

[0527] S6404. The second network element determines the second identifier according to the first identifier, sets the payload container type of the DL NAS TRASPORT message to "UPP-CMI container", includes the user plane connection release response message or the user plane connection release command message in the payload container, and includes the second identifier in the additional information of the DL NAS TRASPORT message;

[0528] S6405. The terminal releases the user plane connection with the first network element.

[0529] 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., an access network device, a core network function node, a core network device, etc.) in any of the above methods.

[0530] 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 realized 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.

[0531] 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.

[0532] Figure 7A is a schematic diagram of the structure of a first network element proposed in an embodiment of the present disclosure. As shown in Figure 7A, first network element 7100 may include a transceiver module 7101. In some embodiments, the transceiver module is configured to send a first identifier and a first message to a second network element. Optionally, the transceiver module is configured to perform the communication steps, such as sending and / or receiving, performed by first network element 1021 in any of the above methods, such as steps S2101 and S2102, which are not further described here.

[0533] Figure 7B is a schematic diagram of the structure of the second network element proposed in an embodiment of the present disclosure. As shown in Figure 7B, the second network element 7200 may include a transceiver module 7201. In some embodiments, the transceiver module is configured to receive a first identifier and a first message sent by the first network element. Optionally, the transceiver module is configured to execute the communication steps, such as sending and / or receiving, performed by the second network element 1022 in any of the above methods, such as steps S2101 and S2102, which are not further described here.

[0534] Figure 7C is a structural diagram of the terminal proposed in an embodiment of the present disclosure. As shown in Figure 7C, the terminal 7300 may include a transceiver module 7301. In some embodiments, the transceiver module receives the second identifier and the first message sent by the second network element; optionally, the above-mentioned transceiver module is used to execute the communication steps such as sending and / or receiving performed by the terminal in any of the above methods, such as step S2101 and step S2102, which are not repeated here.

[0535] 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.

[0536] Figure 8A is a schematic diagram of the structure of a communication device 8100 proposed in an embodiment of the present disclosure. The communication device 8100 can be a network device (such as an access network device, a core network device, etc.), a first network element, a second network element, a terminal, a chip, a chip system, or a processor that supports a network device to implement any of the above methods, a chip, a chip system, or a processor that supports a first network element to implement any of the above methods, a chip, a chip system, or a processor that supports a second network element to implement any of the above methods, or a chip, a chip system, or a processor that supports a terminal to implement any of the above methods. The communication device 8100 can be used to implement the method described in the above method embodiment. For details, please refer to the description of the above method embodiment.

[0537] 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 the communication protocol 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. Optionally, the communication device 8100 is used to perform any of the above methods. Optionally, one or more processors 8101 are used to call instructions to enable the communication device 8100 to perform any of the above methods.

[0538] In some embodiments, the communication device 8100 further includes one or more transceivers 8102. When the communication device 8100 includes one or more transceivers 8102, the transceiver 8102 performs at least one of the communication steps of sending and / or receiving in the above method (e.g., step S2101 and step S2102, but not limited thereto). In an optional embodiment, the transceiver may include a receiver and / or a transmitter, and the receiver and transmitter may be separate or integrated. Optionally, the terms transceiver, transceiver unit, transceiver, transceiver circuit, interface circuit, and interface may be interchangeable, the terms transmitter, transmitting unit, transmitter, and transmitting circuit may be interchangeable, and the terms receiver, receiving unit, receiver, and receiving circuit may be interchangeable.

[0539] In some embodiments, the communication device 8100 further includes one or more memories 8103 for storing data. Alternatively, all or part of the memories 8103 may be located outside the communication device 8100. In alternative embodiments, the communication device 8100 may include one or more interface circuits 8104. Optionally, the interface circuits 8104 are connected to the memory 8102 and may be configured to receive data from the memory 8102 or other devices, or to send data to the memory 8102 or other devices. For example, the interface circuits 8104 may read data stored in the memory 8102 and send the data to the processor 8101.

[0540] The communication device 8100 described in the above embodiments 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.

[0541] FIG8B is a schematic diagram of the structure of a chip 8200 according to an embodiment of the present disclosure. If the communication device 8100 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.

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

[0543] In some embodiments, chip 8200 further includes one or more interface circuits 8202. Terms such as interface circuit, interface, and transceiver pins may be used interchangeably. In some embodiments, chip 8200 further includes one or more memories 8203 for storing data. Alternatively, all or part of memory 8203 may be located external to chip 8200. Optionally, interface circuit 8202 is connected to memory 8203 and may be used to receive data from memory 8203 or other devices, or may be used to send data to memory 8203 or other devices. For example, interface circuit 8202 may read data stored in memory 8203 and send the data to processor 8201.

[0544] In some embodiments, the interface circuit 8202 performs at least one of the communication steps (e.g., step S2101 and step S2102, but not limited thereto) of sending and / or receiving in the above method. For example, the interface circuit 8202 performing the communication steps (e.g., sending and / or receiving) in the above method means that the interface circuit 8202 performs data exchange between the processor 8201, the chip 8200, the memory 8203, or the transceiver device.

[0545] 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.

[0546] 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.

[0547] 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.

Claims

1. A method for processing user plane positioning connection, characterized in that, Performed by a first network element, the method includes: Sending a first identifier and a first message to a second network element; Wherein, the first message is a message related to establishing a user plane connection or a message related to releasing a user plane connection; The first identifier is used to identify first information, and the first information is at least one of the following: the first network element, the user plane connection, the positioning service session between the first network element and the terminal.

2. The method according to claim 1, wherein The first identifier is allocated by the first network element for establishing a user plane connection for user plane positioning, or The first identifier is allocated by the second network element according to a user plane connection establishment request sent by the terminal.

3. The method according to claim 1 or 2, characterized in that, The first message related to establishing a user plane connection is at least one of the following: User plane connection establishment command message; User plane connection establishment response message.

4. The method according to claim 3, characterized in that, The sending the first identifier and the first message to the second network element includes: Determining to establish a user plane connection for user plane positioning and allocating the first identifier; Sending the first identifier and the first message to the second network element, and the first message is a user plane connection establishment command message.

5. The method according to claim 3, wherein The sending the first identifier and the first message to the second network element includes: Receiving a user plane connection establishment request and the first identifier sent by the second network element, and the first identifier is allocated by the second network element according to the user plane connection establishment request sent by the terminal; Accepting the user plane connection establishment request, determining to establish a user plane connection for user plane positioning, and sending the first identifier and the first message to the second network element, and the first message is the user plane connection establishment response message or the user plane connection establishment command message.

6. The method according to claim 3, characterized in that The sending the first identifier and the first message to the second network element includes: Receiving a user plane connection establishment request sent by the second network element, and the user plane connection establishment request is sent by the terminal to the second network element; Accepting the user plane connection establishment request, determining to establish a user plane connection for user plane positioning, and allocating the first identifier; Sending the first identifier and the first message to the second network element, and the first message is the user plane connection establishment response message or the user plane connection establishment command message.

7. The method according to claim 4, characterized in that, After the sending the first identifier and the first message to the second network element, it further includes: Receiving the first identifier and a user plane connection establishment completion message sent by the second network element.

8. The method according to claim 1 or 2, characterized in that, The first message related to releasing a user plane connection is at least one of the following: User plane connection release command message; User plane connection release response message.

9. The method according to claim 8, wherein The sending the first identifier and the first message to the second network element includes: Determining to release the user plane connection and sending the first identifier and the first message to the second network element, and the first message is the user plane connection release command message.

10. The method according to claim 8, characterized in that, The sending the first identifier and the first message to the second network element includes: Receiving a user plane connection release request and the first identifier sent by the second network element; Accepting the user plane connection release request, determining to release the user plane connection, and sending the first identifier to the second network element and a first message, where the first message is the user plane connection release response message or the user plane connection release command message.

11. The method according to claim 9, wherein After sending the first identifier and the first message to the second network element, the method further includes: Receiving the first identifier and the user plane connection release completion message sent by the second network element.

12. A processing method for user plane positioning connection, characterized in that, Executed by the second network element, the method includes: Receiving the first identifier and the first message sent by the first network element; where the first message is a message related to establishing a user plane connection or a message related to releasing a user plane connection; The first identifier is used to identify the first information, and the first information is at least one of the following: the first network element, the user plane connection, and the positioning service session between the first network element and the terminal.

13. The method according to claim 12, wherein the first identifier is allocated by the first network element for establishing a user plane connection for user plane positioning, or the first identifier is allocated by the second network element according to the user plane connection establishment request received from the terminal.

14. The method according to claim 12 or 13, characterized in that, The first message related to establishing a user plane connection is at least one of the following: User plane connection establishment command message; User plane connection establishment response message.

15. The method according to claim 14, wherein The first message is a user plane connection establishment command message; The first identifier and the first message are sent by the first network element for establishing a user plane connection for user plane positioning.

16. The method according to claim 15, wherein The first identifier is used to identify the first information in the core network; After receiving the first identifier and the first message sent by the first network element, the method further includes: Mapping the first identifier to a second identifier, and sending the second identifier and the first message to the terminal, where the second identifier is used to identify the first information in the terminal; Receiving the second identifier and the user plane connection establishment completion message sent by the terminal; Mapping the second identifier to the first identifier, and sending the first identifier and the user plane connection establishment completion message to the first network element indicated by the first identifier.

17. The method according to claim 15, wherein The first identifier is used to identify the first information in the core network and the terminal; After receiving the first identifier and the first message sent by the first network element, the method further includes: Using the first identifier as the second identifier, and sending the second identifier and the first message to the terminal; Receiving the second identifier and the user plane connection establishment completion message sent by the terminal; Using the second identifier as the first identifier, and sending the first identifier and the user plane connection establishment completion message to the first network element indicated by the first identifier.

18. The method according to claim 14, characterized in that, Receiving the first identifier and the first message sent by the first network element includes: Receiving the user plane connection establishment request sent by the terminal; Sending the user plane connection establishment request to the first network element; Receiving the first identifier and the first message sent by the first network element, where the first message is a user plane connection establishment response or a user plane connection establishment command, and the first identifier is allocated by the first network element for establishing a user plane connection for user plane positioning.

19. The method according to claim 14, wherein Receiving the first identifier and the first message sent by the first network element includes: Receiving the user plane connection establishment request sent by the terminal; Allocating the first identifier; Send the user plane connection establishment request and the first identifier to the first network element; Receive the first identifier and the first message sent by the first network element, where the first message is a user plane connection establishment response or a user plane connection establishment command.

20. The method according to claim 18 or 19, characterized in that, The first identifier is used to identify the first information in the core network; After receiving the first identifier and the first message sent by the first network element, it further includes: Map the first identifier to a second identifier, and send the second identifier and the first message to the terminal, where the second identifier is used to Identify the first information in the terminal.

21. The method according to claim 18 or 19, characterized in that, The first identifier is used to identify the first information in the core network and the terminal; After receiving the first identifier and the first message sent by the first network element, it further includes: Use the first identifier as the second identifier, and send the second identifier and the first message to the terminal.

22. The method according to claim 12 or 13, characterized in that, The messages related to releasing the user plane connection include at least one of the following: User plane connection release command message; User plane connection release response message.

23. The method according to claim 22, wherein The first message is a user plane connection release command message; The first identifier and the first message are sent after the first network element determines to release the user plane connection.

24. The method according to claim 23, wherein The first identifier is used to identify the first information in the core network; After receiving the first identifier and the first message sent by the first network element, it further includes: Map the first identifier to a second identifier, and send the second identifier and the first message to the terminal, where the second identifier is used to identify the first information in the terminal; Receive the second identifier and the user plane connection release completion message sent by the terminal; Map the second identifier to the first identifier, and send the first identifier and the user plane connection release completion message to the first network element indicated by the first identifier.

25. The method according to claim 23, wherein The first identifier is used to identify the first information in the core network and the terminal; After receiving the first identifier and the first message sent by the first network element, it further includes: Use the first identifier as the second identifier, and send the second identifier and the first message to the terminal; Receive the second identifier and the user plane connection release completion message sent by the terminal; Use the second identifier as the first identifier, and send the first identifier and the user plane connection release completion message to the first network element indicated by the first identifier.

26. The method according to claim 22, wherein Receiving the first identifier and the first message sent by the first network element includes: Receive the user plane connection release request and the second identifier sent by the terminal, where the second identifier is used to identify the first information in the terminal; Map the second identifier to the first identifier, where the first identifier is used to identify the first information in the core network, and send the user plane connection release request and the first identifier to the first network element indicated by the first identifier; Receive the first identifier and the first message sent by the first network element, where the first message is a user plane connection release response or a user plane connection release command.

27. The method according to claim 22, wherein Receiving the first identifier and the first message sent by the first network element includes: Receive the user plane connection release request and the second identifier sent by the terminal, where the second identifier is used to identify the first information in the core network and the terminal; Use the second identifier as the first identifier, and send the user plane connection release request and the first identifier to the first network element indicated by the first identifier; Receive the first identifier and a first message sent by the first network element, where the first message is a user plane connection release response message or a user plane connection release command message.

28. The method according to claim 26, wherein After receiving the first identifier and the first message sent by the first network element, it further includes: Map the first identifier to a second identifier; Send the second identifier and the first message to the terminal.

29. The method according to claim 27, wherein After receiving the first identifier and the first message sent by the first network element, it further includes: Use the first identifier as the second identifier; Send the second identifier and the first message to the terminal.

30. A user plane positioning connection method, characterized in that, Executed by the terminal, the method includes: Receive the second identifier and the first message sent by the second network element; Wherein, the first message is a message related to establishing a user plane connection or a message related to releasing a user plane connection; The second identifier is determined according to the first identifier sent by the first network element, the first identifier is used to identify first information, and the second identifier is used to identify the first information in the terminal; The first information is at least one of the following: the first network element, the user plane connection, and the positioning service session between the first network element and the terminal.

31. The method according to claim 30, wherein: The first identifier is allocated by the first network element for establishing a user plane connection for user plane positioning, or The first identifier is allocated by the second network element according to the user plane connection establishment request received from the terminal.

32. The method according to claim 30 or 31, characterized in that, When the first message is a user plane connection establishment command message, the method further includes: Establish a user plane connection for user plane positioning; Send the second identifier and a user plane connection establishment completion message to the second network element.

33. The method according to claim 30 or 31, characterized in that, When the first message is a user plane connection release command message, the method further includes: Release the user plane connection for user plane positioning; Send the second identifier and a user plane connection release completion message to the second network element.

34. The method according to claim 30 or 31, characterized in that, The first message is a user plane connection establishment command or a user plane connection establishment response; Before receiving the second identifier and the first message sent by the second network element, it further includes: Send a user plane connection establishment request to the second network element.

35. The method according to claim 30 or 31, characterized in that, The first message is a user plane connection release command or a user plane connection release response; Before receiving the second identifier and the first message sent by the second network element, it further includes: Send a user plane connection release request to the second network element.

36. A first network element, characterized in that, It includes: A transceiver module, configured to send a first identifier and a first message to the second network element; Wherein, the first message is a message related to establishing a user plane connection or a message related to releasing a user plane connection; The first identifier is used to identify first information, and the first information is at least one of the following: the first network element, the user plane connection, and the positioning service session between the first network element and the terminal.

37. A second network element, characterized in that, It includes: A transceiver module, configured to receive the first identifier and the first message sent by the first network element; Wherein, the first message is a message related to establishing a user plane connection or a message related to releasing a user plane connection; The first identifier is used to identify first information, and the first information is at least one of the following: the first network element, the user plane connection, and the positioning service session between the first network element and the terminal.

38. A terminal, characterized in that, Comprising: a transceiver module, configured to receive a second identifier and a first message sent by a second network element; wherein the first message is a message related to establishing a user plane connection or a message related to releasing a user plane connection; the second identifier is determined according to a first identifier sent by a first network element, the first identifier is used to identify first information, and the second identifier is used to identify the first information in a terminal; the first information is at least one of the following: the first network element, the user plane connection, and the positioning service session between the first network element and the terminal.

39. A communication system, characterized in that, Comprising a first network element, a second network element, and a terminal, wherein the first network element is configured to implement the processing method of the user plane positioning connection according to any one of claims 1-11, the second network element is configured to implement the processing method of the user plane positioning connection according to any one of claims 12-29, and the terminal is configured to implement the processing method of the user plane positioning connection according to any one of claims 30-35.

40. A storage medium storing instructions, characterized in that, When the instruction runs on a communication device, the communication device is caused to execute the processing method of the user plane positioning connection according to any one of claims 1-11, 12-29, 30-35.

Images