Connection management method and device, terminal and network side equipment

Abstract

The invention discloses a connection management method and device, a terminal and network side equipment, and belongs to the technical field of communication, and the connection management method comprises the steps that in the process of establishing user plane connection between the network side equipment and the terminal, if a first condition is met, the network side equipment executes first operation; wherein the first condition comprises at least one of the following items: the first timer is overtime, and the first timer is associated with at least one of the following items: a first connection identifier, a terminal identifier of the terminal, a binding process of the terminal and an establishment process of user plane connection; the first connection identifier is not in the effective time; the first operation comprises at least one of the following items: releasing the first connection identifier; releasing the user plane connection; sending a first message to the terminal, wherein the first message is used for indicating the terminal to reestablish the user plane connection with the network side equipment; and replacing the positioning protocol scheme.

Description

Technical Field

[0001] This application belongs to the field of communication technology, specifically relating to a connection management method, apparatus, terminal, and network-side equipment. Background Technology

[0002] Currently, after receiving a connection identifier assigned by the Location Management Function (LMF), the terminal can use the connection identifier to initiate a binding (or association) via user plane messages, so that the LMF can determine which terminal the user plane connection corresponding to the connection identifier belongs to.

[0003] However, if the terminal fails to initiate binding after receiving the connection identifier, or the binding fails, or if it does not receive a response from the network device after initiating binding, and the terminal does not notify the network device, the connection identifier may be invalidally occupied for a long time, which will prevent the network device from allocating the connection identifier and lead to a waste of resources. Summary of the Invention

[0004] This application provides a connection management method, apparatus, terminal, and network-side device that enables the network-side device to reallocate invalidally occupied connection identifiers, thereby saving resources.

[0005] In a first aspect, a connection management method is provided, executed by a network-side device. The method includes: during the process of establishing a user plane connection between the network-side device and a terminal, if a first condition is met, the network-side device performs a first operation; wherein the first condition includes at least one of the following: a first timer times out, the first timer being associated with at least one of the following: a first connection identifier, a terminal identifier of the terminal, a terminal binding process, and a user plane connection establishment process; the first connection identifier is not within a valid time period; the first operation includes at least one of the following: releasing the first connection identifier; releasing the user plane connection; sending a first message to the terminal, the first message instructing the terminal to re-establish a user plane connection with the network-side device; and changing the positioning protocol scheme.

[0006] Secondly, a connection management method is provided, executed by a terminal. This method includes: during the process of establishing a user plane connection between a network-side device and the terminal, if a second condition is met, the terminal performs a second operation; wherein the second condition includes at least one of the following: a second timer expires, the second timer being associated with at least one of the following: a first connection identifier, the initiation of a terminal binding process; a third timer expires, the third timer being associated with at least one of the following: a first connection identifier, the terminal binding process, the establishment process of a user plane connection; the first connection identifier is not within its valid time; the second operation includes at least one of the following: sending a binding request message to the network-side device; releasing the first connection identifier; releasing the user plane connection; sending a third message to the network-side device, the third message indicating that the establishment of the user plane connection failed; changing the positioning protocol scheme.

[0007] Thirdly, a connection management device is provided, comprising a first processing module; the first processing module is configured to perform a first operation if a first condition is met during the process of establishing a user plane connection between a network-side device and a terminal; wherein the first condition includes at least one of the following: a first timer times out, the first timer being associated with at least one of the following: a first connection identifier, a terminal identifier of the terminal, a binding process of the terminal, and a user plane connection establishment process; the first connection identifier is not within a valid time period; the first operation includes at least one of the following: releasing the first connection identifier; releasing the user plane connection; sending a first message to the terminal, the first message being used to instruct the terminal to re-establish a user plane connection with the network-side device; and changing the positioning protocol scheme.

[0008] Fourthly, a connection management device is provided, comprising a second processing module; the second processing module is configured to perform a second operation if a second condition is met during the process of establishing a user plane connection between a network-side device and a terminal; wherein the second condition includes at least one of the following: a second timer expires, the second timer being associated with at least one of the following: a first connection identifier, the initiation of a terminal binding process; a third timer expires, the third timer being associated with at least one of the following: a first connection identifier, the terminal binding process, the establishment process of a user plane connection; the first connection identifier is not within a valid time period; the second operation includes at least one of the following: sending a binding request message to the network-side device; releasing the first connection identifier; releasing the user plane connection; sending a third message to the network-side device, the third message indicating that the establishment of the user plane connection failed; changing the positioning protocol scheme.

[0009] Fifthly, a connection management device is provided, the device being configured to perform the steps of the method described in the first aspect, or to implement the steps of the method described in the second aspect.

[0010] In a sixth aspect, a network-side device is provided, the network-side device including a processor and a memory, the memory storing a program or instructions executable on the processor, the program or instructions, when executed by the processor, implementing the steps of the method as described in the first aspect.

[0011] In a seventh aspect, a network-side device is provided, including a processor and a communication interface, wherein the processor is configured to perform a first operation if a first condition is met during the process of establishing a user plane connection between the network-side device and a terminal; wherein the first condition includes at least one of the following: a first timer times out, the first timer being associated with at least one of the following: a first connection identifier, a terminal identifier of the terminal, a binding process of the terminal, and a user plane connection establishment process; the first connection identifier is not within a valid time period; the first operation includes at least one of the following: releasing the first connection identifier; releasing the user plane connection; sending a first message to the terminal, the first message being used to instruct the terminal to re-establish a user plane connection with the network-side device; and changing the positioning protocol scheme.

[0012] Eighthly, a terminal is provided, the terminal including a processor and a memory, the memory storing a program or instructions executable on the processor, the program or instructions, when executed by the processor, implementing the steps of the method as described in the second aspect.

[0013] A ninth aspect provides a terminal, including a processor and a communication interface, wherein the processor is configured to perform a second operation during the process of establishing a user plane connection between a network-side device and the terminal, if a second condition is met; wherein the second condition includes at least one of the following: a second timer times out, the second timer being associated with at least one of the following: a first connection identifier, the initiation of a terminal binding process; a third timer times out, the third timer being associated with at least one of the following: a first connection identifier, the terminal binding process, the user plane connection establishment process; the first connection identifier not being within a valid time period; the second operation includes at least one of the following: sending a binding request message to the network-side device; releasing the first connection identifier; releasing the user plane connection; sending a third message to the network-side device, the third message indicating that the establishment of the user plane connection failed; changing the positioning protocol scheme.

[0014] In a tenth aspect, a readable storage medium is provided, on which a program or instructions are stored, which, when executed by a processor, implement the steps of the method described in the first aspect, or implement the steps of the method described in the second aspect.

[0015] Eleventhly, a wireless communication system is provided, comprising: a terminal and a network-side device, wherein the network-side device can be used to perform the steps of the method as described in the first aspect, and the terminal can be used to perform the steps of the method as described in the second aspect.

[0016] In a twelfth aspect, a chip is provided, the chip including a processor and a communication interface coupled to the processor, the processor being configured to run programs or instructions to implement the method as described in the first aspect, or to implement the method as described in the second aspect.

[0017] In a thirteenth aspect, a computer program / program product is provided, which is stored in a storage medium and is executed by at least one processor to implement the steps of the method as described in the first aspect, or to implement the steps of the method as described in the second aspect.

[0018] In this embodiment, during the establishment of a user plane connection between the network-side device and the terminal, if a first condition is met, the network-side device performs a first operation. The first condition includes at least one of the following: a first timer times out, and the first timer is associated with at least one of the following: a first connection identifier, a terminal identifier of the terminal, the terminal binding process, and the user plane connection establishment process; the first connection identifier is not within its valid time period. The first operation includes at least one of the following: releasing the first connection identifier; releasing the user plane connection; sending a first message to the terminal, the first message instructing the terminal to re-establish the user plane connection with the network-side device; and changing the positioning protocol scheme. Through this scheme, since the network-side device can perform at least one of the following actions during the establishment of a user plane connection between the network-side device and the terminal when the first timer times out or the first connection identifier is not within its valid time period: releasing the first connection identifier, releasing the user plane connection, sending a first message to the terminal instructing the re-establishment of the user plane connection, and changing the positioning protocol scheme, it can avoid the terminal from ineffectively occupying the first connection identifier for a long time, allowing the network-side device to reallocate the first connection identifier, thereby saving resources. Attached Figure Description

[0019] Figure 1 This is a block diagram of a wireless communication system applicable to embodiments of this application;

[0020] Figure 2 This is a flowchart of establishing a user plane connection in related technologies;

[0021] Figure 3 This is a flowchart of a connection management method provided in an embodiment of this application;

[0022] Figure 4 This is one of the flowcharts for establishing a user plane connection in a connection management method provided in an embodiment of this application;

[0023] Figure 5 This is a flowchart of another connection management method provided in the embodiments of this application;

[0024] Figure 6This is the second flowchart of establishing a user plane connection in a connection management method provided in this application embodiment;

[0025] Figure 7 This is the third flowchart of a connection management method for establishing a user plane connection provided in an embodiment of this application;

[0026] Figure 8 This is a schematic diagram of the structure of a connection management device provided in an embodiment of this application;

[0027] Figure 9 This is a schematic diagram of another connection management device provided in an embodiment of this application;

[0028] Figure 10 This is a schematic diagram of the communication device provided in an embodiment of this application;

[0029] Figure 11 This is a schematic diagram of the hardware structure of the terminal provided in the embodiments of this application;

[0030] Figure 12 This is a schematic diagram of the hardware structure of the network-side device provided in the embodiments of this application. Detailed Implementation

[0031] The technical solutions of the embodiments of this application will be clearly described below with reference to the accompanying drawings. Obviously, the described embodiments are only some, not all, of the embodiments of this application. All other embodiments obtained by those skilled in the art based on the embodiments of this application are within the scope of protection of this application.

[0032] The terms "first," "second," etc., used in this application are used to distinguish similar objects and not to describe a specific order or sequence. It should be understood that such terms can be used interchangeably where appropriate so that embodiments of this application can be implemented in orders other than those illustrated or described herein, and the objects distinguished by "first" and "second" are generally of the same class, not limited in number; for example, the first object can be one or more. Furthermore, "or" in this application indicates at least one of the connected objects. For example, the scope of protection for "A or B" covers at least three scenarios: Scenario 1: including A but not B; Scenario 2: including B but not A; Scenario 3: including both A and B. In addition, the terms "A and / or B," "at least one of A and B," and "at least one of A or B" also cover at least the above three scenarios. The character " / " generally indicates that the preceding and following objects are in an "or" relationship.

[0033] The term "instruction" in this application can be either a direct instruction (or explicit instruction) or an indirect instruction (or implicit instruction). A direct instruction can be understood as one in which the sender explicitly informs the receiver of specific information, the operation to be performed, or the requested result, etc., in the instruction sent. An indirect instruction can be understood as one in which the receiver determines the corresponding information based on the instruction sent by the sender, or makes a judgment and determines the operation to be performed or the requested result, etc., based on the judgment result.

[0034] It is worth noting that the technologies described in this application are not limited to Long Term Evolution (LTE) / LTE-Advanced (LTE-A) systems, but can also be used in other wireless communication systems, such as Code Division Multiple Access (CDMA), Time Division Multiple Access (TDMA), Frequency Division Multiple Access (FDMA), Orthogonal Frequency Division Multiple Access (OFDMA), Single-carrier Frequency-Division Multiple Access (SC-FDMA), or other systems. The terms "system" and "network" in this application are often used interchangeably, and the described technologies can be used with the systems and radio technologies mentioned above, as well as with other systems and radio technologies. The following description describes New Radio (NR) systems for illustrative purposes, and the term NR is used in most of the following description; however, these technologies can also be applied to systems other than NR systems, such as 6th generation (6G) radio systems. th Generation 6G communication system.

[0035] Figure 1This diagram illustrates a block diagram of a wireless communication system applicable to embodiments of this application. The wireless communication system includes a terminal 11 and a network-side device 12. The terminal 11 can be a mobile phone, tablet computer, laptop computer, notebook computer, personal digital assistant (PDA), handheld computer, netbook, ultra-mobile personal computer (UMPC), mobile internet device (MID), augmented reality (AR), virtual reality (VR) device, robot, wearable device, flight vehicle, vehicle user equipment (VUE), shipboard equipment, pedestrian user equipment (PUE), smart home devices (home appliances with wireless communication capabilities, such as refrigerators, televisions, washing machines, or furniture), game consoles, personal computers (PCs), ATMs, or self-service machines, etc. Wearable devices include: smartwatches, smart bracelets, smart headphones, smart glasses, smart jewelry (smart bracelets, smart chains, smart rings, smart necklaces, smart anklets, smart anklets, etc.), smart wristbands, smart clothing, etc. Among these, in-vehicle devices can also be referred to as in-vehicle terminals, in-vehicle controllers, in-vehicle modules, in-vehicle components, in-vehicle chips, or in-vehicle units, etc. It should be noted that the specific type of terminal 11 is not limited in this application embodiment. Network-side equipment 12 may include access network equipment or core network equipment, wherein access network equipment may also be referred to as Radio Access Network (RAN) equipment, radio access network function, or radio access network unit. Access network equipment may include base stations, Wireless Local Area Network (WLAN) access points (AS), or Wireless Fidelity (WiFi) nodes, etc.The term "base station" can be referred to as Node B (NB), Evolved Node B (eNB), Next Generation Node B (gNB), New Radio Node B (NR Node B), Access Point, Relay Base Station (RBS), Serving Base Station (SBS), Base Transceiver Station (BTS), Radio Base Station, Radio Transceiver, Basic Service Set (BSS), Extended Service Set (ESS), Home Node B (HNB), Home Evolved Node B, Transmit / Receive Point (TRP), or any other suitable term in the relevant field, as long as the same technical effect is achieved. The term "base station" is not limited to any specific technical terminology. It should be noted that this application embodiment only uses a base station in an NR system as an example for description and does not limit the specific type of base station.

[0036] Core network equipment, also known as core network nodes, core network functions, or core network elements, includes, but is not limited to, at least one of the following: Mobility Management Entity (MME), Access and Mobility Management Function (AMF), Session Management Function (SMF), User Plane Function (UPF), Policy Control Function (PCF), Policy and Charging Rules Function (PCRF), Edge Application Server Discovery Function (EASDF), Unified Data Management (UDM), Unified Data Repository (UDR), Home Subscriber Server (HSS), Centralized network configuration (CNC), Network Repository Function (NRF), Network Exposure Function (NEF), Local NEF (or L-NEF), and Binding Support Function. Support Functions (BSF), Application Functions (AF), Location Management Functions (LMF), Gateway Mobile Location Centres (GMLC), and Network Data Analytics Functions (NWDAF), etc. It should be noted that this application embodiment only uses core network equipment in the NR system as an example and does not limit the specific type of core network equipment. If the name of the core network equipment mentioned in this application embodiment changes in subsequent protocol versions (e.g., 6G), it will still be within the scope of protection of this application.

[0037] Optionally, the core network equipment can be implemented by one or more functional modules in a single device, or by multiple devices working together; this application does not specifically limit this. It is understood that the aforementioned functional modules can be network elements in hardware devices, software functional modules running on dedicated hardware, or virtualized functional modules instantiated on a platform (e.g., a cloud platform).

[0038] The connection management method, apparatus, terminal, and network-side device provided in this application will be described in detail below with reference to the accompanying drawings and through some embodiments and application scenarios.

[0039] Currently, LMF and terminals can exchange some configuration information through control plane signaling to establish user plane connections and transmit LTE Positioning Protocol (LPP) messages or Location Service (LCS)-SS messages on the user plane. Figure 2 A flowchart for establishing a user plane connection is shown, such as... Figure 2 As shown, the LMF and the terminal can establish a user plane connection through signaling interaction. Figure 2 Based on the illustrated process, step 7 is enhanced as follows: In step 7, the terminal uses the LCS-UP connection identifier received in step 3 to initiate a correlation or binding process via user plane messages, so that the LMF can determine which terminal the user plane connection belongs to.

[0040] It should be noted that, for ease of description, the above association process or binding process will be collectively referred to as binding process or binding in the following text.

[0041] It is unclear whether the terminal initiates binding immediately after receiving a connection identifier (e.g., LCS-UP connection ID) or whether the terminal decides when to initiate binding; furthermore, it is unclear how the LMF supervises the terminal to initiate binding immediately when it is required; and it is also unclear what actions the LMF and the terminal take to manage the connection identifier and the user plane connection (including Transport Layer Security (TLS) connection) from the terminal to the LMF when the terminal fails to initiate binding.

[0042] However, if the terminal does not initiate the binding immediately, or if the LMF does not have a reasonable monitoring mechanism, potential problems include:

[0043] 1. If the terminal fails to initiate the binding process and holds the connection identifier but does not use it, it will affect the LMF's allocation of connection identifiers to new terminals, resulting in a waste of resources.

[0044] 2. If the binding is not completed, the LMF cannot know the association between the user plane connection and the terminal, making it impossible for the LMF and the terminal to use the user plane connection to transmit LPP messages or LCS-SS messages.

[0045] 3. Malicious terminals may blindly guess and bind to the connections of other terminals, or other terminals may mistakenly use the connection identifier of normal terminals, occupying the user name location communication channel of normal terminals. This can lead to the transmission of incorrect location information, causing terminal location reporting errors and affecting the use of normal terminals.

[0046] To address the aforementioned issues, embodiments of this application provide a connection management method, apparatus, terminal, and network-side device. The connection management method provided in this application can be applied to scenarios where a network-side device and a terminal establish a user plane connection.

[0047] In the connection management method provided in this application embodiment, during the process of establishing a user plane connection between the network-side device and the terminal, if a first condition is met, the network-side device performs a first operation. The first condition includes at least one of the following: a first timer times out, and the first timer is associated with at least one of the following: a first connection identifier, a terminal identifier of the terminal, the terminal binding process, and the user plane connection establishment process; the first connection identifier is not within its valid time period. The first operation includes at least one of the following: releasing the first connection identifier; releasing the user plane connection; sending a first message to the terminal, the first message instructing the terminal to re-establish the user plane connection with the network-side device; and changing the positioning protocol scheme. Through this scheme, since the network-side device can perform at least one of the following actions during the process of establishing a user plane connection between the network-side device and the terminal when the first timer times out or the first connection identifier is not within its valid time period: releasing the first connection identifier, releasing the user plane connection, sending a first message to the terminal instructing the re-establishment of the user plane connection, and changing the positioning protocol scheme, it can avoid the terminal from ineffectively occupying the first connection identifier for a long time, allowing the network-side device to reallocate the first connection identifier, thereby saving resources.

[0048] Furthermore, the terminal can be required to initiate the binding as soon as possible during the operation of the first timer or the validity period of the first connection identifier, so that after the LMF and the terminal complete the binding, they can use the user plane connection to transmit LPP messages or LCS-SS messages; at the same time, it can also prevent malicious terminals from blindly guessing the connection of other terminals and binding, or other terminals from misusing the connection identifier of normal terminals, so that the terminal location reporting is accurate and does not affect the use of normal terminals.

[0049] This application provides a connection management method. Figure 3 A flowchart illustrating the connection management method provided in an embodiment of this application is shown. Figure 3As shown, the connection management method provided in this application embodiment may include the following step 301.

[0050] Step 301: During the process of establishing a user plane connection between the network-side device and the terminal, if the first condition is met, the network-side device performs the first operation.

[0051] The first condition mentioned above includes at least one of the following:

[0052] The first timer expires, and the first timer is associated with at least one of the following: the first connection identifier, the terminal identifier of the terminal, the terminal binding process, and the user plane connection establishment process;

[0053] The first connection identifier is not within its valid time period;

[0054] The first operation mentioned above includes at least one of the following:

[0055] Release the first connection identifier;

[0056] Release the user plane connection;

[0057] Send a first message to the terminal, which instructs the terminal to re-establish the user plane connection with the network-side device;

[0058] Change the positioning protocol scheme.

[0059] Optionally, in the embodiments of this application, the network-side device can be a device with location management function, such as an LMF.

[0060] Optionally, in this embodiment of the application, the first message may include the LMF LCS-UP address.

[0061] It should be noted that establishing a user plane connection between the terminal and the LMF includes: establishing a Packet Data Unit Session (PDU) session, establishing a TLS connection between the terminal and the LMF, and binding the user plane connection. The aforementioned re-establishment of the user plane connection with the network-side device can refer to: re-establishing all aspects including the PDU session, TLS connection, and binding; or, if the PDU session has not been released, the terminal only needs to rebuild the TLS connection and re-execute the binding process; or, if the PDU session has not been released and the TLS connection is also valid, the terminal only needs to re-execute the binding process. Therefore, the understanding of "re-establishment" can be a general term referring to the establishment of the entire user plane connection.

[0062] It should also be noted that the meaning of "re-establishment" in the first message can also be understood from the first indication information carried in the first message. If the first message carries the LMF LCS-UP address, the first indication information, and the second connection identifier, and the second connection identifier is different from the first connection identifier in the previous second message, but the LMF LCS-UP address is the same, then it can be understood that the network-side device simply wants the terminal to use a different connection identifier for the binding process. Therefore, if the PDU session and TLS connection process have already been successfully executed, they can be skipped directly, and the terminal only needs to re-execute the binding process, which means "re-establishment".

[0063] Optionally, in this embodiment of the application, the first timer mentioned above may be started by the network-side device after receiving the user plane connection establishment confirmation message.

[0064] Optionally, in this embodiment of the application, the first timer can be used to time the establishment process (including the binding process) of the user plane connection; when the first timer times out, it can be considered that the terminal has not initiated the binding for a long time or the binding has not been successful for a long time during the establishment process of the user plane connection, and at this time the terminal can perform the first operation.

[0065] Optionally, in this embodiment of the application, the first timer mentioned above can be timer T5012 (TS24.572v18.0.0) or a newly added timer for the binding process.

[0066] It should be noted that if the first timer is a newly added timer for the binding process, then this first timer can be started when the network-side device sends a user plane connection establishment command message (e.g., a user plane connectionestablishment command message) carrying an LCS-UP connection identifier, and stopped when it receives a binding request message from the terminal (e.g., a binding request message) that also carries the LCS-UP connection identifier. The entire period of the first timer is dedicated to associating the binding with the LCS-UP connection identifier, so as to prompt the terminal assigned a connection identifier to initiate the binding as soon as possible.

[0067] Optionally, in this embodiment of the application, the first connection identifier is used to identify the user plane connection and the terminal.

[0068] Optionally, in this embodiment of the application, the first connection identifier may be an LCS-UP connection identifier (LCS-UPconnection ID), an LCS-UP binding identifier (e.g., LCS-UP binding ID), or an LCS-UP connection correlation identifier (LCS-UP connection correlation ID), etc.

[0069] Optionally, in this embodiment of the application, the terminal identifier is used to identify the terminal.

[0070] Optionally, in this embodiment of the application, the terminal identifier may be a SubscriptionPermanent Identifier (SUPI) or a Generic Public Subscription Identifier (GPSI), etc.

[0071] Optionally, in this embodiment, the validity period of the first connection identifier can be configured by the network-side device.

[0072] Optionally, in this embodiment of the application, when the first connection identifier is within the valid time period, the first connection identifier can be used in the terminal binding process; when the first connection identifier is not within the valid time period, the first connection identifier cannot be used in the terminal binding process.

[0073] It should be noted that the release involved in the embodiments of this application may include at least one of the following: local release (e.g., locally release), release using signaling procedures (e.g., network requested user planeconnection release procedure), removal, and deletion.

[0074] Optionally, in the embodiments of this application, the above-mentioned release of the first connection identifier can also be understood as: treating the first connection identifier as expired or invalid.

[0075] Optionally, in this embodiment of the application, releasing the user plane connection may include: releasing the context of the terminal, including the association between the first connection identifier and the terminal.

[0076] Optionally, in the embodiments of this application, the above-mentioned location protocol replacement scheme can be understood as: replacing the scheme using user plane positioning with other location protocol schemes.

[0077] Optionally, in the embodiments of this application, the other positioning protocol schemes mentioned above may include: a scheme using control plane positioning or a scheme using Secure User Plane Location (SUPL) to transmit LPP messages, LCS-SS messages, etc.

[0078] Optionally, in this embodiment of the application, the first message mentioned above may be a user plane connection establishment command (e.g., userplane connection establishment command message).

[0079] Optionally, in this embodiment of the application, the first message may include at least one of the following: a second connection identifier, a terminal identifier of the terminal, and a first indication information.

[0080] The first instruction information is used to instruct the terminal to initiate the binding process using the second connection identifier.

[0081] Optionally, in the embodiments of this application, the first connection identifier or the second connection identifier mentioned above can be used by the network-side device to uniquely identify the terminal or connection among numerous user plane connections (e.g., LCS user plane connection, which can also be understood as TLS connection), or it can be understood as an association relationship, which is used by the network-side device to determine the terminal and the user plane connection one-to-one.

[0082] Optionally, in this embodiment of the application, the second connection identifier may be the same as or different from the first connection identifier.

[0083] Optionally, in this embodiment, during the process of establishing a user plane connection between the network-side device and the terminal, when the network-side device initially allocates user plane connection information to the terminal, it can first determine the mapping relationship between the first connection identifier and the terminal. Then, if the first condition is met, the network-side device updates the mapping relationship between the terminal and the connection identifier and sends the second connection identifier or the first indication information to the terminal. For example, it can delete the first connection identifier associated with the terminal and send the second connection identifier to the terminal, or it can maintain the mapping relationship between the first connection identifier and the terminal unchanged, that is, send the first connection identifier as the second connection identifier to the terminal. This can instruct the terminal to re-establish a user plane connection with the network-side device using the second connection identifier.

[0084] In this embodiment of the application, since the first message may include at least one of the second connection identifier, the terminal identifier of the terminal, and the first instruction information, the terminal can be instructed to re-establish the user plane connection with the network side device through different information, thereby improving the flexibility of instructing the establishment of the user plane connection.

[0085] In the connection management method provided in this application embodiment, when the first timer expires or the first connection identifier is not within the valid time during the process of establishing a user plane connection between the network-side device and the terminal, the network-side device can perform at least one of the following: releasing the first connection identifier, releasing the user plane connection, sending a first message to the terminal to indicate the re-establishment of the user plane connection, and changing the location protocol scheme. Therefore, the terminal can avoid occupying the first connection identifier for a long time ineffectively, so that the network-side device can reallocate the first connection identifier, thereby saving resources.

[0086] Optionally, in this embodiment of the application, before step 301 above, the connection management method provided in this embodiment of the application may further include the following step A.

[0087] Step A: The network-side device sends a second message to the terminal.

[0088] The second message mentioned above can be a user plane connection establishment command or an instruction for the terminal to establish a user plane connection with the network-side device.

[0089] Optionally, in this embodiment of the application, the second message mentioned above may be a user plane connection establishment command (e.g., a userplane connection establishment command message).

[0090] It should be noted that both the first message and the second message mentioned above can be user plane connection establishment commands. In this case, the second message can be understood as a user plane connection establishment command sent by the network-side device to the terminal at the very beginning; while the first message is a user plane connection establishment command that may be sent to the terminal after the second message is sent. For example, if the network-side device determines that the timer associated with the connection identifier in the second message has expired, and wants to update the mapping relationship between the terminal and the connection identifier, and reallocate a connection identifier for the terminal to use during the binding process, it may send the first message to the terminal.

[0091] Optionally, in this embodiment of the application, the second message may also include the LMF LCS-UP address (e.g., LMF LCS-UP address).

[0092] It should be noted that the user plane connection established by the second message mentioned above is the same as the user plane connection in step 301 above.

[0093] Optionally, in this embodiment of the application, the second message may include at least one of the following: the first connection identifier, the terminal identifier of the terminal, the relevant information of the second timer, and the first time information.

[0094] The second timer is associated with at least one of the following: the first connection identifier, the initiation of the terminal binding process, and the first time information is used to indicate the validity period of the first connection identifier.

[0095] Optionally, in this embodiment of the application, the relevant information of the second timer may include the duration corresponding to the second timer.

[0096] Optionally, in this embodiment of the application, the second timer can be a General Packet Radio Service (GPRS) 3 format timer in TS24.008v18.0.0. The network-side device can configure the second timer by setting the unit and timer value of the GPRS 3 format timer.

[0097] Optionally, in this embodiment of the application, the second timer can be an implicit indication, that is, the network-side device implicitly instructs the terminal to start the second timer and initiate the binding process within the time corresponding to the second timer.

[0098] Optionally, in the embodiments of this application, the aforementioned first time information may be used to indicate at least one of the following: the valid start time and valid end time of the aforementioned first connection identifier, and the valid time interval of the aforementioned first connection identifier.

[0099] For example, when the aforementioned first time information is used to indicate the valid time interval of the aforementioned first connection identifier, the valid time of the first connection identifier is: a time interval after the terminal receives the first time information; once this time interval is exceeded, the first connection identifier becomes invalid.

[0100] For further descriptions of the second message, please refer to the relevant descriptions of the first message. To avoid repetition, they will not be repeated here.

[0101] In this embodiment of the application, since the second message may include at least one of the first connection identifier, the terminal identifier of the terminal, the second timer and the first time information, the network-side device can start the first timer when sending different information to the terminal, thereby improving the flexibility of starting the first timer.

[0102] Optionally, in this embodiment, after sending the second message to the terminal, the network-side device can determine whether the first connection identifier is valid based on the information included in the second message, and thus determine whether to accept the terminal's binding request. For example, when the second message includes the first time information, after receiving the terminal's binding request message, the network-side device can determine whether the first connection identifier is within a valid time frame based on the first time information. If it is within a valid time frame, the binding request is accepted; if it is not within a valid time frame, the binding request is rejected and the first operation is performed. It is understood that after sending the second message to the terminal, the network-side device may not start the first timer; the network-side device determines whether the first connection identifier is valid based on the first time information.

[0103] Optionally, in this embodiment of the application, before step 301 above, the connection management method provided in this embodiment of the application may further include step 302 below.

[0104] Step 302: When the second message is sent to the terminal, the network-side device starts the first timer.

[0105] Optionally, in the embodiments of this application, the above-mentioned situation of sending a second message to the terminal can be understood as: after sending the second message to the terminal, or after a preset time after sending the second message to the terminal.

[0106] It is understood that after step A above, the network-side device can start the first timer immediately or start the first timer after a preset duration.

[0107] In this embodiment of the application, since the network-side device starts the first timer when the second message is sent to the terminal, the binding process of the terminal can be monitored from the time the terminal is instructed to establish a user plane connection with the network-side device. This allows for accurate determination of whether the binding has failed for a long time, and the first operation described above can be performed to release resources.

[0108] Optionally, the connection management method provided in this application embodiment may further include the following step 303.

[0109] Step 303: When a first message is sent to the terminal, and the first message includes a second connection identifier that is different from the first connection identifier, the network-side device restarts the first timer.

[0110] It is understood that when the first message is sent to the terminal and the first message includes the second connection identifier which is different from the first connection identifier, the network-side device instructs the terminal to re-establish the user plane connection with the network-side device using the different connection identifier. At this time, restarting the first timer can re-monitor the new binding process of the terminal.

[0111] In this embodiment of the application, when the first message is sent to the terminal and the first message includes the second connection identifier which is different from the first connection identifier, the network-side device can restart the first timer, thus accurately monitoring the binding process of the terminal using the second connection identifier.

[0112] Optionally, the connection management method provided in this application embodiment may further include the following step 304.

[0113] Step 304: After sending the second message to the terminal, the network-side device receives the binding request message sent by the terminal.

[0114] The aforementioned binding request message is used to bind the user plane connection and the terminal, and the binding request message includes at least one of the following: a third connection identifier and a terminal identifier of the terminal.

[0115] Optionally, in this embodiment of the application, the binding request message can be used to request the network-side device to associate with the terminal or the first connection identifier to establish a TLS connection.

[0116] Optionally, in this embodiment of the application, the third connection identifier may be the same as or different from the first connection identifier.

[0117] It should be noted that the reason for distinguishing between the third connection identifier and the first connection identifier is that some normal terminals may carry an incorrect connection identifier in the binding request message due to internal operation errors after obtaining the connection identifier, or may mistakenly occupy the connection identifier of other terminals. Therefore, the network needs to determine whether to accept the binding request by judging the third connection identifier.

[0118] Optionally, in this embodiment of the application, the binding request message may be sent through the user plane.

[0119] In this embodiment of the application, since the network-side device can receive the binding request message sent by the terminal after sending the second message to the terminal, the network-side device can know that the terminal has initiated the binding process using the third connection identifier.

[0120] Optionally, in this embodiment of the application, after step 304 above, the connection management method provided in this embodiment of the application may further include step 305 below.

[0121] Step 305: If the binding request message includes a third connection identifier and the third connection identifier is the same as the first connection identifier, the network-side device stops the first timer.

[0122] It is understood that if the above binding request message includes the above third connection identifier and the third connection identifier is the same as the above first connection identifier, the terminal has already used the first connection identifier to initiate the binding process. At this time, there is no need to monitor the initiation of the binding process through the above first timer, so the first timer can be stopped.

[0123] In this embodiment of the application, since the binding request message includes the third connection identifier and the third connection identifier is the same as the first connection identifier, the network-side device can stop the first timer. Therefore, when it is known that the terminal has used the first connection identifier to initiate the binding process, the first timer can be stopped to save device power consumption.

[0124] Optionally, in this embodiment of the application, after step 304 above, the connection management method provided in this embodiment of the application may further include step 306 below.

[0125] Step 306: The network-side device sends a binding reply message to the terminal.

[0126] The aforementioned binding response message includes at least one of the following: second indication information, the aforementioned third connection identifier, first reason value, and third indication information.

[0127] The second indication information is used to indicate whether to accept or reject the binding corresponding to the binding request message, the first reason value is used to indicate the reason for rejecting the binding corresponding to the binding request message, and the third indication information is used to indicate that the terminal releases the user plane connection.

[0128] Optionally, in this embodiment of the application, one implementation of the second indication information is to indicate the result of the user plane connection binding, including successful binding or binding failure; another implementation is that the binding reply message is implemented through message type (e.g., message type), one is a binding accept message (e.g., binding accept message), and the other is a binding reject message (e.g., binding reject message); yet another implementation is that binding acceptance or binding failure is an implicit implementation, for example, if the binding reply message carries the first reason value, it represents binding failure, and if the binding reply message does not carry the first reason value, it represents binding acceptance.

[0129] Optionally, in this embodiment of the application, the third connection identifier is the connection identifier associated with the binding reply message.

[0130] Optionally, in this embodiment of the application, the above-mentioned binding reply message may be sent through the user plane.

[0131] Optionally, in the embodiments of this application, the first cause value mentioned above can be used to indicate at least one of the following: invalid connection identifier (e.g., identifier invalid), connection identifier timeout (e.g., identifier expired), connection identifier conflict (e.g., identifier collision or identifier occupied), binding not accepted (e.g., bindnot accepted), protocol error (e.g., protocol error, unspecified).

[0132] Alternatively, in this embodiment of the application, the connection identifier timeout can also be understood as the connection identifier expiring.

[0133] Optionally, in this embodiment of the application, the above-mentioned connection identifier conflict may include: the connection identifier is already bound or occupied.

[0134] Optionally, in this embodiment, when the binding request message is accepted, the network-side device can provide the terminal with result indication information, indicating successful binding, and optionally carrying the third connection identifier. Afterward, the network-side device binds the TLS connection to the terminal's terminal identifier or the third connection identifier, and can send LPP messages and LCS-SS messages related to the terminal through the TLS connection or user plane connection.

[0135] Optionally, in this embodiment of the application, when the above binding request message cannot be accepted, the network-side device may provide the terminal with result indication information, wherein the indication is that the binding failed; and / or, the network-side device carries the above first reason value to indicate that the binding is not accepted (e.g., bind not accepted).

[0136] Optionally, in this embodiment of the application, when the LCS-UP connection identifier in the binding request message is an invalid value identifier or an unassigned identifier, the network-side device may provide the terminal with result indication information, wherein the indication is that the binding failed; and / or, the network-side device carries the first reason value indicating that the connection identifier is invalid; and / or, the network-side device sends a binding rejection message to the terminal, and carries the first reason value indicating that the connection identifier is invalid.

[0137] When the LCS-UP connection identifier in the binding request has already been bound, the LMF provides the terminal with result indication information, which indicates that the binding failed; and / or, the LMF carries a first reason value indicating that the connection identifier is already bound or occupied (e.g., identifier already bound / identifier occupied), or indicating that the connection identifier is conflicted (e.g., identifier collision); and / or, the network-side device sends a binding rejection message to the terminal, carrying a first reason value indicating that the connection identifier is already bound, occupied, or conflicted.

[0138] It should be noted that one implementation method for the aforementioned connection identifier conflict is as follows: The network-side device receives a binding request message using the first connection identifier and finds that the binding process using that first connection identifier has already been completed, and the network-side device has already bound or associated that first connection identifier or the terminal's terminal identifier with other TLS connections. In this case, a new binding request will inevitably fail, which is an abnormal situation, and one of the terminals must have used the wrong first connection identifier.

[0139] In this situation, the network-side device cannot distinguish which terminal is correct (i.e., the terminal truly associated with the aforementioned first connection identifier) ​​and which is the erroneous terminal. Therefore, the network-side device can send a binding reply message or binding rejection message to the terminal indicating binding failure, carrying the aforementioned first reason value indicating a connection identifier conflict. Upon receiving this first reason value, the correct terminal discovers that the binding process has not yet been completed and thus learns that a terminal has impersonated or occupied its first connection identifier to complete the binding. At this point, the correct terminal can send a message to the network-side device via User Plane Positioning Connection Management Information (UPP-CMI) signaling on the control plane. This message could be a user plane connection release request message or a new report message. The message carries a first connection identifier and optionally a specific indication. This message is used to request the network-side device to release the LCS-secure user plane connection between the terminal and the network-side device, or to report an anomaly in the user plane connection. The specific indication is used to instruct the network-side device to forcibly release the user plane connection or to indicate that the connection identifier is incorrectly bound, occupied, or hijacked. Alternatively, the terminal can include an indication in its user plane connection failure message to inform the network-side device that the connection identifier assigned to the terminal has conflicted during the binding process, or that the connection identifier has been misused, or to request the network-side device to assign a new connection identifier. Upon receiving the release request message, report message, or user plane connection failure message from the terminal, the network-side device verifies that the connection identifier has been misused or conflicted, and immediately releases the user plane connection associated with the first connection identifier. This corrects for occupied connection identifiers or incorrect binding. The aforementioned request for the network-side device to allocate a new connection identifier can prevent the re-use of previously conflicting connection identifiers from causing further conflicts, thus mitigating the conflict issue during the next binding attempt.

[0140] In this embodiment of the application, after receiving the binding request message sent by the terminal, the network-side device can send the above-mentioned binding reply message to the terminal to indicate the binding result and further operations, thereby enabling the terminal to release resources in a timely manner.

[0141] Optionally, in this embodiment of the application, after step 306 above, the connection management method provided in this embodiment of the application may further include step 307 below.

[0142] Step 307: The network-side device receives the third message sent by the terminal.

[0143] The aforementioned third message is used to indicate that the establishment of a user plane connection has failed. This third message can be a user plane connection establishment failure message (e.g., user plane connection establishment failure message) or a user plane connection establishment command rejection message (e.g., user plane connection establishment command rejection message).

[0144] Optionally, in this embodiment of the application, the third message may include at least one of the following: a second reason value and a fourth indication information. The second reason value is used to indicate at least one of the following: binding failure, TLS failure, session failure, invalid connection identifier, connection identifier timeout, connection identifier conflict, or binding not accepted. The fourth indication information is used to request the reassignment of the connection identifier.

[0145] It should be noted that the aforementioned fourth instruction message is sent by the terminal to the network-side device when the current connection establishment fails. Its purpose is to enable the terminal to proactively identify problems discovered during the establishment process and inform the network-side device to directly reassign a new connection identifier during the next connection establishment attempt. These problems include the terminal receiving an invalid connection identifier or connection identifier conflicts. With this fourth instruction message, if the terminal still wants to request the establishment of a user plane connection, it no longer needs to send another user plane connection establishment request message. Instead, the network-side device can directly send a new user plane connection establishment command message carrying the new connection identifier to the terminal, thus saving signaling interaction.

[0146] Optionally, in this embodiment of the application, the aforementioned third message may be sent via the control plane.

[0147] Optionally, in this embodiment of the application, after receiving the aforementioned third message, the network-side device may perform the aforementioned first operation.

[0148] Optionally, in this embodiment of the application, after the network-side device releases the first connection identifier, when it uses the first connection identifier to bind in a subsequent binding request message, it shall carry at least one of the following in the binding reply message: the result indication information is set to binding failure, the first connection identifier, the first reason value is set to invalid connection identifier or connection identifier conflict.

[0149] In this embodiment of the application, since the network-side device can receive the third message sent by the terminal, it can promptly know that the user plane connection has failed to be established and perform the first operation described above to release resources.

[0150] For example, such as Figure 4 As shown, taking the network-side device LMF as an example, the process of establishing a user plane connection between the terminal and LMF includes the following steps 1 to 6:

[0151] Step 1: When initiated by the terminal, the terminal sends a user plane connection establishment request (e.g., userplane connection establishment request message) to the LMF to request the establishment of an LCS-secure user plane connection between the terminal and the LMF.

[0152] Step 2: When initiated by the network-side device, or after receiving the message in Step 1, the LMF sends a user plane connection establishment command to the terminal to transmit user plane connection information and trigger the terminal to establish an LCS-secure user plane connection with the LMF. The command may carry at least one of the following: LMF LCS-UP address, LCS-UP connection identifier; and start timer 1 at the same time.

[0153] Step 3: After receiving the user plane connection establishment command in Step 2, the terminal establishes a PDU to provide PDU connection service from the terminal to the LMF; and after successfully establishing the PDU, it initiates a TLS handshake based on the received LMF LCS-UP address to establish a secure connection from the terminal to the LMF.

[0154] Step 4: Optionally, the terminal sends an LCS-UP binding request to the LMF. This message is used to request the LMF to associate the terminal or the LCS-UP connection identifier with the TLS connection. This message may carry the LCS-UP connection identifier; at the same time, timer 3 is started.

[0155] It should be noted that the aforementioned timer 3 is associated with or bound to the aforementioned LCS-UP connection identifier. This timer 3 is used to monitor or associate the LMF receiving an LCS-UP binding request and replying to the terminal with an LCS-UP binding response message. When this timer 3 times out, it indicates that the LCS-UP binding request has not been sent to the LMF, or that the LCS-UP binding response message has not yet been replied to the terminal. In this case, the terminal needs to resend an LCS-UP binding request to the LMF to ensure the binding is completed. The value of this timer 3 can be preset or determined by the terminal implementation.

[0156] If, while timer 3 is running, has not stopped, or has not timed out, the terminal receives a user plane connection establishment command (i.e., the message in step 2), which can be understood as an abnormal situation: the terminal is performing binding, but due to the long processing time, timer 1 (e.g., T5012) started by the LMF in step 2 times out, so the LMF resends a message; or the LMF has switched over, and the new LMF also decides to establish a user plane connection with the terminal; or because timer 1 timed out, the LMF terminates the current user plane connection establishment process and then decides to initiate a new user plane connection establishment process), the terminal can take one of the following actions:

[0157] 1. If the terminal receives a user plane connection establishment command message during the LCS-UP binding process, and:

[0158] 1) The LMF LCS-UP address contained in the user plane connection establishment command message is the same as the address used to send the LCS-UP binding request message; and,

[0159] 2) The LCS-UP connection identifier contained in the user plane connection establishment command (e.g., USER PLANE CONNECTION ESTABLISHMENT COMMAND) message is the same as the LCS-UP connection identifier contained in the LCS-UP binding request (e.g., LCS-UP BINDING REQUEST) message;

[0160] The terminal should then ignore the user plane connection establishment command message and continue executing the LCS-UP binding process, i.e., wait for the network to respond to the binding request.

[0161] 2. If the terminal receives a user plane connection establishment command message during the LCS-UP binding process, and:

[0162] 1) The LMF LCS-UP address contained in the user plane connection establishment command message is different from the address used to send the LCS-UP binding request message; or

[0163] 2) The LCS-UP connection identifier in the user plane connection establishment command message (e.g., USER PLANE CONNECTION ESTABLISHMENT COMMAND) differs from the LCS-UP connection identifier in the LCS-UP binding request message (e.g., LCS-UP BINDING REQUEST); or,

[0164] 3) Includes 1) and 2) above;

[0165] The terminal should then abort the LCS-UP binding process, stop timer 3, and continue processing the latest user plane connection establishment command message.

[0166] Step 5, Optionally, upon receiving the message from Step 4, the LMF replies to the terminal with an LCS-UP binding reply, which is used to respond to the LCS-UP binding request message and provide the binding result. This message may carry at least one of the following:

[0167] Binding result;

[0168] LCS-UP connection identifier;

[0169] Cause value.

[0170] It should be noted that the terminal can only send its LPP and LCS-SS messages through the aforementioned TLS connection or user plane connection after receiving a successful binding indication. When a binding failure indication is received, the terminal cannot send its LPP and LCS-SS messages through the same TLS connection or user plane connection, and must perform at least one of the following operations:

[0171] Stop Timer 3: After receiving the LCS-UP binding response, if Timer 3 is still running, the terminal will stop Timer 3.

[0172] The LCS-UP connection identifier is considered expired or invalid: The LCS-UP connection identifier is considered expired or invalid and cannot be used for the binding process in the future.

[0173] Change the positioning protocol scheme: Based on local judgment, the terminal decides not to use user plane positioning, but to use control plane positioning or use SUPL to transmit LPP messages and LCS-SS messages.

[0174] It should also be noted that in step 2 above, when the LMF allocates the connection identifier, it internally maintains a mapping relationship between terminal identifiers and connection identifiers. When a terminal provides a terminal identifier or a connection identifier to the LMF, the LMF knows which terminal or connection identifier it is. In step 5, the LMF needs to bind this TLS connection to the terminal or connection identifier. In this way, at the LMF level, the TLS connection, terminal identifier, and connection identifier are in a one-to-one correspondence.

[0175] Step 6: When the binding process succeeds, the terminal sends a "user plane connection establishment complete" message to the LMF to indicate that the user plane connection has been successfully established. When timer 3 times out, the TLS handshake fails, the binding process receives a failure indication, or the PDU session establishment fails, the terminal sends a "user plane connection establishment failure" message to the LMF. Upon receiving the "user plane connection establishment failure" message, the LMF performs the first operation described above.

[0176] It should be noted that when the terminal sends the aforementioned user plane connection establishmentfailure message to the LMF, this message may carry a cause value and / or fourth indication information. The cause value indicates at least one of the following: binding failure, TLS establishment failure, PDU session failure, invalid connection identifier, connection identifier timeout, connection identifier conflict, or binding not accepted. The fourth indication information (e.g., LCS-UP additional information) is used to request the re-allocation of the connection identifier (e.g., request the LMF to re-allocate a new LCS-UP connection ID to the UE). One implementation is shown in the table below:

[0177] (LCS-UP Additional Information Elements)

[0178]

[0179]

[0180] Optionally, in this embodiment of the application, in step 6 above, after the LMF performs the first operation, the terminal can re-establish the user plane connection with the LMF. During this process, the LMF can allocate a new connection identifier to the terminal for re-establishing the user plane connection. The specific process can be referred to steps 1 to 6 above. To avoid repetition, it will not be described again here.

[0181] This application provides another connection management method. Figure 5 A flowchart illustrating the connection management method provided in an embodiment of this application is shown. Figure 5 As shown, the connection management method provided in this application embodiment may include the following step 501.

[0182] Step 501: During the process of establishing a user plane connection between the network-side device and the terminal, if the second condition is met, the terminal performs the second operation.

[0183] The second condition mentioned above includes at least one of the following:

[0184] The second timer expires, and the second timer is associated with at least one of the following: the first connection identifier, or the initiation of the terminal binding process;

[0185] The third timer expires, and the third timer is associated with at least one of the following: the first connection identifier, the terminal binding process, and the user plane connection establishment process;

[0186] The first connection identifier is not within its valid time period;

[0187] The second operation mentioned above includes at least one of the following:

[0188] Send a binding request message to the network-side device;

[0189] Release the first connection identifier;

[0190] Release the user plane connection;

[0191] Send a third message to the network-side device, which indicates that the establishment of the user plane connection has failed;

[0192] Change the positioning protocol scheme.

[0193] Optionally, in this embodiment of the application, the third message mentioned above may be a user plane connection establishment failure message or a user plane connection establishment command reject message.

[0194] Optionally, in this embodiment of the application, the third message may include at least one of the following: a second reason value and a fourth indication information; wherein, the second reason value is used to indicate at least one of the following: binding failure, TLS failure, session failure, invalid connection identifier, connection identifier timeout, connection identifier conflict, binding not accepted; the fourth indication information is used to request the reassignment of the connection identifier.

[0195] Optionally, in this embodiment of the application, the aforementioned third message may be sent via the control plane.

[0196] In the connection management method provided in this application embodiment, during the process of establishing a user plane connection between the network-side device and the terminal, when the second timer times out, the third timer times out, or the first connection identifier is not within the valid time, the terminal can perform at least one of the following actions: sending a binding request message to the network-side device, releasing the first connection identifier, releasing the user plane connection, sending a third message to the network-side device to indicate that the establishment of the user plane connection has failed, and changing the positioning protocol scheme. Therefore, the terminal can avoid occupying the first connection identifier for a long time ineffectively, so that the network-side device can reallocate the first connection identifier, thereby saving resources.

[0197] Optionally, in this embodiment of the application, before step 501 above, the connection management method provided in this embodiment of the application may further include step 502 below.

[0198] Step 502: Upon receiving the second message sent by the network-side device, the terminal starts the second timer.

[0199] The second message mentioned above is used to instruct the terminal to establish a user plane connection with the network-side device.

[0200] Optionally, in this embodiment of the application, the second message may include at least one of the following: the first connection identifier, the terminal identifier of the terminal, the second timer, and the first time information.

[0201] The second timer is associated with at least one of the following: the first connection identifier, the initiation of the terminal binding process, and the first time information is used to indicate the validity period of the first connection identifier.

[0202] Optionally, in this embodiment of the application, the terminal may determine whether the first connection identifier is within the valid time period based on the first time information mentioned above.

[0203] Optionally, in this embodiment of the application, the above-mentioned first-time information can be implemented as shown in the table below:

[0204] (Identifier time validity information element)

[0205]

[0206] Optionally, the connection management method provided in this application embodiment may further include the following step 503.

[0207] Step 503: If the third condition is met, the terminal sends a binding request message to the network-side device.

[0208] The binding request message is used to bind the user plane connection and the terminal. The binding request message includes at least one of the following: a third connection identifier and a terminal identifier of the terminal. The third condition includes any one of the following: the second timer has not expired and the first connection identifier is within the valid time.

[0209] Optionally, in this embodiment of the application, the binding request message may be sent through the user plane.

[0210] Optionally, in this embodiment, before initiating the binding process, the terminal needs to check the first time information associated with the first connection identifier on the terminal side, i.e., whether the first connection identifier is within a valid time. If the first time information shows that the first connection identifier is available, the terminal can use the first connection identifier to send the binding request message to the LMF; if the first time information shows that the first connection identifier is unavailable, the terminal cannot use the first connection identifier to send the binding request message to the LMF.

[0211] Optionally, in this embodiment of the application, after step 503 above, the connection management method provided in this embodiment of the application may further include step 504 below.

[0212] Step 504: The terminal receives the binding reply message sent by the network-side device.

[0213] The aforementioned binding response message includes at least one of the following: second indication information, the aforementioned third connection identifier, first reason value, and third indication information.

[0214] The second indication information is used to indicate whether to accept or reject the binding corresponding to the binding request message, the first reason value is used to indicate the reason for rejecting the binding corresponding to the binding request message, and the third indication information is used to indicate that the terminal releases the user plane connection.

[0215] Optionally, in the embodiments of this application, the first cause value mentioned above can be used to indicate at least one of the following: invalid connection identifier, connection identifier timeout, connection identifier conflict, or binding not accepted.

[0216] Optionally, in this embodiment of the application, the above-mentioned binding reply message may be sent through the user plane.

[0217] Optionally, in this embodiment of the application, after step 503 above, the connection management method provided in this embodiment of the application may further include step 505 below.

[0218] Step 505: The terminal performs the third operation.

[0219] The third operation mentioned above includes at least one of the following:

[0220] Stop the second timer mentioned above;

[0221] Start the third timer mentioned above.

[0222] Optionally, in this embodiment of the application, once the above-mentioned binding request message is sent, the terminal may start the above-mentioned third timer.

[0223] Optionally, in this embodiment of the application, after step 502 above, the connection management method provided in this embodiment of the application may further include step 506 below.

[0224] Step 506: The terminal receives the first message sent by the network-side device while the second timer is running.

[0225] The first message mentioned above includes at least one of the following: a second connection identifier, a terminal identifier of the terminal, and a first instruction message.

[0226] The first instruction information is used to instruct the terminal to initiate the binding process using the second connection identifier.

[0227] Optionally, in this embodiment of the application, after step 506 above, the connection management method provided in this embodiment of the application may further include step 507 below.

[0228] Step 507: The terminal performs the fourth operation based on a message.

[0229] The fourth operation mentioned above includes any one of the following:

[0230] Ignore the first message mentioned above;

[0231] Restart the second timer mentioned above;

[0232] Send a binding request message to the network-side device.

[0233] Optionally, in the embodiments of this application, step 507 can be implemented by step 507a or step 507b as described below.

[0234] Step 507a: If the second connection identifier is the same as the first connection identifier, the terminal ignores the first message.

[0235] Step 507b: If the second connection identifier is different from the first connection identifier, the terminal restarts the second timer and sends a binding request message to the network-side device.

[0236] For example, such as Figure 6 As shown, taking the network-side device LMF as an example, the process of establishing a user plane connection between the terminal and LMF includes the following steps 1 to 6, which are the same as those described above. Figure 4The difference in the steps shown is that the message in step 2 can also carry timer 2. When the terminal receives a user plane connection establishment command, if the user plane connection establishment command can be accepted, then the terminal starts timer 2. This timer 2 is associated with the LCS-UP connection identifier or the binding of the LCS-UP connection identifier received in the step. In step 4, once the terminal sends an LCS-UP binding request, the terminal stops timer 2.

[0237] For example, such as Figure 7 As shown, taking the network-side device LMF as an example, the process of establishing a user plane connection between the terminal and LMF includes the following steps 1 to 6, which are the same as those described above. Figure 4 The difference between the steps shown is that the message in step 2 can also carry first-time information, which allows us to determine whether the LCS-UP connection identifier is within the valid time by detecting the first-time information, thereby releasing resources flexibly and accurately.

[0238] It should be noted that, in Figure 4 , 6 In section 7, messages within the dashed box are sent via user plane messages (such as TCP or IP packets, forwarded by the base station and UPF), while messages outside the dashed box are sent via control plane messages (NAS signaling, forwarded by the base station and AMF).

[0239] For other descriptions of the embodiments of this application and the technical effects that each technical feature can achieve, please refer to the relevant descriptions in the above network-side device method embodiments. To avoid repetition, they will not be repeated here.

[0240] The connection management method provided in this application can be executed by a connection management device. This application uses the execution of the connection management method by a connection management device as an example to illustrate the connection management device provided in this application.

[0241] This application provides a connection management device. As an example, the connection management device may be a communication device or a component within a communication device, such as a chip. The communication device may be a terminal, a network-side device, or a server, etc. Exemplarily, the terminal may include, but is not limited to, the type of terminal 11 listed above, and the network-side device may include, but is not limited to, the type of network-side device 12 listed above. This application does not impose specific limitations.

[0242] The connection management device includes a receiving module, a transmitting module, and a processing module. These modules can be implemented in software or hardware. When implemented in hardware, the processing module can be implemented by a processor. For example, the processor can include general-purpose processors, special-purpose processors, such as a Central Processing Unit (CPU), microprocessor, Digital Signal Processor (DSP), Artificial Intelligence (AI) processor, Graphics Processing Unit (GPU), Application Specific Integrated Circuit (ASIC), Network Processor (NP), Field Programmable Gate Array (FPGA), or other programmable logic devices, gate circuits, transistors, discrete hardware components, etc. The receiving and transmitting modules can be implemented by a communication interface, which can include one or more of the following: transceiver, pins, circuits, bus, radio frequency unit, etc.

[0243] For details, see Figure 8 When the connection management device is a network-side device or a component of a network-side device, the connection management device 80 may include a first processing module 81.

[0244] The first processing module 81 can be used to perform a first operation if a first condition is met during the process of establishing a user plane connection between the network-side device and the terminal. The first condition includes at least one of the following: a first timer times out, the first timer being associated with at least one of the following: a first connection identifier, a terminal identifier of the terminal, the terminal binding process, and the user plane connection establishment process; the first connection identifier is not within its valid time period; the first operation includes at least one of the following: releasing the first connection identifier; releasing the user plane connection; sending a first message to the terminal, the first message instructing the terminal to re-establish the user plane connection with the network-side device; and changing the positioning protocol scheme.

[0245] In one possible implementation, the first message may include at least one of the following: a second connection identifier, a terminal identifier, and first instruction information. The first instruction information is used to instruct the terminal to initiate a binding process using the second connection identifier.

[0246] In one possible implementation, the first processing module 81 can also be used to start a first timer before performing the first operation described above, by sending a second message to the terminal. The second message is used to instruct the terminal to establish a user plane connection with the network-side device.

[0247] In one possible implementation, the second message may include at least one of the following: the first connection identifier, the terminal identifier of the terminal, information related to the second timer, and first time information. The second timer is associated with at least one of the following: the first connection identifier, the initiation of the terminal binding process, and the first time information indicating the validity period of the first connection identifier.

[0248] In one possible implementation, the first processing module 81 can also be used to restart the first timer when sending the first message to the terminal, and the first message includes a second connection identifier that is different from the first connection identifier.

[0249] In one possible implementation, the connection management device 80 may further include a first receiving module. The first receiving module can be used to receive a binding request message sent by the terminal after sending the aforementioned second message to the terminal. The binding request message is used to bind the user plane connection and the terminal, and includes at least one of the following: a third connection identifier and a terminal identifier.

[0250] In one possible implementation, the aforementioned binding request message can be sent through the user plane.

[0251] In one possible implementation, the connection management device 80 may further include a first sending module. The first sending module is configured to send a binding response message to the terminal after the first receiving module receives the binding request message sent by the terminal. The binding response message includes at least one of the following: second indication information, the aforementioned third connection identifier, a first reason value, and third indication information. Specifically, the second indication information indicates whether the binding corresponding to the binding request message is accepted or rejected; the first reason value indicates the reason for rejecting the binding corresponding to the binding request message; and the third indication information indicates that the terminal releases the user plane connection.

[0252] In one possible implementation, the aforementioned first reason value can specifically be used to indicate at least one of the following: invalid connection identifier, connection identifier timeout, connection identifier conflict, or binding not accepted.

[0253] In one possible implementation, the aforementioned binding reply message can be sent through the user plane.

[0254] In one possible implementation, the first processing module 81 can also be used to stop the first timer after the first receiving module receives the binding request message sent by the terminal, provided that the binding request message includes the third connection identifier and the third connection identifier is the same as the first connection identifier.

[0255] In one possible implementation, the first receiving module can also be used to receive a third message sent by the terminal after the first sending module sends a binding reply message to the terminal. This third message indicates that the user plane connection establishment failed.

[0256] In one possible implementation, the third message may include at least one of the following: a second reason value and a fourth indication information; wherein the second reason value is used to indicate at least one of the following: binding failure, TLS failure, session failure, invalid connection identifier, connection identifier timeout, connection identifier conflict, or binding not accepted; and the fourth indication information is used to request the reassignment of the connection identifier.

[0257] In one possible implementation, the aforementioned third message may be sent via the control plane.

[0258] In the connection management device provided in this application embodiment, when the first timer expires or the first connection identifier is not within the valid time during the process of establishing a user plane connection between the network-side device and the terminal, the connection management device can perform at least one of the following: releasing the first connection identifier, releasing the user plane connection, sending a first message to the terminal to indicate the re-establishment of the user plane connection, and changing the location protocol scheme. Therefore, the terminal can be prevented from occupying the first connection identifier for a long time, so that the network-side device can reallocate the first connection identifier, thereby saving resources.

[0259] The connection management device provided in this application embodiment can implement all the processes implemented in the above network-side device method embodiment and achieve the same technical effect. To avoid repetition, it will not be described again here.

[0260] See Figure 9 When the connection management device is a terminal or a component in a terminal, the connection management device 90 may include a second processing module 91.

[0261] The second processing module 91 can be used to perform a second operation if a second condition is met during the process of establishing a user plane connection between the network-side device and the terminal. The second condition includes at least one of the following: a second timer times out, which is associated with at least one of the following: a first connection identifier, the initiation of the terminal binding process; a third timer times out, which is associated with at least one of the following: a first connection identifier, the terminal binding process, the establishment process of the user plane connection; the first connection identifier is not within its valid time. The second operation includes at least one of the following: sending a binding request message to the network-side device; releasing the first connection identifier; releasing the user plane connection; sending a third message to the network-side device, which indicates that the establishment of the user plane connection failed; and changing the positioning protocol scheme.

[0262] In one possible implementation, the second processing module 91 can also be used to start the second timer upon receiving a second message from the network-side device before performing the second operation described above. The second message is used to instruct the terminal to establish a user plane connection with the network-side device.

[0263] In one possible implementation, the second message may include at least one of the following: the first connection identifier, the terminal identifier of the terminal, the relevant information of the second timer, and first time information. The second timer is associated with at least one of the following: the first connection identifier, the initiation of the terminal binding process, and the first time information indicating the validity period of the first connection identifier.

[0264] In one possible implementation, the terminal may determine whether the first connection identifier is within a valid time period based on the aforementioned first time information.

[0265] In one possible implementation, the connection management device 90 may further include a second sending module. The second sending module can be used to send a binding request message to the network-side device when a third condition is met. The binding request message is used to bind the user plane connection and the terminal, and the binding request message includes at least one of the following: a third connection identifier and a terminal identifier of the terminal. The third condition includes any one of the following: the second timer has not expired, or the first connection identifier is within its valid time.

[0266] In one possible implementation, the aforementioned binding request message can be sent through the user plane.

[0267] In one possible implementation, the connection management device 90 may further include a second receiving module. The second receiving module is configured to receive a binding response message sent by the network-side device after the second sending module sends the binding request message to the network-side device. The binding response message includes at least one of the following: second indication information, the third connection identifier, a first reason value, and third indication information. Specifically, the second indication information indicates whether the binding corresponding to the binding request message is accepted or rejected; the first reason value indicates the reason for rejecting the binding corresponding to the binding request message; and the third indication information indicates that the terminal releases the user plane connection.

[0268] In one possible implementation, the aforementioned first reason value can specifically be used to indicate at least one of the following: invalid connection identifier, connection identifier timeout, connection identifier conflict, or binding not accepted.

[0269] In one possible implementation, the aforementioned binding reply message can be sent through the user plane.

[0270] In one possible implementation, the second processing module 91 can also be used to perform a third operation after the second sending module sends the binding request message to the network-side device. The third operation includes at least one of the following: stopping the second timer; starting the third timer.

[0271] In one possible implementation, the second receiving module can also be used to receive a first message sent by the network-side device during the operation of the second timer after the second processing module 91 starts the second timer. The first message includes at least one of the following: a second connection identifier, a terminal identifier of the terminal, and first indication information. The first indication information is used to instruct the terminal to initiate a binding process using the second connection identifier.

[0272] In one possible implementation, the second processing module 91 can also be used to perform a fourth operation based on the first message sent by the network-side device after the second receiving module receives the first message. The fourth operation includes any one of the following: ignoring the first message; restarting the second timer; or sending a binding request message to the network-side device.

[0273] In one possible implementation, the second processing module 91 can be specifically used to: ignore the first message when the second connection identifier is the same as the first connection identifier; or, restart the second timer and send the binding request message to the network-side device when the second connection identifier is different from the first connection identifier.

[0274] In one possible implementation, the third message may include at least one of the following: a second reason value and a fourth indication information; wherein the second reason value is used to indicate at least one of the following: binding failure, TLS failure, session failure, invalid connection identifier, connection identifier timeout, connection identifier conflict, or binding not accepted; and the fourth indication information is used to request the reassignment of the connection identifier.

[0275] In one possible implementation, the aforementioned third message may be sent via the control plane.

[0276] In the connection management device provided in this application embodiment, when the second timer times out, the third timer times out, or the first connection identifier is not within the valid time during the process of establishing a user plane connection between the network-side device and the terminal, the connection management device can perform at least one of the following actions: sending a binding request message to the network-side device, releasing the first connection identifier, releasing the user plane connection, sending a third message to the network-side device to indicate that the establishment of the user plane connection has failed, and changing the positioning protocol scheme. Therefore, the terminal can avoid occupying the first connection identifier for a long time, so that the network-side device can reallocate the first connection identifier, thereby saving resources.

[0277] The connection management device provided in this application embodiment can implement the various processes implemented in the above terminal-side method embodiment and achieve the same technical effect. To avoid repetition, it will not be described again here.

[0278] like Figure 10 As shown, this application embodiment also provides a communication device 100, including a processor 101 and a memory 102. The memory 102 stores programs or instructions that can run on the processor 101. For example, when the communication device 100 is a terminal, the program or instructions executed by the processor 101 implement the various steps of the above-described terminal-side method embodiment and achieve the same technical effect. When the communication device 100 is a network-side device, the program or instructions executed by the processor 101 implement the various steps of the above-described network-side device method embodiment and achieve the same technical effect. To avoid repetition, further details are omitted here.

[0279] This application also provides a terminal, including a processor and a communication interface, wherein the communication interface is coupled to the processor, and the processor is used to run programs or instructions to implement the steps in the above-described terminal-side method embodiments. This terminal embodiment corresponds to the above-described terminal-side method embodiments; all implementation processes and methods of the above method embodiments can be applied to this terminal embodiment and achieve the same technical effects. The terminal can be... Figure 9 The connection management device shown. Specifically, Figure 11 A schematic diagram of the hardware structure of a terminal to implement an embodiment of this application.

[0280] The terminal 1000 includes, but is not limited to, at least some of the following components: radio frequency unit 1001, network module 1002, audio output unit 1003, input unit 1004, sensor 1005, display unit 1006, user input unit 1007, interface unit 1008, memory 1009, and processor 1010.

[0281] Those skilled in the art will understand that the terminal 1000 may also include a power supply (such as a battery) for supplying power to various components. The power supply may be logically connected to the processor 1010 through a power management system, thereby enabling functions such as managing charging, discharging, and power consumption through the power management system. Figure 11 The terminal structure shown does not constitute a limitation on the terminal. The terminal may include more or fewer components than shown, or combine certain components, or have different component arrangements, which will not be elaborated here.

[0282] It should be understood that, in this embodiment, the input unit 1004 may include a graphics processor 10041 and a microphone 10042. The graphics processor 10041 processes image data of still images or videos obtained by an image capture device (such as a camera) in video capture mode or image capture mode. The display unit 1006 may include a display panel 10061, which may be configured in the form of a liquid crystal display, an organic light-emitting diode, or the like. The user input unit 1007 includes a touch panel 10071 and at least one of other input devices 10072. The touch panel 10071 is also called a touch screen. The touch panel 10071 may include a touch detection device and a touch controller. Other input devices 10072 may include, but are not limited to, physical keyboards, function keys (such as volume control buttons, power buttons, etc.), trackballs, mice, and joysticks, which will not be described in detail here.

[0283] In this embodiment, after receiving downlink data from the network-side device, the radio frequency unit 1001 can transmit it to the processor 1010 for processing; in addition, the radio frequency unit 1001 can send uplink data to the network-side device. Typically, the radio frequency unit 1001 includes, but is not limited to, antennas, amplifiers, transceivers, couplers, low-noise amplifiers, duplexers, etc.

[0284] The memory 1009 can be used to store software programs or instructions, as well as various data. The memory 1009 may primarily include a first storage area for storing programs or instructions and a second storage area for storing data. The first storage area may store the operating system, application programs or instructions required for at least one function (such as sound playback, image playback, etc.). Furthermore, the memory 1009 may include volatile memory or non-volatile memory. The non-volatile memory may be read-only memory (ROM), programmable read-only memory (PROM), erasable programmable read-only memory (EPROM), electrically erasable programmable read-only memory (EEPROM), or flash memory. Volatile memory can be random access memory (RAM), static random access memory (SRAM), dynamic random access memory (DRAM), synchronous dynamic random access memory (SDRAM), double data rate synchronous dynamic random access memory (DDRSDRAM), enhanced synchronous dynamic random access memory (ESDRAM), synchronous link dynamic random access memory (SLDRAM), and direct memory bus RAM (DRRAM). The memory 1009 in this embodiment includes, but is not limited to, these and any other suitable types of memory.

[0285] The processor 1010 may include one or more processing units; optionally, the processor 1010 integrates an application processor and a modem processor, wherein the application processor mainly handles operations involving the operating system, user interface, and applications, and the modem processor mainly handles wireless communication signals, such as a baseband processor. It is understood that the aforementioned modem processor may also not be integrated into the processor 1010.

[0286] The processor 1010 can be used to perform a second operation if a second condition is met during the process of establishing a user plane connection between the network-side device and the terminal 1000. The second condition includes at least one of the following: a second timer times out, which is associated with at least one of the following: a first connection identifier, the initiation of the binding process of the terminal 1000; a third timer times out, which is associated with at least one of the following: the first connection identifier, the binding process of the terminal 1000, the establishment process of the user plane connection; the first connection identifier is not within its valid time. The second operation includes at least one of the following: sending a binding request message to the network-side device; releasing the first connection identifier; releasing the user plane connection; sending a third message to the network-side device, which indicates that the establishment of the user plane connection failed; and changing the positioning protocol scheme.

[0287] In one possible implementation, the processor 1010 can also be used to start the second timer upon receiving a second message from the network-side device before performing the second operation described above. The second message is used to instruct the terminal 1000 to establish a user plane connection with the network-side device.

[0288] In one possible implementation, the second message may include at least one of the following: the first connection identifier, the terminal identifier of terminal 1000, the relevant information of the second timer, and first time information. The second timer is associated with at least one of the following: the first connection identifier, the initiation of the binding process of terminal 1000, and the first time information indicating the validity period of the first connection identifier.

[0289] In one possible implementation, the terminal 1000 may determine whether the first connection identifier is within a valid time period based on the aforementioned first time information.

[0290] In one possible implementation, the radio frequency unit 1001 can be used to send a binding request message to the network-side device when a third condition is met. The binding request message is used to bind the user plane connection and the terminal 1000, and includes at least one of the following: a third connection identifier and a terminal identifier of the terminal 1000. The third condition includes any one of the following: the second timer has not expired, or the first connection identifier is within its valid time.

[0291] In one possible implementation, the aforementioned binding request message can be sent through the user plane.

[0292] In one possible implementation, the radio frequency unit 1001 can also be used to receive a binding response message sent by the network-side device after sending the binding request message to the network-side device. The binding response message includes at least one of the following: second indication information, the aforementioned third connection identifier, a first reason value, and third indication information. Specifically, the second indication information indicates whether the binding corresponding to the binding request message is accepted or rejected; the first reason value indicates the reason for rejecting the binding corresponding to the binding request message; and the third indication information indicates that the terminal 1000 releases the user plane connection.

[0293] In one possible implementation, the aforementioned first reason value can specifically be used to indicate at least one of the following: invalid connection identifier, connection identifier timeout, connection identifier conflict, or binding not accepted.

[0294] In one possible implementation, the aforementioned binding reply message can be sent through the user plane.

[0295] In one possible implementation, the processor 1010 can also be used to perform a third operation after the radio frequency unit 1001 sends the aforementioned binding request message to the network-side device. This third operation includes at least one of the following: stopping the aforementioned second timer; and starting the aforementioned third timer.

[0296] In one possible implementation, the radio frequency unit 1001 can also be used to receive a first message sent by the network-side device during the operation of the second timer after the processor 1010 starts the second timer. The first message includes at least one of the following: a second connection identifier, a terminal identifier of the terminal 1000, and first indication information. The first indication information is used to instruct the terminal 1000 to initiate a binding process using the second connection identifier.

[0297] In one possible implementation, the processor 1010 can also be used to perform a fourth operation based on the first message sent by the network-side device after the radio frequency unit 1001 receives the first message. The fourth operation includes any one of the following: ignoring the first message; restarting the second timer; or sending a binding request message to the network-side device.

[0298] In one possible implementation, the processor 1010 can be specifically used to: ignore the first message if the second connection identifier is the same as the first connection identifier; or, restart the second timer and send the binding request message to the network-side device if the second connection identifier is different from the first connection identifier.

[0299] In one possible implementation, the third message may include at least one of the following: a second reason value and a fourth indication information; wherein the second reason value is used to indicate at least one of the following: binding failure, TLS failure, session failure, invalid connection identifier, connection identifier timeout, connection identifier conflict, or binding not accepted; and the fourth indication information is used to request the reassignment of the connection identifier.

[0300] In one possible implementation, the aforementioned third message may be sent via the control plane.

[0301] In the terminal provided in this application embodiment, during the process of establishing a user plane connection between the network-side device and the terminal, when the second timer times out, the third timer times out, or the first connection identifier is not within the valid time, the terminal can perform at least one of the following actions: sending a binding request message to the network-side device, releasing the first connection identifier, releasing the user plane connection, sending a third message to the network-side device to indicate that the establishment of the user plane connection has failed, and changing the positioning protocol scheme. Therefore, the terminal can avoid occupying the first connection identifier for a long time ineffectively, so that the network-side device can reallocate the first connection identifier, thereby saving resources.

[0302] It is understood that the implementation process of each implementation method mentioned in this embodiment can refer to the relevant description of the above terminal side method embodiment and achieve the same or corresponding technical effects. To avoid repetition, it will not be described again here.

[0303] This application also provides a network-side device, including a processor and a communication interface. The communication interface is coupled to the processor, and the processor is used to run programs or instructions to implement the steps of the above-described network-side device method embodiments. This network-side device embodiment corresponds to the above-described network-side device method embodiments. All implementation processes and methods of the above method embodiments can be applied to this network-side device embodiment and achieve the same technical effects.

[0304] Specifically, embodiments of this application also provide a network-side device. For example... Figure 12 As shown, the network-side device 1100 includes: a processor 1101, a network interface 1102, and a memory 1103. This network-side device can be... Figure 8 The connection management device shown. The network interface 1102 is, for example, a common public radio interface (CPRI).

[0305] Specifically, the network-side device 1100 in this application embodiment further includes: instructions or programs stored in memory 1103 and executable on processor 1101. The processor 1101 calls the instructions or programs in memory 1103 to execute the method executed by the network-side device and achieve the same technical effect. To avoid repetition, it will not be described in detail here.

[0306] The processor 1101 can be used to perform a first operation if a first condition is met during the process of establishing a user plane connection between the network-side device 1100 and the terminal. The first condition includes at least one of the following: a first timer expires, which is associated with at least one of the following: a first connection identifier, a terminal identifier of the terminal, the terminal binding process, and the user plane connection establishment process; the first connection identifier is not within a valid time period. The first operation includes at least one of the following: releasing the first connection identifier; releasing the user plane connection; sending a first message to the terminal, which instructs the terminal to re-establish the user plane connection with the network-side device 1100; and changing the positioning protocol scheme.

[0307] In one possible implementation, the first message may include at least one of the following: a second connection identifier, a terminal identifier, and first instruction information. The first instruction information is used to instruct the terminal to initiate a binding process using the second connection identifier.

[0308] In one possible implementation, the processor 1101 can also be used to start a first timer before performing the first operation described above, upon sending a second message to the terminal. The second message is used to instruct the terminal to establish a user plane connection with the network-side device 1100.

[0309] In one possible implementation, the second message may include at least one of the following: the first connection identifier, the terminal identifier of the terminal, information related to the second timer, and first time information. The second timer is associated with at least one of the following: the first connection identifier, the initiation of the terminal binding process, and the first time information indicating the validity period of the first connection identifier.

[0310] In one possible implementation, the processor 1101 can also be used to restart the first timer when sending the first message to the terminal, and the first message includes a second connection identifier that is different from the first connection identifier.

[0311] In one possible implementation, network interface 1102 can be used to receive a binding request message sent by the terminal after sending the aforementioned second message to the terminal. The binding request message is used to bind the user plane connection and the terminal, and includes at least one of the following: a third connection identifier and a terminal identifier.

[0312] In one possible implementation, the aforementioned binding request message can be sent through the user plane.

[0313] In one possible implementation, network interface 1102 can also be used to send a binding response message to the terminal after receiving the binding request message sent by the terminal. The binding response message includes at least one of the following: second indication information, the aforementioned third connection identifier, a first reason value, and third indication information. Specifically, the second indication information indicates whether the binding corresponding to the binding request message is accepted or rejected; the first reason value indicates the reason for rejecting the binding corresponding to the binding request message; and the third indication information indicates that the terminal releases the user plane connection.

[0314] In one possible implementation, the aforementioned first reason value can specifically be used to indicate at least one of the following: invalid connection identifier, connection identifier timeout, connection identifier conflict, or binding not accepted.

[0315] In one possible implementation, the aforementioned binding reply message can be sent through the user plane.

[0316] In one possible implementation, the processor 1101 can also be used to stop the first timer after the network interface 1102 receives a binding request message sent by the terminal, provided that the binding request message includes the third connection identifier and the third connection identifier is the same as the first connection identifier.

[0317] In one possible implementation, network interface 1102 can also be used to receive a third message sent by the terminal after sending a binding reply message to the terminal. This third message indicates that the user plane connection establishment failed.

[0318] In one possible implementation, the third message may include at least one of the following: a second reason value and a fourth indication information; wherein the second reason value is used to indicate at least one of the following: binding failure, TLS failure, session failure, invalid connection identifier, connection identifier timeout, connection identifier conflict, or binding not accepted; and the fourth indication information is used to request the reassignment of the connection identifier.

[0319] In one possible implementation, the aforementioned third message may be sent via the control plane.

[0320] In the network-side device provided in this application embodiment, when the first timer expires or the first connection identifier is not within the valid time during the process of establishing a user plane connection between the network-side device and the terminal, the network-side device can perform at least one of the following: releasing the first connection identifier, releasing the user plane connection, sending a first message to the terminal to indicate the re-establishment of the user plane connection, and changing the location protocol scheme. Therefore, the terminal can be prevented from occupying the first connection identifier for a long time, so that the network-side device can reallocate the first connection identifier, thereby saving resources.

[0321] It is understood that the implementation process of each implementation method mentioned in this embodiment can refer to the relevant description of the above network-side device method embodiment and achieve the same or corresponding technical effects. To avoid repetition, it will not be described again here.

[0322] This application also provides a readable storage medium storing a program or instructions. When the program or instructions are executed by a processor, they implement the various processes of the above-described connection management method embodiments and achieve the same technical effects. To avoid repetition, they will not be described again here.

[0323] The processor mentioned above is the processor in the terminal described in the above embodiments. The readable storage medium includes computer-readable storage media, such as computer read-only memory (ROM), random access memory (RAM), magnetic disk, or optical disk. In some examples, the readable storage medium may be a non-transient readable storage medium.

[0324] This application embodiment also provides a chip, which includes a processor and a communication interface. The communication interface is coupled to the processor. The processor is used to run programs or instructions to implement the various processes of the above-described connection management method embodiments and can achieve the same technical effect. To avoid repetition, it will not be described again here.

[0325] It should be understood that the chip mentioned in the embodiments of this application may also be referred to as a system-on-a-chip, system chip, chip system, or system-on-a-chip, etc.

[0326] This application also provides a computer program / program product, which is stored in a storage medium and executed by at least one processor to implement the various processes of the above-described connection management method embodiments, and can achieve the same technical effect. To avoid repetition, it will not be described again here.

[0327] This application also provides a communication system, including: a terminal and a network-side device, wherein the terminal can be used to perform the steps of the terminal-side method as described above, and the network-side device can be used to perform the steps of the network-side device method as described above.

[0328] It should be noted that, in this document, the terms "comprising," "including," or any other variations thereof are intended to cover non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements includes not only those elements but also other elements not expressly listed, or elements inherent to such a process, method, article, or apparatus. Without further limitations, an element defined by the phrase "comprising one..." does not exclude the presence of other identical elements in the process, method, article, or apparatus that includes that element. Furthermore, it should be noted that the scope of the methods and apparatuses in the embodiments of this application is not limited to performing functions in the order shown or discussed, but may also include performing functions substantially simultaneously or in the reverse order, depending on the functions involved. For example, the described methods may be performed in a different order than described, and various steps may be added, omitted, or combined. Additionally, features described with reference to certain examples may be combined in other examples.

[0329] From the above description of the embodiments, those skilled in the art can clearly understand that the methods of the above embodiments can be implemented by means of computer software products plus necessary general-purpose hardware platforms, and of course, they can also be implemented by hardware. The computer software product is stored in a storage medium (such as ROM, RAM, magnetic disk, optical disk, etc.) and includes several instructions to cause the terminal or network-side device to execute the methods described in the various embodiments of this application.

[0330] The embodiments of this application have been described above with reference to the accompanying drawings. However, this application is not limited to the specific embodiments described above. The specific embodiments described above are merely illustrative and not restrictive. Those skilled in the art can make many other implementations under the guidance of this application without departing from the spirit and scope of the claims. All of these implementations are within the protection scope of this application.

Claims

1. A connection management method, characterized in that, The method includes: During the process of establishing a user plane connection between the network-side device and the terminal, if the first condition is met, the network-side device performs the first operation. The first condition includes at least one of the following: The first timer times out, and the first timer is associated with at least one of the following: the first connection identifier, the terminal identifier of the terminal, the binding process of the terminal, and the user plane connection establishment process; The first connection identifier is not within its valid time period; The first operation includes at least one of the following: Release the first connection identifier; Release the user plane connection; Send a first message to the terminal, the first message being used to instruct the terminal to re-establish the user plane connection with the network-side device; Change the positioning protocol scheme.

2. The method according to claim 1, characterized in that, The first message includes at least one of the following: a second connection identifier, a terminal identifier of the terminal, and a first indication message; The first indication information is used to instruct the terminal to initiate a binding process using the second connection identifier.

3. The method according to claim 1 or 2, characterized in that, Before the network-side device performs the first operation, the method further includes: When a second message is sent to the terminal, the network-side device starts a first timer; The second message is used to instruct the terminal to establish a user plane connection with the network-side device.

4. The method according to claim 3, characterized in that, The second message includes at least one of the following: the first connection identifier, the terminal identifier of the terminal, the relevant information of the second timer, and the first time information; The second timer is associated with at least one of the following: the first connection identifier, the initiation of the terminal binding process, and the first time information used to indicate the validity period of the first connection identifier.

5. The method according to claim 3 or 4, characterized in that, The method further includes: When the first message is sent to the terminal, and the first message includes a second connection identifier that is different from the first connection identifier, the network-side device restarts the first timer.

6. The method according to any one of claims 3 to 5, characterized in that, The method further includes: After sending the second message to the terminal, the network-side device receives the binding request message sent by the terminal; The binding request message is used to bind the user plane connection and the terminal, and the binding request message includes at least one of the following: a third connection identifier and a terminal identifier of the terminal.

7. The method according to claim 6, characterized in that, The binding request message is sent through the user plane.

8. The method according to claim 6 or 7, characterized in that, After the network-side device receives the binding request message sent by the terminal, the method further includes: The network-side device sends a binding response message to the terminal, the binding response message including at least one of the following: second indication information, the third connection identifier, a first reason value, and third indication information; The second indication information is used to indicate whether to accept or reject the binding corresponding to the binding request message, the first reason value is used to indicate the reason for rejecting the binding corresponding to the binding request message, and the third indication information is used to indicate that the terminal releases the user plane connection.

9. The method according to claim 8, characterized in that, The first reason value is specifically used to indicate at least one of the following: invalid connection identifier, connection identifier timeout, connection identifier conflict, or binding not accepted.

10. The method according to claim 8 or 9, characterized in that, The binding reply message is sent through the user plane.

11. The method according to any one of claims 6 to 10, characterized in that, After the network-side device receives the binding request message sent by the terminal, the method further includes: If the binding request message includes the third connection identifier and the third connection identifier is the same as the first connection identifier, the network-side device stops the first timer.

12. The method according to any one of claims 8 to 11, characterized in that, After the network-side device sends a binding reply message to the terminal, the method further includes: The network-side device receives a third message sent by the terminal; The third message is used to indicate that the establishment of a user plane connection failed.

13. The method according to claim 12, characterized in that, The third message includes at least one of the following: a second cause value, a fourth indication message; The second reason value is used to indicate at least one of the following: binding failure, Transport Layer Security (TLS) failure, session failure, invalid connection identifier, connection identifier timeout, connection identifier conflict, or binding not accepted; the fourth indication information is used to request the reassignment of the connection identifier.

14. The method according to claim 12 or 13, characterized in that, The third message is sent via the control plane.

15. A connection management method, characterized in that, The method includes: During the process of establishing a user plane connection between the network-side device and the terminal, if the second condition is met, the terminal performs the second operation. The second condition includes at least one of the following: The second timer times out, and the second timer is associated with at least one of the following: the first connection identifier, and the initiation of the terminal binding process; The third timer times out, and the third timer is associated with at least one of the following: the first connection identifier, the binding process of the terminal, and the user plane connection establishment process; The first connection identifier is not within its valid time period; The second operation includes at least one of the following: Send a binding request message to the network-side device; Release the first connection identifier; Release the user plane connection; Send a third message to the network-side device, the third message indicating that the establishment of the user plane connection failed; Change the positioning protocol scheme.

16. The method according to claim 15, characterized in that, Before the terminal performs the second operation, the method further includes: Upon receiving the second message sent by the network-side device, the terminal starts the second timer; The second message is used to instruct the terminal to establish a user plane connection with the network-side device.

17. The method according to claim 16, characterized in that, The second message includes at least one of the following: the first connection identifier, the terminal identifier of the terminal, the relevant information of the second timer, and the first time information; The second timer is associated with at least one of the following: the first connection identifier, the initiation of the terminal binding process, and the first time information used to indicate the validity period of the first connection identifier.

18. The method according to claim 17, characterized in that, The terminal determines whether the first connection identifier is within a valid time period based on the first time information.

19. The method according to any one of claims 16 to 18, characterized in that, The method further includes: If the third condition is met, the terminal sends a binding request message to the network-side device; The binding request message is used to bind the user plane connection and the terminal. The binding request message includes at least one of the following: a third connection identifier and a terminal identifier of the terminal. The third condition includes any one of the following: the second timer has not expired and the first connection identifier is within a valid time.

20. The method according to claim 19, characterized in that, The binding request message is sent through the user plane.

21. The method according to claim 19 or 20, characterized in that, After the terminal sends a binding request message to the network-side device, the method further includes: The terminal receives a binding response message sent by the network-side device. The binding response message includes at least one of the following: second indication information, the third connection identifier, a first reason value, and third indication information. The second indication information is used to indicate whether to accept or reject the binding corresponding to the binding request message, the first reason value is used to indicate the reason for rejecting the binding corresponding to the binding request message, and the third indication information is used to indicate that the terminal releases the user plane connection.

22. The method according to claim 21, characterized in that, The first reason value is specifically used to indicate at least one of the following: invalid connection identifier, connection identifier timeout, connection identifier conflict, or binding not accepted.

23. The method according to claim 21 or 22, characterized in that, The binding reply message is sent through the user plane.

24. The method according to any one of claims 19 to 23, characterized in that, After the terminal sends a binding request message to the network-side device, the method further includes: The terminal performs a third operation; The third operation includes at least one of the following: Stop the second timer; Start the third timer.

25. The method according to any one of claims 16 to 24, characterized in that, After the terminal starts the second timer, the method further includes: The terminal receives a first message sent by the network-side device during the operation of the second timer. The first message includes at least one of the following: a second connection identifier, the terminal identifier of the terminal, and first indication information. The first indication information is used to instruct the terminal to initiate a binding process using the second connection identifier.

26. The method according to claim 25, characterized in that, After the terminal receives the first message sent by the network-side device, the method further includes: Based on the first message, the terminal performs the fourth operation; The fourth operation includes any one of the following: Ignore the first message; Restart the second timer; Send a binding request message to the network-side device.

27. The method according to claim 26, characterized in that, Based on the first message, the terminal performs a fourth operation, including: If the second connection identifier is the same as the first connection identifier, the terminal ignores the first message; or, If the second connection identifier is different from the first connection identifier, the terminal restarts the second timer and sends the binding request message to the network-side device.

28. The method according to any one of claims 15 to 27, characterized in that, The third message includes at least one of the following: a second cause value, a fourth indication message; The second reason value is used to indicate at least one of the following: binding failure, TLS failure, session failure, invalid connection identifier, connection identifier timeout, connection identifier conflict, or binding not accepted; the fourth indication information is used to request the reassignment of the connection identifier.

29. The method according to any one of claims 15 to 28, characterized in that, The third message is sent via the control plane.

30. A connection management device, characterized in that, The device includes a first processing module; The first processing module is used to perform a first operation if a first condition is met during the process of establishing a user plane connection between the network-side device and the terminal. The first condition includes at least one of the following: The first timer times out, and the first timer is associated with at least one of the following: the first connection identifier, the terminal identifier of the terminal, the binding process of the terminal, and the user plane connection establishment process; The first connection identifier is not within its valid time period; The first operation includes at least one of the following: Release the first connection identifier; Release the user plane connection; Send a first message to the terminal, the first message being used to instruct the terminal to re-establish the user plane connection with the network-side device; Change the positioning protocol scheme.

31. The apparatus according to claim 30, characterized in that, The first processing module is further configured to start a first timer before performing the first operation, in the case of sending a second message to the terminal; The second message is used to instruct the terminal to establish a user plane connection with the network-side device.

32. The apparatus according to claim 30, characterized in that, The first processing module is further configured to restart the first timer when sending the first message to the terminal, and the first message includes a second connection identifier that is different from the first connection identifier.

33. The apparatus according to claim 31 or 32, characterized in that, The device further includes a first receiving module; The first receiving module is configured to receive a binding request message sent by the terminal after sending the second message to the terminal; The binding request message is used to bind the user plane connection and the terminal, and the binding request message includes at least one of the following: a third connection identifier and a terminal identifier of the terminal.

34. The apparatus according to claim 33, characterized in that, The device also includes a first transmitting module; The first sending module is configured to send a binding reply message to the terminal after the first receiving module receives the binding request message sent by the terminal. The binding reply message includes at least one of the following: second indication information, the third connection identifier, a first reason value, and third indication information. The second indication information is used to indicate whether to accept or reject the binding corresponding to the binding request message, the first reason value is used to indicate the reason for rejecting the binding corresponding to the binding request message, and the third indication information is used to indicate that the terminal releases the user plane connection.

35. The apparatus according to claim 33 or 34, characterized in that, The first processing module is further configured to stop the first timer after the first receiving module receives the binding request message sent by the terminal, provided that the binding request message includes the third connection identifier and the third connection identifier is the same as the first connection identifier.

36. The apparatus according to claim 34, characterized in that, The first receiving module is further configured to receive a third message sent by the terminal after the first sending module sends a binding reply message to the terminal; The third message is used to indicate that the establishment of a user plane connection failed.

37. A connection management device, characterized in that, The device includes a second processing module; The second processing module is used to perform a second operation if a second condition is met during the process of establishing a user plane connection between the network-side device and the terminal. The second condition includes at least one of the following: The second timer times out, and the second timer is associated with at least one of the following: the first connection identifier, and the initiation of the terminal binding process; The third timer times out, and the third timer is associated with at least one of the following: the first connection identifier, the binding process of the terminal, and the user plane connection establishment process; The first connection identifier is not within its valid time period; The second operation includes at least one of the following: Send a binding request message to the network-side device; Release the first connection identifier; Release the user plane connection; Send a third message to the network-side device, the third message indicating that the establishment of the user plane connection failed; Change the positioning protocol scheme.

38. The apparatus according to claim 37, characterized in that, The second processing module is further configured to start the second timer upon receiving a second message from the network-side device before performing the second operation; The second message is used to instruct the terminal to establish a user plane connection with the network-side device.

39. The apparatus according to claim 38, characterized in that, The device also includes a second transmitting module; The second sending module is used to send a binding request message to the network-side device when the third condition is met; The binding request message is used to bind the user plane connection and the terminal. The binding request message includes at least one of the following: a third connection identifier and a terminal identifier of the terminal. The third condition includes any one of the following: the second timer has not expired and the first connection identifier is within a valid time.

40. The apparatus according to claim 39, characterized in that, The device also includes a second receiving module; The second receiving module is configured to receive a binding reply message sent by the network-side device after the second sending module sends a binding request message to the network-side device. The binding reply message includes at least one of the following: second indication information, the third connection identifier, a first reason value, and third indication information. The second indication information is used to indicate whether to accept or reject the binding corresponding to the binding request message, the first reason value is used to indicate the reason for rejecting the binding corresponding to the binding request message, and the third indication information is used to indicate that the terminal releases the user plane connection.

41. The apparatus according to claim 39 or 40, characterized in that, The second processing module is further configured to perform a third operation after the second sending module sends a binding request message to the network-side device; The third operation includes at least one of the following: Stop the second timer; Start the third timer.

42. The apparatus according to claim 38, characterized in that, The device also includes a second receiving module; The second receiving module is configured to receive a first message sent by the network-side device during the operation of the second timer after the second processing module starts the second timer, wherein the first message includes at least one of the following: a second connection identifier, a terminal identifier of the terminal, and first indication information; The first indication information is used to instruct the terminal to initiate a binding process using the second connection identifier.

43. The apparatus according to claim 42, characterized in that, The second processing module is further configured to perform a fourth operation based on the first message after the second receiving module receives the first message sent by the network-side device; The fourth operation includes any one of the following: Ignore the first message; Restart the second timer; Send a binding request message to the network-side device.

44. A network-side device, characterized in that, It includes a processor and a memory, the memory storing a program or instructions that can run on the processor, the program or instructions being executed by the processor to implement the steps of the connection management method as described in any one of claims 1 to 14.

45. A terminal, characterized in that, It includes a processor and a memory, the memory storing a program or instructions that can run on the processor, the program or instructions being executed by the processor to implement the steps of the connection management method as described in any one of claims 15 to 29.

46. ​​A readable storage medium, characterized in that, The readable storage medium stores a program or instructions that, when executed by a processor, implement the connection management method as described in any one of claims 1 to 14, or implement the steps of the connection management method as described in any one of claims 15 to 29.

Images