Communication method, device, and system, and storage medium

Abstract

Embodiments of the present disclosure relate to the technical field of communications. Disclosed are a communication method and apparatus, and a computer-readable storage medium. The communication method comprises: upon determining that the state of a user plane of a terminal is unavailable, starting a timer; and before the timer expires or stops, not triggering a user plane connection establishment process with the terminal. In the embodiments of the present disclosure, the timer is started upon determining that the state of the user plane of the terminal is unavailable, and the user plane connection establishment process with the terminal is not triggered before the timer expires or stops, thereby reducing signaling transmission and improving the performance of a communication system.

Description

Communication methods, devices, systems and storage media Technical Field

[0001] This disclosure relates to the field of communication technology, and more specifically, to a communication method, device, system, and storage medium. Background Technology

[0002] In the field of communication technology, user plane connections can be established between terminals and core network equipment (such as Location Management Function (LMF) elements) through access network equipment to enable related services (such as user plane positioning) to be performed through these user plane connections. Either the terminal or the core network equipment may initiate the establishment of the user plane connection. Both the terminal and the core network equipment can maintain established user plane connections. The core network equipment can modify or terminate established user plane connections with the terminal.

[0003] Summary of the Invention

[0004] This disclosure provides a communication method, device, system, and storage medium.

[0005] A first aspect of this disclosure provides a communication method, the method being executed by a first network element, the method comprising:

[0006] When the user plane status of the terminal is determined to be unavailable, start the timer;

[0007] The user plane connection establishment process with the terminal will not be triggered until the timer expires or stops.

[0008] A second aspect of this disclosure provides a communication method, the method being executed by a terminal, the method comprising:

[0009] A message is sent to the first network element, the message being used to notify the first network element whether the user plane of the terminal is available.

[0010] A third aspect of this disclosure provides a first network element, including:

[0011] The first processing module is used to start a timer when it determines that the user plane status of the terminal is unavailable; the user plane connection establishment process with the terminal is not triggered before the timer expires or stops.

[0012] A fourth aspect of this disclosure provides a terminal, including:

[0013] The second transceiver module is used to send a message to the first network element, the message being used to notify the first network element whether the user plane status of the terminal is available.

[0014] A fifth aspect of this disclosure provides a communication device, including:

[0015] One or more processors;

[0016] The terminal is used to execute the optional implementation of the first aspect described above.

[0017] A sixth aspect of this disclosure provides a communication device, including:

[0018] One or more processors;

[0019] The network device is used to perform an optional implementation of the second aspect described above.

[0020] A seventh aspect of this disclosure provides a communication system including a first network element and a terminal, wherein the terminal is used to implement the method described in the optional implementation of the second aspect, and the first network element is used to implement the method described in the optional implementation of the first aspect.

[0021] According to an eighth aspect of the present disclosure, a computer-readable storage medium is provided that stores executable instructions which are loaded and executed by the processor to implement the method described in the optional embodiments of the first or second aspect.

[0022] It should be understood that the above general description and the following detailed description are exemplary and explanatory only, and are not intended to limit this disclosure. Attached Figure Description

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

[0024] Figure 1a is a schematic diagram of a wireless communication system according to an exemplary embodiment;

[0025] Figure 1b is a flowchart illustrating a communication method according to an exemplary embodiment;

[0026] Figure 2a is a flowchart illustrating a communication method according to an exemplary embodiment;

[0027] Figure 2b is a flowchart illustrating a communication method according to an exemplary embodiment;

[0028] Figure 2c is a flowchart illustrating a communication method according to an exemplary embodiment;

[0029] Figure 2d is a flowchart illustrating a communication method according to an exemplary embodiment;

[0030] Figure 2e is a flowchart illustrating a communication method according to an exemplary embodiment;

[0031] Figure 3a is a flowchart illustrating the communication method according to an embodiment of this disclosure;

[0032] Figure 3b is a flowchart illustrating the communication method according to an embodiment of this disclosure;

[0033] Figure 3c is a flowchart illustrating the communication method according to an embodiment of this disclosure;

[0034] Figure 4a is a flowchart illustrating the communication method according to an embodiment of this disclosure;

[0035] Figure 4b is a flowchart illustrating the communication method according to an embodiment of this disclosure;

[0036] Figure 4c is a flowchart illustrating the communication method according to an embodiment of this disclosure;

[0037] Figure 5 is a flowchart illustrating the communication method according to an embodiment of this disclosure;

[0038] Figure 6a is a schematic diagram of the structure of the first network element proposed in an embodiment of this disclosure;

[0039] Figure 6b is a schematic diagram of the structure of the terminal proposed in an embodiment of this disclosure;

[0040] Figure 7a is a schematic diagram of the structure of the communication device proposed in an embodiment of this disclosure;

[0041] Figure 7b is a schematic diagram of the chip structure proposed in an embodiment of this disclosure. Detailed Implementation

[0042] This disclosure provides communication methods, devices, communication systems, and storage media.

[0043] In a first aspect, embodiments of this disclosure propose a communication method, which is executed by a first network element, the method comprising:

[0044] When the user plane status of the terminal is determined to be unavailable, start the timer;

[0045] The user plane connection establishment process with the terminal will not be triggered until the timer expires or stops.

[0046] In the above embodiments, by starting a timer when the user plane status of the terminal is determined to be unavailable, and not triggering the user plane connection establishment process with the terminal before the timer expires or stops, signaling transmission can be saved and the performance of the communication system can be improved.

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

[0048] During the operation of the timer, a control plane-related method is determined for the first service of the terminal.

[0049] In the above embodiments, since the user plane of the terminal is unavailable during the timer operation, the control plane related party method can be used to process the relevant services of the terminal to ensure the normal operation of the terminal services.

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

[0051] If the user plane of the terminal is determined to be available, the timer is stopped; otherwise, the timer runs until it expires.

[0052] In the above embodiments, if it is determined that the user plane of the terminal has been restored to availability during the timer operation, the timer is stopped. Therefore, user plane related methods can be used to process the relevant services of the terminal.

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

[0054] Receive a first message, the first message being used to notify the terminal that the user plane is available;

[0055] Based on the first message, the user plane status of the terminal is determined to be available.

[0056] In the above embodiments, the availability of the user plane can be determined by receiving a first message that notifies the terminal that the user plane status is available, thereby accurately obtaining the user plane status information of the terminal.

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

[0058] A second message is sent to the terminal, the second message being used to determine whether the user plane of the terminal is available.

[0059] In the above embodiments, a second message can be sent to the terminal to determine whether the user plane status of the terminal is available, so as to determine the user plane status information of the terminal based on the actual needs of the first network element.

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

[0061] If the first message is not received and the timer expires at the predetermined time, the second message is resent to the terminal, and the timer is restarted.

[0062] In the above embodiments, the first network element can repeatedly send the second message to determine the user plane status information of the terminal.

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

[0064] If the number of timer restarts exceeds a preset value, the user plane status of the terminal is determined to be unavailable, and user plane-related methods are not applied to the first service of the terminal.

[0065] In the above embodiments, the timer is restarted each time the second message is resent, so that if the number of timer restarts exceeds a preset value, it is determined that the user plane of the terminal is always unavailable, and other methods can be used to process the terminal's services to ensure the normal operation of the terminal's services.

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

[0067] Perceive business;

[0068] Location services;

[0069] Ranging / sidechain positioning services.

[0070] In conjunction with some embodiments of the first aspect, in some embodiments, the control plane-related methods include at least one of the following:

[0071] Control surface perception method;

[0072] Control surface positioning method;

[0073] Control surface ranging / side chain positioning method.

[0074] In conjunction with some embodiments of the first aspect, in some embodiments, the user plane related method includes at least one of the following:

[0075] User-face perception methods;

[0076] User plane positioning method;

[0077] User face ranging / side chain positioning method.

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

[0079] Receive a third message from the terminal, the third message being used to notify the terminal that the user plane is unavailable;

[0080] Based on the third message, it is determined that the user plane of the terminal is unavailable.

[0081] In the above embodiments, the user plane of the terminal is determined to be unavailable by using a third message from the terminal to notify the terminal that the user plane is unavailable, thereby accurately knowing the user plane status of the terminal.

[0082] In conjunction with some embodiments of the first aspect, in some embodiments, the third message includes a first value of a timer, and the method further includes:

[0083] Set the value of the timer to the first value included in the third message.

[0084] In the above embodiments, by carrying the value of a timer in the third message used to notify the terminal that the user plane status is unavailable, the first network element can set the value of the timer to be started to the value indicated by the terminal, thereby attempting to obtain the user plane status of the terminal based on the actual user plane status of the terminal, thereby saving signaling transmission and improving the performance of the communication system.

[0085] In conjunction with some embodiments of the first aspect, in some embodiments, the value of the timer is a predetermined duration.

[0086] Secondly, embodiments of this disclosure provide a communication method, which is executed by a terminal, and the method includes:

[0087] A message is sent to the first network element, the message being used to notify the first network element whether the user plane of the terminal is available.

[0088] In conjunction with some embodiments of the second aspect, in some embodiments, the message includes: a third message, the third message being used to notify the first network element that the user plane of the terminal is unavailable.

[0089] In conjunction with some embodiments of the second aspect, in some embodiments, the third message includes a first value of a timer, the timer being started by the first network element when the user plane state of the terminal is unavailable, and the value of the timer being set by the first network element to the first value included in the third message.

[0090] In conjunction with some embodiments of the second aspect, in some embodiments, the message includes: a first message, the first message being used to notify the first network element that the user plane of the terminal is available.

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

[0092] The system receives at least one second message sent by the first network element, wherein the second message is used to determine whether the user plane status of the terminal is available.

[0093] In conjunction with some embodiments of the second aspect, in some embodiments, if the first network element does not receive the first message and the timer reaches its predetermined expiration time, the second message is retransmitted.

[0094] In conjunction with some embodiments of the second aspect, in some embodiments, sending a message to the first network element includes:

[0095] In response to the second message, the message is sent to the first network element.

[0096] Thirdly, embodiments of this disclosure propose a first network element, including:

[0097] The first processing module is used to start a timer when it determines that the user plane status of the terminal is unavailable; the user plane connection establishment process with the terminal is not triggered before the timer expires or stops.

[0098] Fourthly, embodiments of this disclosure provide a terminal, including:

[0099] The second transceiver module is used to send a message to the first network element, the message being used to notify the first network element whether the user plane status of the terminal is available.

[0100] Fifthly, embodiments of this disclosure provide a communication device, comprising:

[0101] One or more processors;

[0102] The terminal executes the method described in the optional implementation of the first aspect.

[0103] According to a sixth aspect of the present disclosure, a communication device is provided, comprising:

[0104] One or more processors;

[0105] The network device performs the method described in the optional implementation of the second aspect.

[0106] In a seventh aspect, embodiments of this disclosure provide a communication system including a first network element and a terminal, wherein the terminal is used to implement the method described in the optional implementation of the second aspect, and the first network element is used to implement the method described in the optional implementation of the first aspect.

[0107] Eighthly, embodiments of this disclosure provide a storage medium storing instructions that, when executed on a communication device, cause the communication device to perform the method as described in the optional embodiments of the first or second aspect.

[0108] Ninthly, embodiments of this disclosure provide a program product that, when executed by a communication device, causes the communication device to perform the method as described in the optional implementation of the first or second aspect.

[0109] In a tenth aspect, embodiments of this disclosure provide a computer program that, when run on a computer, causes the computer to perform the methods described in an optional implementation of the first or second aspect.

[0110] Eleventhly, embodiments of this disclosure provide a chip or chip system including processing circuitry for performing the method described in an optional implementation of the first or second aspect above.

[0111] Understandably, the aforementioned devices, communication equipment, communication systems, storage media, program products, and computer programs for random access are all used to execute the methods proposed in the embodiments of this disclosure. Therefore, the beneficial effects they can achieve can be referred to the beneficial effects in the corresponding methods, and will not be repeated here. The communication equipment can be a terminal or a network device.

[0112] This disclosure provides communication methods, apparatus, devices, systems, and storage media.

[0113] In some embodiments, the terms "communication method" and "for random access" can be used interchangeably, the terms "apparatus for random access" and "information processing apparatus" and "communication apparatus" can be used interchangeably, and the terms "information processing system" and "communication system" can be used interchangeably.

[0114] This disclosure is not exhaustive, but merely illustrative of some embodiments, and is not intended to limit the scope of protection of the embodiments disclosed. Unless otherwise specified, each step in a particular 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 particular embodiment can also be implemented as an independent embodiment, and the order of the steps in a particular embodiment can be arbitrarily interchanged. Furthermore, the optional implementation methods in a particular embodiment can be arbitrarily combined; moreover, the embodiments can be arbitrarily combined, for example, some or all steps of different embodiments can be arbitrarily combined, and a particular embodiment can be arbitrarily combined with the optional implementation methods of other embodiments.

[0115] In each of the disclosed embodiments, unless otherwise specified or in case of logical conflict, the terminology and / or descriptions of the embodiments are consistent and can be referenced by each other. Technical features in different embodiments can be combined to form new embodiments based on their inherent logical relationships.

[0116] The terminology used in the embodiments of this disclosure is for the purpose of describing particular embodiments only and is not intended to limit the embodiments of this disclosure.

[0117] In this embodiment of the disclosure, unless otherwise stated, elements expressed in the singular form, such as "a," "an," "the," "the," "the," "the," "the," "the," "this," etc., can mean "one and only one," or "one or more," "at least one," etc. For example, when using articles such as "a," "an," "the," etc. in translation, the noun following the article can be understood as either a singular expression or a plural expression.

[0118] In the embodiments disclosed herein, "multiple" refers to two or more.

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

[0120] The descriptions in this disclosure, such as "at least one of A, B, C..." or "A and / or B and / or C...", include the case where any one of A, B, C... exists alone, as well as the case where any combination of any of A, B, C... exists alone. Each case can exist alone. For example, "at least one of A, B, C" includes the cases of A alone, B alone, C alone, A and B combination, A and C combination, B and C combination, and A and B and C combination. For example, A and / or B includes the cases of A alone, B alone, and A and B combination.

[0121] In some embodiments, the notation "in one case A, in another case B" or "in response to one case A, in response to another case B" may include the following technical solutions depending on the situation: A is executed regardless of B, i.e., A is executed in some embodiments; B is executed regardless of A, i.e., B is executed in some embodiments; A and B are selectively executed, i.e., A and B are selected for execution in some embodiments; A and B are both executed, i.e., A and B are executed in some embodiments. The same applies when there are more branches such as A, B, and C.

[0122] The prefixes "first," "second," etc., used in the embodiments of this disclosure are merely for distinguishing different descriptive objects and do not impose restrictions on the position, order, priority, quantity, or content of the descriptive objects. The description of the descriptive objects is found in the claims or the context of the embodiments, and the use of prefixes should not constitute unnecessary restrictions. For example, if the descriptive object is a "field," the ordinal numbers preceding "field" in "first field" and "second field" do not restrict the position or order of the "fields." "First" and "second" do not restrict whether the "fields" they modify are in the same message, nor do they restrict the order of "first field" and "second field." Similarly, if the descriptive object is a "level," the ordinal numbers preceding "level" in "first level" and "second level" do not restrict the priority between "levels." Furthermore, the number of descriptive objects is not limited by ordinal numbers and can be one or more. For example, in "first device," the number of "devices" can be one or more. Furthermore, the objects modified by different prefixes can be the same or different. For example, if the object being described is "device", then "first device" and "second device" can be the same device or different devices, and their types can be the same or different. As another example, if the object being described is "information", then "first configuration" and "second configuration" can be the same information or different information, and their content can be the same or different.

[0123] In some embodiments, “including A,” “containing A,” “for indicating A,” and “carrying A” can be interpreted as directly carrying A or indirectly indicating A.

[0124] In some embodiments, the terms “in response to…”, “in response to determining…”, “in the case of…”, “when…”, “if…”, “if…”, etc., can be used interchangeably.

[0125] In some embodiments, the terms “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 lower than,” and “above” can be used interchangeably, as can the terms “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”.

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

[0127] In some embodiments, the terms "access network device (AN device)," "radio access network device (RAN device)," "base station (BS)," "radio base station," "fixed station," "node," "access point," "transmission point (TP)," "reception point (RP)," "transmission / reception point (TRP)," "panel," "antenna panel," "antenna array," "cell," "macro cell," "small cell," "femto cell," "pico cell," "sector," "cell group," "carrier," "component carrier," and "bandwidth part (BWP)" can be used interchangeably.

[0128] In some embodiments, the terms "terminal", "terminal device", "user equipment (UE)", "user terminal", "mobile station (MS)", "mobile terminal (MT)", "subscriber station", "mobile unit", "subscriber unit", "wireless unit", "remote unit", "mobile device", "wireless device", "wireless communication device", "remote device", "mobile subscriber station", "access terminal", "mobile terminal", "wireless terminal", "remote terminal", "handset", "user agent", "mobile client", and "client" can be used interchangeably.

[0129] In some embodiments, the access network device, core network device, or network device can be replaced by a terminal. For example, various embodiments of this disclosure can also be applied to structures that replace communication between the access network device, core network device, or network device and the terminal with communication between multiple terminals (e.g., also referred to as device-to-device (D2D), vehicle-to-everything (V2X), etc.). In this case, the terminal can also be configured to have all or part of the functions of the access network device. Furthermore, terms such as "uplink" and "downlink" can be replaced with terms corresponding to communication between terminals (e.g., "side").

[0130] For example, uplink channels and downlink channels can be replaced with side channels, and uplink links and downlink links can be replaced with side links.

[0131] In some embodiments, the terms "uplink", "uplink", and "physical uplink" can be used interchangeably, as can the terms "downlink", "downlink", and "physical downlink", as well as the terms "sidelink", "sidelink", "sidelink communication", "sidelink communication", "direct connection", "direct link", "direct communication", and "direct link communication".

[0132] In some embodiments, the terms “downlink control information (DCI),” “downlink (DL) assignment,” “DL DCI,” “uplink (UL) grant,” and “UL DCI” can be used interchangeably.

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

[0134] In some embodiments, the determination or judgment can be made by a value represented by 1 bit (0 or 1), or by a true or false value (boolean), or by a comparison of numerical values ​​(e.g., a comparison with a predetermined value), but is not limited thereto.

[0135] In some embodiments, "network" can be interpreted as devices included in a network (e.g., access network devices, core network devices, etc.).

[0136] In some embodiments, the acquisition of data, information, etc., may comply with the laws and regulations of the country where the location is situated.

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

[0138] Figure 1a is a schematic diagram of the architecture of a communication system according to an embodiment of the present disclosure.

[0139] As shown in Figure 1a, the communication system 100 includes a terminal 101 and a network device 102.

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

[0141] In some embodiments, network device 102 may include at least one of access network device and core network device.

[0142] In some embodiments, the access network device is, for example, a node or device that connects a terminal to a wireless network. The network device may include, but is not limited to, at least one of the following in a 5G communication system: evolved Node B (eNB), next-generation eNB (ng-eNB), next-generation Node B (gNB), node B (NB), home node B (HNB), home evolved node B (HeNB), wireless backhaul device, radio network controller (RNC), base station controller (BSC), base transceiver station (BTS), base band unit (BBU), mobile switching center, base station in a 6G communication system, open RAN, cloud RAN, base station in other communication systems, and access node in a wireless fidelity (WiFi) system.

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

[0144] In some embodiments, the access network device may be composed of a central unit (CU) and a distributed unit (DU). The CU may also be called a control unit. The CU-DU structure can separate the protocol layer of the network device. Some of the protocol layer functions are centrally controlled by the CU, while the remaining part or all of the protocol layer functions are distributed in the DU and centrally controlled by the CU. However, this is not the only possibility.

[0145] In some embodiments, the access network device may be a single device, multiple devices, or a group of devices, including all or part of a first network element, a second network element, etc. Network elements may be virtual or physical. Network devices may include, for example, at least one of an Evolved Packet Core (EPC), a 5G Core Network (5GCN), and a Next Generation Core (NGC).

[0146] In some embodiments, a core network device may be a single device comprising one or more network elements, or it may be multiple devices or a group of devices, each comprising all or part of the aforementioned one or more network elements. Network elements may be virtual or physical. The core network may include, for example, at least one of an Evolved Packet Core (EPC), a 5G Core Network (5GCN), or a Next Generation Core (NGC).

[0147] It is understood that the communication system described in this disclosure is for the purpose of more clearly illustrating the technical solutions of this disclosure, and does not constitute a limitation on the technical solutions proposed in this disclosure. As those skilled in the art will know, with the evolution of system architecture and the emergence of new business scenarios, the technical solutions proposed in this disclosure are also applicable to similar technical problems.

[0148] The following embodiments of this disclosure can be applied to the communication system 100 shown in FIG1a, or to some of the main bodies, but are not limited thereto. The main bodies shown in FIG1a are illustrative. The communication system may include all or some of the main bodies in FIG1a, or it may include other main bodies outside of FIG1a. The number and form of each main body are arbitrary. The connection relationship between the main bodies is illustrative. The main bodies may not be connected or may be connected. The connection can be in any way, it can be a direct connection or an indirect connection, it can be a wired connection or a wireless connection.

[0149] The embodiments disclosed herein can be applied to Long Term Evolution (LTE), LTE-Advanced (LTE-A), LTE-Beyond (LTE-B), SUPER 3G, IMT-Advanced, 4th generation mobile communication system (4G), 5th generation mobile communication system (5G), 5G new radio (NR), Future Radio Access (FRA), New-Radio Access Technology (RAT), New Radio (NR), New radio access (NX), Future generation radio access (FX), Global System for Mobile communications (GSM), CDMA2000, Ultra Mobile Broadband (UMB), IEEE 802.11 (Wi-Fi), IEEE 802.16 (WiMAX), and IEEE 802.20, Ultra-Wideband (UWB), Bluetooth (a 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 systems for random access, and next-generation systems built upon them, etc. Furthermore, multiple systems can be combined (e.g., a combination of LTE or LTE-A with 5G).

[0150] In some embodiments, a core network device may be a single device comprising one or more network elements, or it may be multiple devices or a group of devices, each comprising all or part of the aforementioned one or more network elements. Network elements may be virtual or physical. The core network may include, for example, at least one of the following: Evolved Packet Core (EPC), 5G Core Network (5GCN), 6G Core Network (6GCN), and Next Generation Core (NGC).

[0151] To facilitate understanding, the terminology used in this disclosure will be introduced first.

[0152] 1. The Access and Mobility Management Function (AMF) network element is a logical node functional network element on the core network side. It serves as the core network control plane access point for terminals, receiving all connection and session-related information from user equipment and performing registration, connection, reachability, and mobility management. Furthermore, the AMF network element provides a session management message transmission channel for terminal equipment and Session Management Function (SMF) equipment, providing authentication and authorization functions for user access.

[0153] 2. The Location Management Function (LMF) network element is located on the local side of the Radio Access Network (RAN) or the Core Network (CN) and is used to provide location management function services to the terminal.

[0154] 3. User Plane Function (UPF) network elements, including routing and forwarding of user data packets, data interaction with external data networks, quality of service (QoS) processing of the user plane, and implementation of flow control rules (such as gating, redirection, and traffic redirection).

[0155] 4. 3GPP (3rd Generation Partnership Project) PS (Packet Switch) Data Off is an optional feature. When configured by the HPLMN (Home Public Land Mobile Network) and activated by the user, this feature prevents the transmission of all IP packets, except for IP packets required for the 3GPP PS Data Off exemption service, through the PDN (Packet Data Network) connection in 3GPP access.

[0156] 5. 3GPP PSData Off Exempt Services: A set of operator services that are allowed even when the UE's 3GPP PSData Off function is activated.

[0157] For IP-type PDN connections or PDU sessions, a maximum of two sets of operator services are allowed (including signaling for enabling such services), even if the UE's 3GPP PS data shutdown state is set to active. The UE uses one set in the HPLMN and the other set when roaming in the VPLMN. For non-IP or Ethernet-type PDN connections, or Ethernet or unstructured PDU sessions, no 3GPP data shutdown exemption services are defined.

[0158] The UE can be configured with up to two 3GPP PS data shutdown exemption service lists, and these lists are provided to the UE by the HPLMN through device management or UICC (Universal Integrated Circuit Card).

[0159] This disclosure provides a method that can be applied to business scenarios. For example, it can be applied to a location scenario. Of course, the method provided by this disclosure can also be applied to any other possible business scenario.

[0160] Optionally, the methods for establishing a user plane connection between the LMF network element and the terminal may include the following two:

[0161] The first type is the process of establishing a user plane connection initiated by the network.

[0162] The second type involves the terminal initiating the user plane connection establishment process.

[0163] Optionally, the specific steps of the "network-initiated user plane connection establishment process" in the first method described above may include the following steps:

[0164] Step 1: The LMF sends a user plane connection establishment command to the terminal through the Access and Mobility Management Function (AMF) network element. This user plane connection establishment command may include the Location Service User Plane address (LCS-UP address). The LCS-UP address can be, for example, the LMF's Internet Protocol (IP) address or the LMF's Fully Qualified Domain Name (FQDN).

[0165] Step 2: After receiving the user plane connection establishment command, if the terminal has not established a Packet Data Unit (PDU) session, it will establish a PDU session for user plane positioning. For example, the terminal can establish a PDU session for the Location Service User Plane Protocol (LCS-UPP).

[0166] Step 3: The terminal sends a user plane connection establishment confirmation to the LMF through the AMF (i.e., through the control plane). This user plane connection establishment confirmation can be used to notify the LMF that the PDU session has been established. The user plane connection establishment confirmation may include the terminal's terminal identifier (ID), which can be used to inform the LMF which terminal's PDU session has been established.

[0167] Step 4: The terminal uses the LCS-UP address received in Step 1 to establish a user plane connection (or Transport Layer Security (TLS) connection) with the LMF. During this process, the terminal sends its terminal address to the LMF via the user plane connection. This terminal address can be, for example, the terminal's IP address. This terminal address informs the LMF which specific terminal is establishing the user plane connection with the LMF.

[0168] Step 5: After establishing a user plane connection with the LMF, the terminal will also send a user plane connection establishment confirmation to the LMF through the control plane (e.g., through the AMF). This confirmation is used to inform the LMF that the user plane connection has been established. Optionally, the confirmation may include a terminal identifier, which can be used to inform the LMF which specific terminal has established the user plane connection with the LMF.

[0169] Optionally, only one step can be performed in steps 3 and 5 above. For example, only step 3 can be performed, or only step 5 can be performed, or both steps 3 and 5 can be performed simultaneously.

[0170] Optionally, the specific steps of "the terminal initiating the user plane connection establishment process" in the second method described above may include the following steps:

[0171] Step 0: The terminal sends a user plane connection establishment request to the LMF through the AMF to request the establishment of a user plane connection with the LMF.

[0172] Then, perform steps 1-5 as described above.

[0173] In some embodiments, the implementation process of LCS-UPP (Location Service User Plane) service can be seen in Figure 1b. Specifically, it may include the following steps:

[0174] 1.1 During the user plane connection establishment process requested by the UE, the UE sends a plane connection establishment request to the LMF through the AMF to request the establishment of a user plane connection with the LMF. This step is skipped for user plane connection establishment processes initiated by the network.

[0175] 1.2 For the user plane connection establishment process initiated by the network, the LMF sends a user plane connection establishment command message to the UE through the AMF.

[0176] Upon receiving the User Plane Connection Establishment Command Message, if no PDU session has been established, the UE will establish a PDU session for LCS-UPP. If a PDU session has already been established for LCS-UPP, this operation will be skipped.

[0177] 1.3 The UE performs the TLS (Transport Layer Security) connection establishment process with the LMF.

[0178] 1.4. The UE and LMF perform the TLS connection binding process.

[0179] A. The UE sends a user plane connection binding request to the LMF through the established TLS connection.

[0180] B. The LMF binds the TLS connection to the UE identifier (ID).

[0181] C. In the successful case, the LMF sends a user plane connection binding accept message to the UE via the TLS connection; in the unsuccessful case, the LMF sends a user plane connection binding reject message to the UE.

[0182] 1.5 If the UE receives a user plane connection binding accept message, the UE sends a user plane connection establishment complete message to the LMF through the AMF.

[0183] Optionally, during the network-initiated user plane connection establishment process, one possible scenario is:

[0184] The UE's user plane is unavailable (e.g., due to the 3GPP PS data off state being "active"), but the LMF cannot obtain this user plane unavailability status. The LMF can still send a user plane establishment command message to attempt to establish a secure LCS (Location Service) user plane connection with the UE. Alternatively, because the UE's user plane is unavailable, upon receiving the user plane establishment command message, the UE notifies the LMF of its user plane unavailability status via a user plane connection establishment failure message with the cause value "#4 User plane unavailable". Upon receiving this cause value, the LMF considers the UE's user plane unavailable. The LMF will not initiate a network-initiated user plane connection establishment process; if location services are still required, other available location methods can be considered.

[0185] Optionally, during the user plane connection release process requested by the UE, one possible scenario is:

[0186] This situation occurs when a secure LCS user plane connection has already been established between the UE and the LMF. If the UE's user plane becomes unavailable (e.g., due to the 3GPP PS data off state being "active"), the UE sends a user plane connection release request message with the cause value "#4 User plane unavailable". Upon receiving the cause value, the LMF considers the UE's user plane unavailable. The LMF will not initiate a network-initiated user plane connection establishment process; if location services are still required, other available location methods can be considered.

[0187] In both of the above processes, after receiving the cause value "User plane unavailable", the LMF considers the UE's user plane to be unavailable. When the LMF receives another user plane connection establishment request from the UE, this request means that user plane availability has been restored, and the LMF considers the user plane to be available.

[0188] The business processes for the two scenarios mentioned above might be:

[0189] 1. UE: User plane unavailable (e.g., 3GPP PS data off status is "activated").

[0190] 2a.LMF->AMF->UE: User plane connection establishment command;

[0191] UE->AMF->LMF: User plane connection establishment failed (user plane unavailable).

[0192] 2b.UE->AMF->LMF: User plane connection release request (user plane unavailable);

[0193] 3. LMF: This indicates that the user plane of the UE is unavailable, and other available positioning solutions can be considered.

[0194] 4. UE: User plane available (e.g., 3GPP PS data off status is "deactivated").

[0195] 5. UE->AMF->LMF: User plane connection establishment request.

[0196] 6. LMF: Indicates that the user plane of the UE is available.

[0197] However, without establishing a secure LCS user plane connection, the LMF cannot immediately obtain the UE's user plane availability status when the UE's user plane is unavailable. The LMF will still assume the user plane is available. The LMF must send a user plane connection establishment command message that is destined to fail so that the LMF can obtain the "user plane unavailable" status from the UE.

[0198] Therefore, if there is no established secure LCS user plane connection between the UE and the LMF, the LMF must waste time sending a user plane connection establishment command message to obtain the user plane unavailable status from the UE.

[0199] After the LMF obtains the UE's "user plane unavailable" state, it only considers the user plane available when it receives a user plane connection establishment request from the UE. However, the UE only sends this request when it decides to request the establishment of a secure LCS user plane connection. That is, if the UE does not need to transmit uplink data to the LMF, or if the UE does not decide to request LCS-UPP transmission of uplink data, the LMF will never update the user plane availability state and will always assume the UE's user plane is unavailable. This prevents the LMF from selecting LCS-UPP for location requests and may also lead to increased rejection of location requests during control plane congestion.

[0200] Therefore, once the UE reports its user plane unavailable status to the LMF, the LMF will always consider the UE's user plane unavailable unless the UE decides to request LCS-UPP to transmit uplink data and send a user plane establishment request message.

[0201] To address the aforementioned issues, this disclosure provides a method for the UE and LMF to retry LCS-UPP for the UE's relevant services after the UE reports its "user plane unavailable" status to the LMF.

[0202] It should be noted that in the embodiments of this disclosure, LMF can be replaced with SF (sensing function), location service / request can be replaced with sensing service / request, and LCS-UPP can be replaced with sensing service user plane protocol and ranging / sidechain positioning service user plane protocol.

[0203] Based on the aforementioned wireless communication system, various embodiments of the communication method proposed in this disclosure will be described in detail below.

[0204] It should be understood that the network elements in the embodiments of this disclosure are taken as network elements in the 5G network architecture, but the specific names of the network elements are not limited in the embodiments of this disclosure.

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

[0206] S201, The terminal sends a third message to the first network element.

[0207] In some embodiments, the third message is used to notify the first network element that the user plane status of the terminal is unavailable.

[0208] In some embodiments, the third message may include information indicating that the end-user plane is unavailable.

[0209] In some embodiments, if an established user plane connection already exists between the terminal and the first network element, the third message can be a user plane connection release message.

[0210] Optionally, the terminal can notify the first network element that its user plane is unavailable by sending a user plane connection release message to the first network element.

[0211] In some embodiments, if no user plane connection is established between the terminal and the first network element, the third message may be a user plane availability notification message or a user plane status notification message, but the message name is not limited to these.

[0212] Optionally, the terminal can notify the first network element that its user plane is unavailable by sending a user plane availability notification message or a user plane status notification message to the first network element.

[0213] In some embodiments, the third message may also include a first value of the timer.

[0214] Optionally, the user plane connection release message, user plane availability notification message, or user plane status notification message may also include a first value of a timer, so that when the first network element determines that the user plane of the terminal is unavailable based on the received message, it sets the timer based on the first value of the timer in the message.

[0215] In some embodiments, the first network element can be used to provide location services, such as a Location Management Function (LMF) network element, but the name is not limited thereto.

[0216] Optionally, the first network element can also be a network element within the core network that provides other services. For example, the first network element can be a sensing function (SF) that provides sensing services, or a network element in the core network that provides new services.

[0217] In some embodiments, the terminal can send a third message to the first network element through the second network element.

[0218] Optionally, the method by which the terminal sends a third message to the first network element through the second network element may include, for example, the terminal first sending the third message to the second network element, and then the second network element sending the third message to the first network element.

[0219] In some embodiments, the second network element may be a functional network element that provides access to the core network for the terminal, such as an Access and Mobility Management Function (AMF) network element, but the name is not limited thereto.

[0220] In some embodiments, after the terminal encapsulates the third message in an uplink non-access stratum transport message (UL NAS TRANSPORT) and sends it to the second network element, the second network element encapsulates the third message in an N1 message notification message (Namf_Communication_N1MessageNotify) and sends it to the first network element.

[0221] In some embodiments, network elements can also be described as network functions, network nodes, network function entities, etc. The logical functions that network functions can be flexibly deployed can also be specific logical function entities, but are not limited to this.

[0222] S202. When the first network element determines that the user plane of the terminal is unavailable, it starts a timer.

[0223] In some embodiments, the first network element receives a third message sent by the terminal and determines the status of the terminal user plane as unavailable based on the third message.

[0224] In some embodiments, the first network element receives a third message sent by the terminal through the second network element, and determines the status of the terminal user plane as unavailable based on the third message.

[0225] In some embodiments, if the third message includes a timer value, the first network element can set the timer value to the value in the third message.

[0226] In some embodiments, when the first network element determines that the state of the terminal user plane is unavailable based on a third message, it starts a timer.

[0227] Optionally, if the third message includes the first value of the timer, the value of the timer to be started by the first network element can be set to the first value of the timer in the third message.

[0228] In some embodiments, if the third message does not include the first value of the timer, the value of the timer to be started by the first network element can be a predetermined duration.

[0229] In some embodiments, the terms “duration”, “segment”, “time window”, “window”, and “time” can be used interchangeably.

[0230] In some embodiments, the timer can be a timer related to the location service, such as T5012, T5010, T5015, etc., but is not limited thereto.

[0231] S203. Before the timer expires or stops, the first network element does not trigger the user plane connection establishment process with the terminal.

[0232] In some embodiments, the first network element does not trigger the user plane connection establishment process with the terminal before the timer expires. Optionally, the first network element does not initiate the user plane connection establishment process with the terminal before the timer expires.

[0233] In some embodiments, the first network element does not trigger the user plane connection establishment process with the terminal before the timer stops. Optionally, the first network element does not initiate the user plane connection establishment process with the terminal during the period from when the timer starts to when the timer stops.

[0234] In some embodiments, after the timer is started, during the timer's operation, since the user plane of the terminal is unavailable, the first network element does not trigger the user plane connection establishment process with the terminal.

[0235] Based on the above embodiments, the above method may further include: during the operation of the timer, the first network element determines that a control plane-related method is used for the first service of the terminal.

[0236] In some embodiments, after the timer is started, during the timer's operation, since the user plane of the terminal is unavailable, the first network element can process the terminal's first service using a control plane-related method.

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

[0238] Perceive business;

[0239] Location services;

[0240] Ranging / sidechain positioning services.

[0241] In some embodiments, control plane-related methods may include at least one of the following:

[0242] Control surface perception method;

[0243] Control surface positioning method;

[0244] Control surface ranging / side chain positioning method.

[0245] In some embodiments, after the timer is started, during the timer's operation, since the user plane of the terminal is unavailable, the first network element can process the terminal's sensing services using a control plane sensing method.

[0246] In some embodiments, after the timer is started, during the timer's operation, since the user plane of the terminal is unavailable, the first network element can use the control plane positioning method to process the terminal's positioning service.

[0247] In some embodiments, after the timer is started, during the timer's operation, since the user plane of the terminal is unavailable, the first network element can process the terminal's ranging / sidechain positioning service using the control plane ranging / sidechain positioning method.

[0248] In some embodiments, if the first network element does not receive a message including information indicating that the user plane of the terminal is available after the timer is started, the timer continues to run until it expires.

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

[0250] In some embodiments, terms such as “send,” “transmit,” “report,” “distribute,” “transfer,” “bidirectional transmission,” “send and / or receive” can be used interchangeably.

[0251] In some embodiments, terms such as "certain," "preset," "default," "set," "indicated," "a certain," "any," and "first" can be used interchangeably. "Certain A," "preset A," "default A," "set A," "indicated A," "a certain A," "any A," and "first A" can be interpreted as A pre-defined in a protocol or the like, or as A obtained through setting, configuration, or instruction, or as specific A, a certain A, any A, or first A, but are not limited thereto.

[0252] In some embodiments, terms such as “in the case of,” “when,” “when,” “if,” “if,” etc., can be used interchangeably.

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

[0254] In some embodiments, step S201 is optional and can be combined with the embodiments described above as independent embodiments. In different embodiments, one or more of these steps can be omitted or substituted.

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

[0256] S210, the first network element sends a second message to the terminal.

[0257] In some embodiments, the second message is used to determine whether the user plane status of the terminal is available.

[0258] In some embodiments, the second message is used to attempt to establish a user plane connection.

[0259] In some embodiments, the second message may be a user plane connection establishment command message or a user plane availability query message, but the message name is not limited to these.

[0260] Optionally, the first network element sends a second message to the terminal through the second network element.

[0261] Optionally, the method by which the first network element sends the second message to the terminal through the second network element may include, for example, the first network element sending the second message to the second network element first, and then the second network element sending the second message to the terminal.

[0262] In some embodiments, after the first network element encapsulates the second message in an N1N2 message transfer message (Namf_Communication_N1N2MessageTransfer) and sends it to the second network element, the second network element encapsulates the third message in a downlink non-access stratum transfer message (DL NAS TRANSPORT) and sends it to the terminal.

[0263] Optionally, the first network element can be, for example, an LMF or an SF.

[0264] Optionally, the second network element can be, for example, an AMF.

[0265] In some embodiments, the first network element can determine whether the user plane status of the terminal is available or unavailable by sending a second message to the terminal.

[0266] S211, The terminal sends a third message to the first network element.

[0267] In some embodiments, the third method is used to notify the first network element that the user plane status of the terminal is unavailable.

[0268] In some embodiments, the third message may include information indicating that the user plane of the terminal is unavailable.

[0269] In some embodiments, the terminal may send a third message to the first network element in response to the second message sent by the first network element.

[0270] In some embodiments, if the second message is a user plane connection establishment command message, then the third message can be a user plane connection establishment failure message.

[0271] In some embodiments, if the second message is a user plane availability query message, then the third message can be a user plane availability query response message. Optionally, this message may include information indicating that the user plane of the terminal is unavailable.

[0272] In some embodiments, the third message may also include a first value of the timer.

[0273] Optionally, the user plane connection establishment failure message or the user plane availability query response message may also include a first value of a timer, so that when the first network element determines that the user plane of the terminal is unavailable based on the received message, it sets the timer based on the first value of the timer in the message.

[0274] In some embodiments, if the third message does not include the first value of the timer, the value of the timer to be started by the first network element can be a predetermined duration.

[0275] In some embodiments, the terminal can send a third message to the first network element through the second network element.

[0276] Optionally, the method by which the terminal sends a third message to the first network element through the second network element may include, for example, the terminal first sending the third message to the second network element, and then the second network element sending the third message to the first network element.

[0277] In some embodiments, after the terminal encapsulates the third message in an uplink non-access stratum transport message (UL NAS TRANSPORT) and sends it to the second network element, the second network element encapsulates the third message in an N1 message notification message (Namf_Communication_N1MessageNotify) and sends it to the first network element.

[0278] S212. When the first network element determines that the user plane of the terminal is unavailable, it starts a timer.

[0279] For details of the optional implementation of step S212, please refer to the optional implementation of step S202 in FIG2a and other related parts in the embodiment involved in FIG2a, which will not be repeated here.

[0280] S213. Before the timer expires or stops, the first network element does not trigger the user plane connection establishment process with the terminal.

[0281] For details of the optional implementation of step S213, please refer to the optional implementation of step S203 in FIG2a and other related parts in the embodiment involved in FIG2a, which will not be repeated here.

[0282] S214. The first network element retransmits the second message to the terminal and restarts the timer.

[0283] In some embodiments, when the timer runs to a predetermined expiration time, the first network element can retransmit the second message to the terminal to re-determine the user plane status of the terminal.

[0284] In some embodiments, the predetermined expiration time can be the time when the timer first expires, or it can be other expiration times, such as the time when the timer expires twice consecutively, or a fixed time as the predetermined expiration time, but it is not limited to these.

[0285] In some embodiments, terms such as “moment,” “point in time,” “time,” and “time location” can be used interchangeably.

[0286] In some embodiments, if the first network element receives a third message after sending the second message for the first time, a timer is started. If no other message is received before the timer expires, such as a message indicating that the user plane of the terminal is available (which may correspond to the first message mentioned above), the first network element determines the status of the user plane of the terminal again by restarting the timer and retransmitting the second message.

[0287] In some embodiments, after the first network element retransmits the second message, it may receive a response message from the terminal (e.g., a third message, or a message including information indicating that the terminal's user plane is available), or it may still not receive a message including information indicating that the terminal's user plane is available. Optionally, when the timer reaches a predetermined expiration time, if the first network element receives a third message as a response message, or does not receive a message including information indicating that the terminal's user plane is available, the first network element will continue to retransmit the second message when the timer reaches the predetermined expiration time again, and restart the timer again until it receives a message including information indicating that the terminal's user plane is available.

[0288] S215. If the number of timer restarts exceeds the preset value, the first network element determines that the user plane status of the terminal is unavailable and does not use user plane related methods for the terminal's first service.

[0289] In some embodiments, if the timer restarts more than a predetermined number (e.g., 4 times), that is, when the timer has expired 5 times, the first network element can determine that the user plane of the terminal is consistently unavailable. In this case, the first network element determines that the first service of the terminal will not be processed using user plane-related methods. Optionally, control plane-related methods can be used for processing.

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

[0291] Perceive business;

[0292] Location services;

[0293] Ranging / sidechain positioning services.

[0294] In some embodiments, user-plane related methods may include at least one of the following:

[0295] User-face perception methods;

[0296] User plane positioning method;

[0297] User face ranging / side chain positioning method.

[0298] In some embodiments, if the timer restarts more than a predetermined number of times, and the user plane of the terminal remains unavailable, the first network element does not process the terminal's sensing services using the user plane sensing method. Optionally, the terminal's sensing services can be processed using the control plane sensing method.

[0299] In some embodiments, if the timer restarts more than a predetermined number of times, and the user plane of the terminal remains unavailable, the first network element does not use the user plane positioning method to process the terminal's positioning service. Optionally, the control plane positioning method can be used to process the terminal's positioning service.

[0300] In some embodiments, if the timer restarts more than a predetermined number of times, and the user plane of the terminal remains unavailable, the first network element does not use the user plane ranging / sidechain positioning method to process the terminal's ranging / sidechain positioning service. Optionally, the control plane ranging / sidechain positioning method can be used to process the terminal's ranging / sidechain positioning service.

[0301] The method involved in the embodiments of this disclosure may include at least one of steps S210 to S215. For example, steps S212 and S213 may be implemented as independent embodiments, steps S211, S212 and S213 may be implemented as independent embodiments, steps S210, S211, S212 and S213 may be implemented as independent embodiments, and steps S211, S212, S213, S214 and S215 may be implemented as independent embodiments, but are not limited thereto.

[0302] In some embodiments, step S210 is optional and can be combined with the embodiments described above as independent embodiments. In different embodiments, one or more of these steps can be omitted or substituted.

[0303] In some embodiments, step S211 is optional, and one or more of these steps may be omitted or substituted in different embodiments.

[0304] In some embodiments, step S214 is optional, and one or more of these steps may be omitted or substituted in different embodiments.

[0305] In some embodiments, step S215 is optional, and one or more of these steps may be omitted or substituted in different embodiments.

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

[0307] S221, The terminal sends a third message to the first network element.

[0308] For details on the optional implementation of step S221, please refer to the optional implementation of step S201 in FIG2a and other related parts in the embodiment involved in FIG2a, which will not be repeated here.

[0309] S222. When the first network element determines that the user plane of the terminal is unavailable, it starts a timer.

[0310] For details of the optional implementation of step S222, please refer to the optional implementation of step S202 in FIG2a and other related parts in the embodiment involved in FIG2a, which will not be repeated here.

[0311] S223, The first network element receives the first message.

[0312] In some embodiments, the first message is used to notify the first network element that the user plane status of the terminal is available.

[0313] In some embodiments, the first message may include information indicating that the user plane of the terminal is available.

[0314] In some embodiments, the first network element determines that the user plane of the terminal is available based on the received first message.

[0315] In some embodiments, step S223 may include S223a, where the first network element receives a first message sent by the terminal.

[0316] In some embodiments, the terminal may send a first message to the first network element.

[0317] In some embodiments, the terminal can send a third message to the first network element through the second network element.

[0318] Optionally, the method by which the terminal sends a third message to the first network element through the second network element may include, for example, the terminal first sending the third message to the second network element, and then the second network element sending the third message to the first network element.

[0319] In some embodiments, after the terminal encapsulates the first message in an uplink non-access stratum transport message (UL NAS TRANSPORT) and sends it to the second network element, the second network element encapsulates the first message in an N1 message notification message (Namf_Communication_N1MessageNotify) and sends it to the first network element.

[0320] In some embodiments, the second network element may be an AMF, but is not limited thereto.

[0321] In some embodiments, the first message may be a user plane connection establishment request message. Optionally, if the first network element receives the user plane connection establishment request message sent by the terminal, it can determine that the terminal's user plane has been restored to an available state.

[0322] Optionally, the user plane connection establishment request can be used by the terminal to request the establishment of a user plane connection with the first network element.

[0323] Alternatively, the user plane connection may also be referred to as a Transport Layer Security (TLS) connection.

[0324] In some embodiments, the first message may be a user plane availability notification message or a user plane status notification message, but the message name is not limited to these.

[0325] In some embodiments, the terminal may notify the first network element of user plane availability information by sending a user plane availability notification message or a user plane status notification message to the first network element.

[0326] Optionally, if the first network element receives a user plane availability notification message or a user plane status notification message sent by the terminal, which includes information about the availability of the user plane, then it can determine that the user plane of the terminal has been restored to an available state.

[0327] In some embodiments, step S223 may include S223b, whereby the first network element receives a first message sent by the second network element.

[0328] In some embodiments, the second network element may be a functional network element that provides access to the core network for the terminal, such as an Access and Mobility Management Function (AMF) network element, but the name is not limited thereto.

[0329] In some embodiments, the AMF can notify the first network element of the available user plane information of the terminal via the Namf_EventExposure_Notify message.

[0330] In some embodiments, the second network element can be a functional network element for session services, such as a Session Management Function (SMF) network element, but the name is not limited thereto.

[0331] In some embodiments, the SMF can notify the first network element of the available user plane information of the terminal via the Nsmf_EventExposure_Notify message.

[0332] S224. When the first network element determines that the user plane of the terminal is available, it stops the timer.

[0333] In some embodiments, if the first network element determines that the user plane of the terminal is available based on the received first message, the running timer is stopped.

[0334] In some embodiments, the first network element does not trigger the user plane connection establishment process with the terminal before the timer stops running. Optionally, the first network element does not initiate the user plane connection establishment process with the terminal during the period from when the timer starts running until the timer stops running.

[0335] In some embodiments, if the first network element determines that the user plane of the terminal is available based on the received first message, it processes the first service of the terminal using a user plane-related method when it receives a service request.

[0336] In some embodiments, if the first network element determines that the user plane of the terminal is available, it can trigger the user plane connection establishment process with the terminal.

[0337] In some embodiments, if the first network element determines that the user plane of the terminal is available, then the first service of the terminal can be processed using a user plane-related method.

[0338] It should be noted that the content regarding the methods related to the first business and the user plane can be found in the relevant description in conjunction with Figure 2b above, and will not be repeated here.

[0339] In some embodiments, after the timer is started and before it stops operating, the first network element can process the first service of the terminal using a control plane-related method.

[0340] It should be noted that the methods related to the first business and control plane can be found in the relevant description above in conjunction with Figure 2a, and will not be repeated here.

[0341] The method involved in the embodiments of this disclosure may include at least one of steps S221 to S224. For example, steps S222, S223a, and S224 may be implemented as independent embodiments, as may steps S222, S223b, and S224, as may steps S221, S222, S223a, and S224, as independent embodiments, but are not limited thereto.

[0342] In some embodiments, step S221 is optional and can be combined with the embodiments described above as independent embodiments. In different embodiments, one or more of these steps can be omitted or substituted.

[0343] In some embodiments, step S223a is optional, and one or more of these steps may be omitted or substituted in different embodiments.

[0344] In some embodiments, step S223b is optional, and one or more of these steps may be omitted or substituted in different embodiments.

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

[0346] S230, the first network element sends the second message to the terminal.

[0347] For details of the optional implementation of step S230, please refer to the optional implementation of step S210 in FIG2b and other related parts in the embodiment involved in FIG2b, which will not be repeated here.

[0348] S231, The terminal sends a third message to the first network element.

[0349] For details of the optional implementation of step S231, please refer to the optional implementation of step S211 in Figure 2b and other related parts in the embodiment involved in Figure 2b, which will not be repeated here.

[0350] S232. When the first network element determines that the user plane of the terminal is unavailable, it starts a timer.

[0351] For details of the optional implementation of step S232, please refer to the optional implementation of step S202 in FIG2a and other related parts in the embodiment involved in FIG2a, which will not be repeated here.

[0352] S233. Before the timer expires or stops, the first network element does not trigger the user plane connection establishment process with the terminal.

[0353] For details of the optional implementation of step S233, please refer to the optional implementation of step S203 in FIG2a and other related parts in the embodiment involved in FIG2a, which will not be repeated here.

[0354] S234. The first network element retransmits the second message to the terminal and restarts the timer.

[0355] In some embodiments, when the timer runs to a predetermined expiration time, the first network element can retransmit the second message to the terminal to re-determine the user plane status of the terminal.

[0356] In some embodiments, the predetermined expiration time can be the time when the timer first expires, or it can be other expiration times, such as the time when the timer expires twice consecutively, or a fixed time as the predetermined expiration time, but it is not limited to these.

[0357] In some embodiments, terms such as “moment,” “point in time,” “time,” and “time location” can be used interchangeably.

[0358] In some embodiments, if the first network element receives a third message after sending the second message for the first time, a timer is started. If no other message is received before the timer expires, such as a message indicating that the user plane of the terminal is available (which may correspond to the first message below), the first network element restarts the timer and retransmits the second message to determine the status of the user plane of the terminal again.

[0359] In some embodiments, after the first network element retransmits the second message, it may receive a response message from the terminal (e.g., a third message, or the first message), or it may still not receive the first message. Optionally, when the timer reaches a predetermined expiration time, if the first network element receives a third message as a response message, or does not receive the first message, the first network element will continue to retransmit the second message when the timer reaches the predetermined expiration time again, and restart the timer again until the first message is received.

[0360] In some embodiments, the method by which the first network element retransmits the second message to the terminal through the second network element may include, for example, the first network element sending the second message to the second network element first, and then the second network element sending the second message to the terminal.

[0361] In some embodiments, after the first network element encapsulates the second message in an N1N2 message transfer message (Namf_Communication_N1N2MessageTransfer) and sends it to the second network element, the second network element encapsulates the third message in a downlink non-access stratum transfer message (DL NAS TRANSPORT) and sends it to the terminal.

[0362] S235, The first network element receives the first message.

[0363] In some embodiments, the second message may be a user plane availability query message, and the first message may be a user plane availability query response message. Optionally, the message may include information indicating that the user plane of the terminal is available.

[0364] In some embodiments, the second message may be a user plane connection establishment command message, and the first message may be a user plane connection establishment completion message. Optionally, the message may include information indicating that the user plane of the terminal is available.

[0365] In some embodiments, the first network element may receive a first message from the terminal (e.g., step S235a) or a first message from the second network element (e.g., step S235b).

[0366] For details of the optional implementation of step S235, please refer to the optional implementation of step S223 in FIG2c and other related parts in the embodiment involved in FIG2c, which will not be repeated here.

[0367] S236. When the first network element determines that the user plane of the terminal is available, it stops the timer.

[0368] For details of the optional implementation of step S236, please refer to the optional implementation of step S224 in FIG2c and other related parts in the embodiment involved in FIG2c, which will not be repeated here.

[0369] In some embodiments, if the number of timer restarts exceeds a preset value and the first message is still not received, it is determined that the terminal user plane is always unavailable.

[0370] It should be noted that for solutions regarding the timer restart count exceeding the preset value, please refer to the relevant content of step S215 in Figure 2b above, which will not be repeated here.

[0371] In some embodiments, after the timer is started and before it stops operating, the first network element can process the first service of the terminal using a control plane-related method.

[0372] It should be noted that the methods related to the first business and control plane can be found in the relevant description above in conjunction with Figure 2a, and will not be repeated here.

[0373] The method involved in the embodiments of this disclosure may include at least one of steps S230 to S236. For example, steps S232 and S233 may be implemented as independent embodiments, steps S231, S232, and S233 may be implemented as independent embodiments, steps S230, S231, S232, and S233 may be implemented as independent embodiments, steps S232, S233, S234, S235a, and S236 may be implemented as independent embodiments, steps S232, S233, S234, S235b, and S236 may be implemented as independent embodiments, but are not limited thereto.

[0374] In some embodiments, step S230 is optional and can be combined with the embodiments described above as independent embodiments. In different embodiments, one or more of these steps can be omitted or substituted.

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

[0376] In some embodiments, step S234 is optional, and one or more of these steps may be omitted or substituted in different embodiments.

[0377] In some embodiments, step S235a is optional, and one or more of these steps may be omitted or substituted in different embodiments.

[0378] In some embodiments, step S225b is optional, and one or more of these steps may be omitted or substituted in different embodiments.

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

[0380] S241, The terminal sends a third message to the first network element.

[0381] For details of the optional implementation of step S241, please refer to the optional implementation of step S201 in FIG2a and other related parts in the embodiment involved in FIG2a, which will not be repeated here.

[0382] S242. When the first network element determines that the user plane of the terminal is unavailable, it starts a timer.

[0383] For details of the optional implementation of step S242, please refer to the optional implementation of step S202 in FIG2a and other related parts in the embodiment involved in FIG2a, which will not be repeated here.

[0384] S243. Before the timer expires or stops, the first network element does not trigger the user plane connection establishment process with the terminal.

[0385] For details of the optional implementation of step S243, please refer to the optional implementation of step S203 in FIG2a and other related parts in the embodiment involved in FIG2a, which will not be repeated here.

[0386] S244, The first network element sends a second message to the terminal.

[0387] In some embodiments, the second message is used to determine whether the user plane status of the terminal is available.

[0388] In some embodiments, after the first network element determines that the user plane of the terminal is unavailable, it can determine whether the user plane status of the terminal has been restored to available by sending a second message to the terminal.

[0389] S245, The first network element receives the first message.

[0390] In some embodiments, the first message is used to notify the first network element that the user plane status of the terminal is available.

[0391] For details of the optional implementation of step S245, please refer to the optional implementation of step S235 in FIG2d and other related parts in the embodiment involved in FIG2d, which will not be repeated here.

[0392] S246. When the first network element determines that the user plane of the terminal is available, it stops the timer.

[0393] For details of the optional implementation of step S246, please refer to the optional implementation of step S224 in FIG2c and other related parts in the embodiment involved in FIG2c, which will not be repeated here.

[0394] In some embodiments, after the timer is started and before it stops operating, the first network element can process the first service of the terminal using a control plane-related method.

[0395] It should be noted that the methods related to the first business and control plane can be found in the relevant description above in conjunction with Figure 2a, and will not be repeated here.

[0396] In some embodiments, after the first network element sends the second message to the terminal, it may receive the third message, or if the timer runs to the predetermined expiration time without receiving the first message, the first network element may resend the second message and restart the timer.

[0397] It should be noted that the solution for resending the second message can be found in step S214 of Figure 2b above, or in step S234 of Figure 2d, and will not be repeated here.

[0398] In some embodiments, if the number of timer restarts exceeds a preset value and the first message is still not received, it is determined that the terminal user plane is always unavailable.

[0399] It should be noted that for solutions regarding the timer restart count exceeding the preset value, please refer to the relevant content of step S215 in Figure 2b above, which will not be repeated here.

[0400] In some embodiments, if the first message is received in response to a retransmitted second message, it is determined that the terminal user plane is always available, and the timer is stopped. For details on this scheme, please refer to step S224 in Figure 2c above; it will not be repeated here.

[0401] The method involved in the embodiments of this disclosure may include at least one of steps S241 to S246. For example, steps S242 and S243 may be implemented as independent embodiments, steps S241, S242, and S243 may be implemented as independent embodiments, steps S242, S243, S244, S245a, and S246 may be implemented as independent embodiments, steps S242, S243, S244, S245b, and S246 may be implemented as independent embodiments, and steps S241, S242, S243, S244, S245a, and S246 may be implemented as independent embodiments, but are not limited thereto.

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

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

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

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

[0406] Figure 3a is a flowchart illustrating a communication method according to an embodiment of the present disclosure. As shown in Figure 3a, the communication method can be executed by a first network element, and the method includes:

[0407] S301, Obtain the third message.

[0408] In some embodiments, the third message is used to notify the first network element that the user plane status of the terminal is unavailable.

[0409] In some embodiments, the third message may include information indicating that the end-user plane is unavailable.

[0410] In some embodiments, the first network element acquiring the third message can be understood as receiving the third message. Optionally, the first network element receives the third message sent by the terminal.

[0411] In some embodiments, the first network element receives a third message sent by the terminal via the second network element.

[0412] For details of the optional implementation of step S301, please refer to the optional implementation of step S201 in FIG2a and other related parts in the embodiment involved in FIG2a, which will not be repeated here.

[0413] S302. Based on the third message, determine that the user plane status of the terminal is unavailable, and start the timer.

[0414] For details of the optional implementation of step S302, please refer to the optional implementation of step S202 in FIG2a and other related parts in the embodiment involved in FIG2a, which will not be repeated here.

[0415] In some embodiments, the value of the timer can be a predetermined duration.

[0416] In some embodiments, the third message includes a first value of the timer.

[0417] In some embodiments, if the third message includes a first value of the timer, the first network element can set the value of the timer to the first value in the third message and then start the timer.

[0418] S303. Before the timer expires or stops, the user plane connection establishment process with the terminal will not be triggered.

[0419] For details of the optional implementation of step S303, please refer to the optional implementation of step S203 in FIG2a and other related parts in the embodiment involved in FIG2a, which will not be repeated here.

[0420] In some embodiments, prior to step S301 described above, the method may further include sending a second message to the terminal.

[0421] In some embodiments, the second message is used to determine whether the user plane status of the terminal is available.

[0422] In some embodiments, the third message may be a response message to the second message. In this case, for details of the optional implementation of step S301 above, please refer to the optional implementation of step S211 in FIG2b and other related parts in the embodiment involved in FIG2b, which will not be repeated here.

[0423] In some embodiments, the method described above may further include: retransmitting the second message to the terminal and restarting the timer.

[0424] For details of the above optional implementation methods, please refer to the optional implementation of step S214 in FIG2b, the optional implementation of step S234 in FIG2d, and other related parts in the embodiments involved in FIG2b and FIG2d, which will not be repeated here.

[0425] In some embodiments, the method may further include: if the number of timer restarts exceeds a preset value, determining that the user plane state of the terminal is unavailable, and not using user plane-related methods for the first service of the terminal.

[0426] For details of the above optional implementation methods, please refer to the optional implementation of step S215 in FIG2b and other related parts in the embodiments involved in FIG2b, which will not be repeated here.

[0427] In some embodiments, the method may further include: acquiring a first message; determining, based on the first message, that the user plane of the terminal is available, and stopping the timer.

[0428] For details of the above optional implementation methods, please refer to the optional implementation methods of steps S223 and S224 in FIG2c, the optional implementation methods of steps S235 and S236 in FIG2d, and other related parts in the embodiments involved in FIG2c and FIG2d, which will not be repeated here.

[0429] In some embodiments, after the timer is started and before it stops operating, the first network element can process the first service of the terminal using a control plane-related method.

[0430] It should be noted that the methods related to the first business and control plane can be found in the relevant description above in conjunction with Figure 2a, and will not be repeated here.

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

[0432] In some embodiments, step S301 is optional and can be combined with the embodiments described above as independent embodiments. In different embodiments, one or more of these steps can be omitted or substituted.

[0433] Figure 3b is a flowchart illustrating a communication method according to an embodiment of the present disclosure. As shown in Figure 3b, the communication method can be executed by a first network element, and the method includes:

[0434] S311, Obtain the third message.

[0435] For details of the optional implementation of step S311, please refer to the optional implementation of step S301 in FIG3a and other related parts in the embodiment involved in FIG3a, which will not be repeated here.

[0436] S312. Based on the third message, determine that the user plane status of the terminal is unavailable, and start the timer.

[0437] For details of the optional implementation of step S312, please refer to the optional implementation of step S202 in FIG2a and other related parts in the embodiment involved in FIG2a, which will not be repeated here.

[0438] S313. The user plane connection establishment process with the terminal is not triggered before the timer expires or stops.

[0439] For details of the optional implementation of step S313, please refer to the optional implementation of step S203 in FIG2a and other related parts in the embodiment involved in FIG2a, which will not be repeated here.

[0440] S314, Receive the first message.

[0441] In some embodiments, the first network element receives a first message sent by the terminal.

[0442] In some embodiments, the first network element receives the first message sent by the terminal through the second network element.

[0443] In some embodiments, the first message is used to notify the first network element that the user plane status of the terminal is available.

[0444] In some embodiments, the first message may include information indicating that the user plane of the terminal is available.

[0445] For details of the optional implementation of step S314, please refer to the optional implementation of step S223 in FIG2c and other related parts in the embodiment involved in FIG2c, which will not be repeated here.

[0446] S315. Based on the first message, determine that the user plane of the terminal is available, and stop the timer.

[0447] In some embodiments, the first network element determines that the user plane of the terminal is available based on the received first message.

[0448] For details of the optional implementation of step S315, please refer to the optional implementation of step S224 in FIG2c and other related parts in the embodiment involved in FIG2c, which will not be repeated here.

[0449] In some embodiments, prior to step S314 described above, the method may further include sending a second message to the terminal.

[0450] In some embodiments, the second message is used to determine whether the user plane status of the terminal is available.

[0451] In some embodiments, the first message may be a response message to the second message. In this case, for details of the optional implementation of step S314 above, please refer to the optional implementation of step S245 in FIG2e and other related parts in the embodiment involved in FIG2e, which will not be repeated here.

[0452] The method involved in the embodiments of this disclosure may include at least one of steps S311 to S315. For example, steps S312 and S313 may be implemented as independent embodiments, steps S311, S312 and S313 may be implemented as independent embodiments, and steps S312, S313, S314 and S315 may be implemented as independent embodiments, but are not limited thereto.

[0453] In some embodiments, step S311 is optional and can be combined with the embodiments described above as independent embodiments. In different embodiments, one or more of these steps can be omitted or substituted.

[0454] In some embodiments, step S314 is optional and can be combined with the embodiments described above as independent embodiments. In different embodiments, one or more of these steps can be omitted or substituted.

[0455] In some embodiments, step S315 is optional and can be combined with the embodiments described above as independent embodiments. In different embodiments, one or more of these steps can be omitted or substituted.

[0456] Figure 3c is a flowchart illustrating a communication method according to an embodiment of the present disclosure. As shown in Figure 3c, the communication method can be executed by a first network element, and the method includes:

[0457] S321. Determine that the user plane status of the terminal is unavailable and start the timer.

[0458] For details of the optional implementation of step S321, please refer to the optional implementation of step S202 in FIG2a and other related parts in the embodiment involved in FIG2a, which will not be repeated here.

[0459] S322. The user plane connection establishment process with the terminal is not triggered before the timer expires or stops.

[0460] For details of the optional implementation of step S322, please refer to the optional implementation of step S203 in FIG2a and other related parts in the embodiment involved in FIG2a, which will not be repeated here.

[0461] In some embodiments, the method further includes: during the operation of the timer, determining a control plane-dependent method for a first service of the terminal.

[0462] In some embodiments, the method further includes:

[0463] Receive a first message, the first message being used to notify the terminal that the user plane is available;

[0464] Based on the first message, the user plane status of the terminal is determined to be available.

[0465] In some embodiments, the method further includes: sending a second message to the terminal, the second message being used to determine whether the user plane of the terminal is available.

[0466] In some embodiments, the method further includes:

[0467] If the first message is not received and the timer expires at the predetermined time, the second message is resent to the terminal, and the timer is restarted.

[0468] In some embodiments, the method further includes:

[0469] If the number of timer restarts exceeds a preset value, the user plane status of the terminal is determined to be unavailable, and user plane-related methods are not applied to the first service of the terminal.

[0470] In some embodiments, the first service includes at least one of the following:

[0471] Perceive business;

[0472] Location services;

[0473] Ranging / sidechain positioning services.

[0474] In some embodiments, the control plane-related methods include at least one of the following:

[0475] Control surface perception method;

[0476] Control surface positioning method;

[0477] Control surface ranging / side chain positioning method.

[0478] In some embodiments, the user-plane related methods include at least one of the following:

[0479] User-face perception methods;

[0480] User plane positioning method;

[0481] User face ranging / side chain positioning method.

[0482] In some embodiments, the method further includes:

[0483] Receive a third message from the terminal, the third message being used to notify the terminal that the user plane is unavailable;

[0484] Based on the third message, it is determined that the user plane of the terminal is unavailable.

[0485] In some embodiments, the third message includes a first value of a timer, and the method further includes:

[0486] Set the value of the timer to the first value included in the third message.

[0487] In some embodiments, the value of the timer is a predetermined duration.

[0488] Figure 4a is a flowchart illustrating a communication method according to an embodiment of the present disclosure. As shown in Figure 4a, the communication method can be executed by a terminal, and the method includes:

[0489] S401, Send the third message.

[0490] In some embodiments, the terminal sends a third message to the first network element.

[0491] In some embodiments, the terminal sends a third message to the first network element through the second network element.

[0492] In some embodiments, the third message is used to notify the first network element that the user plane status of the terminal is unavailable.

[0493] In some embodiments, the third message may include information indicating that the end-user plane is unavailable.

[0494] In some embodiments, the third message includes a first value of the timer.

[0495] For details of the optional implementation of step S401, please refer to the optional implementation of step S201 in FIG2a and other related parts in the embodiment involved in FIG2a, which will not be repeated here.

[0496] S402, Obtain the second message.

[0497] In some embodiments, the terminal obtains the second message sent by the first network element through the second network element.

[0498] In some embodiments, the second message is used to determine whether the user plane status of the terminal is available.

[0499] In some embodiments, the terminal acquiring the second message can be understood as receiving the second message. Optionally, the terminal receives the second message sent by the first network element.

[0500] In some embodiments, the second message may be a user plane connection establishment command message or a user plane availability query message, but the message name is not limited to these.

[0501] For details of the optional implementation of step S402, please refer to the optional implementation of step S244 in FIG2e and other related parts in the embodiment involved in FIG2e, which will not be repeated here.

[0502] S403, Send the first message.

[0503] In some embodiments, the terminal sends a first message to the first network element.

[0504] In some embodiments, the terminal sends a first message to the first network element through the second network element.

[0505] In some embodiments, the first message is used to notify the first network element that the user plane status of the terminal is available.

[0506] In some embodiments, the first message may be a response message to the second message.

[0507] For details of the optional implementation of step S403, please refer to the optional implementation of step S245 in FIG2e and other related parts in the embodiment involved in FIG2e, which will not be repeated here.

[0508] In some embodiments, the terminal may receive a second message that has been repeatedly sent by the first network element. That is, the terminal may receive one or more second messages.

[0509] In some embodiments, if the first network element does not receive the first message and the timer expires at a predetermined time, the second message is retransmitted.

[0510] Figure 4b is a flowchart illustrating a communication method according to an embodiment of the present disclosure. As shown in Figure 4b, the communication method can be executed by a terminal, and the method includes:

[0511] S411, Get the second message.

[0512] In some embodiments, the terminal obtains the first message sent by the first network element through the second network element.

[0513] In some embodiments, the second message is used to determine whether the user plane status of the terminal is available.

[0514] In some embodiments, the terminal acquiring the second message can be understood as receiving the second message. Optionally, the terminal receives the second message sent by the first network element.

[0515] In some embodiments, the second message may be a user plane connection establishment command message or a user plane availability query message, but the message name is not limited to these.

[0516] For details of the optional implementation of step S411, please refer to the optional implementation of step S210 in FIG2b and other related parts in the embodiment involved in FIG2b, which will not be repeated here.

[0517] S412, Send the third message.

[0518] In some embodiments, the terminal sends a third message to the first network element.

[0519] In some embodiments, the third message is used to notify the first network element that the user plane status of the terminal is unavailable.

[0520] In some embodiments, the third message may include information indicating that the end-user plane is unavailable.

[0521] In some embodiments, the third message may be a response message to the second message.

[0522] In some embodiments, the third message includes a first value of the timer.

[0523] For details of the optional implementation of step S412, please refer to the optional implementation of step S211 in FIG2b and other related parts in the embodiment involved in FIG2b, which will not be repeated here.

[0524] Figure 4c is a flowchart illustrating a communication method according to an embodiment of the present disclosure. As shown in Figure 4c, the communication method can be executed by a terminal, and the method includes:

[0525] S421, Send message.

[0526] In some embodiments, the terminal sends a message to the first network element. Optionally, the message is used to notify the first network element whether the user plane of the terminal is available.

[0527] In some embodiments, the terminal sends a message to the first network element through the second network element. Optionally, the message is used to notify the first network element whether the user plane of the terminal is available.

[0528] In some embodiments, the above message includes a third message. Optionally, the third message is used to notify the first network element that the user plane of the terminal is unavailable.

[0529] In some embodiments, the third message includes a first value of a timer, which is started by the first network element when the user plane of the terminal is unavailable, and the value of the timer is set by the first network element to the first value included in the third message.

[0530] In some embodiments, the above message includes a first message, which optionally is used to notify the first network element that the user plane of the terminal is available.

[0531] In some embodiments, the method further includes: receiving at least one second message sent by the first network element. Optionally, the second message is used to determine whether the user plane of the terminal is available.

[0532] In some embodiments, if the first network element does not receive the first message and the timer expires at a predetermined time, the second message is retransmitted.

[0533] In some embodiments, sending a message to the first network element includes: in response to the second message, sending the message to the first network element.

[0534] This application also provides an optional embodiment, in which the solution may include at least one of the steps shown in FIG5:

[0535] S501. The user plane of the UE is unavailable. For example, the UE's 3GPP PS data shutdown status is "active" and LCS-UPP is not configured as part of the 3GPP PS data shutdown exemption list.

[0536] S502, the UE reports its "user plane unavailable" status to the LMF through the AMF.

[0537] S502a. If the UE and LMF maintain a secure LCS user plane connection, the UE sends a user plane connection release request message to the LMF through the AMF. This message may include a fault reason IE set to "user plane unavailable". Optionally, the message may also include a timer value.

[0538] In some embodiments, the timer value can be used for a timer in the LMF (e.g., for timer T5015).

[0539] In some embodiments, the LMF should consider starting a timer when the user plane of the UE is unavailable.

[0540] In some embodiments, UE->AMF: UL NAS TRANSPORT (User plane connection release request (User plane unavailable, timer value)); AMF->LMF: Namf_Communication_N1MessageNotify (User plane connection release request (User plane unavailable, timer value)).

[0541] S502b. If the UE and LMF do not maintain a secure LCS user plane connection: If the LMF receives a location request and determines that it will use LCS-UPP for the location request, the LMF sends a user plane connection establishment command message to the UE via the AMF. The UE sends a user plane connection establishment failure message to the LMF. Since the user plane is unavailable, this message may include a failure reason IE set to "user plane unavailable". Optionally, this message may also include a timer value.

[0542] In some embodiments, step S502b may include S502b-1: The LMF sends a user plane connection establishment command message to the UE through the AMF.

[0543] Optionally, S502b-1 may specifically include:

[0544] LMF->AMF: Namf_Communication_N1N2MessageTransfer (User plane connection establishment command);

[0545] AMF->UE: DL NAS TRANSPORT (User plane connection establishment command).

[0546] In some embodiments, step S502b may include S502b-2: the UE sends a user plane connection establishment failure message to the LMF through the AMF.

[0547] Optionally, S502b-2 may specifically include:

[0548] UE->AMF: UL NAS TRANSPORT (User plane connection establishment failed (user plane unavailable, timer value));

[0549] AMF->LMF: Namf_Communication_N1MessageNotify(User plane connection establishment failed (user plane unavailable, timer value)).

[0550] After receiving the "User plane unavailable" message, S503 and LMF should start a timer (e.g., timer T5015).

[0551] In some embodiments, the LMF does not execute the user plane connection establishment process initiated by the LMF until the timer expires or stops.

[0552] In some embodiments, if the user plane connection establishment failure message or user plane connection release request message does not include a timer value, or the UE does not provide a timer value to the LMF, the LMF should set the timer value to a specific value or a preset value, which may be provided according to the implementation.

[0553] In some embodiments, if a user plane connection establishment failure message or user plane connection release request message includes a timer value, the LMF should start the timer using the value provided in the timer value IE when it determines "user plane unavailable" based on the received message.

[0554] In some embodiments, if the LMF receives a positioning request during timer operation, the LMF should not consider the LCS-UPP positioning request, but may consider the control plane positioning method instead.

[0555] S504. When the LMF detects that the UE's user plane (or user plane availability status) is available, stop the timer.

[0556] In some embodiments, step S504 may include S504a, whereby the UE may notify the LMF of its user plane availability status via a user plane connection establishment request message (or a new message, such as a user plane connection availability notification message).

[0557] Optionally, step S504a may include S504a-1, the UE's user plane is available (or the user plane is available state), and the UE sends a user plane connection establishment request message to the LMF.

[0558] In some embodiments, the UE may send the above message in the following circumstances:

[0559] -User plane of UE is available;

[0560] - User plane is available. The UE receives a location request and decides to request an LCS-UPP location request.

[0561] In some embodiments, step S504a-1 may specifically include: the UE sending a user plane connection establishment request to the LMF through the AMF.

[0562] In some embodiments, step S504a-1 may specifically include: UE->AMF:UL NAS TRANSPORT (User Plane Connection Establishment Request);

[0563] AMF->LMF:Namf_Communication_N1MessageNotify(User plane connection establishment request).

[0564] In some embodiments, in addition to the user plane connection establishment request message from the UE, the LMF may also determine whether to consider the user plane through other possible methods:

[0565] - The AMF notifies the LMF that the user plane of the UE is available (e.g., via a Namf_EventExposure_Notify message, and requires a previous Namf_EventExposure_Subscribe message from the LMF to the AMF for subscribing to events);

[0566] - The SMF notifies the LMF that the user plane of the UE is available (e.g., via the Nsmf_EventExposure_Notify message, and requires the Nsmf_EventsExposure_Subscribe message from the LMF to the SMF for subscribing to events);

[0567] Optionally, step S504a may include S504a-2, receiving a user plane connection establishment request message (or user plane connection availability notification message) from the UE, or receiving other notification messages from the AMF or SMF as described above, in which case the LMF should stop the timer and determine that the user plane availability is available.

[0568] In some embodiments, if the LMF receives a location request and the timer is not running, the LMF may consider using LCS-UPP for the location request.

[0569] It should be noted that the above steps S504a-1 and S504a-2 can occur in any step before step S507b.

[0570] In some embodiments, step S504 may include S504b, in which if no message indicating that the user plane is available is received (e.g., the message in step S504a-1), the timer will continue to run until it expires.

[0571] S505 and LMF should resend the user plane connection establishment command message (or send a user plane availability query message) and reset and start the timer when the timer first expires (or at other specific expiration times).

[0572] In some embodiments, the above message is sent a maximum of four times (or other preset values). That is, when the timer expires for the fifth time (a specific expiration time), the LMF should consider that the user plane availability state of the UE is always unavailable (and LCS-UPP is always unavailable), and may not use LCS-UPP for any LCS request of the UE.

[0573] In some embodiments, the LMF sends a user plane connection establishment command message to the UE through the AMF, specifically:

[0574] LMF->AMF: Namf_Communication_N1N2MessageTransfer (User plane connection establishment command);

[0575] AMF->UE:DL NAS TRANSPORT (User plane connection establishment command).

[0576] S506a, the user plane availability status of the UE is available.

[0577] In some embodiments, in step S505, the UE receives a user plane availability status query message from the LMF. The UE sends a user plane connection establishment request message or a user plane connection availability notification message to notify the LMF of its user plane availability status.

[0578] In some embodiments, in step S505, the UE receives a user plane connection establishment command message from the LMF. The UE and the LMF execute a network-initiated user plane connection establishment process, and the UE sends a user plane connection establishment completion message or an LCS-UP connection binding request message through the user plane to notify the LMF of its user plane availability status.

[0579] Optionally, the UE sends a user plane connection establishment completion message to the LMF via the AMF, specifically:

[0580] UE->AMF: UL NAS TRANSPORT (User plane connection established);

[0581] AMF->LMF: Namf_Communication_N1MessageNotify (User plane connection established).

[0582] Optionally, the UE sends an LCS-UP connection binding request message to the LMF, specifically: UE->LMF: LCS-UP connection binding request.

[0583] In some embodiments, if the LMF receives any message indicating that the user plane is available, the LMF should stop the timer and assume that the user plane is available.

[0584] When S507a and LMF receive the message from step S506a, they should stop the timer and consider the availability of the user plane.

[0585] S506b. If the LMF does not receive a message indicating that the user plane is available (only a user plane connection establishment failure message is received), the timer runs until it expires.

[0586] S507b: When the timer expires for the fifth time (at a specific expiration time), the LMF should consider that the UE's user plane availability state has always been unavailable (and LCS-UPP has always been unavailable), and may not use LCS-UPP for any LCS requests of the UE.

[0587] The timer in the above embodiments can be the timer defined in the following table:

[0588] This disclosure also provides an apparatus for implementing any of the above methods. For example, an apparatus is provided that includes units or modules for implementing the steps performed by the terminal in any of the above methods. Alternatively, another apparatus is provided that includes units or modules for implementing the steps performed by a network device (e.g., an access network device, a core network functional node, a core network device, etc.) in any of the above methods.

[0589] It should be understood that the division of units or modules in the above device is only a logical functional division. In actual implementation, they can be fully or partially integrated into a single physical entity, or they can be physically separated. Furthermore, the units or modules in the device can be implemented by a processor calling software: for example, the device includes a processor connected to a memory containing instructions. The processor calls the instructions stored in the memory to implement any of the above methods or to implement the functions of the units or modules in the above device. The processor can be, for example, a general-purpose processor, such as a Central Processing Unit (CPU) or a microprocessor, and the memory can be internal or external to the device. Alternatively, the units or modules in the device can be implemented in the form of hardware circuits. The functions of some or all of the units or modules can be achieved through the design of the hardware circuits. The aforementioned hardware circuits can be understood as one or more processors. For example, in one implementation, the aforementioned hardware circuit is an application-specific integrated circuit (ASIC). The functions of some or all of the aforementioned units or modules are achieved through the design of the logical relationships between the components within the circuit. As another example, in another implementation, the aforementioned hardware circuit can be implemented through a programmable logic device (PLD). Taking a field-programmable gate array (FPGA) as an example, it can include a large number of logic gates. The connection relationships between the logic gates are configured through configuration files, thereby achieving the functions of some or all of the aforementioned units or modules.

[0590] All units or modules of the above devices can be implemented entirely through processor-invoked software, entirely through hardware circuits, or partially through processor-invoked software with the remainder implemented through hardware circuits. In this embodiment, the processor is a circuit with signal processing capabilities. In one implementation, the processor can be a circuit with instruction read and execute 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 relationships of hardware circuits. These logical relationships are fixed or reconfigurable. For example, the processor may be a hardware circuit implemented using an application-specific integrated circuit (ASIC) or a programmable logic device (PLD), such as an FPGA. In a reconfigurable hardware circuit, the process of the processor loading a configuration document and configuring the hardware circuit 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 hardware circuits designed for artificial intelligence, which can be understood as ASICs, such as Neural Network Processing Units (NPUs), Tensor Processing Units (TPUs), and Deep Learning Processing Units (DPUs).

[0591] Figure 6a is a schematic diagram of the structure of the first network element proposed in an embodiment of this disclosure. As shown in Figure 6a, the first network element may include at least one of a first transceiver module 611, a first processing module 612, etc.

[0592] In some embodiments, the first processing module 612 is used to start a timer when it determines that the user plane of the terminal is unavailable; the user plane connection establishment process with the terminal is not triggered before the timer expires or stops.

[0593] Optionally, the first transceiver module 611 is used to execute the steps related to transmitting and receiving signaling executed by the first network element in any of the above methods, such as at least one of the following: step S201 shown in FIG2a, steps S210, S211, S214 shown in FIG2b, steps S221, S223 shown in FIG2c, steps S230, S231, S232, S234, S235 shown in FIG2d, and steps S241, S244, S245 shown in FIG2e, which will not be described in detail here.

[0594] Optionally, the first processing module 612 is also used to execute information processing-related steps performed by the first network element in any of the above methods, such as at least one of steps S214 and S215 shown in FIG2b, step S224 shown in FIG2c, step S234 and S236 shown in FIG2d, and step S246 shown in FIG2e, which will not be described in detail here.

[0595] Figure 6b is a schematic diagram of the structure of a terminal according to an embodiment of this disclosure. As shown in Figure 6b, the terminal includes at least one of a second transceiver module 621, a second processing module 622, etc.

[0596] In some embodiments, the second transceiver module 621 is used to send a message to the first network element, the message being used to notify the first network element whether the user plane status of the terminal is available.

[0597] Optionally, the second transceiver module 621 described above is used to execute the steps related to sending and receiving signaling executed by the terminal in any of the above methods, such as: at least one of the following: step S201 shown in FIG2a, steps S210, S211, S214 shown in FIG2b, steps S221, S223a shown in FIG2c, steps S230, S231, S232, S234, S235a shown in FIG2d, and steps S241, S244, S245a shown in FIG2e, which will not be described in detail here.

[0598] Figure 7a is a schematic diagram of the structure of the communication device 7100 proposed in an embodiment of this disclosure. The communication device 7100 can be a network device (e.g., access network device, core network device, etc.), a terminal (e.g., user equipment, etc.), a chip, chip system, or processor that supports the network device in implementing any of the above methods, or a chip, chip system, or processor that supports the terminal in implementing any of the above methods. The communication device 7100 can be used to implement the methods described in the above method embodiments; for details, please refer to the descriptions in the above method embodiments.

[0599] As shown in Figure 7a, the communication device 7100 includes one or more processors 7101. The processor 7101 can be a general-purpose processor or a dedicated processor, such as a baseband processor or a central processing unit (CPU). The baseband processor can be used to process communication protocols and communication data, while the CPU can be used to control communication devices (e.g., base stations, baseband chips, terminal devices, terminal device chips, DUs or CUs, etc.), execute programs, and process program data. The processor 7101 is used to invoke instructions to cause the communication device 7100 to execute any of the above methods.

[0600] In some embodiments, the communication device 7100 further includes one or more transceivers 7103. When the communication device 7100 includes one or more transceivers 7103, the transceivers 7103 perform communication steps such as sending and / or receiving in the above-described method (for example, steps S201 shown in FIG. 2a, steps S210, S211, S214 shown in FIG. 2b, steps S221, S223 shown in FIG. 2c, steps S230, S231, S232, S234, S235 shown in FIG. 2d, and steps S241, S244, S245 shown in FIG. 2e). At least one of the following steps (but not limited to): processor 7101 executes at least one of the following steps: steps S202 and S203 shown in FIG. 2a, steps S212, S213, S214 and S215 shown in FIG. 2b, steps S222 and S224 shown in FIG. 2c, steps S232, S233, S234 and S236 shown in FIG. 2d, and steps S242, S243 and S246 shown in FIG. 2e, but not limited to. In optional embodiments, the transceiver may include a receiver and / or a transmitter, which may be separate or integrated. Optionally, the terms transceiver, transceiver unit, transceiver, transceiver circuit, interface circuit, interface, etc., can be used interchangeably; the terms transmitter, transmitting unit, transmitter, transmitting circuit, etc., can be used interchangeably; and the terms receiver, receiving unit, receiver, receiving circuit, etc., can be used interchangeably.

[0601] In some embodiments, the communication device 7100 further includes one or more memories 7102 for storing instructions. Optionally, all or part of the memories 7102 may also be located outside the communication device 7100.

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

[0603] Optionally, the communication device 7100 further includes one or more interface circuits 7104, which are connected to the memory 7102. The interface circuits 7104 can be used to receive signals from the memory 7102 or other devices, and can be used to send signals to the memory 7102 or other devices. For example, the interface circuits 7104 can read instructions stored in the memory 7102 and send the instructions to the processor 7101.

[0604] The communication device 7100 described in the above embodiments may be a network device or a terminal, but the scope of the communication device 7100 described in this disclosure is not limited thereto, and the structure of the communication device 7100 may not be limited by FIG. 7a. 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 chip, or chip system or subsystem; (2) a collection of one or more ICs, optionally, the IC collection may also include storage components for storing data and programs; (3) an ASIC, such as a modem; (4) a module that can be embedded in other devices; (5) a receiver, terminal device, smart terminal device, cellular phone, wireless device, handheld device, mobile unit, vehicle device, network device, cloud device, artificial intelligence device, etc.; (6) others, etc.

[0605] Figure 7b is a schematic diagram of the structure of the chip 7200 proposed in an embodiment of this disclosure. For cases where the communication device 7100 can be a chip or a chip system, please refer to the schematic diagram of the chip 7200 shown in Figure 7b, but it is not limited thereto.

[0606] Chip 7200 includes one or more processors 7201. Chip 7200 is used to perform any of the above methods.

[0607] In some embodiments, chip 7200 further includes one or more interface circuits 7202. Optionally, terms such as interface circuit, interface, and transceiver pin can be used interchangeably. In some embodiments, chip 7200 further includes one or more memories 7203 for storing data. Optionally, all or part of the memories 7203 may be located outside of chip 7200. Optionally, interface circuit 7202 is connected to memory 7203, and interface circuit 7202 can be used to receive data from memory 7203 or other devices, and interface circuit 7202 can be used to send data to memory 7203 or other devices. For example, interface circuit 7202 can read data stored in memory 7203 and send the data to processor 7201.

[0608] In some embodiments, the interface circuit 7202 performs at least one of the communication steps such as sending and / or receiving in the above-described method (e.g., at least one of steps S201 shown in FIG. 2a, S210, S211, S214 shown in FIG. 2b, S221, S223 shown in FIG. 2c, S230, S231, S232, S234, S235 shown in FIG. 2d, and S241, S244, S245 shown in FIG. 2e, but not limited thereto). The interface circuit 7202 performing the communication steps such as sending and / or receiving in the above-described method refers, for example, to the interface circuit 7202 performing data interaction between the processor 7201, the chip 7200, the memory 7203, or the transceiver device. In some embodiments, the processor 7201 performs at least one of other steps (e.g., at least one of steps S202 and S203 shown in FIG. 2a, steps S212, S213, S214 and S215 shown in FIG. 2b, steps S222 and S224 shown in FIG. 2c, steps S232, S233, S234 and S236 shown in FIG. 2d, and steps S242, S243 and S246 shown in FIG. 2e, but not limited thereto).

[0609] This disclosure also provides a program product that, when executed by the communication device 7100, causes the communication device 7100 to perform any of the above methods. Optionally, the program product is a computer program product.

[0610] This disclosure also proposes a computer program that, when run on a computer, causes the computer to perform any of the above methods.

[0611] The technical solutions described in the embodiments of this disclosure can be combined arbitrarily without conflict.

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

[0613] It should be understood that the present invention is not limited to the precise structure described above and shown in the accompanying drawings, and various modifications and changes can be made without departing from its scope. The scope of the invention is limited only by the appended claims.

Claims

1. A communication method, characterized in that, The method is executed by a first network element, and the method includes: When the user plane status of the terminal is determined to be unavailable, start the timer; The user plane connection establishment process with the terminal will not be triggered until the timer expires or stops.

2. The method according to claim 1, characterized in that, The method further includes: During the operation of the timer, a control plane-related method is determined for the first service of the terminal.

3. The method according to claim 1, characterized in that, The method further includes: If the user plane of the terminal is determined to be available, the timer is stopped; otherwise, the timer runs until it expires.

4. The method according to claim 3, characterized in that, The method further includes: Receive a first message, the first message being used to notify the terminal that the user plane is available; Based on the first message, the user plane status of the terminal is determined to be available.

5. The method according to claim 4, characterized in that, The method further includes: A second message is sent to the terminal, the second message being used to determine whether the user plane of the terminal is available.

6. The method according to claim 5, characterized in that, The method further includes: If the first message is not received and the timer expires at the predetermined time, the second message is resent to the terminal, and the timer is restarted.

7. The method according to claim 6, characterized in that, The method further includes: If the number of timer restarts exceeds a preset value, the user plane status of the terminal is determined to be unavailable, and user plane-related methods are not applied to the first service of the terminal.

8. The method according to claim 2 or 7, characterized in that, The first service includes at least one of the following: Perceive business; Location services; Ranging / sidechain positioning services.

9. The method according to claim 2 or 8, characterized in that, The control plane-related methods include at least one of the following: Control surface perception method; Control surface positioning method; Control surface ranging / side chain positioning method.

10. The method according to claim 7 or 8, characterized in that, The user-plane related methods include at least one of the following: User-face perception methods; User plane positioning method; User face ranging / side chain positioning method.

11. The method according to any one of claims 1-10, characterized in that, The method further includes: Receive a third message from the terminal, the third message being used to notify the terminal that the user plane is unavailable; Based on the third message, it is determined that the user plane of the terminal is unavailable.

12. The method according to claim 11, characterized in that, The third message includes a first value of the timer, and the method further includes: Set the value of the timer to the first value included in the third message.

13. The method according to any one of claims 1-10, characterized in that, The timer value is a predetermined duration.

14. A communication method, characterized in that, The method is executed by a terminal, and the method includes: A message is sent to the first network element, the message being used to notify the first network element whether the user plane of the terminal is available.

15. The method according to claim 14, characterized in that, The message includes a third message, which is used to notify the first network element that the user plane of the terminal is unavailable.

16. The method according to claim 12, characterized in that, The third message includes a first value of a timer, which is started by the first network element when the user plane of the terminal is unavailable, and the value of the timer is set by the first network element to the first value included in the third message.

17. The method according to claim 14, characterized in that, The message includes: a first message, which is used to notify the first network element that the user plane of the terminal is available.

18. The method according to any one of claims 14-17, characterized in that, The method further includes: The system receives at least one second message sent by the first network element, wherein the second message is used to determine whether the user plane status of the terminal is available.

19. The method according to claim 18, characterized in that, If the first network element does not receive the first message and the timer expires at the predetermined time, the second message is retransmitted.

20. The method according to claim 18, characterized in that, Sending a message to the first network element includes: In response to the second message, the message is sent to the first network element.

21. A first network element, characterized in that, include: The first processing module is used to start a timer when it determines that the user plane of the terminal is unavailable. The user plane connection establishment process with the terminal will not be triggered until the timer expires or stops.

22. A terminal, characterized in that, include: The second transceiver module is used to send a message to the first network element, the message being used to notify the first network element whether the user plane status of the terminal is available.

23. A communication device, characterized in that, include: One or more processors; The processor is used to execute the communication method according to any one of claims 1 to 13.

24. A communication device, characterized in that, include: One or more processors; The processor is used to execute the communication method according to any one of claims 14 to 20.

25. A communication system, characterized in that, include: The first network element and the terminal, wherein the terminal is used to implement the method of any one of claims 14 to 20, and the first network element is used to implement the method of any one of claims 1 to 13.

26. A computer storage medium, characterized in that, The computer-readable storage medium stores executable instructions that are loaded and executed by a processor to implement the method as described in any one of claims 1 to 13 or 14 to 20.

Images