WO2025237207A1 - 连接管理方法、装置、终端及网络侧设备 - Google Patents

连接管理方法、装置、终端及网络侧设备

Info

Publication number
WO2025237207A1
WO2025237207A1 PCT/CN2025/093965 CN2025093965W WO2025237207A1 WO 2025237207 A1 WO2025237207 A1 WO 2025237207A1 CN 2025093965 W CN2025093965 W CN 2025093965W WO 2025237207 A1 WO2025237207 A1 WO 2025237207A1
Authority
WO
WIPO (PCT)
Prior art keywords
terminal
connection
message
binding
connection identifier
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Pending
Application number
PCT/CN2025/093965
Other languages
English (en)
French (fr)
Inventor
于航
张奕忠
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Vivo Mobile Communication Co Ltd
Original Assignee
Vivo Mobile Communication Co Ltd
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Vivo Mobile Communication Co Ltd filed Critical Vivo Mobile Communication Co Ltd
Publication of WO2025237207A1 publication Critical patent/WO2025237207A1/zh
Pending legal-status Critical Current
Anticipated expiration legal-status Critical

Links

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W76/00—Connection management
    • H04W76/10—Connection setup

Definitions

  • This application belongs to the field of communication technology, specifically relating to a connection management method, apparatus, terminal, and network-side equipment.
  • 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.
  • LMF Location Management Function
  • 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.
  • 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.
  • a connection management method 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.
  • a connection management method 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.
  • a connection management device 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.
  • 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 connection management device 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.
  • connection management device 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.
  • a 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.
  • a network-side device 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.
  • 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
  • a 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.
  • 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.
  • a readable storage medium 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.
  • a wireless communication system 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.
  • a 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.
  • 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.
  • 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.
  • 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.
  • Figure 1 is a block diagram of a wireless communication system applicable to an embodiment of this application
  • Figure 2 is a flowchart of establishing a user plane connection in related technologies
  • FIG. 3 is a flowchart of a connection management method provided in an embodiment of this application.
  • Figure 4 is one of the flowcharts for establishing a user plane connection in a connection management method provided in an embodiment of this application;
  • FIG. 5 is a flowchart of another connection management method provided in an embodiment of this application.
  • Figure 6 is a second flowchart of establishing a user plane connection in a connection management method provided in an embodiment of this application;
  • Figure 7 is a flowchart of establishing a user plane connection in a connection management method provided in an embodiment of this application.
  • Figure 8 is a structural schematic diagram of a connection management device provided in an embodiment of this application.
  • FIG. 9 is a schematic diagram of another connection management device provided in an embodiment of this application.
  • Figure 10 is a schematic diagram of the communication device provided in an embodiment of this application.
  • FIG 11 is a schematic diagram of the hardware structure of the terminal provided in an embodiment of this application.
  • Figure 12 is a schematic diagram of the hardware structure of the network-side device provided in an embodiment of this application.
  • first and second 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.
  • “or” in this application indicates at least one of the connected objects.
  • 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.
  • 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.
  • 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.
  • LTE Long Term Evolution
  • LTE-A Long Term Evolution-Advanced
  • CDMA Code Division Multiple Access
  • TDMA Time Division Multiple Access
  • FDMA Frequency Division Multiple Access
  • OFDMA Orthogonal Frequency Division Multiple Access
  • SC-FDMA Single-carrier Frequency-Division Multiple Access
  • NR New Radio
  • FIG. 1 shows a block diagram of a wireless communication system applicable to an embodiment of this application.
  • the wireless communication system includes a terminal 11 and a network-side device 12.
  • 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 (home devices with wireless communication capabilities, such as refrigerators, televisions, washing machines, or furniture), game console, personal computer (PC), ATM, or self-service machine, etc.
  • PDA personal digital assistant
  • UMPC ultra-mobile personal computer
  • MID mobile internet device
  • AR augmented reality
  • VR virtual reality
  • robot wearable device
  • flight vehicle vehicle user equipment
  • VUE shipboard equipment
  • pedestrian user equipment PUE
  • smart home home devices with wireless communication capabilities, such as refrigerators, televisions, washing machines
  • 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.
  • 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.
  • WLAN Wireless Local Area Network
  • WiFi Wireless Fidelity
  • a base station may be referred to as a 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 base station is not limited to specific technical terms. It should be noted that in this application embodiment, only a base station in an NR system is used as an example for introduction, and the specific type of base station is not limited.
  • 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), and Unified Data Warehouse (UDM).
  • MME Mobility Management Entity
  • AMF Access and Mobility Management Function
  • SMF Session Management Function
  • UPF User Plane Function
  • PCF Policy Control Function
  • PCF Policy and Charging Rules Function
  • EASDF Edge Application Server Discovery Function
  • UDM Unified Data Management
  • UDM Unified Data Management
  • UDM Unified Data Warehouse
  • the core network equipment includes: Data Repository (UDR), Home Subscriber Server (HSS), Centralized Network Configuration (CNC), Network Repository Function (NRF), Network Exposure Function (NEF), Local NEF (or L-NEF), Binding Support Function (BSF), Application Function (AF), Location Management Function (LMF), Gateway Mobile Location Centre (GMLC), and Network Data Analytics Function (NWDAF).
  • UDR Data Repository
  • HSS Home Subscriber Server
  • CNC Centralized Network Configuration
  • NEF Network Exposure Function
  • L-NEF Local NEF
  • BSF Binding Support Function
  • AF Application Function
  • LMF Location Management Function
  • GMLC Gateway Mobile Location Centre
  • NWDAF Network Data Analytics Function
  • 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).
  • a platform e.g., a cloud platform
  • 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.
  • the LMF and the terminal can exchange some configuration information via control plane signaling to establish a user plane connection and transmit LTE Positioning Protocol (LPP) messages or Location Service (LCS)-SS messages on the user plane.
  • LPF LTE Positioning Protocol
  • LCS Location Service
  • FIG 2 shows a flowchart of establishing a user plane connection.
  • the LMF and the terminal can establish a user plane connection through signaling interaction.
  • step 7 is enhanced as follows:
  • 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.
  • association process or binding process will be collectively referred to as binding process or binding in the following text.
  • connection identifier e.g., LCS-UP connection ID
  • LCS-UP connection ID e.g., LCS-UP connection ID
  • LMF Transport Layer Security
  • connection identifier 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.
  • 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.
  • 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.
  • connection management method provides 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.
  • 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.
  • 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.
  • 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.
  • connection management method provides a connection management method
  • Figure 3 shows a flowchart of the connection management method provided in this application.
  • the connection management method provided in this application may include the following step 301.
  • 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.
  • the first condition mentioned above includes at least one of the following:
  • 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;
  • the first connection identifier is not within its valid time period
  • the first operation mentioned above includes at least one of the following:
  • the network-side device can be a device with location management function, such as an LMF.
  • the first message mentioned above may include the LMF LCS-UP address.
  • 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.
  • PDU Packet Data Unit Session
  • 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.
  • 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".
  • the first timer mentioned above may be started by the network-side device after receiving the user plane connection establishment confirmation message.
  • 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.
  • the first timer mentioned above can be timer T5012 (TS24.572v18.0.0) or a newly added timer for the binding process.
  • this first timer can be started when the network-side device sends a user plane connection establishment command message (e.g., a user plane connection establishment 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.
  • a user plane connection establishment command message e.g., a user plane connection establishment command message
  • a binding request message e.g., a binding request message
  • 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.
  • the first connection identifier is used to identify the user plane connection and the terminal.
  • the first connection identifier may be an LCS-UP connection identifier, an LCS-UP binding identifier (e.g., LCS-UP binding ID), or an LCS-UP connection correlation identifier, etc.
  • the terminal identifier is used to identify the terminal.
  • the terminal identifier may be a Subscription Permanent Identifier (SUPI) or a Generic Public Subscription Identifier (GPSI), etc.
  • SUPI Subscription Permanent Identifier
  • GPSI Generic Public Subscription Identifier
  • the validity period of the first connection identifier can be configured by the network-side device.
  • the first connection identifier 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.
  • 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 plane connection release procedure), removal, and deletion.
  • local release e.g., locally release
  • signaling procedures e.g., network requested user plane connection release procedure
  • removal e.g., deletion, deletion, and deletion.
  • the above-mentioned release of the first connection identifier can also be understood as: treating the first connection identifier as expired or invalid.
  • releasing the user plane connection may include: releasing the context of the terminal, including the association between the first connection identifier and the terminal.
  • the above-mentioned location protocol replacement scheme can be understood as: replacing the scheme using user plane positioning with other location protocol schemes.
  • the other positioning protocol schemes mentioned above may include: a control plane positioning scheme or a Secure User Plane Location (SUPL) scheme for transmitting LPP messages, LCS-SS messages, etc.
  • SUPL Secure User Plane Location
  • the first message mentioned above may be a user plane connection establishment command (e.g., user plane connection establishment command message).
  • 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.
  • the first instruction information is used to instruct the terminal to initiate the binding process using the second connection identifier.
  • 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.
  • LCS user plane connection which can also be understood as TLS connection
  • association relationship which is used by the network-side device to determine the terminal and the user plane connection one-to-one.
  • the second connection identifier may be the same as or different from the first connection identifier.
  • the network-side device 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.
  • the terminal 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.
  • the network-side device 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.
  • connection management method provided in this embodiment of the application may further include the following step A.
  • Step A The network-side device sends a second message to the terminal.
  • 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.
  • the second message mentioned above may be a user plane connection establishment command (e.g., user plane connection establishment command message).
  • both the first message and the second message mentioned above can be user plane connection establishment commands.
  • 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.
  • 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.
  • the second message may also include the LMF LCS-UP address (e.g., LMF LCS-UP address).
  • the user plane connection established by the second message mentioned above is the same as the user plane connection in step 301 above.
  • 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.
  • 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.
  • the relevant information of the second timer may include the duration corresponding to the second timer.
  • the second timer can be a timer in the General Packet Radio Service (GPRS) 3 format 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.
  • GPRS General Packet Radio Service
  • 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.
  • 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.
  • 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.
  • 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.
  • 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.
  • connection management method provided in this embodiment of the application may further include step 302 below.
  • Step 302 When the second message is sent to the terminal, the network-side device starts the first timer.
  • 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.
  • the network-side device can start the first timer immediately or start the first timer after a preset duration.
  • 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.
  • connection management method provided in this application embodiment may further include the following step 303.
  • 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.
  • 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.
  • the network-side device 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.
  • connection management method provided in this application embodiment may further include the following step 304.
  • Step 304 After sending the second message to the terminal, the network-side device receives the binding request message sent by the terminal.
  • 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.
  • 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.
  • the third connection identifier may be the same as or different from the first connection identifier.
  • 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.
  • the binding request message may be sent through the user plane.
  • the network-side device 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.
  • connection management method provided in this embodiment of the application may further include step 305 below.
  • 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.
  • 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.
  • 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.
  • connection management method provided in this embodiment of the application may further include step 306 below.
  • Step 306 The network-side device sends a binding reply message to the terminal.
  • 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.
  • 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
  • the third indication information is used to indicate that the terminal releases the user plane connection.
  • 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 acceptance message (e.g., binding accept message), and the other is a binding rejection 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.
  • message type e.g., message type
  • binding acceptance message e.g., binding accept message
  • binding rejection message e.g., binding reject message
  • 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.
  • the third connection identifier is the connection identifier associated with the binding reply message.
  • the above-mentioned binding reply message may be sent through the user plane.
  • 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., bind not accepted), protocol error (e.g., protocol error, unspecified).
  • 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., bind not accepted
  • protocol error e.g., protocol error, unspecified
  • connection identifier timeout can also be understood as the connection identifier expiring.
  • connection identifier conflict may include: the connection identifier is already bound or occupied.
  • the network-side device when the binding request message is accepted, 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.
  • 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).
  • 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.
  • the LMF 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 has been 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 has been bound, occupied, or conflicted.
  • a first reason value indicating that the connection identifier has been bound or occupied
  • the network-side device sends a binding rejection message to the terminal, carrying a first reason value indicating that the connection identifier has been bound, occupied, or conflicted.
  • 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.
  • 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.
  • the correct terminal 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.
  • 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.
  • UPF-CMI User Plane Positioning Connection Management Information
  • 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.
  • the terminal can include an indication in a user plane connection failure message to inform the network-side device that the connection identifier assigned to the terminal has conflicted during binding, or that the connection identifier has been misused, or to request the network-side device to assign a new connection identifier.
  • the network-side device 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 allows for the correction of occupied connection identifiers or mis-binding.
  • the aforementioned request for the network-side device to allocate a new connection identifier avoids reusing the previously conflicting identifier, mitigating the conflict issue during subsequent bindings.
  • the network-side device after receiving the binding request message sent by the terminal, 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.
  • connection management method provided in this embodiment of the application may further include step 307 below.
  • Step 307 The network-side device receives the third message sent by the terminal.
  • 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 reject message).
  • 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.
  • the aforementioned fourth instruction message is sent by the terminal to the network-side device in the event of a connection establishment failure. Its purpose is to enable the terminal to proactively identify problems discovered during the connection 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.
  • this fourth instruction message if the terminal still wishes to request a user plane connection, it no longer needs to send another user plane connection establishment request message (e.g., a user plane connection establishment request message). Instead, the network-side device can directly send a new user plane connection establishment command message (e.g., a user plane connection establishment command message) carrying the new connection identifier to the terminal, thus saving signaling interaction.
  • the aforementioned third message may be sent via the control plane.
  • the network-side device may perform the aforementioned first operation.
  • the network-side device after 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.
  • the network-side device 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.
  • the process of establishing a user plane connection between the terminal and LMF includes the following steps 1 to 6:
  • Step 1 If initiated by the terminal, the terminal sends a user plane connection establishment request (e.g., user plane connection establishment request message) to the LMF to request the establishment of an LCS-secure user plane connection between the terminal and the LMF.
  • a user plane connection establishment request e.g., user plane connection establishment request message
  • 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.
  • 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.
  • Step 4 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.
  • 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.
  • 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:
  • timer 1 e.g., T5012
  • the terminal receives a user plane connection establishment command message during the LCS-UP binding process, and:
  • 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;
  • LCS-UP connection identifier contained in the user plane connection establishment command e.g., USER PLANE CONNECTION ESTABLISHMENT COMMAND
  • LCS-UP binding request e.g., LCS-UP BINDING REQUEST
  • 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.
  • the terminal receives a user plane connection establishment command message during the LCS-UP binding process, and:
  • 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;
  • the LCS-UP connection identifier in the user plane connection establishment command message (e.g., USER PLANE CONNECTION ESTABLISHMENT COMMAND) is different from the LCS-UP connection identifier in the LCS-UP binding request message (e.g., LCS-UP BINDING REQUEST); or,
  • the terminal should then abort the LCS-UP binding process, stop timer 3, and continue processing the latest user plane connection establishment command message.
  • Step 5 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:
  • 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.
  • 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:
  • Stop Timer 3 After receiving the LCS-UP binding response, if Timer 3 is still running, the terminal will stop Timer 3.
  • 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.
  • the terminal 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.
  • step 2 when the LMF allocates the connection identifier, it internally maintains a mapping relationship between terminal identifiers and connection identifiers.
  • the LMF knows which terminal or connection identifier it is.
  • 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.
  • 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.
  • 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.
  • the LMF Upon receiving the "user plane connection establishment failure" message, the LMF performs the first operation described above.
  • this message may carry a cause value and/or a 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
  • the fourth indication 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).
  • the terminal can re-establish the user plane connection with the LMF.
  • 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.
  • FIG. 5 shows a flowchart of the connection management method provided in this application. As shown in Figure 5, the connection management method provided in this application may include the following step 501.
  • 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.
  • the second condition mentioned above includes at least one of the following:
  • 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;
  • 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;
  • the first connection identifier is not within its valid time period
  • the second operation mentioned above includes at least one of the following:
  • the aforementioned third message may be a user plane connection establishment failure message or a user plane connection establishment command reject message.
  • 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.
  • the aforementioned third message may be sent via the control plane.
  • 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.
  • connection management method provided in this embodiment of the application may further include step 502 below.
  • Step 502 Upon receiving the second message sent by the network-side device, the terminal starts the second timer.
  • the second message mentioned above is used to instruct the terminal to establish a user plane connection with the network-side device.
  • 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.
  • 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.
  • the terminal may determine whether the first connection identifier is within the valid time period based on the first time information mentioned above.
  • the above-mentioned first-time information can be implemented as shown in the table below:
  • connection management method provided in this application embodiment may further include the following step 503.
  • Step 503 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 the valid time.
  • the binding request message may be sent through the user plane.
  • the terminal 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.
  • connection management method provided in this embodiment of the application may further include step 504 below.
  • Step 504 The terminal receives the binding reply message sent by the network-side device.
  • 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.
  • 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
  • the third indication information is used to indicate that the terminal releases the user plane connection.
  • 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.
  • the above-mentioned binding reply message may be sent through the user plane.
  • connection management method provided in this embodiment of the application may further include step 505 below.
  • Step 505 The terminal performs the third operation.
  • the third operation mentioned above includes at least one of the following:
  • the terminal may start the above-mentioned third timer.
  • connection management method provided in this embodiment of the application may further include step 506 below.
  • Step 506 The terminal receives the first message sent by the network-side device while the second timer is running.
  • 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.
  • the first instruction information is used to instruct the terminal to initiate the binding process using the second connection identifier.
  • connection management method provided in this embodiment of the application may further include step 507 below.
  • Step 507 The terminal performs the fourth operation based on a message.
  • the fourth operation mentioned above includes any one of the following:
  • step 507 can be implemented by step 507a or step 507b as described below.
  • Step 507a If the second connection identifier is the same as the first connection identifier, the terminal ignores the first message.
  • 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.
  • the process of establishing a user plane connection between the terminal and the LMF includes steps 1 to 6 below.
  • the message in step 2 can also carry a timer 2.
  • 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 steps.
  • the terminal stops timer 2.
  • the process of establishing a user plane connection between the terminal and LMF includes the following steps 1 to 6.
  • the message in step 2 can also carry first time information, so that the LCS-UP connection identifier can be determined by detecting the first time information, thereby flexibly and accurately releasing resources.
  • 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.
  • 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.
  • the terminal may include, but is not limited to, the type of terminal 11 listed above
  • 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.
  • the connection management device includes a receiving module, a transmitting module, and a processing module. These modules can be implemented in software or hardware.
  • the processing module can be implemented by a processor.
  • 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.
  • connection management device 80 when the connection management device is a network-side device or a component in a network-side device, the connection management device 80 may include a first processing module 81.
  • 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.
  • 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.
  • 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.
  • 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.
  • 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.
  • 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.
  • the aforementioned binding request message can be sent through the user plane.
  • 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.
  • 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;
  • the third indication information indicates that the terminal releases the user plane connection.
  • 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.
  • the aforementioned binding reply message can be sent through the user plane.
  • 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.
  • 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.
  • 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.
  • the aforementioned third message may be sent via the control plane.
  • the connection management device 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.
  • 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.
  • connection management device 90 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.
  • 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.
  • 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.
  • 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.
  • the terminal may determine whether the first connection identifier is within a valid time period based on the aforementioned first time information.
  • 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.
  • the aforementioned binding request message can be sent through the user plane.
  • 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.
  • 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;
  • the third indication information indicates that the terminal releases the user plane connection.
  • 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.
  • the aforementioned binding reply message can be sent through the user plane.
  • 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.
  • 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.
  • 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.
  • 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.
  • 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.
  • the aforementioned third message may be sent via the control plane.
  • the connection management device 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.
  • 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.
  • 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.
  • 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.
  • 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, this will not be described again here.
  • 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, and all implementation processes and methods of the above-described method embodiments can be applied to this terminal embodiment and achieve the same technical effect.
  • the terminal may be the connection management device shown in FIG9.
  • FIG11 is a schematic diagram of the hardware structure of a terminal implementing an embodiment of this application.
  • 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.
  • the terminal 1000 may also include a power supply (such as a battery) for powering various components.
  • the power supply can be logically connected to the processor 1010 through a power management system, thereby enabling functions such as charging, discharging, and power consumption management through the power management system.
  • the terminal structure shown in Figure 11 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.
  • 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.
  • 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.
  • the radio frequency unit 1001 includes, but is not limited to, antennas, amplifiers, transceivers, couplers, low-noise amplifiers, duplexers, etc.
  • 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.).
  • 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).
  • RAM random access memory
  • SRAM static random access memory
  • DRAM dynamic random access memory
  • SDRAM synchronous dynamic random access memory
  • DDRSDRAM double data rate synchronous dynamic random access memory
  • ESDRAM enhanced synchronous dynamic random access memory
  • SLDRAM synchronous link dynamic random access memory
  • DRRAM direct memory bus RAM
  • the memory 1009 in this embodiment includes, but is not limited to, these and any other suitable types of memory.
  • 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.
  • 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.
  • 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.
  • 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.
  • the terminal 1000 may determine whether the first connection identifier is within a valid time period based on the aforementioned first time information.
  • 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.
  • the aforementioned binding request message can be sent through the user plane.
  • 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.
  • 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;
  • the third indication information indicates that the terminal 1000 releases the user plane connection.
  • 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.
  • the aforementioned binding reply message can be sent through the user plane.
  • 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.
  • 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.
  • 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.
  • 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.
  • 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.
  • the aforementioned third message may be sent via the control plane.
  • 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.
  • 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.
  • the network-side device 1100 includes: a processor 1101, a network interface 1102, and a memory 1103.
  • the network-side device may be the connection management device shown in FIG8.
  • the network interface 1102 is, for example, a common public radio interface (CPRI).
  • CPRI common public radio interface
  • 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.
  • 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.
  • 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.
  • 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.
  • 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.
  • 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.
  • 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.
  • the aforementioned binding request message can be sent through the user plane.
  • 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.
  • 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;
  • the third indication information indicates that the terminal releases the user plane connection.
  • 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.
  • the aforementioned binding reply message can be sent through the user plane.
  • 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.
  • 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.
  • 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.
  • the aforementioned third message may be sent via the control plane.
  • the network-side device 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.
  • This application also provides a readable storage medium storing a program or instructions.
  • the 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.
  • 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.
  • ROM computer read-only memory
  • RAM random access memory
  • magnetic disk magnetic disk
  • optical disk optical disk
  • the readable storage medium may be a non-transient readable storage medium.
  • 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.
  • 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.
  • 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.
  • 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.

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Mobile Radio Communication Systems (AREA)

Abstract

本申请公开了一种连接管理方法、装置、终端及网络侧设备，属于通信技术领域，本申请实施例的连接管理方法包括：在网络侧设备与终端建立用户面连接的过程中，若满足第一条件，则网络侧设备执行第一操作；其中，第一条件包括以下至少一项：第一计时器超时，第一计时器与以下至少一项关联：第一连接标识、终端的终端标识、终端的绑定过程、用户面连接的建立过程；第一连接标识未处于有效时间内；第一操作包括以下至少一项：释放第一连接标识；释放用户面连接；向终端发送第一消息，第一消息用于指示终端重新建立与网络侧设备的用户面连接；更换定位协议方案。

Description

连接管理方法、装置、终端及网络侧设备
相关申请的交叉引用
本申请主张在2024年05月16日在中国提交的申请号为202410611734.7的中国专利的优先权，其全部内容通过引用包含于此。
技术领域
本申请属于通信技术领域，具体涉及一种连接管理方法、装置、终端及网络侧设备。
背景技术
目前，终端在接收到位置管理功能(Location Management Function，LMF)分配的连接标识之后，可以使用该连接标识通过用户面消息发起绑定(或关联)，以使LMF确定该连接标识对应的用户面连接是哪个终端的。
然而，如果终端在接收到上述连接标识之后迟迟未发起绑定，或者绑定失败，或者发起绑定之后没有收到网络侧设备的回复，同时终端也没有通知网络侧设备，那么该连接标识可能会被长时间的无效占用，从而使得网络侧设备无法再分配该连接标识，会导致资源的浪费。
发明内容
本申请实施例提供一种连接管理方法、装置、终端及网络侧设备，能够使网络侧设备再分配被无效占用的连接标识，节省资源。
第一方面，提供了一种连接管理方法，由网络侧设备执行，该方法包括：在网络侧设备与终端建立用户面连接的过程中，若满足第一条件，则网络侧设备执行第一操作；其中，第一条件包括以下至少一项：第一计时器超时，第一计时器与以下至少一项关联：第一连接标识、终端的终端标识、终端的绑定过程、用户面连接的建立过程；第一连接标识未处于有效时间内；第一操作包括以下至少一项：释放第一连接标识；释放用户面连接；向终端发送第一消息，第一消息用于指示终端重新建立与网络侧设备的用户面连接；更换定位协议方案。
第二方面，提供了一种连接管理方法，由终端执行，该方法包括：在网络侧设备与终端建立用户面连接的过程中，若满足第二条件，则终端执行第二操作；其中，第二条件包括以下至少一项：第二计时器超时，第二计时器与以下至少一项关联：第一连接标识、终端绑定过程的发起；第三计时器超时，第三计时器与以下至少一项关联：第一连接标识、终端的绑定过程、用户面连接的建立过程；第一连接标识未处于有效时间内；第二操作包括以下至少一项：向网络侧设备发送绑定请求消息；释放第一连接标识；释放用户面连接；向网络侧设备发送第三消息，第三消息用于指示建立用户面连接失败；更换定位协议方案。
第三方面，提供了一种连接管理装置，该装置包括第一处理模块；第一处理模块，用于在网络侧设备与终端建立用户面连接的过程中，若满足第一条件，则执行第一操作；其中，第一条件包括以下至少一项：第一计时器超时，第一计时器与以下至少一项关联：第一连接标识、终端的终端标识、终端的绑定过程、用户面连接的建立过程；第一连接标识未处于有效时间内；第一操作包括以下至少一项：释放第一连接标识；释放用户面连接；向终端发送第一消息，第一消息用于指示终端重新建立与网络侧设备的用户面连接；更换定位协议方案。
第四方面，提供了一种连接管理装置，该装置包括第二处理模块；第二处理模块，用于在网络侧设备与终端建立用户面连接的过程中，若满足第二条件，则执行第二操作；其中，第二条件包括以下至少一项：第二计时器超时，第二计时器与以下至少一项关联：第一连接标识、终端绑定过程的发起；第三计时器超时，第三计时器与以下至少一项关联：第一连接标识、终端的绑定过程、用户面连接的建立过程；第一连接标识未处于有效时间内；第二操作包括以下至少一项：向网络侧设备发送绑定请求消息；释放第一连接标识；释放用户面连接；向网络侧设备发送第三消息，第三消息用于指示建立用户面连接失败；更换定位协议方案。
第五方面，提供了一种连接管理装置，所述装置被配置为执行如第一方面所述的方法的步骤，或者实现如第二方面所述的方法的步骤。
第六方面，提供了一种网络侧设备，该网络侧设备包括处理器和存储器，所述存储器存储可在所述处理器上运行的程序或指令，所述程序或指令被所述处理器执行时实现如第一方面所述的方法的步骤。
第七方面，提供了一种网络侧设备，包括处理器及通信接口，其中，所述处理器用于在网络侧设备与终端建立用户面连接的过程中，若满足第一条件，则执行第一操作；其中，第一条件包括以下至少一项：第一计时器超时，第一计时器与以下至少一项关联：第一连接标识、终端的终端标识、终端的绑定过程、用户面连接的建立过程；第一连接标识未处于有效时间内；第一操作包括以下至少一项：释放第一连接标识；释放用户面连接；向终端发送第一消息，第一消息用于指示终端重新建立与网络侧设备的用户面连接；更换定位协议方案。
第八方面，提供了一种终端，该终端包括处理器和存储器，所述存储器存储可在所述处理器上运行的程序或指令，所述程序或指令被所述处理器执行时实现如第二方面所述的方法的步骤。
第九方面，提供了一种终端，包括处理器及通信接口，其中，所述处理器用于在网络侧设备与终端建立用户面连接的过程中，若满足第二条件，则执行第二操作；其中，第二条件包括以下至少一项：第二计时器超时，第二计时器与以下至少一项关联：第一连接标识、终端绑定过程的发起；第三计时器超时，第三计时器与以下至少一项关联：第一连接标识、终端的绑定过程、用户面连接的建立过程；第一连接标识未处于有效时间内；第二操作包括以下至少一项：向网络侧设备发送绑定请求消息；释放第一连接标识；释放用户面连接；向网络侧设备发送第三消息，第三消息用于指示建立用户面连接失败；更换定位协议方案。
第十方面，提供了一种可读存储介质，所述可读存储介质上存储程序或指令，所述程序或指令被处理器执行时实现如第一方面所述的方法的步骤，或者实现如第二方面所述的方法的步骤。
第十一方面，提供了一种无线通信系统，包括：终端及网络侧设备，所述网络侧设备可用于执行如第一方面所述的方法的步骤，所述终端可用于执行如第二方面所述的方法的步骤。
第十二方面，提供了一种芯片，所述芯片包括处理器和通信接口，所述通信接口和所述处理器耦合，所述处理器用于运行程序或指令，实现如第一方面所述的方法，或实现如第二方面所述的方法。
第十三方面，提供了一种计算机程序/程序产品，所述计算机程序/程序产品被存储在存储介质中，所述计算机程序/程序产品被至少一个处理器执行以实现如第一方面所述的方法的步骤，或实现如第二方面所述的方法的步骤。
在本申请实施例中，在网络侧设备与终端建立用户面连接的过程中，若满足第一条件，则网络侧设备执行第一操作；其中，第一条件包括以下至少一项：第一计时器超时，第一计时器与以下至少一项关联：第一连接标识、终端的终端标识、终端的绑定过程、用户面连接的建立过程；第一连接标识未处于有效时间内；第一操作包括以下至少一项：释放第一连接标识；释放用户面连接；向终端发送第一消息，第一消息用于指示终端重新建立与网络侧设备的用户面连接；更换定位协议方案。通过该方案，由于在网络侧设备与终端建立用户面连接的过程中，当第一计时器超时或第一连接标识未处于有效时间内时，网络侧设备可以执行释放第一连接标识、释放用户面连接、向终端发送用于指示重新建立用户面连接的第一消息和更换定位协议方案中的至少一项，因此可以避免终端长时间无效占用第一连接标识，使得网络侧设备可以再分配第一连接标识，从而可以节省资源。
附图说明
图1是本申请实施例可应用的一种无线通信系统的框图；
图2是相关技术中建立用户面连接的流程图；
图3是本申请实施例提供的一种连接管理方法的流程图；
图4是本申请实施例提供的一种连接管理方法中建立用户面连接的流程图之一；
图5是本申请实施例提供的另一种连接管理方法的流程图；
图6是本申请实施例提供的一种连接管理方法中建立用户面连接的流程图之二；
图7是本申请实施例提供的一种连接管理方法中建立用户面连接的流程图之三；
图8是本申请实施例提供的一种连接管理装置的结构示意图；
图9是本申请实施例提供的另一种连接管理装置的结构示意图；
图10是本申请实施例提供的通信设备的示意图；
图11是本申请实施例提供的终端的硬件结构示意图；
图12是本申请实施例提供的网络侧设备的硬件结构示意图。
具体实施方式
下面将结合本申请实施例中的附图，对本申请实施例中的技术方案进行清楚描述，显然，所描述的实施例是本申请一部分实施例，而不是全部的实施例。基于本申请中的实施例，本领域普通技术人员所获得的所有其他实施例，都属于本申请保护的范围。
本申请的术语“第一”、“第二”等是用于区别类似的对象，而不用于描述特定的顺序或先后次序。应该理解这样使用的术语在适当情况下可以互换，以便本申请的实施例能够以除了在这里图示或描述的那些以外的顺序实施，且“第一”、“第二”所区别的对象通常为一类，并不限定对象的个数，例如第一对象可以是一个，也可以是多个。此外，本申请中的“或”表示所连接对象的至少其中之一。例如“A或B”的保护范围至少涵盖三种方案，即，方案一：包括A且不包括B；方案二：包括B且不包括A；方案三：既包括A又包括B。此外，术语“A和/或B”、“A和B中的至少一项”、“A或B中的至少一项”也分别至少涵盖上述三种方案。字符“/”一般表示前后关联对象是一种“或”的关系。
本申请的术语“指示”既可以是一个直接的指示(或者说显式的指示)，也可以是一个间接的指示(或者说隐含的指示)。其中，直接的指示可以理解为，发送方在发送的指示中明确告知了接收方具体的信息、需要执行的操作或请求结果等内容；间接的指示可以理解为，接收方根据发送方发送的指示确定对应的信息，或者进行判断并根据判断结果确定需要执行的操作或请求结果等。
值得指出的是，本申请实施例所描述的技术不限于长期演进型(Long Term Evolution，LTE)/LTE的演进(LTE-Advanced，LTE-A)系统，还可用于其他无线通信系统，诸如码分多址(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)或其他系统。本申请实施例中的术语“系统”和“网络”常被可互换地使用，所描述的技术既可用于以上提及的系统和无线电技术，也可用于其他系统和无线电技术。以下描述出于示例目的描述了新空口(New Radio，NR)系统，并且在以下大部分描述中使用NR术语，但是这些技术也可应用于NR系统以外的系统，如第6代(6th Generation，6G)通信系统。
图1示出本申请实施例可应用的一种无线通信系统的框图。无线通信系统包括终端11和网络侧设备12。其中，终端11可以是手机、平板电脑(Tablet Personal Computer)、膝上型电脑(Laptop Computer)、笔记本电脑、个人数字助理(Personal Digital Assistant，PDA)、掌上电脑、上网本、超级移动个人计算机(Ultra-mobile Personal Computer，UMPC)、移动上网装置(Mobile Internet Device，MID)、增强现实(Augmented Reality，AR)、虚拟现实(Virtual Reality，VR)设备、机器人、可穿戴式设备(Wearable Device)、飞行器(flight vehicle)、车载用户设备(Vehicle User Equipment，VUE)、船载设备、行人用户设备(Pedestrian User Equipment，PUE)、智能家居(具有无线通信功能的家居设备，如冰箱、电视、洗衣机或者家具等)、游戏机、个人计算机(Personal Computer，PC)、柜员机或者自助机等终端侧设备。可穿戴式设备包括：智能手表、智能手环、智能耳机、智能眼镜、智能首饰(智能手镯、智能手链、智能戒指、智能项链、智能脚镯、智能脚链等)、智能腕带、智能服装等。其中，车载设备也可以称为车载终端、车载控制器、车载模块、车载部件、车载芯片或车载单元等。需要说明的是，在本申请实施例并不限定终端11的具体类型。网络侧设备12可以包括接入网设备或核心网设备，其中，接入网设备也可以称为无线接入网(Radio Access Network,RAN)设备、无线接入网功能或无线接入网单元。接入网设备可以包括基站、无线局域网(Wireless Local Area Network，WLAN)接入点(Access Point，AS)或无线保真(Wireless Fidelity，WiFi)节点等。其中，基站可被称为节点B(Node B，NB)、演进节点B(Evolved Node B，eNB)、下一代节点B(the next generation Node B，gNB)、新空口节点B(New Radio Node B，NR Node B)、接入点、中继站(Relay Base Station，RBS)、服务基站(Serving Base Station，SBS)、基收发机站(Base Transceiver Station，BTS)、无线电基站、无线电收发机、基本服务集(Basic Service Set，BSS)、扩展服务集(Extended Service Set，ESS)、家用B节点(home Node B，HNB)、家用演进型B节点(home evolved Node B)、发送接收点(Transmit/Receive Point，TRP)或所属领域中其他某个合适的术语，只要达到相同的技术效果，所述基站不限于特定技术词汇，需要说明的是，在本申请实施例中仅以NR系统中的基站为例进行介绍，并不限定基站的具体类型。
核心网设备也可以称为核心网节点、核心网功能或核心网网元等，其包含但不限于如下至少一项：移动管理实体(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)、本地NEF(Local NEF，或L-NEF)、绑定支持功能(Binding Support Function，BSF)、应用功能(Application Function，AF)、位置管理功能(Location Management Function，LMF)、网关的移动位置中心(Gateway Mobile Location Centre，GMLC)、网络数据分析功能(Network Data Analytics Function，NWDAF)等。需要说明的是，在本申请实施例中仅以NR系统中的核心网设备为例进行介绍，并不限定核心网设备的具体类型，如果在后续协议版本(例如6G)中本申请实施例提到的核心网设备的名称发生变化，也在本申请的保护范围内。
可选的，核心网设备可以由一个设备中的一个或多个功能模块实现，也可以由多个设备共同实现，本申请实施例对此不作具体限定。可以理解的是，上述功能模块既可以是硬件设备中的网络元件，也可以是在专用硬件上运行的软件功能模块，或者是平台(例如，云平台)上实例化的虚拟化功能模块。
下面结合附图，通过一些实施例及其应用场景对本申请实施例提供的连接管理方法、装置、终端及网络侧设备进行详细地说明。
目前，LMF和终端之间可以通过控制面信令传递一些配置信息，以用于建立用户面连接并在用户面上传递LTE定位协议(LTE Positioning Protocol，LPP)消息或位置服务(Location Service，LCS)-SS消息。图2示出了建立用户面连接的流程图，如图2所示，LMF和终端之间可以通过信令交互建立用户面连接，在图2示出的流程的基础上，对于步骤7有下述增强：终端在步骤7中使用步骤3中接收到的LCS-UP连接标识，通过用户面消息发起关联(correlation)过程或绑定(bind)过程，以使LMF来确定该用户面连接是哪个终端的。
需要说明的是，为了便于描述，上述关联过程或绑定过程在下文统称为绑定过程或绑定。
终端在接收到连接标识(例如LCS-UP connection ID)之后，是立即发起绑定还是由终端来决定何时发起绑定尚不清楚；而且当需要立即发起绑定时，LMF如何监督终端立即发起绑定也不清楚；当终端迟迟未发起绑定时，LMF和终端对该连接标识以及终端到LMF的用户面连接(包括传输层安全性(Transport Layer Security，TLS)连接)的管理动作也不清楚。
然而，如果终端不立即发起绑定，或LMF没有一个合理的监督机制，潜在的问题包括：
1、若终端迟迟不发起绑定，持有连接标识却不使用，则会影响LMF给新的终端分配连接标识，造成资源的浪费；
2、若未完成绑定，则LMF无法获知用户面连接和终端的关联关系，使得LMF和终端之间无法使用用户面连接传递LPP消息或LCS-SS消息；
3、恶意终端盲猜中其他终端的连接进行绑定，或者其他终端误用了正常终端的连接标识，占用了正常终端的用户名定位通信的渠道，会导致传递错误的位置信息，造成终端位置上报错误并影响正常终端的使用。
为了解决上述问题，本申请实施例提供一种连接管理方法、装置、终端及网络侧设备。本申请实施例提供的连接管理方法可以应用于网络侧设备与终端建立用户面连接的场景。
在本申请实施例提供的连接管理方法中，在网络侧设备与终端建立用户面连接的过程中，若满足第一条件，则网络侧设备执行第一操作；其中，第一条件包括以下至少一项：第一计时器超时，第一计时器与以下至少一项关联：第一连接标识、终端的终端标识、终端的绑定过程、用户面连接的建立过程；第一连接标识未处于有效时间内；第一操作包括以下至少一项：释放第一连接标识；释放用户面连接；向终端发送第一消息，第一消息用于指示终端重新建立与网络侧设备的用户面连接；更换定位协议方案。通过该方案，由于在网络侧设备与终端建立用户面连接的过程中，当第一计时器超时或第一连接标识未处于有效时间内时，网络侧设备可以执行释放第一连接标识、释放用户面连接、向终端发送用于指示重新建立用户面连接的第一消息和更换定位协议方案中的至少一项，因此可以避免终端长时间无效占用第一连接标识，使得网络侧设备可以再分配第一连接标识，从而可以节省资源。
而且可以要求终端在上述第一计时器的运行期间或上述第一连接标识的有效时间内尽快发起绑定，使得LMF和终端在完成绑定之后，可以使用用户面连接传递LPP消息或LCS-SS消息；同时也可以避免恶意终端盲猜中其他终端的连接进行绑定，或者其他终端误用正常终端的连接标识，从而使得终端位置上报准确且不影响正常终端的使用。
本申请实施例提供一种连接管理方法，图3示出了本申请实施例提供的连接管理方法的流程图。如图3所示，本申请实施例提供的连接管理方法可以包括下述的步骤301。
步骤301、在网络侧设备与终端建立用户面连接的过程中，若满足第一条件，则网络侧设备执行第一操作。
其中，上述第一条件包括以下至少一项：
第一计时器超时，该第一计时器与以下至少一项关联：第一连接标识、终端的终端标识、终端的绑定过程、用户面连接的建立过程；
第一连接标识未处于有效时间内；
上述第一操作包括以下至少一项：
释放第一连接标识；
释放用户面连接；
向终端发送第一消息，该第一消息用于指示终端重新建立与网络侧设备的用户面连接；
更换定位协议方案。
可选地，本申请实施例中，上述网络侧设备可以为具有位置管理功能的设备，例如网络侧设备可以为LMF。
可选地，本申请实施例中，上述第一消息可以包括LMF LCS-UP地址(LMF LCS-UP address)。
需要说明的是，终端建立与LMF的用户面连接包括：建立分组数据单元会话(Packet Data Unit Session，PDU)会话、建立终端与LMF的TLS连接、用户面连接的绑定。上述重新建立与网络侧设备的用户面连接可以指：重新建立包括PDU会话、TLS连接、绑定的所有内容；或者当PDU会话没有被释放，终端只需要重建TLS连接以及重新执行一次绑定流程；又或者当PDU会话没有被释放，TLS连接也处于有效状态下，终端只需要重新执行一次绑定过程。因此对于重新建立的理解可以是一种针对整个用户面连接的建立的泛指。
还需要说明的是，上述第一消息中重新建立的含义也可以由上述第一消息中携带的第一指示信息理解得到。在该第一消息中携带LMF LCS-UP地址、第一指示信息和第二连接标识的情况下，如果第二连接标识和之前第二消息中的第一连接标识不一样，但是LMF LCS-UP地址是一样的，那么可以理解为网络侧设备只是希望终端使用不一样的连接标识进行绑定流程，因此如果PDU会话、TLS连接的过程已经成功执行，那么可以被直接跳过，终端只需重新执行绑定过程，也就是“重新建立”的意思。
可选地，本申请实施例中，上述第一计时器可以是网络侧设备在接收到用户面连接建立确认消息之后启动。
可选地，本申请实施例中，上述第一计时器可以用于对用户面连接的建立过程(包括绑定过程)进行计时；当上述第一计时器超时时，可以认为终端在用户面连接的建立过程中迟迟未发起绑定或绑定长时间未成功，此时终端可以执行上述第一操作。
可选地，本申请实施例中，上述第一计时器可以为计时器T5012(TS24.572v18.0.0)或新增的针对绑定过程的计时器。
需要说明的是，如果第一计时器是新增的针对绑定过程的计时器，那么该第一计时器可以在网络侧设备发送用户面连接建立命令消息(例如user plane connection establishment command message)且携带了一个LCS-UP连接标识时启动，并在接收到终端的绑定请求消息(例如binding request message)且该绑定请求消息也携带了该LCS-UP连接标识时，停止该第一计时器。整个第一计时器的周期就是为了关联该LCS-UP连接标识的绑定，以促使被分配了一个连接标识的终端尽快发起绑定。
可选地，本申请实施例中，上述第一连接标识用于对用户面连接与终端进行标识。
可选地，本申请实施例中，上述第一连接标识可以为LCS-UP连接标识(LCS-UP connection ID)、LCS-UP绑定标识(例如LCS-UP binding ID)或LCS-UP连接关联标识(LCS-UP connection correlation ID)等。
可选地，本申请实施例中，上述终端标识用于标识终端。
可选地，本申请实施例中，上述终端标识可以为订阅永久标识符(Subscription Permanent Identifier，SUPI)或通用公共用户标识符(Generic Public Subscription Identifier，GPSI)等。
可选地，本申请实施例中，上述第一连接标识的有效时间可以是网络侧设备配置的。
可选地，本申请实施例中，当上述第一连接标识处于上述有效时间内时，该第一连接标识可以被用于终端的绑定过程；当上述第一连接标识未处于上述有效时间内时，该第一连接标识不可被用于终端的绑定过程。
需要说明的是，本申请实施例中涉及的释放，可以包括以下至少一项：本地释放(例如locally release)、使用信令流程释放(例如network requested user plane connection release procedure)、移除、删除。
可选地，本申请实施例中，上述释放第一连接标识也可以理解为：将该第一连接标识视为过期或失效。
可选地，本申请实施例中，上述释放用户面连接可以包括：释放终端的上下文，包括上述第一连接标识与终端的关联关系。
可选地，本申请实施例中，上述更换定位协议方案可以理解为：将使用用户面定位的方案更换为其他定位协议方案。
可选地，本申请实施例中，上述其他定位协议方案可以包括：使用控制面定位的方案或使用安全用户面定位(Secure User Plane Location，SUPL)方案传递LPP消息、LCS-SS消息等。
可选地，本申请实施例中，上述第一消息可以为用户面连接建立命令(例如user plane connection establishment command message)。
可选地，本申请实施例中，上述第一消息可以包括以下至少一项：第二连接标识、终端的终端标识、第一指示信息。
其中，上述第一指示信息用于指示终端使用第二连接标识发起绑定过程。
可选地，本申请实施例中，上述第一连接标识或上述第二连接标识可以是供网络侧设备在众多的用户面连接(例如LCS user plane connection，也可理解为TLS connection)中唯一确定终端或者连接的，也可以理解为一种关联关系，这种关联关系是供网络侧设备一对一地确定终端与用户面连接的。
可选地，本申请实施例中，上述第二连接标识可以与上述第一连接标识相同或不同。
可选地，本申请实施例中，在上述网络侧设备与终端建立用户面连接的过程中，网络侧设备在为终端首次分配用户面连接信息时，可以先确定上述第一连接标识与终端的映射关系；然后在满足上述第一条件的情况下，网络侧设备更新终端与连接标识的映射关系并将上述第二连接标识或上述第一指示信息发送给终端，例如，可以删除终端关联的该第一连接标识，并将该第二连接标识发送给终端，或者可以依旧维持该第一连接标识与终端的映射关系不变，即将该第一连接标识作为该第二连接标识发送给终端。如此可以指示终端使用该第二连接标识重新建立与网络侧设备的用户面连接。
本申请实施例中，由于上述第一消息可以包括上述第二连接标识、终端的终端标识和上述第一指示信息中的至少一项，因此可以通过不同的信息指示终端重新建立与网络侧设备的用户面连接，从而可以提高指示建立用户面连接的灵活性。
在本申请实施例提供的连接管理方法中，由于在网络侧设备与终端建立用户面连接的过程中，当第一计时器超时或第一连接标识未处于有效时间内时，网络侧设备可以执行释放第一连接标识、释放用户面连接、向终端发送用于指示重新建立用户面连接的第一消息和更换定位协议方案中的至少一项，因此可以避免终端长时间无效占用第一连接标识，使得网络侧设备可以再分配第一连接标识，从而可以节省资源。
可选地，本申请实施例中，在上述步骤301之前，本申请实施例提供的连接管理方法还可以包括下述的步骤A。
步骤A、网络侧设备向终端发送第二消息。
其中，上述第二消息可以为用户面连接建立命令或用于指示终端建立与网络侧设备的用户面连接。
可选地，本申请实施例中，上述第二消息可以为用户面连接建立命令(例如user plane connection establishment command message)。
需要说明的是，上述第一消息和上述第二消息可以均是用户面连接建立命令。在这种情况下，该第二消息可以理解为在最开始，网络侧设备向终端发送的一条用户面连接建立命令；而该第一消息是在该第二消息发送之后可能发送给终端的用户面连接建立命令，比如：判断该第二消息中连接标识关联的计时器超时了，网络侧设备希望更新终端与连接标识的映射关系，重新分配一个连接标识供终端的在绑定过程中使用，从而发送了该第一消息给终端。
可选地，本申请实施例中，上述第二消息还可以包括LMF LCS-UP地址(例如LMF LCS-UP address)。
需要说明的是，上述第二消息指示建立的用户面连接即上述步骤301中的用户面连接。
可选地，本申请实施例中，上述第二消息可以包括以下至少一项：上述第一连接标识、终端的终端标识、第二计时器的相关信息、第一时间信息。
其中，上述第二计时器与以下至少一项关联：上述第一连接标识、终端绑定过程的发起，上述第一时间信息用于指示上述第一连接标识的有效时间。
可选地，本申请实施例中，上述第二计时器的相关信息可以包括该第二计时器对应的时长。
可选地，本申请实施例中，上述第二计时器可以为TS24.008v18.0.0中通用分组无线业务(General Packet Radio Service，GPRS)3格式的计时器，网络侧设备可以通过设置该GPRS 3格式的计时器的单元(unit)和计时器值(timer value)配置该第二计时器。
可选地，本申请实施例中，上述第二计时器可以为一个隐性指示，即网络侧设备隐性指示终端启动该第二计时器，并在该第二计时器对应的时间内发起绑定流程。
可选地，本申请实施例中，上述第一时间信息具体可以用于指示以下至少一项：上述第一连接标识的有效开始时间和有效结束时间、上述第一连接标识的有效时间间隔。
例如，当上述第一时间信息用于指示上述第一连接标识的有效时间间隔时，该第一连接标识的有效时间为：终端在接收到该第一时间信息之后的一个时间间隔，一旦超过该时间间隔，该第一连接标识失效。
对上述第二消息的其他描述，可以参照对上述第一消息的相关描述，为了避免重复，此处不再赘述。
本申请实施例中，由于上述第二消息可以包括上述第一连接标识、终端的终端标识、上述第二计时器和上述第一时间信息中的至少一项，因此使得网络侧设备可以在向终端发送不同信息的情况下，启动上述第一计时器，从而可以提高启动第一计时器的灵活性。
可选地，本申请实施例中，网络侧设备在向终端发送上述第二消息之后，可以通过该第二消息包括的信息判断第一连接标识是否有效，进而确定是否接受终端的绑定请求；例如，当上述第二消息包括上述第一时间信息时，可以在接收到终端的绑定请求消息之后，通过该第一时间信息判断该第一连接标识是否处于有效时间内，若处于有效时间内，则接受终端的绑定请求，若未处于有效时间内，则拒绝终端的绑定请求并执行上述第一操作。可以理解，网络侧设备在向终端发送第二消息之后，可以不启动第一定时器，网络侧设备通过第一时间信息确定第一连接标识是否有效。
可选地，本申请实施例中，在上述步骤301之前，本申请实施例提供的连接管理方法还可以包括下述的步骤302。
步骤302、在向终端发送第二消息的情况下，网络侧设备启动第一计时器。
可选地，本申请实施例中，上述在向终端发送第二消息的情况下，可以理解为：在向终端发送该第二消息之后，或者在向终端发送该第二消息之后的预设时长后。
可以理解，在上述步骤A之后，网络侧设备可以立即启动上述第一计时器或在预设时长后启动该第一计时器。
本申请实施例中，由于在向终端发送上述第二消息的情况下，网络侧设备启动上述第一计时器，因此可以从指示终端建立与网络侧设备的用户面连接时开始对终端的绑定过程进行监控，从而可以准确地判断是否长时间未绑定成功，进而执行上述第一操作以释放资源。
可选地，本申请实施例提供的连接管理方法还可以包括下述的步骤303。
步骤303、在向终端发送第一消息，且第一消息包括与第一连接标识不同的第二连接标识的情况下，网络侧设备重新启动第一计时器。
可以理解，在向终端发送上述第一消息，且该第一消息包括与上述第一连接标识不同的上述第二连接标识的情况下，网络侧设备指示终端使用不同的连接标识重新建立与网络侧设备的用户面连接，此时重新启动上述第一计时器，可以重新监控终端新的绑定流程。
本申请实施例中，由于当向终端发送上述第一消息，且该第一消息包括与上述第一连接标识不同的上述第二连接标识时，网络侧设备可以重新启动上述第一计时器，因此可以准确监控终端使用第二连接标识的绑定流程。
可选地，本申请实施例提供的连接管理方法还可以包括下述的步骤304。
步骤304、在向终端发送第二消息之后，网络侧设备接收终端发送的绑定请求消息。
其中，上述绑定请求消息用于绑定用户面连接和终端，该绑定请求消息包括以下至少一项：第三连接标识、终端的终端标识。
可选地，本申请实施例中，上述绑定请求消息具体可以用于请求网络侧设备关联终端或上述第一连接标识与TLS连接。
可选地，本申请实施例中，上述第三连接标识可以与上述第一连接标识相同或不同。
需要说明的是，之所以需要区分上述第三连接标识与上述第一连接标识，是考虑到部分正常终端在获取到连接标识之后，由于内部操作错误，在绑定请求消息中可能携带了一个错误的连接标识，或者误占用了其他终端的连接标识，因此网络需要通过判断该第三连接标识来决定能否接受绑定请求。
可选地，本申请实施例中，上述绑定请求消息可以是通过用户面发送的。
本申请实施例中，由于在向终端发送上述第二消息之后，网络侧设备可以接收终端发送的绑定请求消息，因此使得网络侧设备可以获知终端已使用上述第三连接标识发起绑定过程。
可选地，本申请实施例中，在上述步骤304之后，本申请实施例提供的连接管理方法还可以包括下述的步骤305。
步骤305、在绑定请求消息包括第三连接标识，且第三连接标识与第一连接标识相同的情况下，网络侧设备停止第一计时器。
可以理解，在上述绑定请求消息包括上述第三连接标识，且该第三连接标识与上述第一连接标识相同的情况下，终端已使用该第一连接标识发起绑定过程，此时无需再通过上述第一计时器监控绑定过程的发起，从而可以停止该第一计时器。
本申请实施例中，由于在上述绑定请求消息包括上述第三连接标识，且该第三连接标识与上述第一连接标识相同的情况下，网络侧设备可以停止上述第一计时器，因此可以在获知终端已使用该第一连接标识发起绑定过程的情况下，停止该第一计时器以节省设备功耗。
可选地，本申请实施例中，在上述步骤304之后，本申请实施例提供的连接管理方法还可以包括下述的步骤306。
步骤306、网络侧设备向终端发送绑定回复消息。
其中，上述绑定回复消息包括以下至少一项：第二指示信息、上述第三连接标识、第一原因值、第三指示信息。
其中，上述第二指示信息用于指示接受或者拒绝上述绑定请求消息对应的绑定，上述第一原因值用于指示拒绝该绑定请求消息对应的绑定的原因，上述第三指示信息用于指示终端释放用户面连接。
可选地，本申请实施例中，上述第二指示信息的一种实现方式是：指示用户面连接绑定的结果，包括绑定成功或绑定失败；另一种实现方式是：上述绑定回复消息通过消息类型(例如message type)来实现，一条为绑定接受消息(例如binding accept message)，一条为绑定拒绝消息(例如binding reject message)；再一种实现方式是：绑定接受或者绑定失败为一种隐式的实现，例如，若上述绑定回复消息携带了上述第一原因值，则代表了绑定失败，若上述绑定回复消息未携带上述第一原因值，则代表绑定接受。
可选地，本申请实施例中，上述第三连接标识为上述绑定回复消息关联的连接标识。
可选地，本申请实施例中，上述绑定回复消息可以是通过用户面发送的。
可选地，本申请实施例中，上述第一原因值具体可以用于指示以下至少一项：连接标识无效(例如identifier invalid)、连接标识超时(例如identifier expired)、连接标识冲突(例如identifier collision或identifier occupied)、绑定不被接受(例如bind not accepted)、协议错误(例如protocol error，unspecified)。
可选地，本申请实施例中，上述连接标识超时也可以为理解为连接标识过期。
可选地，本申请实施例中，上述连接标识冲突可以包括：连接标识已绑定或已占用。
可选地，本申请实施例中，当上述绑定请求消息可以被接受时，网络侧设备可以向终端提供结果指示信息，其中指示为绑定成功，并可选携带上述第三连接标识。在此之后，网络侧设备将该TLS连接与终端的终端标识或该第三连接标识绑定，可以通过该TLS连接或用户面连接发送与该终端相关的LPP消息、LCS-SS消息。
可选地，本申请实施例中，当上述绑定请求消息不可以被接受，网络侧设备可以向终端提供结果指示信息，其中指示为绑定失败；和/或，网络侧设备携带上述第一原因值指示为绑定不被接受(例如bind not accepted)。
可选地，本申请实施例中，当上述绑定请求消息中的LCS-UP连接标识为无效值标识或者未分配的标识时，网络侧设备可以向终端提供结果指示信息，其中指示为绑定失败；和/或，网络侧设备携带上述第一原因值指示为连接标识无效；和/或，网络侧设备向终端发送绑定拒绝消息，并携带第一原因值指示为连接标识无效。
当绑定请求中的LCS-UP连接标识已经被绑定时，LMF向终端提供结果指示信息，其中指示为绑定失败；和/或，LMF携带第一原因值指示为连接标识已绑定或已占用(例如identifier already bound/identifier occupied)，或指示为连接标识冲突(例如identifier collision)；和/或，网络侧设备向终端发送绑定拒绝消息，并携带第一原因值指示为连接标识已绑定或已占用或冲突。
需要说明的是，对于上述连接标识冲突，一种实现方式如下：网络侧设备收到了一条使用第一连接标识的绑定请求消息，并且发现使用该第一连接标识的绑定流程已经完成，网络侧设备已经将该第一连接标识或终端的终端标识与其他TLS连接进行绑定或关联。此时新的绑定请求必然无法成功，属于异常情况，必然有一个终端用错了第一连接标识。
在这种情况下，网络侧设备无法区分哪个是正确的终端(即上述第一连接标识真正关联的终端)，哪个是出错的终端，从而网络侧设备可以向终端发送一条指示绑定失败的绑定回复消息或绑定拒绝消息，携带上述第一原因值指示连接标识冲突。正确的终端在接收到该第一原因值之后，发现绑定流程尚未完成，便可获知有终端冒用或占用了自己的第一连接标识完成了绑定。此时，正确的终端可以通过控制面的用户平面定位连接管理信息(user plane positioning connection management information，UPP-CMI)信令向网络侧设备发送一条消息，例如用户面连接释放请求消息或者新增一条报告消息，消息携带第一连接标识，并且消息可选携带一个特定指示信息，消息用于请求网络侧设备释放终端与网络侧设备之间的LCS安全的用户面连接或者用于上报用户面连接的异常报告，该特定指示信息用于指示网络侧设备强制释放用户面连接或者用于指示连接标识错误绑定、连接标识被占用或连接标识被劫持；又例如，终端在用户面连接失败消息中携带一个指示信息，用于告知网络侧设备分配给该终端的连接标识在绑定过程中发生冲突，或者连接标识被冒用，或者请求网络侧设备分配一个新的连接标识。网络侧设备在收到终端发送的释放请求消息或者报告消息或者用户面连接失败消息之后，验证该连接标识被冒用或者冲突之后，立即执行释放该第一连接标识关联的用户面连接。如此可以完成对占用连接标识或者误绑定情况的纠正。上述提到的请求网络侧设备分配一个新的连接标识，可以避免再次使用之前冲突的连接标识绑定再次发生冲突，让冲突的问题在下一次绑定时得到缓解。
本申请实施例中，由于网络侧设备在接收终端发送的绑定请求消息之后，可以向终端发送上述绑定回复消息，以向终端指示绑定结果及进一步操作，因此可以使得终端能够及时释放资源。
可选地，本申请实施例中，在上述步骤306之后，本申请实施例提供的连接管理方法还可以包括下述的步骤307。
步骤307、网络侧设备接收终端发送的第三消息。
其中，上述第三消息用于指示建立用户面连接失败，该第三消息可以是用户面连接建立失败消息(例如user plane connection establishment failure message)或者是用户面连接建立命令拒绝消息(例如user plane connection establishment command reject message)。
可选地，本申请实施例中，上述第三消息可以包括以下至少一项：第二原因值、第四指示信息，该第二原因值用于指示以下至少一项：绑定失败、TLS失败、会话失败、连接标识无效、连接标识超时、连接标识冲突、绑定不被接受；该第四指示信息用于请求重新分配连接标识。
需要说明的是，上述第四指示信息是终端在本次连接建立失败的情况下发送给网络侧设备的，旨在使能终端能够主动通过判断一些建立过程中发现的问题，来告知网络侧设备在下次建立连接时直接重新分配一个新的连接标识。该建立过程中发现的问题包括终端收到了连接标识无效、连接标识冲突等问题。通过该第四指示信息，终端如果还想继续请求建立用户面连接，那么可以不用再发送一条用户面连接建立请求消息(例如user plane connection establishment request message)，而是网络侧设备可以直接发送一个新的用户面连接建立命令消息(例如user plane connection establishment command message)，携带新的连接标识给终端，从而节省信令交互。
可选地，本申请实施例中，上述第三消息可以是通过控制面发送的。
可选地，本申请实施例中，网络侧设备在接收到上述第三消息之后，可以执行上述第一操作。
可选地，本申请实施例中，网络侧设备在释放上述第一连接标识之后，后面在接收到绑定请求消息中使用该第一连接标识进行绑定的，均在绑定回复消息中携带下述至少一项：结果指示信息设定为绑定失败、该第一连接标识、上述第一原因值设为连接标识无效或连接标识冲突。
本申请实施例中，由于网络侧设备可以接收终端发送的第三消息，因此可以及时获知建立用户面连接失败，并执行上述第一操作以释放资源。
示例性地，如图4所示，以网络侧设备为LMF为例，终端和LMF建立用户面连接的流程包括下述的步骤1至步骤6：
步骤1、在终端发起的情况下，终端向LMF发送用户面连接建立请求(例如user plane connection establishment request message)，以请求建立一个终端到LMF的LCS安全的用户面连接。
步骤2、在网络侧设备发起的情况下，或者在收到步骤1中的消息之后，LMF向终端发送用户面连接建立命令，用于传递用户面连接信息并且触发终端向LMF建立LCS安全的用户面连接，该命令可携带以下至少一项：LMF LCS-UP地址、LCS-UP连接标识；同时启动计时器1。
步骤3、终端在收到步骤2中的用户面连接建立命令之后，建立一条PDU，以提供终端到LMF的PDU连接服务；并在成功建立PDU之后，根据收到的LMF LCS-UP地址发起TLS握手，建立终端到LMF的安全连接。
步骤4、可选地，终端向LMF发送LCS-UP绑定请求，该消息用于请求LMF关联终端或LCS-UP连接标识与TLS连接，该消息可携带LCS-UP连接标识；同时启动计时器3。
需要说明的是，上述计时器3与上述LCS-UP连接标识相关联或者与该LCS-UP连接标识的绑定相关联。该计时器3用于监督或关联LMF收到LCS-UP绑定请求并且回复终端一条LCS-UP绑定响应消息。当该计时器3超时时，说明LCS-UP绑定请求没有发送至LMF处，或者LCS-UP绑定响应消息还未回复至终端，此时终端需要向LMF重新发送一条LCS-UP绑定请求以确保绑定的完成。该计时器3的取值可以是预设或者终端实现决定的。
在上述计时器3正在运行或没有停止或者没有超时的情况下，若终端收到了一条用户面连接建立命令，即步骤2中的消息(可以理解为异常情况：终端正在执行绑定，但是却因为耗时很多，导致步骤2中LMF启动的计时器1(例如T5012)超时了，所以LMF重发了一条消息；或者LMF发生了切换，新的LMF也决定建立与终端的用户面连接；又或者由于计时器1超时了，因此LMF终止了当前的用户面连接建立过程，然后又决定发起一个新的用户面连接建立过程)，则终端可以采取以下动作中的一项：
一、如果终端在LCS-UP绑定过程中收到用户面连接建立命令消息，并且：
1)用户面连接建立命令消息中包含的LMF LCS-UP地址与发送LCS-UP绑定请求消息的地址相同；以及，
2)用户面连接建立命令(例如USER PLANE CONNECTION ESTABLISHMENT COMMAND)消息中包含的LCS-UP连接标识与LCS-UP绑定请求(例如LCS-UP BINDING REQUEST)消息中包含的LCS-UP连接标识相同；
那么终端应忽略用户面连接建立命令消息，并继续执行LCS-UP绑定过程，即等待网络对于绑定请求的回复。
二、如果终端在LCS-UP绑定过程中收到用户面连接建立命令消息，并且：
1)用户面连接建立命令消息中包含的LMF LCS-UP地址与发送LCS-UP绑定请求报文的地址不同；或者
2)用户面连接建立命令(例如USER PLANE CONNECTION ESTABLISHMENT COMMAND)消息中包含LCS-UP连接标识与LCS-UP绑定请求(例如LCS-UP BINDING REQUEST)消息中包含的LCS-UP连接标识不同；或者，
3)包括上述1)和上述2)；
那么终端应中止LCS-UP绑定过程，停止计时器3并继续处理最新的用户面连接建立命令消息。
步骤5、可选地，在收到步骤4中的消息的情况下，LMF向终端回复LCS-UP绑定回复，用于回复LCS-UP绑定请求消息并提供绑定结果，该消息可携带以下至少一项：
绑定结果；
LCS-UP连接标识；
原因值。
需要说明的是，只有在接收到绑定成功的指示之后，终端才可以通过上述TLS连接或用户面连接发送终端的LPP消息、LCS-SS消息。而当接收到绑定失败的指示时，终端不能通过该TLS连接或用户面连接发送终端的LPP消息、LCS-SS消息，并且执行下述至少一项操作：
停止计时器3：终端在收到LCS-UP绑定回复之后，如果计时器3还在运行，则终端停止计时器3；
认为LCS-UP连接标识过期或无效：将LCS-UP连接标识视为过期或无效，后续无法使用该LCS-UP连接标识进行绑定流程；
更换定位协议方案：终端基于本地判断，决定不使用用户面定位，改为使用控制面定位或者使用SUPL传递传递LPP消息、LCS-SS消息。
还需要说明的是，在上述步骤2中LMF分配连接标识时，LMF内部已经维护了一个终端标识与连接标识的映射关系，当终端提供终端标识或连接标识给LMF时，LMF均知道这是哪个终端或者这是哪个连接标识。在步骤5中，LMF需要做的是将这个TLS连接与终端或连接标识绑定起来。这样在LMF处TLS连接、终端标识和连接标识就是一一对应的。
步骤6、当绑定过程成功发生，终端向LMF发送user plane connection establishment complete消息，用于指示用户面连接建立成功。当计时器3超时、TLS握手失败、绑定过程收到失败指示或PDU session建立失败时，终端向LMF发送user plane connection establishment failure消息。在接收到user plane connection establishment failure消息之后，LMF执行上述第一操作。
需要说明的是，终端向LMF发送上述user plane connection establishment failure消息，该消息可携带原因值和/或第四指示信息，该原因值用于指示以下至少一项：绑定失败、TLS建立失败、PDU session失败、连接标识无效、连接标识超时、连接标识冲突、绑定不被接受；该第四指示信息(例如，LCS-UP additional information)用于请求重新分配连接标识(例如request the LMF to re-allocates a new LCS-UP connection ID to the UE)，一种实现方式如下表所示：
(LCS-UP附加信息要素)
可选地，本申请实施例中，在上述步骤6中，当LMF执行上述第一操作之后，终端可以重新建立与LMF的用户面连接，此过程中，LMF可以为终端分配新的连接标识以用于重新建立用户面连接，具体过程可参照上述步骤1至步骤6，为了避免重复，此处不再赘述。
本申请实施例提供另一种连接管理方法，图5示出了本申请实施例提供的连接管理方法的流程图。如图5所示，本申请实施例提供的连接管理方法可以包括下述的步骤501。
步骤501、在网络侧设备与终端建立用户面连接的过程中，若满足第二条件，则终端执行第二操作。
其中，上述第二条件包括以下至少一项：
第二计时器超时，该第二计时器与以下至少一项关联：第一连接标识、终端绑定过程的发起；
第三计时器超时，该第三计时器与以下至少一项关联：第一连接标识、终端的绑定过程、用户面连接的建立过程；
第一连接标识未处于有效时间内；
上述第二操作包括以下至少一项：
向网络侧设备发送绑定请求消息；
释放第一连接标识；
释放用户面连接；
向网络侧设备发送第三消息，该第三消息用于指示建立用户面连接失败；
更换定位协议方案。
可选地，本申请实施例中，上述第三消息可以是user plane connection establishment failure消息或user plane connection establishment command reject消息。
可选地，本申请实施例中，上述第三消息可以包括以下至少一项：第二原因值、第四指示信息；其中，该第二原因值用于指示以下至少一项：绑定失败、TLS失败、会话失败、连接标识无效、连接标识超时、连接标识冲突、绑定不被接受；该第四指示信息用于请求重新分配连接标识。
可选地，本申请实施例中，上述第三消息可以是通过控制面发送的。
在本申请实施例提供的连接管理方法中，由于在网络侧设备与终端建立用户面连接的过程中，当第二计时器超时、第三计时器超时或第一连接标识未处于有效时间内时，终端可以执行向网络侧设备发送绑定请求消息、释放第一连接标识、释放用户面连接、向网络侧设备发送用于指示建立用户面连接失败的第三消息和更换定位协议方案中的至少一项，因此可以避免终端长时间无效占用第一连接标识，使得网络侧设备可以再分配第一连接标识，从而可以节省资源。
可选地，本申请实施例中，在上述步骤501之前，本申请实施例提供的连接管理方法还可以包括下述的步骤502。
步骤502、在接收到网络侧设备发送的第二消息的情况下，终端启动第二计时器。
其中，上述第二消息用于指示终端建立与网络侧设备的用户面连接。
可选地，本申请实施例中，上述第二消息可以包括以下至少一项：上述第一连接标识、终端的终端标识、第二计时器、第一时间信息。
其中，上述第二计时器与以下至少一项关联：上述第一连接标识、终端绑定过程的发起，上述第一时间信息用于指示上述第一连接标识的有效时间。
可选地，本申请实施例中，终端可以是根据上述第一时间信息判断上述第一连接标识是否处于有效时间内的。
可选地，本申请实施例中，上述第一时间信息的实现方式可以如下表所示：
(标识符时间有效性信息要素)
可选地，本申请实施例提供的连接管理方法还可以包括下述的步骤503。
步骤503、在满足第三条件的情况下，终端向网络侧设备发送绑定请求消息。
其中，上述绑定请求消息用于绑定用户面连接和终端，该绑定请求消息包括以下至少一项：第三连接标识、终端的终端标识，上述第三条件包括以下任一项：上述第二计时器未超时、上述第一连接标识处于有效时间内。
可选地，本申请实施例中，上述绑定请求消息可以是通过用户面发送的。
可选地，本申请实施例中，终端在准备发起绑定流程之前，需要检查终端侧的上述第一连接标识关联的第一时间信息，即该第一连接标识处于有效时间内。如果该第一时间信息显示该第一连接标识可用，则终端可以使用该第一连接标识向LMF发送上述绑定请求消息；如果该第一时间信息显示该第一连接标识不可用，则终端不可以使用该第一连接标识向LMF发送上述绑定请求消息。
可选地，本申请实施例中，在上述步骤503之后，本申请实施例提供的连接管理方法还可以包括下述的步骤504。
步骤504、终端接收网络侧设备发送的绑定回复消息。
其中，上述绑定回复消息包括以下至少一项：第二指示信息、上述第三连接标识、第一原因值、第三指示信息。
其中，上述第二指示信息用于指示接受或者拒绝上述绑定请求消息对应的绑定，上述第一原因值用于指示拒绝该绑定请求消息对应的绑定的原因，上述第三指示信息用于指示终端释放用户面连接。
可选地，本申请实施例中，上述第一原因值具体可以用于指示以下至少一项：连接标识无效、连接标识超时、连接标识冲突、绑定不被接受。
可选地，本申请实施例中，上述绑定回复消息可以是通过用户面发送的。
可选地，本申请实施例中，在上述步骤503之后，本申请实施例提供的连接管理方法还可以包括下述的步骤505。
步骤505、终端执行第三操作。
其中，上述第三操作包括以下至少一项：
停止上述第二计时器；
启动上述第三计时器。
可选地，本申请实施例中，一旦发送上述绑定请求消息，终端可以启动上述第三计时器。
可选地，本申请实施例中，在上述步骤502之后，本申请实施例提供的连接管理方法还可以包括下述的步骤506。
步骤506、终端在第二计时器的运行中接收网络侧设备发送的第一消息。
其中，上述第一消息包括以下至少一项：第二连接标识、终端的终端标识、第一指示信息。
其中，上述第一指示信息用于指示终端使用第二连接标识发起绑定过程。
可选地，本申请实施例中，在上述步骤506之后，本申请实施例提供的连接管理方法还可以包括下述的步骤507。
步骤507、终端基于一消息，执行第四操作。
其中，上述第四操作包括以下任一项：
忽略上述第一消息；
重新启动上述第二计时器；
向网络侧设备发送绑定请求消息。
可选地，本申请实施例中，上述步骤507具体可以通过下述的步骤507a或步骤507b实现。
步骤507a、在第二连接标识与第一连接标识相同的情况下，终端忽略第一消息。
步骤507b、在第二连接标识与第一连接标识不同的情况下，终端重新启动第二计时器并向网络侧设备发送绑定请求消息。
示例性地，如图6所示，以网络侧设备为LMF为例，终端和LMF建立用户面连接的流程包括下述的步骤1至步骤6，与上述图4所示的步骤不同的是，步骤2中的消息还可以携带计时器2，当终端收到用户面连接建立命令时，如果用户面连接建立命令可以被接受，那么终端启动计时器2，该计时器2与步骤中收到的LCS-UP连接标识或LCS-UP连接标识的绑定相关联。在步骤4中，一旦终端发送出LCS-UP绑定请求，终端停止计时器2。
又示例性地，如图7所示，以网络侧设备为LMF为例，终端和LMF建立用户面连接的流程包括下述的步骤1至步骤6，与上述图4所示的步骤不同的是，步骤2中的消息还可以携带第一时间信息，使得可以通过检测第一时间信息判断LCS-UP连接标识是否处于有效时间内，从而灵活准确地释放资源。
需要说明的是，在图4、6、7中，虚框内的消息是通过用户面消息发送(比如TCP或IP包，经过基站、UPF转发)，虚框外的消息都是通过控制面消息发送(NAS信令，经过基站、AMF转发)。
对本申请实施例中的其他描述以及各技术特征所能达到的技术效果，具体可以参照上述网络侧设备方法实施例中的相关描述，为了避免重复，此处不再赘述。
本申请实施例提供的连接管理方法，执行主体可以为连接管理装置。本申请实施例中以连接管理装置执行连接管理方法为例，说明本申请实施例提供的连接管理装置。
本申请实施例提供一种连接管理装置，作为一种示例，连接管理装置可以是通信设备或通信设备中的部件，例如芯片。该通信设备可以是终端、网络侧设备或服务器等。示例性的，终端可以包括但不限于上述所列举的终端11的类型，网络侧设备可以包括但不限于上述所列举的网络侧设备12的类型，本申请实施例不作具体限定。
连接管理装置包括接收模块、发送模块和处理模块。其中，接收模块、发送模块和处理模块可以是通过软件实现，也可以通过硬件实现。当通过硬件实现时，处理模块可以由处理器实现，示例性的，处理器可以包括通用处理器、专用处理器等，例如包括中央处理单元(Central Processing Unit，CPU)、微处理器、数字信号处理器(Digital Signal Processor，DSP)、人工智能(Artificial Intelligent，AI)处理器、图形处理器(Graphics Processing Unit，GPU)、专用集成电路(Application Specific Integrated Circuit，ASIC)、网络处理器(Network Processor，NP)、现场可编程门阵列(Field Programmable Gate Array，FPGA)或者其他可编程逻辑器件、门电路、晶体管、分立硬件组件等。接收模块和发送模块可以由通信接口实现，通信接口可以包括收发器、管脚、电路、总线、射频单元等其中一种或多种。
具体的，参见图8，当连接管理装置为网络侧设备或网络侧设备中的部件时，连接管理装置80可以包括第一处理模块81。
其中，第一处理模块81，可以用于在网络侧设备与终端建立用户面连接的过程中，若满足第一条件，则执行第一操作。其中，该第一条件包括以下至少一项：第一计时器超时，该第一计时器与以下至少一项关联：第一连接标识、终端的终端标识、终端的绑定过程、用户面连接的建立过程；第一连接标识未处于有效时间内；该第一操作包括以下至少一项：释放第一连接标识；释放用户面连接；向终端发送第一消息，该第一消息用于指示终端重新建立与网络侧设备的用户面连接；更换定位协议方案。
一种可能的实现方式中，上述第一消息可以包括以下至少一项：第二连接标识、终端的终端标识、第一指示信息。其中，该第一指示信息用于指示终端使用第二连接标识发起绑定过程。
一种可能的实现方式中，第一处理模块81，还可以用于在执行上述第一操作之前，在向终端发送第二消息的情况下，启动第一计时器。其中，该第二消息用于指示终端建立与网络侧设备的用户面连接。
一种可能的实现方式中，上述第二消息可以包括以下至少一项：上述第一连接标识、终端的终端标识、第二计时器的相关信息、第一时间信息。其中，该第二计时器与以下至少一项关联：该第一连接标识、终端绑定过程的发起，该第一时间信息用于指示该第一连接标识的有效时间。
一种可能的实现方式中，第一处理模块81，还可以用于在向终端发送上述第一消息，且该第一消息包括与上述第一连接标识不同的第二连接标识的情况下，重新启动上述第一计时器。
一种可能的实现方式中，连接管理装置80还可以包括第一接收模块。第一接收模块，可以用于在向终端发送上述第二消息之后，接收终端发送的绑定请求消息。其中，该绑定请求消息用于绑定用户面连接和终端，该绑定请求消息包括以下至少一项：第三连接标识、终端的终端标识。
一种可能的实现方式中，上述绑定请求消息可以是通过用户面发送的。
一种可能的实现方式中，连接管理装置80还可以包括第一发送模块。第一发送模块，可以用于在上述第一接收模块接收终端发送的上述绑定请求消息之后，向终端发送绑定回复消息，该绑定回复消息包括以下至少一项：第二指示信息、上述第三连接标识、第一原因值、第三指示信息。其中，该第二指示信息用于指示接受或者拒绝该绑定请求消息对应的绑定，该第一原因值用于指示拒绝该绑定请求消息对应的绑定的原因，该第三指示信息用于指示终端释放用户面连接。
一种可能的实现方式中，上述第一原因值具体可以用于指示以下至少一项：连接标识无效、连接标识超时、连接标识冲突、绑定不被接受。
一种可能的实现方式中，上述绑定回复消息可以是通过用户面发送的。
一种可能的实现方式中，第一处理模块81，还可以用于在上述第一接收模块接收终端发送的绑定请求消息之后，在该绑定请求消息包括上述第三连接标识，且该第三连接标识与上述第一连接标识相同的情况下，停止上述第一计时器。
一种可能的实现方式中，上述第一接收模块，还可以用于在上述第一发送模块向终端发送绑定回复消息之后，接收所述终端发送的第三消息。其中，该第三消息用于指示建立用户面连接失败。
一种可能的实现方式中，上述第三消息可以包括以下至少一项：第二原因值、第四指示信息；其中，该第二原因值用于指示以下至少一项：绑定失败、TLS失败、会话失败、连接标识无效、连接标识超时、连接标识冲突、绑定不被接受；该第四指示信息用于请求重新分配连接标识。
一种可能的实现方式中，上述第三消息可以是通过控制面发送的。
在本申请实施例提供的连接管理装置中，由于在网络侧设备与终端建立用户面连接的过程中，当第一计时器超时或第一连接标识未处于有效时间内时，该连接管理装置可以执行释放第一连接标识、释放用户面连接、向终端发送用于指示重新建立用户面连接的第一消息和更换定位协议方案中的至少一项，因此可以避免终端长时间无效占用第一连接标识，使得网络侧设备可以再分配第一连接标识，从而可以节省资源。
本申请实施例提供的连接管理装置能够实现上述网络侧设备方法实施例实现的各个过程，并达到相同的技术效果，为避免重复，这里不再赘述。
参见图9，当连接管理装置为终端或终端中的部件时，连接管理装置90可以包括第二处理模块91。
其中，第二处理模块91，可以用于在网络侧设备与终端建立用户面连接的过程中，若满足第二条件，则执行第二操作。其中，该第二条件包括以下至少一项：第二计时器超时，该第二计时器与以下至少一项关联：第一连接标识、终端绑定过程的发起；第三计时器超时，该第三计时器与以下至少一项关联：第一连接标识、终端的绑定过程、用户面连接的建立过程；第一连接标识未处于有效时间内；该第二操作包括以下至少一项：向网络侧设备发送绑定请求消息；释放第一连接标识；释放用户面连接；向网络侧设备发送第三消息，该第三消息用于指示建立用户面连接失败；更换定位协议方案。
一种可能的实现方式中，第二处理模块91，还可以用于在执行上述第二操作之前，在接收到网络侧设备发送的第二消息的情况下，启动所述第二计时器。其中，该第二消息用于指示终端建立与网络侧设备的用户面连接。
一种可能的实现方式中，上述第二消息可以包括以下至少一项：上述第一连接标识、终端的终端标识、上述第二计时器的相关信息、第一时间信息。其中，该第二计时器与以下至少一项关联：该第一连接标识、终端绑定过程的发起，该第一时间信息用于指示该第一连接标识的有效时间。
一种可能的实现方式中，终端可以是根据上述第一时间信息判断上述第一连接标识是否处于有效时间内的。
一种可能的实现方式中，连接管理装置90还可以包括第二发送模块。第二发送模块，可以用于在满足第三条件的情况下，向网络侧设备发送绑定请求消息。其中，该绑定请求消息用于绑定用户面连接和终端，该绑定请求消息包括以下至少一项：第三连接标识、终端的终端标识，该第三条件包括以下任一项：上述第二计时器未超时、上述第一连接标识处于有效时间内。
一种可能的实现方式中，上述绑定请求消息可以是通过用户面发送的。
一种可能的实现方式中，连接管理装置90还可以包括第二接收模块。第二接收模块，可以用于在上述第二发送模块向网络侧设备发送上述绑定请求消息之后，接收网络侧设备发送的绑定回复消息，该绑定回复消息包括以下至少一项：第二指示信息、上述第三连接标识、第一原因值、第三指示信息。其中，该第二指示信息用于指示接受或者拒绝该绑定请求消息对应的绑定，该第一原因值用于指示拒绝该绑定请求消息对应的绑定的原因，该第三指示信息用于指示终端释放用户面连接。
一种可能的实现方式中，上述第一原因值具体可以用于指示以下至少一项：连接标识无效、连接标识超时、连接标识冲突、绑定不被接受。
一种可能的实现方式中，上述绑定回复消息可以是通过用户面发送的。
一种可能的实现方式中，第二处理模块91，还可以用于在上述第二发送模块向网络侧设备发送上述绑定请求消息之后，执行第三操作。其中，该第三操作包括以下至少一项：停止上述第二计时器；启动上述第三计时器。
一种可能的实现方式中，上述第二接收模块，还可以用于在第二处理模块91启动上述第二计时器之后，在该第二计时器的运行中接收网络侧设备发送的第一消息，该第一消息包括以下至少一项：第二连接标识、终端的终端标识、第一指示信息。其中，该第一指示信息用于指示终端使用第二连接标识发起绑定过程。
一种可能的实现方式中，第二处理模块91，还可以用于在上述第二接收模块接收网络侧设备发送的上述第一消息之后，基于该一消息，执行第四操作。其中，该第四操作包括以下任一项：忽略该第一消息；重新启动上述第二计时器；向网络侧设备发送绑定请求消息。
一种可能的实现方式中，第二处理模块91，具体可以用于：在上述第二连接标识与上述第一连接标识相同的情况下，忽略上述第一消息；或者，在上述第二连接标识与上述第一连接标识不同的情况下，重新启动上述第二计时器并向网络侧设备发送上述绑定请求消息。
一种可能的实现方式中，上述第三消息可以包括以下至少一项：第二原因值、第四指示信息；其中，该第二原因值用于指示以下至少一项：绑定失败、TLS失败、会话失败、连接标识无效、连接标识超时、连接标识冲突、绑定不被接受；该第四指示信息用于请求重新分配连接标识。
一种可能的实现方式中，上述第三消息可以是通过控制面发送的。
在本申请实施例提供的连接管理装置中，由于在网络侧设备与终端建立用户面连接的过程中，当第二计时器超时、第三计时器超时或第一连接标识未处于有效时间内时，该连接管理装置可以执行向网络侧设备发送绑定请求消息、释放第一连接标识、释放用户面连接、向网络侧设备发送用于指示建立用户面连接失败的第三消息和更换定位协议方案中的至少一项，因此可以避免终端长时间无效占用第一连接标识，使得网络侧设备可以再分配第一连接标识，从而可以节省资源。
本申请实施例提供的连接管理装置能够实现上述终端侧方法实施例实现的各个过程，并达到相同的技术效果，为避免重复，这里不再赘述。
如图10所示，本申请实施例还提供一种通信设备100，包括处理器101和存储器102，存储器102上存储有可在所述处理器101上运行的程序或指令，例如，该通信设备100为终端时，该程序或指令被处理器101执行时实现上述终端侧方法实施例的各个步骤，且能达到相同的技术效果。该通信设备100为网络侧设备时，该程序或指令被处理器101执行时实现上述网络侧设备方法实施例的各个步骤，且能达到相同的技术效果，为避免重复，这里不再赘述。
本申请实施例还提供一种终端，包括处理器和通信接口，所述通信接口和所述处理器耦合，所述处理器用于运行程序或指令，实现上述终端侧方法实施例中的步骤。该终端实施例与上述终端侧方法实施例对应，上述方法实施例的各个实施过程和实现方式均可适用于该终端实施例中，且能达到相同的技术效果。该终端可以是图9所示的连接管理装置。具体地，图11为实现本申请实施例的一种终端的硬件结构示意图。
该终端1000包括但不限于：射频单元1001、网络模块1002、音频输出单元1003、输入单元1004、传感器1005、显示单元1006、用户输入单元1007、接口单元1008、存储器1009以及处理器1010等中的至少部分部件。
本领域技术人员可以理解，终端1000还可以包括给各个部件供电的电源(比如电池)，电源可以通过电源管理系统与处理器1010逻辑相连，从而通过电源管理系统实现管理充电、放电以及功耗管理等功能。图11中示出的终端结构并不构成对终端的限定，终端可以包括比图示更多或更少的部件，或者组合某些部件，或者不同的部件布置，在此不再赘述。
应理解的是，本申请实施例中，输入单元1004可以包括图形处理器10041和麦克风10042，图形处理器10041对在视频捕获模式或图像捕获模式中由图像捕获装置(如摄像头)获得的静态图片或视频的图像数据进行处理。显示单元1006可包括显示面板10061，可以采用液晶显示器、有机发光二极管等形式来配置显示面板10061。用户输入单元1007包括触控面板10071以及其他输入设备10072中的至少一种。触控面板10071，也称为触摸屏。触控面板10071可包括触摸检测装置和触摸控制器两个部分。其他输入设备10072可以包括但不限于物理键盘、功能键(比如音量控制按键、开关按键等)、轨迹球、鼠标、操作杆，在此不再赘述。
本申请实施例中，射频单元1001接收来自网络侧设备的下行数据后，可以传输给处理器1010进行处理；另外，射频单元1001可以向网络侧设备发送上行数据。通常，射频单元1001包括但不限于天线、放大器、收发器、耦合器、低噪声放大器、双工器等。
存储器1009可用于存储软件程序或指令以及各种数据。存储器1009可主要包括存储程序或指令的第一存储区和存储数据的第二存储区，其中，第一存储区可存储操作系统、至少一个功能所需的应用程序或指令(比如声音播放功能、图像播放功能等)等。此外，存储器1009可以包括易失性存储器或非易失性存储器。其中，非易失性存储器可以是只读存储器(Read-Only Memory，ROM)、可编程只读存储器(Programmable ROM，PROM)、可擦除可编程只读存储器(Erasable PROM，EPROM)、电可擦除可编程只读存储器(Electrically EPROM，EEPROM)或闪存。易失性存储器可以是随机存取存储器(Random Access Memory，RAM)，静态随机存取存储器(Static RAM，SRAM)、动态随机存取存储器(Dynamic RAM，DRAM)、同步动态随机存取存储器(Synchronous DRAM，SDRAM)、双倍数据速率同步动态随机存取存储器(Double Data Rate SDRAM，DDRSDRAM)、增强型同步动态随机存取存储器(Enhanced SDRAM，ESDRAM)、同步连接动态随机存取存储器(Synch link DRAM，SLDRAM)和直接内存总线随机存取存储器(Direct Rambus RAM，DRRAM)。本申请实施例中的存储器1009包括但不限于这些和任意其它适合类型的存储器。
处理器1010可包括一个或多个处理单元；可选的，处理器1010集成应用处理器和调制解调处理器，其中，应用处理器主要处理涉及操作系统、用户界面和应用程序等的操作，调制解调处理器主要处理无线通信信号，如基带处理器。可以理解的是，上述调制解调处理器也可以不集成到处理器1010中。
其中，处理器1010，可以用于在网络侧设备与终端1000建立用户面连接的过程中，若满足第二条件，则执行第二操作。其中，该第二条件包括以下至少一项：第二计时器超时，该第二计时器与以下至少一项关联：第一连接标识、终端1000绑定过程的发起；第三计时器超时，该第三计时器与以下至少一项关联：第一连接标识、终端1000的绑定过程、用户面连接的建立过程；第一连接标识未处于有效时间内；该第二操作包括以下至少一项：向网络侧设备发送绑定请求消息；释放第一连接标识；释放用户面连接；向网络侧设备发送第三消息，该第三消息用于指示建立用户面连接失败；更换定位协议方案。
一种可能的实现方式中，处理器1010，还可以用于在执行上述第二操作之前，在接收到网络侧设备发送的第二消息的情况下，启动所述第二计时器。其中，该第二消息用于指示终端1000建立与网络侧设备的用户面连接。
一种可能的实现方式中，上述第二消息可以包括以下至少一项：上述第一连接标识、终端1000的终端标识、上述第二计时器的相关信息、第一时间信息。其中，该第二计时器与以下至少一项关联：该第一连接标识、终端1000绑定过程的发起，该第一时间信息用于指示该第一连接标识的有效时间。
一种可能的实现方式中，终端1000可以是根据上述第一时间信息判断上述第一连接标识是否处于有效时间内的。
一种可能的实现方式中，射频单元1001，可以用于在满足第三条件的情况下，向网络侧设备发送绑定请求消息。其中，该绑定请求消息用于绑定用户面连接和终端1000，该绑定请求消息包括以下至少一项：第三连接标识、终端1000的终端标识，该第三条件包括以下任一项：上述第二计时器未超时、上述第一连接标识处于有效时间内。
一种可能的实现方式中，上述绑定请求消息可以是通过用户面发送的。
一种可能的实现方式中，射频单元1001，还可以用于在向网络侧设备发送上述绑定请求消息之后，接收网络侧设备发送的绑定回复消息，该绑定回复消息包括以下至少一项：第二指示信息、上述第三连接标识、第一原因值、第三指示信息。其中，该第二指示信息用于指示接受或者拒绝该绑定请求消息对应的绑定，该第一原因值用于指示拒绝该绑定请求消息对应的绑定的原因，该第三指示信息用于指示终端1000释放用户面连接。
一种可能的实现方式中，上述第一原因值具体可以用于指示以下至少一项：连接标识无效、连接标识超时、连接标识冲突、绑定不被接受。
一种可能的实现方式中，上述绑定回复消息可以是通过用户面发送的。
一种可能的实现方式中，处理器1010，还可以用于在射频单元1001向网络侧设备发送上述绑定请求消息之后，执行第三操作。其中，该第三操作包括以下至少一项：停止上述第二计时器；启动上述第三计时器。
一种可能的实现方式中，射频单元1001，还可以用于在处理器1010启动上述第二计时器之后，在该第二计时器的运行中接收网络侧设备发送的第一消息，该第一消息包括以下至少一项：第二连接标识、终端1000的终端标识、第一指示信息。其中，该第一指示信息用于指示终端1000使用第二连接标识发起绑定过程。
一种可能的实现方式中，处理器1010，还可以用于在射频单元1001接收网络侧设备发送的上述第一消息之后，基于该一消息，执行第四操作。其中，该第四操作包括以下任一项：忽略该第一消息；重新启动上述第二计时器；向网络侧设备发送绑定请求消息。
一种可能的实现方式中，处理器1010，具体可以用于：在上述第二连接标识与上述第一连接标识相同的情况下，忽略上述第一消息；或者，在上述第二连接标识与上述第一连接标识不同的情况下，重新启动上述第二计时器并向网络侧设备发送上述绑定请求消息。
一种可能的实现方式中，上述第三消息可以包括以下至少一项：第二原因值、第四指示信息；其中，该第二原因值用于指示以下至少一项：绑定失败、TLS失败、会话失败、连接标识无效、连接标识超时、连接标识冲突、绑定不被接受；该第四指示信息用于请求重新分配连接标识。
一种可能的实现方式中，上述第三消息可以是通过控制面发送的。
在本申请实施例提供的终端中，由于在网络侧设备与终端建立用户面连接的过程中，当第二计时器超时、第三计时器超时或第一连接标识未处于有效时间内时，该终端可以执行向网络侧设备发送绑定请求消息、释放第一连接标识、释放用户面连接、向网络侧设备发送用于指示建立用户面连接失败的第三消息和更换定位协议方案中的至少一项，因此可以避免终端长时间无效占用第一连接标识，使得网络侧设备可以再分配第一连接标识，从而可以节省资源。
可以理解，本实施例中提及的各实现方式的实现过程可以参照上述终端侧方法实施例的相关描述，并达到相同或相应的技术效果，为避免重复，在此不再赘述。
本申请实施例还提供一种网络侧设备，包括处理器和通信接口，所述通信接口和所述处理器耦合，所述处理器用于运行程序或指令，实现上述网络侧设备方法实施例的步骤。该网络侧设备实施例与上述网络侧设备方法实施例对应，上述方法实施例的各个实施过程和实现方式均可适用于该网络侧设备实施例中，且能达到相同的技术效果。
具体地，本申请实施例还提供了一种网络侧设备。如图12所示，该网络侧设备1100包括：处理器1101、网络接口1102和存储器1103。该网络侧设备可以是图8所示的连接管理装置。其中，网络接口1102例如为通用公共无线接口(common public radio interface，CPRI)。
具体地，本申请实施例的网络侧设备1100还包括：存储在存储器1103上并可在处理器1101上运行的指令或程序，处理器1101调用存储器1103中的指令或程序执行上述网络侧设备执行的方法，并达到相同的技术效果，为避免重复，故不在此赘述。
其中，处理器1101，可以用于在网络侧设备1100与终端建立用户面连接的过程中，若满足第一条件，则执行第一操作。其中，该第一条件包括以下至少一项：第一计时器超时，该第一计时器与以下至少一项关联：第一连接标识、终端的终端标识、终端的绑定过程、用户面连接的建立过程；第一连接标识未处于有效时间内；该第一操作包括以下至少一项：释放第一连接标识；释放用户面连接；向终端发送第一消息，该第一消息用于指示终端重新建立与网络侧设备1100的用户面连接；更换定位协议方案。
一种可能的实现方式中，上述第一消息可以包括以下至少一项：第二连接标识、终端的终端标识、第一指示信息。其中，该第一指示信息用于指示终端使用第二连接标识发起绑定过程。
一种可能的实现方式中，处理器1101，还可以用于在执行上述第一操作之前，在向终端发送第二消息的情况下，启动第一计时器。其中，该第二消息用于指示终端建立与网络侧设备1100的用户面连接。
一种可能的实现方式中，上述第二消息可以包括以下至少一项：上述第一连接标识、终端的终端标识、第二计时器的相关信息、第一时间信息。其中，该第二计时器与以下至少一项关联：该第一连接标识、终端绑定过程的发起，该第一时间信息用于指示该第一连接标识的有效时间。
一种可能的实现方式中，处理器1101，还可以用于在向终端发送上述第一消息，且该第一消息包括与上述第一连接标识不同的第二连接标识的情况下，重新启动上述第一计时器。
一种可能的实现方式中，网络接口1102，可以用于在向终端发送上述第二消息之后，接收终端发送的绑定请求消息。其中，该绑定请求消息用于绑定用户面连接和终端，该绑定请求消息包括以下至少一项：第三连接标识、终端的终端标识。
一种可能的实现方式中，上述绑定请求消息可以是通过用户面发送的。
一种可能的实现方式中，网络接口1102，还可以用于在接收终端发送的上述绑定请求消息之后，向终端发送绑定回复消息，该绑定回复消息包括以下至少一项：第二指示信息、上述第三连接标识、第一原因值、第三指示信息。其中，该第二指示信息用于指示接受或者拒绝该绑定请求消息对应的绑定，该第一原因值用于指示拒绝该绑定请求消息对应的绑定的原因，该第三指示信息用于指示终端释放用户面连接。
一种可能的实现方式中，上述第一原因值具体可以用于指示以下至少一项：连接标识无效、连接标识超时、连接标识冲突、绑定不被接受。
一种可能的实现方式中，上述绑定回复消息可以是通过用户面发送的。
一种可能的实现方式中，处理器1101，还可以用于在网络接口1102接收终端发送的绑定请求消息之后，在该绑定请求消息包括上述第三连接标识，且该第三连接标识与上述第一连接标识相同的情况下，停止上述第一计时器。
一种可能的实现方式中，网络接口1102，还可以用于在向终端发送绑定回复消息之后，接收所述终端发送的第三消息。其中，该第三消息用于指示建立用户面连接失败。
一种可能的实现方式中，上述第三消息可以包括以下至少一项：第二原因值、第四指示信息；其中，该第二原因值用于指示以下至少一项：绑定失败、TLS失败、会话失败、连接标识无效、连接标识超时、连接标识冲突、绑定不被接受；该第四指示信息用于请求重新分配连接标识。
一种可能的实现方式中，上述第三消息可以是通过控制面发送的。
在本申请实施例提供的网络侧设备中，由于在网络侧设备与终端建立用户面连接的过程中，当第一计时器超时或第一连接标识未处于有效时间内时，该网络侧设备可以执行释放第一连接标识、释放用户面连接、向终端发送用于指示重新建立用户面连接的第一消息和更换定位协议方案中的至少一项，因此可以避免终端长时间无效占用第一连接标识，使得网络侧设备可以再分配第一连接标识，从而可以节省资源。
可以理解，本实施例中提及的各实现方式的实现过程可以参照上述网络侧设备方法实施例的相关描述，并达到相同或相应的技术效果，为避免重复，在此不再赘述。
本申请实施例还提供一种可读存储介质，所述可读存储介质上存储有程序或指令，该程序或指令被处理器执行时实现上述连接管理方法实施例的各个过程，且能达到相同的技术效果，为避免重复，这里不再赘述。
其中，所述处理器为上述实施例中所述的终端中的处理器。所述可读存储介质，包括计算机可读存储介质，如计算机只读存储器ROM、随机存取存储器RAM、磁碟或者光盘等。在一些示例中，可读存储介质可以是非瞬态的可读存储介质。
本申请实施例另提供了一种芯片，所述芯片包括处理器和通信接口，所述通信接口和所述处理器耦合，所述处理器用于运行程序或指令，实现上述连接管理方法实施例的各个过程，且能达到相同的技术效果，为避免重复，这里不再赘述。
应理解，本申请实施例提到的芯片还可以称为系统级芯片，系统芯片，芯片系统或片上系统芯片等。
本申请实施例另提供了一种计算机程序/程序产品，所述计算机程序/程序产品被存储在存储介质中，所述计算机程序/程序产品被至少一个处理器执行以实现上述连接管理方法实施例的各个过程，且能达到相同的技术效果，为避免重复，这里不再赘述。
本申请实施例还提供了一种通信系统，包括：终端及网络侧设备，所述终端可用于执行如上所述的终端侧方法的步骤，所述网络侧设备可用于执行如上所述的网络侧设备方法的步骤。
需要说明的是，在本文中，术语“包括”、“包含”或者其任何其他变体意在涵盖非排他性的包含，从而使得包括一系列要素的过程、方法、物品或者装置不仅包括那些要素，而且还包括没有明确列出的其他要素，或者是还包括为这种过程、方法、物品或者装置所固有的要素。在没有更多限制的情况下，由语句“包括一个……”限定的要素，并不排除在包括该要素的过程、方法、物品或者装置中还存在另外的相同要素。此外，需要指出的是，本申请实施方式中的方法和装置的范围不限按示出或讨论的顺序来执行功能，还可包括根据所涉及的功能按基本同时的方式或按相反的顺序来执行功能，例如，可以按不同于所描述的次序来执行所描述的方法，并且还可以添加、省去或组合各种步骤。另外，参照某些示例所描述的特征可在其他示例中被组合。
通过以上的实施方式的描述，本领域的技术人员可以清楚地了解到上述实施例方法可借助计算机软件产品加必需的通用硬件平台的方式来实现，当然也可以通过硬件。该计算机软件产品存储在存储介质(如ROM、RAM、磁碟、光盘等)中，包括若干指令，用以使得终端或者网络侧设备执行本申请各个实施例所述的方法。
上面结合附图对本申请的实施例进行了描述，但是本申请并不局限于上述的具体实施方式，上述的具体实施方式仅仅是示意性的，而不是限制性的，本领域的普通技术人员在本申请的启示下，在不脱离本申请宗旨和权利要求所保护的范围情况下，还可做出很多形式的实施方式，这些实施方式均属于本申请的保护之内。

Claims (49)

  1. 一种连接管理方法，所述方法包括：
    在网络侧设备与终端建立用户面连接的过程中，若满足第一条件，则所述网络侧设备执行第一操作；
    其中，所述第一条件包括以下至少一项：
    第一计时器超时，所述第一计时器与以下至少一项关联：第一连接标识、所述终端的终端标识、所述终端的绑定过程、用户面连接的建立过程；
    第一连接标识未处于有效时间内；
    所述第一操作包括以下至少一项：
    释放第一连接标识；
    释放用户面连接；
    向所述终端发送第一消息，所述第一消息用于指示所述终端重新建立与所述网络侧设备的用户面连接；
    更换定位协议方案。
  2. 根据权利要求1所述的方法，其中，所述第一消息包括以下至少一项：第二连接标识、所述终端的终端标识、第一指示信息；
    其中，所述第一指示信息用于指示所述终端使用第二连接标识发起绑定过程。
  3. 根据权利要求1或2所述的方法，其中，所述网络侧设备执行第一操作之前，所述方法还包括：
    在向所述终端发送第二消息的情况下，所述网络侧设备启动第一计时器；
    其中，所述第二消息用于指示所述终端建立与所述网络侧设备的用户面连接。
  4. 根据权利要求3所述的方法，其中，所述第二消息包括以下至少一项：所述第一连接标识、所述终端的终端标识、第二计时器的相关信息、第一时间信息；
    其中，所述第二计时器与以下至少一项关联：所述第一连接标识、所述终端绑定过程的发起，所述第一时间信息用于指示所述第一连接标识的有效时间。
  5. 根据权利要求3或4所述的方法，其中，所述方法还包括：
    在向所述终端发送所述第一消息，且所述第一消息包括与所述第一连接标识不同的第二连接标识的情况下，所述网络侧设备重新启动所述第一计时器。
  6. 根据权利要求3至5中任一项所述的方法，其中，所述方法还包括：
    在向所述终端发送所述第二消息之后，所述网络侧设备接收所述终端发送的绑定请求消息；
    其中，所述绑定请求消息用于绑定用户面连接和所述终端，所述绑定请求消息包括以下至少一项：第三连接标识、所述终端的终端标识。
  7. 根据权利要求6所述的方法，其中，所述绑定请求消息是通过用户面发送的。
  8. 根据权利要求6或7所述的方法，其中，所述网络侧设备接收所述终端发送的绑定请求消息之后，所述方法还包括：
    所述网络侧设备向所述终端发送绑定回复消息，所述绑定回复消息包括以下至少一项：第二指示信息、所述第三连接标识、第一原因值、第三指示信息；
    其中，所述第二指示信息用于指示接受或者拒绝所述绑定请求消息对应的绑定，所述第一原因值用于指示拒绝所述绑定请求消息对应的绑定的原因，所述第三指示信息用于指示所述终端释放用户面连接。
  9. 根据权利要求8所述的方法，其中，所述第一原因值具体用于指示以下至少一项：连接标识无效、连接标识超时、连接标识冲突、绑定不被接受。
  10. 根据权利要求8或9所述的方法，其中，所述绑定回复消息是通过用户面发送的。
  11. 根据权利要求6至10中任一项所述的方法，其中，所述网络侧设备接收所述终端发送的绑定请求消息之后，所述方法还包括：
    在所述绑定请求消息包括所述第三连接标识，且所述第三连接标识与所述第一连接标识相同的情况下，所述网络侧设备停止所述第一计时器。
  12. 根据权利要求8至11中任一项所述的方法，其中，所述网络侧设备向所述终端发送绑定回复消息之后，所述方法还包括：
    所述网络侧设备接收所述终端发送的第三消息；
    其中，所述第三消息用于指示建立用户面连接失败。
  13. 根据权利要求12所述的方法，其中，所述第三消息包括以下至少一项：第二原因值、第四指示信息；
    其中，所述第二原因值用于指示以下至少一项：绑定失败、安全传输层协议TLS失败、会话失败、连接标识无效、连接标识超时、连接标识冲突、绑定不被接受；所述第四指示信息用于请求重新分配连接标识。
  14. 根据权利要求12或13所述的方法，其中，所述第三消息是通过控制面发送的。
  15. 一种连接管理方法，所述方法包括：
    在网络侧设备与终端建立用户面连接的过程中，若满足第二条件，则所述终端执行第二操作；
    其中，所述第二条件包括以下至少一项：
    第二计时器超时，所述第二计时器与以下至少一项关联：第一连接标识、所述终端绑定过程的发起；
    第三计时器超时，所述第三计时器与以下至少一项关联：第一连接标识、所述终端的绑定过程、用户面连接的建立过程；
    第一连接标识未处于有效时间内；
    所述第二操作包括以下至少一项：
    向所述网络侧设备发送绑定请求消息；
    释放第一连接标识；
    释放用户面连接；
    向所述网络侧设备发送第三消息，所述第三消息用于指示建立用户面连接失败；
    更换定位协议方案。
  16. 根据权利要求15所述的方法，其中，所述终端执行第二操作之前，所述方法还包括：
    在接收到所述网络侧设备发送的第二消息的情况下，所述终端启动所述第二计时器；
    其中，所述第二消息用于指示所述终端建立与所述网络侧设备的用户面连接。
  17. 根据权利要求16所述的方法，其中，所述第二消息包括以下至少一项：所述第一连接标识、所述终端的终端标识、所述第二计时器的相关信息、第一时间信息；
    其中，所述第二计时器与以下至少一项关联：所述第一连接标识、所述终端绑定过程的发起，所述第一时间信息用于指示所述第一连接标识的有效时间。
  18. 根据权利要求17所述的方法，其中，所述终端是根据所述第一时间信息判断所述第一连接标识是否处于有效时间内的。
  19. 根据权利要求16至18中任一项所述的方法，其中，所述方法还包括：
    在满足第三条件的情况下，所述终端向所述网络侧设备发送绑定请求消息；
    其中，所述绑定请求消息用于绑定用户面连接和所述终端，所述绑定请求消息包括以下至少一项：第三连接标识、所述终端的终端标识，所述第三条件包括以下任一项：所述第二计时器未超时、所述第一连接标识处于有效时间内。
  20. 根据权利要求19所述的方法，其中，所述绑定请求消息是通过用户面发送的。
  21. 根据权利要求19或20所述的方法，其中，所述终端向所述网络侧设备发送绑定请求消息之后，所述方法还包括：
    所述终端接收所述网络侧设备发送的绑定回复消息，所述绑定回复消息包括以下至少一项：第二指示信息、所述第三连接标识、第一原因值、第三指示信息；
    其中，所述第二指示信息用于指示接受或者拒绝所述绑定请求消息对应的绑定，所述第一原因值用于指示拒绝所述绑定请求消息对应的绑定的原因，所述第三指示信息用于指示所述终端释放用户面连接。
  22. 根据权利要求21所述的方法，其中，所述第一原因值具体用于指示以下至少一项：连接标识无效、连接标识超时、连接标识冲突、绑定不被接受。
  23. 根据权利要求21或22所述的方法，其中，所述绑定回复消息是通过用户面发送的。
  24. 根据权利要求19至23中任一项所述的方法，其中，所述终端向所述网络侧设备发送绑定请求消息之后，所述方法还包括：
    所述终端执行第三操作；
    其中，所述第三操作包括以下至少一项：
    停止所述第二计时器；
    启动所述第三计时器。
  25. 根据权利要求16至24中任一项所述的方法，其中，所述终端启动所述第二计时器之后，所述方法还包括：
    所述终端在所述第二计时器的运行中接收所述网络侧设备发送的第一消息，所述第一消息包括以下至少一项：第二连接标识、所述终端的终端标识、第一指示信息；
    其中，所述第一指示信息用于指示所述终端使用第二连接标识发起绑定过程。
  26. 根据权利要求25所述的方法，其中，所述终端在接收所述网络侧设备发送的第一消息之后，所述方法还包括：
    所述终端基于所述第一消息，执行第四操作；
    其中，所述第四操作包括以下任一项：
    忽略所述第一消息；
    重新启动所述第二计时器；
    向所述网络侧设备发送绑定请求消息。
  27. 根据权利要求26所述的方法，其中，所述终端基于所述第一消息，执行第四操作，包括：
    在所述第二连接标识与所述第一连接标识相同的情况下，所述终端忽略所述第一消息；
    或者，
    在所述第二连接标识与所述第一连接标识不同的情况下，所述终端重新启动所述第二计时器并向所述网络侧设备发送所述绑定请求消息。
  28. 根据权利要求15至27中任一项所述的方法，其中，所述第三消息包括以下至少一项：第二原因值、第四指示信息；
    其中，所述第二原因值用于指示以下至少一项：绑定失败、TLS失败、会话失败、连接标识无效、连接标识超时、连接标识冲突、绑定不被接受；所述第四指示信息用于请求重新分配连接标识。
  29. 根据权利要求15至28中任一项所述的方法，其中，所述第三消息是通过控制面发送的。
  30. 一种连接管理装置，所述装置包括第一处理模块；
    所述第一处理模块，用于在网络侧设备与终端建立用户面连接的过程中，若满足第一条件，则执行第一操作；
    其中，所述第一条件包括以下至少一项：
    第一计时器超时，所述第一计时器与以下至少一项关联：第一连接标识、所述终端的终端标识、所述终端的绑定过程、用户面连接的建立过程；
    第一连接标识未处于有效时间内；
    所述第一操作包括以下至少一项：
    释放第一连接标识；
    释放用户面连接；
    向所述终端发送第一消息，所述第一消息用于指示所述终端重新建立与所述网络侧设备的用户面连接；
    更换定位协议方案。
  31. 根据权利要求30所述的装置，其中，
    所述第一处理模块，还用于在执行所述第一操作之前，在向所述终端发送第二消息的情况下，启动第一计时器；
    其中，所述第二消息用于指示所述终端建立与所述网络侧设备的用户面连接。
  32. 根据权利要求30所述的装置，其中，
    所述第一处理模块，还用于在向所述终端发送所述第一消息，且所述第一消息包括与所述第一连接标识不同的第二连接标识的情况下，重新启动所述第一计时器。
  33. 根据权利要求31或32所述的装置，其中，所述装置还包括第一接收模块；
    所述第一接收模块，用于在向所述终端发送所述第二消息之后，接收所述终端发送的绑定请求消息；
    其中，所述绑定请求消息用于绑定用户面连接和所述终端，所述绑定请求消息包括以下至少一项：第三连接标识、所述终端的终端标识。
  34. 根据权利要求33所述的装置，其中，所述装置还包括第一发送模块；
    所述第一发送模块，用于在所述第一接收模块接收所述终端发送的绑定请求消息之后，向所述终端发送绑定回复消息，所述绑定回复消息包括以下至少一项：第二指示信息、所述第三连接标识、第一原因值、第三指示信息；
    其中，所述第二指示信息用于指示接受或者拒绝所述绑定请求消息对应的绑定，所述第一原因值用于指示拒绝所述绑定请求消息对应的绑定的原因，所述第三指示信息用于指示所述终端释放用户面连接。
  35. 根据权利要求33或34所述的装置，其中，
    所述第一处理模块，还用于在所述第一接收模块接收所述终端发送的绑定请求消息之后，在所述绑定请求消息包括所述第三连接标识，且所述第三连接标识与所述第一连接标识相同的情况下，停止所述第一计时器。
  36. 根据权利要求34所述的装置，其中，
    所述第一接收模块，还用于在所述第一发送模块向所述终端发送绑定回复消息之后，接收所述终端发送的第三消息；
    其中，所述第三消息用于指示建立用户面连接失败。
  37. 一种连接管理装置，所述装置包括第二处理模块；
    所述第二处理模块，用于在网络侧设备与终端建立用户面连接的过程中，若满足第二条件，则执行第二操作；
    其中，所述第二条件包括以下至少一项：
    第二计时器超时，所述第二计时器与以下至少一项关联：第一连接标识、所述终端绑定过程的发起；
    第三计时器超时，所述第三计时器与以下至少一项关联：第一连接标识、所述终端的绑定过程、用户面连接的建立过程；
    第一连接标识未处于有效时间内；
    所述第二操作包括以下至少一项：
    向所述网络侧设备发送绑定请求消息；
    释放第一连接标识；
    释放用户面连接；
    向所述网络侧设备发送第三消息，所述第三消息用于指示建立用户面连接失败；
    更换定位协议方案。
  38. 根据权利要求37所述的装置，其中，
    所述第二处理模块，还用于在执行所述第二操作之前，在接收到所述网络侧设备发送的第二消息的情况下，启动所述第二计时器；
    其中，所述第二消息用于指示所述终端建立与所述网络侧设备的用户面连接。
  39. 根据权利要求38所述的装置，其中，所述装置还包括第二发送模块；
    所述第二发送模块，用于在满足第三条件的情况下，向所述网络侧设备发送绑定请求消息；
    其中，所述绑定请求消息用于绑定用户面连接和所述终端，所述绑定请求消息包括以下至少一项：第三连接标识、所述终端的终端标识，所述第三条件包括以下任一项：所述第二计时器未超时、所述第一连接标识处于有效时间内。
  40. 根据权利要求39所述的装置，其中，所述装置还包括第二接收模块；
    所述第二接收模块，用于在所述第二发送模块向所述网络侧设备发送绑定请求消息之后，接收所述网络侧设备发送的绑定回复消息，所述绑定回复消息包括以下至少一项：第二指示信息、所述第三连接标识、第一原因值、第三指示信息；
    其中，所述第二指示信息用于指示接受或者拒绝所述绑定请求消息对应的绑定，所述第一原因值用于指示拒绝所述绑定请求消息对应的绑定的原因，所述第三指示信息用于指示所述终端释放用户面连接。
  41. 根据权利要求39或40所述的装置，其中，
    所述第二处理模块，还用于在所述第二发送模块向所述网络侧设备发送绑定请求消息之后，执行第三操作；
    其中，所述第三操作包括以下至少一项：
    停止所述第二计时器；
    启动所述第三计时器。
  42. 根据权利要求38所述的装置，其中，所述装置还包括第二接收模块；
    所述第二接收模块，用于在所述第二处理模块启动所述第二计时器之后，在所述第二计时器的运行中接收所述网络侧设备发送的第一消息，所述第一消息包括以下至少一项：第二连接标识、所述终端的终端标识、第一指示信息；
    其中，所述第一指示信息用于指示所述终端使用第二连接标识发起绑定过程。
  43. 根据权利要求42所述的装置，其中，
    所述第二处理模块，还用于在所述第二接收模块在接收所述网络侧设备发送的第一消息之后，基于所述第一消息，执行第四操作；
    其中，所述第四操作包括以下任一项：
    忽略所述第一消息；
    重新启动所述第二计时器；
    向所述网络侧设备发送绑定请求消息。
  44. 一种网络侧设备，包括处理器和存储器，所述存储器存储可在所述处理器上运行的程序或指令，所述程序或指令被所述处理器执行时实现如权利要求1至14任一项所述的连接管理方法的步骤。
  45. 一种终端，包括处理器和存储器，所述存储器存储可在所述处理器上运行的程序或指令，所述程序或指令被所述处理器执行时实现如权利要求15至29任一项所述的连接管理方法的步骤。
  46. 一种可读存储介质，所述可读存储介质上存储程序或指令，所述程序或指令被处理器执行时实现如权利要求1至14任一项所述的连接管理方法，或者实现如权利要求15至29任一项所述的连接管理方法的步骤。
  47. 一种计算机程序产品，所述计算机程序产品被至少一个处理器执行以实现如权利要求1至14任一项所述的连接管理方法，或者实现如权利要求15至29任一项所述的连接管理方法。
  48. 一种电子设备，包括所述电子设备被配置成用于执行如权利要求1至14任一项所述的连接管理方法，或者执行如权利要求15至29任一项所述的连接管理方法。
  49. 一种芯片，所述芯片包括处理器和通信接口，所述通信接口和所述处理器耦合，所述处理器用于运行程序或指令，实现如权利要求1至14任一项所述的连接管理方法，或者实现如权利要求15至29任一项所述的连接管理方法。
PCT/CN2025/093965 2024-05-16 2025-05-09 连接管理方法、装置、终端及网络侧设备 Pending WO2025237207A1 (zh)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN202410611734.7 2024-05-16
CN202410611734.7A CN120980720A (zh) 2024-05-16 2024-05-16 连接管理方法、装置、终端及网络侧设备

Publications (1)

Publication Number Publication Date
WO2025237207A1 true WO2025237207A1 (zh) 2025-11-20

Family

ID=97647094

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2025/093965 Pending WO2025237207A1 (zh) 2024-05-16 2025-05-09 连接管理方法、装置、终端及网络侧设备

Country Status (2)

Country Link
CN (1) CN120980720A (zh)
WO (1) WO2025237207A1 (zh)

Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2018126535A1 (zh) * 2017-01-09 2018-07-12 华为技术有限公司 一种会话管理方法及装置
WO2021168713A1 (zh) * 2020-02-26 2021-09-02 华为技术有限公司 通信方法及装置
CN114071649A (zh) * 2020-07-31 2022-02-18 华为技术有限公司 访问本地网络的方法和装置
CN115884112A (zh) * 2021-09-28 2023-03-31 中国移动通信集团设计院有限公司 语音接续方法、装置、系统、设备和存储介质
CN117917180A (zh) * 2023-12-07 2024-04-19 北京小米移动软件有限公司 连接释放方法、设备和存储介质

Patent Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2018126535A1 (zh) * 2017-01-09 2018-07-12 华为技术有限公司 一种会话管理方法及装置
WO2021168713A1 (zh) * 2020-02-26 2021-09-02 华为技术有限公司 通信方法及装置
CN114071649A (zh) * 2020-07-31 2022-02-18 华为技术有限公司 访问本地网络的方法和装置
CN115884112A (zh) * 2021-09-28 2023-03-31 中国移动通信集团设计院有限公司 语音接续方法、装置、系统、设备和存储介质
CN117917180A (zh) * 2023-12-07 2024-04-19 北京小米移动软件有限公司 连接释放方法、设备和存储介质

Also Published As

Publication number Publication date
CN120980720A (zh) 2025-11-18

Similar Documents

Publication Publication Date Title
US20240188047A1 (en) Computing session update method and apparatus, and communication device
WO2020134873A1 (zh) 一种状态切换的方法、移动终端、网络设备及通信系统
US20250142446A1 (en) Identity configuration method and apparatus, terminal, and storage medium
CN111556565A (zh) 一种寻呼方法和寻呼设备
CN114080045B (zh) 数据发送处理方法、资源配置方法及相关设备
US20250024285A1 (en) Method and apparatus for determining radio link failure, and terminal and network side device
US11246065B2 (en) Method, apparatus, terminal and storage medium for measurement report
KR20240047394A (ko) 이중 연결을 이용한 복제를 위한 생존 시간 상태 트리거링 및 폴백 기법
CN114679750B (zh) 切换小区的方法、终端设备和网络设备
US20240147554A1 (en) Relay Identification Method, Relay Determining Method, Terminal, and Network Side Device
WO2025237207A1 (zh) 连接管理方法、装置、终端及网络侧设备
EP4503742A1 (en) Resource control method and apparatus, terminal, and network side device
WO2024022163A1 (zh) 定位方法、终端及网络设备
WO2023202560A1 (zh) 辅小区组信息发送方法、接收方法、终端、设备和介质
CN117221863A (zh) 一种快速建立紧急呼叫方法、装置、电子设备和存储介质
US20260067790A1 (en) Information processing method and apparatus, information transmission method and apparatus, and related device
US20260012877A1 (en) Path switching processing method and apparatus, and terminal
US20260101170A1 (en) Information exchange method and apparatus, terminal, and network-side device
JP7641996B2 (ja) メッセージ送信方法、受信方法、装置及び通信機器
WO2024169805A1 (zh) 配置更新方法、配置更新装置、终端及网络侧设备
WO2025092789A1 (zh) 传输方法、装置、终端及网络侧设备
WO2024140570A1 (zh) 策略配置方法、装置、终端、网络侧设备及可读存储介质
WO2026012474A1 (zh) 通话方法、信息传输方法、装置及设备
CN119893531A (zh) 承载建立方法、装置、终端、网络设备及可读存储介质
WO2024103268A1 (zh) 连接失败后的处理方法、装置、终端设备以及网络侧设备

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 25802856

Country of ref document: EP

Kind code of ref document: A1