Connection release method, device, and storage medium

Abstract

Embodiments of the present invention relate to a connection release method, a device, and a storage medium. The method comprises: sending a first message to a second network element, the first message being used for triggering and releasing a user plane connection, the user plane connection being a connection between a terminal device and a first network element, the first network element being a network element having a location management function or a sensing function, and the second network element being a network element having an access and mobility management function. In this way, the terminal device can actively trigger release of a user plane connection through the first message, thereby improving the flexibility of user plane connection management.

Description

Connection release method, device and storage medium Technical Field

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

[0002] In a wireless communication system, a user plane connection can be established between a terminal device and a network element with positioning management functions, and positioning-related messages can be sent or received through the user plane connection, thereby improving the communication efficiency of the positioning service.

[0003] Summary of the Invention

[0004] The embodiments of the present disclosure provide a connection release method, device, and storage medium.

[0005] According to a first aspect of an embodiment of the present disclosure, a connection release method is provided, which is executed by a terminal device. The method includes:

[0006] A first message is sent to the second network element, where the first message is used to trigger the release of the user plane connection, where the user plane connection is the connection between the terminal device and the first network element, where the first network element is a network element with a positioning management function or a perception function, and where the second network element is a network element with an access and mobility management function.

[0007] According to a second aspect of an embodiment of the present disclosure, a connection release method is proposed, which is performed by a second network element, where the second network element is a network element having access and mobility management functions. The method includes:

[0008] receiving a first message sent by a terminal device, where the first message is used to trigger the release of a user plane connection, where the user plane connection is a connection between the terminal device and a first network element, where the first network element is a network element having a positioning management function or a perception function;

[0009] A fourth message is sent to the first network element, where the fourth message is used to request the first network element to release the user plane connection.

[0010] According to a third aspect of an embodiment of the present disclosure, a connection release method is provided, which is performed by a first network element, where the first network element is a network element having a positioning management function or a perception function. The method includes:

[0011] receiving a fourth message sent by the second network element, where the fourth message is used to request the first network element to release a user plane connection, where the user plane connection is a connection between a terminal device and the first network element;

[0012] Determine whether to accept the request of the terminal device to release the user plane connection.

[0013] According to a fourth aspect of an embodiment of the present disclosure, a connection release method is provided, which is performed by a core network device, wherein the core network device includes a first network element and a second network element, wherein the first network element is a network element having a positioning management function or a perception function, and the second network element is a network element having an access and mobility management function. The method includes:

[0014] The second network element receives a first message sent by the terminal device, where the first message is used to trigger the release of a user plane connection, where the user plane connection is a connection between the terminal device and the first network element, and the first network element is a network element having a positioning management function or a perception function;

[0015] The second network element sends a fourth message to the first network element, where the fourth message is used to request the first network element to release the user plane connection;

[0016] The first network element determines whether to accept the request of the terminal device to release the user plane connection.

[0017] According to a fifth aspect of an embodiment of the present disclosure, a terminal device is provided, including:

[0018] The transceiver module is configured to send a first message to the second network element, where the first message is used to trigger the release of the user plane connection. The user plane connection is a connection between the terminal device and the first network element. The first network element is a network element with a positioning management function or a perception function, and the second network element is a network element with an access and mobility management function.

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

[0020] The transceiver module is configured to receive a first message sent by a terminal device, where the first message is used to trigger the release of a user plane connection, where the user plane connection is a connection between the terminal device and a first network element, where the first network element is a network element with a positioning management function or a perception function; and send a fourth message to the first network element, where the fourth message is used to request the first network element to release the user plane connection.

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

[0022] a transceiver module configured to receive a fourth message sent by the second network element, where the fourth message is used to request the first network element to release a user plane connection, where the user plane connection is a connection between a terminal device and the first network element;

[0023] The processing module is configured to determine whether to accept the request of the terminal device to release the user plane connection.

[0024] According to the eighth aspect of an embodiment of the present disclosure, a core network device is proposed, which may include a first network element and a second network element; wherein, the first network element is configured to execute the method described in the optional implementation manner of the third aspect, and the second network element is configured to execute the method described in the optional implementation manner of the second aspect.

[0025] According to the ninth aspect of an embodiment of the present disclosure, a communication system is proposed, which may include a terminal device, an access network device, a core network device and a server, wherein the core network device includes a first network element and a second network element; wherein the terminal device is configured to execute the method described in the optional implementation manner of the first aspect, the access network device is configured to execute the method described in the optional implementation manner of the fourth aspect, the first network element is configured to execute the method described in the optional implementation manner of the third aspect, the second network element is configured to execute the method described in the optional implementation manner of the second aspect, and the server is configured to execute the method described in the optional implementation manner of the fifth aspect.

[0026] According to a tenth aspect of an embodiment of the present disclosure, a communication device is proposed, comprising: one or more processors; wherein the communication device can be used to execute an optional implementation of the first aspect, the second aspect, the third aspect or the fourth aspect.

[0027] According to the eleventh aspect of an embodiment of the present disclosure, a storage medium is proposed, which stores instructions. When the instructions are executed on a communication device, the communication device executes the method described in the optional implementation of the first aspect, the second aspect, the third aspect or the fourth aspect.

[0028] The technical solution provided by the embodiments of the present disclosure can achieve the following beneficial effects: a first message is sent to a second network element, the first message being used to trigger the release of a user plane connection, where the user plane connection is a connection between a terminal device and a first network element, the first network element being a network element with a positioning management function or a perception function, and the second network element being a network element with an access and mobility management function. In this way, the terminal device can proactively trigger the release of the user plane connection through the first message, thereby improving the flexibility of user plane connection management.

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

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

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

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

[0033] FIG2A is a schematic flow chart of a connection release method according to an embodiment of the present disclosure.

[0034] FIG2B is a schematic flow chart of a connection release method according to an embodiment of the present disclosure.

[0035] FIG2C is a schematic flow chart of a connection release method according to an embodiment of the present disclosure.

[0036] FIG2D is a schematic flow chart of a connection release method according to an embodiment of the present disclosure.

[0037] FIG2E is a schematic flow chart of a connection release method according to an embodiment of the present disclosure.

[0038] FIG3A is a schematic flow chart showing a connection release method according to an embodiment of the present disclosure.

[0039] FIG3B is a schematic flow chart of a connection release method according to an embodiment of the present disclosure.

[0040] FIG3C is a schematic flow chart of a connection release method according to an embodiment of the present disclosure.

[0041] FIG3D is a schematic flow chart of a connection release method according to an embodiment of the present disclosure.

[0042] FIG4A is a schematic flow chart showing a connection release method according to an embodiment of the present disclosure.

[0043] FIG4B is a schematic flow chart of a connection release method according to an embodiment of the present disclosure.

[0044] FIG4C is a schematic flow chart of a connection release method according to an embodiment of the present disclosure.

[0045] FIG5A is a schematic flow chart of a connection release method according to an embodiment of the present disclosure.

[0046] FIG5B is a schematic flow chart of a connection release method according to an embodiment of the present disclosure.

[0047] FIG5C is a schematic flow chart of a connection release method according to an embodiment of the present disclosure.

[0048] FIG5D is a schematic flow chart of a connection release method according to an embodiment of the present disclosure.

[0049] FIG5E is a schematic flow chart of a connection release method according to an embodiment of the present disclosure.

[0050] FIG6 is a schematic flow chart of a connection release method according to an embodiment of the present disclosure.

[0051] FIG7A is a schematic structural diagram of a terminal device according to an embodiment of the present disclosure.

[0052] FIG7B is a schematic structural diagram of a first network element according to an embodiment of the present disclosure.

[0053] FIG7C is a schematic structural diagram of a second network element according to an embodiment of the present disclosure.

[0054] FIG8A is a schematic structural diagram of a communication device according to an embodiment of the present disclosure.

[0055] FIG8B is a schematic structural diagram of a chip according to an embodiment of the present disclosure. DETAILED DESCRIPTION

[0056] The embodiments of the present disclosure provide a connection release method, device, and storage medium.

[0057] In a first aspect, an embodiment of the present disclosure provides a connection release method, which is executed by a terminal device. The method includes:

[0058] A first message is sent to the second network element, where the first message is used to trigger the release of the user plane connection, where the user plane connection is the connection between the terminal device and the first network element, where the first network element is a network element with a positioning management function or a perception function, and where the second network element is a network element with an access and mobility management function.

[0059] In the above embodiment, the terminal device can actively trigger the release of the user plane connection through the first message, thereby improving the flexibility of user plane connection management.

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

[0061] First message identifier;

[0062] User plane connection release reason;

[0063] User plane connection identifier;

[0064] Terminal device identification;

[0065] First network element identifier.

[0066] In the above embodiment, the release of the user plane connection may be triggered by the above at least one item of information in the first message.

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

[0068] Receive a second message sent by the second network element, where the second message is any one of the following:

[0069] a first release message, where the first release message is used to indicate that the user plane connection has been released by the first network element;

[0070] a second release message, where the second release message is used to instruct the terminal device to release the user plane connection;

[0071] A rejection message, where the rejection message is used to reject the terminal device from releasing the user plane connection.

[0072] In the above embodiments, flexible management of user plane connections can be achieved through any of the above items.

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

[0074] User plane connection identifier;

[0075] Terminal device identification;

[0076] First network element identifier.

[0077] In the above embodiment, the user plane connection can be flexibly managed through at least one of the above items.

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

[0079] Determining that the second message is the second release indication information;

[0080] The user plane connection is released.

[0081] In the above embodiment, the user plane connection may be released by the terminal device.

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

[0083] A third message is sent to the second network element, where the third message is used to indicate that the user plane connection has been released by the terminal device.

[0084] In the above embodiment, the terminal device is notified through the third message that the release of the user plane connection has been completed, thereby improving the reliability of user plane connection management.

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

[0086] Determining that there is no other user plane connection between the terminal device and the first network element;

[0087] Release the packet data unit PDU session where the user plane connection is located, and the PDU session is used to carry the user plane connection between the terminal device and the first network element.

[0088] In the above embodiment, the PDU session can be released to save system resources.

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

[0090] Ensure that the first condition is met;

[0091] resending the first message;

[0092] The first condition includes at least one of the following:

[0093] The second message is used to refuse the terminal device from releasing the user plane connection;

[0094] The second message is not received within a specific time after the first message is sent.

[0095] In the above embodiment, when the user plane connection is not released, the terminal device may resend the first message to trigger the release of the user plane connection again, thereby improving the reliability of user plane connection management.

[0096] In a second aspect, an embodiment of the present disclosure provides a connection release method, which is performed by a second network element, where the second network element is a network element having access and mobility management functions. The method includes:

[0097] receiving a first message sent by a terminal device, where the first message is used to trigger the release of a user plane connection, where the user plane connection is a connection between the terminal device and a first network element, where the first network element is a network element having a positioning management function or a perception function;

[0098] A fourth message is sent to the first network element, where the fourth message is used to request the first network element to release the user plane connection.

[0099] In the above embodiment, the second network element forwards the first message, which can realize the user plane connection release triggered by the terminal device, thereby improving the flexibility of user plane connection management.

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

[0101] First message identifier;

[0102] User plane connection release reason;

[0103] User plane connection identifier;

[0104] Terminal device identification;

[0105] First network element identifier.

[0106] With reference to some embodiments of the second aspect, in some embodiments, the first message includes a first network element identifier; and sending the fourth message includes:

[0107] Send the fourth message to the first network element corresponding to the first network element identifier.

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

[0109] Receive a fifth message sent by the first network element, where the fifth message is any one of the following:

[0110] a first release message, where the first release message is used to indicate that the user plane connection has been released by the first network element;

[0111] a second release message, where the second release message is used to instruct the terminal device to release the user plane connection;

[0112] A rejection message, where the rejection message is used to reject the terminal device from releasing the user plane connection.

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

[0114] User plane connection identifier;

[0115] Terminal device identification;

[0116] First network element identifier.

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

[0118] A second message is sent to the terminal device, where the content indicated by the second message is the same as that of the fifth message.

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

[0120] receiving a third message sent by the terminal device, where the third message is used to indicate that the user plane connection has been released by the terminal device;

[0121] A sixth message is sent to the first network element, where content indicated by the sixth message is the same as that of the third message.

[0122] In a third aspect, an embodiment of the present disclosure provides a connection release method, which is performed by a first network element, where the first network element is a network element having a positioning management function or a perception function. The method includes:

[0123] receiving a fourth message sent by the second network element, where the fourth message is used to request the first network element to release a user plane connection, where the user plane connection is a connection between a terminal device and the first network element;

[0124] Determine whether to accept the request of the terminal device to release the user plane connection.

[0125] In the above embodiment, the first network element determines whether to accept the request of the terminal device to release the user plane connection, thereby realizing the user plane connection release triggered by the terminal device and improving the flexibility and security of user plane connection management.

[0126] In conjunction with some embodiments of the third aspect, in some embodiments, the fourth message includes at least one of the following:

[0127] First message identifier;

[0128] User plane connection release reason;

[0129] User plane connection identifier;

[0130] Terminal device identification;

[0131] First network element identifier.

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

[0133] Send a fifth message, where the fifth message includes any one of the following:

[0134] first release indication information, where the first release indication is used to indicate that the user plane connection has been released by the first network element;

[0135] Second release indication information, where the second release indication is used to instruct the terminal device to release the user plane connection;

[0136] Rejection information, where the rejection information is used to reject the terminal device from releasing the user plane connection.

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

[0138] Release the user plane connection between the terminal device and the first network element.

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

[0140] Receive a sixth message sent by the second network element, where the sixth message is used to indicate that the user plane connection has been released by the terminal device.

[0141] In a fourth aspect, an embodiment of the present disclosure provides a connection release method, which is performed by a core network device, wherein the core network device includes a first network element and a second network element, wherein the first network element is a network element having a positioning management function or a perception function, and the second network element is a network element having an access and mobility management function. The method includes:

[0142] The second network element receives a first message sent by the terminal device, where the first message is used to trigger the release of a user plane connection, where the user plane connection is a connection between the terminal device and the first network element, and the first network element is a network element having a positioning management function or a perception function;

[0143] The second network element sends a fourth message to the first network element, where the fourth message is used to request the first network element to release the user plane connection;

[0144] The first network element determines whether to accept the request of the terminal device to release the user plane connection.

[0145] In a fifth aspect, an embodiment of the present disclosure proposes a terminal device, which may include at least one of a transceiver module and a processing module; wherein the terminal device can be used to execute the optional implementation method of the first aspect.

[0146] In a sixth aspect, an embodiment of the present disclosure proposes a second network element, which may include at least one of a transceiver module and a processing module; wherein the second network element may be used to execute an optional implementation method of the second aspect.

[0147] In the seventh aspect, an embodiment of the present disclosure proposes a first network element, which may include at least one of a transceiver module and a processing module; wherein the first network element can be used to execute the optional implementation method of the third aspect.

[0148] In the eighth aspect, an embodiment of the present disclosure proposes a core network device, which may include a first network element and a second network element; wherein, the first network element is configured to execute the method described in the optional implementation manner of the third aspect, and the second network element is configured to execute the method described in the optional implementation manner of the second aspect.

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

[0150] In the tenth aspect, an embodiment of the present disclosure proposes a communication device, which may include: one or more processors; wherein the communication device can be used to execute optional implementation methods of the first aspect, the second aspect, the third aspect or the fourth aspect.

[0151] In the sixteenth aspect, an embodiment of the present disclosure proposes a storage medium storing instructions, which, when executed on a communication device, enables the communication device to execute the method described in the optional implementation of the first aspect, the second aspect, the third aspect or the fourth aspect.

[0152] In the seventeenth aspect, an embodiment of the present disclosure proposes a program product, which, when executed by a communication device, enables the communication device to execute the method described in the optional implementation manner of the first aspect, the second aspect, the third aspect or the fourth aspect.

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

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

[0155] It is understandable that the above-mentioned terminal devices, network devices (access network devices, core network devices, first network elements, second network elements), communication devices, communication systems, storage media, program products, computer programs, chips, or chip systems can all be used to perform the methods proposed in the embodiments of the present disclosure. Therefore, the beneficial effects that can be achieved can refer to the beneficial effects of the corresponding methods and will not be repeated here.

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

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

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

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

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

[0161] In some embodiments, "plurality" may refer to two or more.

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

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

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

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

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

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

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

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

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

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

[0172] In some embodiments, the terms "Access Network Device (AN Device)", "Radio Access Network Device (RAN Device)", "Base Station (BS)", "Radio Base Station (Radio Base Station)", "Fixed Station (Fixed Station)", "Node (Node)", "Access Point (Access Point)", "Transmission Point (TP)", "Reception Point (RP)", "Transmission and / or Reception Point (TRP))", "Panel (Panel)", "Antenna Panel (Antenna Panel)", "Antenna Array (Antenna Array)" "Cell (Cell)", "Macro Cell (Macro Cell)", "Small Cell (Small Cell)", "Femto Cell (Femto Cell)", "Pico Cell (Pico Cell)" "Sector (Sector)", "Cell Group (Cell Group)", "Serving Cell (Cell)", "Carrier (Carrier)", "Component Carrier (Component Carrier)", "Bandwidth Part (BWP)" and the like may be used interchangeably.

[0173] In some embodiments, the terms "terminal", "terminal device", "terminal device", "user equipment (UE)", "user terminal" "mobile station (MS)", "mobile terminal (MT)", subscriber station (Subscriber Station), mobile unit (Mobile Unit), subscriber unit (Subscriber Unit), wireless unit (Wireless Unit), remote unit (Remote Unit), mobile device (Mobile Device), wireless device (Wireless Device), wireless communication device (Wireless Communication Device), remote device (Remote Device), mobile subscriber station (Mobile Subscriber Station), access terminal (Access Terminal), mobile terminal (Mobile Terminal), wireless terminal (Wireless Terminal), remote terminal (Remote Terminal), handset (Handset), user agent (User Agent), mobile client (Mobile Client), client (Client) and the like can be used interchangeably.

[0174] In some embodiments, the access network device, the core network device, or the network device can be replaced by a terminal device. 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 device is replaced by the communication between multiple terminal devices (for example, device-to-device (D2D), vehicle-to-everything (V2X), etc.). In this case, it is also possible to set the structure in which the terminal device has all or part of the functions of the access network device. In addition, terms such as "uplink" and "downlink" can also be replaced by terms corresponding to communication between terminal devices (for example, "side"). For example, uplink channels, downlink channels, etc. can be replaced by side channels or direct channels, and uplinks, downlinks, etc. can be replaced by side links or direct links.

[0175] In some embodiments, the terminal device 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 device.

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

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

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

[0179] FIG1A is a schematic diagram illustrating an architecture of a communication system according to an embodiment of the present disclosure. As shown in FIG1A , the communication system 100 may include a terminal device 101 , an access network device 102 , and a core network device 103 .

[0180] In some embodiments, the terminal device 101 may include at least one of a mobile phone, a wearable device, an Internet of Things device, a car with communication capabilities, a smart car, a tablet computer, a computer with wireless transceiver capabilities, 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 smart grid, a wireless terminal device in transportation safety, a wireless terminal device in smart city, and a wireless terminal device in smart home, but is not limited thereto.

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

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

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

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

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

[0186] In some embodiments, the first network element 1031 may be a sensing function (SF).

[0187] In some embodiments, the first network element 1031 may be a network element having a positioning management function or a perception function, and the name is not limited thereto.

[0188] In some embodiments, the second network element 1032 may be an Access and Mobility Management Function (AMF).

[0189] In some embodiments, the second network element 1032 may be a network element having access and mobility management functions, but the name is not limited thereto.

[0190] In some embodiments, the third network element 1033 may be a user plane function (UPF).

[0191] In some embodiments, the third network element 1033 may be a network element having a user plane function, and the name is not limited thereto.

[0192] In some embodiments, the first network element 1031 may be independent of the core network device 103 .

[0193] In some embodiments, the first network element 1031 may be a part of the core network device 103 .

[0194] In some embodiments, the first network element 1031 may be a network element of an operator, or a network element provided by a third party other than the operator.

[0195] Figure 1B is a schematic diagram of the architecture of another communication system according to an embodiment of the present disclosure. As shown in Figure 1B, the communication system 100 may include a terminal device 101, an access network device 102, and a core network device 103. The core network device 103 may include at least one of the LMF, AMF, and UPF.

[0196] In some embodiments, the core network device 103 described in the embodiment of the present disclosure may further include other network elements, such as one or more of a session management function (SMF), a unified data management (UDM), a network exposure function (NEF), and a policy control function (PCF). For the specific functions, connection relationships, and implementation methods of the above-mentioned LMF, AMF, UPF, SMF, UDM, NEF, and PCF, reference may be made to the relevant descriptions in the relevant technologies (e.g., 3GPP protocols), which will not be elaborated in this disclosure.

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

[0198] The following embodiments of the present disclosure may be applied to the communication system 100 shown in FIG1A , or a portion thereof, but are not limited thereto. The entities shown in FIG1A are examples. The communication system may include all or part of the entities shown in FIG1A , or may include other entities outside of FIG1A . The number and form of the entities are arbitrary. The entities may be physical or virtual. The connection relationship between the entities is an example. The entities may be connected or disconnected. The connection may be in any manner, whether direct or indirect, and may be wired or wireless.

[0199] The embodiments of the present disclosure may be applied to Long Term Evolution (LTE), LTE-Advanced (LTE-A), LTE-Beyond (LTE-B), SUPER 3G, IMT-Advanced, 4th generation mobile communication system (4G), 5th generation mobile communication system (5G), 5G New Radio (NR), 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.17 (WiMAX (registered trademark)), IEEE 802.18 (WiMAX (registered trademark)), IEEE 802.19 (WiMAX (registered trademark)), IEEE 802.20 (WiMAX (registered trademark)), IEEE 802.21 (WiMAX (registered trademark)), IEEE 802.22 (WiMAX (registered trademark)), IEEE 802.23 (WiMAX (registered trademark)), IEEE 802.24 (WiMAX (registered trademark)), IEEE 802.25 (WiMAX (registered trademark)), IEEE 802.26 (WiMAX (registered trademark)), IEEE 802.27 (WiMAX (registered trademark)), IEEE 802.28 (WiMAX (registered trademark)), IEEE 802.29 (WiMAX (registered trademark)), IEEE 802.30 (WiMAX (registered trademark)), IEEE 802.31 (WiMAX (registered trademark)), IEEE 802.32 (WiMAX (registered trademark)), IEEE 802.33 (WiMAX (registered trademark)), 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).

[0200] In some embodiments of the present disclosure, a terminal device and a first network element in the above-mentioned communication system may establish a user plane connection, and the terminal device and the first network element may communicate via the user plane connection. For example, a path for the terminal device to send data to the first network element via the user plane connection may include: terminal device -> access network device -> third network element (e.g., UPF) -> first network element (e.g., LMF); a path for the first network element to send data to the terminal device via the user plane connection may include: first network element (e.g., LMF) -> third network element (e.g., UPF) -> access network device -> terminal device.

[0201] In some embodiments, the terminal device and the first network element can send or receive positioning-related messages through the user plane connection. In this way, by establishing a direct connection with the terminal device through the first network element, there is no need for an intermediate network element (such as an access network device or a second network element) to process the signaling protocol stack, which can improve the communication efficiency of the positioning service. The above-mentioned positioning-related messages may include LTE Positioning Protocol (LPP) messages, Location Service Supplementary Services Messages, Location Services Messages, or other positioning-related messages.

[0202] In some embodiments, the first network element or the terminal device may trigger the establishment of a user plane connection.

[0203] In some embodiments, the first network element or terminal device may maintain the established user plane connection.

[0204] In some embodiments, the first network element or the terminal device may modify or terminate the established user plane connection.

[0205] In some embodiments, the first network element or the terminal device may release the user plane connection between the terminal device and the first network element via the control plane. For example, the first network element may send a user plane connection release command message via the control plane to initiate the release of the user plane connection.

[0206] In some embodiments of the present disclosure, the above-mentioned user plane connection can be carried by a PDU session.

[0207] In some embodiments, the first network element (e.g., LMF) may send user plane information to the terminal device through a downlink non-access stratum transport (DL NAS TRANSPORT) message of the second network element (e.g., AMF), and the user plane information may include the Internet Protocol (IP) address or fully qualified domain name (FQDN) of the first network element. Optionally, if the first network element sends the FQDN to the terminal device, a domain name system (DNS) server or resolver may be used to resolve the IP address of the first network element. For example, the DNS server may be an edge application server discovery function (EASDF) or a local DNS for local LMF address resolution.

[0208] In some embodiments, the terminal device may establish a PDU session for user plane positioning. For example, the terminal device may establish the PDU session based on a User-Defined Routing Service Profile (URSP), where the URSP includes PDU session parameters related to user plane positioning, such as a dedicated data network name (DNN) and a slice network service access identifier (S-NSSAI).

[0209] In some embodiments, the SMF may select a third network element (e.g., UPF) to connect to the first network element based on the S-NSSAI, DNN, and location information of the terminal device to establish the above-mentioned PDU session. Optionally, the third network element may be a protocol data unit session anchor (PSA) UPF, and the PSA UPF may be located at a central site or a local site.

[0210] In some embodiments, the above-mentioned PDU session can be used to carry the user plane connection between the terminal device and the first network element.

[0211] In some embodiments, the terminal device and the first network element may establish one or more user plane connections, and the one or more user plane connections may all be carried by one PDU session.

[0212] FIG2A is a flow chart of a connection release method according to an embodiment of the present disclosure. The method may be executed by the above-mentioned communication system. As shown in FIG2A , the method may include:

[0213] Step S2101: The terminal device determines to initiate a user plane connection release request.

[0214] In some embodiments, the terminal device may determine whether to initiate a user plane connection release request based on its own status.

[0215] For example, the terminal device may determine to initiate a user plane connection release request when the positioning service ends normally.

[0216] For another example, the terminal device may determine to initiate a user plane connection release request according to an instruction input by the user.

[0217] Step S2102: The terminal device sends a first message to the second network element.

[0218] In some embodiments, the second network element may receive the first message. For example, the second network element may receive the first message sent by the terminal device.

[0219] In some embodiments, the second network element is a network element having access and mobility management functions, for example, the second network element may be an AMF.

[0220] In some embodiments, the first message can be used to trigger the release of the user plane connection, where the user plane connection is a connection between a terminal device and a first network element, where the first network element is a network element having a positioning management function or a perception function, for example, the first network element can be an LMF or SF.

[0221] In some embodiments, the first message may be used to request release of the user plane connection.

[0222] In some embodiments, the name of the first message is not limited, and may be, for example, a "user plane connection release request message", a "connection release request message", a "positioning connection release request message", etc.

[0223] In some embodiments, the first message may include at least one of the following:

[0224] A first message identifier, such as a user plane connection release request message identity;

[0225] User plane connection release reason, which can be used to indicate the reason why the terminal device releases the user plane connection;

[0226] A user plane connection identifier, where the user plane connection identifier may indicate a user plane connection requested to be released;

[0227] Terminal device identification, which can be used to indicate the terminal device that triggers the release of the user plane connection;

[0228] A first network element identifier, where the first network element identifier can be used to indicate the first network element corresponding to the user plane connection.

[0229] Optionally, the first network element identifier may be any one of the following: an IP address of the first network element, a routing identifier (Routing ID) of the first network element, or a correlation identifier (Correlation ID) of the first network element.

[0230] Optionally, the terminal device identifier can be used to uniquely identify the terminal device that triggers the release of the user plane connection. For example, the terminal device identifier may include at least one of SUCI (Subscription Concealed Identifier), SUPI (Subscriber Permanent Identifier), GPSI (Generic Public Subscription Identifier), Application Layer ID, GUTI (Globally Unique Temporary Identifier), PEI (Permanent Equipment Identifier), IMEI (International Mobile Equipment Identity), IMSI (International Mobile Subscriber Identity), TMSI (Temporary Mobile Subscriber Identity) or RNTI (Radio Network Temporary Identity). The GUTI can be 5G-GUTI, 4G-GUTI, or GUTI under other network standards, which is not limited in the embodiments of the present disclosure.

[0231] Optionally, the above-mentioned reason for releasing the user plane connection may be a reason agreed upon in the protocol, or a reason determined by the terminal device according to the scenario that triggers the release of the user plane connection.

[0232] In some embodiments, the first message may be carried in a non-access stratum (NAS) message or other message sent by the terminal side device to the second network element. Optionally, the first message may be encapsulated in a container of an uplink non-access stratum transport (UL NAS TRANSPORT) message, which may be a user plane positioning connection information (UPP-CMI) container.

[0233] In some embodiments, the terminal device may send the first message to the second network element via the access network device. Optionally, the access network device only forwards the first message.

[0234] In some embodiments, the terminal device may start a timer. For example, the terminal device may start a timer when sending a first message. The timer may be used to determine whether a response to the first message (e.g., a second message) is received within a time range. If a response to the first message is received, the terminal device may stop the timer. In some embodiments, if no response to the first message is received before the timer expires, the first message may be resent.

[0235] Step S2103: The second network element sends a fourth message to the first network element.

[0236] In some embodiments, the first network element may receive the fourth message. For example, the first network element may receive the fourth message sent by the second network element.

[0237] In some embodiments, the fourth message may be used to request the first network element to release the user plane connection.

[0238] In some embodiments, the fourth message can be used to request the first network element to accept the request of the terminal device to release the user plane connection.

[0239] In some embodiments, the name of the fourth message is not limited, and may be, for example, a "user plane connection release request message", a "connection release request message", a "positioning connection release request message", etc.

[0240] In some embodiments, the content of the fourth message may be the same as the first message. For example, the second network element may forward all the content of the first message to the first network element.

[0241] In some embodiments, the fourth message may include part of the content of the first message. For example, the second network element may forward part of the content of the first message to the first network element.

[0242] In some embodiments, the above-mentioned first message includes a first network element identifier, and the second network element may send the fourth message to the first network element corresponding to the first network element identifier.

[0243] In some embodiments, the fourth message may be carried in an N1 interface message notification (Namf_Communication_N1MessageNotify). For example, the second network element may forward the first message received from the terminal device in step S2102 to the first network element via Namf_Communication_N1MessageNotify.

[0244] Step S2104: The first network element determines whether to accept the user plane connection release request.

[0245] In some embodiments, the first network element determines whether to accept the request of the terminal device to release the user plane connection.

[0246] In some embodiments, the first network element may determine whether to accept or reject the request of the terminal device to release the user plane connection based on its own configuration information and / or permission information of the terminal device.

[0247] Step S2105: The first network element releases the user plane connection.

[0248] In some embodiments, the first network element may release the user plane connection between the terminal device and the first network element.

[0249] In some embodiments, the first network element may release the user plane connection between the terminal device and the first network element when determining to accept the request of the terminal device to release the user plane connection.

[0250] In some embodiments, the first network element may determine the user plane connection to be released according to the user plane connection identifier.

[0251] In some embodiments, the user plane connection may be an IP connection, a TCP connection, or a UDP connection. If the user plane connection is a TCP connection, the first network element may complete the release of the TCP connection as the active release party.

[0252] In some embodiments, step S2105 is optional. For example, if the first network element determines to reject the terminal device's request to release the user plane connection, step S2105 is not performed. For another example, if the terminal device can release the user plane connection, the first network element may not perform step S2105.

[0253] In some embodiments, the first network element executes step S2105 to release the user plane connection, and the terminal device may also execute step S2108 to release the user plane connection. In this way, the first network element and the terminal device can each release the user plane connection at their respective ends, thereby improving the reliability of the connection release.

[0254] Step S2106: The first network element sends a fifth message to the second network element.

[0255] In some embodiments, the second network element may receive the fifth message. For example, the second network element may receive the fifth message sent by the first network element.

[0256] In some embodiments, the fifth message may be a first release message, and the first release message may be used to indicate that the user plane connection has been released by the first network element.

[0257] For example, after executing step S2105 to release the user plane connection, the first network element may execute step S2106 to send a first release message to the second network element, indicating through the first release message that the user plane connection has been released by the first network element.

[0258] For another example, the first network element may execute step S2105 and step S2106 in parallel, release the user plane connection, and send a first release message to the second network element, indicating through the first release message that the user plane connection has been released by the first network element.

[0259] For another example, the first network element may first execute step S2106 to send a first release message to the second network element, and then execute step S2105.

[0260] Optionally, the first release message may include a release indication.

[0261] Optionally, the name of the first release message is not limited, for example, it can be "user plane connection release response message" or the like.

[0262] In some other embodiments, the fifth message may be a second release message, and the second release message may be used to instruct the terminal device to release the user plane connection.

[0263] For example, after the first network element determines in step S2104 that it accepts the user plane connection release request, it may not execute step S2105 but execute step S2106 to send a second release message to the second network element, instructing the terminal device to release the user plane connection through the second release message.

[0264] Optionally, the second release message may include a release indication.

[0265] Optionally, the name of the second release message is not limited, for example, it can be "user plane connection release command message", "user plane connection release instruction message", "user plane connection release acceptance message", etc.

[0266] In some other embodiments, the fifth message may be a rejection message, which may be used to reject the terminal device from releasing the user plane connection.

[0267] For example, after the first network element determines in step S2104 to reject the user plane connection release request, it may not execute step S2105 but execute step S2106 to send a rejection message to the second network element, thereby rejecting the terminal device from releasing the user plane connection through the rejection message.

[0268] Optionally, the rejection message may include a rejection indication and a rejection reason.

[0269] Optionally, the name of the rejection message is not limited, for example, it can be "user plane connection release rejection message" or the like.

[0270] In some embodiments, the fifth message may be carried in Namf_Communication_N1MessageNotify. For example, the first network element may send the fifth message to the second network element via Namf_Communication_N1MessageNotify.

[0271] In some embodiments, the second message may include at least one of the following:

[0272] User plane connection identifier;

[0273] Terminal device identification;

[0274] First network element identifier.

[0275] Step S2107: The second network element sends a second message to the terminal device.

[0276] In some embodiments, the terminal device may receive the second message. For example, the terminal device may receive the second message sent by the second network element.

[0277] In some embodiments, the content indicated by the second message is the same as that of the fifth message mentioned above.

[0278] In some embodiments, the second message includes the entire content of the fifth message.

[0279] In some embodiments, the second message includes part of the content of the fifth message.

[0280] In some embodiments, the fifth message is a first release message, and the second message may be a first release message, which is used to indicate that the user plane connection has been released by the first network element.

[0281] In some embodiments, the fifth message is a second release message, and the second message may be a second release message used to instruct the terminal device to release the user plane connection.

[0282] In some embodiments, the fifth message is a rejection message, and the second message may be a rejection message, which is used to reject the terminal device from releasing the user plane connection.

[0283] In some embodiments, the second message may be carried in a NAS message or other message sent by the second network element to the terminal device. Optionally, the second message may be encapsulated in a container of a DL NAS TRANSPORT message, which may be a UPP-CMI container.

[0284] In some embodiments, the second message may include at least one of the following:

[0285] User plane connection identifier;

[0286] Terminal device identification;

[0287] First network element identifier.

[0288] In some embodiments, if the second message received by the terminal device is a rejection message, the user plane connection may be maintained.

[0289] In some embodiments, if the second message received by the terminal device is a rejection message, the first message may be resent.

[0290] In some embodiments, the terminal device may determine that the first condition is satisfied and resend the first message. Alternatively, the terminal device may resend the first message if the first condition is satisfied. Alternatively, the terminal device may resend the first message after a certain period of time after determining that the first condition is satisfied.

[0291] The first condition may include at least one of the following:

[0292] The second message is used to refuse the terminal device from releasing the user plane connection;

[0293] The second message is not received within a specific time after the first message is sent.

[0294] In some embodiments, the specific time may be the duration of a timer. For example, the terminal device may start the timer when sending the first message and stop the timer when receiving the second message. If the second message is not received before the timer expires, the first message may be resent.

[0295] Step S2108: The terminal device releases the user plane connection.

[0296] In some embodiments, the terminal device may release the user plane connection between the terminal device and the first network element.

[0297] In some embodiments, the terminal device may determine that the received second message is second release indication information and release the user plane connection. Optionally, the terminal device may release the user plane connection if it is determined that the second message includes the second release indication information.

[0298] In some embodiments, the user plane connection may be an IP connection, a TCP connection, or a UDP connection. If the user plane connection is a TCP connection, the terminal device may complete the release of the TCP connection as the active release party.

[0299] In some embodiments, step S2108 is optional. For example, if the terminal device determines that the received second message is not the second release indication information (e.g., the first release message or a rejection message), step S2108 may not be performed. For another example, if the terminal device determines that the received second message is a rejection message, step S2108 may not be performed.

[0300] In some embodiments, when the terminal device determines that the received second message is the first release message, it may also release the user plane connection. In this way, the first network element and the terminal device can each release the user plane connection at their respective ends, thereby improving the reliability of the connection release.

[0301] Step S2109: The terminal device sends a third message to the second network element.

[0302] In some embodiments, the second network element may receive the third message. For example, the second network element may receive the third message sent by the terminal device.

[0303] In some embodiments, the third message may be used to indicate that the user plane connection has been released by the terminal device.

[0304] In some embodiments, the name of the third message is not limited, for example, it can be "user plane connection release completion message", "user plane connection release message", etc.

[0305] In some embodiments, the terminal device may execute step S2109 to send the third message after executing step S2108 to release the user plane connection.

[0306] In some embodiments, the terminal device may not execute step S2109 if it does not execute step S2108.

[0307] In some embodiments, the third message may be carried in a NAS message or other message sent by the terminal device to the second network element. Optionally, the third message may be encapsulated in a container of a UL NAS TRANSPORT message, which may be a UPP-CMI container.

[0308] In some embodiments, the third message may include at least one of the following:

[0309] User plane connection identifier;

[0310] Terminal device identification;

[0311] First network element identifier.

[0312] Step S2110: The second network element sends a sixth message to the first network element.

[0313] In some embodiments, the first network element may receive the sixth message. For example, the first network element may receive the sixth message sent by the second network element.

[0314] In some embodiments, the sixth message may be used to indicate that the user plane connection has been released by the terminal device.

[0315] In some embodiments, the sixth message can be used to notify the first network element that the terminal device has completed the release of the user plane connection.

[0316] In some embodiments, the name of the sixth message is not limited, for example, it can be "user plane connection release completion message", "user plane connection release message", etc.

[0317] In some embodiments, the content indicated by the sixth message may be the same as that of the third message.

[0318] In some embodiments, the content of the sixth message may be the same as the third message. For example, the second network element may forward all the content of the third message to the first network element.

[0319] In some embodiments, the sixth message may include part of the content of the third message. For example, the second network element may forward part of the content of the third message to the first network element.

[0320] In some embodiments, if the third message includes a first network element identifier, the second network element may send the sixth message to the first network element corresponding to the first network element identifier.

[0321] In some embodiments, the sixth message may be carried in Namf_Communication_N1MessageNotify. For example, the second network element may forward the third message received from the terminal device in step S2109 to the first network element through Namf_Communication_N1MessageNotify.

[0322] Step S2111: The terminal device releases the PDU session.

[0323] In some embodiments, the terminal device can determine that there is no other user plane connection between the terminal device and the first network element; release the packet data unit PDU session where the user plane connection is located, and the PDU session is used to carry the user plane connection between the terminal device and the first network element.

[0324] In some embodiments, the terminal device may determine that there is no activated user plane connection between the terminal device and the first network element; and release the PDU session where the user plane connection is located.

[0325] In some embodiments, the terminal device may send a PDU session release request to the second network element via a NAS message. The PDU session release request may include a session identifier of the PDU session. The first network element initiates the release of the PDU session in response to the PDU session release request. It should be noted that the specific implementation method of the PDU session release can be referred to the description in the relevant technology and will not be repeated here.

[0326] In some embodiments, step S2111 is an optional step. For example, if the terminal device determines that there are other user plane connections between the terminal device and the first network element, the PDU session can be maintained.

[0327] The method involved in the embodiment of the present disclosure may include at least one of the above steps S2101 to S2111. For example, step S2102 can be implemented as an independent embodiment, step S2103 can be implemented as an independent embodiment, step S2105 can be implemented as an independent embodiment, step S2108 can be implemented as an independent embodiment, steps S2101+S2102 can be implemented as an independent embodiment, steps S2102+S2107 can be implemented as an independent embodiment, steps S2101+S2102+S2103+S2104+S2105+S2106+S2107 can be implemented as an independent embodiment, steps S2102+S2103+S2104+S2105+S2106+S2107 can be implemented as an independent embodiment, and step S2108 can be implemented as an independent embodiment. 1+S2102+S2103+S2104+S2106+S2107+S2108 can be implemented as an independent embodiment, steps S2102+S2103+S2104+S2106+S2107+S2108 can be implemented as an independent embodiment, steps S2101+S2102+S2103+S2104+S2106+S2107+S2108+S2109+S2110+S2111 can be implemented as an independent embodiment, steps S2102+S2103+S2104+S2106+S2107+S2108+S2109+S2110+S2111 can be implemented as an independent embodiment, but are not limited to this.

[0328] In some embodiments, the above steps S2101 to S2111 can be executed in a swapped order or simultaneously.

[0329] In some embodiments, the above steps S2101 to S2111 are all optional steps.

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

[0331] By adopting the above method, the terminal device can actively trigger the release of the user plane connection through the first message, thereby improving the flexibility of user plane connection management.

[0332] FIG2B is an interactive diagram illustrating a connection release method according to an embodiment of the present disclosure. As shown in FIG2B , the embodiment of the present disclosure relates to a connection release method, which can be executed by a communication system and can include:

[0333] Step S2201: The terminal device determines to initiate a user plane connection release request.

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

[0335] Step S2202: The terminal device sends a first message to the second network element.

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

[0337] Step S2203: The second network element sends a fourth message to the first network element.

[0338] The optional implementation of step S2203 can refer to the optional implementation of step S2103 in FIG2A and other related parts in the embodiment involved in FIG2A , which will not be described in detail here.

[0339] Step S2204: The first network element determines whether to accept the user plane connection release request.

[0340] The optional implementation of step S2204 can refer to the optional implementation of step S2104 in FIG. 2A and other related parts in the embodiment involved in FIG. 2A , which will not be described in detail here.

[0341] Step S2205: The first network element releases the user plane connection.

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

[0343] Step S2206: The first network element sends a fifth message to the second network element.

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

[0345] Step S2207: The second network element sends a second message to the terminal device.

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

[0347] Step S2208: The terminal device releases the PDU session.

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

[0349] In some embodiments, the above steps are all optional steps.

[0350] In some embodiments, the embodiment shown in FIG. 2B may also be combined with any one or more steps in the embodiment shown in FIG. 2A to form a new embodiment.

[0351] FIG2C is an interactive diagram illustrating a connection release method according to an embodiment of the present disclosure. As shown in FIG2C , an embodiment of the present disclosure relates to a connection release method, which can be executed by a communication system and can include:

[0352] Step S2301: The terminal device determines to initiate a user plane connection release request.

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

[0354] Step S2302: The terminal device sends a first message to the second network element.

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

[0356] Step S2303: The second network element sends a fourth message to the first network element.

[0357] The optional implementation of step S2303 can refer to the optional implementation of step S2103 in FIG2A and other related parts in the embodiment involved in FIG2A , which will not be described in detail here.

[0358] Step S2304: The first network element determines whether to accept the user plane connection release request.

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

[0360] Step S2305: The first network element sends a fifth message to the second network element.

[0361] The optional implementation of step S2305 can refer to the optional implementation of step S2106 in FIG2A and other related parts in the embodiment involved in FIG2A , which will not be described in detail here.

[0362] In some embodiments, the fifth message may be second release indication information.

[0363] Step S2306: The second network element sends a second message to the terminal device.

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

[0365] Step S2307: The terminal device releases the user plane connection.

[0366] The optional implementation of step S2307 can refer to the optional implementation of step S2108 in FIG2A and other related parts in the embodiment involved in FIG2A , which will not be described in detail here.

[0367] Step S2308: The terminal device sends a third message to the second network element.

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

[0369] Step S2309: The second network element sends a sixth message to the first network element.

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

[0371] Step S2310: The terminal device releases the PDU session.

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

[0373] In some embodiments, the above steps are all optional steps.

[0374] In some embodiments, the embodiment shown in FIG. 2C may also be combined with any one or more steps in the embodiment shown in FIG. 2A to form a new embodiment.

[0375] FIG2D is an interactive diagram illustrating a connection release method according to an embodiment of the present disclosure. As shown in FIG2D , an embodiment of the present disclosure relates to a connection release method, which can be executed by a communication system and can include:

[0376] Step S2401: The terminal device determines to initiate a user plane connection release request.

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

[0378] Step S2402: The terminal device sends a first message to the second network element.

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

[0380] Step S2403: The second network element sends a fourth message to the first network element.

[0381] The optional implementation of step S2403 can refer to the optional implementation of step S2103 in FIG2A and other related parts in the embodiment involved in FIG2A , which will not be described in detail here.

[0382] Step S2404: The first network element determines whether to accept the user plane connection release request.

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

[0384] Step S2405: The first network element sends a fifth message to the second network element.

[0385] The optional implementation of step S2405 can refer to the optional implementation of step S2106 in FIG2A and other related parts in the embodiment involved in FIG2A , which will not be described in detail here.

[0386] In some embodiments, the fifth message may be a rejection message.

[0387] Step S2406: The second network element sends a second message to the terminal device.

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

[0389] Step S2407: The terminal device maintains the user plane connection.

[0390] In some embodiments, the above steps are all optional steps.

[0391] In some embodiments, the embodiment shown in FIG. 2D may also be combined with any one or more steps in the embodiment shown in FIG. 2A to form a new embodiment.

[0392] FIG2E is an interactive diagram illustrating a connection release method according to an embodiment of the present disclosure. As shown in FIG2E , an embodiment of the present disclosure relates to a connection release method, which can be executed by a communication system and can include:

[0393] Step S2501: The terminal device sends a first message to the second network element.

[0394] The optional implementation of step S2501 can refer to the optional implementation of step S2102 in FIG. 2A and other related parts in the embodiment involved in FIG. 2A , which will not be described in detail here.

[0395] Step S2502: The second network element sends a fourth message to the first network element.

[0396] The optional implementation of step S2502 can refer to the optional implementation of step S2103 in FIG2A and other related parts in the embodiment involved in FIG2A , which will not be described in detail here.

[0397] Step S2503: The first network element determines whether to accept the user plane connection release request.

[0398] The optional implementation of step S2503 can refer to the optional implementation of step S2104 in FIG. 2A and other related parts in the embodiment involved in FIG. 2A , which will not be described in detail here.

[0399] In some embodiments, the above steps are all optional steps.

[0400] In some embodiments, the embodiment shown in FIG. 2E may also be combined with any one or more steps in the embodiment shown in FIG. 2A to form a new embodiment.

[0401] FIG3A is a flow chart of a connection release method according to an embodiment of the present disclosure. As shown in FIG3A , the embodiment of the present disclosure relates to a connection release method, which can be executed by a terminal device. The method may include:

[0402] Step S3101: Determine to initiate a user plane connection release request.

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

[0404] Step S3102: Send the first message.

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

[0406] In some embodiments, the terminal device may send the first message to the second network element, but is not limited thereto. The terminal device may also send the first message to other entities.

[0407] Step S3103: Get the second message.

[0408] The optional implementation of step S3103 can refer to the optional implementation of step S2107 in FIG2A and other related parts in the embodiment involved in FIG2A , which will not be described in detail here.

[0409] In some embodiments, the terminal device may receive the second message sent by the second network element, but is not limited thereto. The terminal device may also receive the second message sent by other entities.

[0410] In some embodiments, the terminal device may obtain a second message specified by the protocol.

[0411] In some embodiments, the terminal device may obtain the second message from upper layer(s).

[0412] In some embodiments, the terminal device may perform processing to obtain the second message.

[0413] Step S3104: Release the user plane connection.

[0414] The optional implementation of step S3104 can refer to the optional implementation of step S2108 in FIG2A and other related parts in the embodiment involved in FIG2A , which will not be described in detail here.

[0415] Step S3105: Send the third message.

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

[0417] In some embodiments, the terminal device may send the third message to the second network element, but is not limited thereto. The terminal device may also send the third message to other entities.

[0418] Step S3106: Release the PDU session.

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

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

[0421] In some embodiments, the above steps S3101 to S3106 can be executed in a swapped order or simultaneously.

[0422] In some embodiments, the above steps S3101 to S3106 are all optional steps.

[0423] FIG3B is a flow chart of a connection release method according to an embodiment of the present disclosure. As shown in FIG3B , the embodiment of the present disclosure relates to a connection release method, which can be executed by a terminal device. The method may include:

[0424] Step S3201: Determine to initiate a user plane connection release request.

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

[0426] Step S3202: Send the first message.

[0427] The optional implementation of step S3202 can be found in step S2102 of FIG. 2A , the optional implementation of step S3102 of FIG. 3A , and other related parts in the embodiments involved in FIG. 2A and FIG. 3A , which will not be described in detail here.

[0428] Step S3203: Get the second message.

[0429] The optional implementation of step S3203 can be found in step S2107 of FIG. 2A , the optional implementation of step S3103 of FIG. 3A , and other related parts in the embodiments involved in FIG. 2A and FIG. 3A , which will not be described in detail here.

[0430] Step S3204: Release the PDU session.

[0431] The optional implementation of step S3204 can be found in step S2111 of FIG. 2A , the optional implementation of step S3106 of FIG. 3A , and other related parts in the embodiments involved in FIG. 2A and FIG. 3A , which will not be described in detail here.

[0432] In some embodiments, the above steps are all optional steps.

[0433] In some embodiments, the embodiment shown in FIG. 3B may also be combined with any one or more steps in the embodiment shown in FIG. 3A to form a new embodiment.

[0434] FIG3C is a flow chart of a connection release method according to an embodiment of the present disclosure. As shown in FIG3C , the embodiment of the present disclosure relates to a connection release method, which can be executed by a terminal device. The method may include:

[0435] Step S3301: Determine to initiate a user plane connection release request.

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

[0437] Step S3302: Send the first message.

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

[0439] Step S3303: Get the second message.

[0440] The optional implementation of step S3303 can be found in step S2107 of FIG. 2A , the optional implementation of step S3103 of FIG. 3A , and other related parts in the embodiments involved in FIG. 2A and FIG. 3A , which will not be described in detail here.

[0441] Step S3304: Release the user plane connection.

[0442] The optional implementation of step S3304 can be found in step S2108 of FIG. 2A , the optional implementation of step S3104 of FIG. 3A , and other related parts in the embodiments involved in FIG. 2A and FIG. 3A , which will not be described in detail here.

[0443] Step S3305: Release the PDU session.

[0444] The optional implementation of step S3305 can be found in step S2111 of FIG. 2A , the optional implementation of step S3106 of FIG. 3A , and other related parts in the embodiments involved in FIG. 2A and FIG. 3A , which will not be described in detail here.

[0445] In some embodiments, the above steps are all optional steps.

[0446] In some embodiments, the embodiment shown in FIG. 3C may also be combined with any one or more steps in the embodiment shown in FIG. 3A to form a new embodiment.

[0447] FIG3D is a flow chart of a connection release method according to an embodiment of the present disclosure. As shown in FIG3D , the embodiment of the present disclosure relates to a connection release method, which can be executed by a terminal device. The method may include:

[0448] Step S3401: Send the first message.

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

[0450] In some embodiments, the embodiment shown in FIG. 3D may also be combined with any one or more steps in the embodiment shown in FIG. 3A to form a new embodiment.

[0451] In some embodiments, the first message is used to trigger the release of a user plane connection, where the user plane connection is a connection between a terminal device and a first network element, and the first network element is a network element having a positioning management function or a perception function.

[0452] In some embodiments, the first message includes at least one of the following:

[0453] First message identifier;

[0454] User plane connection release reason;

[0455] User plane connection identifier;

[0456] Terminal device identification;

[0457] First network element identifier.

[0458] In some embodiments, the method further comprises:

[0459] Receive a second message sent by the second network element, where the second message is any one of the following:

[0460] a first release message, where the first release message is used to indicate that the user plane connection has been released by the first network element;

[0461] a second release message, where the second release message is used to instruct the terminal device to release the user plane connection;

[0462] A rejection message, where the rejection message is used to reject the terminal device from releasing the user plane connection.

[0463] In some embodiments, the second message includes at least one of the following:

[0464] User plane connection identifier;

[0465] Terminal device identification;

[0466] First network element identifier.

[0467] In some embodiments, the method further comprises:

[0468] Determining that the second message is the second release indication information;

[0469] The user plane connection is released.

[0470] In some embodiments, the method further comprises:

[0471] A third message is sent to the second network element, where the third message is used to indicate that the user plane connection has been released by the terminal device.

[0472] In some embodiments, the method further comprises:

[0473] Determining that there is no other user plane connection between the terminal device and the first network element;

[0474] Release the packet data unit PDU session where the user plane connection is located, and the PDU session is used to carry the user plane connection between the terminal device and the first network element.

[0475] In some embodiments, the method further comprises:

[0476] Ensure that the first condition is met;

[0477] resending the first message;

[0478] The first condition includes at least one of the following:

[0479] The second message is used to refuse the terminal device from releasing the user plane connection;

[0480] The second message is not received within a specific time after the first message is sent.

[0481] FIG4A is a flow chart of a connection release method according to an embodiment of the present disclosure. As shown in FIG4A , the embodiment of the present disclosure relates to a connection release method, which can be executed by a second network element. The method includes:

[0482] Step S4101: Get the first message.

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

[0484] In some embodiments, the second network element may receive the first message sent by the terminal device, but is not limited thereto. The second network element may also receive the first message sent by other entities.

[0485] In some embodiments, the second network element may obtain a first message specified by a protocol.

[0486] In some embodiments, the second network element may perform processing to obtain the first message.

[0487] Step S4102: Send the fourth message.

[0488] The optional implementation of step S4102 can refer to the optional implementation of step S2103 in FIG2A and other related parts in the embodiment involved in FIG2A , which will not be described in detail here.

[0489] In some embodiments, the second network element may send the fourth message to the first network element, but is not limited thereto. The second network element may also send the fourth message to other entities.

[0490] Step S4103: Get the fifth message.

[0491] The optional implementation of step S4103 can refer to the optional implementation of step S2106 in FIG2A and other related parts in the embodiment involved in FIG2A , which will not be described in detail here.

[0492] In some embodiments, the second network element may receive the fifth message sent by the first network element, but is not limited thereto. The second network element may also receive the fifth message sent by other entities.

[0493] In some embodiments, the second network element may obtain a fifth message specified by the protocol.

[0494] In some embodiments, the second network element may perform processing to obtain the fifth message.

[0495] Step S4104: Send the second message.

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

[0497] In some embodiments, the second network element may send the second message to the terminal device, but is not limited thereto. The second network element may also send the second message to other entities.

[0498] Step S4105: Get the third message.

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

[0500] In some embodiments, the second network element may receive a third message sent by the terminal device, but is not limited thereto. The second network element may also receive a third message sent by other entities.

[0501] In some embodiments, the second network element may obtain a third message specified by the protocol.

[0502] In some embodiments, the second network element may perform processing to obtain a third message.

[0503] Step S4106: Send the sixth message.

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

[0505] In some embodiments, the second network element may send the sixth message to the first network element, but is not limited thereto. The second network element may also send the sixth message to other entities.

[0506] The method involved in the embodiments of the present disclosure may include at least one of the above steps S4101 to S4106. For example, step S4102 can be implemented as an independent embodiment, step S4103 can be implemented as an independent embodiment, steps S4101+S4102 can be implemented as an independent embodiment, steps S4103+S4104 can be implemented as an independent embodiment, steps S4101+S4102+S4103+S4104 can be implemented as an independent embodiment, and steps S4103+S4104+S4105+S4106 can be implemented as independent embodiments, but the present invention is not limited thereto.

[0507] In some embodiments, the above steps S4101 to S4106 can be executed in a swapped order or simultaneously.

[0508] In some embodiments, the above steps S4101 to S4106 are all optional steps.

[0509] FIG4B is a flow chart of a connection release method according to an embodiment of the present disclosure. As shown in FIG4B , the embodiment of the present disclosure relates to a connection release method, which can be performed by a second network element. The method may include:

[0510] Step S4201: Get the first message.

[0511] The optional implementation of step S4201 can be found in step S2102 of FIG. 2A , the optional implementation of step S4101 of FIG. 4A , and other related parts in the embodiments involved in FIG. 2A and FIG. 4A , which will not be described in detail here.

[0512] Step S4202: Send the fourth message.

[0513] The optional implementation of step S4202 can be found in step S2103 of FIG. 2A , the optional implementation of step S4102 of FIG. 4A , and other related parts in the embodiments involved in FIG. 2A and FIG. 4A , which will not be described in detail here.

[0514] Step S4203: Get the fifth message.

[0515] The optional implementation of step S4203 can be found in step S2106 of FIG. 2A , the optional implementation of step S4103 of FIG. 4A , and other related parts in the embodiments involved in FIG. 2A and FIG. 4A , which will not be described in detail here.

[0516] Step S4204: Send the second message.

[0517] The optional implementation of step S4204 can be found in step S2107 of FIG. 2A , the optional implementation of step S4104 of FIG. 4A , and other related parts in the embodiments involved in FIG. 2A and FIG. 4A , which will not be described in detail here.

[0518] In some embodiments, the above steps are all optional steps.

[0519] In some embodiments, the embodiment shown in FIG. 4B may also be combined with any one or more steps in the embodiment shown in FIG. 4A to form a new embodiment.

[0520] FIG4C is a flow chart of a connection release method according to an embodiment of the present disclosure. As shown in FIG4C , the embodiment of the present disclosure relates to a connection release method, which can be performed by a second network element. The method may include:

[0521] Step S4301: Get the first message.

[0522] The optional implementation of step S4301 can be found in step S2102 of FIG. 2A , the optional implementation of step S4101 of FIG. 4A , and other related parts in the embodiments involved in FIG. 2A and FIG. 4A , which will not be repeated here.

[0523] In some embodiments, the first message is used to trigger the release of a user plane connection, where the user plane connection is a connection between a terminal device and a first network element, and the first network element is a network element having a positioning management function or a perception function.

[0524] Step S4302: Send the fourth message.

[0525] The optional implementation of step S4302 can be found in step S2103 of FIG. 2A , the optional implementation of step S4102 of FIG. 4A , and other related parts in the embodiments involved in FIG. 2A and FIG. 4A , which will not be described in detail here.

[0526] In some embodiments, the fourth message is used to request the first network element to release the user plane connection.

[0527] In some embodiments, the above steps are all optional steps.

[0528] In some embodiments, the embodiment shown in FIG. 4C may also be combined with any one or more steps in the embodiment shown in FIG. 4A to form a new embodiment.

[0529] In some embodiments, the first message includes at least one of the following:

[0530] First message identifier;

[0531] User plane connection release reason;

[0532] User plane connection identifier;

[0533] Terminal device identification;

[0534] First network element identifier.

[0535] In some embodiments, the first message includes a first network element identifier; and sending the fourth message includes:

[0536] Send the fourth message to the first network element corresponding to the first network element identifier.

[0537] In some embodiments, the method further comprises:

[0538] Receive a fifth message sent by the first network element, where the fifth message is any one of the following:

[0539] a first release message, where the first release message is used to indicate that the user plane connection has been released by the first network element;

[0540] a second release message, where the second release message is used to instruct the terminal device to release the user plane connection;

[0541] A rejection message, where the rejection message is used to reject the terminal device from releasing the user plane connection.

[0542] In some embodiments, the fifth message includes at least one of the following:

[0543] User plane connection identifier;

[0544] Terminal device identification;

[0545] First network element identifier.

[0546] In some embodiments, the method further comprises:

[0547] A second message is sent to the terminal device, where the content indicated by the second message is the same as that of the fifth message.

[0548] In some embodiments, the method further comprises:

[0549] receiving a third message sent by the terminal device, where the third message is used to indicate that the user plane connection has been released by the terminal device;

[0550] A sixth message is sent to the first network element, where content indicated by the sixth message is the same as that of the third message.

[0551] FIG5A is a flow chart of a connection release method according to an embodiment of the present disclosure. As shown in FIG5A , the embodiment of the present disclosure relates to a connection release method, which can be executed by a first network element. The method includes:

[0552] Step S5101: Get the fourth message.

[0553] The optional implementation of step S5101 can refer to the optional implementation of step S2103 in FIG2A and other related parts in the embodiment involved in FIG2A , which will not be described in detail here.

[0554] In some embodiments, the first network element may receive the fourth message sent by the second network element, but is not limited thereto. The first network element may also receive the fourth message sent by other entities.

[0555] Step S5102: Determine whether to accept the user plane connection release request.

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

[0557] Step S5103: Release the user plane connection.

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

[0559] Step S5104: Send the fifth message.

[0560] The optional implementation of step S5104 can refer to the optional implementation of step S2106 in FIG2A and other related parts in the embodiment involved in FIG2A , which will not be described in detail here.

[0561] In some embodiments, the first network element may send the fifth message to the second network element, but is not limited thereto. The first network element may also send the fifth message to other entities.

[0562] Step S5105: Get the sixth message.

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

[0564] In some embodiments, the first network element may receive the sixth message sent by the second network element, but is not limited thereto. The first network element may also receive the sixth message sent by other entities.

[0565] The method according to the embodiments of the present disclosure may include at least one of the above steps S5101 to S5105. For example, step S5103 may be implemented as an independent embodiment, step S5105 may be implemented as an independent embodiment, steps S5101+S5103 may be implemented as an independent embodiment, steps S5101+S5102 may be implemented as an independent embodiment, steps S5101+S5102+S5103+S5104 may be implemented as an independent embodiment, and steps S5101+S5102+S5104+S5105 may be implemented as an independent embodiment, but the present invention is not limited thereto.

[0566] In some embodiments, the above steps S5101 to S5105 can be executed in a swapped order or simultaneously.

[0567] In some embodiments, the above steps S5101 to S5105 are all optional steps.

[0568] FIG5B is a flow chart of a connection release method according to an embodiment of the present disclosure. As shown in FIG5B , the embodiment of the present disclosure relates to a connection release method, which can be performed by a first network element. The method may include:

[0569] Step S5201: Get the fourth message.

[0570] The optional implementation of step S5201 can be found in step S2103 of FIG. 2A , the optional implementation of step S5101 of FIG. 5A , and other related parts in the embodiments involved in FIG. 2A and FIG. 5A , which will not be repeated here.

[0571] Step S5202: Determine whether to accept the user plane connection release request.

[0572] The optional implementation of step S5202 can be found in step S2104 of FIG. 2A , the optional implementation of step S5102 of FIG. 5A , and other related parts in the embodiments involved in FIG. 2A and FIG. 5A , which will not be described in detail here.

[0573] Step S5203: Release the user plane connection.

[0574] The optional implementation of step S5203 can be found in step S2105 of FIG. 2A , the optional implementation of step S5103 of FIG. 5A , and other related parts in the embodiments involved in FIG. 2A and FIG. 5A , which will not be described in detail here.

[0575] Step S5204: Send the fifth message.

[0576] The optional implementation of step S5204 can be found in step S2106 of FIG. 2A , the optional implementation of step S5104 of FIG. 5A , and other related parts in the embodiments involved in FIG. 2A and FIG. 5A , which will not be described in detail here.

[0577] In some embodiments, the above steps are all optional steps.

[0578] In some embodiments, the embodiment shown in FIG. 5B may also be combined with any one or more steps in the embodiment shown in FIG. 5A to form a new embodiment.

[0579] FIG5C is a flow chart of a connection release method according to an embodiment of the present disclosure. As shown in FIG5C , the embodiment of the present disclosure relates to a connection release method, which can be performed by a first network element. The method may include:

[0580] Step S5301: Get the fourth message.

[0581] The optional implementation of step S5301 can be found in step S2103 of FIG. 2A , the optional implementation of step S5101 of FIG. 5A , and other related parts in the embodiments involved in FIG. 2A and FIG. 5A , which will not be repeated here.

[0582] Step S5302: Determine whether to accept the user plane connection release request.

[0583] The optional implementation of step S5302 can be found in step S2104 of FIG. 2A , the optional implementation of step S5102 of FIG. 5A , and other related parts in the embodiments involved in FIG. 2A and FIG. 5A , which will not be described in detail here.

[0584] Step S5303: Send the fifth message.

[0585] The optional implementation of step S5303 can be found in step S2106 of FIG. 2A , the optional implementation of step S5104 of FIG. 5A , and other related parts in the embodiments involved in FIG. 2A and FIG. 5A , which will not be described in detail here.

[0586] Step S5304: Get the sixth message.

[0587] The optional implementation of step S5304 can be found in step S2110 of FIG. 2A , the optional implementation of step S5105 of FIG. 5A , and other related parts in the embodiments involved in FIG. 2A and FIG. 5A , which will not be repeated here.

[0588] In some embodiments, the above steps are all optional steps.

[0589] In some embodiments, the embodiment shown in FIG. 5C may also be combined with any one or more steps in the embodiment shown in FIG. 5A to form a new embodiment.

[0590] FIG5D is a flow chart of a connection release method according to an embodiment of the present disclosure. As shown in FIG5D , the embodiment of the present disclosure relates to a connection release method, which can be performed by a first network element. The method may include:

[0591] Step S5401: Get the fourth message.

[0592] The optional implementation of step S5401 can be found in step S2103 of FIG. 2A , the optional implementation of step S5101 of FIG. 5A , and other related parts in the embodiments involved in FIG. 2A and FIG. 5A , which will not be repeated here.

[0593] Step S5402: Determine whether to accept the user plane connection release request.

[0594] The optional implementation of step S5402 can be found in step S2104 of FIG. 2A , the optional implementation of step S5102 of FIG. 5A , and other related parts in the embodiments involved in FIG. 2A and FIG. 5A , which will not be repeated here.

[0595] Step S5403: Send the fifth message.

[0596] The optional implementation of step S5403 can be found in step S2106 of FIG. 2A , the optional implementation of step S5104 of FIG. 5A , and other related parts in the embodiments involved in FIG. 2A and FIG. 5A , which will not be described in detail here.

[0597] In some embodiments, the above steps are all optional steps.

[0598] In some embodiments, the embodiment shown in FIG. 5D may also be combined with any one or more steps in the embodiment shown in FIG. 5A to form a new embodiment.

[0599] Figure 5E is a flow chart of a connection release method according to an embodiment of the present disclosure. As shown in Figure 5E, the embodiment of the present disclosure relates to a connection release method, which can be performed by a first network element. The method may include:

[0600] Step S5501: Get the fourth message.

[0601] The optional implementation of step S5501 can be found in step S2103 of FIG. 2A , the optional implementation of step S5101 of FIG. 5A , and other related parts in the embodiments involved in FIG. 2A and FIG. 5A , which will not be repeated here.

[0602] In some embodiments, the fourth message is used to request the first network element to release a user plane connection, where the user plane connection is a connection between the terminal device and the first network element;

[0603] Step S5502: Determine whether to accept the user plane connection release request.

[0604] The optional implementation of step S5502 can be found in step S2104 of FIG. 2A , the optional implementation of step S5102 of FIG. 5A , and other related parts in the embodiments involved in FIG. 2A and FIG. 5A , which will not be repeated here.

[0605] In some embodiments, the above steps are all optional steps.

[0606] In some embodiments, the embodiment shown in FIG. 5E may also be combined with any one or more steps in the embodiment shown in FIG. 5A to form a new embodiment.

[0607] In some embodiments, the fourth message includes at least one of the following:

[0608] First message identifier;

[0609] User plane connection release reason;

[0610] User plane connection identifier;

[0611] Terminal device identification;

[0612] First network element identifier.

[0613] In some embodiments, the method further comprises:

[0614] Send a fifth message, where the fifth message includes any one of the following:

[0615] first release indication information, where the first release indication is used to indicate that the user plane connection has been released by the first network element;

[0616] Second release indication information, where the second release indication is used to instruct the terminal device to release the user plane connection;

[0617] Rejection information, where the rejection information is used to reject the terminal device from releasing the user plane connection.

[0618] In some embodiments, the method further comprises:

[0619] Release the user plane connection between the terminal device and the first network element.

[0620] In some embodiments, the method further comprises:

[0621] Receive a sixth message sent by the second network element, where the sixth message is used to indicate that the user plane connection has been released by the terminal device.

[0622] FIG6 is a flow chart of a connection release method according to an embodiment of the present disclosure. As shown in FIG6, an embodiment of the present disclosure relates to a connection release method, which can be executed by a core network device and can include:

[0623] Step S6101: The second network element obtains the first message.

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

[0625] Step S6102: The second network element sends a fourth message to the first network element.

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

[0627] Step S6103: The first network element determines whether to accept the request of the terminal device to release the user plane connection.

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

[0629] In some embodiments, the above steps are all optional steps.

[0630] In some embodiments, the embodiment shown in FIG. 6 may also be combined with any one or more steps in the embodiment shown in FIG. 2A to form a new embodiment.

[0631] In some embodiments of the present disclosure, a core network device is provided, which may include a first network element and a second network element, the first network element being a network element with a positioning management function, and the second network element being a network element with an access and mobility management function; wherein the first network element may be configured to execute the connection release method executed by the first network element in the aforementioned embodiment of the present disclosure; the second network element may execute the connection release method executed by the second network element in the aforementioned embodiment of the present disclosure.

[0632] In some embodiments of the present disclosure, an access network device is provided, which can be used to transmit data or signaling between a terminal device and a core network device.

[0633] In some embodiments of the present disclosure, a communication system is provided, which may include a terminal device, an access network device and a core network device, the core network device including a first network element and a second network element, the first network element being a network element with a positioning management function, and the second network element being a network element with an access and mobility management function; wherein, the terminal device may be configured to execute the connection release method executed by the terminal device in the aforementioned embodiment of the present disclosure; the access network device may be configured to execute the connection release method executed by the access network device in the aforementioned embodiment of the present disclosure; the first network element may be configured to execute the connection release method executed by the first network element in the aforementioned embodiment of the present disclosure; the second network element may execute the connection release method executed by the second network element in the aforementioned embodiment of the present disclosure.

[0634] The embodiments of the present disclosure further provide an apparatus for implementing any of the above methods. For example, an apparatus is provided, comprising units or modules for implementing each step performed by a terminal device 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 device, a core network function node, a first network element, a second network element, etc.) in any of the above methods.

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

[0636] 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 a 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 to implement the hardware circuit configuration can be understood as the process of the processor loading instructions to implement the functions of some or all of the above units or modules. In addition, it can also be a hardware circuit designed for artificial intelligence, which can be understood as ASIC, such as a neural network processing unit (NPU), a tensor processing unit (TPU), a deep learning processing unit (DPU), etc.

[0637] Figure 7A is a structural diagram of a terminal device proposed in an embodiment of the present disclosure. As shown in Figure 7A, the terminal device 101 may include: at least one of a transceiver module 7101, a processing module 7102, etc. In some embodiments, the transceiver module 7101 is configured to send a first message to the second network element, and the first message is used to trigger the release of the user plane connection. The user plane connection is a connection between the terminal device and the first network element. The first network element is a network element with a positioning management function or a perception function, and the second network element is a network element with an access and mobility management function. Optionally, the transceiver module 7101 can be used to execute at least one of the communication steps such as sending and / or receiving performed by the terminal device in any of the above methods (for example, step S2102, step S2103, step S2106, step S2107, step S2109, step S2110, but not limited to this), which will not be repeated here. Optionally, the processing module 7102 can be used to execute at least one of the other steps (such as step S2101, step S2104, step S2105, step S2108, step S2111, but not limited to these) performed by the terminal device in any of the above methods, which will not be repeated here.

[0638] Figure 7B is a schematic diagram of the structure of a first network element proposed in an embodiment of the present disclosure. As shown in Figure 7B, the first network element 1031 may include: at least one of a transceiver module 7201, a processing module 7202, etc. In some embodiments, the transceiver module 7201 is configured to receive a fourth message sent by the second network element, the fourth message being used to request the first network element to release a user plane connection, the user plane connection being a connection between a terminal device and the first network element; the processing module 7202 is configured to determine whether to accept the request of the terminal device to release the user plane connection. Optionally, the transceiver module 7201 can be used to execute at least one of the communication steps such as sending and / or receiving (for example, step S2102, step S2103, step S2106, step S2107, step S2109, step S2110, but not limited thereto) performed by the first network element in any of the above methods, which will not be repeated here. Optionally, the processing module 7202 can be used to execute at least one of the other steps (for example, step S2101, step S2104, step S2105, step S2108, step S2111, but not limited to these) performed by the first network element in any of the above methods, which will not be repeated here.

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

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

[0641] Figure 7C is a schematic diagram of the structure of a second network element proposed in an embodiment of the present disclosure. As shown in Figure 7C, the second network element 1032 may include: at least one of a transceiver module 7301, a processing module 7302, etc. In some embodiments, the transceiver module 7301 is configured to receive a first message sent by a terminal device, the first message being used to trigger the release of a user plane connection, the user plane connection being a connection between a terminal device and a first network element, the first network element being a network element with a positioning management function or a perception function; and send a fourth message to the first network element, the fourth message being used to request the first network element to release the user plane connection. Optionally, the transceiver module 7301 can be used to execute at least one of the communication steps such as sending and / or receiving performed by the second network element in any of the above methods (for example, step S2102, step S2103, step S2106, step S2107, step S2109, step S2110, but not limited thereto), which will not be repeated here. Optionally, the processing module 7302 can be used to execute at least one of the other steps (for example, step S2101, step S2104, step S2105, step S2108, step S2111, but not limited to these) performed by the second network element in any of the above methods, which will not be repeated here.

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

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

[0644] 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 any device in a communication system, for example, a terminal device, an access network device, a core network device, a network device, or a server. It can also be a chip, a chip system, or a processor in the communication system that implements 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.

[0645] 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 can be 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.

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

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

[0648] 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 memories 8103 and may be configured to receive data from the memories 8103 or other devices, or to send data to the memories 8103 or other devices. For example, the interface circuits 8104 may read data stored in the memories 8103 and send the data to the processor 8101.

[0649] The communication device 8100 described in the above embodiments may be a terminal device, an access network device, a core network device, a network device, or a server, 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.

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

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

[0652] In some embodiments, chip 8200 further includes one or more interface circuits 8204. Alternatively, the terms 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 memories 8203 may be located external to chip 8200.

[0653] Optionally, the interface circuit 8204 is connected to the memory 8203. The interface circuit 8204 can be used to receive data from the memory 8203 or other devices, and the interface circuit 8204 can be used to send data to the memory 8203 or other devices. For example, the interface circuit 8204 can read data stored in the memory 8203 and send the data to the processor 8201.

[0654] In some embodiments, the interface circuit 8204 performs at least one of the communication steps of sending and / or receiving in the above method (e.g., step S2102, step S2103, step S2106, step S2107, step S2109, and step S2110, but not limited thereto). The interface circuit 8204 performing the communication steps of sending and / or receiving in the above method, for example, means that the interface circuit 8204 performs data exchange between the processor 8201, chip 8200, memory 8203, or transceiver device. In some embodiments, the processor 8201 may perform at least one of the other steps (e.g., step S2101, step S2104, step S2105, step S2108, and step S2111, but not limited thereto).

[0655] The modules and / or devices described in various embodiments, such as virtual devices, physical devices, and chips, can be arbitrarily combined or separated according to circumstances. Optionally, some or all steps can also be performed collaboratively by multiple modules and / or devices, which is not limited here.

[0656] The embodiments of the present disclosure further provide a storage medium having instructions stored thereon. When the instructions are executed on the communication device 8100, the communication device 8100 executes 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.

[0657] 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 may be a computer program product.

[0658] The embodiments of the present disclosure also provide a computer program, which, when executed on a computer, enables the computer to execute any one of the above methods.

Claims

1. A connection release method, characterized in that, performed by a terminal device, the method comprising: sending a first message to a second network element, the first message being used to trigger the release of a user plane connection, the user plane connection being a connection between the terminal device and a first network element, the first network element being a network element with positioning management function or sensing function, and the second network element being a network element with access and mobility management function.

2. The method according to claim 1, characterized in that, the first message includes at least one of the following: First message identifier; User plane connection release reason; User plane connection identifier; Terminal device identifier; First network element identifier.

3. The method according to claim 1 or 2, characterized in that, the method further comprises: receiving a second message sent by the second network element, the second message being any one of the following: A first release message, the first release message being used to indicate that the user plane connection has been released by the first network element; A second release message, the second release message being used to indicate that the terminal device releases the user plane connection; A rejection message, the rejection message being used to reject the terminal device from releasing the user plane connection.

4. The method according to claim 3, characterized in that, the second message includes at least one of the following: User plane connection identifier; Terminal device identifier; First network element identifier.

5. The method according to claim 3 or 4, characterized in that, the method further comprises: determining that the second message is the second release indication information; releasing the user plane connection.

6. The method according to claim 5, characterized in that, the method further comprises: sending a third message to the second network element, the third message being used to indicate that the user plane connection has been released by the terminal device.

7. The method according to any one of claims 3 to 6, characterized in that, the method further comprises: determining that there is no other user plane connection between the terminal device and the first network element; releasing the packet data unit PDU session where the user plane connection is located, the PDU session being used to carry the user plane connection between the terminal device and the first network element.

8. The method according to any one of claims 3 to 7, characterized in that, the method further comprises: determining that a first condition is met; resending the first message to the second network element; wherein, the first condition includes at least one of the following: The second message is used to reject the terminal device from releasing the user plane connection; The second message is not received within a specific time after sending the first message.

9. A connection release method, characterized in that, performed by a second network element, the second network element being a network element with access and mobility management function, the method comprising: receiving a first message sent by a terminal device, the first message being used to trigger the release of a user plane connection, the user plane connection being a connection between the terminal device and a first network element, the first network element being a network element with positioning management function or sensing function; sending a fourth message to the first network element, the fourth message being used to request the first network element to release the user plane connection.

10. The method according to claim 9, wherein, the first message includes at least one of the following: a first message identifier; a user plane connection release reason; a user plane connection identifier; a terminal device identifier; a first network element identifier.

11. The method according to claim 9 or 10, wherein, the first message includes a first network element identifier; and sending the fourth message to the first network element includes: sending the fourth message to the first network element corresponding to the first network element identifier.

12. The method according to any one of claims 9 to 11, wherein, the method further includes: receiving a fifth message sent by the first network element, where the fifth message is any one of the following: a first release message for indicating that the user plane connection has been released by the first network element; a second release message for indicating that the terminal device releases the user plane connection; a rejection message for rejecting the terminal device from releasing the user plane connection.

13. The method according to claim 12, wherein, the fifth message includes at least one of the following: a user plane connection identifier; a terminal device identifier; a first network element identifier.

14. The method according to claim 12 or 13, wherein, the method further includes: sending a second message to the terminal device, where the content indicated by the second message is the same as that of the fifth message.

15. The method according to any one of claims 12 to 14, wherein, the method further includes: receiving a third message sent by the terminal device, where the third message is used to indicate that the user plane connection has been released by the terminal device; sending a sixth message to the first network element, where the content indicated by the sixth message is the same as that of the third message.

16. A connection release method, wherein, executed by a first network element, the first network element being a network element with a positioning management function or a sensing function, and the method includes: receiving a fourth message sent by a second network element, where the fourth message is used to request the first network element to release a user plane connection, the user plane connection being a connection between a terminal device and the first network element, and the second network element being a network element with an access and mobility management function; determining whether to accept the request of the terminal device to release the user plane connection.

17. The method according to claim 16, wherein, the fourth message includes at least one of the following: a first message identifier; a user plane connection release reason; a user plane connection identifier; a terminal device identifier; a first network element identifier.

18. The method according to claim 16 or 17, wherein, the method further includes: sending a fifth message to the second network element, where the fifth message includes any one of the following: a first release indication for indicating that the user plane connection has been released by the first network element; a second release indication for indicating that the terminal device releases the user plane connection; a rejection indication for rejecting the terminal device from releasing the user plane connection.

19. The method according to claim 16, wherein, the method further includes: releasing the user plane connection between the terminal device and the first network element.

20. The method according to claim 18 or 19, wherein, the method further includes: receiving a sixth message sent by the second network element, where the sixth message is used to indicate that the user plane connection has been released by the terminal device.

21. A connection release method, wherein, executed by a core network device, the core network device includes a first network element and a second network element, the first network element is a network element with positioning management function or sensing function, the second network element is a network element with access and mobility management function, and the method includes: the second network element receives a first message sent by a terminal device, the first message is used to trigger the release of a user plane connection, the user plane connection is a connection between the terminal device and the first network element, and the first network element is a network element with positioning management function or sensing function; the second network element sends a fourth message to the first network element, and the fourth message is used to request the first network element to release the user plane connection; the first network element determines whether to accept the request of the terminal device to release the user plane connection.

22. A terminal device, wherein, including: a transceiver module configured to send a first message to a second network element, the first message is used to trigger the release of a user plane connection, the user plane connection is a connection between the terminal device and the first network element, the first network element is a network element with positioning management function or sensing function, and the second network element is a network element with access and mobility management function.

23. A second network element, wherein, including: a transceiver module configured to receive a first message sent by a terminal device, the first message is used to trigger the release of a user plane connection, the user plane connection is a connection between the terminal device and the first network element, the first network element is a network element with positioning management function or sensing function; and send a fourth message to the first network element, the fourth message is used to request the first network element to release the user plane connection.

24. A first network element, wherein, including: a transceiver module configured to receive a fourth message sent by a second network element, the fourth message is used to request the first network element to release a user plane connection, the user plane connection is a connection between the terminal device and the first network element; a processing module configured to determine whether to accept the request of the terminal device to release the user plane connection.

25. A core network device, wherein, the core network device includes a first network element and a second network element, wherein the first network element is configured to implement the connection release method according to any one of claims 9 to 15, and the second network element is configured to implement the connection release method according to any one of claims 16 to 20.

26. A communication system, wherein, The communication system includes a terminal device and a core network device. The core network device includes a first network element and a second network element. The first network element is a network element with positioning management function, and the second network element is a network element with authentication management function. Among them, the terminal device is configured to implement the connection release method described in any one of claims 1 to 8, the first network element is configured to implement the connection release method described in any one of claims 9 to 15, and the second network element is configured to implement the connection release method described in any one of claims 16 to 20.

27. A communication device, characterized in that, it includes: one or more processors; wherein, the communication device is used to execute the connection release method described in any one of claims 1 to 8, claims 9 to 15 or claims 16 to 20.

28. A storage medium storing instructions, characterized in that, when the instructions run on a communication device, the communication device is caused to execute the connection release method described in any one of claims 1 to 8, claims 9 to 15 or claims 16 to 20.

Images