Communication method, network element, terminal, communication system and storage medium

By passing the first notification and the first parameter in the 5G system, the terminal establishes or releases the user-side connection when specific conditions are met, solving the problem of resource waste and load increase caused by the terminal needing to maintain a connection for a long time, and achieving the effect of resource saving and communication load reduction.

WO2025091419A1PCT designated stage expired Publication Date: 2025-05-08BEIJING XIAOMI MOBILE SOFTWARE CO LTD
View PDF 5 Cites 0 Cited by

Patent Information

Application Number
PCT/CN2023/129449
Authority / Receiving Office
WO · WO
Patent Type
Applications
Current Assignee / Owner
Filing Date
2023-11-02
Publication Date
2025-05-08

AI Technical Summary

Technical Problem

In 5G systems, the terminal needs to maintain a user interface connection with the first network element for a long time, resulting in waste of resources and increased communication load.

Method used

By passing the first notification and the first parameter between the first network element, the second network element and the terminal, the terminal establishes or releases the user plane connection when the specific parameter conditions are met.

Benefits of technology

This reduces the number of user-plane connections that the terminal needs to maintain, saves the terminal's resources, and reduces the load of the communication system.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN2023129449_08052025_PF_FP_ABST
    Figure CN2023129449_08052025_PF_FP_ABST
Patent Text Reader

Abstract

The present disclosure relates to a communication method, a network element, a terminal, a communication system and a storage medium. The method comprises: sending to a second network element at least one of a first notification and a first parameter, so that the second network element sends to a terminal at least one of the first notification and the first parameter, wherein the first notification is used for instructing the terminal to establish a user plane connection with a first network element, and the first parameter comprises at least one of the following: a parameter related to establishing the user plane connection with the terminal, and a parameter related to releasing the user plane connection with the terminal. In the present disclosure, by means of sending to a terminal parameters for establishing and releasing a user plane connection, the terminal does not need to maintain the user plane connection for a long time, thereby saving on resources of the terminal.
Need to check novelty before this filing date? Find Prior Art

Description

Communication method, network element, terminal, communication system and storage medium Technical Field

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

[0002] Currently, in the field of wireless communication technology, a user plane connection can be established between a terminal and a location management function (LMF network element). The user plane connection is independent of the fifth generation mobile communication technology (5G mobile communication technology). th The connection between the 5G network and other network elements in the 5G Generation Mobile Communication Technology (5G) system can be strengthened, and user plane positioning can enable the 5G system to have a more efficient communication load. A single session can handle multiple transactions and support multiple positioning methods.

[0003] Summary of the Invention

[0004] The embodiments of the present disclosure provide a communication method, a network element, a terminal, a communication system, and a storage medium.

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

[0006] Sending at least one of the first notification and the first parameter to the second network element, so that the second network element sends at least one of the first notification and the first parameter to the terminal;

[0007] The first notification is used to instruct the terminal to establish a user plane connection with the first network element;

[0008] The first parameter includes at least one of the following:

[0009] Parameters related to establishing a user plane connection with the terminal;

[0010] Parameters related to the terminal releasing the user plane connection.

[0011] In a second aspect, an embodiment of the present disclosure provides a communication method, which is applied to a second network element. The method includes:

[0012] receiving at least one of a first notification and a first parameter sent by a first network element;

[0013] sending at least one of the first notification and the first parameter to a terminal;

[0014] The first notification is used to instruct the terminal to establish a user plane connection with the first network element;

[0015] The first parameter includes at least one of the following:

[0016] Parameters related to establishing a user plane connection with the terminal;

[0017] Parameters related to the terminal releasing the user plane connection.

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

[0019] receiving at least one of a first notification and a first parameter sent by a second network element;

[0020] The first notification and the first parameter sent by the second network element are received from the first network element;

[0021] The first notification is used to instruct the terminal to establish a user plane connection with the first network element;

[0022] The first parameter includes at least one of the following:

[0023] Parameters related to establishing a user plane connection with the terminal;

[0024] Parameters related to the terminal releasing the user plane connection.

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

[0026] a transceiver module, configured to send at least one of the first notification and the first parameter to the second network element, so that the second network element sends at least one of the first notification and the first parameter to the terminal;

[0027] The first notification is used to instruct the terminal to establish a user plane connection with the first network element;

[0028] The first parameter includes at least one of the following:

[0029] Parameters related to establishing a user plane connection with the terminal;

[0030] Parameters related to the terminal releasing the user plane connection.

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

[0032] a transceiver module, configured to receive at least one of a first notification and a first parameter sent by a first network element, and

[0033] sending at least one of the first notification and the first parameter to a terminal;

[0034] The first notification is used to instruct the terminal to establish a user plane connection with the first network element;

[0035] The first parameter includes at least one of the following:

[0036] Parameters related to establishing a user plane connection with the terminal;

[0037] Parameters related to the terminal releasing the user plane connection.

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

[0039] a transceiver module, configured to receive at least one of a first notification and a first parameter sent by a second network element;

[0040] The first notification and the first parameter sent by the second network element are received from the first network element;

[0041] The first notification is used to instruct the terminal to establish a user plane connection with the first network element;

[0042] The first parameter includes at least one of the following:

[0043] Parameters related to establishing a user plane connection with the terminal;

[0044] Parameters related to the terminal releasing the user plane connection.

[0045] In the seventh aspect, an embodiment of the present disclosure proposes a communication system, including a first network element, a second network element, and a terminal; wherein the first network element is configured to implement the communication method of any one of the first aspect of the embodiment of the present disclosure; the second network element is configured to implement the communication method of any one of the second aspect of the embodiment of the present disclosure; and the terminal is configured to implement the communication method of any one of the third aspect of the embodiment of the present disclosure.

[0046] In an eighth aspect, an embodiment of the present disclosure proposes a storage medium, which, when an instruction is executed on a communication device, enables the communication device to execute any one of the communication methods of the embodiments of the present disclosure. BRIEF DESCRIPTION OF THE DRAWINGS

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

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

[0049] FIG1B is an interactive schematic diagram of a communication method in related art;

[0050] FIG2 is one of interactive schematic diagrams illustrating a communication method according to an embodiment of the present disclosure;

[0051] FIG3A is a second interactive schematic diagram of a communication method according to an embodiment of the present disclosure;

[0052] FIG3B is a third interactive schematic diagram of a communication method according to an embodiment of the present disclosure;

[0053] FIG3C is a fourth interactive schematic diagram of a communication method according to an embodiment of the present disclosure;

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

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

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

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

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

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

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

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

[0062] The embodiments of the present disclosure provide a communication method, a network element, a terminal, a communication system, and a storage medium.

[0063] In a first aspect, an embodiment of the present disclosure provides a communication method, the method comprising:

[0064] Sending at least one of the first notification and the first parameter to the second network element, so that the second network element sends at least one of the first notification and the first parameter to the terminal;

[0065] The first notification is used to instruct the terminal to establish a user plane connection with the first network element;

[0066] The first parameter includes at least one of the following:

[0067] Parameters related to establishing a user plane connection with the terminal;

[0068] Parameters related to the terminal releasing the user plane connection.

[0069] In the above embodiment, by sending at least one of the first notification and the first parameter to the terminal, the terminal establishes or releases the user plane connection only when the first parameter is met. Therefore, the terminal does not need to maintain the user plane connection with the first network element for a long time, saving the terminal's resources.

[0070] In combination with some embodiments of the first aspect, in some embodiments, the second network element is an AMF network element or a UPF network element.

[0071] In the above embodiment, the AMF network element forwards at least one of the first notification and the first parameter to the terminal through a control plane message, or the UPF network element forwards at least one of the first notification and the first parameter to the terminal through a user plane message, so that the terminal can obtain at least one of the first notification and the first parameter through multiple channels.

[0072] In conjunction with some embodiments of the first aspect, in some embodiments, the second network element is an AMF network element;

[0073] The sending at least one of the first notification and the first parameter to the second network element includes:

[0074] Determine to use a user plane connection, and send at least one of user plane information and the first parameter to the AMF network element;

[0075] Receive a first message, and send the first notification to the AMF network element, where the first message is used to indicate that the terminal has successfully established a PDU session for user plane positioning.

[0076] In the above embodiment, the AMF network element sends at least one of the first parameter and the user plane information to the terminal; in this way, the first parameter can be sent to the terminal in advance instead of being sent to the terminal at the same time as the first notification, thereby reducing the pressure on the terminal to process messages.

[0077] In combination with some embodiments of the first aspect, in some embodiments, sending at least one of the user plane information and the first parameter to the AMF network element includes:

[0078] sending the user plane information and the first parameter in different messages respectively, or;

[0079] sending the user plane information and the first parameter in the same message, where the user plane information includes the first parameter, or;

[0080] The user plane information and the first parameter are sent in the same message, and the user plane information does not include the first parameter.

[0081] In the above embodiment, the user plane information and the first parameter are sent in different messages or the same message. In this way, the user plane information and the first parameter can be sent more flexibly, so that the terminal can obtain the user plane information and the first parameter in a diversified manner.

[0082] In conjunction with some embodiments of the first aspect, in some embodiments, sending at least one of the first notification and the first parameter to the second network element includes:

[0083] Determine to use the user plane connection and send user plane information to the AMF network element;

[0084] Receive a first message, and send at least one of the first notification and a first parameter to the second network element, where the first message is used to indicate that the terminal successfully establishes a PDU session for user plane positioning.

[0085] In the above embodiment, after the terminal successfully establishes a PDU session for user plane positioning, it sends a first notification and at least one of the first parameters to the second network element; in this way, the AMF network element sends the first notification and at least one of the first parameters to the terminal through a control plane message, or the UPF network element sends the first notification and at least one of the first notification to the terminal through a user plane message, so that the terminal can obtain at least one of the first notification and the first parameter through multiple channels.

[0086] In conjunction with some embodiments of the first aspect, in some embodiments, sending at least one of the first notification and the first parameter to the second network element includes:

[0087] sending the first notification and the first parameter in different messages respectively, or;

[0088] sending the first notification and the first parameter in the same message, where the first notification includes the first parameter, or;

[0089] The first notification and the first parameter are sent in the same message, and the first notification does not include the first parameter.

[0090] In the above embodiment, the first notification and the first parameter are sent in different messages or the same message. In this way, the first notification and the first parameter can be sent more flexibly, so that the terminal can obtain the first notification and the first parameter in a diversified manner.

[0091] In conjunction with some embodiments of the first aspect, in some embodiments, the parameters related to establishing a user plane connection with the terminal include at least one of the following:

[0092] The time point for periodically establishing user plane connections;

[0093] The time period for periodically establishing user plane connections;

[0094] The number of times user plane connections are periodically established;

[0095] A timer for periodically establishing user plane connections;

[0096] Trigger the LCS process to establish a user plane connection;

[0097] An event that triggers the establishment of a user plane connection;

[0098] The time point when the user plane connection is triggered;

[0099] The time period for triggering establishment of a user plane connection;

[0100] The area that triggers the establishment of a user plane connection;

[0101] Tracking area identifier that triggers establishment of a user plane connection;

[0102] The geographical location that triggers the establishment of a user plane connection.

[0103] In the above embodiment, parameters related to establishing a user plane connection are sent to the terminal; in this way, the terminal can trigger the establishment of a user plane connection with the first network element based on the received parameters when the conditions for establishing a user plane connection are met; in this way, the terminal can establish a user plane connection with the first network element under specific conditions without having to establish a user plane connection with the first network element in advance, thereby saving terminal resources.

[0104] In conjunction with some embodiments of the first aspect, in some embodiments, the parameters related to the terminal releasing the user plane connection include at least one of the following:

[0105] The time point for periodically releasing the user plane connection;

[0106] The time period for periodically releasing the user plane connection;

[0107] The number of times the user plane connection is periodically released;

[0108] A timer for periodically releasing user plane connections;

[0109] Trigger the LCS process of releasing the user plane connection;

[0110] An event that triggers the release of the user plane connection;

[0111] The time point when the user plane connection is released is triggered;

[0112] The time period for triggering the release of the user plane connection;

[0113] The area that triggers the release of the user plane connection;

[0114] Tracking area identifier that triggers release of the user plane connection;

[0115] The geographical location that triggers the release of the user plane connection;

[0116] Method for releasing user plane connections.

[0117] In the above embodiment, parameters related to releasing the user plane connection are sent to the terminal; in this way, the terminal can trigger the release of the user plane connection with the first network element based on the received parameters and when the conditions for releasing the user plane connection are met; in this way, the terminal can release the user plane connection with the first network element under specific conditions without maintaining the user plane connection with the first network element for a long time, thereby saving terminal resources.

[0118] In conjunction with some embodiments of the first aspect, in some embodiments, the manner of releasing the user plane connection includes at least one of the following:

[0119] The terminal sends all data packets to the LMF network element and releases the current user plane connection;

[0120] The terminal releases the current user plane connection and discards unsent data packets;

[0121] After the terminal releases the current user plane connection, it creates a new user plane connection;

[0122] After the terminal creates a new user plane connection, it releases the current user plane connection.

[0123] In the above embodiment, the user plane connection mode is sent to the terminal; thus, the terminal can more reasonably select a mode for releasing the user plane connection according to the received release mode.

[0124] In a second aspect, an embodiment of the present disclosure provides a communication method, which is applied to a second network element. The method includes:

[0125] receiving at least one of a first notification and a first parameter sent by a first network element;

[0126] sending at least one of the first notification and the first parameter to a terminal;

[0127] The first notification is used to instruct the terminal to establish a user plane connection with the first network element;

[0128] The first parameter includes at least one of the following:

[0129] Parameters related to establishing a user plane connection with the terminal;

[0130] Parameters related to the terminal releasing the user plane connection.

[0131] In the above embodiment, by sending at least one of the first notification and the first parameter to the terminal, the terminal establishes or releases the user plane connection only when the first parameter is met. Therefore, the terminal does not need to maintain the user plane connection with the first network element for a long time, saving the terminal's resources.

[0132] In combination with some embodiments of the second aspect, in some embodiments, the second network element is an AMF network element or a UPF network element.

[0133] In the above embodiment, the AMF network element forwards at least one of the first notification and the first parameter to the terminal through a control plane message, or the UPF network element forwards at least one of the first notification and the first parameter to the terminal through a user plane message, so that the terminal can obtain at least one of the first notification and the first parameter through multiple channels.

[0134] In conjunction with some embodiments of the second aspect, in some embodiments, the second network element is an AMF network element;

[0135] The receiving at least one of the first notification and the first parameter sent by the first network element includes:

[0136] receiving at least one of the user plane information and the first parameter sent by the first network element;

[0137] receiving a first notification sent by the first network element;

[0138] The user plane information and the first parameter are determined by the first network element to be sent using a user plane connection;

[0139] The first notification is sent by the first network element after receiving a first message, where the first message is used to indicate that the terminal has successfully established a PDU session for user plane positioning.

[0140] In the above embodiment, the AMF network element sends at least one of the first parameter and the user plane information to the terminal; in this way, the first parameter can be sent to the terminal in advance instead of being sent to the terminal at the same time as the first notification, thereby reducing the pressure on the terminal to process messages.

[0141] In combination with some embodiments of the second aspect, in some embodiments, the AMF network element receives at least one of the user plane information and the first parameter sent by the first network element, including:

[0142] receiving the user plane information and the first parameter in different messages respectively, or;

[0143] receiving the user plane information and the first parameter in the same message, where the user plane information includes the first parameter, or;

[0144] The user plane information and the first parameter are received in the same message, where the user plane information does not include the first parameter.

[0145] In the above embodiment, the user plane information and the first parameter are sent in different messages or the same message. In this way, the user plane information and the first parameter can be sent more flexibly, so that the terminal can obtain the user plane information and the first parameter in a diversified manner.

[0146] In conjunction with some embodiments of the second aspect, in some embodiments, sending at least one of the first notification and the first parameter to the terminal includes:

[0147] Send at least one of the user plane information, the first parameter, and the first notification to a terminal.

[0148] In the above embodiment, at least one of the user plane information, the first parameter and the first notification is sent to the terminal; thus, repeated sending of information to the terminal can be avoided based on the information currently obtained by the terminal, thereby reducing the pressure on the terminal to process information.

[0149] In conjunction with some embodiments of the second aspect, in some embodiments, sending at least one of the user plane information and the first parameter to the terminal includes:

[0150] sending the user plane information and the first parameter to the terminal in different messages respectively, or;

[0151] sending the user plane information and the first parameter to the terminal in the same message, where the user plane information includes the first parameter, or;

[0152] The user plane information and the first parameter are sent to the terminal in the same message, where the user plane information does not include the first parameter.

[0153] In the above embodiment, the first notification and the first parameter are sent in different messages or the same message. In this way, the user plane information and the first parameter can be sent more flexibly, so that the terminal can obtain the user plane information and the first parameter in a diversified manner.

[0154] In combination with some embodiments of the second aspect, in some embodiments, the first notification and the first parameter are sent after the first network element determines to use the user plane connection, sends user plane information to the AMF network element, and receives the first message.

[0155] In the above embodiment, after establishing a PDU session for positioning between the terminal and the UPF network element, the first notification and the first parameter are sent to the terminal; in this way, the first notification and the first parameter can be sent to the terminal using a control plane message, and the first notification and the first parameter can also be sent to the terminal using a user plane message, so that the first notification and the first parameter can be sent to the terminal through multiple channels, thereby increasing the fault tolerance of the terminal in obtaining the first notification and the first parameter.

[0156] In conjunction with some embodiments of the second aspect, in some embodiments, receiving at least one of the first notification and the first parameter sent by the first network element includes:

[0157] receiving the first notification and the first parameter in different messages respectively, or;

[0158] receiving the first notification and the first parameter in the same message, wherein the first notification includes the first parameter, or;

[0159] The first notification and the first parameter are received in a same message, the first notification excluding the first parameter.

[0160] In the above embodiment, the first notification and the first parameter are received in different messages or the same message; in this way, the first notification and the first parameter can be received more flexibly, so that the way in which the second network element obtains the first notification and the first parameter is diversified, thereby increasing the fault tolerance of the second network element in obtaining the first notification and the first parameter.

[0161] In conjunction with some embodiments of the second aspect, in some embodiments, sending at least one of the first notification and the first parameter to the terminal includes:

[0162] sending the first notification and the first parameter to the terminal in different messages respectively, or;

[0163] sending the first notification and the first parameter to the terminal in the same message, where the first notification includes the first parameter, or;

[0164] The first notification and the first parameter are sent to the terminal in a same message, where the first notification does not include the first parameter.

[0165] In the above embodiment, the first notification and the first parameter are sent in different messages or the same message; in this way, the first notification and the first parameter can be sent more flexibly, so that the terminal obtains the first notification and the first parameter in a diversified manner, thereby increasing the fault tolerance of the terminal in obtaining the first notification and the first parameter.

[0166] In conjunction with some embodiments of the second aspect, in some embodiments, the parameters related to establishing a user plane connection with the terminal include at least one of the following:

[0167] The time point for periodically establishing user plane connections;

[0168] The time period for periodically establishing user plane connections;

[0169] The number of times user plane connections are periodically established;

[0170] A timer for periodically establishing user plane connections;

[0171] Trigger the LCS process to establish a user plane connection;

[0172] An event that triggers the establishment of a user plane connection;

[0173] The time point when the user plane connection is triggered;

[0174] The time period for triggering establishment of a user plane connection;

[0175] The area that triggers the establishment of a user plane connection;

[0176] Tracking area identifier that triggers establishment of a user plane connection;

[0177] The geographical location that triggers the establishment of a user plane connection.

[0178] In the above embodiment, parameters related to establishing a user plane connection are sent to the terminal; in this way, the terminal can trigger the establishment of a user plane connection with the first network element based on the received parameters when the conditions for establishing a user plane connection are met; in this way, the terminal can establish a user plane connection with the first network element under specific conditions without having to establish a user plane connection with the first network element in advance, thereby saving terminal resources.

[0179] In conjunction with some embodiments of the second aspect, in some embodiments, the parameters related to the terminal releasing the user plane connection include at least one of the following:

[0180] The time point for periodically releasing the user plane connection;

[0181] The time period for periodically releasing the user plane connection;

[0182] The number of times the user plane connection is periodically released;

[0183] A timer for periodically releasing user plane connections;

[0184] Trigger the LCS process of releasing the user plane connection;

[0185] An event that triggers the release of the user plane connection;

[0186] The time point when the user plane connection is released is triggered;

[0187] The time period for triggering the release of the user plane connection;

[0188] The area that triggers the release of the user plane connection;

[0189] Tracking area identifier that triggers release of the user plane connection;

[0190] The geographical location that triggers the release of the user plane connection;

[0191] Method for releasing user plane connections.

[0192] In the above embodiment, parameters related to releasing the user plane connection are sent to the terminal; in this way, the terminal can trigger the release of the user plane connection with the first network element based on the received parameters and when the conditions for releasing the user plane connection are met; in this way, the terminal can release the user plane connection with the first network element under specific conditions without maintaining the user plane connection with the first network element for a long time, thereby saving terminal resources.

[0193] In conjunction with some embodiments of the second aspect, in some embodiments, the manner of releasing the user plane connection includes at least one of the following:

[0194] The terminal sends all data packets to the LMF network element and releases the current user plane connection;

[0195] The terminal releases the current user plane connection and discards unsent data packets;

[0196] After the terminal releases the current user plane connection, it creates a new user plane connection;

[0197] After the terminal creates a new user plane connection, it releases the current user plane connection.

[0198] In the above embodiment, by sending at least one of the first notification and the first parameter to the terminal, the terminal establishes or releases the user plane connection only when the first parameter is met. Therefore, the terminal does not need to maintain the user plane connection with the first network element for a long time, saving the terminal's resources.

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

[0200] receiving at least one of a first notification and a first parameter sent by a second network element;

[0201] The first notification and the first parameter sent by the second network element are received from the first network element;

[0202] The first notification is used to instruct the terminal to establish a user plane connection with the first network element;

[0203] The first parameter includes at least one of the following:

[0204] Parameters related to establishing a user plane connection with the terminal;

[0205] Parameters related to the terminal releasing the user plane connection.

[0206] In the above embodiment, by sending at least one of the first notification and the first parameter to the terminal, the terminal establishes or releases the user plane connection only when the first parameter is met. Therefore, the terminal does not need to maintain the user plane connection with the first network element for a long time, saving the terminal's resources.

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

[0208] At least one of establishing a user plane connection and releasing the user plane connection is performed according to the first notification and the first parameter.

[0209] In the above embodiment, the terminal establishes or releases the user plane connection only when the first parameter is met based on the received first notification and the first parameter. Therefore, the terminal does not need to maintain the user plane connection with the first network element for a long time, saving terminal resources.

[0210] In combination with some embodiments of the third aspect, in some embodiments, the second network element is an AMF network element or a UPF network element.

[0211] In the above embodiment, the AMF network element forwards at least one of the first notification and the first parameter to the terminal through a control plane message, or the UPF network element forwards at least one of the first notification and the first parameter to the terminal through a user plane message, so that the terminal can obtain at least one of the first notification and the first parameter through multiple channels, thereby increasing the fault tolerance of the terminal in obtaining the first notification and the first parameter.

[0212] In conjunction with some embodiments of the third aspect, in some embodiments, the second network element is an AMF network element;

[0213] The receiving at least one of the first notification and the first parameter sent by the second network element includes:

[0214] Receive at least one of the user plane information, the first parameter, and the first notification sent by the second network element.

[0215] In the above embodiment, the AMF network element sends at least one of the first parameter and the user plane information to the terminal; in this way, the first parameter can be sent to the terminal in advance instead of being sent to the terminal at the same time as the first notification, thereby reducing the pressure on the terminal to process messages.

[0216] In conjunction with some embodiments of the third aspect, in some embodiments, the receiving at least one of the user plane information and the first parameter sent by the second network element includes:

[0217] receiving the user plane information and the first parameter in different messages respectively, or;

[0218] receiving the user plane information and the first parameter in the same message, where the user plane information includes the first parameter, or;

[0219] The user plane information and the first parameter are received in the same message, where the user plane information does not include the first parameter.

[0220] In the above embodiment, the user plane information and the first parameter are sent in different messages or the same message; in this way, the user plane information and the first parameter can be sent more flexibly, so that the terminal obtains the user plane information and the first parameter in a diversified manner, thereby increasing the success rate of the terminal in obtaining the user plane information and the first parameter.

[0221] In combination with some embodiments of the third aspect, in some embodiments, the first notification and the first parameter are sent to the second network element after the first network element determines to use the user plane connection, sends user plane information to the AMF network element, and receives the first message.

[0222] In the above embodiment, after receiving the first message, the first network element determines that there is a PDU session for positioning between the terminal and the UPF network element; in this way, the first network element can send the first notification and the first parameter to the terminal through a user plane message or a control plane message, thereby increasing the fault tolerance of the terminal in obtaining the first notification and the first parameter.

[0223] In conjunction with some embodiments of the third aspect, in some embodiments, receiving at least one of the first notification and the first parameter sent by the second network element includes:

[0224] receiving the first notification and the first parameter in different messages respectively, or;

[0225] receiving the first notification and the first parameter in the same message, wherein the first notification includes the first parameter, or;

[0226] The first notification and the first parameter are received in a same message, wherein the first notification does not include the first parameter.

[0227] In the above embodiment, after the terminal successfully establishes a PDU session for user plane positioning, it sends a first notification and at least one of the first parameters to the second network element; in this way, the AMF network element sends the first notification and at least one of the first parameters to the terminal through a control plane message, or the UPF network element sends the first notification and at least one of the first parameters to the terminal through a user plane message, so that the terminal can obtain at least one of the first notification and the first parameter through multiple channels, thereby increasing the success rate of the terminal in obtaining the first notification.

[0228] In conjunction with some embodiments of the third aspect, in some embodiments, the parameters related to establishing a user plane connection with the terminal include at least one of the following:

[0229] The time point for periodically establishing user plane connections;

[0230] The time period for periodically establishing user plane connections;

[0231] The number of times user plane connections are periodically established;

[0232] A timer for periodically establishing user plane connections;

[0233] Trigger the LCS process to establish a user plane connection;

[0234] An event that triggers the establishment of a user plane connection;

[0235] The time point when the user plane connection is triggered;

[0236] The time period for triggering establishment of a user plane connection;

[0237] The area that triggers the establishment of a user plane connection;

[0238] Tracking area identifier that triggers establishment of a user plane connection;

[0239] The geographical location that triggers the establishment of a user plane connection.

[0240] In the above embodiment, parameters related to establishing a user plane connection are sent to the terminal; in this way, the terminal can trigger the establishment of a user plane connection with the first network element based on the received parameters when the conditions for establishing a user plane connection are met; in this way, the terminal can establish a user plane connection with the first network element under specific conditions without having to establish a user plane connection with the first network element in advance, thereby saving terminal resources.

[0241] In conjunction with some embodiments of the third aspect, in some embodiments, the parameters related to the terminal releasing the user plane connection include at least one of the following:

[0242] The time point for periodically releasing the user plane connection;

[0243] The time period for periodically releasing the user plane connection;

[0244] The number of times the user plane connection is periodically released;

[0245] A timer for periodically releasing user plane connections;

[0246] Trigger the LCS process of releasing the user plane connection;

[0247] An event that triggers the release of the user plane connection;

[0248] The time point when the user plane connection is released is triggered;

[0249] The time period for triggering the release of the user plane connection;

[0250] The area that triggers the release of the user plane connection;

[0251] Tracking area identifier that triggers release of the user plane connection;

[0252] The geographical location that triggers the release of the user plane connection;

[0253] Method for releasing user plane connections.

[0254] In the above embodiment, parameters related to releasing the user plane connection are sent to the terminal; in this way, the terminal can trigger the release of the user plane connection with the first network element based on the received parameters and when the conditions for releasing the user plane connection are met; in this way, the terminal can release the user plane connection with the first network element under specific conditions without maintaining the user plane connection with the first network element for a long time, thereby saving terminal resources.

[0255] In conjunction with some embodiments of the third aspect, in some embodiments, the manner of releasing the user plane connection includes at least one of the following:

[0256] The terminal sends all data packets to the LMF network element and releases the current user plane connection;

[0257] The terminal releases the current user plane connection and discards unsent data packets;

[0258] After the terminal releases the current user plane connection, it creates a new user plane connection;

[0259] After the terminal creates a new user plane connection, it releases the current user plane connection.

[0260] In the above embodiment, the user plane connection mode is sent to the terminal; thus, the terminal can more reasonably select a mode for releasing the user plane connection according to the received release mode.

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

[0262] a transceiver module, configured to send at least one of the first notification and the first parameter to the second network element, so that the second network element sends at least one of the first notification and the first parameter to the terminal;

[0263] The first notification is used to instruct the terminal to establish a user plane connection with the first network element;

[0264] The first parameter includes at least one of the following:

[0265] Parameters related to establishing a user plane connection with the terminal;

[0266] Parameters related to the terminal releasing the user plane connection.

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

[0268] a transceiver module, configured to receive at least one of a first notification and a first parameter sent by a first network element, and

[0269] sending at least one of the first notification and the first parameter to a terminal;

[0270] The first notification is used to instruct the terminal to establish a user plane connection with the first network element;

[0271] The first parameter includes at least one of the following:

[0272] Parameters related to establishing a user plane connection with the terminal;

[0273] Parameters related to the terminal releasing the user plane connection.

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

[0275] a transceiver module, configured to receive at least one of a first notification and a first parameter sent by a second network element;

[0276] The first notification and the first parameter sent by the second network element are received from the first network element;

[0277] The first notification is used to instruct the terminal to establish a user plane connection with the first network element;

[0278] The first parameter includes at least one of the following:

[0279] Parameters related to establishing a user plane connection with the terminal;

[0280] Parameters related to the terminal releasing the user plane connection.

[0281] In the seventh aspect, an embodiment of the present disclosure proposes a communication system, including a first network element, a second network element, and a terminal; wherein the first network element is configured to implement the communication method of any one of the first aspect, the second network element is configured to implement the communication method of any one of the first aspect, and the terminal is configured to implement the communication method of any one of the third aspect.

[0282] In an eighth aspect, an embodiment of the present disclosure proposes a storage medium, which, when an instruction is executed on a communication device, enables the communication device to execute a communication method as described in any one of the first, second, and third aspects.

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

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

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

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

[0287] The embodiments of the present disclosure provide a communication method, a network element, a terminal, a communication system, and a storage medium. In some embodiments, the terms communication method, signal transmission method, wireless frame transmission method, etc. are interchangeable, and the terms information processing system, communication system, etc. are interchangeable.

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

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

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

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

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

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

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

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

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

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

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

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

[0300] In some embodiments, “access network device (AN device)”, “radio access network device (radio

[0301] The terms 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”, and “bandwidth part (BWP)” are used interchangeably.

[0302] In some embodiments, the terms "terminal", "terminal device", "user equipment (terminal)", "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.

[0303] In some embodiments, the access network device, the core network device, or the network device can be replaced by a terminal. For example, the various embodiments of the present disclosure can also be applied to a structure in which the communication between the access network device, the core network device, or the network device and the terminal is replaced by communication between multiple terminals (for example, it can also be called 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, language such as "uplink" and "downlink" can also be replaced by language corresponding to communication between terminals (for example, "side"). For example, uplink channels, downlink channels, etc. can be replaced by side channels, and uplinks, downlinks, etc. can be replaced by side links.

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

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

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

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

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

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

[0310] In some embodiments, "predetermined" and "preset" can be interpreted as pre-specified in a protocol, etc., or can be interpreted as a pre-set action performed by a device, etc.

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

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

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

[0314] FIG1A is an exemplary schematic diagram showing the architecture of a communication system according to an embodiment of the present disclosure. As shown in FIG1A , a communication system 100 includes a first network element, a second network element, and a terminal.

[0315] In some embodiments, the terminal 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. It is understandable 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. A person skilled in the art will know that with the evolution of the system architecture,

[0316] With the emergence of new business scenarios, the technical solutions proposed in the embodiments of the present disclosure are also applicable to similar technical problems. The following embodiments of the present disclosure can be applied to the communication system 100 shown in Figure 1A, or part of the subject, but are not limited thereto. The subjects shown in Figure 1A are examples. The communication system may include all or part of the subjects in Figure 1A, or may include other subjects other than Figure 1A. The number and form of each subject are arbitrary. The connection relationship between the subjects is an example. The subjects may be connected or disconnected. The connection may be in any manner, which may be a direct connection or an indirect connection, and may be a wired connection or a wireless connection.

[0317] 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), 6th generation mobile communication system (6G), 5G New Radio (NR), Future Radio Access (FRA), New-Radio Access Technology (RAT), New Radio (NR), New Radio Access (NX), Future Generation Radio Access (FX), Global System for Mobile Communications (GSM (registered trademark)), CDMA2000, Ultra Mobile Broadband (UMB), IEEE 802.11 (Wi-Fi (registered trademark)), IEEE 802.16 (WiMAX (registered trademark)), IEEE 802.20, Ultra-WideBand (UWB), Bluetooth (registered trademark), Public Land Mobile Network (PLMN) networks, Device-to-Device (D2D) systems, Machine-to-Machine (M2M) systems, Internet of Things (IoT) systems, Vehicle-to-Everything (V2X), systems utilizing other communication methods, and next-generation systems based on and extending these methods. Furthermore, multiple systems may be combined (for example, a combination of LTE or LTE-A with 5G).

[0318] In some embodiments, the first network element may be a location management function (LMF) network element.

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

[0320] In some embodiments, the LMF network element can send its user plane information, such as an IP address or a fully qualified domain name (FQDN), to the terminal via a DL NAS TRANSPORT message of an Access and Mobility Management Function (AMF) network element. If the LMF network element sends its FQDN to the terminal, a DNS server / resolver is used to resolve the IP address of the LMF network element (e.g., EASDF or local DNS for local LMF network element address resolution). The terminal uses a terminal route selection policy (URSP) including user plane positioning related PDU session parameters, such as a dedicated data network name (DNN) and network slice selection assistance information (S-NSSAI) to establish a PDU session for user plane positioning. The Session Management Function (SMF) shall select the PDU Session Anchor-User Plane Function (PSA-UPF) network element connected to the LMF network element for the PDU session based on the S-NSSAI, DNN and terminal location information. The PDU Session Anchor-User Plane Function (PSA-UPF) network element shall be located at the central site or the local site.

[0321] In some embodiments, session interruption for local LMF services for user plane positioning can be supported by using the IP address / network prefix of the local LMF and its DNAI to pre-configure the Session Management Function (SMF), which is used to locate the dedicated PDU session in a specific service area where the local PDU Session Anchor (PSA) and UL CL / BP are inserted.

[0322] In some embodiments, if the target terminal does not have a user plane connection with the LMF network element, the LMF network element may trigger the establishment of a user plane connection after receiving a location request from the AMF network element. If the terminal supports user plane positioning, the AMF network element also subscribes to the status of the LCS user plane connection of the target terminal from the LMF network element using the Nlmf_Location_UP Subscribe message.

[0323] FIG1B is an interactive diagram of a communication method of the related art. As shown in FIG1B , the method includes the following steps:

[0324] Step S1101: The LMF network element determines to use the user plane for positioning.

[0325] In some embodiments, the LMF network element determines to use the user plane connection between the terminal and the LMF network element for positioning based on the user plane positioning capability of the terminal, the control plane congestion status and other implementation factors.

[0326] In some embodiments, the LMF network element invokes the Nnrf_NFDiscovery service operation to retrieve the control plane congestion status.

[0327] In some embodiments, based on the load information of the AMF network element, if there is an available user plane connection between the terminal and the LMF network element, the LMF network element determines to use user plane positioning.

[0328] Optionally, the control plane congestion status may be the load status of the AMF network element.

[0329] Step S1102: The LMF network element sends a Namf_Communication_N1N2Transfer message to the AMF network element.

[0330] In some embodiments, when the LMF network element determines to use the user plane connection for positioning, and no user plane connection is established between the terminal and the LMF network element, the LMF network element calls the Namf_Communication_N1N2Transfer service operation and sends user plane information to the AMF network element to instruct the terminal to use the user plane S connection for positioning.

[0331] In some embodiments, the user plane information includes the IP address or FQDN of the LMF network element.

[0332] Step S1103: The AMF network element sends a DL NAS TRANSPORT message to the terminal.

[0333] In some embodiments, when the AMF network element receives the user plane information sent by the LMF network element, the AMF network element sends the user plane information to the terminal via a DL NAS TRANSPORT message.

[0334] Step S1104: The terminal sends a UL NAS TRANSPORT message to the AMF network element.

[0335] In some embodiments, if there is no PDU session available for user plane positioning between the terminal and the UPF network element, the terminal uses URSP to establish a PDU session for user plane positioning.

[0336] In some embodiments, the terminal may send a confirmation to the LMF network element through the AMF network element to indicate the successful utilization or failure of the user plane connection for the positioning service.

[0337] Optionally, the URSP includes PDU session parameters related to user plane positioning, such as dedicated DNN and S-NSSAI.

[0338] Alternatively, for example, no appropriate PDU session is established.

[0339] Step S1105: The AMF network element sends a Namf_N1MessageNotify message to the LMF network element.

[0340] In some embodiments, the AMF network element sends the confirmation received in step S1104 to the LMF network element through the Namf_N1MessageNotify message notification service.

[0341] Step S1106: The LMF network element uses the terminal's IP address to notify the terminal to establish a user plane connection.

[0342] In some embodiments, the LMF network element uses the terminal's IP address to notify the terminal to establish a user plane connection.

[0343] Step S1107: The terminal establishes a user plane connection with the LMF network element.

[0344] In some embodiments, if the terminal receives the FQDN sent by the LMF network element, the terminal uses a DNS server or resolver to resolve the FQDN sent by the LMF network element and obtain the IP address of the LMF network element.

[0345] In some embodiments, the terminal establishes a user plane connection with the LMF network element based on the obtained IP address of the LMF network element.

[0346] Step S1108, the LMF network element sends an Nlmf_Location_UPNotify message to the AMF network element.

[0347] In some embodiments, the LMF network element sends an Nlmf_Location_UPNotify message to the AMF network element to indicate that a user plane connection between the terminal and the LMF network element has been established.

[0348] Step S1109: The AMF network element stores the context of the user plane connection.

[0349] In some embodiments, the AMF network element saves the context of the user plane connection between the terminal and the LMF network element into the context of the terminal.

[0350] Step S1110: The terminal and the LMF network element transmit terminal positioning messages and / or supplementary service messages via a user plane connection.

[0351] In some embodiments, if the LMF network element or terminal determines to use the user plane connection for positioning and establishes a user plane connection between the terminal and the LMF network element, LPP messages are transmitted between the terminal and the LMF network element for terminal positioning, terminal-assisted positioning and transmission of auxiliary data.

[0352] In some embodiments, the terminal and the LMF network element transmit a terminal positioning message (UE positioning message) and / or a supplementary service message (Supplementary service message) through a user plane connection.

[0353] In some embodiments, supplementary services event report messages from the terminal may also be transmitted to the LMF network element via the established user plane connection.

[0354] In the related art, the LMF network element sends a user plane connection notification to the terminal through the known IP address of the terminal, which is used to instruct the terminal to establish a user plane connection with the LMF network element. However, it is not clarified whether the terminal is notified to establish the user plane connection through a control plane message or a user plane message. In addition, the parameters related to the establishment of the user plane connection with the terminal and the parameters related to the release of the user plane connection with the terminal are not defined in the message.

[0355] FIG2 is one of the interactive schematic diagrams of a communication method according to an embodiment of the present disclosure. As shown in FIG2 , an embodiment of the present disclosure relates to a communication method for a communication system 100, the method comprising:

[0356] Step S2101: The first network element sends a first notification and a first parameter to the second network element.

[0357] In some embodiments, the first network element is a LMF network element.

[0358] In some embodiments, the first notification is used to instruct the terminal and the LMF network element to establish a user plane connection.

[0359] In some embodiments, the first network element determines to use positioning by utilizing a user plane connection between the terminal and the first network element based on the user plane positioning capability of the terminal, the control plane congestion status, and other implementation factors.

[0360] In some embodiments, the first network element calls the Nnrf_NFDiscovery service operation to retrieve the control plane congestion status, and based on the load information of the AMF network element, if there is an available user plane connection between the terminal and the first network element, the first network element determines to use user plane positioning.

[0361] Optionally, the control plane congestion status may be the load status of the AMF network element.

[0362] In some embodiments, when the first network element determines to use the user plane connection for positioning and no user plane connection is established between the terminal and the first network element, a Namf_Communication_N1N2Transfer message is sent to the second network element to instruct the terminal to use the user plane connection for positioning; wherein the second network element is an AMF network element, and the Namf_Communication_N1N2Transfer message includes user plane information.

[0363] In some embodiments, the user plane information includes the IP address or FQDN of the LMF network element.

[0364] In some embodiments, the first network element further sends the first parameter to the second network element via a Namf_Communication_N1N2Transfer message.

[0365] In some embodiments, the manner in which the first network element sends the user plane information and the first parameter to the second network element through the Namf_Communication_N1N2Transfer message includes:

[0366] Send the user plane information and the first parameter to the AMF network element using different Namf_Communication_N1N2Transfer messages respectively;

[0367] Sending user plane information and the first parameter to the AMF network element in the same Namf_Communication_N1N2Transfer message, where the user plane information includes the first parameter;

[0368] Send the user plane information and the first parameter to the AMF network element with the same Namf_Communication_N1N2Transfer message; wherein the user plane information does not include the first parameter.

[0369] In some embodiments, after the first network element sends the user plane information and the first parameter to the AMF network element, it also includes: sending a first notification to the AMF network element through a Namf_Communication_N1N2Transfer message.

[0370] In some embodiments, the first network element determines to establish a user plane connection for positioning, and after receiving a first message sent by the terminal, sends a first notification and a first parameter to the second network element, wherein the first message is used to indicate that the terminal has successfully established a PDU session with the UPF for user plane positioning; wherein the second network element is an AMF network element or a UPF network element.

[0371] In some instances, the first network element has a default route to the UPF network element, and the first network element sends the first notification and the first parameter to the UPF network element through the default route.

[0372] In some embodiments, when the second network element is an AMF network element, the manner in which the first network element sends the first notification and the first parameter to the second network element includes:

[0373] Sending the first notification and the first parameter to the AMF network element using different Namf_Communication_N1N2Transfer messages respectively;

[0374] Sending a first notification and a first parameter to the AMF network element using the same Namf_Communication_N1N2Transfer message, where the first notification includes the first parameter;

[0375] Sending a first notification and a first parameter to the AMF network element using the same Namf_Communication_N1N2Transfer message, wherein the first notification does not include the first parameter;

[0376] In some embodiments, when the second network element is a UPF network element, the manner in which the first network element sends the first notification and the first parameter to the second network element includes:

[0377] Sending the first notification and the first parameter to the AMF network element in different IP data packets respectively;

[0378] Sending a first notification and a first parameter to the AMF network element in the same IP data packet, wherein the first notification includes the first parameter;

[0379] Send a first notification and a first parameter to the AMF network element in the same IP data packet, wherein the first notification does not include the first parameter.

[0380] In some embodiments, the first parameter includes at least one of a parameter related to establishing a user plane connection with the terminal and a parameter related to releasing the user plane connection with the terminal.

[0381] In some embodiments, the first parameter is used to specify a condition for triggering the terminal to establish a user plane connection and a condition for releasing the user plane connection, including at least one of the following:

[0382] A specific point in time or a specific area;

[0383] Periodic time points and time periods;

[0384] An event that triggers the establishment of a user plane connection;

[0385] An event that triggers the release of the user plane connection.

[0386] In some embodiments, when a specific time point is met, the terminal is triggered to establish or release a user plane connection with the first network element.

[0387] In some embodiments, the specific area includes a specific geographic location area or a specific area indicated by a TAI;

[0388] In some embodiments, when the terminal is located in a specific area, the terminal is triggered to establish or release a user plane connection with the first network element.

[0389] In some embodiments, the periodic time points and time periods are used to instruct the terminal to periodically establish or release a user plane connection with the first network element.

[0390] In some embodiments, the event triggering establishment of the user plane connection and the event triggering release of the user plane connection include different event types or operation types.

[0391] In some embodiments, the first network element may specify different user plane operations for different event types or operation types, wherein different user plane operations include one of establishing a user plane connection, releasing a user plane connection, and maintaining a user plane connection.

[0392] In some embodiments, the event that triggers establishment of the user plane connection and the event that triggers release of the user plane connection include at least one of the following:

[0393] periodicEvent;

[0394] enteringAreaEvent;

[0395] leavingAreaEvent and beingInsideAreaEvent;

[0396] motionEvent;

[0397] maximumIntervalExpirationEvent;

[0398] locationCancellationEvent.

[0399] In some embodiments, the event that triggers establishment of the user plane connection and the operation type that triggers release of the user plane connection include at least one of the following:

[0400] LocationNotification operation;

[0401] EventReport operation;

[0402] PeriodicTriggeredInvoke operation;

[0403] CancelDeferredLocation operation;

[0404] MSCancelDeferredPosition operation.

[0405] In some embodiments, parameters related to establishing a user plane connection with a terminal include at least one of the following:

[0406] The time point for periodically establishing user plane connections;

[0407] The time period for periodically establishing user plane connections;

[0408] The number of times user plane connections are periodically established;

[0409] A timer for periodically establishing user plane connections;

[0410] Trigger the LCS process to establish a user plane connection;

[0411] An event that triggers the establishment of a user plane connection;

[0412] The time point when the user plane connection is triggered;

[0413] The time period for triggering establishment of a user plane connection;

[0414] The area that triggers the establishment of a user plane connection;

[0415] Tracking area identifier that triggers establishment of a user plane connection;

[0416] The geographical location that triggers the establishment of a user plane connection.

[0417] In some embodiments, parameters related to the terminal releasing the user plane connection include at least one of the following:

[0418] The time point for periodically releasing the user plane connection;

[0419] The time period for periodically releasing the user plane connection;

[0420] The number of times the user plane connection is periodically released;

[0421] A timer for periodically releasing user plane connections;

[0422] Trigger the LCS process of releasing the user plane connection;

[0423] An event that triggers the release of the user plane connection;

[0424] The time point when the user plane connection is released is triggered;

[0425] The time period for triggering the release of the user plane connection;

[0426] The area that triggers the release of the user plane connection;

[0427] Tracking area identifier that triggers release of the user plane connection;

[0428] The geographical location that triggers the release of the user plane connection;

[0429] Method for releasing user plane connections.

[0430] In some embodiments, a method of releasing a user plane connection includes at least one of the following:

[0431] The terminal sends all data packets to the LMF network element and releases the current user plane connection;

[0432] The terminal releases the current user plane connection and discards unsent data packets;

[0433] After the terminal releases the current user plane connection, it creates a new user plane connection;

[0434] After the terminal creates a new user plane connection, it releases the current user plane connection.

[0435] Step S2102: The second network element sends a first notification and a first parameter to the terminal.

[0436] In some embodiments, when the second network element is an AMF network element, the user plane information and the first parameter are sent to the terminal via a DL NAS TRANSPORT message.

[0437] In some embodiments, the user plane information includes the IP address or FQDN of the LMF network element.

[0438] In some embodiments, the manner in which the second network element sends the user plane information and the first parameter to the terminal through a DL NAS TRANSPORT message includes:

[0439] Send the user plane information and the first parameter to the AMF network element using different DL NAS TRANSPORT messages respectively;

[0440] Sending user plane information and the first parameter to the AMF network element in the same DL NAS TRANSPORT message, wherein the user plane information includes the first parameter;

[0441] Send the user plane information and the first parameter to the AMF network element in the same DL NAS TRANSPORT message; wherein the user plane information does not include the first parameter.

[0442] In some embodiments, after the second network element sends the user plane information and the first parameter to the terminal, the method further includes: sending a first notification to the terminal through a DL NAS TRANSPORT message.

[0443] In some embodiments, after the second network element receives the first notification and the first parameter sent by the first network element, it also includes sending the first notification and the first parameter to the terminal; wherein the second network element is an AMF network element or a UPF network element.

[0444] In some embodiments, when the second network element is an AMF network element, the manner in which the second network element sends the first notification and the first parameter to the terminal includes:

[0445] sending the first notification and the first parameter to the terminal using different DL NAS TRANSPORT messages respectively;

[0446] Sending a first notification and a first parameter to the terminal using the same DL NAS TRANSPORT message, wherein the first notification includes the first parameter;

[0447] Sending a first notification and a first parameter to the terminal in the same DL NAS TRANSPORT message, wherein the first notification does not include the first parameter;

[0448] In some embodiments, when the second network element is a UPF network element, the manner in which the second network element sends the first notification and the first parameter to the terminal includes:

[0449] Sending a first notification and a first parameter to the UPF network element in different IP data packets respectively;

[0450] Sending a first notification and a first parameter to the UPF network element in the same IP data packet, wherein the first notification includes the first parameter;

[0451] Sending a first notification and a first parameter to the UPF network element in the same IP data packet, wherein the first notification does not include the first parameter;

[0452] In some embodiments, if the UPF network element that establishes a PDU session for positioning with the terminal and the UPF network element that receives the IP data packet sent by the first network element are the same network element, the IP data packet is directly sent to the terminal using the PDU session.

[0453] In some embodiments, if the UPF network element that establishes a PDU session for positioning with the terminal and the UPF network element that receives the IP data packet sent by the first network element are not the same network element, the IP data packet is forwarded to the UPF corresponding to the terminal IP address, that is, the UPF network element that establishes the PDU session for positioning with the terminal, and the UPF network element uses the PDU session to send the IP data packet to the terminal.

[0454] In some embodiments, the first notification is used to instruct the terminal and the LMF network element to establish a user plane connection.

[0455] In some embodiments, the first parameter includes at least one of a parameter related to establishing a user plane connection with the terminal and a parameter related to releasing the user plane connection with the terminal.

[0456] In some embodiments, after the terminal receives the first notification and first parameter sent by the first network element, if the first parameter includes parameters related to establishing a user plane connection with the terminal, then based on the obtained IP address of the first network element, a user plane connection with the first network element is established when the conditions for triggering the terminal to establish a user plane connection are met.

[0457] In some embodiments, if the first parameter received by the terminal only includes parameters related to the terminal releasing the user plane connection, the terminal establishes a user plane connection with the first network element after receiving the first notification.

[0458] In some embodiments, reference may be made to other optional implementations described before or after the description corresponding to FIG. 2 .

[0459] FIG3A is a second interactive diagram of a communication method according to an embodiment of the present disclosure. As shown in FIG3A , the embodiment of the present disclosure relates to a communication method, which includes:

[0460] Step S3101: The LMF network element determines to use the user plane for positioning.

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

[0462] In some embodiments, the LMF network element determines to use positioning using the user plane connection between the terminal and the LMF network element based on the user plane positioning capability of the terminal, the control plane congestion status and other implementation factors.

[0463] In some embodiments, the LMF network element calls the Nnrf_NFDiscovery service operation to retrieve the control plane congestion status, and based on the load information of the AMF network element, if there is an available user plane connection between the terminal and the LMF network element, the LMF network element determines to use user plane positioning.

[0464] Step S3102: The LMF network element sends a Namf_Communication_N1N2Transfer message to the AMF network element.

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

[0466] In some embodiments, when the LMF network element determines to use the user plane connection for positioning, and no user plane connection is established between the terminal and the LMF network element, the user plane information and the first parameter are sent to the AMF network element via the Namf_Communication_N1N2Transfer message to instruct the terminal to use the user plane connection for positioning.

[0467] In some embodiments, the AMF network element receives a Namf_Communication_N1N2Transfer message.

[0468] Step S3103: The AMF network element sends a DL NAS TRANSPORT message to the terminal.

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

[0470] Step S3104: The terminal sends a UL NAS TRANSPORT message to the AMF network element.

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

[0472] In some embodiments, the terminal sends a confirmation to the AMF network element through a UL NAS TRANSPORT message, which is used to indicate that the user plane connection is successfully used for positioning service or that the user plane connection cannot be successfully used for positioning service.

[0473] In some embodiments, the AMF network element receives a UL NAS TRANSPORT message.

[0474] Step S3105: The AMF network element sends a Namf_N1MessageNotify message to the LMF network element.

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

[0476] In some embodiments, the AMF network element sends the received confirmation to the LMF network element through the Namf_N1MessageNotify message, which is used to indicate that the user plane connection is successfully used for positioning service or that the user plane connection cannot be successfully used for positioning service.

[0477] In some embodiments, the LMF network element receives a Namf_N1MessageNotify message.

[0478] Step S3106: The LMF network element sends a Namf_Communication_N1N2Transfer message to the AMF network element.

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

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

[0481] In some embodiments, the LMF network element sends a first notification to the AMF network element via a Namf_Communication_N1N2Transfer message.

[0482] Step S3107: The AMF network element sends a DL NAS TRANSPORT message to the terminal.

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

[0484] In some embodiments, the AMF network element sends a first notification to the terminal via a DL NAS TRANSPORT message.

[0485] In some embodiments, the terminal receives a first notification sent by the AMF network element via a DL NAS TRANSPORT message.

[0486] Step S3108: The terminal determines to establish a user plane connection with the LMF network element.

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

[0488] In some embodiments, the terminal determines to establish a user plane connection with the first network element based on the received first notification and the first parameter.

[0489] Step S3109: The terminal establishes a user plane connection with the LMF network element.

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

[0491] In some embodiments, after the terminal receives the first notification and the first parameter sent by the first network element, if the first parameter includes parameters related to establishing a user plane connection with the terminal, then based on the obtained IP address of the first network element, it is determined that a user plane connection with the first network element is established when the conditions for triggering the terminal to establish a user plane connection are met.

[0492] In some embodiments, if the first parameter received by the terminal only includes parameters related to the terminal releasing the user plane connection, the terminal establishes a user plane connection with the first network element after receiving the first notification.

[0493] Step S3110, the LMF network element sends an Nlmf_Location_UPNotify message to the AMF network element.

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

[0495] In some embodiments, the LMF network element sends a confirmation to the AMF network element via an Nlmf_Location_UPNotify message, which is used to indicate that a user plane connection has been established between the terminal and the LMF network element.

[0496] In some embodiments, the AMF network element receives a confirmation sent by the LMF network element via an Nlmf_Location_UPNotify message, which is used to indicate that a user plane connection has been established between the terminal and the LMF network element.

[0497] Step S3111: The AMF network element stores the context of the user plane connection.

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

[0499] In some embodiments, the AMF network element saves the context of the user plane connection between the terminal and the LMF network element into the context of the terminal.

[0500] Step S3112: The terminal and the LMF network element transmit terminal positioning messages and / or supplementary service messages through the user plane.

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

[0502] In some embodiments, if the LMF network element or terminal determines to use the user plane connection for positioning and establishes a user plane connection between the terminal and the LMF network element, LPP messages are transmitted between the terminal and the LMF network element for terminal positioning, terminal-assisted positioning and transmission of auxiliary data.

[0503] In some embodiments, the supplementary service event report message from the terminal may also be transmitted to the LMF network element via the established user plane connection.

[0504] Step S3113: The terminal releases the user plane connection.

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

[0506] In some embodiments, when parameters related to the terminal releasing the user plane connection are met, the terminal sends a user plane connection release request to the first network element via an IP data packet to release the user plane connection with the first network element.

[0507] In some embodiments, after receiving a user plane connection release request sent by the terminal via an IP data packet, the first network element releases the user plane connection with the terminal.

[0508] In some embodiments, after the user plane connection is released, if there is no other user plane connection between the terminal and the first network element, the terminal will release the PDU session for positioning between the terminal and the UPF network element.

[0509] FIG3B is a third interactive diagram of a communication method according to an embodiment of the present disclosure. As shown in FIG3B , the embodiment of the present disclosure relates to a communication method, which includes:

[0510] Step S3201: The LMF network element determines to use the user plane for positioning.

[0511] Optional implementations of step S3201 can be found in step S2101 of FIG. 2 , optional implementations of step S3101 of FIG. 3A , and other related parts in the embodiments involved in FIG. 2 and FIG. 3A , which will not be described in detail here.

[0512] Step S3202: The LMF network element sends a Namf_Communication_N1N2Transfer message to the AMF network element.

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

[0514] Step S3203: The AMF network element sends a DL NAS TRANSPORT message to the terminal.

[0515] Optional implementations of step S3203 may refer to step S2102 in FIG. 2 , optional implementations of step S3103 in FIG. 3A , and other related parts in the embodiments involved in FIG. 2 and FIG. 3A , which will not be described in detail here.

[0516] Step S3204: The terminal sends a UL NAS TRANSPORT message to the AMF network element.

[0517] Optional implementations of step S3204 can be found in step S2102 of FIG. 2 , optional implementations of step S3104 of FIG. 3A , and other related parts in the embodiments involved in FIG. 2 and FIG. 3A , which will not be described in detail here.

[0518] Step S3205: The AMF network element sends a Namf_N1MessageNotify message to the LMF network element.

[0519] Optional implementations of step S3205 can be found in step S2102 of FIG. 2 , optional implementations of step S3105 of FIG. 3A , and other related parts in the embodiments involved in FIG. 2 and FIG. 3A , which will not be described in detail here.

[0520] Step S3206: The LMF network element sends a Namf_Communication_N1N2Transfer message to the AMF network element.

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

[0522] In some embodiments, the LMF network element sends the first notification and the first parameter to the AMF network element via a Namf_Communication_N1N2Transfer message.

[0523] In some embodiments, the AMF network element receives a Namf_Communication_N1N2Transfer message.

[0524] Step S3207: The AMF network element sends a DL NAS TRANSPORT message to the terminal.

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

[0526] In some embodiments, the AMF network element sends the first notification and the first parameter to the terminal via a DL NAS TRANSPORT message.

[0527] In some embodiments, the terminal receives a DL NAS TRANSPORT message.

[0528] Step S3208: The terminal determines to establish a user plane connection with the LMF network element.

[0529] The optional implementation of step S3208 can refer to step S2102 in FIG. 2 , the optional implementation of step S3108 in FIG. 3A , and other related parts in the embodiments involved in FIG. 2 and FIG. 3A , which will not be described in detail here.

[0530] Step S3209: The terminal establishes a user plane connection with the LMF network element.

[0531] The optional implementation of step S3209 can refer to step S2102 in FIG. 2 , the optional implementation of step S3109 in FIG. 3A , and other related parts in the embodiments involved in FIG. 2 and FIG. 3A , which will not be described in detail here.

[0532] In some embodiments, after the terminal receives the first notification and the first parameter sent by the first network element, if the first parameter includes parameters related to establishing a user plane connection with the terminal, then based on the obtained IP address of the first network element, it is determined that a user plane connection with the first network element is established when the conditions for triggering the terminal to establish a user plane connection are met.

[0533] In some embodiments, if the first parameter received by the terminal only includes parameters related to the terminal releasing the user plane connection, the terminal establishes a user plane connection with the first network element after receiving the first notification.

[0534] Step S3210, the LMF network element sends an Nlmf_Location_UPNotify message to the AMF network element.

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

[0536] Step S3211, the AMF network element stores the context of the user plane connection.

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

[0538] In some embodiments, the AMF network element saves the context of the user plane connection between the terminal and the LMF network element into the context of the terminal.

[0539] Step S3212: The terminal and the LMF network element transmit terminal positioning messages and / or supplementary service messages through the user plane.

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

[0541] Step S3213: The terminal releases the user plane connection.

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

[0543] FIG3C is a fourth interactive diagram of a communication method according to an embodiment of the present disclosure. As shown in FIG3C , the embodiment of the present disclosure relates to a communication method, which includes:

[0544] Step S3301: The LMF network element determines to use the user plane for positioning.

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

[0546] Step S3302: The LMF network element sends a Namf_Communication_N1N2Transfer message to the AMF network element.

[0547] The optional implementation of step S3302 can refer to the optional implementation of step S2101 in Figure 2, step S3202 in Figure 3B, and other related parts in the embodiments involved in Figures 2 and 3B, which will not be repeated here.

[0548] Step S3203: The AMF network element sends a DL NAS TRANSPORT message to the terminal.

[0549] The optional implementation of step S3303 can refer to step S2101 in Figure 2, the optional implementation of step S3203 in Figure 3B, and other related parts in the embodiments involved in Figures 2 and 3B, which will not be repeated here.

[0550] Step S3304: The terminal sends a UL NAS TRANSPORT message to the AMF network element.

[0551] The optional implementation of step S3304 can be found in the optional implementation of step S2102 in Figure 2, step S3104 in Figure 3A, step S3204 in Figure 3B, and other related parts in the embodiments involved in Figures 2, 3A and 3B, which will not be repeated here.

[0552] Step S3305: The AMF network element sends a Namf_N1MessageNotify message to the LMF network element.

[0553] The optional implementation of step S3305 can be found in the optional implementation of step S2102 in Figure 2, step S3105 in Figure 3A, step S3205 in Figure 3B, and other related parts in the embodiments involved in Figures 2, 3A and 3B, which will not be repeated here.

[0554] Step S3306: The LMF network element sends a first notification and a first parameter to the UPF network element.

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

[0556] In some instances, the LMF network element has a default route to the UPF network element, and the LMF network element sends the first notification and the first parameter to the UPF network element through the default route.

[0557] In some embodiments, the UPF network element receives the first notification and the first parameter sent by the LMF network element via an IP data packet.

[0558] Step S3307: The UPF network element sends a first notification and a first parameter to the terminal.

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

[0560] In some embodiments, the UPF network element sends the first notification and the first parameter to the terminal via an IP data packet.

[0561] In some embodiments, if the UPF network element that establishes a PDU session for positioning with the terminal and the UPF network element that receives the IP data packet sent by the first network element are the same network element, the IP data packet is directly sent to the terminal using the PDU session.

[0562] In some embodiments, if the UPF network element that establishes a PDU session for positioning with the terminal and the UPF network element that receives the IP data packet sent by the first network element are not the same network element, the IP data packet is forwarded to the UPF corresponding to the terminal IP address, that is, the UPF network element that establishes the PDU session for positioning with the terminal, and the UPF network element uses the PDU session to send the IP data packet to the terminal.

[0563] In some embodiments, the terminal receives an IP data packet sent by a UPF network element using a PDU session, wherein the IP data packet includes a first notification and a first parameter.

[0564] Step S3308: The terminal determines to establish a user plane connection with the LMF network element.

[0565] The optional implementation of step S3308 can be found in the optional implementation of step S2102 in Figure 2, step S3108 in Figure 3A, step S3208 in Figure 3B, and other related parts in the embodiments involved in Figures 2, 3A and 3B, which will not be repeated here.

[0566] Step S3309: The terminal establishes a user plane connection with the LMF network element.

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

[0568] In some embodiments, after the terminal receives the first notification and the first parameter sent by the first network element, if the first parameter includes parameters related to establishing a user plane connection with the terminal, then based on the obtained IP address of the first network element, it is determined that a user plane connection with the first network element is established when the conditions for triggering the terminal to establish a user plane connection are met.

[0569] In some embodiments, if the first parameter received by the terminal only includes parameters related to the terminal releasing the user plane connection, the terminal establishes a user plane connection with the first network element after receiving the first notification.

[0570] Step S3310, the LMF network element sends an Nlmf_Location_UPNotify message to the AMF network element.

[0571] The optional implementation of step S3310 can be found in the optional implementation of step S2102 in Figure 2, step S3110 in Figure 3A, step S3210 in Figure 3B, and other related parts in the embodiments involved in Figures 2, 3A and 3B, which will not be repeated here.

[0572] Step S3311, the AMF network element stores the context of the user plane connection.

[0573] The optional implementation of step S3311 can refer to the optional implementation of step S2102 in Figure 2, step S3111 in Figure 3A, step S3211 in Figure 3B, and other related parts in the embodiments involved in Figures 2, 3A and 3B, which will not be repeated here.

[0574] Step S3312: The terminal and the LMF network element transmit terminal positioning messages and / or supplementary service messages through the user plane.

[0575] The optional implementation of step S3312 can be found in the optional implementation of step S2102 in Figure 2, step S3112 in Figure 3A, step S3212 in Figure 3B, and other related parts in the embodiments involved in Figures 2, 3A and 3B, which will not be repeated here.

[0576] Step S3313: The terminal releases the user plane connection.

[0577] The optional implementation of step S3313 can refer to the optional implementation of step S2102 in Figure 2, step S3113 in Figure 3A, the optional implementation of step S3213 in Figure 3B, and other related parts in the embodiments involved in Figures 2, 3A and 3B, which will not be repeated here.

[0578] FIG4 is a flow chart of a communication method according to an embodiment of the present disclosure. As shown in FIG4 , the embodiment of the present disclosure involves a first network element, and the method includes:

[0579] Step S4101: The first network element determines to use the user plane for positioning.

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

[0581] In some embodiments, the first network element may be a LMF network element.

[0582] In some embodiments, the first network element determines to use the user plane connection between the terminal and the first network element for positioning based on the user plane positioning capability of the terminal, the control plane congestion status, and other implementation factors.

[0583] In some embodiments, the first network element invokes the Nnrf_NFDiscovery service operation to retrieve the control plane congestion status.

[0584] In some embodiments, based on the load status of the AMF network element, if there is an available user plane connection between the terminal and the first network element, the first network element determines to use user plane positioning.

[0585] Optionally, the control plane congestion status may be the load status of the AMF network element.

[0586] Step S4102: The first network element sends user plane information to the second network element.

[0587] The optional implementation of step S4102 can refer to the optional implementation of step S2101, step S3102, step S3202, step S3302 in Figure 2, and other related parts in the embodiments involved in Figures 2, 3A, 3B, and 3C, which will not be repeated here.

[0588] In some embodiments, when the first network element determines to use the user plane connection for positioning and no user plane connection is established between the terminal and the first network element, a Namf_Communication_N1N2Transfer message is sent to the second network element to instruct the terminal to use the user plane connection for positioning, wherein the second network element is an AMF network element, and the Namf_Communication_N1N2Transfer message includes user plane information.

[0589] Step S4103: The first network element sends a first notification and a first parameter to the second network element.

[0590] The optional implementation methods of step S4103 can be found in the optional implementation methods of step S2101 in Figure 2, step S3102, step S3106 in Figure 3A, step S3207 in Figure 3B, and step S3307 in Figure 3C, as well as other related parts in the embodiments involved in Figures 2, 3A, 3B, and 3C, which will not be repeated here.

[0591] In some embodiments, if the second network element is an AMF network element, the first network element also sends the first parameter to the second network element through a Namf_Communication_N1N2Transfer message.

[0592] In some embodiments, the manner in which the first network element sends the user plane information and the first parameter to the second network element through the Namf_Communication_N1N2Transfer message includes:

[0593] Send the user plane information and the first parameter to the AMF network element using different Namf_Communication_N1N2Transfer messages respectively;

[0594] Sending user plane information and the first parameter to the AMF network element in the same Namf_Communication_N1N2Transfer message, where the user plane information includes the first parameter;

[0595] Send the user plane information and the first parameter to the AMF network element with the same Namf_Communication_N1N2Transfer message; wherein the user plane information does not include the first parameter.

[0596] In some embodiments, after the first network element sends the user plane information and the first parameter to the AMF network element, it also includes: sending a first notification to the AMF network element through a Namf_Communication_N1N2Transfer message.

[0597] In some embodiments, after the first network element receives the first message sent by the terminal, it also includes sending a first notification and a first parameter to the second network element, wherein the first message is used to indicate that the terminal successfully establishes a PDU session for user plane positioning with the UPF; wherein the second network element is an AMF network element or a UPF network element.

[0598] In some instances, the first network element has a default route to the UPF network element, and the first network element sends the first notification and the first parameter to the UPF network element through the default route.

[0599] In some embodiments, when the second network element is an AMF network element, the manner in which the first network element sends the first notification and the first parameter to the second network element includes:

[0600] Sending the first notification and the first parameter to the AMF network element using different Namf_Communication_N1N2Transfer messages respectively;

[0601] Sending a first notification and a first parameter to the AMF network element using the same Namf_Communication_N1N2Transfer message, where the first notification includes the first parameter;

[0602] Sending a first notification and a first parameter to the AMF network element using the same Namf_Communication_N1N2Transfer message, wherein the first notification does not include the first parameter;

[0603] In some embodiments, when the second network element is a UPF network element, the manner in which the first network element sends the first notification and the first parameter to the second network element includes:

[0604] Sending a first notification and a first parameter to the UPF network element in different IP data packets respectively;

[0605] Sending a first notification and a first parameter to the UPF network element in the same IP data packet, wherein the first notification includes the first parameter;

[0606] A first notification and a first parameter are sent to the UPF network element in the same IP data packet, wherein the first notification does not include the first parameter.

[0607] Step S4104: The first network element establishes a user plane connection with the terminal.

[0608] The optional implementation of step S4104 can be found in the optional implementation of step S2102 in Figure 2, step S3108 in Figure 3A, step S3208 in Figure 3B, step S3308 in Figure 3C, and other related parts in the embodiments involved in Figures 2, 3A, 3B, and 3C, which will not be repeated here.

[0609] In some embodiments, if the user plane information received by the terminal is the FQDN of the first network element, a DNS server or resolver is used to resolve the FQDN to obtain the IP address of the first network element.

[0610] In some embodiments, after receiving the first notification and the first parameter, if the first parameter includes parameters related to establishing a user plane connection with the terminal, based on the obtained IP address of the first network element, when the conditions for triggering the terminal to establish a user plane connection are met, a user plane connection with the first network element is established.

[0611] In some embodiments, if the first parameter received by the terminal only includes parameters related to the terminal releasing the user plane connection, the terminal establishes a user plane connection with the first network element after receiving the first notification.

[0612] Step S4105: The first network element sends a confirmation to the second network element.

[0613] The optional implementation of step S4105 can be found in the optional implementation of step S2101 in Figure 2, step S3110 in Figure 3A, step S3210 in Figure 3B, step S3310 in Figure 3C, and other related parts in the embodiments involved in Figures 2, 3A, 3B, and 3C, which will not be repeated here.

[0614] In some embodiments, the second network element is an AMF network element.

[0615] In some embodiments, when the terminal and the first network element establish a user plane, the LMF network element sends a confirmation to the AMF network element, which is used to indicate that the terminal and the LMF network element have established a user plane connection.

[0616] Step S4106: The terminal and the first network element transmit a terminal positioning message and / or a supplementary service message via the user plane.

[0617] The optional implementation of step S4106 can be found in the optional implementation of step S2102 in Figure 2, step S3112 in Figure 3A, step S3212 in Figure 3B, step S3312 in Figure 3C, and other related parts in the embodiments involved in Figures 2, 3A, 3B, and 3C, which will not be repeated here.

[0618] In some embodiments, if the LMF network element or terminal determines to use the user plane connection for positioning and establishes a user plane connection between the terminal and the LMF network element, LPP messages are transmitted between the terminal and the LMF network element for terminal positioning, terminal-assisted positioning and transmission of auxiliary data.

[0619] In some embodiments, the supplementary service event report message from the terminal may also be transmitted to the LMF network element via the established user plane connection.

[0620] Step S4107: The first network element releases the user plane connection with the terminal.

[0621] The optional implementation of step S4107 can be found in the optional implementation of step S2102 in Figure 2, step S3113 in Figure 3A, step S3213 in Figure 3B, step S3313 in Figure 3C, and other related parts in the embodiments involved in Figures 2, 3A, 3B, and 3C, which will not be repeated here.

[0622] In some embodiments, after receiving a user plane connection release request sent by the terminal via an IP data packet, the first network element releases the user plane connection with the terminal.

[0623] FIG5 is a flow chart of a communication method according to an embodiment of the present disclosure. As shown in FIG5 , the embodiment of the present disclosure involves a second network element, and the method includes:

[0624] Step S5101: The second network element sends user plane information to the terminal.

[0625] The optional implementation of step S5101 can be found in the optional implementation of step S2102 in Figure 2, step S3113 in Figure 3A, step S3213 in Figure 3B, step S3313 in Figure 3C, and other related parts in the embodiments involved in Figures 2, 3A, 3B, and 3C, which will not be repeated here.

[0626] In some embodiments, when the second network element is an AMF network element, user plane information is sent to the terminal via a DL NAS TRANSPORT message to instruct the terminal to use the user plane for positioning.

[0627] In some embodiments, when the second network element is an AMF network element, user plane information and a first parameter are sent to the terminal via a DL NAS TRANSPORT message to instruct the terminal to use the user plane for positioning.

[0628] In some embodiments, the user plane information includes an IP address or FQDN of the first network element.

[0629] Step S5102: The second network element sends a user plane location confirmation to the first network element.

[0630] The optional implementation of step S5102 can be found in the optional implementation of step S2102 in Figure 2, step S3105 in Figure 3A, step S3205 in Figure 3B, step S3305 in Figure 3C, and other related parts in the embodiments involved in Figures 2, 3A, 3B, and 3C, which will not be repeated here.

[0631] In some embodiments, when the second network element is an AMF network element, the second network element sends the received confirmation to the first network element through a Namf_N1MessageNotify message, where the confirmation is used to indicate that the user plane connection is successfully used for positioning service or that the user plane connection cannot be successfully used for positioning service.

[0632] Step S5103: The second network element sends a first notification and a first parameter to the terminal.

[0633] The optional implementation methods of step S5103 can be found in step S2102 of Figure 2, step S3103, step S3107 of Figure 3A, step S3207 of Figure 3B, and step S3307 of Figure 3C, as well as other related parts in the embodiments involved in Figures 2, 3A, 3B, and 3C, which will not be repeated here.

[0634] Step S5104: The second network element stores the context of the user plane connection.

[0635] The optional implementation of step S5104 can be found in the optional implementation of step S2102 in Figure 2, step S3111 in Figure 3A, step S3211 in Figure 3B, step S3311 in Figure 3C, and other related parts in the embodiments involved in Figures 2, 3A, 3B, and 3C, which will not be repeated here.

[0636] In some embodiments, when the second network element is an AMF network element, the context of the user plane connection between the terminal and the first network element is saved in the context of the terminal.

[0637] FIG6 is a flow chart of a communication method according to an embodiment of the present disclosure. As shown in FIG6 , the embodiment of the present disclosure relates to a terminal, and the method includes:

[0638] Step S6101: The terminal receives user plane information sent by the second network element.

[0639] The optional implementation of step S6101 can be found in the optional implementation of step S2102 in Figure 2, step S3103 in Figure 3A, step S3203 in Figure 3B, step S3303 in Figure 3C, and other related parts in the embodiments involved in Figures 2, 3A, 3B, and 3C, which will not be repeated here.

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

[0641] In some embodiments, when the second network element is an AMF network element, the user plane information sent by the AMF network element through a DL NAS TRANSPORT message is received to instruct the terminal to use the user plane connection for positioning.

[0642] Step S6102: The terminal sends a user plane location confirmation to the second network element.

[0643] The optional implementation of step S6102 can be found in the optional implementation of step S2102 in Figure 2, step S3104 in Figure 3A, step S3204 in Figure 3B, step S3304 in Figure 3C, and other related parts in the embodiments involved in Figures 2, 3A, 3B, and 3C, which will not be repeated here.

[0644] In some embodiments, if there is no PDU session that can be used for user plane positioning between the terminal and the UPF network element, a PDU session that can be used for user plane positioning is established between the terminal and the UPF network element.

[0645] In some embodiments, when the second network element is an AMF network element, the terminal sends a confirmation to the AMF network element through a UL NAS TRANSPORT message, which is used to indicate that the user plane connection is successfully used for positioning service or that the user plane connection cannot be successfully used for positioning service.

[0646] Optionally, if the terminal does not establish a suitable PDU session for user plane positioning, the terminal sends a confirmation to the first network element through the AMF network element, which is used to indicate that the user plane connection cannot be used for positioning services.

[0647] Step S6103: The terminal receives the first notification and the first parameter sent by the second network element.

[0648] The optional implementation methods of step S6103 can be found in the optional implementation methods of step S2102 in Figure 2, step S3103, step S3107 in Figure 3A, step S3207 in Figure 3B, and step S3307 in Figure 3C, as well as other related parts in the embodiments involved in Figures 2, 3A, 3B, and 3C, which will not be repeated here.

[0649] Step S6104: The terminal determines to establish a user plane connection with the first network element.

[0650] The optional implementation of step S6104 can be found in the optional implementation of step S2102 in Figure 2, step S3108 in Figure 3A, step S3208 in Figure 3B, step S3308 in Figure 3C, and other related parts in the embodiments involved in Figures 2, 3A, 3B, and 3C, which will not be repeated here.

[0651] In some embodiments, based on the received first notification and first parameter, if the first parameter includes parameters related to establishing a user plane connection with the terminal, the terminal determines to establish a user plane connection with the first network element when the conditions for triggering the terminal to establish a user plane connection are met.

[0652] In some embodiments, if the first parameter received by the terminal only includes parameters related to the terminal releasing the user plane connection, the terminal establishes a user plane connection with the first network element after receiving the first notification.

[0653] Step S6105: The terminal establishes a user plane connection with the first network element.

[0654] The optional implementation of step S6105 can be found in the optional implementation of step S2102 in Figure 2, step S3109 in Figure 3A, step S3209 in Figure 3B, step S3309 in Figure 3C, and other related parts in the embodiments involved in Figures 2, 3A, 3B, and 3C, which will not be repeated here.

[0655] In some embodiments, if the terminal receives the FQDN sent by the first network element, the terminal uses a DNS server or a resolver to resolve the FQDN sent by the first network element and obtain the IP address of the first network element.

[0656] In some embodiments, after the terminal receives the first notification and first parameter sent by the first network element, if the first parameter includes parameters related to establishing a user plane connection with the terminal, then based on the obtained IP address of the first network element, a user plane connection with the first network element is established when the conditions for triggering the terminal to establish a user plane connection are met.

[0657] In some embodiments, if the first parameter received by the terminal only includes parameters related to the terminal releasing the user plane connection, the terminal establishes a user plane connection with the first network element after receiving the first notification.

[0658] Step S6106: The terminal and the first network element transmit a terminal positioning message and / or a supplementary service message via the user plane.

[0659] The optional implementation of step S6106 can be found in the optional implementation of step S2102 in Figure 2, step S3112 in Figure 3A, step S3212 in Figure 3B, step S3312 in Figure 3C, and other related parts in the embodiments involved in Figures 2, 3A, 3B, and 3C, which will not be repeated here.

[0660] In some embodiments, if the terminal or the first network element determines to use a user plane connection for positioning and establishes a user plane connection between the terminal and the first network element, LPP messages are transmitted between the terminal and the first network element for terminal positioning, terminal-assisted positioning, and transmission of auxiliary data.

[0661] In some embodiments, the supplementary service event report message from the terminal may also be transmitted to the first network element via the established user plane connection.

[0662] Step S6107: The terminal releases the user plane connection with the first network element.

[0663] The optional implementation of step S6107 can be found in the optional implementation of step S2102 in Figure 2, step S3113 in Figure 3A, step S3213 in Figure 3B, step S3313 in Figure 3C, and other related parts in the embodiments involved in Figures 2, 3A, 3B, and 3C, which will not be repeated here.

[0664] In some embodiments, when parameters related to the terminal releasing the user plane connection are met, the terminal sends a user plane connection release request to the first network element via an IP data packet to release the user plane connection with the first network element.

[0665] In some embodiments, after the user plane connection is released, if there is no other user plane connection between the terminal and the first network element, the terminal will release the PDU session for positioning between the terminal and the UPF network element.

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

[0667] 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), which realizes the functions of some or all of the above units or modules by designing the logical relationship of the components in the circuit; for example, in another implementation, the above-mentioned hardware circuit can be realized by a programmable logic device (PLD). Taking a field programmable gate array (FPGA) as an example, it can include a large number of logic gate circuits, and the connection relationship between the logic gate circuits is configured by configuring the configuration file, thereby realizing the functions of some or all of the above units or modules. All units or modules of the above devices can be realized in the form of software called by the processor, or in the form of hardware circuits, or in part by the form of software called by the processor, and the rest by hardware circuits.

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

[0669] FIG7A is a schematic diagram of the structure of a first network element proposed in an embodiment of the present disclosure. As shown in FIG7A , the terminal may include: a processing module 7101 .

[0670] In some embodiments, the transceiver module is configured to send at least one of the first notification and the first parameter to the second network element, so that the second network element sends at least one of the first notification and the first parameter to the terminal;

[0671] The first notification is used to instruct the terminal to establish a user plane connection with the first network element;

[0672] The first parameter includes at least one of the following:

[0673] Parameters related to establishing a user plane connection with the terminal;

[0674] Parameters related to the terminal releasing the user plane connection.

[0675] Optionally, the above-mentioned processing module is used to execute the communication steps such as sending and / or receiving performed by the first network element in any of the above methods, such as step S4101, which will not be repeated here.

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

[0677] In some embodiments, the transceiver module is configured to receive at least one of a first notification and a first parameter sent by a first network element, and

[0678] sending at least one of the first notification and the first parameter to a terminal;

[0679] The first notification is used to instruct the terminal to establish a user plane connection with the first network element;

[0680] The first parameter includes at least one of the following:

[0681] Parameters related to establishing a user plane connection with the terminal;

[0682] Parameters related to the terminal releasing the user plane connection.

[0683] Optionally, the above-mentioned processing module is used to execute the communication steps such as sending and / or receiving performed by the second network element in any of the above methods, such as step S5101, which will not be repeated here.

[0684] FIG7C is a schematic diagram of the structure of a terminal proposed in an embodiment of the present disclosure. As shown in FIG7C , the terminal may include: a transceiver module 7301 .

[0685] In some embodiments, the transceiver module is configured to receive at least one of the first notification and the first parameter sent by the second network element;

[0686] The first notification and the first parameter sent by the second network element are received from the first network element;

[0687] The first notification is used to instruct the terminal to establish a user plane connection with the first network element;

[0688] The first parameter includes at least one of the following:

[0689] Parameters related to establishing a user plane connection with the terminal;

[0690] Parameters related to the terminal releasing the user plane connection.

[0691] Optionally, the above-mentioned processing module is used to execute the communication steps such as sending and / or receiving performed by the terminal in any of the above methods, such as step S6101, which will not be repeated here.

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

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

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

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

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

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

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

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

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

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

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

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

Claims

1. A communication method, characterized in that: Applied to a first network element, the method includes: Sending at least one of the first notification and the first parameter to the second network element, so that the second network element sends at least one of the first notification and the first parameter to the terminal; The first notification is used to instruct the terminal to establish a user plane connection with the first network element; The first parameter includes at least one of the following: Parameters related to establishing a user plane connection with the terminal; Parameters related to the terminal releasing the user plane connection.

2. The method according to claim 1, characterized in that The second network element is an access and mobility management function AMF network element or a user plane function UPF network element.

3. The method according to claim 2, characterized in that The second network element is an AMF network element; The sending at least one of the first notification and the first parameter to the second network element comprises: Determine to use a user plane connection, and send user plane information and at least one of the first parameter to the AMF network element; Receive a first message, and send the first notification to the AMF network element, where the first message is used to indicate that the terminal has successfully established a PDU session for user plane positioning.

4. The method according to claim 3, characterized in that The sending at least one of the user plane information and the first parameter to the AMF network element comprises: sending the user plane information and the first parameter in different messages respectively, or; sending the user plane information and the first parameter in the same message, wherein the user plane information includes the first parameter, or; The user plane information and the first parameter are sent in the same message, and the user plane information does not include the first parameter.

5. The method according to claim 2, characterized in that: The sending at least one of the first notification and the first parameter to the second network element comprises: Determine to use the user plane connection, and send user plane information to the AMF network element; Receive a first message, and send at least one of the first notification and a first parameter to the second network element, wherein the first message is used to indicate that the terminal successfully establishes a PDU session for user plane positioning.

6. The method according to claim 5, characterized in that The sending at least one of the first notification and the first parameter to the second network element comprises: sending the first notification and the first parameter in different messages respectively, or; sending the first notification and the first parameter in the same message, where the first notification includes the first parameter, or; The first notification and the first parameter are sent in a same message, and the first notification does not include the first parameter.

7. The method according to any one of claims 1 to 6, characterized in that: The parameters related to establishing a user plane connection with the terminal include at least one of the following: The time point for periodically establishing a user plane connection; The time period for periodically establishing a user plane connection; The number of times user plane connections are periodically established; A timer for periodically establishing a user plane connection; Trigger the location service LCS process to establish a user plane connection; An event that triggers establishment of a user plane connection; The time point at which the user plane connection is established is triggered; The time period for triggering establishment of a user plane connection; An area that triggers establishment of a user plane connection; A tracking area identifier that triggers establishment of a user plane connection; The geographical location that triggers the establishment of a user plane connection.

8. The method according to any one of claims 1 to 6, characterized in that: The parameters related to the terminal releasing the user plane connection include at least one of the following: The time point for periodically releasing the user plane connection; The time period for periodically releasing the user plane connection; The number of times the user plane connection is periodically released; A timer for periodically releasing user plane connections; Trigger the LCS process of releasing the user plane connection; An event that triggers the release of a user plane connection; The time point at which the user plane connection is released is triggered; The time period for triggering the release of the user plane connection; An area that triggers the release of a user plane connection; A tracking area identifier that triggers the release of the user plane connection; A geographical location that triggers the release of a user plane connection; Method for releasing user plane connection.

9. The method according to claim 8, characterized in that The method of releasing the user plane connection includes at least one of the following: The terminal sends all data packets to the LMF network element and releases the current user plane connection; The terminal releases the current user plane connection and discards unsent data packets; After the terminal releases the current user plane connection, a new user plane connection is created; After the terminal creates a new user plane connection, it releases the current user plane connection.

10. A communication method, characterized in that: Applied to a second network element, the method comprises: receiving at least one of a first notification and a first parameter sent by a first network element; sending at least one of the first notification and the first parameter to a terminal; The first notification is used to instruct the terminal to establish a user plane connection with the first network element; The first parameter includes at least one of the following: Parameters related to establishing a user plane connection with the terminal; Parameters related to the terminal releasing the user plane connection.

11. The method according to claim 10, characterized in that The second network element is an AMF network element or a UPF network element.

12. The method according to claim 11, characterized in that The second network element is an AMF network element; The receiving at least one of a first notification and a first parameter sent by a first network element includes: receiving at least one of the user plane information and the first parameter sent by the first network element; receiving a first notification sent by the first network element; The user plane information and the first parameter are determined by the first network element to be sent using a user plane connection; The first notification is sent by the first network element after receiving a first message, where the first message is used to indicate that the terminal successfully establishes a PDU session for user plane positioning.

13. The method according to claim 12, characterized in that The AMF network element receives at least one of the user plane information and the first parameter sent by the first network element, including: receiving the user plane information and the first parameter in different messages respectively, or; receiving the user plane information and the first parameter in the same message, wherein the user plane information includes the first parameter, or; The user plane information and the first parameter are received in a same message, wherein the user plane information does not include the first parameter.

14. The method according to claim 12 or 13, characterized in that The sending at least one of the first notification and the first parameter to the terminal includes: Send at least one of the user plane information, the first parameter and the first notification to a terminal.

15. The method according to claim 14, characterized in that The sending at least one of the user plane information and the first parameter to the terminal includes: sending the user plane information and the first parameter to the terminal in different messages respectively, or; sending the user plane information and the first parameter to the terminal in the same message, where the user plane information includes the first parameter, or; The user plane information and the first parameter are sent to the terminal in the same message, where the user plane information does not include the first parameter.

16. The method according to claim 11, characterized in that The first notification and the first parameter are sent after the first network element determines to use the user plane connection, sends user plane information to the AMF network element, and receives the first message.

17. The method according to claim 16, characterized in that The receiving at least one of a first notification and a first parameter sent by a first network element includes: receiving the first notification and the first parameter in different messages respectively, or; receiving the first notification and the first parameter in the same message, wherein the first notification includes the first parameter, or; The first notification and the first parameter are received in a same message, the first notification excluding the first parameter.

18. The method according to claim 16 or 17, characterized in that The sending at least one of the first notification and the first parameter to the terminal includes: sending the first notification and the first parameter to the terminal in different messages respectively, or; sending the first notification and the first parameter to the terminal in the same message, where the first notification includes the first parameter, or; The first notification and the first parameter are sent to the terminal in a same message, wherein the first notification does not include the first parameter.

19. The method according to any one of claims 10 to 18, characterized in that: The parameters related to establishing a user plane connection with the terminal include at least one of the following: The time point for periodically establishing a user plane connection; The time period for periodically establishing a user plane connection; The number of times user plane connections are periodically established; A timer for periodically establishing a user plane connection; Trigger the LCS process of establishing a user plane connection; An event that triggers establishment of a user plane connection; The time point at which the user plane connection is established is triggered; The time period for triggering establishment of a user plane connection; An area that triggers establishment of a user plane connection; A tracking area identifier that triggers establishment of a user plane connection; The geographical location that triggers the establishment of a user plane connection.

20. The method according to any one of claims 10 to 18, characterized in that: The parameters related to the terminal releasing the user plane connection include at least one of the following: The time point for periodically releasing the user plane connection; The time period for periodically releasing the user plane connection; The number of times the user plane connection is periodically released; A timer for periodically releasing user plane connections; Trigger the LCS process of releasing the user plane connection; An event that triggers the release of a user plane connection; The time point at which the user plane connection is released is triggered; The time period for triggering the release of the user plane connection; An area that triggers the release of a user plane connection; A tracking area identifier that triggers the release of the user plane connection; A geographical location that triggers the release of a user plane connection; Method for releasing user plane connection.

21. The method according to claim 20, characterized in that The method of releasing the user plane connection includes at least one of the following: The terminal sends all data packets to the LMF network element and releases the current user plane connection; The terminal releases the current user plane connection and discards unsent data packets; After the terminal releases the current user plane connection, a new user plane connection is created; After the terminal creates a new user plane connection, it releases the current user plane connection.

22. A communication method, characterized in that: Applied to a terminal, the method comprises: receiving at least one of a first notification and a first parameter sent by a second network element; The first notification and the first parameter sent by the second network element are received from the first network element; The first notification is used to instruct the terminal to establish a user plane connection with the first network element; The first parameter includes at least one of the following: Parameters related to establishing a user plane connection with the terminal; Parameters related to the terminal releasing the user plane connection.

23. The method according to claim 22, characterized in that Also includes: At least one of establishing a user plane connection and releasing the user plane connection is performed according to the first notification and the first parameter.

24. The method according to claim 22 or 23, characterized in that The second network element is an AMF network element or a UPF network element.

25. The method according to any one of claims 22 to 24, characterized in that: The second network element is an AMF network element; The receiving at least one of the first notification and the first parameter sent by the second network element includes: Receive at least one of the user plane information, the first parameter and the first notification sent by the second network element.

26. The method according to claim 25, characterized in that The receiving at least one of the user plane information and the first parameter sent by the second network element includes: receiving the user plane information and the first parameter in different messages respectively, or; receiving the user plane information and the first parameter in the same message, wherein the user plane information includes the first parameter, or; The user plane information and the first parameter are received in a same message, wherein the user plane information does not include the first parameter.

27. The method according to claim 24, characterized in that The first notification and the first parameter are sent to the second network element after the first network element determines to use the user plane connection, sends user plane information to the AMF network element, and receives the first message.

28. The method according to claim 27, characterized in that Receiving at least one of a first notification and a first parameter sent by a second network element includes: receiving the first notification and the first parameter in different messages respectively, or; receiving the first notification and the first parameter in the same message, wherein the first notification includes the first parameter, or; The first notification and the first parameter are received in a same message, the first notification excluding the first parameter.

29. The method according to any one of claims 22 to 28, characterized in that: The parameters related to establishing a user plane connection with the terminal include at least one of the following: The time point for periodically establishing a user plane connection; The time period for periodically establishing a user plane connection; The number of times user plane connections are periodically established; A timer for periodically establishing a user plane connection; Trigger the LCS process of establishing a user plane connection; An event that triggers establishment of a user plane connection; The time point at which the user plane connection is established is triggered; The time period for triggering establishment of a user plane connection; An area that triggers establishment of a user plane connection; A tracking area identifier that triggers establishment of a user plane connection; The geographical location that triggers the establishment of a user plane connection.

30. The method according to any one of claims 22 to 28, characterized in that: The parameters related to the terminal releasing the user plane connection include at least one of the following: The time point for periodically releasing the user plane connection; The time period for periodically releasing the user plane connection; The number of times the user plane connection is periodically released; A timer for periodically releasing user plane connections; Trigger the LCS process of releasing the user plane connection; An event that triggers the release of a user plane connection; The time point at which the user plane connection is released is triggered; The time period for triggering the release of the user plane connection; An area that triggers the release of a user plane connection; A tracking area identifier that triggers the release of the user plane connection; A geographical location that triggers the release of a user plane connection; Method for releasing user plane connection.

31. The method according to claim 30, characterized in that The method of releasing the user plane connection includes at least one of the following: The terminal sends all data packets to the LMF network element and releases the current user plane connection; The terminal releases the current user plane connection and discards unsent data packets; After the terminal releases the current user plane connection, a new user plane connection is created; After the terminal creates a new user plane connection, it releases the current user plane connection.

32. A first network element, characterized in that: include: A transceiver module, configured to send at least one of a first notification and a first parameter to a second network element, so that the second network element sends at least one of the first notification and the first parameter to a terminal; The first notification is used to instruct the terminal to establish a user plane connection with the first network element; The first parameter includes at least one of the following: Parameters related to establishing a user plane connection with the terminal; Parameters related to the terminal releasing the user plane connection.

33. A second network element, characterized in that: include: a transceiver module, configured to receive at least one of a first notification and a first parameter sent by a first network element, and sending at least one of the first notification and the first parameter to a terminal; The first notification is used to instruct the terminal to establish a user plane connection with the first network element; The first parameter includes at least one of the following: Parameters related to establishing a user plane connection with the terminal; Parameters related to the terminal releasing the user plane connection.

34. A terminal, characterized in that: include: A transceiver module, configured to receive at least one of a first notification and a first parameter sent by a second network element; The first notification and the first parameter sent by the second network element are received from the first network element; The first notification is used to instruct the terminal to establish a user plane connection with the first network element; The first parameter includes at least one of the following: Parameters related to establishing a user plane connection with the terminal; Parameters related to the terminal releasing the user plane connection.

35. A communication system, characterized in that: It includes a first network element, a second network element, and a terminal, wherein the first network element is configured to implement the communication method described in any one of claims 1 to 9, the second network element is configured to implement the communication method described in any one of claims 10 to 21, and the terminal is configured to implement the communication method described in any one of claims 22 to 31.

36. A storage medium storing instructions, characterized in that: When the instruction is executed on a communication device, the communication device is caused to execute the communication method according to any one of claims 1-9, 10-21, and 22-31.

Citation Information

Patent Citations

  • PDU session switching method and device

    CN111436087A

  • Method for establishing connection, communication device and system

    CN113453292A

  • User plane connection establishment method and device, and storage medium

    CN116889083A

  • Session management method and terminal

    WO2019047209A1

  • Session release method and apparatus

    WO2021203249A1