Communication method and device

Abstract

The present application relates to a communication method, a device, a computer readable storage medium, a computer program product, and a computer program. The method comprises: a terminal sending execution indication information, the execution indication information being used to indicate that data transmission control be executed on a first 3GPP user plane connection, and the first 3GPP user plane connection being one of multiple 3GPP user plane connections supported and established by the terminal.

Description

Communication method and device Technical Field

[0001] The present application relates to the field of communications, and more specifically, to a communication method, device, computer-readable storage medium, computer program product, and computer program. Background Art

[0002] In the related art, the premise for achieving the common correspondence between a 3GPP (3rd Generation Partnership Project) user plane connection and a non-3GPP user plane connection on a PDU session is that the UE can establish a control plane connection through 3GPP access and non-3GPP access, and the signaling processes related to the establishment of the two user plane connections can also interact on the two control plane connections respectively. However, in the related art, the terminal cannot support the establishment or maintenance of multiple 3GPP user plane connections through multiple 3GPP accesses, and the related art cannot realize the control of data transmission of different 3GPP user plane connections in the scenario where the terminal supports multiple 3GPP user plane connections.

[0003] Summary of the Invention

[0004] Embodiments of the present application provide a communication method, device, computer-readable storage medium, computer program product, and computer program.

[0005] An embodiment of the present application provides a communication method, including:

[0006] The terminal sends execution indication information, wherein the execution indication information is used to instruct execution of data transmission control on a first 3GPP user plane connection, where the first 3GPP user plane connection is one of multiple 3GPP user plane connections supported by the terminal.

[0007] An embodiment of the present application provides a communication method, including:

[0008] The core network element receives execution instruction information, wherein the execution instruction information is used to instruct execution of data transmission control on a first 3GPP user plane connection of the terminal, where the first 3GPP user plane connection is one of multiple 3GPP user plane connections supported by the terminal.

[0009] An embodiment of the present application provides a terminal, including:

[0010] The first communication unit is configured to send execution indication information, wherein the execution indication information is used to instruct execution of data transmission control on a first 3GPP user plane connection, where the first 3GPP user plane connection is one of a plurality of 3GPP user plane connections supported by the terminal.

[0011] The present invention provides a core network element, including:

[0012] The second communication unit is configured to receive execution instruction information, wherein the execution instruction information is used to instruct execution of data transmission control on a first 3GPP user plane connection of the terminal, where the first 3GPP user plane connection is one of multiple 3GPP user plane connections supported by the terminal.

[0013] An embodiment of the present application provides a terminal, comprising: a transceiver, a processor, and a memory. The memory is used to store a computer program, the transceiver is used to communicate with other devices, and the processor is used to call and run the computer program stored in the memory, so that the terminal executes the above method.

[0014] An embodiment of the present application provides a core network element, comprising: a transceiver, a processor, and a memory. The memory is used to store a computer program, the transceiver is used to communicate with other devices, and the processor is used to call and execute the computer program stored in the memory, so that the core network element performs the above method.

[0015] The embodiment of the present application provides a chip for implementing the above method.

[0016] Specifically, the chip includes: a processor, which is used to call and run a computer program from a memory, so that a device equipped with the chip executes the above method.

[0017] An embodiment of the present application provides a computer-readable storage medium for storing a computer program, which enables a device to perform the above method when the computer program is executed by the device.

[0018] An embodiment of the present application provides a computer program product, including computer program instructions, which enable a computer to execute the above method.

[0019] An embodiment of the present application provides a computer program, which, when executed on a computer, enables the computer to execute the above method.

[0020] By adopting the solution provided in this embodiment, when a terminal supports establishing multiple 3GPP user plane connections, the terminal can initiate execution indication information to control data transmission of any 3GPP user plane connection. In this way, the terminal can flexibly control data transmission of different 3GPP user plane connections when supporting multiple 3GPP user plane connections. BRIEF DESCRIPTION OF THE DRAWINGS

[0021] FIG1 is a schematic diagram of an application scenario according to an embodiment of the present application.

[0022] Figure 2 is a schematic diagram of the 5G network system architecture.

[0023] FIG3 is a schematic diagram of a scenario of a multi-access (MA)-PDU.

[0024] FIG4 is a schematic flowchart of a communication method according to an embodiment of the present application.

[0025] FIG5 is a schematic flowchart of a communication method according to another embodiment of the present application.

[0026] FIG6a and FIG6b are schematic diagrams of two scenarios in which a user plane connection is established through two 3GPP accesses in the present application.

[0027] 7 to 13 are various exemplary flow charts of a communication method according to an embodiment of the present application.

[0028] FIG14 is a schematic block diagram of a terminal according to an embodiment of the present application.

[0029] FIG15 is a schematic block diagram of a core network element according to an embodiment of the present application.

[0030] FIG16 is a schematic block diagram of a communication device according to an embodiment of the present application.

[0031] FIG17 is a schematic block diagram of a chip according to an embodiment of the present application.

[0032] FIG18 is a schematic block diagram of a communication system according to an embodiment of the present application. DETAILED DESCRIPTION

[0033] The technical solutions in the embodiments of the present application will be described below in conjunction with the drawings in the embodiments of the present application.

[0034] The technical solutions of the embodiments of the present application can be applied to various communication systems, such as: Long Term Evolution (LTE) system, Advanced Long Term Evolution (LTE-A) system, New Radio (NR) system, NR system evolution system, LTE on unlicensed spectrum (LTE-U) system, NR on unlicensed spectrum (NR-based access to unlicensed spectrum, NR-U) system, Non-Terrestrial Networks (NTN) system, Universal Mobile Telecommunication System (UMTS), Wireless Local Area Networks (WLAN), Wireless Fidelity (WiFi), Fifth Generation (5G) system or other communication systems.

[0035] Generally speaking, traditional communication systems support a limited number of connections and are easy to implement. However, with the development of communication technology, mobile communication systems will not only support traditional communications, but will also support, for example, device-to-device (D2D) communication, machine-to-machine (M2M) communication, machine-type communication (MTC), vehicle-to-vehicle (V2V) communication, or vehicle-to-everything (V2X) communication, and the embodiments of the present application may also be applied to these communication systems. In one possible implementation, the communication system in the embodiment of the present application may be applied to a carrier aggregation (CA) scenario, a dual connectivity (DC) scenario, or a standalone (SA) networking scenario. In one possible implementation, the communication system in the embodiment of the present application may be applied to an unlicensed spectrum, where the unlicensed spectrum may also be considered a shared spectrum; or, the communication system in the embodiment of the present application may also be applied to an authorized spectrum, where the authorized spectrum may also be considered a non-shared spectrum.

[0036] The embodiments of the present application describe various embodiments in conjunction with network devices and terminal devices, where the terminal device may also be referred to as user equipment (UE), access terminal, subscriber unit, subscriber station, mobile station, mobile station, remote station, remote terminal, mobile device, user terminal, terminal, wireless communication device, user agent, or user device, etc. The terminal device may be a station (STAION, ST) in a WLAN, a cellular phone, a cordless phone, a Session Initiation Protocol (SIP) phone, a Wireless Local Loop (WLL) station, a Personal Digital Assistant (PDA) device, a handheld device with wireless communication capabilities, a computing device or other processing device connected to a wireless modem, an in-vehicle device, a wearable device, a terminal device in a next-generation communication system such as a NR network, or a terminal device in a future-evolved Public Land Mobile Network (PLMN) network, etc. In an embodiment of the present application, the terminal device can be deployed on land, including indoors or outdoors, handheld, wearable or vehicle-mounted; it can also be deployed on the water surface (such as a ship, etc.); it can also be deployed in the air (such as an airplane, a balloon, and a satellite, etc.). In an embodiment of the present application, the terminal device can be a mobile phone, a tablet computer, a computer with wireless transceiver function, a virtual reality (VR) terminal device, an augmented reality (AR) terminal device, a wireless terminal device in industrial control, a wireless terminal device in self-driving, a wireless terminal device in remote medical, a wireless terminal device in a smart grid, a wireless terminal device in transportation safety, a wireless terminal device in a smart city, or a wireless terminal device in a smart home, etc. As an example and not a limitation, in an embodiment of the present application, the terminal device can also be a wearable device. Wearable devices, also known as wearable smart devices, are a general term for wearable devices developed by applying wearable technology to intelligently design everyday wearables, such as glasses, gloves, watches, clothing, and shoes. Wearable devices are portable devices that are worn directly on the body or integrated into clothing or accessories. Wearable devices are more than just hardware devices; they also enable powerful functionality through software support, data interaction, and cloud-based interaction.In a broad sense, wearable smart devices include those that are fully functional, large in size, and can achieve complete or partial functions without relying on smartphones, such as smart watches or smart glasses, as well as those that only focus on a certain type of application function and need to be used in conjunction with other devices such as smartphones, such as various smart bracelets and smart jewelry for vital sign monitoring.

[0037] In an embodiment of the present application, a network device may be a device for communicating with a mobile device. The network device may be an access point (AP) in a WLAN, a base station (BTS) in a GSM or CDMA, a base station (NodeB, NB) in a WCDMA, an evolved base station (eNB or eNodeB) in an LTE, or a relay station or access point, or a vehicle-mounted device, a wearable device, a network device (gNB) in an NR network, or a network device in a future evolved PLMN network or a network device in an NTN network. As an example and not a limitation, in an embodiment of the present application, the network device may have a mobile feature, for example, the network device may be a mobile device. Optionally, the network device may be a satellite or a balloon station. For example, the satellite may be a low earth orbit (LEO) satellite, a medium earth orbit (MEO) satellite, a geostationary earth orbit (GEO) satellite, a high elliptical orbit (HEO) satellite, etc. Optionally, the network device may also be a base station set up in a location such as land or water. In an embodiment of the present application, the network device may provide services for a cell, and the terminal device may communicate with the network device through the transmission resources used by the cell (for example, frequency domain resources, or spectrum resources). The cell may be a cell corresponding to the network device (for example, a base station), and the cell may belong to a macro base station or a base station corresponding to a small cell. The small cells here may include: metro cells, micro cells, pico cells, femto cells, etc. These small cells have the characteristics of small coverage and low transmission power, and are suitable for providing high-speed data transmission services.

[0038] Figure 1 exemplarily shows a communication system 100. The communication system includes a network device 110 and two terminal devices 120. In a possible implementation, the communication system 100 may include multiple network devices 110, and each network device 110 may include other number of terminal devices 120 within its coverage area, which is not limited in this embodiment of the present application. In a possible implementation, the communication system 100 may also include other network entities such as a Mobility Management Entity (MME) and an Access and Mobility Management Function (AMF), which is not limited in this embodiment of the present application. Among them, the network device may include an access network device and a core network network element. That is, the wireless communication system also includes multiple core networks for communicating with the access network device. The access network equipment may be an evolutionary base station (evolutional node B, which may be referred to as eNB or e-NodeB) macro base station, micro base station (also called "small base station"), micro base station, access point (AP), transmission point (TP) or new generation Node B (gNodeB) in a long-term evolution (LTE) system, a next-generation (mobile communication system) (next radio, NR) system or an authorized auxiliary access long-term evolution (LAA-LTE) system. It should be understood that the equipment with communication functions in the network / system in the embodiment of the present application may be referred to as communication equipment. Taking the communication system shown in Figure 1 as an example, the communication equipment may include network equipment and terminal equipment with communication functions. The network equipment and terminal equipment may be specific equipment in the embodiment of the present application, which will not be repeated here; the communication equipment may also include other equipment in the communication system, such as network controllers, mobile management entities and other network entities, which are not limited in the embodiment of the present application.

[0039] To facilitate understanding of the embodiments of the present application, the following briefly describes the basic processes and basic concepts involved in the embodiments of the present application. It should be understood that the basic processes and basic concepts introduced below do not limit the embodiments of the present application.

[0040] The 5G network system architecture is shown in Figure 2, which includes: NSSF (Network Slice Selection Function) is mainly used to manage network slice related information, such as selecting network slices for terminal devices; AUSF (Authentication Server Function) is used to complete the identity authentication function of user access; UDM (Unified Data Management) is used to manage and store contract data and authentication data; AMF (Access and Mobility Management Function) is used to complete mobility management, security anchor and secure UE policy management, etc. In addition to managing the mobility of UE, AMF is also responsible for forwarding session management related messages between UE and SMF; SMF (Session Management Function) is used to complete session management, UE IP address allocation and management, etc.; PCF (Policy Control Function) is responsible for formulating policies related to UE mobility management, session management, billing, etc.; AF (Application Function) is used for external application servers; UPF (User Plane Function) is used to manage and store user data and authentication data; The 5GC (5G Core Network) is used for complex user plane processing, such as forwarding traffic between the radio access network and the internet, reporting traffic usage, and implementing QoS (Quality of Service) policies. The DN (Data Network) is the external data network of the 5GC (such as the internet). Data is transmitted between the various nodes of the 5GC (5G Core Network), between the user equipment (UE) and 5GC nodes, between the UE and the Radio Access Network ((R)AN, Radio Access Network), and between the RAN and 5GC nodes through corresponding interfaces. For example, as shown in Figure 2: Data is transmitted between the AMF and NSSF in the 5GC via interface N22; the AMF transmits data with the SMF via interface N11; the AMF transmits data with the AUSF via N12; and the AMF transmits data with the UDM via interface N8. Data is transmitted between the SMF and the UPF via interface N4. The UPF transmits data with the external data network via interface N6 and with the AN via interface N3. The UE establishes an access layer connection with the (R)AN through the Uu interface, exchanges access layer messages and wireless data transmission, and establishes a non-access layer (NAS) connection with the AMF through the N1 interface, exchanges NAS messages.Data is transmitted between the RAN and AMF via the N2 interface, and between the RAN and UPF via the N3 interface. It should be understood that the above description only describes the interfaces between some nodes, and the other interfaces between other 5GC nodes in Figure 2 are not detailed one by one. In Figure 2, except for the UE, (R)AN, and DN, all other nodes are core network nodes; core network nodes can be further divided into user plane nodes (i.e., UPF in Figure 2) and control plane nodes (i.e., other core network nodes in the core network except UPF).

[0041] The current 3GPP (3rd Generation Partnership Project) system supports a multiple access (MA)-PDU ​​scenario (or session mode) that combines 3GPP access and non-3GPP (Non-3GPP) access. In the multiple access (MA)-PDU ​​scenario shown in Figure 3, the UE can access the core network through 3GPP access and non-3GPP access at the same time, and realize the transmission of different data packets through 3GPP access or non-3GPP (non-3gpp) access. In some actual use cases, there are many types of 3GPP access, including but not limited to NR access, E-UTRA access, satellite access, etc.; non-3GPP access includes but is not limited to Wi-Fi, etc. Specifically, the multi-access (MA)-PDU ​​scenario shown in Figure 3 includes: the UE connects to the UPF through the N3 interface via 3GPP access, the UPF connects to the UPF (PSA (Protocol Data Unit Session Anchor)) through the N9 interface, and finally the UPF (PSA) is connected to the server host through the N6 interface, so that the UE can transmit PDU (Protocol Data Unit) (or transmit PDU session) through a 3GPP connection; the UE connects to the N3IWF (Non-3GPP Inter Working Function) through non-3GPP access, the N3IWF connects to the UPF through the N3 interface, the UPF connects to the UPF (PSA) through the N9 interface, and finally the UPF (PSA) is connected to the server host through the N6 interface, so that the UE can transmit PDU (linked) through a non-3GPP connection.

[0042] Assuming that a PDU session allows both 3GPP and non-3GPP access, Multi-Access PDU Connection Service is implemented by establishing a Multi-Access PDU (MA-PDU) session, which may have user plane resources on two access networks. The MA-PDU session establishment method provided or supported by current 3GPP systems allows both a 3GPP user plane connection and a non-3GPP user plane connection to be mapped to a single MA-PDU session. This allows packets within this session to be steered, switched, or split according to policy (hereinafter referred to as SSS), a mechanism known as ATSSS (Access Traffic Steering, Switching, Splitting). The ATSSS mechanism supports Multi-Access PDU Connection Service by exchanging PDUs between the UE and a data network (e.g., a server host) using a 3GPP access network, a non-3GPP access network, and two independent N3 / N9 tunnels between the PSA and the RAN.

[0043] A UE may request an MA PDU session when it is registered via both 3GPP and non-3GPP access, or when it is registered via only one access. After establishing an MA PDU session, when user plane resources are available on both access networks, the UE applies the network-provided policies (i.e. ASSSS rules) and considers local conditions (e.g. network interface availability, signal loss conditions, user preferences, etc.) to decide how to distribute uplink traffic across the two access networks. Similarly, the UPF anchor of the MA PDU session applies the network-provided policies (i.e. N4 rules) and feedback information received from the UE via the user plane (e.g. access network unavailable or available) to decide how to distribute downlink traffic across devices. In two N3 / N9 tunnels and two access networks, when user plane resources are available on only one access network, the UE applies ASSSS rules and considers local conditions to trigger the establishment or activation of user plane resources on the other access network.

[0044] The type of the MA PDU session does not support the unstructured type. Specifically, the type of the MA PDU session can be one of the following types: IPv4, IPv6, IPv4v6, and Ethernet.

[0045] As can be seen, the MAPDU session relies on the convergence (anchor) of two access points on the UPF, which requires additional complexity on the network side to support. In the scenario of two 3GPP access points, even if steering, switching, or splitting (SSS) is performed using a similar establishment method as the current MA-PDU session, additional network configuration is still required. This configuration is relatively static and requires constant negotiation and update with the application, which cannot achieve flexible control of data transmission of user plane connections corresponding to different 3GPP access points.

[0046] Furthermore, if the SSS function is placed in the application layer, the 3GPP system only supports the opening and closing of data for each PDU session, and there is no need to aggregate the data to the same anchor point. In this case, the current mechanism needs to be enhanced as follows: For user plane connections (PDU sessions, PDN connections, etc.) established on different RAT types, it is necessary to support the UE's ability to quickly open or close data transmission, and considering compatibility issues, a negotiation mechanism is required; for opening and closing data transmission, operations of different granularities need to be supported, including UE granularity, user plane connection granularity, QoS flow / bearer granularity, uplink and downlink granularity, etc.

[0047] It should be understood that the terms "system" and "network" are often used interchangeably in this article. The term "and / or" in this article is merely a description of the association relationship of associated objects, indicating that three relationships may exist. For example, A and / or B can represent: A exists alone, A and B exist at the same time, and B exists alone. In addition, the character " / " in this article generally indicates that the objects associated before and after are in an "or" relationship. It should be understood that the "indication" mentioned in the embodiments of this application can be a direct indication, an indirect indication, or an indication of an association relationship. For example, A indicates B, which can mean that A directly indicates B, for example, B can be obtained through A; it can also mean that A indirectly indicates B, for example, A indicates C, and B can be obtained through C; it can also mean that there is an association relationship between A and B. In the description of the embodiments of this application, the term "corresponding" can mean that there is a direct or indirect correspondence between the two, or it can mean that there is an association relationship between the two, or it can mean a relationship between indication and indication, configuration and configuration, etc.

[0048] Figure 4 is a schematic flow chart of a communication method according to an embodiment of the present application. The method includes at least part of the following contents.

[0049] S410. The terminal sends execution indication information, where the execution indication information is used to instruct execution of data transmission control on a first 3GPP user plane connection, where the first 3GPP user plane connection is one of multiple 3GPP user plane connections established or supported by the terminal.

[0050] Figure 5 is a schematic flow chart of a communication method according to another embodiment of the present application. The method includes at least part of the following contents.

[0051] S510. A core network element receives execution instruction information, where the execution instruction information is used to instruct execution of data transmission control on a first 3GPP user plane connection of a terminal, where the first 3GPP user plane connection is one of multiple 3GPP user plane connections established or supported by the terminal.

[0052] Here, the core network elements may include control plane elements and / or user plane elements. Exemplarily, the control plane elements may include at least one of the following: one or more AMFs and one or more SMFs; the user plane elements may include a UPF. It should be understood that the above description is merely illustrative and does not exhaustively enumerate all possible control plane elements and / or user plane elements in the core network.

[0053] The terminal may be a 3GPP terminal, that is, a terminal that can access a 3GPP network to send and receive data. For example, the terminal may be a mobile phone, a watch, a tablet, etc. This embodiment does not enumerate or limit various possible types of terminals.

[0054] The first 3GPP user plane connection may be a 3GPP user plane connection currently established by the terminal. Furthermore, the first 3GPP user plane connection is a 3GPP user plane connection established before the terminal sends the execution instruction information. Exemplarily, the terminal currently (or before sending the execution instruction information) has established and simultaneously maintained multiple 3GPP user plane connections, and the multiple 3GPP user plane connections include the first 3GPP user plane connection; or, the first 3GPP user plane connection is the only 3GPP user plane connection established by the terminal, and the terminal supports the establishment of multiple 3GPP user plane connections, or the terminal has the ability to establish multiple 3GPP user plane connections.

[0055] The multiple 3GPP user plane connections may correspond to the same PDU session or the same PDN connection; or, different 3GPP user plane connections in the multiple 3GPP user plane connections may correspond to different PDU sessions or different PDN connections.

[0056] Different 3GPP user plane connections among the multiple 3GPP user plane connections correspond to at least one of the following differences: radio access technology (RAT), system type, network type, and network number.

[0057] Specifically, the terminal supports establishing multiple 3GPP user plane connections using at least one of the following: one or more RATs, one or more network types, one or more system types, and one or more network numbers. Furthermore, among the multiple 3GPP user plane connections supported by the terminal, different 3GPP user plane connections use at least one different RAT, network type, or system type.

[0058] The one or more RATs may include at least one of the following: Evolved Universal Terrestrial Radio Access (E-UTRA), NR terrestrial access, NR satellite access, etc. For example, the terminal supports establishing multiple 3GPP user plane connections using at least one of E-UTRA, NR, and satellite. For example, the terminal supports establishing one 3GPP user plane connection using NR and another 3GPP user plane connection using satellite, etc.

[0059] The one or more network types include at least one of the following: TN (Terrestrial Network) and NTN (Non-Terrestrial Network). For example, the terminal supports establishing multiple 3GPP user plane connections using at least one of TN and NTN. For example, the terminal supports establishing one 3GPP user plane connection using TN and another 3GPP user plane connection using NTN, and so on.

[0060] The one or more network types include at least one of the following: a PLMN (Public Land Mobile Network) and an NPN (Non-public network). For example, the terminal supports establishing multiple 3GPP user plane connections using at least one of a PLMN and an NPN. For example, the terminal supports establishing one 3GPP user plane connection using a PLMN and another 3GPP user plane connection using an NPN, and so on.

[0061] The one or more system types include at least one of the following: 5GS (fifth generation wireless communication system) and EPS (evolved packet system). For example, the terminal supports establishing multiple 3GPP user plane connections using at least one of 5GS and EPS. For example, the terminal supports establishing a 3GPP user plane connection (such as a PDU session) using 5GS and another 3GPP user plane connection (such as a public data network (PDN) connection) using EPS, etc.

[0062] The network number may also be alternatively referred to as a network identifier or network ID. The one or more network numbers may include at least one of the following: an ID of each PLMN in the one or more PLMNs, an ID of each SNPN in the one or more SNPNs.

[0063] It should be understood that the above-mentioned one or more RATs, one or more network types, and one or more system types can also be used in combination. For example, the terminal supports the use of PLMN and NPN under TN to establish multiple 3GPP user plane connections, etc., which are not limited or exhaustive here.

[0064] In conjunction with Figures 6a and 6b, an exemplary description is given of a scenario in which a UE establishes multiple 3GPP user plane connections. The difference between Figure 6a and Figure 6b is that the two 3GPP user plane connections in Figure 6a will be anchored to the same user plane anchor point (for example, anchor or anchor point (Anchor) UPF), and the two 3GPP user plane connections in Figure 6b do not need to be anchored to the same UPF. Specifically, the multi-access (MA) PDU scenario shown in Figure 6a includes: the UE is connected to 3GPP access-1, 3GPP access-1 is connected to UPF through the N3 interface, UPF is connected to the user plane anchor point through the N9 interface, and finally the user plane anchor point is connected to the DN through the N6 interface, so that the UE can transmit PDU (or PDU session) through a 3GPP user plane connection; the UE is also connected to 3GPP access-2, 3GPP access-2 is connected to another UPF through the N3 interface, UPF is connected to the user plane anchor point through the N9 interface, and finally the user plane anchor point is connected to the DN through the N6 interface, so that the UE can transmit PDU (linked) through the second 3GPP user plane connection. The multi-access (MA) PDU scenario shown in Figure 6b includes: the UE is connected to 3GPP access-1, 3GPP access-1 is connected to the UPF via the N3 interface, and the UPF is connected to the DN, that is, the UE establishes a 3GPP user plane connection; the UE can also be connected to 3GPP access-2, 3GPP access-2 is connected to another UPF via the N3 interface, and the UPF is connected to the DN, so that the UE can transmit PDUs through the second 3GPP user plane connection. The solution provided in the embodiment of the present application can be applied to any scenario provided in Figure 6a or Figure 6b above, that is, the solution provided in this embodiment does not limit whether multiple 3GPP user plane connections are anchored to the same UPF.

[0065] The data transmission control includes one of the following: enabling data transmission, disabling data transmission, and switching data transmission. That is, the execution indication information is used to instruct the terminal to request or require one of the following: enabling data transmission for the first 3GPP user plane connection, disabling data transmission for the first 3GPP user plane connection, or performing data switching for the first 3GPP user plane connection. The data switching for the first 3GPP user plane connection may include switching data transmitted on the first 3GPP user plane connection to another 3GPP user plane connection, or switching data from another 3GPP user plane connection to the first 3GPP user plane connection.

[0066] In some possible implementations, the terminal side may locally generate and save one or more execution parameters and / or one or more execution identifiers.

[0067] The one or more execution parameters and / or one or more execution identifiers generated locally by the terminal may include at least one of the following: an execution parameter for indicating the start of data transmission; an execution parameter for indicating the stop of data transmission; an execution parameter for indicating data switching; an execution identifier for indicating the start of data transmission; an execution identifier for indicating the stop of data transmission; an execution identifier for indicating data switching; an execution parameter for indicating one or more granularities of data transmission control; an execution identifier for indicating one or more granularities of data transmission control.

[0068] The one or more granularities include at least one of the following: session, 3GPP user plane connection, data flow, bearer, uplink, and downlink.

[0069] Here, the one or more execution parameters and / or one or more execution identifiers generated locally by the terminal refer to: the execution parameters and / or execution identifiers corresponding to all behaviors that the terminal itself supports or requests or requires or is capable of executing, and / or the execution parameters and / or execution identifiers corresponding to the granularity of all behaviors that the terminal itself supports or requests or requires or is capable of executing.

[0070] One or more execution parameters and / or one or more execution identifiers generated locally on the terminal side. When the terminal needs to send execution indication information, it can select one or more execution parameters or one or more execution identifiers from the one or more execution parameters and / or one or more execution identifiers generated and saved locally and add them to the execution indication information, so as to indicate the specific behavior and / or the target granularity of the specific behavior requested or required by the terminal to be performed on the first 3GPP user plane connection through the execution indication information.

[0071] Exemplarily, the execution parameters generated and saved locally by the terminal may also be referred to as candidate execution parameters, or available execution parameters, or candidate execution parameters, etc. Exemplarily, the execution identifier generated and saved locally by the terminal may also be referred to as candidate execution identifier, or available execution identifier, or candidate execution identifier, etc. In the following, in order to distinguish the execution parameters or execution identifiers carried by the execution indication information sent by the terminal from the execution parameters and / or execution identifiers generated and saved locally by the terminal, in some relevant examples involving the execution parameters and / or execution identifiers generated and saved locally by the execution terminal, they will be alternatively expressed as candidate execution parameters and / or candidate execution identifiers, but it should be understood that this alternative expression is only used to distinguish the execution parameters and execution identifiers in different stages or different processes, and is not used to limit the possible names of the execution parameters and execution identifiers.

[0072] Optionally, each candidate execution parameter may be represented by description information.

[0073] For example, the candidate execution parameter for indicating starting data transmission may be represented by any descriptive information such as "open", "switch on", "turn on", "enable", "activate", "enactivate", etc.

[0074] The candidate execution parameter for indicating closing data transmission may be represented by any description information such as "pending", "stop", "close", "disable", "disactivate", etc.

[0075] The candidate execution parameter for indicating data switching may be represented by "switch". It should be noted that the switching direction or switching mode corresponding to the candidate execution parameter for indicating data switching may be a default setting by both the terminal and the core network element, or a setting specified by the protocol.

[0076] The candidate execution parameters corresponding to each of the one or more granularities for indicating data transmission control can be represented by at least one descriptive information such as "flow", "data flow", "QoS Flow", "session", "connection", "Up", "Down", etc.

[0077] Optionally, each candidate execution identifier may be represented by various identifier values ​​or various values.

[0078] The candidate execution identifier for indicating the start of data transmission may be a first value; the candidate execution identifier for indicating the stop of data transmission may be a second value; the candidate execution identifier for indicating data switching may be a third value; the first value, the second value, and the third value are different from each other. For example, the first value may be 001, the second value may be 002, and the third value may be 003, or the first value may be 00, the second value may be 01, and the third value may be 10, and so on. All possible values ​​of the first value, the second value, and the third value are not limited or enumerated here. As long as the first value, the second value, and the third value are different from each other, they are within the scope of protection of this application. It should be pointed out that the switching direction or switching mode corresponding to the candidate execution identifier for indicating data switching may be the default of both the terminal and the core network element side, or specified by the protocol.

[0079] The candidate execution identifiers for indicating one or more granularities of data transmission control may include: candidate execution identifiers corresponding to each of the one or more granularities of data transmission control, and different granularities may have different candidate execution identifiers.

[0080] Specifically, the candidate execution identifier for indicating that data transmission control is at session granularity is the third value, the candidate execution identifier for indicating that data transmission control is at user plane connection granularity is the fourth value, the candidate execution identifier for indicating that data transmission control is at data flow granularity is the fifth value, the candidate execution identifier for indicating that data transmission control is at uplink granularity is the sixth value, and the candidate execution identifier for indicating that data transmission control is at downlink granularity is the seventh value. Among them, the third value to the seventh value are different values, for example, the third value to the seventh value can be 003, 004, 005, 006, 007, etc., respectively. It should be understood that this is only an exemplary explanation. In actual processing, as long as the specific values ​​of the execution identifiers corresponding to different granularities are different, they are within the scope of protection of this application and are not exhaustively listed or limited here.

[0081] It should be understood that one or more execution parameters and / or one or more execution identifiers generated locally on the terminal side can also be synchronized with the core network network element in a certain way. For example, they can be configured to the core network network element in a pre-configured manner, etc. In this way, both the terminal and the core network element can have the same definition for each execution parameter and / or each execution identifier. This embodiment does not limit the way in which one or more execution parameters and / or one or more execution identifiers are synchronized between the terminal and the core network element.

[0082] In some possible implementations, the terminal may first negotiate with the core network before sending the execution instruction information.

[0083] In some embodiments, before the terminal sends the execution indication information, the method further includes: the terminal sending a second request message, wherein the second request message carries at least one of the following: execution capability information, a first identifier, an association identifier, and an identifier of the first 3GPP user plane connection. Correspondingly, before the core network element receives the execution indication information, the method further includes: the core network element receiving the second request message, wherein the second request message carries at least one of the following: execution capability information, the first identifier, an association identifier, and an identifier of the first 3GPP user plane connection.

[0084] The second request message may be one of the following: a session establishment request message, a session modification request message, a connection establishment request message, a connection modification request message, a registration request message, an attach request message, or a Tracking Area Update (TAU) request message. Specifically, the session establishment (or modification) request message may be a PDU session establishment (or modification) request message. Specifically, the connection establishment (or modification) request message may be a PDN connection establishment (or modification) request message.

[0085] The second request message may be sent through the first access network device or may be sent through the first 3GPP control plane connection, wherein the first access network device corresponds to the first 3GPP user plane connection, the first 3GPP control plane connection corresponds to the first access network device, or the first 3GPP control plane connection is established through the first access network device.

[0086] It should be understood that the specific type of the second request message described above is merely an example. In actual processing, the second request message may also be of other types, which are not exhaustively listed here. It should also be noted that when the second request message is of any of the above types, the second request message may also carry parameters and / or content specified in the relevant protocol. For example, when the second request message is a session establishment request message, in addition to carrying at least one of the execution capability information, the first identifier, the association identifier, and the identifier of the first 3GPP user plane connection, the second request message may also carry content and / or parameters required to be carried by the session establishment request message specified in the relevant protocol, but this embodiment does not limit or exhaustively list them.

[0087] The execution capability information is used to indicate that the terminal supports data transmission control at one or more granularities, wherein the one or more granularities include at least one of the following: session, 3GPP user plane connection, data flow, bearer, uplink, and downlink. Here, the execution capability information may also be alternatively referred to as execution request information.

[0088] Optionally, one or more granularities may include a session, which may be a PDU session. The execution capability information may be used to indicate that the terminal supports data transmission control with a session (such as an entire PDU session) as the granularity.

[0089] Optionally, the one or more granularities may include a 3GPP user plane connection. The execution capability information may be used to indicate that the terminal supports executing data transmission control at a 3GPP user plane connection as a granularity.

[0090] In one case, the execution capability information may be used to indicate that the terminal supports executing data transmission control separately for each of multiple 3GPP user plane connections.

[0091] In one case, the second request message may carry the identifier of the first 3GPP user plane connection; accordingly, the execution capability information may be used to indicate that the terminal supports executing data transmission control on the first 3GPP user plane connection.

[0092] In another case, the execution capability information may also include at least one of the following: one or more RATs, one or more system types, and one or more network types, to indicate that the terminal supports data transmission control for user plane connections corresponding to at least one of the one or more RATs, one or more system types, and one or more network types. For example, the execution capability information may include E-UTRA and NR, and the execution capability information may be used to indicate that the terminal supports data transmission control for user plane connections corresponding to E-UTRA and NR, respectively. For example, the execution capability information may include EPS and 5GS, that is, the execution capability information may be used to indicate that the terminal supports data transmission control for user plane connections corresponding to EPS and 5GS, respectively.

[0093] Optionally, one or more granularities may include data flows and / or bearers. The data flows may refer to QoS (Quality of Service) flows.

[0094] In one case, the execution capability information may be used to indicate that the terminal supports data transmission control at a data flow granularity; and / or, the execution capability information may be used to indicate that the terminal supports data transmission control at a bearer granularity. Exemplarily, the execution capability information may be used to indicate that the terminal supports data transmission control at a data flow granularity for each 3GPP user plane connection in multiple 3GPP user plane connections; and / or, the execution capability information may be used to indicate that the terminal supports data transmission control at a bearer granularity for each 3GPP user plane connection in multiple 3GPP user plane connections.

[0095] In one case, the data flow or bearer granularity can be used together with other granularities.

[0096] Exemplarily, the one or more granularities include a 3GPP user plane connection and a data flow, or the one or more granularities include a 3GPP user plane connection and a bearer. The second request message may carry an identifier of the first 3GPP user plane connection, and the execution capability information may be used to indicate that the terminal supports executing data transmission control on the first 3GPP user plane connection at a data flow granularity, or the execution capability information may be used to indicate that the terminal supports executing data transmission control on the first 3GPP user plane connection at a bearer granularity.

[0097] The execution capability information may also include relevant information about one or more data flows, or relevant information about one or more bearers. For example, if a first 3GPP user plane connection has been established before sending the second request message, and the terminal has obtained relevant information about all data flows or all bearers corresponding to the first 3GPP user plane connection, the terminal may indicate in the execution indication information which data flow or data flows, or which bearers the terminal supports or requests to perform data transmission control on.

[0098] The related information of the one or more data streams includes related information of each data stream in the one or more data streams. The related information of each data stream may include at least one of the following: an identifier (such as an ID) of the data stream, filter information corresponding to the data stream, and the like.

[0099] The relevant information of the one or more bearers includes relevant information of each bearer in the one or more bearers. The relevant information of each bearer may include at least one of the following: an identifier of the bearer, Filter information corresponding to the bearer, and the like.

[0100] Optionally, one or more granularities may include upstream and / or downstream.

[0101] In one case, the execution capability information may be used to indicate that the terminal supports data transmission control for uplink data and / or downlink data. Here, uplink data may refer to data transmitted by all uplink data flows in all 3GPP user plane connections (or the entire PDU session) of the terminal, or data transmitted by all uplink bearers in all 3GPP user plane connections (or the entire PDU session) of the terminal; downlink data may refer to data transmitted by all downlink data flows in all 3GPP user plane connections of the terminal, or data transmitted by all downlink bearers in all 3GPP user plane connections of the terminal.

[0102] In one case, the uplink and / or downlink granularity may also be used in combination with other granularities.

[0103] Exemplarily, the uplink and / or downlink granularity is combined with at least one of the data flow and bearer granularity. The execution capability information may be used to indicate that the terminal supports data transmission control at the data flow and uplink and / or downlink granularity, and / or the execution capability information may be used to indicate that the terminal supports data transmission control at the bearer and uplink and / or downlink granularity.

[0104] Exemplarily, the uplink and / or downlink granularity is combined with the 3GPP user plane connection granularity. The execution capability information may be used to indicate that the terminal supports data transmission control for an uplink data flow and / or a downlink data flow of a first 3GPP user plane connection, and / or the execution capability information may be used to indicate that the terminal supports data transmission control for an uplink bearer and / or a downlink bearer of the first 3GPP user plane connection.

[0105] Exemplarily, the uplink and / or downlink granularity is combined with the 3GPP user plane connection granularity and the data flow granularity. The second request message may carry the identifier of the first 3GPP user plane connection, and the execution capability information may further include relevant information of one or more data flows; accordingly, the execution capability information may be used to indicate that the terminal supports uplink and / or downlink data transmission control for one or more data flows of the first 3GPP user plane connection.

[0106] Exemplarily, the uplink and / or downlink granularity is combined with the 3GPP user plane connection granularity and the bearer granularity. The second request message may carry the identifier of the first 3GPP user plane connection, and the execution capability information may further include relevant information of one or more bearers; accordingly, the execution capability information may be used to indicate that the terminal supports uplink and / or downlink data transmission control for one or more bearers of the first 3GPP user plane connection.

[0107] It should be understood that the above is only an exemplary description of the execution capability information, and does not exhaustively list or limit all possible combinations of the execution capability information at all possible granularities.

[0108] The first identifier is used to indicate at least one of the following: the terminal supports or requests to establish multiple 3GPP user plane connections, the terminal supports or requests to divert data between the multiple 3GPP user plane connections, the terminal supports or requests to migrate data between the multiple 3GPP user plane connections, and the terminal supports or requests to split data between the multiple 3GPP user plane connections.

[0109] The terminal supporting or requesting to establish multiple 3GPP user plane connections may refer to: the terminal having the capability of establishing multiple 3GPP user plane connections, and / or the terminal requesting to establish multiple 3GPP user plane connections.

[0110] The terminal supports or requests data diversion between the multiple 3GPP user plane connections, which may mean that the terminal supports or requests selection of the multiple 3GPP user plane connections for a new data flow and transmits the traffic of the data flow through the selected 3GPP user plane connection.

[0111] The terminal supports or requests data migration between the multiple 3GPP user plane connections, which may mean that the terminal supports or requests moving all traffic of an ongoing data flow from a 3GPP user plane connection corresponding to one access network to a 3GPP user plane connection corresponding to another access network.

[0112] The terminal supporting or requesting data splitting among the multiple 3GPP user plane connections may mean that the terminal supports or requests data flow traffic to be divided among the multiple 3GPP user plane connections. For example, some services of a data flow are transmitted through one 3GPP user plane connection, while other services of the same data flow are transmitted through another 3GPP user plane connection.

[0113] The association identifier is the same identifier associated with multiple 3GPP user plane connections supported or requested by the terminal. Specifically, the association identifier may refer to the same identifier corresponding to multiple 3GPP user plane connections supporting SSS of the terminal.

[0114] The identifier of the first 3GPP user plane connection and the association identifier can be combined into one parameter, for example, it can be a second identifier; the second identifier can include an association domain value and a coding domain value. The role of the association domain value can be the same as that of the association identifier, and the role of the coding domain value can be the same as that of the identifier of the first 3GPP user plane connection, which will not be repeated here.

[0115] In some embodiments, before the terminal sends the execution indication information, the process further includes: the terminal receiving a second reply message, wherein the second reply message carries execution-related parameters for the behavior that the terminal is allowed, requested, or required to execute. Correspondingly, before the core network element receives the execution indication information, the process further includes: the core network element sending the second reply message, wherein the second reply message carries execution-related parameters for the behavior that the terminal is allowed, requested, or required to execute.

[0116] Optionally, the core network element may send the second reply message after receiving the second request message and before receiving the execution instruction information. Correspondingly, the terminal may receive the second reply message after sending the second request message and before sending the execution instruction information.

[0117] Specifically, the core network element sending the second reply message may include: the core network element receiving the second request message; generating the second reply message based on at least one of the execution capability information, the first identifier, the association identifier, and the identifier of the first 3GPP user plane connection carried in the second request message; and sending the second reply message. This embodiment does not limit the specific manner in which the core network element generates the second reply message.

[0118] Furthermore, the transmission mode and message type of the second reply message and the second request message may correspond to each other. For example, the second request message is a registration request message sent by the terminal to the core network element through the first access network device, and the second reply message may be a registration reply message sent by the core network element to the terminal through the first access network device; for another example, the second request message may be a connection establishment or modification request message sent by the terminal to the core network element through the first 3GPP control plane connection, and the second reply message may be a connection establishment or modification reply message sent by the core network element to the terminal through the first 3GPP control plane connection. The various possible types and transmission modes of the second request message are the same as those in the aforementioned embodiment, so they will not be repeated.

[0119] Optionally, the core network element may send the second reply message before receiving the execution instruction information; accordingly, the terminal may receive the second reply message before sending the execution instruction information. That is, the core network element may proactively or automatically trigger the generation of execution-related parameters without receiving any one or at least one of the execution capability information, the first identifier, the association identifier, and the identifier of the first 3GPP user plane connection sent by the terminal, and send the execution-related parameters to the terminal via the second reply message.

[0120] It should be pointed out that the fact that the core network element did not receive any one or at least one of the execution capability information, the first identifier, the association identifier, and the identifier of the first 3GPP user plane connection sent by the terminal does not mean that the core network element did not receive any message sent by the terminal. For example, the core network element can still send a second reply message after receiving the request message sent by the terminal through the first 3GPP control plane connection or the first access network device, but the request message transmitted through the first 3GPP control plane connection or the first access network device only carries the content specified by the relevant protocol and does not carry any one or at least one of the following: execution capability information, the first identifier, the association identifier, and the identifier of the first 3GPP user plane connection. Among them, the type of request message transmitted by the first 3GPP control plane connection or the first access network device is similar to the aforementioned second request message and will not be repeated.

[0121] It should be noted that the behavior that the terminal is allowed, requested, or required to perform may include multiple behaviors or multiple behaviors; the multiple behaviors that the terminal is allowed, requested, or required to perform may refer to multiple data transmission control related behaviors that the terminal is allowed, requested, or required to perform. Furthermore, there is a corresponding relationship between each behavior that the terminal is allowed, requested, or required to perform and execution-related parameters. For example, if one of the behaviors that the terminal is allowed, requested, or required to perform is to enable data transmission, then the behavior of enabling data transmission has corresponding execution-related parameters; for another example, if one of the behaviors that the terminal is allowed, requested, or required to perform is to disable data transmission, then the behavior of disabling data transmission has corresponding execution-related parameters; for another example, if one of the behaviors that the terminal is allowed, requested, or required to perform is to switch data, then the behavior of switching data transmission has corresponding execution-related parameters.

[0122] Here, one or more execution parameters and / or one or more execution identifiers contained in the execution-related parameters refer to: the execution parameters and / or execution identifiers corresponding to all behaviors that the core network network element allows, requests or requires the terminal to execute, and / or the execution parameters and / or execution identifiers corresponding to the granularity of all behaviors that the core network network element allows, requests or requires the terminal to execute.

[0123] Specifically, the execution-related parameters include at least one of the following: an execution parameter for indicating the start of data transmission; an execution parameter for indicating the stop of data transmission; an execution parameter for indicating data switching; an execution flag for indicating the start of data transmission; an execution flag for indicating the stop of data transmission; an execution flag for indicating data switching; an execution parameter for indicating one or more granularities of data transmission control; and an execution flag for indicating one or more granularities of data transmission control. The description of the one or more granularities is the same as in the previous embodiment and is not repeated here.

[0124] The processing of the terminal after receiving the execution-related parameters may include: the terminal locally saves one or more execution parameters and / or one or more execution identifiers contained in the execution-related parameters. In this way, the terminal and the core network side (such as the core network element) jointly save one or more execution parameters and / or one or more execution identifiers with the same meaning or the same definition. Furthermore, when the terminal needs to send execution indication information, it can select one or more execution parameters or one or more execution identifiers from the one or more execution parameters and / or one or more execution identifiers contained in the locally saved execution-related parameters and add them to the execution indication information, so as to indicate the specific behavior and / or the target granularity of the specific behavior that the terminal requests or requires to be executed on the first 3GPP user plane connection through the execution indication information.

[0125] Exemplarily, the execution parameters contained in the execution-related parameters may also be referred to as execution candidate parameters, or available execution parameters, or candidate execution parameters, etc. Exemplarily, the execution identifier contained in the execution-related parameters may also be referred to as execution candidate identifier, or available execution identifier, or candidate execution identifier, etc. In the following, in order to distinguish the execution parameters or execution identifiers carried by the execution indication information sent by the terminal from the execution parameters and / or execution identifiers contained in the execution-related parameters, some relevant examples involving the execution parameters and / or execution identifiers contained in the execution-related parameters will be alternatively expressed as candidate execution parameters and / or candidate execution identifiers, but it should be understood that this alternative expression is only used to distinguish the execution parameters and execution identifiers in different stages or different processes, rather than to limit the possible names of the execution parameters and execution identifiers. The relevant descriptions and representations of each candidate execution parameter and each candidate execution identifier are the same as those in the aforementioned embodiment, so they will not be repeated.

[0126] Optionally, the execution-related parameters further include at least one of the following: information related to one or more data streams, and information related to one or more bearers. Specifically, when the execution-related parameters include execution identifiers and / or execution parameters for indicating one or more granularities of data transmission control, and one or more granularities include data streams and / or bearers, the execution-related parameters further include at least one of the following: information related to one or more data streams, and information related to one or more bearers.

[0127] Here, the one or more data streams included in the execution-related parameters may refer to: one or more data streams corresponding to the first 3GPP user plane connection that the network side allows / requests / requires the terminal to perform data transmission control; the one or more bearers included in the execution-related parameters may refer to: one or more bearers corresponding to the first 3GPP user plane connection that the network side allows / requests / requires the terminal to perform data transmission control. Alternatively, the one or more data streams included in the execution-related parameters may refer to: one or more data streams corresponding to each 3GPP user plane connection among multiple 3GPP user plane connections that the network side allows / requests / requires the terminal to perform data transmission control; the one or more bearers included in the execution-related parameters may refer to: one or more bearers corresponding to each 3GPP user plane connection that the network side allows / requests / requires the terminal to perform data transmission control.

[0128] That is, if the core network element instructs the network side to allow / request / require the terminal to perform data transmission control at the data flow and / or bearer granularity by executing relevant parameters, the core network element may further instruct the network side to allow / request / require the terminal to perform data transmission control by executing relevant parameters. The relevant information of each data flow and the relevant information of each bearer are the same as those in the previous embodiment and are not repeated here.

[0129] In some embodiments, the terminal and the core network side can complete the negotiation through a certain interaction. The negotiation process can be implemented by exchanging a second request message and / or a second reply message between the terminal and the core network element in the aforementioned embodiment, which is not described in detail here. For example, the terminal can complete the negotiation with the core network side and obtain the execution-related parameters before or during the process of establishing a certain 3GPP user plane connection.

[0130] In some embodiments, the terminal may negotiate with the network side (e.g., a core network element) during or before establishing each 3GPP user plane connection. In this embodiment, the terminal sends multiple second request messages to the core network element, and / or the terminal receives multiple second reply messages sent by the core network element.

[0131] Different second request messages among the multiple second request messages may be sent through different access network devices. For example, the terminal sends a second request message through the first access network device and another second request message through the second access network device; wherein, the second access network device and the first access network device have at least one different RAT, system type, and network type. It should be understood that the content types that may be carried by different second request messages may all include at least one of execution capability information, a first identifier, an association identifier, and an identifier of a 3GPP user plane connection, but the specific content carried in different second request messages may be different, for example, different second request messages may carry different identifiers of 3GPP user plane connections.

[0132] Different second reply messages among the multiple second reply messages are also sent through different access network devices, which will not be described in detail here. It should be understood that different second reply messages may all carry execution-related parameters, but the specific contents of the execution-related parameters carried by different second reply messages may be different, such as different second reply messages may carry different information about the data stream and / or the related information about the carrier.

[0133] For example, the terminal may first send a second request message (which may be a PDU session establishment request message) to the 5GS core network element through the first 3GPP control plane connection (or called the first NAS connection) of the 5GS. The second request message may carry execution capability information, a first identifier, an associated identifier, and at least one of the identifiers of the first 3GPP user plane connection. After the 5GS core network element receives the second request message, it sends a second reply message (carrying execution-related parameters) to the terminal through the first 3GPP control plane connection. Then, the terminal may send another second request message to the EPS core network element through the second 3GPP control plane connection (or called the second NAS connection) of the EPS. The message may carry execution capability information, a first identifier, an associated identifier, and at least one of the identifiers of the second 3GPP user plane connection. After receiving the second request message, the EPS core network element sends a second reply message (which may carry execution-related parameters) to the terminal through the second 3GPP control plane connection.

[0134] In some possible implementations, when the terminal needs to perform data transmission control on the first 3GPP user plane connection, the terminal may send execution indication information for instructing to perform data transmission control on the first 3GPP user plane connection.

[0135] The execution indication information includes one of the following: an execution parameter indicating the start of transmission of data related to the first 3GPP user plane connection; an execution parameter indicating the end of transmission of data related to the first 3GPP user plane connection; an execution parameter indicating the switching of data related to the first 3GPP user plane connection; an execution identifier indicating the start of transmission of data related to the first 3GPP user plane connection; an execution identifier indicating the end of transmission of data related to the first 3GPP user plane connection; an execution identifier indicating the switching of data related to the first 3GPP user plane connection.

[0136] Alternatively, the execution parameter indicating the start of data transmission related to the first 3GPP user plane connection may also be described as an execution parameter corresponding to the first 3GPP user plane connection for indicating the start of data transmission. The execution parameter indicating the stop of data transmission related to the first 3GPP user plane connection may be described as an execution parameter corresponding to the first 3GPP user plane connection for indicating the stop of data transmission. The execution parameter indicating the data switching related to the first 3GPP user plane connection may be described as an execution parameter corresponding to the first 3GPP user plane connection for indicating the data switching. The execution identifier indicating the start of data transmission related to the first 3GPP user plane connection may be described as an execution identifier corresponding to the first 3GPP user plane connection for indicating the start of data transmission. The execution identifier indicating the stop of data transmission related to the first 3GPP user plane connection may be described as an execution identifier corresponding to the first 3GPP user plane connection for indicating the stop of data transmission. The execution identifier indicating the data switching related to the first 3GPP user plane connection may be described as an execution identifier corresponding to the first 3GPP user plane connection for indicating the data switching.

[0137] It should be noted that the execution parameter or execution identifier indicating data switching related to the first 3GPP user plane connection can specifically be used to indicate a request or requirement for data transmitted through the first 3GPP user plane connection to be switched to another 3GPP user plane connection; or to request or require data transmitted through another 3GPP user plane connection to be switched to the first 3GPP user plane connection. The switching direction or switching method specifically indicated by the execution identifier or execution parameter indicating data switching corresponding to the first 3GPP user plane connection can be a default setting by both the terminal and the core network element, or a setting specified by a protocol, or an indication by the terminal.

[0138] It should also be pointed out that the above-mentioned execution parameters or execution identifiers indicating data switching related to the first 3GPP user plane connection are particularly suitable for scenarios where multiple 3GPP user plane connections that perform switching with each other have the same anchor point (Anchor). For example, when multiple 3GPP user plane connections of the terminal correspond to the same UPF anchor, data switching processing at various target granularities can be performed in these 3GPP user plane connections.

[0139] The processing of the terminal generating execution indication information may be: based on the data transmission control that needs to be performed on the first 3GPP user plane connection, the terminal selects one or more execution parameters or one or more execution identifiers from one or more locally stored execution parameters and / or one or more execution identifiers to carry or add to the execution indication information.

[0140] Among them, the one or more execution parameters and / or one or more execution identifiers stored locally may be those configured to the terminal by the core network element through execution-related parameters in the aforementioned embodiment; or, the one or more execution parameters and / or one or more execution identifiers generated locally may refer to the one or more execution parameters and / or one or more execution identifiers generated locally by the terminal in the aforementioned embodiment. In order to distinguish the execution parameters and / or execution identifiers used in different stages below, each execution parameter among all the execution parameters stored locally in the terminal is referred to as a candidate execution parameter, and each execution identifier among all the execution identifiers stored locally in the terminal is referred to as a candidate execution identifier. However, it should be understood that this alternative expression is only used to distinguish the execution parameters and execution identifiers in different stages or different processes, and is not used to limit the different contents of the execution parameters and execution identifiers.

[0141] Optionally, the terminal may further indicate, in the execution indication information, a target granularity of specific content or specific behavior to be executed for the data transmission control of the first 3GPP user plane connection.

[0142] Specifically, the execution indication information further includes one of the following: an execution parameter indicating a target granularity of data transmission control related to the first 3GPP user plane connection, and an execution identifier indicating a target granularity of data transmission control related to the first 3GPP user plane connection. The target granularity includes at least one of the following: session, 3GPP user plane connection, bearer, data flow, uplink, and downlink.

[0143] Alternatively, the execution parameter indicating the target granularity of data transmission control related to the first 3GPP user plane connection may also be described as an execution parameter corresponding to the first 3GPP user plane connection for indicating the target granularity of data transmission control. The execution identifier indicating the target granularity of data transmission control related to the first 3GPP user plane connection may also be described as an execution identifier corresponding to the first 3GPP user plane connection for indicating the target granularity of data transmission control.

[0144] For example, assuming that the terminal needs to close the data transmission of the first 3GPP user plane connection this time, the terminal can select a candidate execution identifier for indicating the closing of data transmission and a candidate execution identifier for indicating that the target granularity of data transmission control is the 3GPP user plane connection from all candidate execution identifiers, and use them as the execution identifier indicating that the transmission of data related to the first 3GPP user plane connection is closed and the execution identifier indicating that the target granularity of data transmission control related to the first 3GPP user plane connection is the 3GPP user plane connection, respectively. The execution parameter indicating the closing of data transmission related to the first 3GPP user plane connection and the execution identifier indicating that the target granularity of data transmission control related to the first 3GPP user plane connection is the user plane connection are added to the execution indication information, so that the execution indication information is used to indicate that the terminal requests or requires to close the data transmission of the first 3GPP user plane connection.

[0145] The execution instruction information may further include an identifier of the first 3GPP user plane connection to indicate that the user plane connection targeted by the terminal is specifically the first 3GPP user plane connection. It should be understood that this is merely an exemplary description. In actual processing, since the execution instruction information may be issued by the first access network device corresponding to the first 3GPP user plane connection, the execution instruction information may not need to carry the identifier of the first 3GPP user plane connection, and this embodiment does not limit this.

[0146] For example, assuming that the terminal needs to start uplink data transmission of the first 3GPP user plane connection this time, the terminal can select a candidate execution identifier for indicating the start of data transmission and a candidate execution identifier for indicating the uplink granularity from all candidate execution identifiers, as the execution identifier indicating the start of transmission of data related to the first 3GPP user plane connection and the execution identifier indicating that the target granularity of data transmission control related to the first 3GPP user plane connection is the uplink granularity, respectively, and add the execution identifier indicating the start of transmission of data related to the first 3GPP user plane connection and the execution identifier indicating that the target granularity of data transmission control related to the first 3GPP user plane connection is the uplink granularity to the execution indication information, so that the execution indication information is used to indicate that the terminal requests or requires to start uplink data transmission of the first 3GPP user plane connection.

[0147] Optionally, when the target granularity includes bearers and / or data flows, the execution indication information also includes one of the following: relevant information of one or more data flows for executing data transmission control corresponding to the first 3GPP user plane connection, and relevant information of one or more bearers for executing data transmission control corresponding to the first 3GPP user plane connection.

[0148] The relevant information of the one or more data streams and the relevant information of the one or more bearers are the same as those in the above embodiment and are not repeated here.

[0149] For example, assuming that the terminal needs to turn off the data transmission of the first QoS flow of the first 3GPP user plane connection this time, the terminal can select a candidate execution identifier for indicating the turning off of data transmission and a candidate execution identifier for indicating the data flow granularity from all candidate execution identifiers, respectively as the execution identifier indicating the turning off of data transmission related to the first 3GPP user plane connection and the execution identifier indicating that the target granularity of data transmission control related to the first 3GPP user plane connection is the data flow granularity, and add the execution identifier indicating the turning off of data transmission related to the first 3GPP user plane connection, the execution identifier indicating the target granularity of data transmission control related to the first 3GPP user plane connection is the data flow granularity, and the ID of the first QoS flow to the execution indication information, so that the execution indication information is used to indicate that the terminal requests or requires to turn off the data transmission of the first QoS flow of the first 3GPP user plane connection.

[0150] Exemplarily, assuming that the terminal needs to start downlink data transmission of the first bearer of the first 3GPP user plane connection this time, the terminal can select a candidate execution identifier for indicating the start of data transmission, a candidate execution identifier for indicating the bearer granularity, and a candidate execution identifier for indicating the downlink granularity from all candidate execution identifiers, and use them as the execution identifier indicating the start of transmission of data related to the first 3GPP user plane connection, the execution identifier indicating that the target granularity of data transmission control related to the first 3GPP user plane connection is the bearer granularity, and the execution identifier indicating that the target granularity of data transmission control related to the first 3GPP user plane connection is the downlink granularity, respectively. The execution identifier indicating the start of transmission of data related to the first 3GPP user plane connection, the execution identifier indicating that the target granularity of data transmission control related to the first 3GPP user plane connection is the bearer granularity, the execution identifier indicating that the target granularity of data transmission control related to the first 3GPP user plane connection is the downlink granularity, and the ID of the first bearer are added to the execution indication information, so that the execution indication information is used to indicate that the terminal requests or requires to start downlink data transmission of the first bearer of the first 3GPP user plane connection.

[0151] Exemplarily, assuming that the terminal needs to switch the data transmission of the first 3GPP user plane connection this time, the terminal can select a candidate execution identifier for indicating data switching and a candidate execution identifier for indicating that the target granularity of data transmission control is a 3GPP user plane connection from all candidate execution identifiers, respectively as an execution identifier indicating data switching related to the first 3GPP user plane connection and an execution identifier indicating that the target granularity of data transmission control related to the first 3GPP user plane connection is a 3GPP user plane connection, and add the execution identifier indicating data switching related to the first 3GPP user plane connection and the execution identifier corresponding to the first 3GPP user plane connection for indicating that the target granularity of data transmission control is a 3GPP user plane connection to the execution indication information, so that the execution indication information is used to indicate that the terminal requests or requires switching the data transmission of the first 3GPP user plane connection.

[0152] Optionally, the request or requirement to switch data transmission of the first 3GPP user plane connection may specifically refer to requesting or requiring that data transmitted by the first 3GPP user plane connection be switched to another 3GPP user plane connection.

[0153] In one scenario, if the current terminal has only two established 3GPP user plane connections, sending the execution instruction information can be used to indicate that data transmitted through the first 3GPP user plane connection should be switched to the other 3GPP user plane connection. That is, the execution instruction information may not carry any other content. Alternatively, the execution instruction information may further include an identifier of the first 3GPP user plane connection to explicitly instruct that data transmitted through the first 3GPP user plane connection be switched to the other 3GPP user plane connection.

[0154] In one case, if the current terminal has only established a first 3GPP user plane connection, the execution instruction information may also be used to instruct the data transmitted by the first 3GPP user plane connection to be switched to the next established 3GPP user plane connection. Furthermore, the terminal may also send a message for requesting the establishment of a second 3GPP user plane connection to establish the second 3GPP user plane connection and switch the data transmitted by the first 3GPP user plane connection to the second 3GPP user plane connection.

[0155] In one scenario, if the terminal currently has three or more 3GPP user plane connections established, the execution indication information may carry at least one of the following: an identifier of the first 3GPP user plane connection and an identifier of the target 3GPP connection for the handover process. In this way, the execution indication information may indicate that the handover process requested and required by the terminal is specifically to hand over data transmitted through the first 3GPP user plane connection to the target 3GPP user plane connection.

[0156] Optionally, the request or requirement to switch data transmission of the first 3GPP user plane connection may specifically refer to requesting or requiring data transmitted through other 3GPP user plane connections to be switched to the first 3GPP user plane connection for transmission.

[0157] In one scenario, if the current terminal has only two established 3GPP user plane connections, sending the above-mentioned execution instruction information can be used to indicate that data transmitted by the other 3GPP user plane connection is to be switched to the first 3GPP user plane connection. The execution instruction information may not carry any other content. Alternatively, the execution instruction information may further include an identifier of the first 3GPP user plane connection to explicitly instruct that data transmitted by the other 3GPP user plane connection be switched to the first 3GPP user plane connection.

[0158] In one scenario, if the terminal currently has three or more 3GPP user plane connections established, the execution indication information may carry at least one of the following: an identifier of the first 3GPP user plane connection and an identifier of the source 3GPP connection for the handover process. In this way, the execution indication information may indicate that the handover process requested and required by the terminal is specifically to hand over data transmitted via the source 3GPP user plane connection to the first 3GPP user plane connection.

[0159] It should be understood that this is merely an example. In actual processing, since the execution instruction information can be sent by the first access network device corresponding to the first 3GPP user plane connection, the execution instruction information may not need to carry the identifier of the first 3GPP user plane connection, and this embodiment is not limited thereto. In addition, the above-mentioned execution identifier can also be replaced by an execution parameter, which is not described in detail here.

[0160] For example, assuming that the terminal needs to switch the data transmission of the first QoS flow on the first 3GPP user plane connection this time, the terminal can select a candidate execution identifier for indicating data switching and a candidate execution identifier for indicating that the target granularity of data transmission control is a QoS flow from all candidate execution identifiers, and use them as the execution identifier indicating the data switching related to the first 3GPP user plane connection and the execution identifier indicating that the target granularity of data transmission control related to the first 3GPP user plane connection is a QoS flow, respectively. The execution identifier indicating the data switching related to the first 3GPP user plane connection, the execution identifier indicating that the target granularity of data transmission control related to the first 3GPP user plane connection is a QoS flow, and the relevant information of the first QoS flow are added to the execution indication information, so that the execution indication information is used to indicate that the terminal requests or requires to switch the data transmission of the first 3GPP user plane connection.

[0161] Optionally, the request or requirement to switch the data transmission of the first QoS flow of the first 3GPP user plane connection may specifically refer to requesting or requiring switching the data transmitted by the first QoS flow of the first 3GPP user plane connection to other 3GPP user plane connections.

[0162] In one case, if the current terminal has only two 3GPP user plane connections established, the execution instruction information can be sent to indicate that the data transmitted by the first QoS flow of the first 3GPP user plane connection is switched to the other 3GPP user plane connection. In other words, the execution instruction information may not carry any other content.

[0163] In one case, if the current terminal has only established a first 3GPP user plane connection, the execution instruction information may also be used to instruct the data transmitted by the first 3GPP user plane connection to be switched to the next established 3GPP user plane connection. Furthermore, the terminal may also send a message for requesting the establishment of a second 3GPP user plane connection to establish the second 3GPP user plane connection and switch the data transmitted by the first QoS flow of the first 3GPP user plane connection to the second 3GPP user plane connection.

[0164] In one scenario, if the terminal currently has three or more 3GPP user plane connections established, the execution indication information may carry at least one of the following: an identifier of the first 3GPP user plane connection and an identifier of the target 3GPP connection for the handover process. In this way, the execution indication information may indicate that the handover process requested and required by the terminal is specifically to hand over data transmitted by the first QoS flow of the first 3GPP user plane connection to the target 3GPP user plane connection.

[0165] It should be understood that this is merely an example. In actual processing, since the execution instruction information can be sent by the first access network device corresponding to the first 3GPP user plane connection, the execution instruction information may not need to carry the identifier of the first 3GPP user plane connection, and this embodiment is not limited thereto. In addition, the above-mentioned execution identifier can also be replaced by an execution parameter, which is not described in detail here.

[0166] It should also be understood that the above only illustrates the target granularity for executing data transmission control as 3GPP user plane connection and QoS flow. In actual processing, the above 3GPP user plane connection and QoS flow can also be replaced with other target granularities, or the 3GPP user plane connection and / or QoS flow granularity can also be combined with other target granularities, such as uplink, downlink and other target granularities. Various possible combinations and their related processing are not described here one by one.

[0167] After the core network element receives the execution instruction information, the further step includes: the core network element performing data transmission control on the first 3GPP user plane connection based on the execution instruction information.

[0168] Specifically, the core network network element performs data transmission control on the first 3GPP user plane connection based on the execution indication information, which may include: the core network network element performs data transmission control on the first 3GPP user plane connection based on one or more execution parameters or one or more execution identifiers corresponding to the first 3GPP user plane connection included in the execution indication information.

[0169] Exemplarily, when the execution indication information includes an execution identifier indicating that the transmission of data related to the first 3GPP user plane connection is started and an execution identifier indicating that the target granularity of the data transmission control related to the first 3GPP user plane connection is the uplink granularity, the core network element controls the start of uplink data transmission of the first 3GPP user plane connection.

[0170] Exemplarily, when the execution indication information includes an execution identifier indicating that the transmission of data related to the first 3GPP user plane connection is closed, an execution identifier indicating that the target granularity of the data transmission control related to the first 3GPP user plane connection is the data flow granularity, and the ID of the first QoS flow, the core network element controls the closing of the data transmission of the first QoS flow of the first 3GPP user plane connection.

[0171] Exemplarily, when the execution indication information includes an execution identifier indicating that the transmission of data related to the first 3GPP user plane connection is started, an execution identifier indicating that the target granularity of the data transmission control related to the first 3GPP user plane connection is the bearer granularity, an execution identifier indicating that the target granularity of the data transmission control related to the first 3GPP user plane connection is the downlink granularity, and the ID of the first bearer, the core network element controls the downlink data transmission of the first bearer of the first 3GPP user plane connection to be started.

[0172] It should be understood that the above description is merely an example using the execution identifier as an example. In actual processing, the execution identifier may also be replaced with an execution parameter, and the description will not be repeated here. It should also be understood that the above description is merely an example of several possible situations that may be requested by the execution indication information and the processing that may be performed by the core network element. In actual processing, the possible situations include but are not limited to the above, but this embodiment is not intended to be exhaustive.

[0173] In one embodiment, the execution indication information is carried by a first request message, wherein the first request message is one of the following: a session modification request message, a connection modification request message, a service request message, a registration request message, or a tracking area update request message.

[0174] Optionally, the first request message is sent through a first 3GPP control plane connection.

[0175] The first 3GPP control plane connection and the first 3GPP user plane connection may correspond to the same first access network device; or, the first 3GPP control plane connection and the first 3GPP user plane connection may correspond to different access network devices or different RATs.

[0176] Specifically, the terminal sending the execution indication information includes: the terminal sending a first request message to a core network element via a first 3GPP control plane connection, where the first request message carries the execution indication information. The core network element receiving the execution indication information includes: the core network element receiving the first request message sent by the terminal via the first 3GPP control plane connection. In this embodiment, the core network element may be a control plane element.

[0177] After the core network element receives the execution instruction information, the method further includes: the core network element sending a first reply message, wherein the first reply message carries an execution result of executing data transmission control on the first 3GPP user plane connection. Correspondingly, after the terminal sends the execution instruction information, the method further includes: the terminal receiving a first reply message, wherein the first reply message carries an execution result of executing data transmission control on the first 3GPP user plane connection.

[0178] Here, the first reply message is a reply message corresponding to the first request message. The type of the first reply message corresponds to the first request message, and the transmission method of the first reply message also corresponds to the first request message, and no repeated explanation is given.

[0179] It should be noted that, in addition to carrying execution indication information, the above-mentioned first request message may also carry content and / or parameters specified in the relevant protocol, which is not limited here; accordingly, the above-mentioned first reply message may not only carry the execution result of performing data transmission control on the first 3GPP user plane connection, but also carry content and / or parameters specified in the relevant protocol, which is not limited here.

[0180] In one embodiment, the terminal sending the execution instruction information includes one of the following: the terminal sending the execution instruction information to the first access network device corresponding to the first 3GPP user plane connection; the terminal sending the execution instruction information via the first 3GPP user plane connection. Correspondingly, the core network element receiving the execution instruction information includes one of the following: the core network element receiving the execution instruction information sent by the first access network device corresponding to the first 3GPP user plane connection; the core network element receiving the execution instruction information via the first 3GPP user plane connection.

[0181] The terminal sending the execution instruction information through the first 3GPP user plane connection may specifically refer to the terminal sending the execution instruction information to a core network element through the first 3GPP user plane connection. In this embodiment, the core network element may include a control plane network element (such as at least one of an SMF, a PCF, etc.), or the core network element may include a user plane network element (such as a UPF).

[0182] This embodiment differs from the previous embodiment in that the execution indication information in this embodiment can be carried by user plane data (or user plane data packet). Specifically, the execution indication information can be carried by uplink user plane data (or uplink user plane data packet).

[0183] For example, the terminal can place the execution indication information in a certain layer of the AS (access layer) protocol stack, such as the SDAP (Service Data Adaptation Protocol) layer, and send it to the first access network device. After identification by the first access network device, the information is placed in a GTP-U (User Plane Part of GTP (GPRS Tunnelling Protocol)) data packet or a GTP-U data packet header and sent to the user plane network element. For another example, the user plane network element can read what the terminal adds through the protocol layer between the terminal and the user plane network element (such as above the SDAP and GTP-U protocol layers); for example, the terminal transmits an uplink user plane data packet (carrying execution indication information) through the protocol layer between the terminal and the user plane network element. Accordingly, the user plane network element can directly read the execution indication information carried in the uplink user plane data packet, and then perform subsequent control processing.

[0184] In some embodiments, the terminal may send execution indication information multiple times to request data transmission control for multiple 3GPP user plane connections. Different execution indication information in the multiple sent execution indication information may be carried by different first request messages in the multiple first request messages, or may be sent by different access network devices.

[0185] In one embodiment, the terminal may establish multiple 3GPP user plane connections before sending the execution indication information, and the first 3GPP user plane connection is any one of the multiple 3GPP user plane connections established by the terminal.

[0186] When a terminal establishes multiple 3GPP user plane connections, the SUPI (SUbscription Permanent Identifier) ​​(or International Mobile Subscriber Identity (IMSI)) corresponding to different initiations of establishing 3GPP user plane connections is the same, that is, multiple 3GPP user plane connections correspond to the same USIM. Alternatively, when a terminal establishes multiple 3GPP user plane connections, the SUPI corresponding to different initiations of establishing 3GPP user plane connections is different, that is, each corresponds to a different USIM (Universal Subscriber Identity Module).

[0187] Exemplarily, the terminal may perform different data transmission controls on different 3GPP user plane connections through different execution indication information.

[0188] For example, when a terminal needs to disable data transmission for a first 3GPP user plane connection and enable data transmission for a second 3GPP user plane connection, the terminal's processing may include: sending an execution instruction message through a first access network device corresponding to the first 3GPP user plane connection, the execution instruction message carrying an execution parameter (or execution identifier) ​​corresponding to the first 3GPP user plane connection for instructing to disable data transmission; and sending another execution instruction message through a second access network device corresponding to the second 3GPP user plane connection, the execution instruction message carrying an execution parameter (or execution identifier) ​​corresponding to the second 3GPP user plane connection for instructing to enable data transmission. Accordingly, the core network element's processing may include: upon receiving the execution instruction message transmitted through the first access network device, the core network element controlling the first 3GPP user plane connection to disable data transmission; and upon receiving the execution instruction message transmitted through the second access network device, the core network element controlling the second 3GPP user plane connection to enable data transmission. In this way, by disabling all data transmission on one connection and then enabling all data transmission on another connection, the purpose of switching data flows is achieved.

[0189] For example, when the terminal needs to execute the closing of the uplink data transmission of the first data flow for the first 3GPP user plane connection and the opening of the uplink data transmission of the second data flow for the second 3GPP user plane connection, the terminal processing may include: the terminal may send an execution indication message through the first access network device corresponding to the first 3GPP user plane connection, and the execution indication message carries the execution parameter (or execution identifier) ​​corresponding to the first 3GPP user plane connection for indicating the closing of data transmission, the execution parameter (or execution identifier) ​​corresponding to the first 3GPP user plane connection for indicating that the target granularity of data transmission control is data flow and uplink, and related information of the first data flow; the terminal may send another execution indication message through the second access network device corresponding to the second 3GPP user plane connection, and the execution indication message carries the execution parameter (or execution identifier) ​​corresponding to the second 3GPP user plane connection for indicating the opening of data transmission, the execution parameter (or execution identifier) ​​corresponding to the second 3GPP user plane connection for indicating that the target granularity of data transmission control is data flow and uplink, and related information of the second data flow. Accordingly, the core network element's processing may include: upon receiving the execution instruction information transmitted via the first access network device, the core network element controlling the disabling of uplink data transmission of the first data flow of the first 3GPP user plane connection; and upon receiving the execution instruction information transmitted via the second access network device, the core network element controlling the enabling of uplink data transmission of the second data flow of the second 3GPP user plane connection. In this way, by disabling partial data transmission on one connection and enabling partial data transmission on another connection, the purpose of data flow switching is achieved.

[0190] It should be understood that the above is only an exemplary description. In actual processing, the content of the execution instruction information that may be issued for each 3GPP user plane connection includes but is not limited to the above content, but this embodiment does not list them all.

[0191] It should also be understood that when the terminal only executes data transmission control with a target granularity of uplink, the core network network element may not execute the corresponding data transmission control processing. That is, the terminal may only send execution indication information to the core network network element (which includes the execution parameters or identifiers corresponding to the first 3GPP user plane connection for indicating that the target granularity of data transmission control is uplink), and the terminal itself controls the opening or closing of the uplink data. The role of the execution indication information is to enable the core network network element to know that the first 3GPP user plane connection of the terminal has closed the uplink data transmission and the second 3GPP user plane connection has opened the uplink data transmission. That is to say, the core network network element may no longer execute the corresponding control processing.

[0192] In one embodiment, the terminal may switch all data transmitted by one access to another access, or the terminal may switch all uplink data or all downlink data transmitted by one access to another access. In this embodiment, the first request message carrying the execution indication information may include a registration request message, a service request message, a TAU request message, and the like.

[0193] When the terminal needs to execute the closing of uplink data transmission for the first 3GPP user plane connection and the opening of uplink data transmission for the second 3GPP user plane connection, the terminal's processing may include: the terminal may send an execution indication message through the first access network device corresponding to the first 3GPP user plane connection, and the execution indication message carries the execution parameter (or execution identifier) ​​corresponding to the first 3GPP user plane connection for indicating the closing of data transmission, and the execution parameter (or execution identifier) ​​corresponding to the first 3GPP user plane connection for indicating that the target granularity of data transmission control is uplink; the terminal may send another execution indication message through the second access network device corresponding to the second 3GPP user plane connection, and the execution parameter (or execution identifier) ​​corresponding to the second 3GPP user plane connection for indicating the opening of data transmission. Accordingly, the processing of the core network element may include: upon receiving the execution instruction information transmitted via the first access network device, the core network element controls the closure of all uplink data transmission of the first 3GPP user plane connection; upon receiving the execution instruction information transmitted via the second access network device, the core network element controls the closure of all uplink data transmission of the second 3GPP user plane connection. In this case, the terminal may also only send the execution instruction information to the core network element, and the terminal itself controls the opening or closing of the uplink data. The purpose of the execution instruction information is to enable the core network element to know that the first 3GPP user plane connection of the terminal has closed uplink data transmission and the second 3GPP user plane connection has opened uplink data transmission. In other words, the core network element may no longer perform the corresponding control processing.

[0194] Alternatively, when the terminal needs to execute the shutdown of downlink data transmission for the first 3GPP user plane connection and the activation of downlink data transmission for the second 3GPP user plane connection, the terminal's processing may include: the terminal may send an execution indication message through the first access network device corresponding to the first 3GPP user plane connection, and the execution indication message carries the execution parameter (or execution identifier) ​​corresponding to the first 3GPP user plane connection for indicating the shutdown of data transmission, and the execution parameter (or execution identifier) ​​corresponding to the first 3GPP user plane connection for indicating that the target granularity of data transmission control is downlink; the terminal may send another execution indication message through the second access network device corresponding to the second 3GPP user plane connection, and the execution parameter (or execution identifier) ​​corresponding to the second 3GPP user plane connection for indicating that the target granularity of data transmission control is downlink. Correspondingly, the processing of the core network network element may include: when the core network network element receives the execution indication information transmitted through the first access network device, it controls the closing of all downlink data transmission of the first 3GPP user plane connection; when the core network network element receives the execution indication information transmitted through the second access network device, it controls the opening of all downlink data transmission of the second 3GPP user plane connection.

[0195] In one embodiment, a terminal may transmit all data on only one access at a given time or time period, and then transmit all data on another access at the next time or time period. The "all data" refers to data transmitted on all PDU sessions (or the only currently established 3GPP user plane connection). Therefore, this embodiment does not distinguish between PDU session granularity and data flow granularity, and only enables and disables the entire connection.

[0196] In this embodiment, the terminal may only establish the first 3GPP user plane connection before sending the execution indication information. The first request message carrying the execution indication information may include one of a registration request message, a service request message, a TAU request message, and the like.

[0197] The processing of the terminal may include: the terminal may send an execution indication message through the first access network device corresponding to the first 3GPP user plane connection, and the execution indication message carries the execution parameter (or execution identifier) ​​corresponding to the first 3GPP user plane connection for indicating the closing of data transmission (it may also carry the execution parameter or identifier of the target granularity of the first 3GPP user plane connection as the PDU session); receive a first reply message sent by the core network network element through the first access network device, and the first reply message carries the execution result of closing all data transmitted through the first access network device; the terminal may send another execution indication message through the second access network device, and the execution indication message carries the execution parameter (or execution identifier) ​​for indicating the opening of data transmission, and then receive the first reply message sent by the core network network element through the second access network device, and the first reply message carries the execution result of opening all data transmitted through the second access network device. Accordingly, the processing of the core network network element may include: when the core network network element receives the execution indication information transmitted through the first access network device, the core network network element executes the control of closing all data transmission on the first 3GPP user plane connection, and sends a first reply message carrying the execution result of closing all data transmitted through the first access network device; when the core network network element receives the execution indication information transmitted through the second access network device, the core network network element executes the control of opening or activating all data transmission on the second 3GPP user plane connection, and sends a first reply message, which carries the execution result of opening all data transmitted through the second access network device.

[0198] It should be understood that the explanation here is only illustrative using the first 3GPP user plane connection and the second 3GPP user plane connection as examples. In actual processing, the above processing method can also be used to open or close the data transmitted by other 3GPP user plane connections (or PDU sessions) as a whole, but they will not be described one by one.

[0199] In some embodiments, the core network element may also actively trigger control of data transmission of one or more 3GPP user plane connections of the terminal.

[0200] In this embodiment, the core network element may also send execution instruction information to the terminal. The content of the execution instruction information may be similar to the content of the execution instruction information sent by the aforementioned terminal. The only difference is that the sending subject of this embodiment becomes the core network element, so it will not be repeated.

[0201] Optionally, the core network element may control the transmission of data with a target granularity of downlink. In this case, the terminal may not perform any processing and may only determine that the downlink data transmission is switched from one 3GPP user plane connection to other 3GPP user plane connections through the execution indication information sent by the core network element.

[0202] For example, assuming that the core network element needs to execute the shutdown of downlink data transmission of the first data flow for the first 3GPP user plane connection of the terminal and the activation of downlink data transmission of the second data flow for the second 3GPP user plane connection of the terminal, the processing of the core network element may include: the core network element may send an execution indication message through the first access network device corresponding to the first 3GPP user plane connection, and the execution indication message carries the execution parameter (or execution identifier) ​​corresponding to the first 3GPP user plane connection for indicating the shutdown of data transmission, the execution parameter (or execution identifier) ​​corresponding to the first 3GPP user plane connection for indicating that the target granularity of data transmission control is data flow and downlink, and related information of the first data flow; the core network element may send another execution indication message through the second access network device corresponding to the second 3GPP user plane connection, and the execution indication message carries the execution parameter (or execution identifier) ​​corresponding to the second 3GPP user plane connection for indicating the activation of data transmission, the execution parameter (or execution identifier) ​​corresponding to the second 3GPP user plane connection for indicating that the target granularity of data transmission control is data flow and downlink, and related information of the second data flow.

[0203] Optionally, the core network element may be responsible for controlling the transmission of uplink data with a target granularity. In this case, the terminal may perform corresponding processing based on the execution parameters (or execution identifier) ​​contained in the execution indication information to complete the switching of uplink data transmission from one 3GPP user plane connection to other 3GPP user plane connections.

[0204] For example, assuming that the core network element needs to execute the shutdown of uplink data transmission for the first 3GPP user plane connection of the terminal and the activation of uplink data transmission for the second 3GPP user plane connection of the terminal, the processing of the core network element may include: the core network element may send an execution indication message through the first access network device corresponding to the first 3GPP user plane connection, and the execution indication message carries the execution parameter (or execution identifier) ​​corresponding to the first 3GPP user plane connection for indicating the shutdown of data transmission, and the execution parameter (or execution identifier) ​​corresponding to the first 3GPP user plane connection for indicating that the target granularity of data transmission control is uplink; the core network element may send another execution indication message through the second access network device corresponding to the second 3GPP user plane connection, and the execution parameter (or execution identifier) ​​corresponding to the second 3GPP user plane connection for indicating the activation of data transmission, and the execution parameter (or execution identifier) ​​corresponding to the second 3GPP user plane connection for indicating that the target granularity of data transmission control is uplink. Accordingly, the processing of the terminal may include: when the terminal receives the execution indication information transmitted through the first access network device, the terminal executes the control of closing the uplink data transmission on the first 3GPP user plane connection; when the terminal receives the execution indication information transmitted through the second access network device, the terminal executes the control of opening or activating the uplink data transmission on the second 3GPP user plane connection.

[0205] It should be understood that the above is only an exemplary explanation. In actual processing, the core network element can actively trigger data transmission control for one or more other target granularities. However, as long as the data transmission control processing needs to include the control of uplink data transmission, the terminal can perform the corresponding control processing. As long as the data transmission control processing only includes the control of downlink data transmission, the terminal may not perform the corresponding processing, and they will not be elaborated here.

[0206] In some embodiments, the core network element may also receive execution instruction information from the application server, and then the core network element may control the data transmission of one or more 3GPP user plane connections of the terminal based on the execution instruction information sent by the application server.

[0207] In this embodiment, the execution instruction information sent by the application server may contain content similar to the content of the execution instruction information sent by the terminal in the aforementioned embodiment. The only difference is that the sending entity in this embodiment becomes the application server and the execution instruction information can be carried by downlink user plane data (or downlink user plane data packet). The description is not repeated here. The data transmission control performed by the core network element based on the execution instruction information is also similar to the related processing after the core network element receives the execution instruction information from the terminal in the aforementioned embodiment, and therefore is not repeated here.

[0208] Next, the implementation methods provided in this application are described with reference to a variety of examples.

[0209] In Example 1, in conjunction with Figure 7, the terminal in Figure 7 can have two USIMs, and different connection-related processes are performed through different USIMs. In the execution process illustrated in Figure 7, after the terminal completes multiple user plane connections established through multiple access points (i.e., NR base stations and E-UTRA base stations), one or more of steps 701, 702, and 703 can be executed to complete the opening and closing of data transmission in the user plane connection, or switch to other connections for transmission.

[0210] Step 701: The terminal initiates a first NAS message (such as a PDU session modification request) to the 5GC (the first NAS message may be sent through the NR base station, and the first NAS message is the first request message in the aforementioned embodiment). The first NAS message may carry an execution parameter or an execution identifier.

[0211] The execution parameters or execution identifiers may be parameters generated by the terminal itself (such as predefined parameters), or may be obtained through negotiation. This embodiment does not limit this. The possible contents of the execution parameters or execution identifiers are the same as those in the previous embodiment and will not be repeated.

[0212] Accordingly, after receiving the execution parameters, the 5GC core network element executes the behavior corresponding to the execution parameters. This is one or more combinations of the following three dimensions: opening, closing, or switching data flows (or opening, closing, or switching data transmission); opening, closing, or switching the granularity of data flows, QoS flow granularity or the entire PDU session granularity. If it is a QoS flow granularity, it can further determine which QoS flow(s) to use based on the indication in the first NAS message (such as indicating QoS flow ID or filter information); opening, closing, or switching uplink and / or downlink data flows.

[0213] Step 702: The terminal initiates a second NAS message (such as a PDN connection modification request) to the EPC (the second NAS message may be sent via the E-UTRA base station). The second NAS message may carry an execution parameter or an execution identifier.

[0214] The execution parameters or execution identifiers may be parameters generated by the terminal itself (such as predefined parameters), or may be obtained through negotiation. This embodiment does not limit this. The possible contents of the execution parameters or execution identifiers are the same as those in the previous embodiment and will not be repeated.

[0215] Accordingly, after receiving the execution parameters, the EPC core network element executes the behavior corresponding to the execution parameters. This includes one or more combinations of the following three dimensions: opening, closing, or switching a data flow; opening, closing, or switching the granularity of a data flow, a bearer granularity, or an entire PDU session granularity. If it is a bearer granularity, the granularity of the bearer(s) may be further determined based on the indication in the second NAS message; and opening, closing, or switching uplink and / or downlink data.

[0216] Step 703: The 5GC and / or EPC control plane network element automatically opens, closes, switches data transmission, etc. for one or more 3GPP user plane connections of the terminal.

[0217] In addition, FIG7 also illustrates an application server. Although the relevant processing of the application server is not involved in this example, it is shown for the sake of architectural completeness of the example and no relevant description is given.

[0218] In embodiment 2, the terminal and the core network element can trigger data transmission control through user plane messages. Specifically, the terminal carries the execution identifier and / or execution parameters through the user plane data packet, and the network element of 5GC or EPC reads and executes the corresponding actions such as opening, closing, or switching data transmission. The execution process illustrated in Figure 8 can be that when the terminal completes multiple user plane connections established through access (i.e., NR base station and E-UTRA base station), one or more of steps 801, 802, and 803 can be executed to complete the opening, closing, or switching of data transmission in the user plane connection to other connections. Specifically including:

[0219] Step 801: The terminal sends uplink user plane data to the 5GC through the NR base station. The uplink user plane data may carry execution parameters or execution identifiers.

[0220] Correspondingly, after receiving the execution parameter or execution identifier, the 5GC core network element (user plane network element) executes the behavior corresponding to the execution parameter or execution identifier, such as opening, closing, or switching the data transmission of the user plane connection. Here, the execution parameter or execution identifier can be generated locally by the terminal (predefined parameter), or can be obtained by the terminal through a negotiation process, which is not limited in this embodiment.

[0221] Step 802: The terminal initiates uplink user plane data to the EPC through the E-UTRA base station. The uplink user plane data may include an execution parameter or an execution identifier.

[0222] Accordingly, after the EPC core network element (user plane network element) receives the execution parameter or execution identifier, it executes the behavior corresponding to the execution parameter or execution identifier, such as one of opening, closing, and switching the data transmission of the user plane connection. Here, the execution parameter or execution identifier can also be generated locally by the terminal (predefined parameters), or can be obtained by the terminal through a negotiation process, which is not limited in this embodiment.

[0223] For steps 801 and 802, the terminal can place the execution parameter or execution identifier at a certain layer of the AS protocol stack, such as the SDAP layer, which is then recognized by the base station and placed in a GTP-U packet or GTP-U packet header and sent to the user plane network element. Alternatively, it can be added through the protocol layer between the UE and the user plane network element (such as above the SDAP and GTP-U protocol layers), which can be read by the user plane network element.

[0224] Step 803 (optionally): The EPC user plane network element (or 5GC user plane network element) can receive downlink user plane data from the application server, which may also carry execution parameters or execution identifiers, and then the EPC user plane network element can execute corresponding actions after receiving the execution parameters or execution identifiers.

[0225] In the process provided in this embodiment 2, the terminal may generate the execution parameter or execution identifier locally. Alternatively, the terminal may negotiate with the core network element in advance to obtain the execution parameter and / or execution identifier.

[0226] Step 803 is an optional step. For example, if the AF needs to trigger data transmission control of the user plane connection in advance of negotiation, step 803 can be executed. The execution parameters or execution identifiers carried by the AF are configured by the core network element during the negotiation process, and the AF can obtain the execution parameters or execution identifiers from the core network element side.

[0227] In embodiment 3, the terminal and the core network element need to perform a negotiation process. Specifically, with reference to FIG9 , the terminal may have two USIMs in FIG9 , and different connection-related processes are performed through different USIMs. Embodiment 3 may be used in conjunction with the aforementioned embodiment 1 or embodiment 2, for example, it may be performed before embodiment 1 or before embodiment 2. With reference to FIG9 , the negotiation process between the terminal and the core network element includes:

[0228] Step 90a1: The terminal initiates a PDU session modification / establishment request (i.e., the second request message in the aforementioned embodiment) to the 5GS core network (i.e., the core network network element) through the 5GS NAS (i.e., through the NR base station, which can be the first access network device in the aforementioned embodiment) to initiate the PDU session modification / establishment process. In addition to the existing parameters (parameters specified in the existing protocol) to establish the first 3GPP user plane connection (i.e., PDU session) in the 5GS, the PDU session modification / establishment request may also carry the following new parameters for the negotiation process:

[0229] First identification: has the ability to establish multiple user plane connections or requests to establish multiple user plane connections, and supports data steering and / or splitting and / or switching (hereinafter referred to as SSS) between multiple user plane connections, which are described as follows: Access Traffic Steering: The procedure that selects an access network for a new data flow and transfers the traffic of this data flow over the selected access network. (Access traffic steering: The process of selecting an access network for a new data flow and transmitting the traffic of this data flow over the selected access network); Access Traffic Switching: The procedure that moves all traffic of an ongoing data flow from one access network to another access network (Access traffic switching: The process of moving all traffic of an ongoing data flow from one access network to another access network); Access Traffic Splitting: The procedure that splits the traffic of a data flow across multiple access networks. When traffic splitting is applied to a data flow, some traffic of the data flow is transferred via one access and some other traffic of the same data flow is transferred via another Access traffic splitting: The process of dividing a data flow's traffic across multiple access networks. When traffic splitting is applied to a data flow, some services of the data flow are transmitted over one access, while other services of the same data flow are transmitted over another access. It should be noted that access traffic steering applies to multiple accesses.

[0230] Association ID: Supports multiple user plane connections between SSSs corresponding to the same association ID.

[0231] Connection identifier: a parameter that identifies the first 3GPP user plane connection (ie, the identifier of the first 3GPP user plane connection in the aforementioned embodiment), and different 3GPP user plane connections use different connection identifiers.

[0232] It should be noted that the association identifier and the connection identifier can be combined into one parameter such as the second identifier, the second identifier = association domain value + coding domain value, the association domain value plays the role of association identifier, and the coding domain value plays the role of identifying the specific connection.

[0233] Execution capability information (or execution request information), including at least one of the following: execution of opening and closing the data transmission of the user plane connection, execution of data transmission switching; the execution granularity is the QoS Flow granularity or the entire PDU session granularity. If it is the QoS flow granularity, it can further indicate which / which QoS flow (such as indicating the QoS flow ID, or filter information); execution for uplink (UL) and / or downlink (DL) data flow.

[0234] Step 90a2: Execute the PDU session establishment / modification process. For example, during this process, the SMF can carry new parameters to interact with the UDM / PCF to obtain the subscription and PCC rules, and can select the UPF based on these parameters.

[0235] Step 90a3: The 5GS core network element sends a PDU session establishment / modification reply message (i.e., the second reply message of the aforementioned embodiment) to the terminal.

[0236] The second reply message may carry reply parameters (execution-related parameters in the aforementioned embodiment), that is, the behavior that the network side allows / requests / requires the terminal to execute, and the reply parameters include at least one of the following: execution parameters, execution identifiers. Among them, the execution parameters include at least one of the following information: whether to turn on or off the data flow, whether to switch the data transmission; the granularity of turning on, off, and switching the data flow, the QoS Flow granularity or the entire PDU session granularity. If it is the Qos flow granularity, it can further indicate which / which QoS flows (such as indicating the QoS flow ID, or filter information); turn on, turn off, and switch the uplink and / or downlink data flow. The execution identifier is used to carry the identifier in the subsequent execution stage, and the network can execute the corresponding behavior (the specific behavior corresponding to the above three execution parameters and / or one or more combinations of behaviors in the granularity) accordingly.

[0237] Step 90b1: The terminal sends a PDN connection establishment / modification request to the EPS core network through the EPS NAS (sends a PDN connection establishment / modification request to the EPC through the E-UTRA base station) to initiate the PDN connection establishment / modification process. In addition to existing parameters, the PDN connection establishment / modification request may also carry new parameters. The new parameters are the same or similar to those in step 90a1. The control granularity should be the EPS Bearer granularity and may carry EPS Bearer ID or filter information, etc.

[0238] In this step, the PDN connection establishment / modification request sent by the terminal can be understood as the terminal sending the second request message multiple times. Step 90b1 (i.e., establishing or modifying the PDN connection during EPS online access) can be performed before step 90a1. In this case, step 90a1 can optionally carry negotiation-related parameters.

[0239] The PDN connection establishment request may be carried in the Attach or TAU process and sent to the EPC core network element.

[0240] In addition, the situations where the establishment request is initiated in steps 90a1 and 90b1 include: the SUPI (or IMSI) corresponding to the two initiations is the same, that is, they correspond to the same USIM; the SUPIs corresponding to the two initiations are different, that is, they correspond to different USIMs.

[0241] Step 90b2: Execute the PDN connection establishment / modification process. For example, during this process, the SMF can carry new parameters to interact with the UDM / PCF to obtain the subscription and PCC rules, and can select the UPF based on these parameters.

[0242] Step 90b3: The EPS core network element sends a PDN connection establishment / modification reply message (reply parameters) to the terminal. The description of the reply parameters in this step is similar to that in step 90a3 and is not repeated here.

[0243] Example 4: In the scenario of NR base station and NR base station, both base stations are connected to 5GC, which can be the same 5GC or different 5GCs, depending on the PLMN network selection, which is not limited in this embodiment. As shown in Figure 10, the two base stations can correspond to different RAT types, such as NR ground base station (NR ground access) and NR non-ground base station (such as NR satellite base station (NR satellite access)), where NR ground base station refers to a base station that uses 3GPP NR access technology to communicate with the terminal at the air interface, and NR non-ground base station (such as NR satellite base station) refers to a base station that uses 3GPP-NR-SAT access technology to communicate with the terminal at the air interface. The negotiation process in this scenario may include:

[0244] Step 100a1: The terminal initiates a PDU session modification / establishment request (i.e., the second request message in the aforementioned embodiment) to the 5GS core network (5GC) through an NR non-terrestrial base station (such as an NR satellite base station) to initiate a PDU session modification / establishment process. In addition to the existing parameters (parameters specified in the existing protocol) to establish the first 3GPP user plane connection (i.e., PDU session) in the 5GS, the PDU session modification / establishment request may also carry the following new parameters for the negotiation process. The relevant description of the new parameters is the same as that in step 90a1 and will not be repeated here.

[0245] Step 100a2: Execute the PDU session establishment / modification process. For example, during this process, the SMF can carry new parameters to interact with the UDM / PCF to obtain the subscription and PCC rules, and can select the UPF based on these parameters.

[0246] Step 100a3: The 5GS core network element sends a PDU session establishment / modification reply message (i.e., the second reply message of the aforementioned embodiment) to the terminal. The PDU session establishment / modification reply message may carry reply parameters. The relevant description of the reply parameters is the same as that in step 90a3 of the aforementioned embodiment and is not repeated here.

[0247] Steps 100b1 to 100b3 are similar to steps 100a1 to 100a3. The only difference is that the NR non-ground base station is replaced by an NR ground base station, which is not repeated here.

[0248] After completing Example 4, similar processing to that of the aforementioned Example 1 can be performed. The only difference is that the E-UTRA base station in Example 1 is replaced by an NR non-terrestrial base station, so no repeated description is given.

[0249] Alternatively, after completing Example 4, similar processing to that of the aforementioned Example 2 can be performed. The only difference is that the E-UTRA base station in Example 2 is replaced by an NR non-terrestrial base station, so no repeated description is given.

[0250] Example 5: Terminal directly triggers. In this example, the terminal directly sends NAS messages to enable and disable data transmission. The specific process is shown in Figure 11 and includes:

[0251] First, by executing the PDU session establishment process and the PDN connection establishment process, the PDU session and PDN connection have been established on 5GS and EPS.

[0252] Step 11011: The terminal initiates a first NAS message (specifically, the first NAS message may be sent through the NR base station, and the first NAS message may be the first request message in the aforementioned embodiment), such as a PDU session modification request, which includes an execution parameter or an execution identifier (i.e., execution indication information). The relevant description of the execution parameter or execution identifier is the same as that in the aforementioned embodiment and is not repeated here.

[0253] Step 11012: Based on the terminal's request, the 5GC internally decides to enable, disable, or switch transmission of the corresponding data and executes the remaining PDU session modification procedures. For example, during this process, the SMF can communicate with the UDM / PCF with new parameters to obtain the contract and PCC rules, and can select the UPF based on these parameters.

[0254] Step 11013: 5GC sends a first NAS reply message carrying an execution result, which is used to indicate whether the action requested by the terminal is executed.

[0255] Steps 11021 to 11023 are similar to steps 11011 to 11013, except that data transmission of the PDN connection is enabled or disabled. Specifically:

[0256] Step 11021: The terminal initiates a second NAS message (specifically, the second NAS message may be sent through the E-UTRA base station), such as a PDN connection modification request, which includes an execution parameter or an execution identifier (i.e., execution indication information). The relevant description of the execution parameter or execution identifier is the same as that in the previous embodiment and is not repeated here.

[0257] Step 11022: The EPC internally determines whether to enable, disable, or switch transmission of the corresponding data based on the UE's request and executes the remaining PDN connection modification procedures. For example, during this process, the SMF can carry new parameters to interact with the UDM / PCF to obtain the subscription and PCC rules, and can select the UPF based on these parameters.

[0258] Step 11023: The EPC sends a second NAS reply message carrying an execution result, which is used to indicate whether the terminal's request is executed.

[0259] In addition, steps 11021 to 11023 and steps 11011 to 11013 initiate establishment requests in situations where: the SUPI (or IMSI) corresponding to the two initiations is the same, that is, they correspond to the same USIM; or, the SUPIs corresponding to the two initiations are different, that is, they correspond to different USIMs.

[0260] Example 6: The terminal directly triggers all data flows. If the terminal transmits data on only one access at a time point, and / or the UE switches all data transmitted on the current access to another access, the following process as shown in Figure 12 can be executed:

[0261] In step 12011, the terminal sends a first NAS message (which may be a Service Request or a Registration Request message) to suspend / stop / deactivate all data corresponding to the terminal (ie, a USIM (SUPI) of the terminal).

[0262] Because it is at the terminal granularity, the execution parameters or execution flags carried in the first NAS message only need to indicate whether to open or close the data flow (in this example, close the data flow). Among them, the "all data" refers to the data transmitted on all PDU sessions. Therefore, there is no need to distinguish between PDU session granularity or QoS flow granularity, only the overall opening and closing.

[0263] In some possible examples, the execution parameter or execution identifier carried in the first NAS message may also indicate whether to enable or disable uplink and / or downlink data flows.

[0264] In this embodiment, the execution parameter or execution identifier is pre-configured / pre-defined locally by the terminal and does not require a negotiation process.

[0265] Step 12012: The 5GC executes the process of suspending (Pending), stopping (Stop), or disabling (Disable / disactive) the data transmission of the user plane connection of the terminal. Specifically, the AMF in the 5GC receives the first NAS message and sends it to the SMF. The SMF interacts with the UPF to suspend (Pending), stop, or disable / disactive) the data transmission of the user plane connection of the terminal.

[0266] Step 12013: 5GC sends a first NAS reply message to the terminal, which carries the execution result. Specifically, the execution result can be sent to the terminal by AMF.

[0267] It should be noted that due to the limited number of radio frequencies of the terminal (such as single radio capability), the terminal may initiate step 12021 before receiving the first NAS reply message.

[0268] In step 12021, the terminal sends a second NAS message (which can be a Service Request or TAU Request message) to enable / activate all data corresponding to the terminal (i.e., a USIM (SUPI) of the terminal). Due to the terminal granularity, the execution parameters or execution flags carried in the second NAS message only need to indicate whether to enable or disable the data flow (in this example, enable the data flow).

[0269] In some possible examples, the execution parameter or execution identifier carried in the second NAS message may also indicate whether to enable or disable uplink and / or downlink data flows.

[0270] Step 12022: The EPC starts / activates data transmission of the user plane connection of the terminal. Specifically, the MME in the EPC receives the second NAS message and sends it to the PGW. The PGW starts or activates data transmission of the user plane connection of the terminal.

[0271] Step 12023: The EPC sends a second NAS reply message to the terminal, which carries the execution result. Specifically, the MME can send the execution result to the UE.

[0272] The SUPIs corresponding to steps 12011 to 12013 and steps 12021 to 12023 may be the same (same USIM) or two different SUPIs (two USIMs). The enabling or disabling operations of steps 12011 to 12013 and steps 12021 to 12023 may be reversed.

[0273] Example 7: The terminal and the core network element need to perform a negotiation process and trigger data transmission control through a control plane message. Specifically, with reference to Figure 13, the following process is included:

[0274] Step 130a1: The terminal initiates a registration request (i.e., the second request message in the aforementioned embodiment) to the 5GS core network (5GC is specifically the core network element) through the NR base station. In addition to the existing parameters (parameters specified in the existing protocol), the registration request may also carry new parameters. The content of the new parameters is the same as that in the aforementioned embodiment and will not be repeated here.

[0275] Step 130a2: 5GC (such as AMF) AMF executes the registration request process and interacts with UDM, PCF, etc. to determine the response parameters.

[0276] Step 130a3: 5GC sends a registration reply message (i.e., the second reply message in the aforementioned embodiment) to the terminal, which may carry reply parameters (execution-related parameters in the aforementioned embodiment), which will not be described in detail.

[0277] Step 130b1: The terminal sends an attach request / TAU request to the EPS core network (EPC) through the E-UTRA base station. The attach request / TAU request may carry new parameters in addition to existing parameters.

[0278] Step 130b2: The EPC (eg, MME) performs an attach procedure and interacts with the HSS etc. to determine response parameters.

[0279] Step 130b3: The EPS core network element sends an attach reply / TAU reply (reply parameters) to the terminal. The description of the reply parameters in this step is similar to that in the previous embodiment and will not be repeated here.

[0280] Step 130c1: The terminal initiates a first NAS message (service request or registration request) to the 5GC. The first NAS message may carry execution parameters or execution identifiers. The execution parameters or execution identifiers may be obtained from steps 130a3 and / or 130b3, or may be parameters generated by the terminal itself (such as predefined parameters).

[0281] Step 130c2: The 5GC core network element (such as AMF) receives the first NAS message and sends it to the SMF. The SMF interacts with the UPF to suspend (Pending), stop (Stop), or deactivate (Disable / disactive) the data transmission of the user plane connection of the terminal.

[0282] Step 130c3: 5GC sends a first NAS reply message to the terminal, which carries the execution result. Specifically, the AMF can send the execution result to the terminal.

[0283] In step 130d1, the terminal sends a second NAS message (which may be a Service Request or TAU Request message) to enable / activate all data corresponding to the terminal (i.e., a USIM (SUPI) of the terminal). The execution parameter or execution flag carried in the second NAS message only needs to indicate whether to enable or disable the data flow (in this example, it only indicates enabling the data flow).

[0284] Step 130d2: The EPC performs a process of switching on / activating data transmission of the user plane connection of the terminal. Specifically, the MME in the EPC receives the second NAS message and sends it to the PGW, which switches on / turns on or activates data transmission of the user plane connection of the UE.

[0285] Step 130d3: The EPC sends a second NAS reply message to the terminal, which carries the execution result. Specifically, the MME may send the execution result to the UE.

[0286] It should be noted that Examples 6 and 7 can also be used in the scenario of NR ground base station + NR satellite base station, and will not be repeated here.

[0287] It should also be noted that some of the 5GC and EPC network elements involved in Examples 1 to 7 may be co-located or completely separate. That is, the processing flows provided in Examples 1 to 7 are applicable to either of the two possible architecture scenarios illustrated in Figures 6a and 6b.

[0288] It can be seen that by adopting the above solution, when the terminal supports establishing multiple 3GPP user plane connections, the terminal initiates data transmission control for any 3GPP user plane connection. In this way, the terminal can flexibly control data transmission of different 3GPP user plane connections when supporting 3GPP multiple user plane connections.

[0289] In addition, data transmission control for different 3GPP user plane connections not only includes opening or closing, but also further includes operations at different granularities, such as 3GPP user plane connection, session, data flow, bearer, downlink and uplink, etc., making data transmission control for different 3GPP user plane connections more flexible.

[0290] Furthermore, the terminal and the core network can negotiate in advance to obtain execution parameters or execution identifiers, so that on the basis of supporting the ability to quickly turn on or off data transmission for 3GPP user plane connections (PDU sessions, PDN connections, etc.) established for different RATs, or different systems or different networks, incompatibility issues between different RATs, or different systems or different networks are avoided.

[0291] FIG14 is a schematic diagram of the structure of a terminal according to an embodiment of the present application, including:

[0292] The first communication unit 1401 is configured to send execution indication information, wherein the execution indication information is used to instruct execution of data transmission control on a first 3GPP user plane connection, where the first 3GPP user plane connection is one of multiple 3GPP user plane connections supported by the terminal.

[0293] The data transmission control includes one of the following: turning on data transmission, turning off data transmission, and switching data transmission.

[0294] The execution indication information includes one of the following: an execution parameter indicating the start of transmission of data related to the first 3GPP user plane connection; an execution parameter indicating the end of transmission of data related to the first 3GPP user plane connection; an execution parameter indicating the switching of data related to the first 3GPP user plane connection; an execution identifier indicating the start of transmission of data related to the first 3GPP user plane connection; an execution identifier indicating the end of transmission of data related to the first 3GPP user plane connection; an execution identifier indicating the switching of data related to the first 3GPP user plane connection.

[0295] The execution indication information also includes one of the following: an execution parameter indicating the target granularity of data transmission control related to the first 3GPP user plane connection, and an execution identifier indicating the target granularity of data transmission control related to the first 3GPP user plane connection; wherein, the target granularity includes at least one of the following: session, 3GPP user plane connection, bearer, data flow, uplink, and downlink.

[0296] The execution indication information further includes one of the following: relevant information of one or more data flows for executing data transmission control corresponding to the first 3GPP user plane connection, and relevant information of one or more bearers for executing data transmission control corresponding to the first 3GPP user plane connection.

[0297] Different 3GPP user plane connections among the multiple 3GPP user plane connections correspond to at least one of the following differences: radio access technology RAT, system type, network type, and network number.

[0298] The execution indication information is carried by a first request message, wherein the first request message is one of the following: a session modification request message, a connection modification request message, a service request message, a registration request message, and a tracking area update request message.

[0299] The first request message is sent through a first 3GPP control plane connection.

[0300] The first communication unit is configured to perform one of the following: sending the execution instruction information to the first access network device corresponding to the first 3GPP user plane connection; and sending the execution instruction information through the first 3GPP user plane connection.

[0301] The first communication unit is configured to send a second request message, wherein the second request message carries at least one of the following: execution capability information, a first identifier, an association identifier, and an identifier of the first 3GPP user plane connection.

[0302] The execution capability information is used to indicate that the terminal supports data transmission control at one or more granularities.

[0303] The first identifier is used to indicate at least one of the following: the terminal supports or requests to establish multiple 3GPP user plane connections, the terminal supports or requests to divert data between the multiple 3GPP user plane connections, the terminal supports or requests to migrate data between the multiple 3GPP user plane connections, and the terminal supports or requests to split data between the multiple 3GPP user plane connections.

[0304] The association identifier is the same identifier associated with multiple 3GPP user plane connections supported or requested to be established by the terminal.

[0305] The first communication unit is configured to receive a second reply message, wherein the second reply message carries execution-related parameters of the behavior that the terminal is allowed, requested, or required to execute.

[0306] The execution-related parameters include at least one of the following: an execution parameter for indicating the start of data transmission; an execution parameter for indicating the stop of data transmission; an execution parameter for indicating data switching; an execution identifier for indicating the start of data transmission; an execution identifier for indicating the stop of data transmission; an execution identifier for indicating data switching; an execution parameter for indicating one or more granularities of data transmission control; an execution identifier for indicating one or more granularities of data transmission control.

[0307] The execution-related parameters further include at least one of the following: related information of one or more data flows, and related information of one or more bearers.

[0308] The one or more granularities include at least one of the following: session, 3GPP user plane connection, data flow, bearer, uplink, and downlink.

[0309] FIG15 is a schematic diagram of the structure of a core network element according to an embodiment of the present application, including:

[0310] The second communication unit 1501 is configured to receive execution instruction information, wherein the execution instruction information is used to instruct execution of data transmission control on a first 3GPP user plane connection of the terminal, where the first 3GPP user plane connection is one of multiple 3GPP user plane connections supported by the terminal.

[0311] The data transmission control includes one of the following: turning on data transmission, turning off data transmission, and switching data transmission.

[0312] The execution indication information includes one of the following: an execution parameter indicating the start of transmission of data related to the first 3GPP user plane connection; an execution parameter indicating the end of transmission of data related to the first 3GPP user plane connection; an execution parameter indicating the switching of data related to the first 3GPP user plane connection; an execution identifier indicating the start of transmission of data related to the first 3GPP user plane connection; an execution identifier indicating the end of transmission of data related to the first 3GPP user plane connection; an execution identifier indicating the switching of data related to the first 3GPP user plane connection.

[0313] The execution indication information also includes one of the following: an execution parameter indicating the target granularity of data transmission control related to the first 3GPP user plane connection, and an execution identifier indicating the target granularity of data transmission control related to the first 3GPP user plane connection; wherein, the target granularity includes at least one of the following: session, 3GPP user plane connection, bearer, data flow, uplink, and downlink.

[0314] The execution indication information further includes one of the following: relevant information of one or more data flows for executing data transmission control corresponding to the first 3GPP user plane connection, and relevant information of one or more bearers for executing data transmission control corresponding to the first 3GPP user plane connection.

[0315] As shown in FIG15 , the core network element further includes:

[0316] The second processing unit 1502 is configured to perform data transmission control on the first 3GPP user plane connection based on the execution instruction information.

[0317] Different 3GPP user plane connections among the multiple 3GPP user plane connections correspond to at least one of the following differences: radio access technology RAT, system type, network type, and network number.

[0318] The execution indication information is carried by a first request message, wherein the first request message is one of the following: a session modification request message, a connection modification request message, a service request message, a registration request message, and a tracking area update request message.

[0319] The first request message is received through a first 3GPP control plane connection.

[0320] The second communication unit is configured to perform one of the following: receiving the execution indication information sent by the first access network device corresponding to the first 3GPP user plane connection; and receiving the execution indication information through the first 3GPP user plane connection.

[0321] The second communication unit is configured to receive a second request message, wherein the second request message carries at least one of the following: execution capability information, a first identifier, an association identifier, and an identifier of the first 3GPP user plane connection.

[0322] The execution capability information is used to indicate that the terminal supports data transmission control at one or more granularities.

[0323] The first identifier is used to indicate at least one of the following: the terminal supports or requests to establish multiple 3GPP user plane connections, the terminal supports or requests to divert data between the multiple 3GPP user plane connections, the terminal supports or requests to migrate data between the multiple 3GPP user plane connections, and the terminal supports or requests to split data between the multiple 3GPP user plane connections.

[0324] The association identifier is the same identifier associated with multiple 3GPP user plane connections supported or requested to be established by the terminal.

[0325] The second communication unit is configured to send a second reply message, wherein the second reply message carries execution-related parameters of the behavior that the terminal is allowed, requested, or required to execute.

[0326] The execution-related parameters include at least one of the following: an execution parameter for indicating the start of data transmission; an execution parameter for indicating the stop of data transmission; an execution parameter for indicating data switching; an execution identifier for indicating the start of data transmission; an execution identifier for indicating the stop of data transmission; an execution identifier for indicating data switching; an execution parameter for indicating one or more granularities of data transmission control; an execution identifier for indicating one or more granularities of data transmission control.

[0327] The execution-related parameters further include at least one of the following: related information of one or more data flows, and related information of one or more bearers.

[0328] The one or more granularities include at least one of the following: session, 3GPP user plane connection, data flow, bearer, uplink, and downlink.

[0329] The device of the embodiment of the present application can realize the corresponding functions of each device in the aforementioned authentication method embodiment. The corresponding processes, functions, implementation methods and beneficial effects of each module (sub-module, unit or component, etc.) in the terminal or core network element can be found in the corresponding description in the above method embodiment, which will not be repeated here. It should be noted that the functions described in the terminal or each module (sub-module, unit or component, etc.) in the core network element of the embodiment of the application can be implemented by different modules (sub-modules, units or components, etc.) or by the same module (sub-module, unit or component, etc.).

[0330] Figure 16 is a schematic structural diagram of a communication device 1600 according to an embodiment of the present application. The communication device 1600 includes a processor 1610, which can retrieve and execute computer programs from a memory to enable the communication device 1600 to implement the methods according to the embodiments of the present application. In one possible implementation, the communication device 1600 may also include a memory 1620. The processor 1610 can retrieve and execute computer programs from the memory 1620 to enable the communication device 1600 to implement the methods according to the embodiments of the present application. The memory 1620 may be a separate device independent of the processor 1610 or integrated into the processor 1610. In one possible implementation, the communication device 1600 may also include a transceiver 1630. The processor 1610 may control the transceiver 1630 to communicate with other devices. Specifically, the transceiver 1630 may send information or data to other devices or receive information or data sent by other devices. The transceiver 1630 may include a transmitter and a receiver. The transceiver 1630 may further include one or more antennas.

[0331] In one possible implementation, the communication device 1600 may be a terminal or a core network element of an embodiment of the present application, and the communication device 1600 may implement the corresponding processes implemented by the terminal or the core network element in each method of the embodiment of the present application. For the sake of brevity, they will not be repeated here.

[0332] Figure 17 is a schematic structural diagram of a chip 1700 according to an embodiment of the present application. Chip 1700 includes a processor 1710, which can access and execute computer programs from a memory to implement the methods in the embodiments of the present application. In one possible implementation, chip 1700 may also include a memory 1720. Processor 1710 can access and execute computer programs from the memory 1720 to implement the methods in the embodiments of the present application performed by a terminal or a core network element. Memory 1720 may be a separate device independent of processor 1710 or integrated into processor 1710. In one possible implementation, chip 1700 may also include an input interface 1730. Processor 1710 may control input interface 1730 to communicate with other devices or chips, specifically, to obtain information or data sent by other devices or chips. In one possible implementation, chip 1700 may also include an output interface 1740. The processor 1710 may control the output interface 1740 to communicate with other devices or chips, and specifically, may output information or data to other devices or chips.

[0333] In one possible implementation, the chip can be applied to the terminal or core network element in the embodiment of the present application, and the chip can implement the corresponding processes implemented by the terminal or core network element in the various methods of the embodiment of the present application. For the sake of brevity, they are not described here. It should be understood that the chip mentioned in the embodiment 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. The processor mentioned above can be a general-purpose processor, a digital signal processor (DSP), a field programmable gate array (FPGA), an application specific integrated circuit (ASIC) or other programmable logic devices, transistor logic devices, discrete hardware components, etc. Among them, the general-purpose processor mentioned above can be a microprocessor or any conventional processor, etc. The memory mentioned above can be a volatile memory or a non-volatile memory, or can include both volatile and non-volatile memories. Among them, the non-volatile memory can 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. The volatile memory can be a random access memory (RAM). It should be understood that the above-mentioned memory is exemplary but not restrictive. For example, the memory in the embodiment of the present application can also be a static random access memory (SRAM), a dynamic random access memory (DRAM), a synchronous dynamic random access memory (SDRAM), a double data rate synchronous dynamic random access memory (DDR SDRAM), an enhanced synchronous dynamic random access memory (ESDRAM), a synchronous link dynamic random access memory (SLDRAM) and a direct memory bus random access memory (DR RAM), etc. That is, the memory in the embodiment of the present application is intended to include but is not limited to these and any other suitable types of memory.

[0334] Figure 18 is a schematic block diagram of a communication system 1800 according to an embodiment of the present application. Communication system 1800 includes a terminal 1810 and a core network element 1820. Terminal 1810 can be used to implement the corresponding functions implemented by the terminal in the above-described method. Core network element 1820 can be used to implement the corresponding functions implemented by the core network element in the above-described method. For the sake of brevity, these details are not further described here.

[0335] In the above embodiments, it can be implemented in whole or in part by software, hardware, firmware or any combination thereof. When software is used for implementation, it can be implemented in whole or in part in the form of a computer program product. The computer program product includes one or more computer instructions. When the computer program instructions are loaded and executed on a computer, the process or function in accordance with the embodiment of the present application is generated in whole or in part. The computer can be a general-purpose computer, a special-purpose computer, a computer network, or other programmable devices. The computer instructions can be stored in a computer-readable storage medium, or transmitted from one computer-readable storage medium to another computer-readable storage medium. For example, the computer instructions can be transmitted from a website, computer, server or data center by wired (such as coaxial cable, optical fiber, digital subscriber line (DSL)) or wireless (such as infrared, wireless, microwave, etc.) mode to another website, computer, server or data center. The computer-readable storage medium can be any available medium that a computer can access or a data storage device such as a server or data center that includes one or more available media integrations. The available medium may be a magnetic medium (eg, a floppy disk, a hard disk, a magnetic tape), an optical medium (eg, a DVD), or a semiconductor medium (eg, a solid state disk (SSD)).

[0336] It should be understood that in the various embodiments of the present application, the size of the sequence number of each process mentioned above does not mean the order of execution, and the execution order of each process should be determined by its function and internal logic, and should not constitute any limitation on the implementation process of the embodiment of the present application. Those skilled in the art can clearly understand that, for the convenience and brevity of description, the specific working process of the system, device and unit described above can refer to the corresponding process in the aforementioned method embodiment, and will not be repeated here. The above is only a specific implementation method of the present application, but the scope of protection of the present application is not limited thereto. Any person skilled in the art who is familiar with the technical field can easily think of changes or replacements within the technical scope disclosed in the present application, which should be included in the scope of protection of the present application. Therefore, the scope of protection of the present application should be based on the scope of protection of the claim.

Claims

1. A communication method, comprising: The terminal sends execution indication information, where the execution indication information is used to indicate performing data transmission control on a first 3GPP user plane connection, and the first 3GPP user plane connection is one of multiple 3GPP user plane connections supported by the terminal to be established.

2. The method according to claim 1, wherein The data transmission control includes one of the following: enabling data transmission, disabling data transmission, and switching data transmission.

3. The method according to claim 2, wherein, The execution indication information includes one of the following: An execution parameter indicating that data related to the first 3GPP user plane connection starts to be transmitted; An execution parameter indicating that data related to the first 3GPP user plane connection stops being transmitted; An execution parameter indicating data switching related to the first 3GPP user plane connection; An execution identifier indicating that data related to the first 3GPP user plane connection starts to be transmitted; An execution identifier indicating that data related to the first 3GPP user plane connection stops being transmitted; An execution identifier indicating data switching related to the first 3GPP user plane connection.

4. The method according to any one of claims 1 to 3, wherein, The execution indication information further includes one of the following: an execution parameter indicating the target granularity of data transmission control related to the first 3GPP user plane connection, an execution identifier indicating the target granularity of data transmission control related to the first 3GPP user plane connection; where the target granularity includes at least one of the following: session, 3GPP user plane connection, bearer, data flow, uplink, downlink.

5. The method according to any one of claims 1 to 4, wherein The execution indication information further includes one of the following: information related to one or more data flows for performing data transmission control corresponding to the first 3GPP user plane connection, information related to one or more bearers for performing data transmission control corresponding to the first 3GPP user plane connection.

6. The method according to any one of claims 1-5, wherein, Among the multiple 3GPP user plane connections, different 3GPP user plane connections correspond to at least one of the following differences: radio access technology (RAT), system type, network type, network number.

7. According to the method of any one of claims 1-6, wherein The execution indication information is carried by a first request message, where the first request message is one of the following: a session modification request message, a connection modification request message, a service request message, a registration request message, a tracking area update request message.

8. The method according to claim 7, wherein The first request message is sent through a first 3GPP control plane connection.

9. The method according to any one of claims 1 to 6, wherein The terminal sending the execution indication information includes one of the following: The terminal sends the execution indication information to a first access network device corresponding to the first 3GPP user plane connection; The terminal sends the execution indication information through the first 3GPP user plane connection.

10. The method according to any one of claims 1-9, wherein, Before the terminal sends the execution indication information, it further includes: The terminal sends a second request message, where the second request message carries at least one of the following: execution capability information, a first identifier, an associated identifier, an identifier of the first 3GPP user plane connection.

11. The method according to claim 10, wherein, The execution capability information is used to indicate that the terminal supports performing data transmission control at one or more granularities.

12. The method according to claim 10, wherein The first identifier is used to indicate at least one of the following: the terminal supports or requests to establish multiple 3GPP user plane connections, the terminal supports or requests to split data between the multiple 3GPP user plane connections, the terminal supports or requests to migrate data between the multiple 3GPP user plane connections, and the terminal supports or requests to split data between the multiple 3GPP user plane connections.

13. The method according to claim 10, wherein The associated identifier is the same identifier associated with the multiple 3GPP user plane connections supported or requested to be established by the terminal.

14. The method according to any one of claims 1-13, wherein, Before the terminal sends the execution indication information, it further includes: The terminal receives a second reply message, where the second reply message carries execution-related parameters of an action that allows or requests or requires the terminal to execute.

15. The method according to claim 14, wherein, The execution-related parameters include at least one of the following: An execution parameter for indicating to start data transmission; An execution parameter for indicating to stop data transmission; An execution parameter for indicating data handover; An execution identifier for indicating to start data transmission; An execution identifier for indicating to stop data transmission; An execution identifier for indicating data handover; An execution parameter for indicating one or more granularities of data transmission control; An execution identifier for indicating one or more granularities of data transmission control.

16. The method according to claim 15, wherein, The execution-related parameters further include at least one of the following: information related to one or more data flows, and information related to one or more bearers.

17. The method according to any one of claims 11, 15, and 16, wherein The one or more granularities include at least one of the following: session, 3GPP user plane connection, data flow, bearer, uplink, and downlink.

18. A communication method, including: A core network element receives execution indication information, where the execution indication information is used to indicate to perform data transmission control on a first 3GPP user plane connection of a terminal, and the first 3GPP user plane connection is one of the multiple 3GPP user plane connections supported to be established by the terminal.

19. The method according to claim 18, wherein, The data transmission control includes one of the following: starting data transmission, stopping data transmission, and switching data transmission.

20. The method according to claim 19, wherein, The execution indication information includes one of the following: An execution parameter for indicating to start transmission of data related to the first 3GPP user plane connection; An execution parameter for indicating to stop transmission of data related to the first 3GPP user plane connection; An execution parameter for indicating to switch data related to the first 3GPP user plane connection; An execution identifier for indicating to start transmission of data related to the first 3GPP user plane connection; An execution identifier for indicating to stop transmission of data related to the first 3GPP user plane connection; An execution identifier for indicating to switch data related to the first 3GPP user plane connection.

21. The method according to any one of claims 18 - 20, wherein The execution indication information further includes one of the following: an execution parameter for indicating a target granularity of data transmission control related to the first 3GPP user plane connection, and an execution identifier for indicating a target granularity of data transmission control related to the first 3GPP user plane connection; where the target granularity includes at least one of the following: session, 3GPP user plane connection, bearer, data flow, uplink, and downlink.

22. The method according to any one of claims 18-21, wherein, The execution indication information further includes one of the following: information related to one or more data streams for performing data transmission control corresponding to the first 3GPP user plane connection, information related to one or more bearers for performing data transmission control corresponding to the first 3GPP user plane connection.

23. The method according to any one of claims 18-22, wherein, After the core network element receives the execution indication information, it further includes: Based on the execution indication information, the core network element performs data transmission control on the first 3GPP user plane connection.

24. The method according to any one of claims 18-23, wherein, Among the multiple 3GPP user plane connections, different 3GPP user plane connections correspond to at least one of the following being different: radio access technology (RAT), system type, network type, network number.

25. The method according to any one of claims 18 - 24, wherein, The execution indication information is carried by a first request message, where the first request message is one of the following: session modification request message, connection modification request message, service request message, registration request message, tracking area update request message.

26. The method according to claim 25, wherein, The first request message is received through a first 3GPP control plane connection.

27. The method according to any one of claims 18 - 24, wherein The core network element receiving the execution indication information includes one of the following: The core network element receives the execution indication information sent by the first access network device corresponding to the first 3GPP user plane connection; The core network element receives the execution indication information through the first 3GPP user plane connection.

28. The method according to any one of claims 18-27, wherein Before the core network element receives the execution indication information, it further includes: The core network element receives a second request message, where the second request message carries at least one of the following: execution capability information, a first identifier, an association identifier, an identifier of the first 3GPP user plane connection.

29. The method according to claim 28, wherein, The execution capability information is used to indicate that the terminal supports data transmission control at one or more granularities.

30. The method according to claim 28, wherein The first identifier is used to indicate at least one of the following: the terminal supports or requests to establish multiple 3GPP user plane connections, the terminal supports or requests to perform data splitting among the multiple 3GPP user plane connections, the terminal supports or requests to perform data migration among the multiple 3GPP user plane connections, the terminal supports or requests to perform data splitting among the multiple 3GPP user plane connections.

31. The method according to claim 28, wherein The association identifier is the same identifier associated with multiple 3GPP user plane connections that the terminal supports or requests to establish.

32. The method according to any one of claims 18 - 31, wherein, Before the core network element receives the execution indication information, it further includes: The core network element sends a second reply message, where the second reply message carries execution-related parameters of the behavior that allows or requests or requires the terminal to perform The execution-related parameters include at least one of the following:

33. The method according to claim 32, wherein Execution parameters for indicating the start of data transmission; Execution parameters for indicating the end of data transmission; Execution parameters for indicating data switching; Execution identifier for indicating the start of data transmission; Execution identifier for indicating the end of data transmission; Execution identifier for indicating data switching; Execution parameters for indicating one or more granularities of data transmission control; Execution identifier for indicating one or more granularities of data transmission control. The execution-related parameters further include at least one of the following: information related to one or more data streams, information related to one or more bearers.

34. The method according to claim 33, wherein, ​ 35. The method according to any one of claims 29, 33, and 34, wherein, The one or more granularities include at least one of the following: session, 3GPP user plane connection, data flow, bearer, uplink, downlink.

36. A terminal, comprising: A first communication unit, configured to send execution indication information, where the execution indication information is used to indicate performing data transmission control on a first 3GPP user plane connection, and the first 3GPP user plane connection is one of multiple 3GPP user plane connections supported by the terminal for establishment.

37. The terminal according to claim 36, wherein, The data transmission control includes one of the following: enabling data transmission, disabling data transmission, switching data transmission.

38. The terminal according to claim 37, wherein, The execution indication information includes one of the following: execution parameters indicating that data related to the first 3GPP user plane connection starts to be transmitted; execution parameters indicating that data related to the first 3GPP user plane connection stops being transmitted; execution parameters indicating data switching related to the first 3GPP user plane connection; execution identifiers indicating that data related to the first 3GPP user plane connection starts to be transmitted; execution identifiers indicating that data related to the first 3GPP user plane connection stops being transmitted; execution identifiers indicating data switching related to the first 3GPP user plane connection.

39. The terminal according to any one of claims 36-38, wherein, The execution indication information further includes one of the following: execution parameters indicating a target granularity of data transmission control related to the first 3GPP user plane connection, execution identifiers indicating a target granularity of data transmission control related to the first 3GPP user plane connection; where the target granularity includes at least one of the following: session, 3GPP user plane connection, bearer, data flow, uplink, downlink.

40. The terminal according to any one of claims 36 - 39, wherein, The execution indication information further includes one of the following: information related to one or more data flows for performing data transmission control corresponding to the first 3GPP user plane connection, information related to one or more bearers for performing data transmission control corresponding to the first 3GPP user plane connection.

41. The terminal according to any one of claims 36-40, wherein, Among the multiple 3GPP user plane connections, different 3GPP user plane connections correspond to at least one of the following differences: radio access technology (RAT), system type, network type, network number.

42. The terminal according to any one of claims 36-41, wherein, The execution indication information is carried by a first request message, where the first request message is one of the following: session modification request message, connection modification request message, service request message, registration request message, tracking area update request message.

43. The terminal according to claim 42, wherein, The first request message is sent through a first 3GPP control plane connection.

44. The terminal according to any one of claims 36 - 41, wherein, The first communication unit is configured to perform one of the following: sending the execution indication information to a first access network device corresponding to the first 3GPP user plane connection; sending the execution indication information through the first 3GPP user plane connection.

45. The terminal according to any one of claims 36-44, wherein, The first communication unit is configured to send a second request message, where the second request message carries at least one of the following: execution capability information, a first identifier, an association identifier, an identifier of the first 3GPP user plane connection.

46. The terminal according to claim 45, wherein, The execution capability information is used to indicate that the terminal supports data transmission control at one or more granularities.

47. The terminal according to claim 45, wherein, The first identifier is used to indicate at least one of the following: the terminal supports or requests to establish multiple 3GPP user plane connections, the terminal supports or requests to perform data splitting between the multiple 3GPP user plane connections, the terminal supports or requests to perform data migration between the multiple 3GPP user plane connections, and the terminal supports or requests to perform data splitting between the multiple 3GPP user plane connections.

48. The terminal according to claim 45, wherein, The associated identifier is the same identifier associated with the multiple 3GPP user plane connections supported or requested to be established by the terminal.

49. The terminal according to any one of claims 36-48, wherein, The first communication unit is configured to receive a second reply message, where the second reply message carries execution-related parameters of an action that allows or requests or requires the terminal to perform.

50. The terminal according to claim 49, wherein, The execution-related parameters include at least one of the following: an execution parameter for indicating to start data transmission; an execution parameter for indicating to stop data transmission; an execution parameter for indicating data handover; an execution identifier for indicating to start data transmission; an execution identifier for indicating to stop data transmission; an execution identifier for indicating data handover; an execution parameter for indicating one or more granularities of data transmission control; an execution identifier for indicating one or more granularities of data transmission control.

51. The terminal according to claim 50, wherein, The execution-related parameters further include at least one of the following: information related to one or more data flows, information related to one or more bearers.

52. The terminal according to any one of claims 46, 50, and 51, wherein, The one or more granularities include at least one of the following: session, 3GPP user plane connection, data flow, bearer, uplink, downlink.

53. A core network element, comprising: A second communication unit, configured to receive execution indication information, where the execution indication information is used to indicate to perform data transmission control on a first 3GPP user plane connection of a terminal, and the first 3GPP user plane connection is one of the multiple 3GPP user plane connections supported to be established by the terminal.

54. The core network element according to claim 53, wherein, The data transmission control includes one of the following: starting data transmission, stopping data transmission, switching data transmission.

55. The core network element according to claim 54, wherein, The execution indication information includes one of the following: an execution parameter for indicating to start data transmission related to the first 3GPP user plane connection; an execution parameter for indicating to stop data transmission related to the first 3GPP user plane connection; an execution parameter for indicating data handover related to the first 3GPP user plane connection; an execution identifier for indicating to start data transmission related to the first 3GPP user plane connection; an execution identifier for indicating to stop data transmission related to the first 3GPP user plane connection; an execution identifier for indicating data handover related to the first 3GPP user plane connection.

56. The core network element according to any one of claims 53-55, wherein, The execution indication information further includes one of the following: an execution parameter for indicating a target granularity of data transmission control related to the first 3GPP user plane connection, an execution identifier for indicating a target granularity of data transmission control related to the first 3GPP user plane connection; where the target granularity includes at least one of the following: session, 3GPP user plane connection, bearer, data flow, uplink, downlink.

57. The core network element according to any one of claims 53-56, wherein, The execution indication information further includes one of the following: information related to one or more data streams for performing data transmission control corresponding to the first 3GPP user plane connection, information related to one or more bearers for performing data transmission control corresponding to the first 3GPP user plane connection.

58. The core network element according to any one of claims 53-57, wherein, The core network element further includes: A second processing unit, configured to perform data transmission control on the first 3GPP user plane connection based on the execution indication information.

59. The core network element according to any one of claims 53-58, wherein, Among the multiple 3GPP user plane connections, different 3GPP user plane connections correspond to at least one of the following being different: radio access technology (RAT), system type, network type, network number.

60. The core network element according to any one of claims 53-59, wherein, The execution indication information is carried by a first request message, where the first request message is one of the following: a session modification request message, a connection modification request message, a service request message, a registration request message, a tracking area update request message.

61. The core network element according to claim 60, wherein, The first request message is received through a first 3GPP control plane connection.

62. The core network element according to any one of claims 53-59, wherein, The second communication unit is configured to perform one of the following: receive the execution indication information sent by a first access network device corresponding to the first 3GPP user plane connection; receive the execution indication information through the first 3GPP user plane connection.

63. The core network element according to any one of claims 53-62, wherein, The second communication unit is configured to receive a second request message, where the second request message carries at least one of the following: execution capability information, a first identifier, an association identifier, an identifier of the first 3GPP user plane connection.

64. The core network element according to claim 63, wherein, The execution capability information is used to indicate that the terminal supports data transmission control at one or more granularities.

65. The core network element according to claim 63, wherein, The first identifier is used to indicate at least one of the following: the terminal supports or requests to establish multiple 3GPP user plane connections, the terminal supports or requests to perform data splitting among the multiple 3GPP user plane connections, the terminal supports or requests to perform data migration among the multiple 3GPP user plane connections, the terminal supports or requests to perform data splitting among the multiple 3GPP user plane connections.

66. The core network element according to claim 63, wherein, The association identifier is the same identifier associated with multiple 3GPP user plane connections supported or requested to be established by the terminal.

67. The core network element according to any one of claims 53-66, wherein, The second communication unit is configured to send a second reply message, where the second reply message carries execution-related parameters of an action allowed or requested or required to be performed by the terminal.

68. The core network element according to claim 67, wherein The execution-related parameters include at least one of the following: execution parameters for indicating to start data transmission; execution parameters for indicating to stop data transmission; execution parameters for indicating data switching; execution identifiers for indicating to start data transmission; execution identifiers for indicating to stop data transmission; execution identifiers for indicating data switching; execution parameters for indicating one or more granularities of data transmission control; execution identifiers for indicating one or more granularities of data transmission control.

69. The core network element according to claim 68, wherein, The execution-related parameters further include at least one of the following: information related to one or more data streams, information related to one or more bearers.

70. The core network element according to any one of claims 64, 68, and 69, wherein, The one or more granularities include at least one of the following: session, 3GPP user plane connection, data stream, bearer, uplink, downlink.

71. A terminal, comprising: A transceiver, a processor, and a memory for storing a computer program, the transceiver for communicating with other devices, and the processor for invoking and running the computer program stored in the memory, so that the terminal executes the method according to any one of claims 1 to 17.

72. A core network element, comprising: A transceiver, a processor, and a memory for storing a computer program, the transceiver for communicating with other devices, and the processor for invoking and running the computer program stored in the memory, so that the core network element executes the method according to any one of claims 18 to 35.

73. A chip, comprising: A processor for invoking and running a computer program from a memory, such that a device installed with the chip executes the method according to any one of claims 1 to 17 or claims 18 to 35.

74. A computer-readable storage medium for storing a computer program, which when run by a device causes the device to execute the method according to any one of claims 1 to 17 or claims 18 to 35.

75. A computer program product comprising computer program instructions that cause a computer to execute the method according to any one of claims 1 to 17 or claims 18 to 35.

76. A computer program that causes a computer to execute the method according to any one of claims 1 to 17 or claims 18 to 35.

Images