Communication methods, devices, system and storage medium

Abstract

The embodiments of the present disclosure relate to the technical field of communications. Disclosed are communication methods, apparatuses and a computer-readable storage medium. A communication method comprises: a first terminal sends first information to a first network element, the first information comprising a routing ID, and the first information being used for instructing to establish a first user plane connection with a second network element corresponding to the first routing ID, or being used for indicating that the establishment of a first user plane connection with a second network element corresponding to the first routing ID is completed. In the embodiments of the present disclosure, the first terminal sends to the first network element the first information comprising the routing ID, so as to instruct to establish the user plane connection with the second network element identified by the routing ID, or so as to indicate that the establishment of the user plane connection with the second network element identified by the routing ID is completed, such that the first network element does not need to execute a selection process of the second network element, and can directly forward information to the second network element identified by the routing ID, thus optimizing and improving the establishment process of user plane connections.

Description

Communication method, device, system and storage medium Technical Field

[0001] The present disclosure relates to the field of communication technology, and in particular to a communication method, device, system, and storage medium. Background Art

[0002] Terminals can be located using either user plane positioning or control plane positioning. User plane positioning enables communication systems to have more efficient communication loads, allowing a single session to handle multiple transactions and supporting multiple positioning methods.

[0003] Summary of the Invention

[0004] Embodiments of the present disclosure provide a communication method, device, system, and storage medium.

[0005] According to a first aspect of the present disclosure, a communication method is provided, which is applied to a first terminal. The method includes:

[0006] Sending first information to the first network element, where the first information includes a first routing identifier ID;

[0007] The first information is used to instruct the second network element corresponding to the first routing ID to establish a first user plane connection, or to indicate that the first user plane connection between the second network elements corresponding to the first routing ID is established.

[0008] A second aspect of the embodiments of the present disclosure provides a communication method, applied to a first network element, the method including:

[0009] receiving first information sent by a first terminal, where the first information includes a first routing identifier ID;

[0010] Sending second information to a second network element corresponding to the first routing ID, where the second information includes a first correlation ID corresponding to the first routing ID;

[0011] The first information is used to indicate that a first user plane connection is established with the second network element, or is used to indicate that establishment of the first user plane connection with the second network element is completed.

[0012] According to a third aspect of the present disclosure, a communication method is provided, which is applied to a second network element. The method includes:

[0013] receiving second information sent by the first network element, where the second information includes a first correlation ID corresponding to the first routing ID;

[0014] The first information is used to instruct the second network element corresponding to the first routing ID to establish a first user plane connection, or to indicate that the first user plane connection between the second network elements corresponding to the first routing ID is established.

[0015] According to a fourth aspect of the present disclosure, a terminal is provided, including:

[0016] A first transceiver module is configured to send first information to a first network element, where the first information includes a first routing identifier ID;

[0017] The first information is used to instruct the second network element corresponding to the first routing ID to establish a first user plane connection, or to indicate that the first user plane connection between the second network elements corresponding to the first routing ID is established.

[0018] According to a fifth aspect of the embodiments of the present disclosure, a first network element is provided, including:

[0019] A second transceiver module is configured to receive first information sent by a first terminal, where the first information includes a first routing identifier ID;

[0020] further configured to send second information to a second network element corresponding to the first routing ID, where the second information includes a first correlation ID corresponding to the first routing ID;

[0021] The first information is used to indicate that a first user plane connection is established with the second network element, or is used to indicate that establishment of the first user plane connection with the second network element is completed.

[0022] According to a sixth aspect of the embodiments of the present disclosure, a second network element is provided, including:

[0023] a third transceiver module, configured to receive second information sent by the first network element, where the second information includes a first correlation ID corresponding to the first routing ID;

[0024] The second information is sent after the first network element receives the first information sent by the first terminal, and the first information includes the first routing ID;

[0025] The first information is used to instruct the second network element corresponding to the first routing ID to establish a first user plane connection, or to indicate that establishment of the first user plane connection between the second network elements corresponding to the first routing ID is completed.

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

[0027] one or more processors;

[0028] The processor is used to execute the optional implementation of the aforementioned first aspect.

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

[0030] one or more processors;

[0031] The processor is used to execute the optional implementation of the aforementioned second aspect.

[0032] According to a ninth aspect of the embodiments of the present disclosure, a second network element is provided, including:

[0033] one or more processors;

[0034] The processor is used to execute the optional implementation of the aforementioned third aspect.

[0035] According to a tenth aspect of the embodiments of the present disclosure, a communication system is provided, including a first network element and a second network element, wherein:

[0036] The first network element is configured to receive first information sent by a first terminal, where the first information includes a first routing identifier ID;

[0037] The first network element is configured to send second information to a second network element corresponding to the first routing ID, where the second information includes a first correlation ID corresponding to the first routing ID;

[0038] The first information is used to instruct the second network element corresponding to the first routing ID to establish a first user plane connection, or to indicate that the first user plane connection between the second network elements corresponding to the first routing ID is established.

[0039] According to the eleventh aspect of an embodiment of the present disclosure, a computer-readable storage medium is provided, in which executable instructions are stored. The executable instructions are loaded and executed by the processor to implement the method described in the aforementioned first aspect or second aspect, or the optional implementation of the third aspect.

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

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

[0042] FIG1 is a schematic structural diagram of a wireless communication system according to an exemplary embodiment;

[0043] FIG2a is a flow chart showing a communication method according to an exemplary embodiment;

[0044] FIG2b is a flow chart showing a communication method according to an exemplary embodiment;

[0045] FIG2c is a flow chart showing a communication method according to an exemplary embodiment;

[0046] FIG3a is a flow chart of a communication method according to an embodiment of the present disclosure;

[0047] FIG3 b is a flow chart of a communication method according to an embodiment of the present disclosure;

[0048] FIG3c is a flow chart of a communication method according to an embodiment of the present disclosure;

[0049] FIG3 d is a flow chart of a communication method according to an embodiment of the present disclosure;

[0050] FIG4a is a flow chart of a communication method according to an embodiment of the present disclosure;

[0051] FIG4 b is a flow chart of a communication method according to an embodiment of the present disclosure;

[0052] FIG4c is a flow chart of a communication method according to an embodiment of the present disclosure;

[0053] FIG5a is a flow chart of a communication method according to an embodiment of the present disclosure;

[0054] FIG5 b is a flow chart of a communication method according to an embodiment of the present disclosure;

[0055] FIG5c is a flow chart of a communication method according to an embodiment of the present disclosure;

[0056] FIG5 d is a flow chart of a communication method according to an embodiment of the present disclosure;

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

[0058] FIG6 b is a schematic structural diagram of a first network element proposed in an embodiment of the present disclosure;

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

[0060] FIG7 a is a flow chart of a communication method according to an embodiment of the present disclosure;

[0061] FIG7 b is a flow chart of a communication method according to an embodiment of the present disclosure;

[0062] FIG7c is a flow chart of a communication method according to an embodiment of the present disclosure;

[0063] FIG7 d is a flow chart of a communication method according to an embodiment of the present disclosure;

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

[0065] FIG8 b is a schematic structural diagram of a chip proposed in an embodiment of the present disclosure. DETAILED DESCRIPTION

[0066] The embodiments of the present disclosure provide a communication method, a device, a communication system, and a storage medium.

[0067] In a first aspect, an embodiment of the present disclosure provides a communication method, applied to a first terminal, the method comprising:

[0068] Sending first information to the first network element, where the first information includes a first routing identifier ID;

[0069] The first information is used to instruct the second network element corresponding to the first routing ID to establish a first user plane connection, or to indicate that the first user plane connection between the second network elements corresponding to the first routing ID is established.

[0070] In the above embodiment, the first terminal includes the first routing ID in the first information sent to the first network element to indicate the establishment of a user plane connection with the second network element identified by the first routing ID, or the user plane connection between the first network element identified by the first routing ID is completed, so that the first network element does not need to perform the selection process of the second network element, and can directly forward the information to the second network element identified by the first routing ID, thereby optimizing and improving the user plane connection establishment process.

[0071] In conjunction with some embodiments of the first aspect, in some embodiments, the first routing ID includes at least one of the following:

[0072] Delayed routing ID received via the user plane;

[0073] Delayed route ID received via the control plane;

[0074] a second routing ID received during a second user plane connection release process between the first terminal and the second network element;

[0075] Location service LCS session ID received via the user plane.

[0076] In the above embodiment, the obtained delayed routing ID or LCS session ID, or the routing ID received during the user plane connection release process can be set as the first routing ID, and the first routing ID is transmitted to the first network element, so that the first network element can know that the second network element establishing a user plane connection with the first terminal is a specific network element identified by the first routing ID, without the need to perform a selection process to determine the second network element establishing a user plane connection with the first terminal.

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

[0078] receiving, via a user plane, third information sent by the second network element, where the third information includes a delayed routing ID and / or an LCS session ID;

[0079] The first routing ID is set based on the delay routing ID and / or the LCS session ID included in the third information.

[0080] In the above embodiment, the first terminal obtains the delay routing ID and / or LCS session ID through the user plane, sets the first routing ID based on the delay routing ID and / or LCS session ID, and transmits it to the first network element, so that the first network element can know that the second network element that establishes a user plane connection with the first terminal is a specific network element identified by the first routing ID, and there is no need to perform a selection process to determine the second network element that establishes a user plane connection with the first terminal.

[0081] In combination with some embodiments of the first aspect, in some embodiments, if the third information is used to request the call of LCS periodically triggered positioning event reporting, the third information includes a delayed routing ID; or, if the third information is used for positioning service, the third information includes an LCS session ID.

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

[0083] receiving, via the control plane, fourth information sent by the first network element, where the fourth information is used to request invoking an LCS periodically triggered positioning event reporting, and the fourth information includes a delayed routing ID;

[0084] The delayed route ID included in the fourth information is set as the first route ID.

[0085] In the above embodiment, the first terminal obtains the delayed routing ID through the control plane, and sets the delayed routing ID as the first routing ID to transmit to the first network element, so that the first network element can know that the second network element that establishes a user plane connection with the first terminal is a specific network element identified by the first routing ID, without the need to perform a selection process to determine the second network element that establishes a user plane connection with the first terminal.

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

[0087] receiving, via a control plane, fifth information sent by the first network element, where the fifth information is used to notify the first terminal to change a second user plane connection between the first terminal and the second network element, where the fifth information includes a second routing ID, where the second routing ID corresponds to the second network element that establishes the first user plane connection with the first terminal;

[0088] The first terminal is further configured to set the second routing ID included in the fifth information as the first routing ID.

[0089] In the above embodiment, the first terminal can set the routing ID received during the user plane connection release process as the first routing ID and transmit it to the first network element, so that the first network element can know that the second network element that establishes a user plane connection with the first terminal is a specific network element identified by the first routing ID, without the need to perform a selection process to determine the second network element that establishes a user plane connection with the first terminal.

[0090] In combination with some embodiments of the first aspect, in some embodiments, the fifth information is sent by the first network element after receiving the sixth information sent by the second network element, the sixth information includes a second related ID, and the second routing ID included in the fifth information corresponds to the second related ID, and the second related ID is used to identify the second network element that establishes the first user plane connection with the first terminal.

[0091] In the above embodiment, the first terminal can receive a routing ID during the user plane connection release process triggered by the network side, and set the routing ID as the first routing ID to transmit to the first network element, so that the first network element can know that the second network element that establishes a user plane connection with the first terminal is a specific network element identified by the first routing ID, without the need to perform a selection process to determine the second network element that establishes a user plane connection with the first terminal.

[0092] In conjunction with some embodiments of the first aspect, in some embodiments, the sixth information further includes at least one of the following information:

[0093] a third correlation ID, where the third correlation ID is used to identify a second network element that establishes a second user plane connection with the first terminal;

[0094] first indication information, used to instruct to change the second user plane connection;

[0095] Second indication information, used to instruct to release the second user plane connection;

[0096] third indication information, used to indicate a condition for releasing the second user plane connection;

[0097] and / or,

[0098] The fifth information further includes at least one of the following information:

[0099] a third routing ID, where the third routing ID corresponds to a second network element establishing a second user plane connection with the first terminal;

[0100] first indication information, used to instruct to change the second user plane connection;

[0101] Second indication information, used to instruct to release the second user plane connection;

[0102] The third indication information is used to indicate a condition for releasing the second user plane connection.

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

[0104] Send seventh information to the first network element, where the seventh information is used to request release of the second user plane connection between the first network element and the second network element, where the seventh information includes a third routing ID, and the third routing ID corresponds to the second network element that establishes the second user plane connection with the first terminal.

[0105] In the above embodiment, the first terminal can receive a routing ID during the user plane connection release process triggered by the terminal, and set the routing ID as the first routing ID to transmit to the first network element, so that the first network element can know that the second network element that establishes a user plane connection with the first terminal is a specific network element identified by the first routing ID, without the need to perform a selection process to determine the second network element that establishes a user plane connection with the first terminal.

[0106] In a second aspect, an embodiment of the present disclosure provides a communication method, applied to a first network element, the method including:

[0107] receiving first information sent by a first terminal, where the first information includes a first routing identifier ID;

[0108] Sending second information to a second network element corresponding to the first routing ID, where the second information includes a first correlation ID corresponding to the first routing ID;

[0109] The first information is used to indicate that a first user plane connection is established with the second network element, or is used to indicate that establishment of the first user plane connection with the second network element is completed.

[0110] In conjunction with some embodiments of the second aspect, in some embodiments, the first routing ID includes at least one of the following:

[0111] a delayed routing ID received by the first terminal via a user plane;

[0112] a delayed routing ID received by the first terminal via a control plane;

[0113] a second routing ID received by the first terminal during a process of releasing a second user plane connection between the first terminal and the second network element;

[0114] The positioning service LCS session ID received by the first terminal via the user plane.

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

[0116] receiving fourth information sent by the second network element, the fourth information being used to request invoking an LCS periodically triggered positioning event reporting, the fourth information including a delayed routing ID;

[0117] The fourth information is sent to the first terminal through the control surface.

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

[0119] receiving sixth information sent by a second network element, where the sixth information is used to indicate a change in a second user plane connection between the first terminal and the second network element, the sixth information including a second correlation ID, where the second correlation ID is used to identify the second network element that establishes the first user plane connection with the first terminal;

[0120] The control plane sends fifth information to the first terminal, where the second routing ID included in the fifth information corresponds to the second correlation ID.

[0121] In conjunction with some embodiments of the second aspect, in some embodiments, the sixth information further includes at least one of the following information:

[0122] a third correlation ID, where the third correlation ID is used to identify a second network element that establishes a second user plane connection with the first terminal;

[0123] first indication information, used to instruct to change the second user plane connection;

[0124] Second indication information, used to instruct to release the second user plane connection;

[0125] third indication information, used to indicate a condition for releasing the second user plane connection;

[0126] and / or,

[0127] The fifth information further includes at least one of the following information:

[0128] a third routing ID, where the third routing ID corresponds to a second network element establishing a second user plane connection with the first terminal;

[0129] first indication information, used to instruct to change the second user plane connection;

[0130] Second indication information, used to instruct to release the second user plane connection;

[0131] The third indication information is used to indicate a condition for releasing the second user plane connection.

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

[0133] receiving seventh information sent by the first terminal, where the seventh information is used to request release of the second user plane connection between the first terminal and the second network element, the seventh information including a third routing ID, where the third routing ID corresponds to the second network element that establishes the second user plane connection with the first terminal;

[0134] Eighth information is sent to the second network element corresponding to the third routing ID, where the eighth information includes a third correlation ID, and the third correlation ID is used to identify the second network element that establishes a second user plane connection with the first terminal.

[0135] In a third aspect, an embodiment of the present disclosure provides a communication method, applied to a second network element, the method comprising:

[0136] receiving second information sent by the first network element, where the second information includes a first correlation ID corresponding to the first routing ID;

[0137] The first information is used to instruct the second network element corresponding to the first routing ID to establish a first user plane connection, or to indicate that the first user plane connection between the second network elements corresponding to the first routing ID is established.

[0138] In conjunction with some embodiments of the third aspect, in some embodiments, the first routing ID includes at least one of the following:

[0139] a delayed routing ID received by the first terminal via a user plane;

[0140] a delayed routing ID received by the first terminal via a control plane;

[0141] a second routing ID received by the first terminal during a process of releasing a second user plane connection between the first terminal and the second network element;

[0142] The positioning service LCS session ID received by the first terminal via the user plane.

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

[0144] The third information is sent to the first terminal via the user, where the third information includes a delay routing ID and / or an LCS session ID.

[0145] In combination with some embodiments of the third aspect, in some embodiments, the third information is used to request the call of LCS periodically triggered positioning event reporting, then the third information includes a delayed routing ID; or, the third information is used for positioning service, then the third information includes an LCS session ID.

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

[0147] Sending fourth information to the first network element, where the fourth information is used to request calling the LCS periodically triggered positioning event reporting, and the fourth information includes a delayed routing ID.

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

[0149] Send sixth information to the first network element, where the sixth information is used to indicate a change in the second user plane connection between the first terminal and the second network element, and the sixth information includes a second related ID, where the second related ID is used to identify the second network element that establishes the first user plane connection with the first terminal.

[0150] In conjunction with some embodiments of the third aspect, in some embodiments, the sixth information further includes at least one of the following information:

[0151] a third correlation ID, where the third correlation ID is used to identify a second network element that establishes a second user plane connection with the first terminal;

[0152] first indication information, used to instruct to change the second user plane connection;

[0153] Second indication information, used to instruct to release the second user plane connection;

[0154] The third indication information is used to indicate a condition for releasing the second user plane connection.

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

[0156] Receive the eighth information sent by the first network element, where the eighth information is used to request the release of the second user plane connection between the first terminal and the second network element, and the eighth information includes a third related ID, where the third related ID is used to identify the second network element that establishes the second user plane connection with the first terminal.

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

[0158] A first transceiver module is configured to send first information to a first network element, where the first information includes a first routing identifier ID;

[0159] The first information is used to instruct the second network element corresponding to the first routing ID to establish a first user plane connection, or to indicate that the first user plane connection between the second network elements corresponding to the first routing ID is established.

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

[0161] A second transceiver module is configured to receive first information sent by a first terminal, where the first information includes a first routing identifier ID;

[0162] further configured to send second information to a second network element corresponding to the first routing ID, where the second information includes a first correlation ID corresponding to the first routing ID;

[0163] The first information is used to indicate that a first user plane connection is established with the second network element, or is used to indicate that establishment of the first user plane connection with the second network element is completed.

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

[0165] a third transceiver module, configured to receive second information sent by the first network element, where the second information includes a first correlation ID corresponding to the first routing ID;

[0166] The first information is used to instruct the second network element corresponding to the first routing ID to establish a first user plane connection, or to indicate that the first user plane connection between the second network elements corresponding to the first routing ID is established.

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

[0168] one or more processors;

[0169] The processor is used to execute the method described in the optional implementation manner of the first aspect.

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

[0171] one or more processors;

[0172] The processor executes the method described in the optional implementation of the second aspect.

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

[0174] one or more processors;

[0175] The processor is used to execute the method described in the optional implementation of the third aspect.

[0176] In a tenth aspect, an embodiment of the present disclosure provides a communication system, including a first network element and a second network element, wherein:

[0177] The first network element is configured to receive first information sent by a first terminal, where the first information includes a first routing identifier ID;

[0178] The first network element is configured to send second information to a second network element corresponding to the first routing ID, where the second information includes a first correlation ID corresponding to the first routing ID;

[0179] The first information is used to instruct the second network element corresponding to the first routing ID to establish a first user plane connection, or to indicate that the first user plane connection between the second network elements corresponding to the first routing ID is established.

[0180] In conjunction with some embodiments of the tenth aspect, in some embodiments,

[0181] The first routing ID includes at least one of the following:

[0182] Delayed routing ID received via the user plane;

[0183] Delayed route ID received via the control plane;

[0184] a second routing ID received during a second user plane connection release process between the first terminal and the second network element;

[0185] Location service LCS session ID received via the user plane.

[0186] In conjunction with some embodiments of the tenth aspect, in some embodiments,

[0187] The second network element is further configured to send third information to the first terminal via the user, wherein the third information includes a delay routing ID and / or an LCS session ID.

[0188] In combination with some embodiments of the tenth aspect, in some embodiments, if the third information is used to request the call of LCS periodically triggered positioning event reporting, the third information includes a delayed routing ID; or, if the third information is used for positioning service, the third information includes an LCS session ID.

[0189] In combination with some embodiments of the tenth aspect, in some embodiments, the first network element is also used to receive fourth information sent by the second network element, and send the fourth information to the first terminal via the control surface, and the fourth information is used to request to call the LCS period to trigger the positioning event report, and the fourth information includes the delayed routing ID.

[0190] In conjunction with some embodiments of the tenth aspect, in some embodiments, the first network element is further configured to send fifth information to the first terminal via the control plane, where the fifth information is used to notify the first terminal to change the second user plane connection with the second network element, and the fifth information includes a second routing ID, where the second routing ID corresponds to the second network element that establishes the first user plane connection with the first terminal.

[0191] The first terminal is further configured to set the second routing ID included in the fifth information as the first routing ID.

[0192] In conjunction with some embodiments of the tenth aspect, in some embodiments, the first network element is further configured to receive sixth information sent by the second network element, where the sixth information is used to indicate a change in the second user plane connection, and the sixth information includes a second correlation ID, where the second correlation ID is used to identify the second network element that establishes the first user plane connection with the first terminal;

[0193] The first network element is further configured to send the fifth information to the first terminal, where the second routing ID included in the fifth information corresponds to the second correlation ID.

[0194] In conjunction with some embodiments of the tenth aspect, in some embodiments, the sixth information further includes at least one of the following information:

[0195] a third correlation ID, where the third correlation ID is used to identify a second network element that establishes a second user plane connection with the first terminal;

[0196] first indication information, used to instruct to change the second user plane connection;

[0197] Second indication information, used to instruct to release the second user plane connection;

[0198] third indication information, used to indicate a condition for releasing the second user plane connection;

[0199] and / or,

[0200] The fifth information further includes at least one of the following information:

[0201] a third routing ID, where the third routing ID corresponds to a second network element establishing a second user plane connection with the first terminal;

[0202] first indication information, used to instruct to change the second user plane connection;

[0203] Second indication information, used to instruct to release the second user plane connection;

[0204] The third indication information is used to indicate a condition for releasing the second user plane connection.

[0205] In conjunction with some embodiments of the tenth aspect, in some embodiments, the first network element is further configured to receive seventh information sent by the first terminal, where the seventh information is used to request release of the second user plane connection with the second network element, and the seventh information includes a third routing ID, where the third routing ID corresponds to the second network element that establishes the second user plane connection with the first terminal;

[0206] The first network element is further used to send eighth information to the second network element corresponding to the third routing ID, where the eighth information includes a third related ID, and the third related ID is used to identify the second network element that establishes a second user plane connection with the first terminal.

[0207] In the eleventh 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.

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

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

[0210] In a fourteenth aspect, an embodiment of the present disclosure proposes a chip or a chip system, which includes a processing circuit for executing the method described in the optional implementation of the first aspect, the second aspect, or the third aspect above.

[0211] It is understandable that the above-mentioned communication devices, communication systems, storage media, program products, and computer programs are all used to perform the methods 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. Among them, the communication device can be a terminal or a network element.

[0212] The present disclosure provides a communication method, a communication device, a communication system, and a storage medium. In some embodiments, the terms communication method and information processing method are interchangeable, the terms communication device and information processing device are interchangeable, and the terms information processing system and communication system are interchangeable.

[0213] 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 embodiments 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.

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

[0215] 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 embodiments of the present disclosure.

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

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

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

[0219] In the embodiments of the present disclosure, descriptions such as “at least one of A, B, C…”, “A and / or B and / or C…”, etc. include the situation where any one of A, B, C… exists alone, and also include any combination of any multiple of A, B, C…, and each situation can exist alone; for example, “at least one of A, B, C” includes the situation where A exists alone, B exists alone, C exists alone, the combination of A and B, the combination of A and C, the combination of B and C, and the combination of A, B, and C; for example, A and / or B includes the situation where A exists alone, B exists alone, and the combination of A and B.

[0220] In some embodiments, descriptions such as "in one case A, in another case B," or "in response to one case A, in response to another case B," may include the following technical solutions depending on the situation: executing A independently of B (in some embodiments, A); executing B independently of A (in some embodiments, B); selectively executing A and B (in some embodiments, selecting between A and B); and executing both A and B (in some embodiments, A and B). The same applies when there are more branches, such as A, B, and C.

[0221] 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 configuration" and the "second configuration" can be the same information or different information, and their contents can be the same or different.

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

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

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

[0225] 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", "carrier", "component carrier", "bandwidth part (BWP)" and the like may be used interchangeably.

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

[0227] 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 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, it can also be described as device-to-device (D2D), vehicle-to-everything (V2X), etc.). In this case, it can also be set as a structure in which the terminal has all or part of the functions of the access network device. In addition, languages ​​such as "uplink" and "downlink" can also be replaced with languages ​​corresponding to communication between terminals (for example, "side").

[0228] For example, an uplink channel, a downlink channel, etc. may be replaced by a side channel, and an uplink, a downlink, etc. may be replaced by a side link.

[0229] In some embodiments, terms such as "uplink", "uplink", "physical uplink" can be interchangeable with each other, and terms such as "downlink", "downlink", "physical downlink" can be interchangeable with each other, and terms such as "side", "sidelink", "side communication", "sidelink communication", "direct connection", "direct link", "direct communication", "direct link communication" can be interchangeable with each other.

[0230] In some embodiments, the terms "downlink control information (DCI)", "downlink (DL) assignment", "DL DCI", "uplink (UL) grant", "UL DCI" and the like may be used interchangeably.

[0231] In some embodiments, terms such as "physical downlink shared channel (PDSCH)" and "DL data" can be used interchangeably, and terms such as "physical uplink shared channel (PUSCH)" and "UL data" can be used interchangeably.

[0232] In some embodiments, the determination or judgment can be performed by a value represented by 1 bit (0 or 1), or by a true or false value (Boolean value) represented by true or false, or by comparison of numerical values ​​(for example, comparison with a predetermined value), but is not limited thereto.

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

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

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

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

[0237] As shown in FIG1 , a communication system 100 includes a terminal 101 and a network device 102 .

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

[0239] In some embodiments, the network device 102 may include at least one of an access network device and a core network device.

[0240] In some embodiments, the access network device is, for example, a node or device that accesses a terminal to a wireless network. The 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 wireless fidelity (WiFi) system, but is not limited thereto.

[0241] In some embodiments, the technical solutions of the embodiments of the present disclosure may be applicable to the Open RAN architecture. In this case, the interfaces between or within the network devices involved in the embodiments of the present disclosure may become internal interfaces of the Open RAN, and the processes and information interactions between these internal interfaces may be implemented through software or programs.

[0242] 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 described as a control unit. The CU-DU structure can be used to split the protocol layer of the 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.

[0243] In some embodiments, the access network device may be a single device, multiple devices, or a group of devices. The network element may be virtual or physical. The network device may include, for example, at least one of an Evolved Packet Core (EPC), a 5G Core Network (5GCN), or a Next Generation Core (NGC).

[0244] In some embodiments, the core network device may be a device including one or more network elements, or may be multiple devices or device groups, each including all or part of the one or more network elements. The network element may be virtual or physical. The core network may include, for example, at least one of an Evolved Packet Core (EPC), a 5G Core Network (5GCN), a 6G Core Network (6GCN), and a Next Generation Core (NGC).

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

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

[0247] The embodiments of the present disclosure may 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), 6th generation mobile communication system (6G), 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).

[0248] In some examples, a Location Management Function (LMF) or a User Equipment (UE) may trigger the establishment of a user plane connection. The UE and the LMF may maintain the established user plane connection. In some examples, the LMF may modify or terminate the user plane connection established between the UE and the LMF.

[0249] Specifically, in some embodiments, the LMF triggers the process of establishing a user connection with the UE. The LMF can send the user plane information of the LMF (i.e., Internet Protocol (IP) address or fully qualified domain name (FQDN)) to the UE via the downlink non-access stratum transport (DL NAS TRANSPORT) message of the access and mobility management function (AMF). If the LMF sends the FQDN of the LMF to the UE, the UE can use the Domain Name System (DNS) server / resolver to resolve the IP address of the LMF (e.g., Edge Application Server Discovery Function (EASDF) or local DNS for local LMF address resolution). The UE uses the UE Route Selection Policy (URSP) including user plane positioning-related PDU session parameters (e.g., dedicated data network name (DNN) and single network slice selection assistance information (S-NSSAI)) to establish a packet data unit (PDU) session for user plane positioning. The Session Management Function (SMF) selects a PDU Session Anchor User Plane Function (PSA UPF) connected to the LMF for the PDU session based on the S-NSSAI, DNN, and UE location information.

[0250] In some embodiments, the Identity (ID) includes a Routing ID and a Correlation ID. The Correlation ID and the Routing ID are different terms for the same identity. The "Correlation ID" is an identity used for service operations between the AMF and the LMF, and the "Routing ID" is an identity used in NAS messages sent over the N1 reference point between the UE and the AMF.

[0251] In the process related to LCS, the correlation ID (or routing ID) is used between the LMF, AMF and UE to identify the LMF and the LCS session between the LMF and the UE. For example, when the AMF receives a message and a routing ID from the UE, the AMF can map the routing ID to the correlation ID and send the message to the LMF identified by the correlation ID.

[0252] During the user plane connection establishment process triggered by the UE, the relevant ID is the routing ID. The UE sends a user plane connection establishment request without the routing ID. The AMF receives the UL NAS TRANSPORT message without the routing ID and selects the LMF for the UE.

[0253] However, in some cases, if the LMF has previously provided the corresponding routing ID to the UE, and no routing ID is provided during the user plane connection establishment process triggered by the UE, the LMF selected by the AMF may not be the LMF corresponding to the above routing ID. Therefore, the following situation is not considered during the user plane connection establishment process triggered by the UE: after receiving the routing ID from the LMF, the UE can send a user plane connection establishment request including the routing ID.

[0254] To this end, the solution provided by the embodiment of the present disclosure provides a UE-triggered user plane connection establishment process, wherein the UE sends a UL NAS TRANSPORT message to the AMF, which includes a user plane connection establishment request and a routing ID. The AMF does not need to perform LMF selection, and the AMF only needs to send a message to the LMF identified by the routing ID.

[0255] In some embodiments, the UE may set the value of the routing ID provided to the AMF to be: the delayed routing ID received during the delayed 5G Core-Mobile Terminated-Location Request (5GC-MT-LR) process, or the LCS session ID or routing ID received during the user plane connection reestablishment (or release) process.

[0256] In some embodiments, "obtain", "get", "get", "receive", "transmit", "bidirectional transmission", "send and / or receive" can be interchangeable, and can be interpreted as receiving from other entities, obtaining from protocols, obtaining from higher layers, obtaining by self-processing, autonomous implementation, etc.

[0257] Based on the above wireless communication system, various embodiments of the communication method proposed in the present disclosure are described in detail below.

[0258] FIG2a is an interactive schematic diagram of a communication method according to an embodiment of the present disclosure. As shown in FIG2a , the communication method is used in a communication system 100, and the method includes:

[0259] S201. A second network element sends third information to a first terminal via a user.

[0260] In some embodiments, the second network element may be a LMF, or a SF, or an enhanced LMF.

[0261] In some embodiments, the first terminal may receive the third information sent by the second network element via the user plane.

[0262] In some embodiments, the third information may be transmitted via a downlink location service-user plane transmission (DL LCS-UP TRANSPORT) message. Optionally, the DL LCS-UP TRANSPORT message may include: a Location Positioning Protocol (LPP) message or a location supplementary services message, and an LCS session ID; or, the DL LCS-UP TRANSPORT message may include: an LCS message; or, the DL LCS-UP TRANSPORT message may include: an LCS message and an LCS session ID.

[0263] In some embodiments, when the LCS message is a positioning service periodic-triggered invoke request message (LCS Periodic-Triggered Invoke Request message), the LCS Periodic-Triggered Invoke Request message includes a delayed routing ID.

[0264] In some embodiments, the third information is used to request to call the LCS periodically trigger the reporting of positioning events. Optionally, the third information includes a deferred routing ID.

[0265] Optionally, the positioning service period triggering invocation request message is transmitted through a DL LCS-UP TRANSPORT message, where the positioning service period triggering invocation request message includes a delayed routing ID.

[0266] In some embodiments, the delay route ID may identify the second network element.

[0267] In some embodiments, the delay route ID may identify a serving second network element or a default second network element.

[0268] In some embodiments, the third information is used for positioning services.

[0269] In some embodiments, the LPP message or the positioning supplementary service message and the LCS session ID are transmitted through a DL LCS-UP TRANSPORT message.

[0270] In some embodiments, the LCS session ID may identify the initiating and reporting sessions of the positioning event session.

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

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

[0273] S202: The first terminal sets a first routing ID based on the delayed routing ID and / or the LCS session ID in the third information.

[0274] In some embodiments, the third information includes a delayed routing ID, and the first terminal sets the delayed routing ID as the first routing ID.

[0275] In some embodiments, the third information includes an LCS session ID, and the first terminal sets the LCS session as the first routing ID.

[0276] In some embodiments, the third information includes a delay route ID and an LCS session ID, and the first terminal sets the delay route ID as the first route ID.

[0277] In some embodiments, the first routing ID corresponds to a specific second network element that establishes a user plane connection with the first terminal. Optionally, the first routing ID can be mapped to a correlation ID that identifies the specific second network element, so that the first network element determines the specific second network element that establishes a user plane connection with the first terminal.

[0278] Steps S201 and S202 are optional steps. In some embodiments, after the first terminal sets the first routing ID locally, steps S201 and S202 may not be executed before executing step S203. That is, steps S201 and S202 are not necessarily executed before each execution of step S203.

[0279] S203. The first terminal sends first information to the first network element.

[0280] In some embodiments, the first network element may be an AMF.

[0281] In some embodiments, the first information includes a first routing ID.

[0282] In some embodiments, the first routing ID includes at least one of the following:

[0283] Delayed routing ID received via the user plane;

[0284] Location service LCS session ID received via the user plane.

[0285] In some embodiments, if the third information sent by the second network element received by the first terminal via the user plane includes a delayed routing ID, the first routing ID is the delayed routing ID; if the third information sent by the second network element received by the first terminal via the user plane includes an LCS session ID, the first routing ID is the LCS session ID.

[0286] In some embodiments, the first information is used to instruct a second network element corresponding to the first routing ID to establish a first user plane connection.

[0287] In some embodiments, the first information may further include a user plane connection establishment request message.

[0288] In some embodiments, the first information is used to indicate that establishment of a first user plane connection between the second network element corresponding to the first routing ID is complete.

[0289] In some embodiments, the first information may further include a user plane connection establishment complete message.

[0290] Optionally, the first information may be transmitted to the first network element via an uplink non-access stratum transmission (UL NAS TRANSPORT) message.

[0291] S204. The first network element sends second information to the second network element.

[0292] In some embodiments, the first network element converts the first routing ID into a first correlation ID.

[0293] In some embodiments, the second information includes a first correlation ID corresponding to the first routing ID.

[0294] In some embodiments, the first network element does not perform the second network element selection operation.

[0295] In some embodiments, the first network element may convert the first routing ID into a first correlation ID. Optionally, the first network element maps the first routing ID into the first correlation ID.

[0296] In some embodiments, the first network element sends a second message to a second network element identified by the first routing ID or the first correlation ID.

[0297] In some embodiments, the first network element obtains the corresponding first correlation ID based on the first routing ID in the first information, thereby determining the second network element identified by the first correlation ID, and sends second information to the determined second network element, where the second information includes the first correlation ID.

[0298] Optionally, if the first information is used to instruct the second network element corresponding to the first routing ID to establish a first user plane connection, the second information is used to request to establish the first user plane connection.

[0299] In some embodiments, the second information may further include a user plane connection establishment request message.

[0300] In some embodiments, the second information may further include a user plane connection establishment completion message.

[0301] In some embodiments, the second information may be transmitted via an LMF user plane location configuration (Nlmf_Location_UPConfig) message. Optionally, the message may include a user plane connection establishment request and the first correlation ID.

[0302] Optionally, if the first information is used to indicate a first user plane connection establishment request between a second network element corresponding to the first routing ID, the second information is used to notify the first user plane connection establishment request.

[0303] Optionally, if the first information is used to indicate that the first user plane connection between the second network element corresponding to the first routing ID is established, the second information is used to notify that the first user plane connection is established.

[0304] In some embodiments, the second message may be transmitted via an AMF communication N1 notification (Namf_Communication_N1MessageNotify) message. Optionally, the message may include user plane connection establishment completion and the first correlation ID.

[0305] In the solution of the embodiment of the present disclosure, by carrying the first routing ID in the first information sent by the first terminal to the first network element, the first network element can learn the second network element that establishes a user plane connection with the first terminal, and send the second information carrying the first related ID corresponding to the first routing ID to the second network element, thereby realizing the establishment of a user plane connection between the terminal and the specific second network element.

[0306] The method involved in the embodiment of the present disclosure may include at least one of steps S201 to S204. For example, steps S203 and S204 may be implemented as independent embodiments, and steps S202, S203, and S204 may be implemented as independent embodiments, but are not limited thereto.

[0307] In some embodiments, step S201 is optional and can be combined with the above-mentioned embodiments implemented as independent embodiments. In different embodiments, one or more of these steps can be omitted or replaced.

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

[0309] FIG2b is an interactive schematic diagram of a communication method according to an embodiment of the present disclosure. As shown in FIG2b , the communication method is used in a communication system 100, and the method includes:

[0310] S211 - 1. The second network element sends fourth information to the first network element.

[0311] In some embodiments, the second network element may be a LMF, or a SF, or an enhanced LMF.

[0312] In some embodiments, the first network element may be an AMF.

[0313] In some embodiments, the fourth information is used to request to call the LCS periodically trigger the reporting of the positioning event. Optionally, the fourth information includes a deferred routing ID.

[0314] Optionally, the fourth information can be transmitted via an AMF communication N1N2 transmission (Namf_Communication_N1N2MessageTransfer) message.

[0315] In some embodiments, the second network element may transmit a positioning service periodic-triggered invocation request message (LCS Periodic-Triggered Invoke Request message) through a Namf_Communication_N1N2MessageTransfer message, where the LCS Periodic-Triggered Invoke Request message includes a delayed routing ID.

[0316] In some embodiments, the Namf_Communication_N1N2MessageTransfer message may further include a correlation ID, where the correlation ID is used to identify the second network element.

[0317] In some embodiments, the delay routing ID may identify an identifier of the serving second network element or a default second network element.

[0318] In some embodiments, the delay route ID may identify the initiation and reporting of the location event process.

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

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

[0321] S211-2. The first network element sends fourth information to the first terminal under control.

[0322] In some embodiments, the fourth information is used to request to call the LCS periodically trigger the reporting of the positioning event. Optionally, the fourth information includes a deferred routing ID.

[0323] Optionally, the fourth information may be transmitted via a downlink non-access stratum transmission (DL NAS TRANSPORT) message.

[0324] In some embodiments, the first network element may transmit the fourth information to the first terminal via a DL NAS TRANSPORT message. Optionally, a positioning service period trigger invocation request message is transmitted via a DL NAS TRANSPORT message, where the positioning service period trigger invocation request message includes a delayed routing ID.

[0325] In some embodiments, if the first network element further receives a correlation ID, the DL NAS TRANSPORT message may further include a routing ID, where the routing ID is obtained by the first network element through mapping based on the received correlation ID.

[0326] S212: The first terminal sets the delayed routing ID in the fourth information as the first routing ID.

[0327] In some embodiments, the fourth information includes a delayed routing ID, and the first terminal sets the delayed routing ID as the first routing ID.

[0328] In some embodiments, the first routing ID corresponds to a specific second network element that establishes a user plane connection with the first terminal. Optionally, the first routing ID can be mapped to a correlation ID that identifies the specific second network element, so that the first network element determines the specific second network element that establishes a user plane connection with the first terminal.

[0329] Steps S211-1, S211-2 and step S212 are optional steps. In some embodiments, steps S211-1, S211-2 and step S212 may not be executed before executing step S213, that is, steps S211-1, S211-2 and step S212 are not necessarily executed before each execution of step S213.

[0330] S213. The first terminal sends first information to the first network element.

[0331] In some embodiments, the first information includes a first routing ID.

[0332] In some embodiments, the first route ID comprises a delayed route ID received via a control plane.

[0333] In some embodiments, the fourth information sent by the first network element and received by the first terminal via the control plane includes a delayed routing ID, and the first routing ID is the delayed routing ID.

[0334] In some embodiments, the first information is used to instruct a second network element corresponding to the first routing ID to establish a first user plane connection.

[0335] In some embodiments, the first information may be transmitted via an uplink non-access stratum transport (UL NAS TRANSPORT) message. Optionally, the UL NAS TRANSPORT message may further include a user plane connection establishment request message.

[0336] In some embodiments, the first information is used to indicate that establishment of a first user plane connection between the second network element corresponding to the first routing ID is complete.

[0337] In some embodiments, the first information may be transmitted via an uplink non-access stratum transport (UL NAS TRANSPORT) message. Optionally, the UL NAS TRANSPORT message may further include a user plane connection establishment complete message.

[0338] S214. The first network element sends second information to the second network element.

[0339] For optional implementation of the above step S214, reference may be made to the relevant content of step S204 in FIG. 2a , which will not be described in detail here.

[0340] The method involved in the embodiment of the present disclosure may include at least one of steps S211-1 to S214. For example, steps S213 and S214 may be implemented as independent embodiments, and steps S212, S213, and S214 may be implemented as independent embodiments, but are not limited thereto.

[0341] In some embodiments, steps S211 - 1 and S211 - 2 are optional and can be combined with the above-mentioned embodiments implemented as independent embodiments. In different embodiments, one or more of these steps can be omitted or replaced.

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

[0343] FIG2c is an interactive schematic diagram of a communication method according to an embodiment of the present disclosure. As shown in FIG2c, the communication method is used in a communication system 100, and the method includes:

[0344] S221-1. The second network element sends sixth information to the first network element.

[0345] In some embodiments, the second network element may be a LMF, or a SF, or an enhanced LMF.

[0346] In some embodiments, the first network element may be an AMF.

[0347] In some embodiments, the sixth information is used to indicate a change in the second user plane connection between the first terminal and the second network element.

[0348] Optionally, changing the second user plane connection between the first terminal and the second network element includes: releasing the second user plane connection and re-establishing the user plane connection between the first terminal and the second network element; or, releasing the second user plane connection and establishing a user plane connection between the first terminal and another network element.

[0349] In some embodiments, when the second network element determines to change the user plane connection between the second network element and the first terminal, the sixth information may be sent to the first network element.

[0350] In some embodiments, the sixth information includes a second correlation ID, where the second correlation ID is used to identify a second network element that establishes a first user plane connection with the first terminal. Optionally, the second network element may be the second network element that sends the sixth information (i.e., the network element that has established a second user plane connection with the first terminal), or may be a network element different from the second network element that sends the sixth information (i.e., a network element different from the network element that has established a second user plane connection with the first terminal).

[0351] In some embodiments, the sixth information may further include at least one of the following information:

[0352] a third correlation ID, where the third correlation ID is used to identify a second network element that establishes a second user plane connection with the first terminal;

[0353] first indication information, used to instruct to change the second user plane connection;

[0354] Second indication information, used to instruct to release the second user plane connection;

[0355] The third indication information is used to indicate a condition for releasing the second user plane connection.

[0356] Optionally, the sixth information may include first indication information, used to instruct the first terminal to change the second user plane connection between the first terminal and the second network element.

[0357] In some embodiments, the first indication information may instruct the first terminal to reestablish a user plane connection with the second network element, for example, a newly established user plane connection.

[0358] In some embodiments, the sixth information may further include: relevant information of the second network element, at least one of the second indication information and the third indication information.

[0359] Optionally, the relevant information of the second network element may include at least one of the identifier (ID) of the second network element, the IP address (for example, LMF LCS-UP address) and the relevant ID corresponding to the second user plane connection.

[0360] Optionally, the relevant ID corresponding to the second user plane connection may also be the third relevant ID corresponding to the second network element.

[0361] Optionally, the second indication information is used to indicate the release of the first user plane connection.

[0362] Optionally, the third indication information is used to indicate a condition for releasing the first user plane connection.

[0363] Exemplarily, the third indication information is used to indicate that the condition for releasing the second user plane connection is to release the second user plane connection before or after the first terminal reestablishes a new user plane connection (which may correspond to the first user plane connection mentioned above) with the second network element.

[0364] In some embodiments, the condition for releasing the second user plane connection may be determined based on a service demand related to the second user plane connection.

[0365] Exemplarily, if the service related to the second user plane connection allows network interruption, the condition for releasing the second user plane connection is to release the second user plane connection before the first terminal and the second network element reestablish a new user plane connection; otherwise, the second user plane connection is released after the first terminal and the second network element reestablish a new user plane connection.

[0366] In some embodiments, the sixth information may be transmitted via an AMF communication N1N2 transmission (Namf_Communication_N1N2MessageTransfer) message.

[0367] Optionally, the Namf_Communication_N1N2MessageTransfer message may further include a user plane connection release command message, but the message name is not limited thereto.

[0368] In some embodiments, the second network element may transmit the user plane connection release command message, the second correlation ID, and the third correlation ID through a Namf_Communication_N1N2MessageTransfer message.

[0369] In some embodiments, the sixth information includes a user plane connection release command and a third correlation ID. Optionally, the user plane connection release command includes a second correlation ID.

[0370] Optionally, the Namf_Communication_N1N2MessageTransfer message may further include a user plane connection re-etasblishment command message, but the message name is not limited thereto.

[0371] Optionally, the user plane connection reestablishment command message may include a second correlation ID or a second routing ID.

[0372] Optionally, the Namf_Communication_N1N2MessageTransfer message may also include a user plane connection modification command message, but the name of the message is not limited thereto.

[0373] Optionally, the user plane connection change command message may include a second correlation ID or a second routing ID.

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

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

[0376] S221-2. The first network element sends fifth information to the first terminal under control.

[0377] In some embodiments, the fifth information is used to notify the first terminal to change the second user plane connection with the second network element. Optionally, the fifth information includes a second routing ID corresponding to the second network element that establishes the first user plane connection with the first terminal.

[0378] Optionally, the second network element that establishes the first user plane connection with the first terminal may be a network element that releases the second user plane connection established with the first terminal, or may be another network element different from the network element that establishes the second user plane connection with the first terminal.

[0379] In some embodiments, the fifth information may further include at least one of the following information:

[0380] a third routing ID, where the third routing ID corresponds to a second network element establishing a second user plane connection with the first terminal;

[0381] first indication information, used to instruct to change the second user plane connection;

[0382] Second indication information, used to instruct to release the second user plane connection;

[0383] The third indication information is used to indicate a condition for releasing the second user plane connection.

[0384] Optionally, the fifth information may include first indication information, used to instruct the first terminal to change the second user plane connection between the first terminal and the second network element.

[0385] In some embodiments, the first indication information may instruct the first terminal to reestablish a user plane connection with the second network element, for example, a newly established user plane connection.

[0386] In some embodiments, the fifth information may further include: at least one of the second indication information and the third indication information.

[0387] Optionally, the second indication information is used to indicate the release of the first user plane connection.

[0388] Optionally, the third indication information is used to indicate a condition for releasing the first user plane connection.

[0389] Exemplarily, the third indication information is used to indicate that the condition for releasing the second user plane connection is to release the second user plane connection before or after the first terminal reestablishes a new user plane connection (which may correspond to the first user plane connection mentioned above) with the second network element.

[0390] In some embodiments, the condition for releasing the second user plane connection may be determined based on a service demand related to the second user plane connection.

[0391] Exemplarily, if the service related to the second user plane connection allows network interruption, the condition for releasing the second user plane connection is to release the second user plane connection before the first terminal and the second network element reestablish a new user plane connection; otherwise, the second user plane connection is released after the first terminal and the second network element reestablish a new user plane connection.

[0392] Optionally, the fifth information may also include: relevant information of the second network element, such as: the identifier (ID) of the second network element, the IP address (for example: LMF LCS-UP address) and at least one of the routing ID corresponding to the second user plane connection.

[0393] Optionally, the routing ID corresponding to the second user plane connection may also be a third routing ID corresponding to the second network element.

[0394] In some embodiments, the fifth information may be transmitted via a downlink non-access stratum transport (DL NAS TRANSPORT) message. Optionally, the DL NAS TRANSPORT message may also include a user plane connection release command message, but the name of the message is not limited thereto.

[0395] In some embodiments, the fifth message includes a user plane connection release command and a third routing ID.

[0396] Optionally, the user plane connection release command includes a second correlation ID or a second routing ID.

[0397] In some embodiments, the fifth message includes a user plane connection change command and a third routing ID. Optionally, the user plane change command includes a second correlation ID or a second routing ID.

[0398] In some embodiments, the first network element converts the third correlation ID into a third routing ID.

[0399] In some embodiments, the first network element converts the second correlation ID into a second routing ID.

[0400] In some embodiments, the first network element transmits the user plane connection release command message, the second routing ID, and the third routing ID through a DL NAS TRANSPORT message.

[0401] S222: The first terminal sets the second routing ID in the fifth information as the first routing ID.

[0402] In some embodiments, the fifth information includes a second routing ID, and the first terminal sets the second routing ID as the first routing ID.

[0403] In some embodiments, the fifth information includes a second correlation ID, and the first terminal sets the second correlation ID as the first routing ID. Optionally, the value of the second correlation ID is the same as the value of the second routing ID.

[0404] In some embodiments, the second routing ID corresponds to the second network element that establishes the first user plane connection with the first terminal. The first terminal sets the second routing ID to the first routing ID and carries it in the first information indicating the establishment of the first user plane connection and transmits it to the first network element, so that the first network element can accurately know the second network element that establishes the first user plane connection with the first terminal.

[0405] In some embodiments, the first routing ID corresponds to a specific second network element that establishes a user plane connection with the first terminal. Optionally, the first routing ID can be mapped to a correlation ID that identifies the specific second network element, so that the first network element determines the specific second network element that establishes a user plane connection with the first terminal.

[0406] Steps S221-1, S221-2 and step S222 are optional steps. In some embodiments, after the first terminal locally sets the first routing ID, steps S221-1, S221-2 and step S222 may not be executed before executing step S223, that is, steps S221-1, S221-2 and step S222 are not necessarily executed before executing step S223 every time.

[0407] S223. The first terminal sends first information to the first network element.

[0408] In some embodiments, the first routing ID includes: a second routing ID received during a second user plane connection release process between the first terminal and the second network element.

[0409] In some embodiments, the fifth information sent by the first network element and received by the first terminal via the control plane includes a second routing ID, and the first routing ID is set to the second routing ID. Optionally, the second routing ID corresponds to the second network element that establishes the first user plane connection with the first terminal.

[0410] In some embodiments, the fifth information sent by the first network element and received by the first terminal via the control plane includes a second correlation ID, and the first routing ID is set to the second correlation ID. Optionally, the second correlation ID is used to identify the second network element that establishes the first user plane connection with the first terminal.

[0411] In some embodiments, the first information is used to instruct a second network element corresponding to the first routing ID to establish a first user plane connection.

[0412] In some embodiments, the first information may further include a user plane connection establishment request message.

[0413] In some embodiments, the first information is used to indicate that establishment of a first user plane connection between the second network element corresponding to the first routing ID is complete.

[0414] In some embodiments, the first information may further include a user plane connection establishment complete message.

[0415] Optionally, the first information may be transmitted to the first network element via an uplink non-access stratum transmission (UL NAS TRANSPORT) message.

[0416] S224. The first network element sends second information to the second network element.

[0417] For optional implementation of the above step S224, reference may be made to the relevant content of step S204 in FIG. 2a , which will not be described in detail here.

[0418] In some embodiments, if the performance of the old user plane connection between the first terminal and the second network element degrades and cannot meet relevant business requirements, the second network element can determine to change (for example: release, rebuild, modify) the user plane connection between the first terminal and the second network element.

[0419] In some embodiments, the first terminal may determine to release the user plane connection between the first terminal and the second network element.

[0420] In some embodiments, before step S221-1, the method may further include the following steps:

[0421] S220-1. The first terminal sends seventh information to the first network.

[0422] In some embodiments, the seventh information is used to request release of the second user plane connection with the second network element.

[0423] In some embodiments, the seventh information includes a third routing ID, where the third routing ID corresponds to a second network element that establishes a second user plane connection with the first terminal.

[0424] In some embodiments, when the first terminal determines to release the user plane connection between the first terminal and the second network element (which may correspond to the second user plane connection mentioned above), the first terminal may send seventh information to the first network element.

[0425] In some embodiments, the seventh information may be transmitted via an uplink non-access stratum transport (UL NAS TRANSPORT) message. Optionally, the first terminal may transmit a user plane connection release request message and the third routing ID to the first network element via a UL NAS TRANSPORT message.

[0426] In some embodiments, if the first terminal determines to release the user plane connection established between it and the second network element, it can send information requesting the release of the user plane connection to the second network element via the first network element, and carry a third routing identifier corresponding to the second network element in the information, so that the first network element knows which network element the user plane connection to be released is established between the first terminal and, thereby determining the corresponding network element.

[0427] S220-2. The first network element sends eighth information to the second network.

[0428] In some embodiments, the eighth information is used to request release of the second user plane connection between the first terminal and the second network element.

[0429] In some embodiments, the first network element converts the third routing ID into a third correlation ID.

[0430] In some embodiments, the eighth information includes a third correlation ID, where the third correlation ID is used to identify a second network element that establishes a second user plane connection with the first terminal.

[0431] In some embodiments, the first network element may convert the third routing ID into a third correlation ID. Optionally, the first network element maps the third routing ID into the third correlation ID.

[0432] In some embodiments, the first network element obtains the corresponding third correlation ID based on the third routing ID in the seventh information, thereby determining the second network element identified by the third correlation ID, and sends the eighth information to the determined second network element, where the eighth information includes the third correlation ID.

[0433] In some embodiments, the second network element accepts (can be understood as allowing) changing the user plane connection established with the first terminal (can correspond to the second user plane connection mentioned above), and then sends sixth information to the first network element.

[0434] In some embodiments, the eighth information may be transmitted via an AMF communication N1 notification (Namf_Communication_N1MessageNotify) message. Optionally, the first network element may transmit a user plane connection release request message (user plane connection release Request message) and the third correlation ID to the second network element via a Namf_Communication_N1MessageNotify message.

[0435] In some embodiments, after step S221-2, the following steps may also be included:

[0436] S225 (not shown in the figure): the first terminal sends ninth information to the second network element via the first network element.

[0437] In some embodiments, the ninth information is used to notify that the second user plane connection has been released.

[0438] In some embodiments, the first terminal may send the ninth information to the first network element via an uplink non-access layer transmission (UL NAS TRANSPORT) message; or, the first network element may send the ninth information to the second network element via an AMF communication N1 notification (Namf_Communication_N1MessageNotify) message.

[0439] In some embodiments, the ninth information may include a user plane connection release complete message, but the name of the message is not limited thereto.

[0440] In some embodiments, the ninth information may include a user plane connection re-establishment complete message, but the name of the message is not limited thereto.

[0441] In some embodiments, the ninth information may include a user plane connection modification complete message, but the name of the message is not limited thereto.

[0442] In some embodiments, step S225 includes S225-1, the first terminal sends ninth information to the first network element.

[0443] Optionally, the ninth information sent by the first terminal to the first network element may be carried by an uplink non-access layer transmission (UL NAS TRANSPORT) message.

[0444] In some embodiments, the ninth information sent by the first terminal to the first network element includes the third routing ID.

[0445] In some embodiments, the first network element may convert the third routing ID into a third correlation ID.

[0446] In some embodiments, step S225 includes S225-2, the first network element sends ninth information to the second network element.

[0447] Optionally, the ninth information sent by the first network element to the second network element can be carried by an AMF communication N1 notification (Namf_Communication_N1MessageNotify) message.

[0448] In some embodiments, the ninth information sent by the first network element to the second network element includes the third correlation ID.

[0449] The method involved in the embodiments of the present disclosure may include at least one of steps S220-1 to S225. For example, steps S223 and S224 can be implemented as independent embodiments, steps S222, S223, and S224 can be implemented as independent embodiments, steps S223, S224, and S225 can be implemented as independent embodiments, steps S221-1, S221-2, S223, and S224 can be implemented as independent embodiments, steps S221-1, S221-2, S223, S224, and S225 can be implemented as independent embodiments, steps S222, S223, S224, and S225 can be implemented as independent embodiments, and steps S221-1, S221-2, S222, S223, S224, and S225 can be implemented as independent embodiments, but are not limited thereto.

[0450] In some embodiments, steps S220 - 1 and S220 - 2 are optional and can be combined with the above-mentioned embodiments implemented as independent embodiments. In different embodiments, one or more of these steps can be omitted or replaced.

[0451] In some embodiments, steps S221 - 1 and S221 - 2 are optional and can be combined with the above-mentioned embodiments implemented as independent embodiments. In different embodiments, one or more of these steps can be omitted or replaced.

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

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

[0454] FIG3a is a flow chart of a communication method according to an embodiment of the present disclosure. As shown in FIG3a, the communication method can be executed by a first terminal, and the method includes:

[0455] S301. Receive third information sent by a second network element via a user plane.

[0456] The optional implementation of step S301 can refer to the optional implementation of step S201 in FIG2a and other related parts in the embodiment involved in FIG2a, which will not be described in detail here.

[0457] In some embodiments, the second network element may be a LMF, or a SF, or an enhanced LMF.

[0458] In some embodiments, the third information may be a downlink positioning service-user plane transmission (DL LCS-UP TRANSPORT) message.

[0459] In some embodiments, the third information is used to request to call the LCS periodically trigger the reporting of the positioning event. Optionally, the third information includes a delayed routing ID.

[0460] Optionally, the third information may include a positioning service periodic-triggered invoke request message (LCS Periodic-Triggered Invoke Request message). Optionally, the LCS Periodic-Triggered Invoke Request message includes a delayed routing ID.

[0461] In some embodiments, the delay route ID may identify the second network element.

[0462] In some embodiments, the delay route ID may identify a serving second network element or a default second network element.

[0463] In some embodiments, the third information is used for positioning services. Optionally, the third information includes an LCS session ID.

[0464] Optionally, the third information may include a Positioning Protocol (LPP) message or a location supplementary services message.

[0465] In some embodiments, the LCS session ID may identify the initiating and reporting sessions of the positioning event session.

[0466] In some embodiments, the third information includes a delay route ID and an LCS session ID.

[0467] S302: Set the delayed routing ID and / or LCS session ID in the third information as the first routing ID.

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

[0469] In some embodiments, the third information includes a delay routing ID, and the first terminal sets the delay routing ID to the first routing ID; the third information includes an LCS session ID, and the first terminal sets the LCS session to the first routing ID; the third information includes a delay routing ID and an LCS session ID, and the first terminal sets the delay routing ID to the first routing ID.

[0470] Step S301 and step S302 are optional steps. In some embodiments, step S301 and step S302 may not be executed before step S303 is executed. That is, step S301 and step S302 are not necessarily executed before step S303 is executed every time.

[0471] S303: Send first information to the first network element.

[0472] The optional implementation of step S303 can refer to the optional implementation of step S203 in FIG2a and other related parts in the embodiment involved in FIG2a, which will not be described in detail here.

[0473] In some embodiments, in some embodiments, the first network element may be an AMF.

[0474] In some embodiments, the first information includes a first routing ID.

[0475] In some embodiments, the first information is used to instruct a second network element corresponding to the first routing ID to establish a first user plane connection.

[0476] In some embodiments, the first information is used to indicate that establishment of a first user plane connection between the second network element corresponding to the first routing ID is complete.

[0477] The method involved in the embodiment of the present disclosure may include at least one of steps S301 to S303. For example, step S303 may be implemented as an independent embodiment, and steps S302 and S303 may be implemented as independent embodiments, but are not limited thereto.

[0478] In some embodiments, step S301 is optional and can be combined with the above-mentioned embodiments implemented as independent embodiments. In different embodiments, one or more of these steps can be omitted or replaced.

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

[0480] FIG3b is a flow chart of a communication method according to an embodiment of the present disclosure. As shown in FIG3b, the communication method can be executed by a first terminal, and the method includes:

[0481] S311. Receive fourth information sent by the first network element via the control plane.

[0482] The optional implementation of step S311 can refer to the optional implementation of step S211-2 in Figure 2b and other related parts in the embodiment involved in Figure 2b, which will not be repeated here.

[0483] In some embodiments, the first network element may be an AMF.

[0484] In some embodiments, the fourth information is used to request to call the LCS periodically triggered positioning event reporting. Optionally, the fourth information includes a delayed routing ID.

[0485] Optionally, the fourth information may include a positioning service periodic-triggered invoke request message (LCS Periodic-Triggered Invoke Request message).

[0486] In some embodiments, the delay route ID may identify the second network element.

[0487] In some embodiments, the fourth information is obtained by the first network element from the second network element.

[0488] In some embodiments, the first network element receives the fourth information sent by the second network element, and sends the fourth information to the first terminal.

[0489] The above optional implementation method can refer to the optional implementation method of step S211-1 in Figure 2b and other related parts in the embodiment involved in Figure 2b, which will not be repeated here.

[0490] In some embodiments, the second network element may be a LMF, or a SF, or an enhanced LMF.

[0491] S312: Set the delayed routing ID in the fourth information as the first routing ID.

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

[0493] Step S311 and step S312 are optional steps. In some embodiments, step S311 and step S312 may not be executed before step S313 is executed, that is, step S311 and step S312 are not necessarily executed before step S313 is executed every time.

[0494] S313. Send first information to the first network element.

[0495] The optional implementation of step S313 can refer to the optional implementation of step S203 in FIG2a and other related parts in the embodiment involved in FIG2a, which will not be described in detail here.

[0496] In some embodiments, the first information includes a first routing ID.

[0497] In some embodiments, the first information is used to instruct a second network element corresponding to the first routing ID to establish a first control plane connection.

[0498] In some embodiments, the first information is used to indicate that establishment of a first control plane connection between the second network element corresponding to the first routing ID is complete.

[0499] The method involved in the embodiment of the present disclosure may include at least one of steps S311 to S313. For example, step S313 may be implemented as an independent embodiment, and steps S312 and S313 may be implemented as independent embodiments, but are not limited thereto.

[0500] In some embodiments, step S311 is optional and can be combined with the above-mentioned embodiments implemented as independent embodiments. In different embodiments, one or more of these steps can be omitted or replaced.

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

[0502] Figure 3c is a flow chart of a communication method according to an embodiment of the present disclosure. As shown in Figure 3c, the communication method can be executed by the first terminal, and the method includes:

[0503] S321. Receive fifth information sent by the first network element via the control plane.

[0504] The optional implementation of step S321 can refer to the optional implementation of step S221-2 in Figure 2c and other related parts in the embodiment involved in Figure 2c, which will not be repeated here.

[0505] In some embodiments, the first network element may be an AMF.

[0506] In some embodiments, the fifth information is used to notify the first terminal to change the second user plane connection with the second network element. Optionally, the fifth information includes a second routing ID corresponding to the second network element that establishes the first user plane connection with the first terminal.

[0507] In some embodiments, the fifth information may further include at least one of the following information:

[0508] a third routing ID, where the third routing ID corresponds to a second network element establishing a second user plane connection with the first terminal;

[0509] first indication information, used to instruct to change the second user plane connection;

[0510] Second indication information, used to instruct to release the second user plane connection;

[0511] The third indication information is used to indicate a condition for releasing the second user plane connection.

[0512] In some embodiments, the first network element sends the fifth information after obtaining the sixth information from the second network element.

[0513] In some embodiments, the sixth information is used to indicate a change in the second user plane connection between the first terminal and the second network element.

[0514] In some embodiments, the sixth information includes a second correlation ID, where the second correlation ID is used to identify a second network element that establishes the first user plane connection with the first terminal.

[0515] In some embodiments, the sixth information may further include at least one of the following information:

[0516] a third correlation ID, where the third correlation ID is used to identify a second network element that establishes a second user plane connection with the first terminal;

[0517] first indication information, used to instruct to change the second user plane connection;

[0518] Second indication information, used to instruct to release the second user plane connection;

[0519] The third indication information is used to indicate a condition for releasing the second user plane connection.

[0520] In some embodiments, after receiving the sixth information sent by the second network element, the first network element sends the fifth information to the first terminal.

[0521] The above optional implementation method can refer to the optional implementation method of step S221-1 in Figure 2c and other related parts in the embodiment involved in Figure 2c, which will not be repeated here.

[0522] In some embodiments, the second network element may be a LMF, or a SF, or an enhanced LMF.

[0523] S322: Set the second routing ID in the fifth information as the first routing ID.

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

[0525] Step S321 and step S322 are optional steps. In some embodiments, step S321 and step S322 may not be executed before step S323 is executed, that is, step S321 and step S322 are not necessarily executed before step S323 is executed every time.

[0526] S323. Send first information to the first network element.

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

[0528] In some embodiments, the first information includes a first routing ID.

[0529] In some embodiments, the first information is used to instruct a second network element corresponding to the first routing ID to establish a first control plane connection.

[0530] In some embodiments, the first information is used to indicate that establishment of a first control plane connection between the second network element corresponding to the first routing ID is complete.

[0531] In some embodiments, after step S321, the method may further include:

[0532] S320 (not shown in the figure): Send the seventh information to the first network element.

[0533] The optional implementation of step S320 can refer to the optional implementation of step S220-1 in Figure 2c and other related parts in the embodiment involved in Figure 2c, which will not be repeated here.

[0534] In some embodiments, the seventh information is used to request release of the second user plane connection with the second network element.

[0535] In some embodiments, the seventh information includes a third routing ID, where the third routing ID corresponds to a second network element that establishes a second user plane connection with the first terminal.

[0536] The method involved in the embodiments of the present disclosure may include at least one of steps S320 to S323. For example, step S323 may be implemented as an independent embodiment, steps S322 and S323 may be implemented as independent embodiments, and steps S321, S322, and S323 may be implemented as independent embodiments, but are not limited thereto.

[0537] In some embodiments, step S320 is optional and can be combined with the above-mentioned embodiments implemented as independent embodiments. In different embodiments, one or more of these steps can be omitted or replaced.

[0538] In some embodiments, step S321 is optional and can be combined with the above-mentioned embodiments implemented as independent embodiments. In different embodiments, one or more of these steps can be omitted or replaced.

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

[0540] Figure 3d is a flow chart of a communication method according to an embodiment of the present disclosure. As shown in Figure 3d, the communication method can be executed by a first terminal, and the method includes:

[0541] S331. Send first information to a first network element.

[0542] The optional implementation of step S331 can refer to the optional implementation of step S203 in FIG2a and other related parts in the embodiment involved in FIG2a, which will not be described in detail here.

[0543] In some embodiments, the first information includes a first routing ID.

[0544] In some embodiments, the first information is used to instruct a second network element corresponding to the first routing ID to establish a first control plane connection.

[0545] In some embodiments, the first information is used to indicate that establishment of a first control plane connection between the second network element corresponding to the first routing ID is complete.

[0546] In some embodiments, the first routing ID includes at least one of:

[0547] Delayed routing ID received via the user plane;

[0548] Delayed route ID received via the control plane;

[0549] a second routing ID received during a second user plane connection release process between the first terminal and the second network element;

[0550] Location service LCS session ID received via the user plane.

[0551] In some embodiments, the above method may further include:

[0552] receiving, via a user plane, third information sent by the second network element, where the third information includes a delayed routing ID and / or an LCS session ID;

[0553] The first routing ID is set based on the delay routing ID and / or the LCS session ID included in the third information.

[0554] In some embodiments, the third information is used to request the invocation of LCS periodically triggered positioning event reporting, and the third information includes a delayed routing ID; or, the third information is used for positioning service, and the third information includes an LCS session ID.

[0555] In some embodiments, the above method may further include:

[0556] receiving, via the control plane, fourth information sent by the first network element, where the fourth information is used to request invoking an LCS periodically triggered positioning event reporting, and the fourth information includes a delayed routing ID;

[0557] The delayed route ID included in the fourth information is set as the first route ID.

[0558] In some embodiments, the above method may further include:

[0559] receiving, via a control plane, fifth information sent by the first network element, where the fifth information is used to notify the first terminal to change a second user plane connection between the first terminal and the second network element, where the fifth information includes a second routing ID, where the second routing ID corresponds to the second network element that establishes the first user plane connection with the first terminal;

[0560] The first terminal is further configured to set the second routing ID included in the fifth information as the first routing ID.

[0561] In some embodiments, the fifth information is sent by the first network element after receiving the sixth information sent by the second network element, the sixth information includes a second related ID, the second routing ID included in the fifth information corresponds to the second related ID, and the second related ID is used to identify the second network element that establishes the first user plane connection with the first terminal.

[0562] In some embodiments, the sixth information further includes at least one of the following information:

[0563] a third correlation ID, where the third correlation ID is used to identify a second network element that establishes a second user plane connection with the first terminal;

[0564] first indication information, used to instruct to change the second user plane connection;

[0565] Second indication information, used to instruct to release the second user plane connection;

[0566] third indication information, used to indicate a condition for releasing the second user plane connection;

[0567] and / or,

[0568] The fifth information further includes at least one of the following information:

[0569] a third routing ID, where the third routing ID corresponds to a second network element establishing a second user plane connection with the first terminal;

[0570] first indication information, used to instruct to change the second user plane connection;

[0571] Second indication information, used to instruct to release the second user plane connection;

[0572] The third indication information is used to indicate a condition for releasing the second user plane connection.

[0573] In some embodiments, the above method may further include:

[0574] Send seventh information to the first network element, where the seventh information is used to request release of the second user plane connection between the first network element and the second network element, where the seventh information includes a third routing ID, and the third routing ID corresponds to the second network element that establishes the second user plane connection with the first terminal.

[0575] FIG4a is a flow chart of a communication method according to an embodiment of the present disclosure. As shown in FIG4a , the communication method may be executed by a first network element, and the method includes:

[0576] S401: Send fourth information to the first terminal via a control surface.

[0577] The optional implementation of step S401 can refer to the optional implementation of step S211-2 in Figure 2b and other related parts in the embodiment involved in Figure 2b, which will not be repeated here.

[0578] In some embodiments, the fourth information is used to request to call the LCS periodically triggered positioning event reporting. Optionally, the fourth information includes a delayed routing ID.

[0579] Optionally, the fourth information may include a positioning service periodic-triggered invoke request message (LCS Periodic-Triggered Invoke Request message).

[0580] In some embodiments, the delay route ID may identify the second network element.

[0581] In some embodiments, the fourth information is obtained by the first network element from the second network element.

[0582] In some embodiments, before step S401, the method further includes:

[0583] S400 (not shown in the figure): receiving fourth information sent by the second network element.

[0584] The above optional implementation method can refer to the optional implementation method of step S211-1 in Figure 2b and other related parts in the embodiment involved in Figure 2b, which will not be repeated here.

[0585] In some embodiments, the first network element receives the fourth information sent by the second network element, and sends the fourth information to the first terminal.

[0586] In some embodiments, the first network element may be an AMF; the second network element may be an LMF, or an SF, or an enhanced LMF.

[0587] Step S400 and step S401 are optional steps. In some embodiments, step S400 and step S401 may not be executed before step S402 is executed. That is, step S400 and step S401 are not necessarily executed before step S402 is executed every time.

[0588] S402: Receive first information sent by a first network element.

[0589] The optional implementation of step S402 can refer to the optional implementation of step S203 in FIG2a and other related parts in the embodiment involved in FIG2a, which will not be described in detail here.

[0590] In some embodiments, the first information includes a first routing ID.

[0591] In some embodiments, the first information is used to instruct a second network element corresponding to the first routing ID to establish a first control plane connection.

[0592] In some embodiments, the first information is used to indicate that establishment of a first control plane connection between the second network element corresponding to the first routing ID is complete.

[0593] S403: Send second information to the second network element corresponding to the first routing ID.

[0594] The optional implementation of step S403 can refer to the optional implementation of step S204 in FIG2a and other related parts in the embodiment involved in FIG2a, which will not be described in detail here.

[0595] In some embodiments, the second information includes a first correlation ID corresponding to the first routing ID.

[0596] In some embodiments, the first network element may convert the first routing ID into a first correlation ID. Optionally, the first network element maps the first routing ID into the first correlation ID.

[0597] In some embodiments, if the first information is used to instruct the second network element corresponding to the first routing ID to establish the first user plane connection, the second information is used to request to establish the first user plane connection.

[0598] In some embodiments, if the first information is used to indicate that the first user plane connection between the second network element corresponding to the first routing ID is established, the second information is used to notify that the first user plane connection is established.

[0599] The method involved in the embodiment of the present disclosure may include at least one of steps S400 to S403. For example, steps S402 and S403 may be implemented as independent embodiments, and steps S401, S402, and S403 may be implemented as independent embodiments, but are not limited thereto.

[0600] In some embodiments, step S400 is optional and can be combined with the above-mentioned embodiments implemented as independent embodiments. In different embodiments, one or more of these steps can be omitted or replaced.

[0601] In some embodiments, step S401 is optional and can be combined with the above-mentioned embodiments implemented as independent embodiments. In different embodiments, one or more of these steps can be omitted or replaced.

[0602] FIG4b is a flow chart of a communication method according to an embodiment of the present disclosure. As shown in FIG4b , the communication method may be executed by a first network element, and the method includes:

[0603] S411. Receive sixth information sent by the second network element.

[0604] In some embodiments, the sixth information is used to indicate a change in the second user plane connection between the first terminal and the second network element.

[0605] In some embodiments, the sixth information includes a second correlation ID, where the second correlation ID is used to identify a second network element that establishes the first user plane connection with the first terminal.

[0606] The optional implementation of step S412 can refer to the optional implementation of step S212-1 in Figure 2c and other related parts in the embodiment involved in Figure 2c, which will not be repeated here.

[0607] In some embodiments, the second network element may be a LMF, or a SF, or an enhanced LMF.

[0608] In some embodiments, the sixth information may further include at least one of the following information:

[0609] a third correlation ID, where the third correlation ID is used to identify a second network element that establishes a second user plane connection with the first terminal;

[0610] first indication information, used to instruct to change the second user plane connection;

[0611] Second indication information, used to instruct to release the second user plane connection;

[0612] The third indication information is used to indicate a condition for releasing the second user plane connection.

[0613] S412: Send fifth information to the first terminal through the control plane.

[0614] The optional implementation of step S412 can refer to the optional implementation of step S212-2 in Figure 2c and other related parts in the embodiment involved in Figure 2c, which will not be repeated here.

[0615] In some embodiments, after receiving the sixth information sent by the second network element, the first network element sends the fifth information to the first terminal.

[0616] In some embodiments, the fifth information is used to notify the first terminal to change the second user plane connection with the second network element. Optionally, the fifth information includes a second routing ID corresponding to the second network element that establishes the first user plane connection with the first terminal.

[0617] In some embodiments, the fifth information may further include at least one of the following information:

[0618] a third routing ID, where the third routing ID corresponds to a second network element establishing a second user plane connection with the first terminal;

[0619] first indication information, used to instruct to change the second user plane connection;

[0620] Second indication information, used to instruct to release the second user plane connection;

[0621] The third indication information is used to indicate a condition for releasing the second user plane connection.

[0622] Step S411 and step S412 are optional steps. In some embodiments, step S411 and step S412 may not be executed before step S413 is executed. That is, step S411 and step S412 are not necessarily executed before step S413 is executed every time.

[0623] S413: Receive first information sent by the first network element.

[0624] The optional implementation of step S413 can refer to the optional implementation of step S203 in FIG2a and other related parts in the embodiment involved in FIG2a, which will not be described in detail here.

[0625] In some embodiments, the first information includes a first routing ID.

[0626] In some embodiments, the first information is used to instruct a second network element corresponding to the first routing ID to establish a first control plane connection.

[0627] In some embodiments, the first information is used to indicate that establishment of a first control plane connection between the second network element corresponding to the first routing ID is complete.

[0628] S414. Send second information to the second network element corresponding to the first routing ID.

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

[0630] In some embodiments, the second information includes a first correlation ID corresponding to the first routing ID.

[0631] In some embodiments, the first network element may convert the first routing ID into a first correlation ID. Optionally, the first network element maps the first routing ID into the first correlation ID.

[0632] In some embodiments, if the first information is used to instruct the second network element corresponding to the first routing ID to establish the first user plane connection, the second information is used to request to establish the first user plane connection.

[0633] In some embodiments, if the first information is used to indicate that the first user plane connection between the second network element corresponding to the first routing ID is established, the second information is used to notify that the first user plane connection is established.

[0634] In some embodiments, before step S411, the method may further include:

[0635] S410a (not shown in the figure): receiving seventh information sent by the first terminal.

[0636] The optional implementation of step S410a can refer to the optional implementation of step S220-1 in FIG2c and other related parts in the embodiment involved in FIG2c, which will not be repeated here.

[0637] In some embodiments, the seventh information is used to request release of the second user plane connection with the second network element.

[0638] In some embodiments, the seventh information includes a third routing ID, where the third routing ID corresponds to a second network element that establishes a second user plane connection with the first terminal.

[0639] S410b (not shown in the figure): send the eighth information to the second network element.

[0640] The optional implementation of step S410b can refer to the optional implementation of step S220-2 in Figure 2c and other related parts in the embodiment involved in Figure 2c, which will not be repeated here.

[0641] In some embodiments, the eighth information is used to request release of the second user plane connection with the second network element.

[0642] In some embodiments, the eighth information includes a third correlation ID, where the third correlation ID is used to identify a second network element that establishes a second user plane connection with the first terminal.

[0643] In some embodiments, after obtaining the seventh information from the first terminal, the first network element sends the eighth information to the second network element.

[0644] The method involved in the embodiment of the present disclosure may include at least one of steps S410a to S413. For example, steps S412 and S413 may be implemented as independent embodiments, and steps S411, S412, and S413 may be implemented as independent embodiments, but are not limited thereto.

[0645] In some embodiments, steps S410a and S410b are optional and can be combined with the above-mentioned embodiments implemented as independent embodiments. In different embodiments, one or more of these steps can be omitted or replaced.

[0646] In some embodiments, step S411 is optional and can be combined with the above-mentioned embodiments implemented as independent embodiments. In different embodiments, one or more of these steps can be omitted or replaced.

[0647] Figure 4c is a flow chart of a communication method according to an embodiment of the present disclosure. As shown in Figure 4c, the communication method can be executed by a first network element, and the method includes:

[0648] S421. Receive first information sent by a first network element.

[0649] The optional implementation of step S421 can refer to the optional implementation of step S203 in FIG2a and other related parts in the embodiment involved in FIG2a, which will not be described in detail here.

[0650] In some embodiments, the first information includes a first routing ID.

[0651] In some embodiments, the first information is used to instruct a second network element corresponding to the first routing ID to establish a first control plane connection.

[0652] In some embodiments, the first information is used to indicate that establishment of a first control plane connection between the second network element corresponding to the first routing ID is complete.

[0653] S422. Send second information to the second network element corresponding to the first routing ID.

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

[0655] In some embodiments, the second information includes a first correlation ID corresponding to the first routing ID.

[0656] In some embodiments, the first network element may convert the first routing ID into a first correlation ID. Optionally, the first network element maps the first routing ID into the first correlation ID.

[0657] In some embodiments, if the first information is used to instruct the second network element corresponding to the first routing ID to establish the first user plane connection, the second information is used to request to establish the first user plane connection.

[0658] In some embodiments, if the first information is used to indicate that the first user plane connection between the second network element corresponding to the first routing ID is established, the second information is used to notify that the first user plane connection is established.

[0659] In some embodiments, the first routing ID includes at least one of the following:

[0660] a delayed routing ID received by the first terminal via a user plane;

[0661] a delayed routing ID received by the first terminal via a control plane;

[0662] a second routing ID received by the first terminal during a process of releasing a second user plane connection between the first terminal and the second network element;

[0663] The positioning service LCS session ID received by the first terminal via the user plane.

[0664] In some embodiments, the above method may further include:

[0665] receiving fourth information sent by the second network element, the fourth information being used to request invoking an LCS periodically triggered positioning event reporting, the fourth information including a delayed routing ID;

[0666] The fourth information is sent to the first terminal through the control surface.

[0667] In some embodiments, the above method may further include:

[0668] receiving sixth information sent by a second network element, where the sixth information is used to indicate a change in a second user plane connection between the first terminal and the second network element, the sixth information including a second correlation ID, where the second correlation ID is used to identify the second network element that establishes the first user plane connection with the first terminal;

[0669] The control plane sends fifth information to the first terminal, where the second routing ID included in the fifth information corresponds to the second correlation ID.

[0670] In some embodiments, the sixth information further includes at least one of the following information:

[0671] a third correlation ID, where the third correlation ID is used to identify a second network element that establishes a second user plane connection with the first terminal;

[0672] first indication information, used to instruct to change the second user plane connection;

[0673] Second indication information, used to instruct to release the second user plane connection;

[0674] third indication information, used to indicate a condition for releasing the second user plane connection;

[0675] and / or,

[0676] The fifth information further includes at least one of the following information:

[0677] a third routing ID, where the third routing ID corresponds to a second network element establishing a second user plane connection with the first terminal;

[0678] first indication information, used to instruct to change the second user plane connection;

[0679] Second indication information, used to instruct to release the second user plane connection;

[0680] The third indication information is used to indicate a condition for releasing the second user plane connection.

[0681] In some embodiments, the above method may further include:

[0682] receiving seventh information sent by the first terminal, where the seventh information is used to request release of the second user plane connection between the first terminal and the second network element, the seventh information including a third routing ID, where the third routing ID corresponds to the second network element that establishes the second user plane connection with the first terminal;

[0683] Eighth information is sent to the second network element corresponding to the third routing ID, where the eighth information includes a third correlation ID, and the third correlation ID is used to identify the second network element that establishes a second user plane connection with the first terminal.

[0684] Figure 5a is a flow chart of a communication method according to an embodiment of the present disclosure. As shown in Figure 5a, the communication method can be executed by a second network element, and the method includes:

[0685] S501: Send third information to the first terminal via the user.

[0686] The optional implementation of step S501 can refer to the optional implementation of step S201 in FIG2a and other related parts in the embodiment involved in FIG2a, which will not be described in detail here.

[0687] In some embodiments, the second network element may be a LMF, or a SF, or an enhanced LMF.

[0688] In some embodiments, the third information is used to request to call the LCS periodically trigger the reporting of the positioning event. Optionally, the third information includes a delayed routing ID.

[0689] Optionally, the third information may include a positioning service periodic-triggered invoke request message (LCS Periodic-Triggered Invoke Request message). Optionally, the LCS Periodic-Triggered Invoke Request message includes a delayed routing ID.

[0690] In some embodiments, the delay route ID may identify the second network element.

[0691] In some embodiments, the third information is used for positioning services. Optionally, the third information includes an LCS session ID.

[0692] Optionally, the third information may include a Positioning Protocol (LPP) message or a location supplementary services message.

[0693] In some embodiments, the LCS session ID may identify the initiating and reporting sessions of the positioning event session.

[0694] In some embodiments, the first terminal receives third information sent by the second network element via the user plane, sets the delayed routing ID or LCS session ID included in the third information to the first routing ID, and sends first information including the first routing ID to the first network element.

[0695] S502: Receive second information sent by the first network element.

[0696] The optional implementation of step S502 can refer to the optional implementation of step S204 in FIG2a and other related parts in the embodiment involved in FIG2a, which will not be described in detail here.

[0697] In some embodiments, the second information includes a first correlation ID corresponding to the first routing ID.

[0698] In some embodiments, the second information is sent by the first network element after receiving the first information sent by the first terminal, and the first information includes the first routing ID.

[0699] In some embodiments, the first network element may be an AMF.

[0700] In some embodiments, the first network element may convert the first routing ID into a first correlation ID. Optionally, the first network element maps the first routing ID into the first correlation ID.

[0701] In some embodiments, if the first information is used to instruct the second network element corresponding to the first routing ID to establish the first user plane connection, the second information is used to request to establish the first user plane connection.

[0702] In some embodiments, if the first information is used to indicate that the first user plane connection between the second network element corresponding to the first routing ID is established, the second information is used to notify that the first user plane connection is established.

[0703] The method involved in the embodiment of the present disclosure may include at least one of steps S501 and S502. For example, step S502 may be implemented as an independent embodiment, but is not limited thereto.

[0704] In some embodiments, step S501 is optional and can be combined with the above-mentioned embodiments implemented as independent embodiments. In different embodiments, one or more of these steps can be omitted or replaced.

[0705] FIG5b is a flow chart of a communication method according to an embodiment of the present disclosure. As shown in FIG5b , the communication method may be executed by a second network element, and the method includes:

[0706] S511. Send fourth information to the first network element.

[0707] The optional implementation of step S511 can refer to the optional implementation of step S211-1 in Figure 2b and other related parts in the embodiment involved in Figure 2a, which will not be repeated here.

[0708] In some embodiments, the first network element may be an AMF.

[0709] In some embodiments, the fourth information is used to request to call the LCS periodically triggered positioning event reporting. Optionally, the fourth information includes a delayed routing ID.

[0710] Optionally, the fourth information may include a positioning service periodic-triggered invoke request message (LCS Periodic-Triggered Invoke Request message). Optionally, the LCS Periodic-Triggered Invoke Request message includes a delayed routing ID.

[0711] In some embodiments, the delay route ID may identify the second network element.

[0712] In some embodiments, after receiving the fourth information sent by the second network element, the first network element may forward it to the first terminal.

[0713] In some embodiments, the first terminal receives fourth information sent by the first network element, sets the delayed routing ID included in the fourth information to the first routing ID, and sends first information including the first routing ID to the first network element.

[0714] S512: Receive second information sent by the first network element.

[0715] The optional implementation of step S512 can refer to the optional implementation of step S204 in FIG2 a and other related parts in the embodiment involved in FIG2 a , which will not be described in detail here.

[0716] In some embodiments, the second information includes a first correlation ID corresponding to the first routing ID.

[0717] In some embodiments, the second information is sent by the first network element after receiving the first information sent by the first terminal, and the first information includes the first routing ID.

[0718] In some embodiments, the first network element may be an AMF.

[0719] In some embodiments, the first network element may convert the first routing ID into a first correlation ID. Optionally, the first network element maps the first routing ID into the first correlation ID.

[0720] In some embodiments, if the first information is used to instruct the second network element corresponding to the first routing ID to establish the first user plane connection, the second information is used to request to establish the first user plane connection.

[0721] In some embodiments, if the first information is used to indicate that the first user plane connection between the second network element corresponding to the first routing ID is established, the second information is used to notify that the first user plane connection is established.

[0722] The method involved in the embodiment of the present disclosure may include at least one of steps S511 to S512. For example, step S512 may be implemented as an independent embodiment, but is not limited thereto.

[0723] In some embodiments, step S511 is optional and can be combined with the above-mentioned embodiments implemented as independent embodiments. In different embodiments, one or more of these steps can be omitted or replaced.

[0724] Figure 5c is a flow chart of a communication method according to an embodiment of the present disclosure. As shown in Figure 5c, the communication method can be executed by the second network element, and the method includes:

[0725] S521. Send sixth information to the first network element.

[0726] The optional implementation of step S521 can refer to the optional implementation of step S221-1 in Figure 2c and other related parts in the embodiment involved in Figure 2a, which will not be repeated here.

[0727] In some embodiments, the first network element may be an AMF.

[0728] In some embodiments, the sixth information is used to indicate a change in the second user plane connection between the first terminal and the second network element.

[0729] In some embodiments, the sixth information includes a second correlation ID, where the second correlation ID is used to identify a second network element that establishes the first user plane connection with the first terminal.

[0730] In some embodiments, the sixth information may further include at least one of the following information:

[0731] a third correlation ID, where the third correlation ID is used to identify a second network element that establishes a second user plane connection with the first terminal;

[0732] first indication information, used to instruct to change the second user plane connection;

[0733] Second indication information, used to instruct to release the second user plane connection;

[0734] The third indication information is used to indicate a condition for releasing the second user plane connection.

[0735] In some embodiments, after receiving the sixth information sent by the second network element, the first network element sends the fifth information to the first terminal.

[0736] In some embodiments, the fifth information is used to notify the first terminal to change the second user plane connection with the second network element. Optionally, the fifth information includes a second routing ID corresponding to the second network element that establishes the first user plane connection with the first terminal.

[0737] In some embodiments, the first terminal receives fifth information sent by the first network element, sets the second routing ID included in the fifth information as the first routing ID, and sends first information including the first routing ID to the first network element.

[0738] S522. Receive second information sent by the first network element.

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

[0740] In some embodiments, the second information includes a first correlation ID corresponding to the first routing ID.

[0741] In some embodiments, the second information is sent by the first network element after receiving the first information sent by the first terminal, and the first information includes the first routing ID.

[0742] In some embodiments, the first network element may be an AMF.

[0743] In some embodiments, the first network element may convert the first routing ID into a first correlation ID. Optionally, the first network element maps the first routing ID into the first correlation ID.

[0744] In some embodiments, if the first information is used to instruct the second network element corresponding to the first routing ID to establish the first user plane connection, the second information is used to request to establish the first user plane connection.

[0745] In some embodiments, if the first information is used to indicate that the first user plane connection between the second network element corresponding to the first routing ID is established, the second information is used to notify that the first user plane connection is established.

[0746] In some embodiments, before step S521, the method may further include:

[0747] S520 (not shown in the figure): receive the eighth information sent by the first network element.

[0748] The optional implementation of step S520 can refer to the optional implementation of step S220-2 in Figure 2c and other related parts in the embodiment involved in Figure 2c, which will not be repeated here.

[0749] In some embodiments, the eighth information is used to request release of the second user plane connection with the second network element.

[0750] In some embodiments, the eighth information includes a third correlation ID, where the third correlation ID is used to identify a second network element that establishes a second user plane connection with the first terminal.

[0751] In some embodiments, after obtaining the seventh information from the first terminal, the first network element sends the eighth information to the second network element.

[0752] The above optional implementation method can refer to the optional implementation method of step S220-1 in Figure 2c and other related parts in the embodiment involved in Figure 2c, which will not be repeated here.

[0753] In some embodiments, the seventh information is used to request release of the second user plane connection with the second network element.

[0754] In some embodiments, the seventh information includes a third routing ID, where the third routing ID corresponds to a second network element that establishes a second user plane connection with the first terminal.

[0755] The method involved in the embodiment of the present disclosure may include at least one of steps S520 to S522. For example, steps S522 and S523 may be implemented as independent embodiments, but are not limited thereto.

[0756] In some embodiments, step S520 is optional and can be combined with the above-mentioned embodiments implemented as independent embodiments. In different embodiments, one or more of these steps can be omitted or replaced.

[0757] Figure 5d is a flow chart of a communication method according to an embodiment of the present disclosure. As shown in Figure 5d, the communication method can be executed by the second network element, and the method includes:

[0758] S531. Receive second information sent by a first network element.

[0759] The optional implementation of step S531 can refer to the optional implementation of step S204 in FIG2a and other related parts in the embodiment involved in FIG2a, which will not be described in detail here.

[0760] In some embodiments, the second information includes a first correlation ID corresponding to the first routing ID.

[0761] In some embodiments, the second information is sent by the first network element after receiving the first information sent by the first terminal, and the first information includes the first routing ID.

[0762] In some embodiments, the first network element may be an AMF.

[0763] In some embodiments, the first network element may convert the first routing ID into a first correlation ID. Optionally, the first network element maps the first routing ID into the first correlation ID.

[0764] In some embodiments, if the first information is used to instruct the second network element corresponding to the first routing ID to establish the first user plane connection, the second information is used to request to establish the first user plane connection.

[0765] In some embodiments, if the first information is used to indicate that the first user plane connection between the second network element corresponding to the first routing ID is established, the second information is used to notify that the first user plane connection is established.

[0766] In some embodiments, the first routing ID includes at least one of the following:

[0767] a delayed routing ID received by the first terminal via a user plane;

[0768] a delayed routing ID received by the first terminal via a control plane;

[0769] a second routing ID received by the first terminal during a process of releasing a second user plane connection between the first terminal and the second network element;

[0770] The positioning service LCS session ID received by the first terminal via the user plane.

[0771] In some embodiments, the above method may further include: sending third information to the first terminal via the user, where the third information includes a delay routing ID and / or an LCS session ID.

[0772] In some embodiments, the third information is used to request the invocation of LCS periodically triggered positioning event reporting, and the third information includes a delayed routing ID; or, the third information is used for positioning service, and the third information includes an LCS session ID.

[0773] In some embodiments, the above method may further include: sending fourth information to the first network element, where the fourth information is used to request invoking an LCS periodically triggered positioning event report, and the fourth information includes a delayed routing ID.

[0774] In some embodiments, the above method may also include: sending sixth information to the first network element, the sixth information is used to indicate the change of the second user plane connection between the first terminal and the second network element, the sixth information includes a second related ID, and the second related ID is used to identify the second network element that establishes the first user plane connection with the first terminal.

[0775] In some embodiments, the sixth information further includes at least one of the following information:

[0776] a third correlation ID, where the third correlation ID is used to identify a second network element that establishes a second user plane connection with the first terminal;

[0777] first indication information, used to instruct to change the second user plane connection;

[0778] Second indication information, used to instruct to release the second user plane connection;

[0779] third indication information, used to indicate a condition for releasing the second user plane connection;

[0780] and / or,

[0781] The fifth information further includes at least one of the following information:

[0782] a third routing ID, where the third routing ID corresponds to a second network element establishing a second user plane connection with the first terminal;

[0783] first indication information, used to instruct to change the second user plane connection;

[0784] Second indication information, used to instruct to release the second user plane connection;

[0785] The third indication information is used to indicate a condition for releasing the second user plane connection.

[0786] In some embodiments, the above method may also include: receiving an eighth message sent by the first network element, the eighth message being used to request the release of the second user plane connection between the first terminal and the second network element, the eighth message including a third related ID, and the third related ID being used to identify the second network element that establishes a second user plane connection with the first terminal.

[0787] FIG6 a is a schematic diagram of the structure of a terminal proposed in an embodiment of the present disclosure. As shown in FIG6 a , the terminal may include at least one of: a first transceiver module 611 , a first processing module 612 , and the like.

[0788] In some embodiments, the first transceiver module 611 is used to send first information to the first network element, where the first information includes a first routing identifier ID; wherein the first information is used to indicate that a first user plane connection is established with the second network element corresponding to the first routing ID, or to indicate that the first user plane connection between the second network elements corresponding to the first routing ID is completed.

[0789] Optionally, the first routing ID includes at least one of the following:

[0790] Delayed routing ID received via the user plane;

[0791] Delayed route ID received via the control plane;

[0792] a second routing ID received during a second user plane connection release process between the first terminal and the second network element;

[0793] Location service LCS session ID received via the user plane.

[0794] Optionally, the first transceiver module 611 is further configured to receive, via a user plane, third information sent by a second network element, where the third information includes a delay routing ID and / or an LCS session ID. The first processing module 612 is configured to set the first routing ID based on the delay routing ID and / or the LCS session ID included in the third information.

[0795] Optionally, if the third information is used to request calling LCS periodically triggered positioning event reporting, the third information includes a delayed routing ID; or, if the third information is used for positioning service, the third information includes an LCS session ID.

[0796] Optionally, the first processing module 612 is further configured to receive, via the control plane, fourth information sent by the first network element, the fourth information being used to request invocation of an LCS periodically triggered positioning event reporting, the fourth information including a delay routing ID. The first processing module 612 is configured to set the delay routing ID included in the fourth information as the first routing ID.

[0797] Optionally, the first processing module 612 is further configured to receive, via the control plane, fifth information sent by the first network element, the fifth information being used to notify the first terminal to change the second user plane connection with the second network element, the fifth information including a second routing ID corresponding to the second network element that established the first user plane connection with the first terminal. The first processing module 612 is configured to set the second routing ID included in the fifth information to the first routing ID.

[0798] Optionally, the fifth information further includes at least one of the following information:

[0799] a third routing ID, where the third routing ID corresponds to a second network element establishing a second user plane connection with the first terminal;

[0800] first indication information, used to instruct to change the second user plane connection;

[0801] Second indication information, used to instruct to release the second user plane connection;

[0802] The third indication information is used to indicate a condition for releasing the second user plane connection.

[0803] Optionally, the above-mentioned first processing module 612 is also used to send seventh information to the first network element, and the seventh information is used to request the release of the second user plane connection between the first network element and the second network element, and the seventh information includes a third routing ID, and the third routing ID corresponds to the second network element that establishes the second user plane connection with the first terminal.

[0804] FIG6 b is a schematic diagram of the structure of a first network element proposed in an embodiment of the present disclosure. As shown in FIG6 b , the first network element includes at least one of a second transceiver module 621 and a second processing module 622 .

[0805] In some embodiments, the second transceiver module 621 is used to receive first information sent by the first terminal, and the first information includes a first routing identifier ID; the second transceiver module 621 is also used to send second information to a second network element corresponding to the first routing ID, and the second information includes a first related ID corresponding to the first routing ID; wherein the first information is used to indicate the establishment of a first user plane connection with the second network element, or to indicate that the establishment of the first user plane connection between the second network element is completed.

[0806] Optionally, the first routing ID includes at least one of the following:

[0807] a delayed routing ID received by the first terminal via a user plane;

[0808] a delayed routing ID received by the first terminal via a control plane;

[0809] a second routing ID received by the first terminal during a process of releasing a second user plane connection between the first terminal and the second network element;

[0810] The positioning service LCS session ID received by the first terminal via the user plane.

[0811] Optionally, the above-mentioned second transceiver module 621 is also used to receive the fourth information sent by the second network element, and send the fourth information to the first terminal via the control surface; wherein, the fourth information is used to request to call the LCS period to trigger the positioning event report, and the fourth information includes the delayed routing ID.

[0812] Optionally, the above-mentioned second transceiver module 621 is also used to receive sixth information sent by the second network element, and to send fifth information to the first terminal via the control plane; wherein, the sixth information is used to indicate a change in the second user plane connection between the first terminal and the second network element, and the sixth information includes a second related ID, and the second related ID is used to identify the second network element that establishes the first user plane connection with the first terminal; the second routing ID included in the fifth information corresponds to the second related ID.

[0813] Optionally, the sixth information further includes at least one of the following information:

[0814] a third correlation ID, where the third correlation ID is used to identify a second network element that establishes a second user plane connection with the first terminal;

[0815] first indication information, used to instruct to change the second user plane connection;

[0816] Second indication information, used to instruct to release the second user plane connection;

[0817] third indication information, used to indicate a condition for releasing the second user plane connection;

[0818] and / or,

[0819] The fifth information further includes at least one of the following information:

[0820] a third routing ID, where the third routing ID corresponds to a second network element establishing a second user plane connection with the first terminal;

[0821] first indication information, used to instruct to change the second user plane connection;

[0822] Second indication information, used to instruct to release the second user plane connection;

[0823] The third indication information is used to indicate a condition for releasing the second user plane connection.

[0824] Optionally, the above-mentioned second transceiver module 621 is also used to receive the seventh information sent by the first terminal, and send the eighth information to the second network element corresponding to the third routing ID; wherein, the seventh information is used to request the release of the second user plane connection between the first terminal and the second network element, and the seventh information includes the third routing ID, and the third routing ID corresponds to the second network element that establishes the second user plane connection with the first terminal; the eighth information includes the third related ID, and the third related ID is used to identify the second network element that establishes the second user plane connection with the first terminal.

[0825] Figure 6c is a schematic diagram of the structure of a second network element proposed in an embodiment of the present disclosure. As shown in Figure 6c, the second network element may include: at least one of a third transceiver module 631, a third processing module 632, etc.

[0826] In some embodiments, the third transceiver module 631 is used to receive second information sent by the first network element, where the second information includes a first related ID corresponding to the first routing ID; wherein the first information is used to indicate that a first user plane connection is established with the second network element corresponding to the first routing ID, or to indicate that the first user plane connection between the second network elements corresponding to the first routing ID is completed.

[0827] Optionally, the first routing ID includes at least one of the following:

[0828] a delayed routing ID received by the first terminal via a user plane;

[0829] a delayed routing ID received by the first terminal via a control plane;

[0830] a second routing ID received by the first terminal during a process of releasing a second user plane connection between the first terminal and the second network element;

[0831] The positioning service LCS session ID received by the first terminal via the user plane.

[0832] Optionally, the third transceiver module 631 is further configured to send third information to the first terminal via the user, where the third information includes a delayed routing ID and / or an LCS session ID.

[0833] Optionally, if the third information is used to request calling LCS periodically triggered positioning event reporting, the third information includes a delayed routing ID; or, if the third information is used for positioning service, the third information includes an LCS session ID.

[0834] Optionally, the third transceiver module 631 is further configured to send fourth information to the first network element, where the fourth information is used to request invoking an LCS periodically triggered positioning event report, and the fourth information includes a delayed routing ID.

[0835] Optionally, the above-mentioned third transceiver module 631 is also used to send sixth information to the first network element, and the sixth information is used to indicate the change of the second user plane connection between the first terminal and the second network element. The sixth information includes a second related ID, and the second related ID is used to identify the second network element that establishes the first user plane connection with the first terminal.

[0836] Optionally, the sixth information further includes at least one of the following information:

[0837] a third correlation ID, where the third correlation ID is used to identify a second network element that establishes a second user plane connection with the first terminal;

[0838] first indication information, used to instruct to change the second user plane connection;

[0839] Second indication information, used to instruct to release the second user plane connection;

[0840] The third indication information is used to indicate a condition for releasing the second user plane connection.

[0841] Optionally, the above-mentioned third transceiver module 631 is also used to receive the eighth information sent by the first network element, and the eighth information is used to request the release of the second user plane connection between the first terminal and the second network element. The eighth information includes a third related ID, and the third related ID is used to identify the second network element that establishes the second user plane connection with the first terminal.

[0842] 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 elements in the circuit; for example, in another implementation, the above-mentioned hardware circuit can be implemented by a programmable logic device (PLD), taking a field programmable gate array (FPGA) as an example, which 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.

[0843] All units or modules of the above devices can be implemented in the form of software called by the processor, or in the form of hardware circuits, or partially implemented in the form of software called by the processor, and the remaining part implemented in the form of hardware circuits. In the embodiment 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 hardware circuit is fixed or reconfigurable, such as a hardware circuit implemented by a processor as 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 to implement 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 ASIC, such as a neural network processing unit (NPU), a tensor processing unit (TPU), a deep learning processing unit (DPU), etc.

[0844] The present disclosure also provides an optional implementation scheme. The LMF (including LMF1 and LMF2) in the following optional embodiments may be an enhanced LMF or a SF (sensing function, perception function) for 6G.

[0845] S701. UE (which may correspond to the first terminal mentioned above) requests to establish a user plane connection for user plane positioning.

[0846] In some embodiments, the UE sets the payload container type to "UPP-CMI container", includes the user plane connection establishment request in the payload container, and may also include the routing ID (which may correspond to the first routing ID above) in the additional information IE of the UL NAS TRASPORT message (which may correspond to the first information above).

[0847] In some embodiments, the routing ID may be a deferred routing ID received in an LCS Periodic-Triggered Invoke Request message from a user plane or a control plane during the initiation and reporting of a positioning event.

[0848] In some embodiments, the routing ID may also be a routing ID received during the user plane connection release process initiated by the UE or LMF.

[0849] In some cases, the value of the Routing ID (between the UE and the AMF) is the same as the value of the LCS Session ID (used in the user plane) and the value of the Correlation ID (between the AMF and the LMF).

[0850] S702. AMF (which may correspond to the first network element mentioned above) receives the UPP-CMI container with the additional information IE. The AMF uses the routing ID contained in the additional information to identify the LMF and maps the routing ID to the correlation ID.

[0851] Optionally, the AMF may set the value of the Correlation ID to the value of the Routing ID.

[0852] In some embodiments, the AMF sends an Nlmf_Location_UPConfig message (which may correspond to the second information above), which includes a user plane connection establishment request (user plane connection establishment request) and a related ID of the LMF identified by the routing ID (which may correspond to the first related ID above).

[0853] In some embodiments, the AMF sends a Namf_Communication_N1MessageNotify message, which includes a user plane connection establishment request and a correlation ID of the LMF identified by the routing ID (which may correspond to the first correlation ID above).

[0854] S703. LMF accepts the use of LCS-UPP for user plane positioning and no user plane connection is established. The LMF calls Namf_Communication_N1N2MessageTransfer to AMF to transmit the user plane connection establishment command message and related ID received from AMF (which may correspond to the first related ID above).

[0855] S704. AMF maps the correlation ID to the routing ID.

[0856] In some embodiments, the AMF sets the Payload container type to "UPP-CMI container", includes the user plane connection release command in the Payload container, and includes the routing ID in the additional information of the DL NAS TRASPORT message.

[0857] S705. The UE establishes a user plane connection with the LMF.

[0858] In some embodiments, step S705 may also be performed after step S707.

[0859] S706. The UE sends a UL NAS TRANSPORT message (which may correspond to the first information above) including a user plane connection establishment complete message and a routing ID (which may correspond to the first correlation ID above) to the AMF.

[0860] S707. AMF maps the routing ID to the relevant ID, and sends a Namf_Communication_N1MessageNotify message (which may correspond to the second information above) including the relevant ID and the user plane connection establishment completion message to the LMF identified by the routing ID.

[0861] In some embodiments, the routing ID in the above step S701 is a deferred routing ID. Detailed description will be given below in conjunction with the content shown in FIG7b.

[0862] The present disclosure also provides an optional embodiment, wherein the method shown in FIG7b comprises the following steps:

[0863] S711a: The UE receives a delayed routing ID via a user plane.

[0864] In some embodiments, the UE receives a DL LCS-UP TRANPSPORT message (which may correspond to the third information above) including an LCS period triggered call request message from the LMF through the user plane, and the delayed routing ID is included in the LCS period triggered call request message.

[0865] Optionally, the delayed routing ID may identify a serving second network element or a default second network element.

[0866] Optionally, the DL LCS-UP TRANPSPORT message may further include an LCS session ID.

[0867] Optionally, the LCS session ID may identify the initiation and reporting session of the positioning event process.

[0868] Optionally, the LCS session ID may be set to "immediate Correlation ID" or "immediate Routing ID".

[0869] S711b. The UE receives a delayed routing ID via the control plane.

[0870] In some embodiments, S711b includes S711b-1 and S711b-2. Specifically,

[0871] S711b-1. AMF receives an LCS periodic triggered call request message including a delayed routing ID from LMF.

[0872] In some embodiments, the AMF receives an LCS periodic triggered invocation request message and a correlation ID from the LMF.

[0873] In some embodiments, the correlation ID may identify the LMF.

[0874] In some embodiments, the correlation ID may identify the LCS session.

[0875] In some embodiments, the correlation ID may also be an immediate routing ID.

[0876] In some embodiments, the AMF converts the correlation ID into a routing ID.

[0877] In some embodiments, the routing ID may be a converted immediate routing ID.

[0878] S711b-2. AMF sends a DL NAS TRANSPORT message to the UE (which may correspond to the fourth information above).

[0879] In some embodiments, the DL NAS TRANSPORT message includes an LCS period trigger invocation request for the delayed route ID.

[0880] In some embodiments, the DL NAS TRANSPORT message includes a route ID.

[0881] Optionally, the UE may receive an LCS periodic trigger invocation request message to obtain the delay routing ID in the message.

[0882] S712. The UE determines to establish a user plane connection with the LMF identified by the delayed routing ID received through the LCS periodically triggered invocation request message.

[0883] In some embodiments, the UE sets the route ID (which may correspond to the first route ID mentioned above) included in the UL NAS TRAPOSRT message as the delayed route ID.

[0884] In some embodiments, the routing ID in step S701 is the routing ID received from the LMF in the control plane. Detailed description is given below in conjunction with the content shown in FIG7c.

[0885] The present disclosure also provides an optional embodiment, wherein the method shown in FIG7c includes the following steps:

[0886] S721. The UE sends a UL NAS TRANSPORT message (which may correspond to the seventh information above) to the AMF with routing ID 1 (which may correspond to the third routing ID above).

[0887] In some embodiments, the UL NAS TRANSPORT message includes a user plane connection release request and route ID1.

[0888] Optionally, the routing ID1 may identify the LMF1 or the LCS session between the UE and the LMF1.

[0889] S722. AMF maps routing ID1 to correlation ID1 (which may correspond to the third correlation ID above), and forwards the Namf_Communication_N1MessageNotify message (which may correspond to the eighth information above) to LMF1 identified by correlation ID1.

[0890] In some embodiments, the Namf_Communication_N1MessageNotify message includes a user plane connection release request and a related ID1.

[0891] Optionally, the value of route ID1 may be the same as the value of correlation ID1.

[0892] It should be noted that, for the user plane connection release process triggered by LMF1, the above steps S721-S722 are skipped.

[0893] S723. LMF1 accepts and releases the user plane connection with the UE.

[0894] In some embodiments, if LMF1 finds that it is necessary to change LMF or re-establish the user plane connection between the UE and another LMF 2 (or LMF1), LMF1 or AMF can select LMF2 for the UE and include the correlation ID2 (which may correspond to the second correlation ID above) in the Namf_Communication_N1N2MessageTransfer message.

[0895] In some embodiments, LMF1 or AMF performs LMF selection.

[0896] Optionally, LMF1 may select LMF 2 and send an Nlmf_Location_UPNotify message (which may correspond to the sixth information above) including a connection reestablishment (or modification, termination) indication to the AMF. Optionally, the message may include the ID of LMF2. Optionally, the ID of LMF2 may be the related ID2.

[0897] For example: LMF1 sends an Nlmf_Location_UPNotify message to AMF, which includes: re-establishment indication information (which may correspond to the first indication information above) used to indicate the establishment of a first user plane connection between the UE and LMF2 (or LMF1).

[0898] The AMF may respond to LMF1 with an Nlmf_Location_UPConfig message including the ID of LMF2. Optionally, the ID of LMF2 may be Correlation ID2. Optionally, LMF2 may be selected by the AMF.

[0899] For example: AMF sends an Nlmf_Location_UPConfig message to LMF1, which includes: re-establishment indication information and the ID of LMF2.

[0900] In some embodiments, LMF1 sends a Namf_Communication_N1N2MessageTransfer message including a user plane connection release command message, correlation ID1 and correlation ID2 to AMF.

[0901] S724. AMF maps correlation ID1 and correlation ID2 to routing ID1 and routing ID2 respectively (which may correspond to the second routing ID mentioned above), and includes routing ID1 and routing ID2 in the additional information IE of the DL NAS TRANSPORT message (which may correspond to the fifth information mentioned above).

[0902] In some embodiments, a user plane connection release command message may be included in a UPP-CMI container of a DL NAS TRANSPORT message.

[0903] S725-S726. The UE receives routing ID1 and routing ID2 from the AMF. The UE releases the user plane connection with LMF1 (which may correspond to the second user plane connection above), and sends a user plane connection release complete message to LMF1 through the AMF. The relevant ID1 indicates LMF1.

[0904] S727. The UE determines to establish a user plane connection (which may correspond to the first user plane connection mentioned above) with the LMF identified by routing ID 2 (which may be LMF 2 or routing ID 2 may also identify LMF 1). The UE sends a user plane connection establishment request to the AMF with routing ID 2.

[0905] S728. The AMF maps the routing ID2 to the correlation ID2 and forwards the message to the LMF identified by the correlation ID2.

[0906] Optionally, the LMF identified by the related ID2 may be LMF1 or LMF2.

[0907] In some embodiments, the routing ID in the above step S701 is the LCS session ID received by the UE in the user plane. Detailed description will be given below in conjunction with the content shown in FIG7d.

[0908] The present disclosure also provides an optional embodiment, wherein the method shown in FIG7d comprises the following steps:

[0909] S731. The LMF sends a DL LCS-UP TRANSPORT message (which may correspond to the third information above) to the UE via the user plane.

[0910] In some embodiments, the DL LCS-UP TRANSPORT message includes an LPP message or a positioning supplementary service message for LCS session ID1 and LCS session ID2.

[0911] In some embodiments, LCS session ID 2 indicates LMF 2.

[0912] It should be noted that the LMF 2 selection process may include the relevant content about LMF 2 selection in the above step S723, which will not be repeated here.

[0913] S732. The UE uses LCS session ID2 (which may correspond to the LCS session ID mentioned above) as a routing ID (which may correspond to the first routing ID mentioned above) during the user plane connection establishment process initiated by the UE.

[0914] In a service-based architecture (SBA), interactions between network elements can be achieved by calling services, rather than sending request messages and response messages. In a non-SBA architecture, this is achieved by sending corresponding messages. For example, in SBA, sending an Nlmf_Location_DetermineLocation request corresponds to calling the Nlmf_Location_DetermineLocation service, and the Nlmf_Location_DetermineLocation response corresponds to the output after the Nlmf_Location_DetermineLocation service is executed. Of course, for other requests sent, the corresponding service can also be called for implementation, and the response corresponding to the request corresponds to the output after the corresponding service is called for execution. There is no specific limitation on the request and / or response.

[0915] Figure 8a is a schematic diagram of the structure of a communication device 900 proposed in an embodiment of the present disclosure. Communication device 900 can be a network element (such as the first network element or second network element described above), a terminal (such as user equipment), a chip, a chip system, or a processor that supports a network device 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. Communication device 900 can be used to implement the methods described in the above method embodiments. For details, please refer to the description of the above method embodiments.

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

[0917] In some embodiments, the communication device 900 further includes one or more transceivers 902. When the communication device 900 includes one or more transceivers 902, the transceiver 902 performs at least one of the communication steps such as sending and / or receiving in the above method (for example, at least one of steps S201, S203, and S204 shown in FIG. 2a, steps S211-1, S211-2, S213, and S214 shown in FIG. 2b, and steps S220-1, S220-2, S221-1, S221-2, S223, and S224 shown in FIG. 2c, but not limited thereto), and the processor 901 performs at least one of the other steps (for example, at least one of step S202 shown in FIG. 2a, step S212 shown in FIG. 2b, and step S222 shown in FIG. 2c, 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, terms such as transceiver, transceiver unit, transceiver, transceiver circuit, interface circuit, and interface can be replaced with each other, terms such as transmitter, transmitting unit, transmitter, and transmitting circuit can be replaced with each other, and terms such as receiver, receiving unit, receiver, and receiving circuit can be replaced with each other.

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

[0919] In some embodiments, the communication device 900 further includes one or more transceivers 903. When the communication device 900 includes one or more transceivers 903, the communication steps such as sending and receiving in the above method are performed by the transceiver 903, and the other steps are performed by the processor 901.

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

[0921] Optionally, the communication device 900 further includes one or more interface circuits 904, which are connected to the memory 902. The interface circuits 904 may be configured to receive signals from the memory 902 or other devices, and may be configured to send signals to the memory 902 or other devices. For example, the interface circuits 904 may read instructions stored in the memory 902 and send the instructions to the processor 901.

[0922] The communication device 900 described in the above embodiment may be a network device or a terminal, but the scope of the communication device 900 described in the embodiment of the present disclosure is not limited thereto, and the structure of the communication device 900 may not be limited by FIG8a. 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 and 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.

[0923] FIG8b is a schematic diagram of the structure of the chip 910 proposed in an embodiment of the present disclosure. If the communication device 900 can be a chip or a chip system, please refer to the schematic diagram of the structure of the chip 910 shown in FIG8b, but the present disclosure is not limited thereto.

[0924] The chip 910 includes one or more processors 911. The chip 910 is configured to execute any of the above methods.

[0925] In some embodiments, chip 910 also includes one or more interface circuits 912. Alternatively, terms such as interface circuit, interface, and transceiver pins may be used interchangeably. In some embodiments, chip 910 also includes one or more memories 913 for storing data. Alternatively, all or part of memory 913 may be located outside chip 910. Optionally, interface circuit 912 is connected to memory 913 and may be used to receive data from memory 913 or other devices, or may be used to send data to memory 913 or other devices. For example, interface circuit 912 may read data stored in memory 913 and send the data to processor 911.

[0926] In some embodiments, the interface circuit 912 performs at least one of the communication steps such as sending and / or receiving in the above method (for example, at least one of steps S201, S203, and S204 shown in FIG. 2a , steps S211-1, S211-2, S213, and S214 shown in FIG. 2b , and steps S220-1, S220-2, S221-1, S221-2, S223, and S224 shown in FIG. 2c , but not limited thereto). The interface circuit 912 performing the communication steps such as sending and / or receiving in the above method, for example, means that the interface circuit 912 performs data exchange between the processor 911, the chip 910, the memory 913, or the transceiver device. In some embodiments, the processor 911 performs at least one of the other steps (for example, at least one of step S202 shown in FIG. 2a , step S212 shown in FIG. 2b , and step S222 shown in FIG. 2c , but not limited thereto).

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

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

[0929] The technical solutions described in the embodiments of the present disclosure can be arbitrarily combined without conflict.

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

[0931] It should be understood that the present invention is not limited to the exact construction described above and shown in the drawings, and that various modifications and changes may be made without departing from the scope thereof. The scope of the present invention is limited only by the appended claims.

Claims

1. A communication system, characterized in that: include: A first network element and a second network element, wherein The first network element is configured to receive first information sent by a first terminal, where the first information includes a first routing identifier ID; The first network element is configured to send second information to a second network element corresponding to the first routing ID, where the second information includes a first correlation ID corresponding to the first routing ID; The first information is used to instruct the second network element corresponding to the first routing ID to establish a first user plane connection, or to indicate that the first user plane connection between the second network elements corresponding to the first routing ID is established.

2. The system according to claim 1, wherein: The first routing ID includes at least one of the following: Delayed routing ID received via the user plane; Delayed route ID received via the control plane; a second routing ID received during a second user plane connection release process between the first terminal and the second network element; Location service LCS session ID received via the user plane.

3. The system according to claim 2, characterized in that The second network element is further configured to send third information to the first terminal via the user, where the third information includes a delay routing ID and / or an LCS session ID.

4. The system according to claim 3, characterized in that If the third information is used to request the invocation of LCS periodically triggered positioning event reporting, the third information includes a delayed routing ID; or, if the third information is used for positioning service, the third information includes an LCS session ID.

5. The system according to claim 2, wherein: The first network element is further used to receive fourth information sent by the second network element, and send the fourth information to the first terminal through the control surface, where the fourth information is used to request to call the LCS period to trigger positioning event reporting, and the fourth information includes a delayed routing ID.

6. The system according to claim 2, wherein: The first network element is further configured to send fifth information to the first terminal via the control plane, where the fifth information is used to notify the first terminal to change a second user plane connection between the first terminal and the second network element, where the fifth information includes a second routing ID, where the second routing ID corresponds to the second network element that establishes the first user plane connection with the first terminal; The first terminal is further configured to set the second routing ID included in the fifth information as the first routing ID.

7. The system according to claim 6, characterized in that The first network element is further configured to receive sixth information sent by the second network element, where the sixth information is used to indicate a change in the second user plane connection, and the sixth information includes a second correlation ID, where the second correlation ID is used to identify the second network element that establishes the first user plane connection with the first terminal; The first network element is further configured to send the fifth information to the first terminal, where the second routing ID included in the fifth information corresponds to the second correlation ID.

8. The system according to claim 7, characterized in that The sixth information further includes at least one of the following information: a third correlation ID, where the third correlation ID is used to identify a second network element that establishes a second user plane connection with the first terminal; first indication information, used to instruct to change the second user plane connection; Second indication information, used to instruct to release the second user plane connection; third indication information, used to indicate a condition for releasing the second user plane connection; and / or, The fifth information further includes at least one of the following information: a third routing ID, where the third routing ID corresponds to a second network element establishing a second user plane connection with the first terminal; first indication information, used to instruct to change the second user plane connection; Second indication information, used to instruct to release the second user plane connection; The third indication information is used to indicate a condition for releasing the second user plane connection.

9. The system according to any one of claims 6 to 8, characterized in that The first network element is further configured to receive seventh information sent by the first terminal, where the seventh information is used to request release of the second user plane connection between the first terminal and the second network element, where the seventh information includes a third routing ID, where the third routing ID corresponds to the second network element that establishes the second user plane connection with the first terminal; The first network element is further used to send eighth information to the second network element corresponding to the third routing ID, where the eighth information includes a third related ID, and the third related ID is used to identify the second network element that establishes a second user plane connection with the first terminal.

10. A communication method, characterized in that: The method is performed by a first terminal, and includes: Sending first information to the first network element, where the first information includes a first routing identifier ID; The first information is used to instruct the second network element corresponding to the first routing ID to establish a first user plane connection, or to indicate that the first user plane connection between the second network elements corresponding to the first routing ID is established.

11. The method according to claim 10, characterized in that The first routing ID includes at least one of the following: Delayed routing ID received via the user plane; Delayed route ID received via the control plane; a second routing ID received during a second user plane connection release process between the first terminal and the second network element; Location service LCS session ID received via the user plane.

12. The method according to claim 11, characterized in that The method further comprises: receiving, via a user plane, third information sent by the second network element, where the third information includes a delayed routing ID and / or an LCS session ID; The first routing ID is set based on the delay routing ID and / or the LCS session ID included in the third information.

13. The method according to claim 12, characterized in that If the third information is used to request the invocation of LCS periodically triggered positioning event reporting, the third information includes a delayed routing ID; or, if the third information is used for positioning service, the third information includes an LCS session ID.

14. The method according to claim 11, characterized in that The method further comprises: receiving, via the control plane, fourth information sent by the first network element, where the fourth information is used to request invoking an LCS periodically triggered positioning event reporting, and the fourth information includes a delayed routing ID; The delayed route ID included in the fourth information is set as the first route ID.

15. The method according to claim 11, characterized in that The method further comprises: receiving, via a control plane, fifth information sent by the first network element, where the fifth information is used to notify the first terminal to change a second user plane connection between the first terminal and the second network element, where the fifth information includes a second routing ID, where the second routing ID corresponds to the second network element that establishes the first user plane connection with the first terminal; The first terminal is further configured to set the second routing ID included in the fifth information as the first routing ID.

16. The method according to claim 15, characterized in that The fifth information further includes at least one of the following information: a third routing ID, where the third routing ID corresponds to a second network element establishing a second user plane connection with the first terminal; first indication information, used to instruct to change the second user plane connection; Second indication information, used to instruct to release the second user plane connection; The third indication information is used to indicate a condition for releasing the second user plane connection.

17. The method according to claim 15 or 16, characterized in that The method further comprises: Send seventh information to the first network element, where the seventh information is used to request release of the second user plane connection between the first network element and the second network element, where the seventh information includes a third routing ID, and the third routing ID corresponds to the second network element that establishes the second user plane connection with the first terminal.

18. A communication method, characterized in that: The method is performed by a first network element, and the method includes: receiving first information sent by a first terminal, where the first information includes a first routing identifier ID; Sending second information to a second network element corresponding to the first routing ID, where the second information includes a first correlation ID corresponding to the first routing ID; The first information is used to indicate that a first user plane connection is established with the second network element, or is used to indicate that establishment of the first user plane connection with the second network element is completed.

19. The method according to claim 18, characterized in that The first routing ID includes at least one of the following: a delayed routing ID received by the first terminal via a user plane; a delayed routing ID received by the first terminal via a control plane; a second routing ID received by the first terminal during a process of releasing a second user plane connection between the first terminal and the second network element; The positioning service LCS session ID received by the first terminal via the user plane.

20. The method according to claim 19, characterized in that The method further comprises: receiving fourth information sent by the second network element, the fourth information being used to request invoking an LCS periodically triggered positioning event reporting, the fourth information including a delayed routing ID; The fourth information is sent to the first terminal through the control surface.

21. The method according to claim 19, wherein The method further comprises: receiving sixth information sent by a second network element, where the sixth information is used to indicate a change in a second user plane connection between the first terminal and the second network element, the sixth information including a second correlation ID, where the second correlation ID is used to identify the second network element that establishes the first user plane connection with the first terminal; The control plane sends fifth information to the first terminal, where the second routing ID included in the fifth information corresponds to the second correlation ID.

22. The method according to claim 21, characterized in that The sixth information further includes at least one of the following information: a third correlation ID, where the third correlation ID is used to identify a second network element that establishes a second user plane connection with the first terminal; first indication information, used to instruct to change the second user plane connection; Second indication information, used to instruct to release the second user plane connection; third indication information, used to indicate a condition for releasing the second user plane connection; and / or, The fifth information further includes at least one of the following information: a third routing ID, where the third routing ID corresponds to a second network element establishing a second user plane connection with the first terminal; first indication information, used to instruct to change the second user plane connection; Second indication information, used to instruct to release the second user plane connection; The third indication information is used to indicate a condition for releasing the second user plane connection.

23. The method according to claim 21 or 22, characterized in that The method further comprises: receiving seventh information sent by the first terminal, where the seventh information is used to request release of the second user plane connection between the first terminal and the second network element, the seventh information including a third routing ID, where the third routing ID corresponds to the second network element that establishes the second user plane connection with the first terminal; Eighth information is sent to the second network element corresponding to the third routing ID, where the eighth information includes a third correlation ID, and the third correlation ID is used to identify the second network element that establishes a second user plane connection with the first terminal.

24. A communication method, characterized in that: The method is performed by a second network element, and the method includes: receiving second information sent by the first network element, where the second information includes a first correlation ID corresponding to the first routing ID; The first information is used to instruct the second network element corresponding to the first routing ID to establish a first user plane connection, or to indicate that the first user plane connection between the second network elements corresponding to the first routing ID is established.

25. The method according to claim 24, characterized in that The first routing ID includes at least one of the following: a delayed routing ID received by the first terminal via a user plane; a delayed routing ID received by the first terminal via a control plane; a second routing ID received by the first terminal during a process of releasing a second user plane connection between the first terminal and the second network element; The positioning service LCS session ID received by the first terminal via the user plane.

26. The method according to claim 25, characterized in that The method further comprises: The third information is sent to the first terminal via the user, where the third information includes a delay routing ID and / or an LCS session ID.

27. The method according to claim 26, characterized in that If the third information is used to request the invocation of LCS periodically triggered positioning event reporting, the third information includes a delayed routing ID; or, if the third information is used for positioning service, the third information includes an LCS session ID.

28. The method according to claim 25, characterized in that The method further comprises: Sending fourth information to the first network element, where the fourth information is used to request calling the LCS periodically triggered positioning event reporting, and the fourth information includes a delayed routing ID.

29. The method according to claim 25, characterized in that The method further comprises: Send sixth information to the first network element, where the sixth information is used to indicate a change in the second user plane connection between the first terminal and the second network element, and the sixth information includes a second related ID, where the second related ID is used to identify the second network element that establishes the first user plane connection with the first terminal.

30. The method according to claim 29, wherein: The sixth information further includes at least one of the following information: a third correlation ID, where the third correlation ID is used to identify a second network element that establishes a second user plane connection with the first terminal; first indication information, used to instruct to change the second user plane connection; Second indication information, used to instruct to release the second user plane connection; The third indication information is used to indicate a condition for releasing the second user plane connection.

31. The method according to claim 29 or 30, characterized in that The method further comprises: Receive the eighth information sent by the first network element, where the eighth information is used to request the release of the second user plane connection between the first terminal and the second network element, and the eighth information includes a third related ID, where the third related ID is used to identify the second network element that establishes the second user plane connection with the first terminal.

32. A terminal, characterized in that: include: A first transceiver module is configured to send first information to a first network element, where the first information includes a first routing identifier ID; The first information is used to instruct the second network element corresponding to the first routing ID to establish a first user plane connection, or to indicate that the first user plane connection between the second network elements corresponding to the first routing ID is established.

33. A first network element, characterized in that: include: A second transceiver module is configured to receive first information sent by a first terminal, where the first information includes a first routing identifier ID; further configured to send second information to a second network element corresponding to the first routing ID, where the second information includes a first correlation ID corresponding to the first routing ID; The first information is used to indicate that a first user plane connection is established with the second network element, or is used to indicate that establishment of the first user plane connection with the second network element is completed.

34. A second network element, characterized in that: include: a third transceiver module, configured to receive second information sent by the first network element, where the second information includes a first correlation ID corresponding to the first routing ID; The first information is used to instruct the second network element corresponding to the first routing ID to establish a first user plane connection, or to indicate that the first user plane connection between the second network elements corresponding to the first routing ID is established.

35. A terminal, characterized in that: include: one or more processors; The processor is configured to execute the communication method according to any one of claims 10 to 17.

36. A first network element, characterized in that: include: one or more processors; The processor is configured to execute the communication method described in any one of claims 18 to 23.

37. A second network element, characterized in that: include: one or more processors; The processor is configured to execute the communication method described in any one of claims 24 to 31.

38. A computer-readable storage medium having a computer program stored thereon, characterized in that: The computer-readable storage medium stores executable instructions, which are loaded and executed by the processor to implement the communication method as described in any one of claims 10 to 17, or claims 18 to 23, or claims 24 to 31.

Images