Transmission method and apparatus, terminal and network side device

Abstract

The present application relates to the technical field of communications. Disclosed are a transmission method and apparatus, a terminal and a network side device. The transmission method provided by embodiments of the present application comprises: a terminal receives a first message sent by a first network element, wherein the first message carries first information, and the first information is used for indicating at least one of the following: whether to receive a first user plane connection establishment request message sent by the terminal, a reason for requesting modification of a user plane connection between the terminal and the first network element, and a reason for requesting release of the user plane connection between the terminal and the first network element; and the first user plane connection establishment request message is used for requesting establishment of the user plane connection between the terminal and the first network element.

Description

Transmission method, device, terminal and network side equipment

[0001] CROSS-REFERENCE TO RELATED APPLICATIONS

[0002] This application claims priority to the Chinese patent application filed with the China Patent Office on November 3, 2023, with application number 202311465554.4 and invention name “Transmission method, device, terminal and network side equipment”, the entire contents of which are incorporated by reference into this application. Technical Field

[0003] The present application belongs to the field of communication technology, and specifically relates to a transmission method, apparatus, terminal and network-side equipment. Background Art

[0004] Currently, some mobile communication systems support the use of the user plane to transmit data service-related messages (e.g., positioning services, perception services, computing services, etc.) between terminals and the network. For example, positioning messages can be transmitted between the terminal and the Location Management Function (LMF) using the user plane. However, the related art lacks a corresponding solution for managing user plane operations for data services between the terminal and the network (e.g., establishing, modifying, or releasing user plane connections), which can easily affect the effectiveness of using the user plane to transmit data service-related messages between the terminal and the network.

[0005] Summary of the Invention

[0006] The embodiments of the present application provide a transmission method, apparatus, terminal and network-side equipment, which can provide a method for managing user plane operations for data services between the terminal and the network side, which is conducive to the terminal and the network side to use the user plane more efficiently to transmit data service-related messages.

[0007] In a first aspect, a transmission method is provided, the method comprising:

[0008] The terminal receives a first message sent by the first network element;

[0009] Among them, the first message carries first information, and the first information is used to indicate at least one of the following: whether to accept the first user plane connection establishment request message sent by the terminal, the reason for requesting to modify the user plane connection between the terminal and the first network element, and the reason for requesting to release the user plane connection between the terminal and the first network element; the first user plane connection establishment request message is used to request to establish a user plane connection between the terminal and the first network element.

[0010] In a second aspect, a transmission device is provided, the device comprising:

[0011] A first receiving module, configured to receive a first message sent by a first network element;

[0012] Among them, the first message carries first information, and the first information is used to indicate at least one of the following: whether to accept the first user plane connection establishment request message sent by the terminal, the reason for requesting to modify the user plane connection between the terminal and the first network element, and the reason for requesting to release the user plane connection between the terminal and the first network element; the first user plane connection establishment request message is used to request to establish a user plane connection between the terminal and the first network element.

[0013] In a third aspect, a transmission method is provided, the method comprising:

[0014] The first network element sends a first message to the terminal;

[0015] Among them, the first message carries first information, and the first information is used to indicate at least one of the following: whether to accept the first user plane connection establishment request message sent by the terminal, the reason for requesting to modify the user plane connection between the terminal and the first network element, and the reason for requesting to release the user plane connection between the terminal and the first network element; the first user plane connection establishment request message is used to request to establish a user plane connection between the terminal and the first network element.

[0016] In a fourth aspect, a transmission device is provided, the device comprising:

[0017] A first sending module, configured to send a first message to a terminal;

[0018] Among them, the first message carries first information, and the first information is used to indicate at least one of the following: whether to accept the first user plane connection establishment request message sent by the terminal, the reason for requesting to modify the user plane connection between the terminal and the first network element, and the reason for requesting to release the user plane connection between the terminal and the first network element; the first user plane connection establishment request message is used to request to establish a user plane connection between the terminal and the first network element.

[0019] In a fifth aspect, a terminal is provided, comprising a processor and a memory, wherein the memory stores a program or instruction that can be run on the processor, and when the program or instruction is executed by the processor, the steps of the method described in the first aspect are implemented.

[0020] In the sixth aspect, a terminal is provided, comprising a processor and a communication interface, wherein the communication interface is used to receive a first message sent by a first network element; wherein the first message carries first information, and the first information is used to indicate at least one of the following: whether to accept the first user plane connection establishment request message sent by the terminal, the reason for requesting to modify the user plane connection between the terminal and the first network element, and the reason for requesting to release the user plane connection between the terminal and the first network element; the first user plane connection establishment request message is used to request to establish a user plane connection between the terminal and the first network element.

[0021] In the seventh aspect, a network side device is provided, which includes a processor and a memory, wherein the memory stores programs or instructions that can be run on the processor, and when the program or instructions are executed by the processor, the steps of the method described in the third aspect are implemented.

[0022] In the eighth aspect, a network side device is provided, including a processor and a communication interface, wherein the communication interface is used to send a first message to a terminal; wherein the first message carries first information, and the first information is used to indicate at least one of the following: whether to accept the first user plane connection establishment request message sent by the terminal, the reason for requesting to modify the user plane connection between the terminal and the first network element, and the reason for requesting to release the user plane connection between the terminal and the first network element; the first user plane connection establishment request message is used to request to establish a user plane connection between the terminal and the first network element.

[0023] In the ninth aspect, a transmission system is provided, comprising: a terminal and a network side device, wherein the terminal can be used to execute the steps of the transmission method described in the first aspect, and the network side device can be used to execute the steps of the transmission method described in the third aspect.

[0024] In the tenth aspect, a readable storage medium is provided, on which a program or instruction is stored. When the program or instruction is executed by a processor, the steps of the method described in the first aspect are implemented, or the steps of the method described in the third aspect are implemented.

[0025] In the eleventh aspect, a chip is provided, which includes 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 of the method described in the first aspect, or to implement the steps of the method described in the third aspect.

[0026] In the twelfth 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 described in the first aspect, or to implement the steps of the method described in the third aspect.

[0027] In an embodiment of the present application, a terminal receives a first message sent by a first network element; wherein the first message carries first information, and the first information is used to indicate at least one of the following: whether to accept the first user plane connection establishment request message sent by the terminal, the reason for requesting to modify the user plane connection between the terminal and the first network element, and the reason for requesting to release the user plane connection between the terminal and the first network element; the first user plane connection establishment request message is used to request to establish a user plane connection between the terminal and the first network element, and then the terminal can perform corresponding actions according to the first information, which is conducive to the terminal and the network side to use the user plane more efficiently to transmit data service-related messages. BRIEF DESCRIPTION OF THE DRAWINGS

[0028] FIG1 is a block diagram of a wireless communication system to which embodiments of the present application may be applied;

[0029] FIG2a is a flowchart of positioning based on a user plane connection between a UE and an LMF initiated by an LMF according to an embodiment of the present application;

[0030] FIG2b is a flowchart of a positioning method based on a user plane connection between a UE and an LMF initiated by a UE, provided in an embodiment of the present application;

[0031] FIG2c is a flowchart of modifying a user plane connection between a UE and an LMF provided in an embodiment of the present application;

[0032] FIG3 is a flow chart of a transmission method provided in an embodiment of the present application;

[0033] FIG4a is a flowchart of establishing a user plane connection between a UE and an LMF according to an embodiment of the present application;

[0034] FIG4b is a flowchart of a user plane connection modification between a UE and an LMF provided in an embodiment of the present application;

[0035] FIG4c is a flowchart of releasing a user plane connection between a UE and an LMF provided in an embodiment of the present application;

[0036] FIG5 is a flow chart of another transmission method provided in an embodiment of the present application;

[0037] FIG6 is a structural diagram of a transmission device provided in an embodiment of the present application;

[0038] FIG7 is a structural diagram of another transmission device provided in an embodiment of the present application;

[0039] FIG8 is a structural diagram of a communication device provided in an embodiment of the present application;

[0040] FIG9 is a structural diagram of a terminal provided in an embodiment of the present application;

[0041] FIG10 is a structural diagram of a network-side device provided in an embodiment of the present application. DETAILED DESCRIPTION

[0042] The following will be combined with the accompanying drawings in the embodiments of this application to clearly describe the technical solutions in the embodiments of this application. Obviously, the embodiments described are part of the embodiments of this application, not all of the embodiments. Based on the embodiments in this application, all other embodiments obtained by ordinary technicians in this field are within the scope of protection of this application.

[0043] The terms "first", "second", etc. in this application are used to distinguish similar objects, and are not used to describe a specific order or sequence. It should be understood that the terms used in this way are interchangeable where appropriate, so that the embodiments of the present application can be implemented in an order other than those illustrated or described herein, and the objects distinguished by "first" and "second" are generally of the same type, and do not limit the number of objects, for example, the first object can be one or more. In addition, "or" in this application represents at least one of the connected objects. For example, "A or B" covers three options, namely, Option 1: including A but not including B; Option 2: including B but not including A; Option 3: including both A and B. The character " / " generally indicates that the objects associated before and after are in an "or" relationship.

[0044] The term "indication" in this application can be either a direct indication (or explicit indication) or an indirect indication (or implicit indication). A direct indication can be understood as the sender explicitly informing the receiver of specific information, the operation to be performed, or the requested result, etc. in the instruction sent; an indirect indication can be understood as the receiver determining the corresponding information based on the instruction sent by the sender, or making a judgment and determining the operation to be performed or the requested result, etc. based on the judgment result.

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

[0046] FIG1 is a block diagram of a wireless communication system applicable to an embodiment of the present application. The wireless communication system includes a terminal 11 and a network-side device 12. The terminal 11 may be a mobile phone, a tablet computer (Tablet Personal Computer), a laptop computer (Laptop Computer), a notebook computer, a personal digital assistant (PDA), a handheld computer, a netbook, an ultra-mobile personal computer (UMPC), a mobile internet device (MID), an augmented reality (AR), a virtual reality (VR) device, a robot, a wearable device (Wearable Device), an aircraft (Flight Vehicle), a vehicle-mounted device (VUE), a ship-mounted device, a pedestrian user equipment (PUE), a smart home (home appliances with wireless communication capabilities, such as refrigerators, televisions, washing machines, or furniture), a game console, a personal computer (PC), an ATM, or a self-service machine, or other terminal-side devices. Wearable devices include: smart watches, smart bracelets, smart headphones, smart glasses, smart jewelry (smart bracelets, smart bracelets, smart rings, smart necklaces, smart anklets, smart anklets, etc.), smart wristbands, smart clothing, etc. Among them, the vehicle-mounted device can also be called a vehicle-mounted terminal, a vehicle-mounted controller, a vehicle-mounted module, a vehicle-mounted component, a vehicle-mounted chip or a vehicle-mounted unit, etc. It should be noted that the specific type of the terminal 11 is not limited in the embodiment of the present application. The network side device 12 may include an access network device or a core network device, wherein the access network device may also be called a radio access network (Radio Access Network, RAN) device, a radio access network function or a radio access network unit. The access network device may include a base station, a wireless local area network (WLAN) access point (AP) or a wireless fidelity (WiFi) node, etc.Among them, the base station can be referred to as Node B (NB), Evolved Node B (eNB), the 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 (home evolved Node B), Transmission Reception Point (TRP) or other appropriate terms in the field. As long as the same technical effect is achieved, the base station is not limited to specific technical vocabulary. It should be noted that in the embodiment of the present application, only the base station in the NR system is used as an example for introduction, and the specific type of the base station is not limited.

[0047] The core network equipment may include but is not limited to at least one of the following: core network node, core network function, mobility management entity (MME), access mobility management function (AMF), session management function (SMF), user plane function (UPF), policy control function (PCF), policy and charging rules function unit (PCRF), edge application service discovery function (EASDF), unified data management (UDM), unified data repository (UDR), home subscriber server (HSS), centralized network configuration (CNC), network storage function (NRF), network exposure function (NEF), local NEF (L-NEF), binding support function (BSF), application function ( It should be noted that in the embodiments of the present application, only the core network device in the NR system is introduced as an example, and the specific type of the core network device is not limited.

[0048] For ease of understanding, some of the contents involved in the embodiments of this application are described below:

[0049] The eighteenth version (Release 18, R18) supports the use of the user plane to transmit positioning messages (including LTE Positioning Protocol (LPP) messages and Location Service Supplementary Service (LCS-SS) messages) between the UE and the network side (including LMF and Location Services (LCS) client) / AF). The following shows the process related to location services, including UE-triggered user plane establishment, network-triggered user plane establishment, network-triggered user plane modification, and network-triggered user plane release.

[0050] 1. LMF initiates or triggers user plane connection

[0051] Exemplarily, referring to FIG2a , the LMF initiating or triggering the user plane connection process may include the following steps:

[0052] Step 11. The LMF decides whether to use the positioning procedure via the user plane connection between the UE and the LMF based on the UE user plane positioning capability, the control plane congestion status (such as the AMF load status) and other execution factors.

[0053] LMF can call Nnrf_NFDiscovery service operation to obtain control plane congestion status (such as AMF load information). If there is an available user plane connection between UE and LMF, LMF can determine to use user plane positioning based on AMF load information.

[0054] If the user plane connection context between the target UE and the LMF already exists in the LMF, and the LMF determines to use the user plane connection for positioning, steps 12 to 17 are skipped.

[0055] NOTE: The LMF may select user plane positioning for a specific positioning method (e.g. motion sensor based method). The specific positioning method that requires user plane transmission depends on the implementation and local configuration.

[0056] Step 12. [Conditionally] If the LMF decides to use the user plane for positioning and no secure user plane connection is established between the terminal and the LMF, the LMF invokes the Namf_communication_N1N2Transfer service operation, places the user plane information in a non-access stratum (NAS) container and sends it to the AMF, instructing the terminal to use the user plane for positioning over TLS. The user plane information includes the user plane positioning address of the LMF and security-related information.

[0057] Step 13. [Conditionally] When the AMF receives the user plane information from the LMF in step 12, the AMF sends it to the UE through a DL NAS TRANSPORT message.

[0058] Step 14. [Conditionally] If an applicable Protocol Data Unit (PDU) session has not been established for user plane positioning, the terminal uses the User Equipment Route Selection Policy (URSP) defined by the relevant protocol (including PDU session parameters related to user plane positioning, such as the dedicated data network name (DNN) and single network slice selection assistance information (S-NSSAI)) to establish a PDU session for user plane positioning. The UE may send an acknowledgment to the LMF via the AMF, indicating that the user plane connection was successfully used for positioning services, or that the use of the user plane connection failed, for example, no appropriate PDU session was established.

[0059] Step 15. [Conditionally] AMF sends the confirmation message received in step 14 to LMF via Namf_N1messageNotify service.

[0060] Step 16. [Conditionally] If the LMF knows the UE's IP address information, the LMF may notify the UE to establish a secure user plane connection through the known IP address.

[0061] Step 17. [Conditionally] The UE establishes a secure user plane connection with the LMF. If the LMF sends the Fully Qualified Domain Name (FQDN) to the UE, the LMF's IP address is resolved using a Domain Name System (DNS) server / resolver (e.g., Edge Application Server Discovery Function (EASDF) or local DNS for local LMF address resolution).

[0062] Step 18. [Conditionally] The LMF indicates to the AMF in the Nlmf_Location_UPNotify message that the user plane connection between the UE and the LMF has been established.

[0063] Step 19. [Conditionally] The AMF stores the LCS User Plane (LCS-UP) connection context as part of the UE context.

[0064] Step 110. If the LMF or UE decides to utilize a user plane connection for positioning and a secure user plane connection is established, LPP messages are transmitted between the UE and LMF for UE-based positioning, UE-assisted positioning, and transmission of assistance data. Supplementary service event report messages from the UE may also be transmitted to the LMF over the established user plane connection.

[0065] UE initiated User Plane Connection

[0066] If the UE does not have a user plane connection with the LMF, the UE may trigger the establishment of a user plane connection. For example, FIG2b shows a user plane connection process initiated or triggered by the UE between the UE and the LMF, which specifically includes the following steps:

[0067] Step 21. If the UE decides to request a user plane connection for the upcoming positioning request, it sends a user plane establishment request to the AMF via a NAS message.

[0068] Step 22. [Conditionally] If the UE is authorized to use user plane positioning via UE subscription, the AMF shall select a LMF that can establish a user plane positioning session with the UE. The AMF may query the NRF or discover and select a suitable LMF based on local configuration.

[0069] Step 23. [Conditionally] AMF sends Nlmf_Location_UPConfig request (Request) to LMF to request to establish LCS-UP connection.

[0070] Step 24. [Conditionally] If the LMF accepts the use of the user plane for positioning and no secure user plane connection is established between the UE and the LMF, the LMF sends user plane information to the AMF, instructing the UE to accept and use the user plane for positioning. The user plane information includes the user plane positioning address of the LMF and security-related information.

[0071] Step 25. [Conditionally] When the AMF receives the user plane information from the LMF in step 24, the AMF forwards it to the UE via a DL NAS transport (TRANSPORT) message.

[0072] Step 26. [Conditionally] If a secure user plane connection is not established, the UE establishes a secure user plane connection with the LMF. The UE determines the PDU session parameters, including the DNN + S-NSSAI, based on the user plane location address of the LMF and information in the URSP. The UE uses the PDU session parameters to establish a PDU session. Upon receiving the request, the SMF selects an appropriate UPF based on the DNN + S-NSSAI and establishes a connection between the UPF and the LMF.

[0073] Step 27. [Conditionally] LMF responds to AMF that the user plane connection between UE and LMF has been established.

[0074] Step 28. [Conditionally] The AMF stores the LCS-UP connection context as part of the UE context.

[0075] Step 29. [Conditionally] After the secure user plane connection is established, if the LMF decides to use the user plane connection for positioning after receiving the positioning request from the AMF, or if the UE decides to use the user plane connection for positioning, LPP messages are transmitted between the UE and the LMF for UE-based positioning, UE-assisted positioning, and transmission of assistance data. Supplementary service event report messages from the UE may also be transmitted to the LMF over the established user plane connection.

[0076] 3. Modification of User Plane Connection between UE and LMF

[0077] For example, Figure 2c illustrates a process for modifying a secure user plane connection between a UE and an LMF. This process describes a change in the LMF, but is also applicable when the source and target LMFs are the same. This process can also be used to terminate the user plane connection with the source LMF without selecting any target LMF.

[0078] Step 31a. [Conditionally] The LMF discovers that a change in LMF is required, or that the user plane connection between the UE and the LMF needs to be re-established or terminated. The LMF sends an Nlmf_Location_UPNotify message, which includes a connection change (termination or establishment) or the need for termination. If a connection change is requested, the message may include the target LMF identifier. The address of the AMF is provided to the LMF as the "Notification Target Address" in the most recent Nlmf_Location_UPConfig message or Nlmf_Location_UP Subscribe message.

[0079] Note: The LMF change process is independent of the Session and Service Continuity Mode (SSC) mode of the PDU session, which has a dedicated DNN for positioning. For SSC Mode 2 / 3, the connection between the PDU Session Anchor (PSA) UPF and the LMF can be relocated as the UE moves, and the LMF can detect the need to change the LMF to reduce the user plane path delay.

[0080] Step 31b. [Conditionally] The AMF that performs user plane positioning based on the target LMF identity received from the source LMF, or when the UE moves to a new location (which may be outside the source LMF service area but within the target LMF service area), the AMF may perform LMF reselection and select the target LMF for the current UE location based on the LMF service area, the LMF user plane positioning capability information and other information listed in clause 5.1. The LMF needs to be able to establish a user plane session for positioning with the UE. In addition, when the AMF is relocated, the target AMF needs to notify the LMF of the change of AMF.

[0081] Step 32. [Conditionally] If the AMF has been reallocated, skip this step 3. Otherwise, perform steps 33-8 in Figure 2b between the AMF, UE and target LMF, and the UE will also terminate the connection with the source LMF.

[0082] Step 33. The AMF sends an Nlmf_Location_UPConfig request to the source LMF. This message may include a request from the source LMF to terminate a specific user plane connection to the UE and the target LMF identifier; or, the message may include information about AMF reallocation.

[0083] Steps 34 to 35. [Conditionally] The source LMF may call the Nlmf_Location_LocationContextTransfer request service operation to the target LMF to provide the UE's current location context, if there is a periodic and triggered UE location event reporting context. The target LMF notifies the source LMF of the location context transfer operation result.

[0084] Step 36. [Conditionally] If the user plane connection with the source LMF is still active, the source LMF terminates the connection with the UE.

[0085] Step 37.LMF sends Nlmf_Location_UPConfig Response message to AMF to confirm the connection termination or confirm the change of AMF. If the procedure is for termination, AMF will release the LCS-UP context after receiving the response message.

[0086] The transmission method provided by the embodiment of the present application is described in detail below with reference to some embodiments and their application scenarios in conjunction with the accompanying drawings. In addition, for ease of understanding, the embodiment of the present application is described by taking the data service as a positioning service as an example.

[0087] Please refer to FIG3 , which is a flowchart of a transmission method provided in an embodiment of the present application. The method can be executed by a terminal, as shown in FIG3 , and includes the following steps:

[0088] Step 301: A terminal receives a first message sent by a first network element;

[0089] Among them, the first message carries first information, and the first information is used to indicate at least one of the following: whether to accept the first user plane connection establishment request message sent by the terminal, the reason for requesting to modify the user plane connection between the terminal and the first network element, and the reason for requesting to release the user plane connection between the terminal and the first network element; the first user plane connection establishment request message is used to request to establish a user plane connection between the terminal and the first network element.

[0090] In this embodiment, the first network element may include but is not limited to LMF, AF or network data analysis function (Network Data Analytics Function, NWDAF) and the like.

[0091] The first information is used to indicate whether to accept the first user plane connection establishment request message sent by the terminal. It can be understood that the first information is used to indicate whether the first network element accepts the first user plane connection establishment request message sent by the terminal. For example, the first information indicates that the first network element accepts the first user plane connection establishment request message sent by the terminal, that is, agrees to establish the user plane connection, or the first information indicates that the first network element rejects the first user plane connection establishment request message sent by the terminal, that is, does not agree to establish the user plane connection. It should be noted that the first information can explicitly indicate whether to accept the first user plane connection establishment request message sent by the terminal. For example, the first information includes a first message type, and the first message type is used to indicate whether to reject or accept the user plane connection establishment request; or the first information can implicitly indicate whether to accept the first user plane connection establishment request message sent by the terminal. For example, if the first information includes a cause value or a backoff time, it indicates that the user plane connection establishment request is rejected. If the first information does not include a cause value or a backoff time, it indicates that the user plane connection establishment request is accepted.

[0092] The reasons for requesting to modify the user plane connection between the terminal and the first network element may include but are not limited to network element congestion, exceeding the network element service range, insufficient resources or protocol switching.

[0093] The reasons for requesting to release the user plane connection between the terminal and the first network element may include but are not limited to regular release, protocol switching, insufficient resources or network element restart.

[0094] The following examples illustrate the embodiments of the present application:

[0095] Case 1: The first information is used to indicate whether to accept the first user plane connection establishment request message sent by the terminal.

[0096] The UE triggers or the network triggers the establishment of a user plane connection, and the UE sends a first user plane connection establishment request message to the first network element, where the first user plane connection establishment request message is used to request the establishment of a user plane connection between the UE and the first network element for data transmission. Exemplarily, the first user plane connection establishment request message may carry a message type, where the message type is used to indicate that the message is a user plane connection establishment request message.

[0097] Upon receiving the first user plane connection establishment request message, the first network element may send a user plane connection establishment response message to the terminal, the message carrying first information indicating whether to accept the first user plane connection establishment request message sent by the terminal. Upon receiving the user plane connection establishment response message, the terminal may perform corresponding operations according to the first information. For example, if the first information indicates rejection of the user plane connection establishment request, the terminal may send the user plane connection establishment request message to the first network element again after waiting for a preset time, or may perform corresponding operations according to the reason why the first network element rejects the user plane connection establishment request. For example, if the rejection reason is protocol mismatch, the UE may re-initiate the terminal-initiated user plane connection process (see the aforementioned UE-triggered user plane connection process) after waiting for a preset time, and request the network side to select a network element that supports the protocol used by the terminal to establish a user plane connection. The preset time may be implemented locally by the UE or indicated to the UE by the network side in the first message. If the first information indicates acceptance of the user plane connection establishment request, the terminal may establish a user plane connection with the first network element.

[0098] Case 2: The first information is used to indicate the reason for requesting to modify the user plane connection between the terminal and the first network element.

[0099] When a network side (e.g., a first network element or a second network element) determines that a first network element handover is required, the first network element sends a user plane connection modification request message to a terminal, requesting the terminal to switch the user plane connection to a target network element. The message carries first information indicating a reason for requesting to modify the user plane connection between the terminal and the first network element. Upon receiving the first message, the terminal may perform corresponding operations based on the first information. For example, if the first information indicates that the reason for requesting to modify the user plane connection is congestion in the first network element, the terminal may maintain the user plane connection with the first network element and wait for a preset time before sending a user plane location message. The preset time may be implemented locally by the UE or indicated to the UE by the network side in the first message. If the first information indicates that the reason for requesting to modify the user plane connection is insufficient resources, the terminal may maintain the user plane connection with the first network element and wait for a preset time before sending a user plane location message. The preset time may be implemented locally by the UE or indicated to the UE by the network side in the first message. If the first information indicates that the reason for requesting to modify the user plane connection is out of the service area of ​​the first network element or protocol handover, the terminal may initiate a new user plane connection establishment request message to the target network element. Exemplarily, the above-mentioned second network element can be AMF.

[0100] Case 3: The first information is used to indicate the reason for requesting to release the user plane connection between the terminal and the first network element.

[0101] When the network side (for example, the first network element or the second network element, etc.) determines that it is necessary to release the user plane connection between the first network element and the terminal, the first network element sends a user plane connection release request message to the terminal, requesting to release the user plane connection between the current terminal and the first network element. The message carries first information indicating the reason for requesting to release the user plane connection between the terminal and the first network element. When the terminal receives the first message, it can perform corresponding operations according to the first information. For example, if the above-mentioned first information indicates that the reason for requesting to release the user plane connection is a regular release, the terminal can refuse to release the user plane connection with the first network element; if the above-mentioned first information indicates that the reason for requesting to release the user plane connection is a protocol switch or a restart of the first network element, etc., the terminal can release the user plane connection with the first network element, and after releasing the user plane connection, use the target protocol to establish a user plane connection and communicate with the first network element. The target protocol can be selected locally by the UE or indicated to the UE by the first network element in the first message; if the above-mentioned first information indicates that the reason for requesting to release the user plane connection is insufficient resources, the terminal can release the user plane connection with the first network element and initiate the user plane positioning connection request process after waiting for a preset time. The preset time can be implemented locally by the UE or indicated to the UE by the network in the first message. Exemplarily, the above-mentioned second network element can be an AMF.

[0102] The transmission method provided by an embodiment of the present application is that a terminal receives a first message sent by a first network element; wherein the first message carries first information, and the first information is used to indicate at least one of the following: whether to accept the first user plane connection establishment request message sent by the terminal, the reason for requesting to modify the user plane connection between the terminal and the first network element, and the reason for requesting to release the user plane connection between the terminal and the first network element; the first user plane connection establishment request message is used to request to establish a user plane connection between the terminal and the first network element, and then the terminal can perform corresponding actions according to the first information, which is conducive to the terminal and the network side to use the user plane more efficiently to transmit data service-related messages.

[0103] Optionally, when the first information is used to indicate whether to accept the first user plane connection establishment request message sent by the terminal, the first information includes at least one of the following: a first message type, a first cause value, and a backoff time; wherein, the first message type is used to indicate rejection or acceptance of the user plane connection establishment request, and the first cause value is used to indicate congestion of the first network element or protocol mismatch.

[0104] In this embodiment, the first cause value is used to indicate the reason for rejecting or not accepting the first user plane connection establishment request message sent by the terminal, wherein the reason for rejecting or not accepting the first user plane connection establishment request message sent by the terminal may include congestion of the first network element or protocol mismatch. For protocol mismatch, for example, the terminal uses the LCS user plane positioning (LCS User Plane Positioning, LCS-UPP) protocol, while the first network element only supports the secure user plane location (Secure User Plane Location, SUPL) protocol. The back-off time (Back-off Time) is used to indicate the time the terminal needs to wait for sending the user plane connection establishment request again.

[0105] In this embodiment, the first information includes at least one of the first message type, the first cause value, and the backoff time, which helps the terminal to perform corresponding user plane operations more accurately.

[0106] Optionally, the method further includes:

[0107] In a case where the first information includes the backoff time, the terminal starts a timer and sends a second user plane connection establishment request message to the first network element after the timer expires; wherein an initial value of the timer is the backoff time;

[0108] or,

[0109] When the first cause value indicates that the protocol does not match, the terminal sends a third user plane connection establishment request message to the second network element; wherein the third user plane connection establishment request message includes at least one of the following: first indication information, the protocol used by the terminal; the first indication information is used to instruct the second network element to select a third network element that supports the protocol used by the terminal.

[0110] In one embodiment, when the first information includes the backoff time, the terminal can wait for the backoff time and then send a user plane connection establishment request message (i.e., the second user plane connection establishment request message) to the first network element again. For example, the terminal can start a timer at the first moment or after the first moment, and send a second user plane connection establishment request message to the first network element after the timer expires; wherein, the first moment is the moment when the terminal obtains the backoff time, which is conducive to quickly establishing a user plane connection between the terminal and the first network element.

[0111] In some optional embodiments, the terminal may send the second user plane connection establishment request message to the first network element via the user plane. Taking the first network element as the LMF as an example, the terminal may send the second user plane connection establishment request message to the LMF via the RAN and UPF in sequence.

[0112] In some optional embodiments, when the first information includes the first cause value and the backoff time, and the first cause value indicates that the first network element is congested, the terminal starts a timer and sends a second user plane connection establishment request message to the first network element after the timer expires.

[0113] In another embodiment, when the first cause value indicates that the protocol does not match, the terminal sends a third user plane connection establishment request message to the second network element, wherein the type of the second network element is different from the type of the first network element, for example, the first network element is an LMF and the second network element is an AMF. The first indication information is used to instruct the second network element to select a third network element that supports the protocol used by the terminal, wherein the type of the third network element is the same as the type of the first network element, for example, the first network element and the third network element are different LMFs. The protocol used by the terminal, for example, if the protocol used by the terminal is the LCS-UPP protocol, then the third user plane connection establishment request message carries the LCS-UPP protocol.

[0114] It can be understood that when the second network element receives the third user plane connection establishment request message, it can select a third network element that supports the protocol used by the terminal. For example, if the protocol used by the terminal is the LCS-UPP protocol, the AMF can select the LMF that supports the LCS-UPP protocol for the terminal.

[0115] In this embodiment, when the first network element does not support the protocol used by the terminal, the terminal can quickly request the second network element to select a network element that supports the protocol used by the terminal, which is conducive to the terminal quickly establishing a user plane connection with the network element that supports the protocol used by the terminal.

[0116] In another embodiment, when the first information includes a backoff time and a first cause value, and the first cause value is a protocol mismatch, the terminal starts a timer and sends a second user plane connection establishment request message to the first network element after the timer expires, or the terminal starts a timer and sends a third user plane connection establishment request message to the second network element after the timer expires, wherein the third user plane connection establishment request message includes at least one of the following: first indication information, the protocol used by the terminal; the first indication information is used to instruct the second network element to select a third network element that supports the protocol used by the terminal.

[0117] Optionally, the first user plane connection establishment request message is a user plane connection establishment request message sent by the terminal to the first network element through the user plane.

[0118] In this embodiment, the terminal sends a user plane connection establishment request message to the first network element through the user plane to request establishment of a user plane connection between the terminal and the first network element.

[0119] The following describes the user plane connection establishment process using the data service as the positioning service and the first network element as the LMF as an example:

[0120] As shown in Figure 4a, the user plane connection establishment process between the UE and the LMF may include the following steps:

[0121] Step 50, UE triggers or network triggers the process of establishing a user plane connection. For details, please refer to steps 11 to 16 in the aforementioned LMF triggered user plane connection process or steps 21 to 25 in the aforementioned UE triggered user plane connection process.

[0122] It should be noted that the above step 50 uses control plane signaling, and all messages are transmitted through the control plane and do not involve the UPF.

[0123] Step 51. The UE sends a user plane connection establishment request message to the LMF. The message has a request to establish a user plane connection between the UE and the LMF to transmit the user plane positioning message. The message may carry: a message type (Message type), used to indicate that the message is a user plane connection establishment request message; and an expected connection duration, used to indicate the duration that the UE expects to use the user plane connection. The expected connection duration can be expressed as a time period, such as from 0:00 on October 1 to 20:00 on October 1, or can be expressed as a time size, such as 5 hours.

[0124] It should be noted that the above user plane connection establishment request message is sent through the user plane, that is, the user plane channel from UE to RAN to UPF to LMF.

[0125] Step 52: The LMF sends a user plane connection establishment response message to the UE, indicating the result of the UE's request to establish a user plane connection. The message carries at least one of the following: message type, cause value, and backoff time. The message type includes either accept or reject the request, and the cause value includes either LMF congestion or protocol mismatch.

[0126] Step 53: After receiving the user plane connection establishment response message, the UE performs corresponding actions.

[0127] One implementation method is: when the message type indicates a rejection of the request, the cause value indicates LMF congestion, and carries a backoff time, the UE starts a timer after receiving the cause value and the backoff time. The initial value of the timer is the backoff time. After the timer times out, the user plane connection establishment request message is sent to the LMF again.

[0128] Another implementation method is: when the message type indicates a rejection of the request and the cause value indicates a protocol mismatch, the UE executes step 21 of the aforementioned UE-triggered user plane connection process after receiving the cause value, and the message sent carries indication information, which is used to request the AMF to perform LMF selection and select the LMF that supports the UE to use the protocol stack.

[0129] Optionally, when the first information is used to indicate the reason for requesting to modify the user plane connection between the terminal and the first network element, the first information includes a second reason value, wherein the second reason value is used to indicate at least one of the following: congestion of the first network element, the terminal moving out of the service area of ​​the first network element, insufficient resources, and protocol switching.

[0130] In this embodiment, the above-mentioned second reason value is used to indicate the reason for requesting to modify the user plane connection between the terminal and the first network element, wherein the reason for requesting to modify the user plane connection between the terminal and the first network element may include at least one of the following: the first network element is congested, the terminal moves out of the service area of ​​the first network element, insufficient resources, and protocol switching.

[0131] Exemplarily, the above-mentioned protocol switching may be that the first network element determines that the currently used protocol stack needs to be switched to transmit data service related messages, for example, the LMF determines that the currently used protocol stack needs to be switched to transmit positioning messages.

[0132] It can be understood that when the terminal obtains the above-mentioned second cause value, it can perform corresponding actions based on the second cause value. For example, when the above-mentioned second cause value indicates protocol switching or the terminal moves out of the service area of ​​the first network element, the terminal can initiate a terminal-triggered user plane connection process to the network side to request a new network element address (for example, LMF address) to establish a new user plane connection; when the above-mentioned second cause value indicates that the first network element is congested, the terminal can send a user plane connection establishment request to the target network element or can reject the first network element's request to modify the user plane connection between the terminal and the first network element; when the above-mentioned second cause value indicates insufficient resources, the terminal can suspend sending user plane messages (for example, positioning messages), and send user plane messages (for example, positioning messages) after waiting for a preset time, or the terminal can release the current user plane connection and initiate a terminal-triggered user plane connection process to the network side to request a new network element address (for example, LMF address) to establish a new user plane connection.

[0133] Optionally, the first information further includes at least one of the following: a second message type, a target network element address; wherein the second message type is used to indicate that the first message is used to request modification of a user plane connection.

[0134] In this embodiment, the type of the target network element is the same as that of the first network element. For example, the target network element and the first network element are different LMFs. It is understandable that when the first information includes the address of the target network element, the terminal can initiate a user plane connection establishment request message to the target network element according to the address of the target network element.

[0135] In some optional embodiments, when the second cause value is used to indicate protocol switching, the first information also includes a target protocol.

[0136] An optional implementation manner is that the first information carries a target protocol information element (Target Protocol Information Element), where the target protocol information element includes a first bit, where the first bit indicates whether the terminal is required to switch to protocol A (such as SUPL protocol). When the value of the first bit is 0, the terminal is not required to use protocol A for transmission of user plane messages, such as positioning messages; when the value of the first bit is 1, the terminal is required to use protocol A for transmission of user plane messages, such as positioning messages.

[0137] Optionally, the first message is a message sent by the first network element to the terminal through a user plane, or the first message is a message sent by the first network element to the terminal through a control plane.

[0138] In one embodiment, the first network element may send a first message to the terminal through a user face. For example, the first network element sends a user plane connection modification request message (i.e., the above-mentioned first message) to the terminal through a user face. The message carries at least one of a message type (i.e., the above-mentioned second message type), a target network element address, and a modification cause value (i.e., the above-mentioned second cause value).

[0139] In another embodiment, the first network element can send a first message to the terminal through the control plane. For example, taking the first network element as LMF as an example, the AMF sends an Nlmf_Location_UPConfig Request message to the LMF to request to establish an LCS-UP connection. If the LMF accepts the use of the user plane for positioning and a secure user plane connection is not established between the UE and the LMF, the LMF sends a Namf_Communication_N1N2MessageTransfer message to the AMF, which carries user plane information and a modification reason value (i.e., the above-mentioned second reason value). When the AMF receives the user plane information and the modification reason value from the LMF, the AMF forwards it to the UE via a DL NAS TRANSPORT message.

[0140] Optionally, the method further includes:

[0141] The terminal sends a second message to the first network element, where the second message is used to indicate acceptance or rejection of the user plane connection modification request.

[0142] Exemplarily, the second message is used to indicate acceptance or rejection of the user plane connection modification request, which can be understood as the second message is used to indicate acceptance or rejection of the user plane connection modification request message sent by the first network element.

[0143] In some examples, the second message may carry a third message type, where the third message type is used to indicate acceptance or rejection of the user plane connection modification request.

[0144] Specifically, the terminal can determine whether to accept the user plane connection modification request based on the first information. If it is determined that the user plane connection modification request is accepted, the terminal sends a message to the first network element to indicate the acceptance of the user plane connection modification request. If it is determined that the user plane connection modification request is rejected, the terminal sends a message to the first network element to indicate the rejection of the user plane connection modification request.

[0145] The following describes the user plane connection modification process using the data service as the positioning service and the first network element as the LMF as an example:

[0146] As shown in Figure 4b, the user plane connection modification process between the UE and the LMF may include the following steps:

[0147] Step 60: LMF or AMF triggers the handover of LMF. For example, because the UE moves out of the service area of ​​​​the LMF, or the LMF load is too large, the LMF needs to be switched. For details, please refer to steps 31a and 31b of the user plane connection modification process between the UE and LMF.

[0148] For LMF to send the modification cause value (mod cause or mod cause) to UE, there are two methods: method 1, using a control plane message (ie, LMF->AMF->UE) to send it to UE; method 2, using a user plane message (ie, LMF->UPF->RAN->UE) to send it to UE.

[0149] The above-mentioned method 1 can refer to steps 23 to 25 of the aforementioned UE-initiated user plane connection process. The enhanced portion is that step 22, in addition to carrying user plane information, also carries a modification reason value. The modification reason value includes LMF congestion, UE moving out of the LMF service area, insufficient resources, or protocol switching. The above-mentioned user plane information is used to provide user plane connection-related information, including the LMF address. Specifically, the above-mentioned method 1 may include the following steps:

[0150] Step 61a: AMF sends Nlmf_Location_UPConfig Request to LMF to request establishment of LCS-UP connection. When AMF receives user plane information and modification cause value from LMF, AMF forwards it to UE through DL NAS TRANSPORT message.

[0151] Step 62a. If the LMF accepts the use of the user plane for positioning and no secure user plane connection is established between the UE and the LMF, the LMF sends a Namf_Communication_N1N2MessageTransfer message to the AMF, which carries the user plane information and the modification cause value (i.e., the second cause value mentioned above).

[0152] Step 63a: When the AMF receives the user plane information and the modification cause value from the LMF, the AMF forwards it to the UE via a DL NAS TRANSPORT message.

[0153] Step 64a: The UE sends a user plane connection modification response message, which may carry a message type to indicate rejection or acceptance of the above-mentioned user plane connection release request. The message is encapsulated in a UL NAS TRANSPORT message and sent to the AMF.

[0154] Step 65a: When the AMF receives the UL NAS TRANSPORT message from the UE, the AMF finds the LMF according to the UE LCS-UP context and forwards the user plane connection modification response message carried in the UL NAS TRANSPORT message to the UE.

[0155] The above-mentioned method 2 may include the following steps:

[0156] Step 61b: The LMF sends a User Plane Connection Modification Request message to the UE, requesting the UE to switch the user plane connection to the target LMF. The message carries at least one of the following: message type, target LMF address, and modification cause value. Modification cause values ​​include LMF congestion, UE moving out of the LMF service area, or protocol handover.

[0157] Step 62b: The UE sends a reply message to the LMF. The message carries a message type, which is used to indicate whether to accept or reject the user plane connection modification request message sent by the first network element.

[0158] Step 64: After receiving the modification reason value, the UE initiates a new user plane connection establishment request message to the target LMF.

[0159] Optionally, when the first information is used to indicate the reason for requesting to release the user plane connection between the terminal and the first network element, the first information includes a third cause value, wherein the third cause value is used to indicate normal release, protocol switching, insufficient resources or restart of the first network element.

[0160] In this embodiment, the above-mentioned third reason value is used to indicate the reason for requesting to release the user plane connection between the terminal and the first network element, wherein the reason for requesting to release the user plane connection between the terminal and the first network element may include normal release, protocol switching, insufficient resources or restart of the first network element.

[0161] Exemplarily, the above-mentioned regular release includes regular release situations such as normal release due to long-term non-use; the above-mentioned switching protocol may refer to the first network element determining that the currently used protocol stack needs to be switched to transmit data service-related messages, for example, LMF determines that the currently used protocol stack needs to be switched to transmit positioning messages; insufficient resources may refer to the first network element itself being too heavily loaded, requiring the terminal to wait for a period of time to send a user-plane positioning message or to find a replacement network element (for example, LMF) to provide services, for example, the LMF computing task load is too heavy; the first network element restart may refer to the first network element itself requiring a machine upgrade and being unable to support the current user-plane connection task, for example, LMF restart means that the LMF itself requires a machine upgrade and is unable to support the current user-plane connection task.

[0162] It can be understood that when the terminal obtains the above-mentioned third reason value, it can perform corresponding actions based on the third reason value. For example, when the above-mentioned third reason value indicates a regular release, the terminal can refuse to release the user plane connection between the terminal and the first network element; when the above-mentioned third reason value indicates a protocol switch, the terminal can release the current user plane connection and can use the target protocol to communicate with the first network element on the user plane; when the above-mentioned third reason value indicates insufficient resources, the terminal can release the current user plane connection and re-initiate the user plane connection process triggered by the terminal to request a new network element (for example, LMF) address to establish a new user plane connection to send a user plane message, for example, a positioning message; when the above-mentioned third reason value indicates a restart of the first network element, the terminal can release the current user plane connection and can choose to establish a user plane connection with other network elements.

[0163] Optionally, when the third cause value is used to indicate protocol switching, the first information also includes a target protocol.

[0164] An optional implementation manner is that the first information carries a target protocol information element, and the target protocol information element includes a first bit, where the first bit indicates whether the terminal is required to switch to protocol A (such as SUPL protocol). When the value of the first bit is 0, the terminal is not required to use protocol A for transmission of user plane messages, such as positioning messages; when the value of the first bit is 1, the terminal is required to use protocol A for transmission of user plane messages, such as positioning messages.

[0165] Optionally, the first message further includes a backoff time, where the backoff time is used to indicate that after releasing the current user plane connection, the terminal can wait for a set time before reusing the process of establishing a user plane connection.

[0166] Optionally, the method further includes:

[0167] The terminal sends a third message to the first network element, where the third message is used to indicate acceptance or rejection of the user plane connection release request.

[0168] Exemplarily, the third message is used to indicate acceptance or rejection of the user plane connection release request, which can be understood as the third message is used to indicate acceptance or rejection of the user plane connection release request message sent by the first network element.

[0169] In some examples, the third message may carry a fourth message type, where the fourth message type is used to indicate acceptance or rejection of the user plane connection release request.

[0170] Specifically, the terminal can determine whether to accept the user plane connection release request based on the first information. If it is determined that the user plane connection release request is received, the terminal sends a message to the first network element to indicate the acceptance of the user plane connection release request. If it is determined that the user plane connection release request is rejected, the terminal sends a message to the first network element to indicate the rejection of the user plane connection release request.

[0171] Optionally, the first message is a message sent by the first network element to the terminal through a user plane, or the first message is a message sent by the first network element to the terminal through a control plane.

[0172] In one embodiment, the first network element may send a first message to the terminal via the user plane. For example, the LMF may send a user plane connection release request message to the UE via the user plane (ie, LMF->UPF->RAN->UE), which carries the above-mentioned first information.

[0173] In another embodiment, the first network element can send a first message to the terminal through the control plane. For example, the LMF can send a user plane connection release request message to the UE through the control plane (i.e., LMF->AMF->UE), which carries the above-mentioned first information.

[0174] Optionally, the method further includes:

[0175] In a case where the third message is used to indicate acceptance of the user plane connection release request, the terminal releases the user plane connection between the terminal and the first network element.

[0176] In this embodiment, when the terminal determines to accept the user plane connection release request, the terminal can release the user plane connection between the terminal and the first network element, and then the terminal can choose to establish a user plane connection with other network elements when the first cause value indicates insufficient resources or the first network element is restarted, or use the target protocol to re-establish the user plane connection with the first network element when the third cause value indicates protocol switching.

[0177] Optionally, the method further includes:

[0178] In a case where the third cause value is used to indicate protocol switching, the terminal uses the target protocol to perform user plane communication with the first network element.

[0179] Exemplarily, when the third cause value is used to indicate protocol switching, the terminal can release the current user plane connection, that is, release the user plane connection between the current terminal and the first network element, and use the target protocol to re-establish the user plane connection with the first network element, and then use the target protocol to communicate with the first network element on the user plane.

[0180] Optionally, the method further includes:

[0181] In a case where the third cause value is used to indicate insufficient resources, the terminal sends a fourth user plane connection establishment request message to the second network element.

[0182] Exemplarily, the above-mentioned second network element can be AMF.

[0183] In this embodiment, when the above-mentioned third reason value indicates insufficient resources, the terminal can release the current user plane connection and send a fourth user plane connection establishment request message to the second network element, and then the second network element can reselect the fourth network element for the terminal to establish a user plane connection between the terminal and the fourth network element. The fourth network element is of the same type as the first network element. For example, taking the first network element as LMF and the second network element as AMF as an example, the terminal sends a fourth user plane connection establishment request message to AMF to request a new LMF address for establishing a new user plane positioning connection to send a user plane message.

[0184] The following describes the user plane connection release process using the data service as the positioning service and the first network element as the LMF as an example:

[0185] As shown in Figure 4c, the user plane connection release process between the UE and the LMF may include the following steps:

[0186] Step 70a: Since the LMF handover requires the release of the current LMF connection, please refer to steps 31a and 31b of the aforementioned user plane connection modification process between the UE and the LMF for details.

[0187] Step 70b: The LMF decides to release the current connection based on the current service load and transmission performance. For example, the LMF believes that the LCS-UPP transmission rate is slow and wishes to switch the protocol, for example, to SUPL.

[0188] It should be noted that only one of the two steps 70a and 70b is executed.

[0189] For LMF to send the release cause value (release cause) to UE, there are two ways: Method 1, using a control plane message (ie, LMF->AMF->UE) to send it to UE; Method 2, using a user plane message (ie, LMF->UPF->RAN->UE) to send it to UE.

[0190] Release method 1:

[0191] Step 71a, LMF decides to release the current user plane connection, then LMF sends a Namf_Communication_N1N2MessageTransfer message to AMF, which carries a user plane connection release message and a release reason value (i.e., the third reason value).

[0192] Step 72a: When the AMF receives the user plane release message from the LMF, the AMF forwards it to the UE via a DL NAS TRANSPORT message.

[0193] Step 73a: The UE sends a user plane connection release response message, which may carry a message type to indicate rejection or acceptance of the above-mentioned user plane connection release request. The message is encapsulated in a UL NAS TRANSPORT message and sent to the AMF.

[0194] Step 74a: When the AMF receives the UL NAS TRANSPORT message from the UE, the AMF finds the LMF according to the UE LCS-UP context and forwards the user plane connection release response message carried in the UL NAS TRANSPORT message to the UE.

[0195] Release method 2:

[0196] Step 71b: The LMF sends a user plane connection release request message to the UE to request the release of the current user plane connection between the UE and the LMF. The message may carry a message type and a release cause value. The release cause value may include one of the following: normal release, protocol switching, insufficient resources, or LMF restart.

[0197] Optionally, when the release reason is protocol switching, the user plane connection release request message further carries a target protocol.

[0198] Step 72b: The UE sends a user plane connection release response message to the LMF. The message may carry a message type to indicate rejection or acceptance of the above user plane connection release request.

[0199] Step 73b: After receiving the release request message, the UE releases the current user plane connection and does not send any message on the current user plane connection.

[0200] An optional implementation manner is: when the release cause indicates protocol switching, the UE uses the target protocol to communicate with the LMF on the user plane.

[0201] An optional implementation is: when the release reason indicates insufficient resources, the UE can release the current user plane connection and re-initiate the terminal-triggered user plane connection process to request a new network element (e.g., LMF) address to establish a new user plane connection to send user plane messages, such as positioning messages.

[0202] Please refer to FIG5 , which is a flowchart of a transmission method provided in an embodiment of the present application. The method can be performed by a network-side device, as shown in FIG5 , including the following steps:

[0203] Step 501: A first network element sends a first message to a terminal.

[0204] Among them, the first message carries first information, and the first information is used to indicate at least one of the following: whether to accept the first user plane connection establishment request message sent by the terminal, the reason for requesting to modify the user plane connection between the terminal and the first network element, and the reason for requesting to release the user plane connection between the terminal and the first network element; the first user plane connection establishment request message is used to request to establish a user plane connection between the terminal and the first network element.

[0205] Optionally, when the first information is used to indicate whether to accept the first user plane connection establishment request message sent by the terminal, the first information includes at least one of the following: a first message type, a first cause value, and a backoff time; wherein, the first message type is used to indicate rejection or acceptance of the user plane connection establishment request, and the first cause value is used to indicate congestion of the first network element or protocol mismatch.

[0206] Optionally, the first user plane connection establishment request message is a user plane connection establishment request message sent by the terminal to the first network element through the user plane.

[0207] Optionally, when the first information is used to indicate the reason for requesting to modify the user plane connection between the terminal and the first network element, the first information includes a second reason value, wherein the second reason value is used to indicate at least one of the following: congestion of the first network element, the terminal moving out of the service area of ​​the first network element, insufficient resources, and protocol switching.

[0208] Optionally, when the second cause value is used to indicate protocol switching, the first information also includes a target protocol.

[0209] An optional implementation manner is: the first information carries a target protocol information element (target protocol information element), the target protocol information element includes a first bit, the first bit indicates whether the terminal is required to switch to protocol A (such as SUPL protocol), when the value of the first bit is 0, the terminal is not required to use protocol A for transmitting user plane messages, such as positioning messages; when the value of the first bit is 1, the terminal is required to use protocol A for transmitting user plane messages, such as positioning messages.

[0210] Optionally, the first information further includes at least one of the following: a second message type, a target network element address; wherein the second message type is used to indicate that the first message is used to request modification of a user plane connection.

[0211] Optionally, the first message is a message sent by the first network element to the terminal through a user plane, or the first message is a message sent by the first network element to the terminal through a control plane.

[0212] Optionally, the method further includes:

[0213] The first network element receives a second message sent by the terminal, wherein the second message is used to indicate acceptance or rejection of a user plane connection modification request.

[0214] Optionally, when the first information is used to indicate the reason for requesting to release the user plane connection between the terminal and the first network element, the first information includes a third cause value, wherein the third cause value is used to indicate normal release, protocol switching, insufficient resources or restart of the first network element.

[0215] Optionally, when the third cause value is used to indicate protocol switching, the first information also includes a target protocol.

[0216] An optional implementation manner is: the first information carries a target protocol information element, the target protocol information element includes a first bit, and the first bit indicates whether the terminal is required to switch to protocol A (such as SUPL protocol). When the value of the first bit is 0, the terminal is not required to use protocol A for user plane message transmission, such as positioning message; when the value of the first bit is 1, the terminal is required to use protocol A for user plane message transmission, such as positioning message.

[0217] Optionally, the method further includes:

[0218] In a case where the third cause value is used to indicate protocol switching, the first network element uses the target protocol to perform user plane communication with the terminal.

[0219] Optionally, the first message is a message sent by the first network element to the terminal through a user plane, or the first message is a message sent by the first network element to the terminal through a control plane.

[0220] Optionally, the method further includes:

[0221] The first network element receives a third message sent by the terminal, wherein the third message is used to indicate acceptance or rejection of a user plane connection release request.

[0222] Optionally, the first network element sending the first message to the terminal includes:

[0223] When the first network element determines that the service load and transmission performance determine that the user plane connection between the first network element and the terminal needs to be released, the first network element sends a first message to the terminal.

[0224] It should be noted that the implementation of this embodiment can refer to the relevant description of the embodiment shown in Figure 3, and will not be repeated here.

[0225] It should be noted that the transmission method provided in the embodiment of the present application can be executed by a transmission device, or a control module in the transmission device for executing the transmission method. In the embodiment of the present application, the transmission device provided in the embodiment of the present application is described by taking the transmission method executed by the transmission device as an example.

[0226] Please refer to FIG6 , which is a structural diagram of a transmission device provided in an embodiment of the present application. As shown in FIG6 , the transmission device 600 includes:

[0227] A first receiving module 601 is configured to receive a first message sent by a first network element;

[0228] Among them, the first message carries first information, and the first information is used to indicate at least one of the following: whether to accept the first user plane connection establishment request message sent by the terminal, the reason for requesting to modify the user plane connection between the terminal and the first network element, and the reason for requesting to release the user plane connection between the terminal and the first network element; the first user plane connection establishment request message is used to request to establish a user plane connection between the terminal and the first network element.

[0229] Optionally, when the first information is used to indicate whether to accept the first user plane connection establishment request message sent by the terminal, the first information includes at least one of the following: a first message type, a first cause value, and a backoff time; wherein, the first message type is used to indicate rejection or acceptance of the user plane connection establishment request, and the first cause value is used to indicate congestion of the first network element or protocol mismatch.

[0230] Optionally, the device further includes a second sending module, specifically configured to:

[0231] In a case where the first information includes the backoff time, starting a timer, and sending a second user plane connection establishment request message to the first network element after the timer expires; wherein the initial value of the timer is the backoff time;

[0232] or,

[0233] When the first cause value indicates that the protocol does not match, a third user plane connection establishment request message is sent to the second network element; wherein the third user plane connection establishment request message includes at least one of the following: first indication information, the protocol used by the terminal; the first indication information is used to instruct the second network element to select a third network element that supports the protocol used by the terminal.

[0234] Optionally, the first user plane connection establishment request message is a user plane connection establishment request message sent by the terminal to the first network element through the user plane.

[0235] Optionally, when the first information is used to indicate the reason for requesting to modify the user plane connection between the terminal and the first network element, the first information includes a second reason value, wherein the second reason value is used to indicate at least one of the following: congestion of the first network element, the terminal moving out of the service area of ​​the first network element, insufficient resources, and protocol switching.

[0236] Optionally, the first information further includes at least one of the following: a second message type, a target network element address; wherein the second message type is used to indicate that the first message is used to request modification of a user plane connection.

[0237] Optionally, the first message is a message sent by the first network element to the terminal through a user plane, or the first message is a message sent by the first network element to the terminal through a control plane.

[0238] Optionally, the device further comprises:

[0239] The third sending module is used to send a second message to the first network element, wherein the second message is used to indicate acceptance or rejection of the user plane connection modification request.

[0240] Optionally, when the first information is used to indicate the reason for requesting to release the user plane connection between the terminal and the first network element, the first information includes a third cause value, wherein the third cause value is used to indicate normal release, protocol switching, insufficient resources or restart of the first network element.

[0241] Optionally, when the third cause value is used to indicate protocol switching, the first information also includes a target protocol.

[0242] Optionally, the device further comprises:

[0243] The fourth sending module is used to send a third message to the first network element, wherein the third message is used to indicate acceptance or rejection of the user plane connection release request.

[0244] Optionally, the device further comprises:

[0245] A release module is used to release the user plane connection between the terminal and the first network element when the third message is used to indicate acceptance of the user plane connection release request.

[0246] Optionally, the device further comprises:

[0247] The first communication module is configured to perform user plane communication with the first network element by using the target protocol when the third cause value is used to indicate protocol switching.

[0248] Optionally, the first message is a message sent by the first network element to the terminal through a user plane, or the first message is a message sent by the first network element to the terminal through a control plane.

[0249] Optionally, the device further comprises:

[0250] The fifth sending module is used to send a fourth user plane connection establishment request message to the second network element when the third cause value is used to indicate insufficient resources.

[0251] The transmission device in the embodiments of the present application can be an electronic device, such as an electronic device with an operating system, or a component in an electronic device, such as an integrated circuit or chip. The electronic device can be a terminal, or it can be other devices other than a terminal. For example, the terminal can include but is not limited to the types of terminal 11 listed above, and other devices can be servers, network attached storage (NAS), etc., which are not specifically limited in the embodiments of the present application.

[0252] The transmission device provided in the embodiment of the present application can implement each process implemented in the method embodiment of Figure 3 and achieve the same technical effect. To avoid repetition, it will not be repeated here.

[0253] Please refer to FIG. 7 , which is a structural diagram of a transmission device provided in an embodiment of the present application. As shown in FIG. 7 , the transmission device 700 includes:

[0254] A first sending module 701 is configured to send a first message to a terminal;

[0255] Among them, the first message carries first information, and the first information is used to indicate at least one of the following: whether to accept the first user plane connection establishment request message sent by the terminal, the reason for requesting to modify the user plane connection between the terminal and the first network element, and the reason for requesting to release the user plane connection between the terminal and the first network element; the first user plane connection establishment request message is used to request to establish a user plane connection between the terminal and the first network element.

[0256] Optionally, when the first information is used to indicate whether to accept the first user plane connection establishment request message sent by the terminal, the first information includes at least one of the following: a first message type, a first cause value, and a backoff time; wherein, the first message type is used to indicate rejection or acceptance of the user plane connection establishment request, and the first cause value is used to indicate congestion of the first network element or protocol mismatch.

[0257] Optionally, the first user plane connection establishment request message is a user plane connection establishment request message sent by the terminal to the first network element through the user plane.

[0258] Optionally, when the first information is used to indicate the reason for requesting to modify the user plane connection between the terminal and the first network element, the first information includes a second reason value, wherein the second reason value is used to indicate at least one of the following: congestion of the first network element, the terminal moving out of the service area of ​​the first network element, insufficient resources, and protocol switching.

[0259] Optionally, the first information further includes at least one of the following: a second message type, a target network element address; wherein the second message type is used to indicate that the first message is used to request modification of a user plane connection.

[0260] Optionally, the first message is a message sent by the first network element to the terminal through a user plane, or the first message is a message sent by the first network element to the terminal through a control plane.

[0261] Optionally, the device further comprises:

[0262] The second receiving module is configured to receive a second message sent by the terminal, wherein the second message is used to indicate acceptance or rejection of the user plane connection modification request.

[0263] Optionally, when the first information is used to indicate the reason for requesting to release the user plane connection between the terminal and the first network element, the first information includes a third cause value, wherein the third cause value is used to indicate normal release, protocol switching, insufficient resources or restart of the first network element.

[0264] Optionally, when the third cause value is used to indicate protocol switching, the first information also includes a target protocol.

[0265] Optionally, the device further comprises:

[0266] The second communication module is configured to perform user plane communication with the terminal using the target protocol when the third cause value is used to indicate protocol switching.

[0267] Optionally, the first message is a message sent by the first network element to the terminal through a user plane, or the first message is a message sent by the first network element to the terminal through a control plane.

[0268] Optionally, the device further comprises:

[0269] The third receiving module is used to receive a third message sent by the terminal, wherein the third message is used to indicate acceptance or rejection of the user plane connection release request.

[0270] Optionally, the sending module is specifically configured to:

[0271] When it is determined that the service load and the transmission performance determine that the user plane connection between the first network element and the terminal needs to be released, the first network element sends a first message to the terminal.

[0272] The transmission device in the embodiments of the present application can be an electronic device, such as an electronic device with an operating system, or a component in an electronic device, such as an integrated circuit or chip. The electronic device can be a network-side device, or it can be a device other than a network-side device. For example, the network-side device can include, but is not limited to, the types of network-side devices 12 listed above. Other devices can include servers, network attached storage (NAS), etc., and the embodiments of the present application do not specifically limit this.

[0273] The transmission device provided in the embodiment of the present application can implement each process implemented in the method embodiment of Figure 5 and achieve the same technical effect. To avoid repetition, it will not be repeated here.

[0274] Optionally, as shown in Figure 8, an embodiment of the present application further provides a communication device 800, including a processor 801 and a memory 802, wherein the memory 802 stores a program or instruction that can be run on the processor 801. For example, when the communication device 800 is a terminal, the program or instruction is executed by the processor 801 to implement the various steps of the above-mentioned transmission method embodiment and can achieve the same technical effect. When the communication device 800 is a network-side device, the program or instruction is executed by the processor 801 to implement the various steps of the above-mentioned transmission method embodiment and can achieve the same technical effect. To avoid repetition, it will not be repeated here.

[0275] An embodiment of the present application also provides a terminal, including a processor and a communication interface, wherein the communication interface is used to receive a first message sent by a first network element; wherein the first message carries first information, and the first information is used to indicate at least one of the following: whether to accept the first user plane connection establishment request message sent by the terminal, the reason for requesting to modify the user plane connection between the terminal and the first network element, and the reason for requesting to release the user plane connection between the terminal and the first network element; the first user plane connection establishment request message is used to request to establish a user plane connection between the terminal and the first network element. This terminal embodiment corresponds to the above-mentioned terminal side method embodiment, and each implementation process and implementation method of the above-mentioned method embodiment can be applied to this terminal embodiment and can achieve the same technical effect. Specifically, Figure 9 is a schematic diagram of the hardware structure of a terminal that implements an embodiment of the present application.

[0276] The terminal 900 includes but is not limited to: a radio frequency unit 901, a network module 902, an audio output unit 903, an input unit 904, a sensor 905, a display unit 906, a user input unit 907, an interface unit 908, a memory 909 and at least some of the components of the processor 910.

[0277] Those skilled in the art will appreciate that the terminal 900 may further include a power source (such as a battery) for powering various components. The power source may be logically connected to the processor 910 via a power management system, thereby enabling the power management system to manage charging, discharging, and power consumption. The terminal structure shown in FIG9 does not limit the terminal. The terminal may include more or fewer components than shown, or may combine certain components, or have different component arrangements, which will not be described in detail here.

[0278] It should be understood that in an embodiment of the present application, the input unit 904 may include a graphics processing unit (GPU) 9041 and a microphone 9042, and the graphics processor 9041 processes the image data of a static picture or video obtained by an image capture device (such as a camera) in a video capture mode or an image capture mode. The display unit 906 may include a display panel 9061, and the display panel 9061 may be configured in the form of a liquid crystal display, an organic light emitting diode, etc. The user input unit 907 includes a touch panel 9071 and at least one of other input devices 9072. The touch panel 9071 is also called a touch screen. The touch panel 9071 may include two parts: a touch detection device and a touch controller. Other input devices 9072 may include, but are not limited to, a physical keyboard, function keys (such as volume control keys, switch keys, etc.), a trackball, a mouse, and an operating stick, which will not be repeated here.

[0279] In the embodiment of the present application, after receiving downlink data from a network-side device, the RF unit 901 may transmit the data to the processor 910 for processing. Furthermore, the RF unit 901 may send uplink data to the network-side device. Typically, the RF unit 901 includes, but is not limited to, an antenna, an amplifier, a transceiver, a coupler, a low-noise amplifier, a duplexer, and the like.

[0280] The memory 909 can be used to store software programs or instructions and various data. The memory 909 may mainly include a first storage area for storing programs or instructions and a second storage area for storing data, wherein the first storage area may store an operating system, applications or instructions required for at least one function (such as a sound playback function, an image playback function, etc.). In addition, the memory 909 may include a volatile memory or a non-volatile memory. Among them, the non-volatile memory may be a read-only memory (ROM), a programmable read-only memory (PROM), an erasable programmable read-only memory (EPROM), an electrically erasable programmable read-only memory (EEPROM), or a 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 RAM bus random access memory (DRRAM). The memory 909 in the embodiment of the present application includes but is not limited to these and any other suitable types of memory.

[0281] Processor 910 may include one or more processing units. Optionally, processor 910 integrates an application processor and a modem processor. The application processor primarily handles operations related to the operating system, user interface, and application programs, while the modem processor primarily processes wireless communication signals, such as a baseband processor. It is understood that the modem processor may not be integrated into processor 910.

[0282] Among them, the radio frequency unit 901 is used to receive a first message sent by a first network element; wherein the first message carries first information, and the first information is used to indicate at least one of the following: whether to accept the first user plane connection establishment request message sent by the terminal, the reason for requesting to modify the user plane connection between the terminal and the first network element, and the reason for requesting to release the user plane connection between the terminal and the first network element; the first user plane connection establishment request message is used to request to establish a user plane connection between the terminal and the first network element.

[0283] It can be understood that the implementation process of each implementation method mentioned in this embodiment can refer to the relevant description of the aforementioned method embodiment and achieve the same or corresponding technical effects. To avoid repetition, it will not be repeated here.

[0284] An embodiment of the present application also provides a network-side device, including a processor and a communication interface, the communication interface being used to send a first message to a terminal; wherein the first message carries first information, the first information being used to indicate at least one of the following: whether to accept the first user-plane connection establishment request message sent by the terminal, the reason for requesting to modify the user-plane connection between the terminal and the first network element, and the reason for requesting to release the user-plane connection between the terminal and the first network element; the first user-plane connection establishment request message is used to request to establish a user-plane connection between the terminal and the first network element. This network-side device embodiment corresponds to the above-mentioned network-side device method embodiment, and each implementation process and implementation method of the above-mentioned method embodiment can be applied to this network-side device embodiment and can achieve the same technical effect.

[0285] Specifically, the embodiment of the present application further provides a network side device. As shown in FIG10 , the network side device 1000 includes: a processor 1001, a network interface 1002, and a memory 1003. The network interface 1002 is, for example, a common public radio interface (CPRI).

[0286] Specifically, the network side device 1000 of the embodiment of the present application also includes: instructions or programs stored in the memory 1003 and executable on the processor 1001. The processor 1001 calls the instructions or programs in the memory 1003 to execute the method of execution of each module shown in Figure 7 and achieve the same technical effect. To avoid repetition, it will not be repeated here.

[0287] An embodiment of the present application also provides a readable storage medium, on which a program or instruction is stored. When the program or instruction is executed by a processor, the various processes of the above-mentioned transmission method embodiment are implemented and the same technical effect can be achieved. To avoid repetition, it will not be repeated here.

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

[0289] An embodiment of the present application further provides a chip, which includes a processor and a communication interface, the communication interface and the processor are coupled, and the processor is used to run programs or instructions to implement the various processes of the above-mentioned transmission method embodiment and can achieve the same technical effect. To avoid repetition, it will not be repeated here.

[0290] It should be understood that the chip mentioned in the embodiments of the present application can also be called a system-level chip, a system chip, a chip system or a system-on-chip chip, etc.

[0291] An embodiment of the present application further provides a computer program / program product, which is stored in a storage medium. The computer program / program product is executed by at least one processor to implement the various processes of the above-mentioned transmission method embodiment and can achieve the same technical effect. To avoid repetition, it will not be repeated here.

[0292] An embodiment of the present application also provides a transmission system, including: a terminal and a network-side device, wherein the terminal is used to execute the various processes as shown in Figure 3 and the various method embodiments described above, and the network-side device is used to execute the various processes as shown in Figure 5 and the various method embodiments described above, and can achieve the same technical effect. To avoid repetition, it will not be repeated here.

[0293] It should be noted that, in this article, the terms "comprise", "include" or any other variants thereof are intended to cover non-exclusive inclusion, so that a process, method, article or device comprising a series of elements includes not only those elements, but also other elements not explicitly listed, or also includes elements inherent to such process, method, article or device. In the absence of further restrictions, an element defined by the sentence "comprises a ..." does not exclude the presence of other identical elements in the process, method, article or device comprising the element. In addition, it should be pointed out that the scope of the methods and devices in the embodiments of the present application is not limited to performing functions in the order shown or discussed, and may also include performing functions in a substantially simultaneous manner or in the opposite order according to the functions involved. For example, the described method may be performed in an order different from that described, and various steps may also be added, omitted or combined. In addition, the features described with reference to certain examples may be combined in other examples.

[0294] Through the description of the above embodiments, those skilled in the art can clearly understand that the above-mentioned embodiment methods can be implemented by means of a computer software product plus a necessary general-purpose hardware platform, or of course, by hardware. The computer software product is stored in a storage medium (such as ROM, RAM, magnetic disk, optical disk, etc.) and includes a number of instructions for enabling a terminal or network-side device to execute the methods described in each embodiment of the present application.

[0295] The embodiments of the present application are described above in conjunction with the accompanying drawings, but the present application is not limited to the above-mentioned specific implementation methods. The above-mentioned specific implementation methods are merely illustrative and not restrictive. Under the guidance of this application, ordinary technicians in this field can also make many forms of implementation methods without departing from the purpose of this application and the scope of protection of the claims. These implementation methods are all within the protection of this application.

Claims

1. A transmission method, wherein: include: The terminal receives a first message sent by the first network element; The first message carries first information, and the first information is used to indicate at least one of the following: whether to accept the first user plane connection establishment request message sent by the terminal, the reason for requesting to modify the user plane connection between the terminal and the first network element, and the reason for requesting to release the user plane connection between the terminal and the first network element; The first user plane connection establishment request message is used to request to establish a user plane connection between the terminal and the first network element.

2. The method according to claim 1, wherein: In the case where the first information is used to indicate whether to accept the first user plane connection establishment request message sent by the terminal, the first information includes at least one of the following: a first message type, a first cause value, and a backoff time; wherein the first message type is used to indicate rejection or acceptance of the user plane connection establishment request, and the first cause value is used to indicate congestion or protocol mismatch of the first network element.

3. The method according to claim 2, wherein: The method further comprises: In the case where the first information includes the backoff time, the terminal starts a timer, and sends a second user plane connection establishment request message to the first network element after the timer times out; wherein an initial value of the timer is the backoff time; or, When the first cause value indicates that the protocol does not match, the terminal sends a third user plane connection establishment request message to the second network element; wherein the third user plane connection establishment request message includes at least one of the following: first indication information, the protocol used by the terminal; the first indication information is used to instruct the second network element to select a third network element that supports the protocol used by the terminal.

4. The method according to any one of claims 1 to 3, wherein: The first user plane connection establishment request message is a user plane connection establishment request message sent by the terminal to the first network element through the user plane.

5. The method according to any one of claims 1 to 4, wherein: In the case where the first information is used to indicate the reason for requesting to modify the user plane connection between the terminal and the first network element, the first information includes a second reason value, wherein the second reason value is used to indicate at least one of the following: congestion in the first network element, the terminal moves out of the service area of ​​the first network element, insufficient resources, and protocol switching.

6. The method according to claim 5, wherein: The first information also includes at least one of the following: a second message type, a target network element address; wherein the second message type is used to indicate that the first message is used to request modification of a user plane connection.

7. The method according to claim 5 or 6, wherein: The first message is a message sent by the first network element to the terminal through a user plane, or the first message is a message sent by the first network element to the terminal through a control plane.

8. The method according to any one of claims 5 to 7, wherein: The method further comprises: The terminal sends a second message to the first network element, wherein the second message is used to indicate acceptance or rejection of a user plane connection modification request.

9. The method according to any one of claims 1 to 8, wherein: In the case where the first information is used to indicate the reason for requesting to release the user plane connection between the terminal and the first network element, the first information includes a third cause value, wherein the third cause value is used to indicate normal release, protocol switching, insufficient resources, or restart of the first network element.

10. The method according to claim 9, wherein: In the case where the third cause value is used to indicate protocol switching, the first information further includes a target protocol.

11. The method according to any one of claims 9 to 10, wherein: The first message is a message sent by the first network element to the terminal through a user plane, or the first message is a message sent by the first network element to the terminal through a control plane.

12. The method according to any one of claims 9 to 11, wherein: The method further comprises: The terminal sends a third message to the first network element, wherein the third message is used to indicate acceptance or rejection of a user plane connection release request.

13. The method according to claim 12, wherein: The method further comprises: In a case where the third message is used to indicate acceptance of a user plane connection release request, the terminal releases the user plane connection between the terminal and the first network element.

14. The method according to any one of claims 10 to 13, wherein: The method further comprises: In a case where the third cause value is used to indicate protocol switching, the terminal uses the target protocol to perform user plane communication with the first network element.

15. The method according to any one of claims 9 to 13, wherein: The method further comprises: When the third cause value is used to indicate insufficient resources, the terminal sends a fourth user plane connection establishment request message to the second network element.

16. A transmission method, wherein: include: The first network element sends a first message to the terminal; The first message carries first information, and the first information is used to indicate at least one of the following: whether to accept the first user plane connection establishment request message sent by the terminal, the reason for requesting to modify the user plane connection between the terminal and the first network element, and the reason for requesting to release the user plane connection between the terminal and the first network element; The first user plane connection establishment request message is used to request to establish a user plane connection between the terminal and the first network element.

17. The method according to claim 16, wherein: In the case where the first information is used to indicate whether to accept the first user plane connection establishment request message sent by the terminal, the first information includes at least one of the following: a first message type, a first cause value, and a backoff time; wherein the first message type is used to indicate rejection or acceptance of the user plane connection establishment request, and the first cause value is used to indicate congestion or protocol mismatch of the first network element.

18. The method according to any one of claims 16 to 17, wherein: The first user plane connection establishment request message is a user plane connection establishment request message sent by the terminal to the first network element through the user plane.

19. The method according to any one of claims 16 to 18, wherein: In the case where the first information is used to indicate the reason for requesting to modify the user plane connection between the terminal and the first network element, the first information includes a second reason value, wherein the second reason value is used to indicate at least one of the following: congestion in the first network element, the terminal moves out of the service area of ​​the first network element, insufficient resources, and protocol switching.

20. The method according to claim 19, wherein: The first information also includes at least one of the following: a second message type, a target network element address; wherein the second message type is used to indicate that the first message is used to request modification of a user plane connection.

21. The method according to claim 19 or 20, wherein: The first message is a message sent by the first network element to the terminal through a user plane, or the first message is a message sent by the first network element to the terminal through a control plane.

22. The method according to any one of claims 19 to 21, wherein: The method further comprises: The first network element receives a second message sent by the terminal, wherein the second message is used to indicate acceptance or rejection of a user plane connection modification request.

23. The method according to any one of claims 16 to 22, wherein: In the case where the first information is used to indicate the reason for requesting to release the user plane connection between the terminal and the first network element, the first information includes a third cause value, wherein the third cause value is used to indicate normal release, protocol switching, insufficient resources, or restart of the first network element.

24. The method according to claim 23, wherein: In the case where the third cause value is used to indicate protocol switching, the first information further includes a target protocol.

25. The method according to claim 24, wherein: The method further comprises: In a case where the third cause value is used to indicate protocol switching, the first network element uses the target protocol to perform user plane communication with the terminal.

26. The method according to any one of claims 23 to 25, wherein: The first message is a message sent by the first network element to the terminal through a user plane, or the first message is a message sent by the first network element to the terminal through a control plane.

27. The method according to any one of claims 23 to 26, wherein: The method further comprises: The first network element receives a third message sent by the terminal, wherein the third message is used to indicate acceptance or rejection of a user plane connection release request.

28. The method according to any one of claims 23 to 27, wherein: The first network element sending a first message to the terminal includes: When the first network element determines that the service load and transmission performance determine that the user plane connection between the first network element and the terminal needs to be released, the first network element sends a first message to the terminal.

29. A transmission device, wherein: include: A first receiving module, configured to receive a first message sent by a first network element; The first message carries first information, and the first information is used to indicate at least one of the following: whether to accept the first user plane connection establishment request message sent by the terminal, the reason for requesting to modify the user plane connection between the terminal and the first network element, and the reason for requesting to release the user plane connection between the terminal and the first network element; The first The user plane connection establishment request message is used to request to establish a user plane connection between the terminal and the first network element.

30. A transmission device, wherein: include: A first sending module, used to send a first message to a terminal; The first message carries first information, and the first information is used to indicate at least one of the following: whether to accept the first user plane connection establishment request message sent by the terminal, the reason for requesting to modify the user plane connection between the terminal and the first network element, and the reason for requesting to release the user plane connection between the terminal and the first network element; The first user plane connection establishment request message is used to request to establish a user plane connection between the terminal and the first network element.

31. A terminal, wherein: The method comprises a processor and a memory, wherein the memory stores a program or instruction that can be run on the processor, and when the program or instruction is executed by the processor, the steps of the transmission method according to any one of claims 1 to 15 are implemented.

32. A network side device, wherein: It comprises a processor and a memory, wherein the memory stores a program or instruction that can be run on the processor, and when the program or instruction is executed by the processor, the steps of the transmission method according to any one of claims 16 to 28 are implemented.

33. A readable storage medium, wherein: The readable storage medium stores a program or instruction, and when the program or instruction is executed by the processor, it implements the steps of the transmission method according to any one of claims 1 to 15, or implements the steps of the transmission method according to any one of claims 16 to 28.

34. A chip, wherein: The chip includes a processor and a communication interface, the communication interface is coupled to the processor, and the processor is used to run a program or instruction to implement the steps of the transmission method as described in any one of claims 1 to 15, or to implement the steps of the transmission method as described in any one of claims 16 to 28.

35. A computer program product, wherein: The program product is executed by at least one processor to implement the steps of the information transmission method according to any one of claims 1 to 11, or to implement the steps of the transmission method according to any one of claims 1 to 15, or to implement the steps of the transmission method according to any one of claims 16 to 28.

36. A transmission device / equipment, wherein: The apparatus / device is configured to perform the steps of the transmission method according to any one of claims 1 to 15, or the steps of the transmission method according to any one of claims 16 to 28.

Images