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: on the basis of description information of a first service data flow, a terminal determining that an uplink data packet belongs to the first service data flow, wherein the description information of the first service data flow comprises at least one of the following: an identifier of the first service data flow, and an identifier of a first device; and the terminal transmitting the uplink data packet to a first core network element.

Description

Communication method and device Technical Field The present application relates to the field of communications, and more specifically, to a communication method, a device, a computer-readable storage medium, a computer program product, and a computer program. Background Art The existing technology requires that the devices in the 3GPP (3rd Generation Partnership Project) network support the configuration of filters for service data flows based on various transmission protocols, and parse and identify the data packet headers using various transmission protocols, so as to control the transmission of service data flows. However, with the development of various network applications such as the Internet and the Internet of Things, some data packets may be transmitted using transmission protocols other than those supported by the current 3GPP network, or various devices may access the network and transmit data through the same terminal. In these cases, since the 3GPP network cannot distinguish between data of different service types and / or different devices, there will be a problem of being unable to perform accurate or detailed transmission control. Summary of the invention Embodiments of the present application provide a communication method, a device, a computer-readable storage medium, a computer program product, and a computer program. The present application provides a communication method, including: The terminal determines, based on the description information of the first service data flow, that the uplink data packet belongs to the first service data flow, wherein the description information of the first service data flow includes at least one of the following: an identifier of the first service data flow and an identifier of the first device; The terminal transmits the uplink data packet to the first core network element. The present application provides a communication method, including: The first core network element receives the data packet; The first core network element determines, based on the description information of the first service data flow, that the data packet belongs to the first service data flow, wherein the description information of the first service data flow includes at least one of the following: an identifier of the first service data flow and an identifier of the first device; The first core network element transmits the data packet. The present application provides a communication method, including: The terminal transmits an uplink data packet through a first tunnel, wherein a header of the uplink data packet carries description information of the first tunnel, and the first tunnel is a tunnel between the terminal and a first core network element. The present application provides a communication method, including: The first core network element receives an uplink data packet, wherein a header of the uplink data packet carries description information of a first tunnel, and the first tunnel is a tunnel between a terminal and the first core network element; The first core network element transmits the uplink data packet through a second tunnel, wherein a header of the uplink data packet carries description information of the second tunnel, and the second tunnel is a tunnel between the first core network element and an application server. The present application provides a communication method, including: The first core network element receives a downlink data packet, wherein a header of the downlink data packet carries description information of a second tunnel, and the second tunnel is a tunnel between the first core network element and an application server; The first core network element transmits a downlink data packet through a first tunnel, wherein a header of the downlink data packet carries description information of the first tunnel, and the first tunnel is a tunnel between a terminal and the first core network element. An embodiment of the present application provides a terminal, including: A first processing unit, configured to determine, based on description information of a first service data flow, that an uplink data packet belongs to the first service data flow, wherein the description information of the first service data flow includes at least one of the following: an identifier of the first service data flow and an identifier of a first device; The first communication unit is used to transmit the uplink data packet to the first core network element. The embodiment of the present application provides a first core network element, including: A second communication unit, configured to receive a data packet and transmit the data packet; The second processing unit is used to determine that the data packet belongs to the first business data flow based on the description information of the first business data flow, wherein the description information of the first business data flow includes at least one of the following: an identifier of the first business data flow and an identifier of the first device. An embodiment of the present application provides a terminal, including: The first communication unit is used to transmit an uplink data packet through a first tunnel, wherein a header of the uplink data packet carries description information of the first tunnel, and the first tunnel is a tunnel between the terminal and a first core network element. The embodiment of the present application provides a first core network element, including: The second communication unit is configured to receive an uplink data packet, wherein the header of the uplink data packet carries description information of a first tunnel, and the first tunnel is a tunnel between the terminal and the first core network element; transmit the uplink data packet through the second tunnel, wherein the The header of the uplink data packet carries description information of the second tunnel, where the second tunnel is a tunnel between the first core network element and the application server. The embodiment of the present application provides a first core network element, including: The second communication unit is used to receive a downlink data packet, wherein the header of the downlink data packet carries description information of a second tunnel, and the second tunnel is a tunnel between the first core network element and the application server; and transmit a downlink data packet through the first tunnel, wherein the header of the downlink data packet carries description information of the first tunnel, and the first tunnel is a tunnel between a terminal and the first core network element. The embodiment of the present application provides a terminal, including: 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. The embodiment of the present application provides a first 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 run the computer program stored in the memory, so that the first core network element executes the above method. The embodiment of the present application provides a chip for implementing the above method. 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. 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. An embodiment of the present application provides a computer program product, including computer program instructions, which enable a computer to execute the above method. An embodiment of the present application provides a computer program, which, when executed on a computer, enables the computer to execute the above method. By adopting the solution provided by this embodiment, by adding at least one of the identifier of the first service data flow and the identifier of the first device to the description information of the first service data flow, when transmitting a data packet, the description information of the data packet and the first service data flow can be matched to determine the service data flow to which the data belongs, so that the transmission control of the data packet based on the service data flow to which the data packet belongs can be realized. In this way, for the case of a transmission protocol (unstructured data) that cannot be recognized by the 3GPP network, or for the case where an application packages multiple service flows together and encrypts them for transmission, or for the case where multiple devices access the network through the same terminal, the network (such as the operator network) can distinguish the service data flow to which the data packet belongs and control it by configuring the identifier of the service data flow and / or the identifier of the device, thereby ensuring the accuracy of transmission control. BRIEF DESCRIPTION OF THE DRAWINGS FIG. 1 is a schematic diagram of an application scenario according to an embodiment of the present application. Figure 2 is a schematic diagram of a scenario based on the 5G network system architecture. FIG3 is a schematic diagram of another scenario based on the 5G network system architecture. FIG4 is a schematic flowchart of a communication method according to an embodiment of the present application. FIG5 is a schematic flowchart of a communication method according to another embodiment of the present application. FIG6 is an exemplary flowchart of a communication method according to an embodiment of the present application. FIG. 7 is a schematic flowchart of a communication method according to yet another embodiment of the present application. FIG8 is a schematic flowchart of a communication method according to yet another embodiment of the present application. FIG. 9 is a schematic flowchart of a communication method according to another embodiment of the present application. FIG. 10 is another exemplary flowchart of a communication method according to an embodiment of the present application. FIG. 11 is a schematic diagram of a scenario for establishing a tunnel according to an embodiment of the present application. FIG12 is a schematic block diagram of a terminal according to an embodiment of the present application. FIG13 is a schematic block diagram of a first core network element according to an embodiment of the present application. FIG14 is a schematic block diagram of a communication device according to an embodiment of the present application. FIG. 15 is a schematic block diagram of a chip according to an embodiment of the present application. FIG. 16 is a schematic block diagram of a communication system according to an embodiment of the present application. DETAILED DESCRIPTION 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. 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-based access to 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) system. System, UMTS), Wireless Local Area Networks (WLAN), Wireless Fidelity (WiFi), fifth-generation communication (5th-Generation, 5G) system or other communication systems, etc. Generally speaking, the number of connections supported by traditional communication systems is limited and easy to implement. However, with the development of communication technology, mobile communication systems will not only support traditional communications, but 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, etc. The embodiments of the present application can also be applied to these communication systems. In one possible implementation, the communication system in the embodiment of the present application can be applied to a carrier aggregation (CA) scenario, a dual connectivity (DC) scenario, and a standalone (SA) networking scenario. In one possible implementation, the communication system in the embodiment of the present application can be applied to an unlicensed spectrum, wherein the unlicensed spectrum can also be considered as a shared spectrum; or, the communication system in the embodiment of the present application can also be applied to an authorized spectrum, wherein the authorized spectrum can also be considered as a non-shared spectrum. The embodiments of the present application describe various embodiments in combination with network devices and terminal devices, wherein the terminal device may also be referred to as user equipment (UE), access terminal, user unit, user 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 function, a computing device or other processing device connected to a wireless modem, a vehicle-mounted device, a wearable device, a terminal device in a next-generation communication system such as an NR network, or a terminal device in a future-evolved Public Land Mobile Network (PLMN) network, etc. In the 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 ships, etc.); it can also be deployed in the air (such as airplanes, balloons and satellites, etc.). In the 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 smart grid, a wireless terminal device in transportation safety, a wireless terminal device in smart city, or a wireless terminal device in smart home, etc. As an example and not a limitation, in the embodiment of the present application, the terminal device can also be a wearable device. Wearable devices can also be called wearable smart devices. They are a general term for wearable devices that use wearable technology to intelligently design and develop wearable devices for daily wear, such as glasses, gloves, watches, clothing and shoes. Wearable devices are portable devices that are worn directly on the body or integrated into the user's clothes or accessories. Wearable devices are not just hardware devices, but also realize powerful functions through software support, data interaction, and cloud 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. In an embodiment of the present application, a network device may be a device for communicating with a mobile device, and the network device may be an access point (AP) in a WLAN, a base station (BTS) in a GSM or CDMA, or a base station (NodeB, NB) in a WCDMA, or 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, and 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, etc. As an example and not a limitation, in an embodiment of the present application, a 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, a 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 communicates with the network device through the transmission resources (e.g., frequency domain resources, or spectrum resources) used by the cell. The cell may be a cell corresponding to the network device (e.g., 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: a metro cell, a micro cell, a pico cell, a femto cell, etc. These small cells have the characteristics of small coverage and low transmission power, and are suitable for providing high-speed data transmission services. FIG1 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 the 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 the embodiment of the present application. Among them, the network device may include an access network device and a core network device. That is, the wireless communication system also includes a device for communicating with the access network device. Multiple core networks for communication. 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-micro base station, access point (AP), transmission point (TP) or new generation Node B (gNodeB), etc. 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 device with communication function in the network / system in the embodiment of the present application may be referred to as a communication device. Taking the communication system shown in Figure 1 as an example, the communication equipment may include network equipment and terminal equipment with communication function, and 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. In order to facilitate understanding of the embodiments of the present application, the basic processes and basic concepts involved in the embodiments of the present application are briefly described below. It should be understood that the basic processes and basic concepts introduced below do not limit the embodiments of the present application. The 5G network system architecture diagram is shown in Figures 2 and 3. Figure 2 shows that the core network elements are connected to each other through agreed interfaces, and Figure 3 shows that the core network elements interact by calling the services provided by the network elements. Specifically, Figures 2 and 3 show that the UE connects to the (R)AN (Radio Access Network) through the Uu port, exchanges access layer messages and transmits wireless data; the UE connects to the AMF (Access and Mobility Management Function) through the N1 port to connect to the NAS (Non-Access Stratum) and exchange NAS messages. In Figures 2 and 3, AMF is the mobility management function in the core network, and SMF (Session Management Function) is the session management function in the core network. In addition to mobility management of the UE, AMF is also responsible for forwarding session management related messages between the UE and SMF. PCF (Policy Control Function) is the policy management function in the core network, responsible for formulating policies related to mobility management, session management, billing, etc. for the UE. UPF (User Plane Function) is a user plane function in the core network, which transmits data with the external data network through the N6 interface and with the (R)AN through the N3 interface. Furthermore, FIG3 also illustrates that AMF interacts by calling the Namf service, PCF interacts by calling the Npcf service, SMF interacts by calling the Nsmf service, and AF interacts by calling the Naf service. In related technologies, 5G networks perform QoS control based on QoS flow granularity, and a QoS flow can include multiple service data flows. For downlink data packets (such as downlink data packets from the DN (Data Network) shown in Figure 2 or Figure 3), the UPF matches the received downlink data packets with the service data flow filter to determine the QoS (Quality of Service) flow to which the service data flow belongs, so that the network performs QoS control on the QoS flow. For uplink data packets, the UE matches the uplink data packets to be sent with the service data flow filter to determine the QoS flow to which the service data flow belongs, so that the network performs QoS control on the QoS flow. Among them, the business data flow filter can be a packet header field in IP (Internet Protocol) or TCP (Transmission Control Protocol), for example, including information such as IP address, port number, etc.; and / or, the business data flow filter can include a field in the MAC protocol packet header, for example, including information such as MAC address. Furthermore, the specific contents of the service data flow filter (or data packet filter, or data packet filter set) currently defined by the 3GPP protocol are as follows: IP Packet Filter Set. For IP PDU Session Type, the Packet Filter Set shall support Packet Filters based on at least any combination of: Source / destination IP address or IPv6 prefix; Source / destination port number; Protocol ID of the protocol above IP / Next header type; Type of Service (TOS) (IPv4) / Traffic class (IPv6) and Mask; Flow Label (IPv6); Security parameter index; Packet Filter direction. Ethernet Packet Filter Set. For Ethernet PDU Session Type, the Packet Filter Set shall support Packet Filters based on at least any combination of: Source / destination MAC address; IEEE 802.3

[0131] Ethertype as defined in IEEE 802.3

[0131] ; Customer-VLAN tag (C-TAG) and / or Service-VLAN tag (S-TAG) VID fields as defined in IEEE Std 802.1Q

[0098] ; Customer-VLAN tag (C-TAG) and / or Service-VLAN tag (S-TAG) PCP / DEI fields as defined in IEEE Std 802.1Q

[0098] ; IP Packet Filter Set, in the case that Ethertype indicates an IPv4 / IPv6 payload Ethertype indicates IPv4 / IPv6 payload); Packet Filter direction. From the above description, it can be seen that the prior art requires that the devices in the 3GPP (3rd Generation Partnership Project) network support the configuration of filters for service data flows based on IP protocol / TCP protocol / MAC protocol, and parse and identify the data packet headers using transmission protocols such as IP protocol / TCP protocol / MAC address, so as to perform QoS control on the service data flow. However, with the development of applications in various networks such as the Internet and the Internet of Things, some data packets may use transmission protocols other than IP / TCP / MAC that are currently unrecognizable by the 3GPP network (called unstructured data in the 3GPP network), and some applications package multiple service flows together and encrypt them for transmission. In some scenarios, various tethered devices (such as wearable devices, notebooks, etc.) access the network through the same UE, and the UE packages data from multiple devices together and transmits them through the same set of IP five-tuples. In these cases, the 3GPP network cannot distinguish data of different service types and different tethered devices, so it can only provide the same quality of service in general, and cannot distinguish the refined quality of service, which will affect the user experience. 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 only a description of the association relationship of associated objects, indicating that there can be three relationships. 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 with each other are in an "or" relationship. It should be understood that the "indication" mentioned in the embodiments of the present 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 the present application, the term "correspondence" can mean that there is a direct or indirect correspondence relationship between the two, or it can mean that there is an association relationship between the two, or it can mean that there is an indication and being indicated, configuration and being configured, etc. To facilitate understanding of the technical solutions of the embodiments of the present application, the relevant technologies of the embodiments of the present application are described below. The following related technologies can be arbitrarily combined with the technical solutions of the embodiments of the present application as optional solutions, and they all belong to the protection scope of the embodiments of the present application. Fig. 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. S410. The terminal determines that the uplink data packet belongs to the first service data flow based on the description information of the first service data flow, wherein the description information of the first service data flow includes at least one of the following: an identifier of the first service data flow and an identifier of the first device; S420. The terminal transmits the uplink data packet to the first core network element. Fig. 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. S510, a first core network element receives a data packet; S520. The first core network element determines that the data packet belongs to the first service data flow based on the description information of the first service data flow, wherein the description information of the first service data flow includes at least one of the following: an identifier of the first service data flow and an identifier of the first device; S530. The first core network element transmits the data packet. Here, the first core network element may include a user plane element, and illustratively, the user plane element may include a UPF. It should be understood that the above is only an exemplary description, and in actual processing, the first core network element is not limited to the UPF listed above, and all possible elements of the first core network element are not exhaustively listed here. The first device may be one of one or more electronic devices that transmit data through a terminal. Specifically, the first device is a device that transmits data or data packets of a first service data flow through a terminal. Among them, any electronic device that transmits data through the terminal may be: an electronic device that accesses the network through the terminal and sends uplink data packets through the terminal and / or receives downlink data packets through the terminal. Exemplarily, any electronic device that transmits data through a terminal may be referred to as a tethered device, or may be referred to as any tethered device associated with the terminal; the first device may be one of the one or more tethered devices associated with the terminal. For example, the terminal may be a mobile phone, and the one or more tethered devices associated with the mobile phone may include at least one of the following: one or more wearable devices associated with the mobile phone, one or more notebooks associated with the mobile phone, etc.; the first device may be a wearable device or a notebook associated with the mobile phone, etc. In some possible implementations, before the terminal and the first core network network element transmit uplink data packets and / or transmit downlink data packets of the first service data flow, the terminal and the first core network network element need to obtain a filter of the first service data flow, wherein the filter of the first service data flow includes description information of the first service data flow. Specifically, before the terminal determines that the uplink data packet belongs to the first service data flow based on the description information of the first service data flow, the method may further include: the terminal receives a filter for the first service data flow sent by the second core network network element. Before the first core network element receives the data packet, the method may also include: the first core network element receives a filter for the first service data flow sent by the second core network element, wherein the filter for the first service data flow includes description information of the first service data flow. Correspondingly, the processing of the second core network element may include: the second core network element sends the filter of the first service data flow to the terminal; the second core network element sends the filter of the first service data flow to the first core network element. The second core network element sends the filter of the first service data flow to the terminal at a time when the second core network element sends the filter of the first service data flow to the terminal, and the second core network element sends the filter of the first service data flow to the terminal at a time when the second core network element sends the filter of the first service data flow to the terminal The timing at which the first core network element sends the filter for the first service data flow may be the same or different. The second core network element may include at least one of the following: a mobility management element, a session management element, and a policy control element. The mobility management element may include an AMF; the session management element may include an SMF; and the policy control element may include a PCF. In some embodiments, the second core network element may obtain the filter of the first service data flow from the terminal or application function (AF) before sending the filter of the first service data flow to the terminal and sending the filter of the first service data flow to the first core network element. Optionally, before the terminal determines that the uplink data packet belongs to the first service data flow based on the description information of the first service data flow, the method further includes: the terminal sends a transmission request message of the first service data flow to the second core network network element, and the transmission request message carries the filter of the first service data flow. Correspondingly, before the second core network element sends the filter of the first service data flow to the terminal and sends the filter of the first service data flow to the first core network network element, the method may include: the second core network network element receives a transmission request message sent by the terminal, and the transmission request message carries the filter of the first service data flow. In this case, before the terminal sends the transmission request message of the first service data flow to the second core network element, the method may further include: synchronizing a filter of the first service data flow between the terminal and the AF. Optionally, the processing of AF may include: AF sends a transmission request message of the first service data flow to the second core network network element, and the transmission request message carries the filter of the first service data flow. That is to say, before the second core network element sends the filter of the first service data flow to the terminal and sends the filter of the first service data flow to the first core network network element, it may include: the second core network element receives the transmission request message sent by AF, and the transmission request message carries the filter of the first service data flow. In this case, before the AF sends the transmission request message of the first service data flow to the second core network element, the method may further include: synchronizing a filter of the first service data flow between the terminal and the AF. In some embodiments, the filter of the first service data stream includes at least description information of the first service data stream, that is, the filter of the first service data stream includes at least one of the following: an identifier of the first service data stream, an identifier of the first device. In this case, the filter of the first service data stream synchronized between the terminal and the AF may include at least one of the following: an identifier of the first service data stream synchronized between the terminal and the AF; an identifier of the first device synchronized between the terminal and the AF. Furthermore, the filter of the first service data stream may include, in addition to the description information of the first service data stream, a filter field defined by a related protocol corresponding to the first service data stream; wherein the filter field defined by the related protocol may include at least one of the following: an IP address, a port number, a MAC address, etc. In this case, the processing of the filter of the first service data stream synchronized between the terminal and the AF may include, in addition to the identifier of the first service data stream synchronized between the terminal and the AF and / or the identifier of the first device synchronized between the terminal and the AF, further include: a filter field defined by a related protocol corresponding to the first service data stream synchronized between the terminal and the AF. It should be understood that this is only an exemplary description. In actual processing, the filter of the first business data stream may also include more other content or more types of fields, but this embodiment is not exhaustive. As long as the filter of the first business data stream includes the description information of the first business data stream, it is within the protection scope of this embodiment. In one embodiment, synchronizing the identifier of the first service data flow between the terminal and the AF may include: the AF assigning the identifier of the first service data flow; and the AF interacting with the terminal through the application layer to synchronize the identifier of the first service data flow to the terminal. Optionally, the identifier of the first service data flow may be the same as the flow identifier of the first service data flow in the upper layer protocol. Taking the upper layer protocol corresponding to the first business data flow as a transmission protocol (unstructured data) that cannot be recognized by the 3GPP network, such as the QUIC (Quick UDP Internet Connection) protocol as an example, the AF can take the stream id (stream identifier) ​​of the first business data flow in the QUIC protocol as the identifier of the first business data flow; then the AF can interact with the terminal through the application layer to synchronize the identifier of the first business data flow to the terminal. Optionally, the identifier of the first service data flow may be different from the flow identifier of the first service data flow in the upper layer protocol, and there is a corresponding relationship between the identifier of the first service data flow and the flow identifier of the first service data flow in the upper layer protocol. Synchronizing the identifier of the first business data flow between the terminal and the AF may include: the AF assigning the identifier of the first business data flow, and determining the correspondence between the identifier of the first business data flow and the flow identifier of the first business data flow; the AF may interact with the terminal through the application layer, and synchronize with the terminal the identifier of the first business data flow, the correspondence between the flow identifier of the first business data flow and the identifier of the first business data flow. Still taking the QUIC protocol as an example, assuming that the stream id (stream identifier) ​​of the first business data stream in the QUIC protocol is "001", the AF can assign the identifier of the first business data stream as "a1", and the AF can determine the correspondence between the stream identifier of the first business data stream and the identifier of the first business data stream. In this case, the AF can interact with the terminal through the application layer to synchronize the identifier of the first business data stream to the terminal, and the AF will also synchronize the correspondence between the stream id (stream identifier) ​​of the first business data stream and the identifier of the first business data stream with the terminal. In one embodiment, synchronizing the identifier of the first service data flow between the terminal and the AF may include: the terminal allocating the identifier of the first service data flow; and the terminal interacting with the AF through the application layer to synchronize the identifier of the first service data flow to the AF. Optionally, the identifier of the first service data flow may be the same as the flow identifier of the first service data flow in the upper layer protocol. In this example, the way in which the terminal allocates the identifier of the first service data flow is similar to the way in which the AF allocates the identifier of the first service data flow in the aforementioned example. No repetitive explanation is given. Optionally, the identifier of the first service data flow may be different from the flow identifier of the first service data flow in the upper layer protocol, and there is a correspondence between the identifier of the first service data flow and the flow identifier of the first service data flow in the upper layer protocol. In this example, the manner in which the terminal allocates the identifier of the first service data flow and the correspondence between the identifier and the flow identifier of the first service data flow are similar to the description of the manner in which the terminal allocates the identifier of the first service data flow and the correspondence between the identifier and the flow identifier of the first service data flow in the aforementioned example AF, and no repeated description is given. It should be noted that the synchronization of the identifier of the first business data stream between the terminal and the AF in the aforementioned embodiments may include: synchronizing the identifier of each business data stream in one or more business data streams between the terminal and the AF, wherein the one or more business data streams include the first business data stream. Here, the identifier of each business data stream in all business data streams may be allocated and synchronized between the terminal and the AF at one time; or, the identifier of each business data stream may be allocated and synchronized between the terminal and the AF separately. It should be understood that whether the identifiers of all business data streams are allocated and synchronized between the terminal and the AF at one time, or the identifier of each business data stream is allocated and synchronized separately, except that the upper layer protocols corresponding to different business data streams may be different, the method of synchronizing the identifier of each business data stream between the terminal and the AF is the same as the method of synchronizing the identifier of the first business data stream between the terminal and the AF in the above example, so the allocation or determination method of the identifier of each business data stream will not be described one by one here. In an embodiment, synchronizing the identifier of the first device between the terminal and the AF may include: the terminal acquiring the identifier of the first device; and the terminal and the AF interacting through the application layer to synchronize the identifier of the first device to the AF. Optionally, the terminal acquiring the identifier of the first device may include: the terminal directly acquiring the identifier of the first device from the first device. In this case, the identifier of the first device may refer to the identity (ID) of the first device itself, and the ID may include but is not limited to at least one of the following: number, serial number, name, SUPI (Subscription Permanent Identifier), SUCI (Subscription Concealed Identifier), PEI (Permanent Equipment Identifier), 5G-GUTI (5G Globally Unique Temporary Identifier), Internal-Group Identifier (IGI), GPSI (Generic Public Subscription Identifier), etc. Optionally, the terminal acquiring the identifier of the first device may include: the terminal assigning the identifier of the first device to the first device. In this case, since the first device is a tethered device associated with the terminal, the terminal can assign an identifier to the tethered device associated with itself, and the identifier assigned by the terminal to the first device can have a corresponding relationship with the ID of the first device itself; that is, the terminal assigning the identifier of the first device to the first device may include: the terminal assigning the identifier of the first device to the first device, and determining the corresponding relationship between the identifier of the first device and the ID of the first device itself. Correspondingly, the terminal and AF interact through the application layer to synchronize the identifier of the first device to the AF, which may include: the terminal and AF interact through the application layer to synchronize the identifier of the first device, the corresponding relationship between the identifier of the first device and the ID of the first device itself to the AF. The specific manner in which the terminal allocates the identifier of the first device is not limited here. As long as the terminal and each network element on the core network side can uniquely identify the first device through the identifier of the first device, it is within the protection scope of this embodiment. It should be noted that in the aforementioned embodiment, synchronizing the identifier of the first device between the terminal and the AF may include: synchronizing the identifiers of one or more tethered devices between the terminal and the AF, wherein the one or more tethered devices include the first device. Here, the identifier of each tethered device in all tethered devices may be synchronized between the terminal and the AF at one time; or, the identifier of each tethered device may be synchronized between the terminal and the AF separately. It should be understood that whether the identifiers of all tethered devices are synchronized between the terminal and the AF at one time or the identifier of each tethered device is synchronized separately, the way in which the terminal obtains the identifier of each tethered device is the same as the way in which the terminal obtains the identifier of the first device in the aforementioned embodiment, and therefore, it will not be described one by one here. In some possible implementations, before the terminal and the first core network element transmit uplink data packets and / or transmit downlink data packets of the first service data flow, the terminal and the first core network element may also obtain control information associated with the first service data flow. Specifically, before the terminal determines that the uplink data packet belongs to the first service data flow based on the description information of the first service data flow, it may also include: the terminal receives control information associated with the first service data flow sent by the second core network network element. Before the first core network element receives the data packet, the method may also include: the terminal receiving control information associated with the first service data flow sent by the second core network element. Correspondingly, the processing of the second core network network element may include: the second core network network element sends control information associated with the first service data flow to the terminal; the second core network network element sends control information associated with the first service data flow to the first core network element. The second core network element may send the control information associated with the first service data flow and the filter of the first service data flow to the terminal in the same message, such as the first message. That is, the second core network element may send the first message to the terminal; the processing of the terminal may include: the terminal receives the first message sent by the second core network element, and the first message may carry the control information associated with the first service data flow and the filter of the first service data flow. The second core network element may send the control information associated with the first service data flow and the filter of the first service data flow to the first core network element in the same message, such as the second message. Sending a second message; the processing of the first core network network element may include: the first core network network element receives a second message sent by the second core network network element, and the second message may carry control information associated with the first business data flow and a filter of the first business data flow. The timing of sending the above-mentioned first message and second message may not be in particular order. For example, the second core network element may send the first message and the second message at the same time, or the second core network element may send the first message first and then the second message, or the second core network element may send the second message first and then the first message. In one embodiment, the second core network network element may obtain a filter for the first service data flow from the terminal or an application function (AF) before sending control information associated with the first service data flow to the terminal and sending control information associated with the first service data flow to the first core network network element. The manner in which the second core network network element obtains the filter for the first service data flow from the terminal or AF is the same as in the aforementioned embodiment and will not be described repeatedly. The manner in which the second core network network element specifically determines the control information associated with the first service data flow is not limited in this embodiment. In one embodiment, the control information associated with the first business data flow includes at least one of the following: wireless resources associated with the first business data flow, a bit rate associated with the first business data flow, quality of service QoS parameters associated with the first business data flow, gateway parameters associated with the first business data flow, billing parameters associated with the first business data flow, and a data flow identifier associated with the first business data flow. The wireless resources may include time domain resources and / or frequency domain resources. The gateway parameter may be a gateway control parameter. The data flow identifier associated with the first service data flow includes at least one of the following: an identifier of the first service data flow, and a QoS flow identifier associated with the first service data flow. Optionally, the control information associated with the first service data flow sent by the second core network network element to the terminal and the control information associated with the first service data flow sent to the first core network network element may be the same. For example, the control information associated with the first business data flow sent by the second core network element to the terminal and the control information associated with the first business data flow sent to the first core network element may include at least one of the following: wireless resources associated with the first business data flow, the bit rate associated with the first business data flow, the quality of service QoS parameters associated with the first business data flow, the gateway parameters associated with the first business data flow, the billing parameters associated with the first business data flow, and the data flow identifier associated with the first business data flow. Optionally, the control information associated with the first service data flow sent by the second core network network element to the terminal and the control information associated with the first service data flow sent to the first core network network element may be at least partially different. For example, the control information associated with the first service data flow sent by the second core network element to the terminal is mainly used for the terminal to control the transmission of uplink data packets belonging to the first service data flow. Correspondingly, the control information associated with the first service data flow sent by the second core network element to the terminal may include at least one of the following: wireless resources associated with the first service data flow, bit rate associated with the first service data flow, data flow identifier associated with the first service data flow, etc. The control information associated with the first service data flow sent by the second core network network element to the first core network network element is mainly used by the first core network network element to control the transmission of uplink data packets and / or downlink data packets belonging to the first service data flow. Correspondingly, the control information associated with the first service data flow sent by the second core network network element to the first core network network element may include at least one of the following: the bit rate associated with the first service data flow, the quality of service QoS parameters associated with the first service data flow, the gateway parameters associated with the first service data flow, the billing parameters associated with the first service data flow, the data flow identifier associated with the first service data flow, and the like. It should be understood that the above is only an exemplary explanation, and there is no limitation or exhaustive list of parameters that may be included in the control information associated with the first service data flow sent by the second core network element to the terminal and the control information associated with the first service data flow sent to the first core network element. In some possible implementations, the terminal determines that an uplink data packet belongs to the first business data flow based on the description information of the first business data flow, including at least one of the following: the terminal receives an uplink data packet sent by a first device, and determines that the uplink data packet belongs to the first business data flow when the description information of the first business data flow includes an identifier of the first device; the terminal determines that the uplink data packet belongs to the first business data flow when the flow identifier carried by the uplink data packet matches the identifier of the first business data flow in the description information of the first business data flow. In one embodiment, the terminal can receive an uplink data packet sent by each of the one or more tethered devices associated with the terminal; the first device is one of the one or more tethered devices associated with the terminal, so the terminal can receive the uplink data packet sent by the first device. In one case, the description information of the first service data flow only includes the identifier of the first device. The terminal determines that the uplink data packet belongs to the first service data stream based on the description information of the first service data stream, which may only include: the terminal receives the uplink data packet sent by the first device, and when the description information of the first service data stream includes the identifier of the first device, determines that the uplink data packet belongs to the first service data stream. In addition, it may also include: when the description information of the first service data stream does not include the identifier of the first device, determines that the uplink data packet does not belong to the first service data stream. In one case, the description information of the first service data flow only includes an identifier of the first service data flow. The terminal determines that the uplink data packet belongs to the first business data flow based on the description information of the first business data flow, which may only include: the terminal receives an uplink data packet sent by the first device, and the terminal determines that the uplink data packet belongs to the first business data flow when the flow identifier carried by the uplink data packet matches the identifier of the first business data flow in the description information of the first business data flow. Specifically, when the flow identifier carried by the uplink data packet matches the identifier of the first business data flow in the description information of the first business data flow, the terminal determines that the uplink data packet belongs to the first business data flow, which may include: the terminal extracts the flow identifier from the uplink data packet; determines whether the flow identifier carried by the uplink data packet matches the identifier of the first business data flow in the description information of the first business data flow; and determines that the uplink data packet belongs to the first business data flow when the flow identifier carried by the uplink data packet matches the identifier of the first business data flow in the description information of the first business data flow. In addition, it may also include: when the flow identifier carried by the uplink data packet does not match the identifier of the first business data flow in the description information of the first business data flow, determining that the uplink data packet does not belong to the first business data flow. Wherein, the determination of whether the flow identifier carried by the uplink data packet matches the identifier of the first business data flow in the description information of the first business data flow, may include: determining whether the flow identifier carried by the uplink data packet is the same as the identifier of the first business data flow in the description information of the first business data flow, or determining whether the flow identifier carried by the uplink data packet has a corresponding relationship with the identifier of the first business data flow in the description information of the first business data flow. Wherein, the manner in which the terminal side obtains the corresponding relationship between the identifier of the first business data flow and the flow identifier of the first business data flow has been described in detail in the aforementioned embodiment, and will not be repeated here. In one case, the description information of the first service data flow includes an identifier of the first service data flow and an identifier of the first device. The terminal determines that an uplink data packet belongs to the first business data flow based on the description information of the first business data flow, which may include: the terminal receives an uplink data packet sent by a first device, and the terminal determines that the uplink data packet belongs to the first business data flow when the description information of the first business data flow includes an identifier of the first device and the flow identifier carried by the uplink data packet matches the identifier of the first business data flow in the description information of the first business data flow. In one embodiment, the uplink data packet to be sent by the terminal side may be generated by the terminal itself. In this embodiment, after the terminal generates the uplink data packet, the terminal may perform processing of determining that the uplink data packet belongs to the first service data flow based on the description information of the first service data flow. In this embodiment, the description information of the first service data flow needs to include at least an identifier of the first service data flow. Accordingly, the terminal determines that the uplink data packet belongs to the first service data flow based on the description information of the first service data flow, which may include: the terminal determines that the uplink data packet belongs to the first service data flow when the flow identifier carried by the uplink data packet matches the identifier of the first service data flow in the description information of the first service data flow. The detailed description of this process is the same as that of the above embodiment, and will not be repeated. It should be understood that this embodiment does not limit whether the description information of the first business data flow includes the identifier of the first device; when the description information of the first business data flow includes the identifier of the first business data flow and the identifier of the first device, the terminal may not use the identifier of the first device in the description information of the first business data flow to make a corresponding judgment, so it is not elaborated here. In some possible implementations, after the terminal determines that the uplink data packet belongs to the first service data flow based on the description information of the first service data flow, before the terminal transmits the uplink data packet to the first core network element, it may also include: the terminal adding at least one of the following to the header of the uplink data packet: an identifier of the first service data flow, an identifier of the first device. In one case, the description information of the first service data flow only includes the identifier of the first device. In this case, before the terminal transmits the uplink data packet to the first core network element, the method may further include: the terminal adds the identifier of the first device to the header of the uplink data packet. In one case, the description information of the first service data flow only includes the identifier of the first service data flow. In this case, before the terminal transmits the uplink data packet to the first core network element, the method may further include: the terminal adds the identifier of the first service data flow to the header of the uplink data packet. In one case, the description information of the first service data flow includes an identifier of the first service data flow and an identifier of the first device. In this case, before the terminal transmits an uplink data packet to the first core network element, the method may also include: the terminal adds at least one of the following to the header of the uplink data packet: an identifier of the first service data flow and an identifier of the first device. In some possible implementations, the terminal may execute processing for transmitting an uplink data packet to the first core network element. The terminal transmits an uplink data packet to a first core network element, including: the terminal transmits the uplink data packet to the first core network element based on control information associated with the first service data flow. The terminal transmits the uplink data packet to the first core network element based on the control information associated with the first service data flow, which may refer to: the terminal transmits the uplink data packet to the first core network element through an access network device based on the control information associated with the first service data flow. The access network device may be an access network device serving the terminal. Optionally, the control information associated with the first service data flow on the terminal side may include a wireless Resources, the bit rate associated with the first business data flow, the quality of service QoS parameters associated with the first business data flow, the gateway parameters associated with the first business data flow, the billing parameters associated with the first business data flow, and part or all of the parameters in the data flow identifier associated with the first business data flow. For example, the control information associated with the first service data stream may include: wireless resources associated with the first service data stream, and the bit rate associated with the first service data stream. The terminal transmits the uplink data packet to the first core network network element through the access network device based on the control information associated with the first service data stream, which may mean that the terminal transmits the uplink data packet to the first core network network element through the access network device based on the wireless resources and bit rate associated with the first service data stream. It should be understood that this is only an exemplary description, and the control information associated with the first service data stream received by the terminal in actual processing may not only include the above parameters, which are not limited or enumerated here. In some possible implementations, the first core network element receives a data packet, which is an uplink data packet. In this embodiment, the first core network network element determines that the data packet belongs to the first service data flow based on the description information of the first service data flow, including at least one of the following: the first core network network element determines that the data packet belongs to the first service data flow when the identifier of the service data flow carried in the header of the data packet is the same as the identifier of the first service data flow in the description information of the first service data flow; the first core network network element determines that the data packet belongs to the first service data flow when the identifier of the device carried in the header of the data packet is the same as the identifier of the first device in the description information of the first service data flow. In this implementation manner, the data packet is an uplink data packet. Specifically, the first core network element receiving the data packet includes: the first core network element receiving the uplink data packet transmitted by the terminal. Correspondingly, the first core network network element determines that the data packet belongs to the first service data flow based on the description information of the first service data flow, including at least one of the following: the first core network network element determines that the uplink data packet belongs to the first service data flow when the identifier of the service data flow carried in the header of the uplink data packet is the same as the identifier of the first service data flow in the description information of the first service data flow; the first core network network element determines that the uplink data packet belongs to the first service data flow when the identifier of the device carried in the header of the uplink data packet is the same as the identifier of the first device in the description information of the first service data flow. Specifically, the first core network element determines, based on the description information of the first service data flow, that the data packet belongs to the first service data flow, including one of the following: The first core network network element determines that the uplink data packet belongs to the first service data flow when the header of the uplink data packet carries only the identifier of the device, and the identifier of the device carried in the header of the uplink data packet is the same as the identifier of the first device in the description information of the first service data flow; The first core network network element determines that the uplink data packet belongs to the first service data flow when the header of the uplink data packet carries only the identifier of the service data flow and the identifier of the service data flow carried in the header of the uplink data packet is the same as the identifier of the first service data flow in the description information of the first service data flow; When the first core network network element carries an identifier of a service data flow and an identifier of a device in the header of the uplink data packet, if the identifier of the service data flow carried in the header of the uplink data packet is the same as the identifier of the first service data flow in the description information of the first service data flow, and the identifier of the device carried in the header of the uplink data packet is the same as the identifier of the first device in the description information of the first service data flow, then it is determined that the uplink data packet belongs to the first service data flow. In addition, it may also include: when the identifier of the service data flow carried by the first core network element in the header of the uplink data packet is different from the identifier of the first service data flow in the description information of the first service data flow, and / or the identifier of the device carried in the header of the uplink data packet is different from the identifier of the first device in the description information of the first service data flow, determining that the uplink data packet does not belong to the first service data flow. In this implementation manner, the first core network element transmitting the data packet includes: the first core network element transmitting the uplink data packet to the application server based on the control information associated with the first service data flow. Wherein, all the contents that may be included in the control information associated with the first service data flow are the same as those in the previous embodiment, and are not repeated here. The control information associated with the first business data flow received by the first core network network element may include wireless resources associated with the first business data flow, bit rate associated with the first business data flow, quality of service QoS parameters associated with the first business data flow, gateway parameters associated with the first business data flow, billing parameters associated with the first business data flow, and part or all of the parameters in the data flow identifier associated with the first business data flow. For example, the control information associated with the first business data flow may include: the bit rate associated with the first business data flow, the gateway parameters associated with the first business data flow, and the billing parameters associated with the first business data flow. The first core network network element transmits the uplink data packet to the application server based on the control information associated with the first business data flow, which may mean that the first core network network element controls the transmission of the uplink data packet to the application server based on the bit rate, gateway parameters and calculation parameters associated with the first business data flow. It should be understood that this is only an exemplary description, and in actual processing, the control information associated with the first business data flow received by the first core network network element The control information may include more than just the above parameters, which are not limited or exhaustive here. In some possible implementations, the first core network element receives a data packet, which is a downlink data packet. In this embodiment, the first core network network element determines that the data packet belongs to the first service data flow based on the description information of the first service data flow, including at least one of the following: the first core network network element determines that the data packet belongs to the first service data flow when the identifier of the service data flow carried in the header of the data packet is the same as the identifier of the first service data flow in the description information of the first service data flow; the first core network network element determines that the data packet belongs to the first service data flow when the identifier of the device carried in the header of the data packet is the same as the identifier of the first device in the description information of the first service data flow. In this implementation manner, the data packet is a downlink data packet. Specifically, the first core network element receiving the data packet includes: the first core network element receiving the downlink data packet transmitted by the application server. Correspondingly, the first core network network element determines that the data packet belongs to the first business data flow based on the description information of the first business data flow, including at least one of the following: the first core network network element determines that the downlink data packet belongs to the first business data flow when the identifier of the business data flow carried in the header of the downlink data packet is the same as the identifier of the first business data flow in the description information of the first business data flow; the first core network network element determines that the downlink data packet belongs to the first business data flow when the identifier of the device carried in the header of the downlink data packet is the same as the identifier of the first device in the description information of the first business data flow. Specifically, the first core network element determines, based on the description information of the first service data flow, that the data packet belongs to the first service data flow, including one of the following: The first core network network element determines that the downlink data packet belongs to the first service data flow when the header of the downlink data packet carries only the identifier of the device, and the identifier of the device carried in the header of the downlink data packet is the same as the identifier of the first device in the description information of the first service data flow; The first core network network element determines, when the header of the downlink data packet carries only the identifier of the service data flow and the identifier of the service data flow carried in the header of the downlink data packet is the same as the identifier of the first service data flow in the description information of the first service data flow, that the downlink data packet belongs to the first service data flow; When the first core network network element carries an identifier of a service data flow and an identifier of a device in the header of the downlink data packet, if the identifier of the service data flow carried in the header of the downlink data packet is the same as the identifier of the first service data flow in the description information of the first service data flow, and the identifier of the device carried in the header of the downlink data packet is the same as the identifier of the first device in the description information of the first service data flow, then it is determined that the uplink data packet belongs to the first service data flow. In addition, it may also include: when the first core network network element carries an identifier of the service data flow carried in the header of the downlink data packet and the identifier of the first service data flow in the description information of the first service data flow is different, and / or the identifier of the device carried in the header of the downlink data packet is different from the identifier of the first device in the description information of the first service data flow, determining that the downlink data packet does not belong to the first service data flow. In this implementation manner, the first core network element transmitting the data packet includes: the first core network element transmitting the downlink data packet to the terminal based on the control information associated with the first service data flow. Wherein, all the contents that may be included in the control information associated with the first service data flow are the same as those in the previous embodiment, and are not repeated here. For example, the control information associated with the first service data flow on the first core network network element side may include: the bit rate associated with the first service data flow, the quality of service QoS parameter associated with the first service data flow, the gateway parameter associated with the first service data flow, the charging parameter associated with the first service data flow, and the data flow identifier associated with the first service data flow. The first core network network element transmits the downlink data packet to the terminal based on the control information associated with the first service data flow, which may refer to: the first core network network element marks the downlink data packet with the data flow identifier associated with the first service data flow, controls based on the QoS parameter, bit rate, gateway parameter and calculation parameter associated with the first service data flow, and transmits the downlink data packet to the terminal through the access network device. Among them, the access network device is an access network device serving the terminal. It should be understood that this is only an exemplary description. In actual processing, the control information associated with the first service data flow received by the first core network network element may not only include the above parameters, which are not limited or exhaustive here. It should be understood that the above description is for the transmission of uplink data packets and / or downlink data packets belonging to the first service data flow by the terminal and the first core network element. In actual processing, if the terminal and the first core network element both obtain the description information (filter) of each service data flow in multiple service data flows and the control information of each service data flow, then the terminal and the first core network element can also perform corresponding transmission control on the uplink data packets and / or downlink data packets belonging to each service data flow. In this case, the transmission control of the uplink data packets and / or downlink data packets belonging to each service data flow is the same as the transmission control of the uplink data packets and / or downlink data packets belonging to the first service data flow. Therefore, for the sake of brevity, this application will no longer repeat the transmission control of the uplink data packets and / or downlink data packets of each service data flow one by one. By adopting the above solution, at least one of the first service data flow identifier and the first device identifier can be added to the description information of the first service data flow, so that when transmitting a data packet, the data packet can be matched with the description information of the first service data flow. Then the service data flow to which the data belongs is determined, so that the transmission of the data packet can be controlled based on the service data flow described in the data packet. In this way, for the case of a transmission protocol (unstructured data) that the 3GPP network cannot recognize, or for the case where an application packages multiple service flows together and encrypts them for transmission, or for the case where multiple tethered devices access the network through the same UE, the network (such as the operator network) can distinguish the service data flow to which the data packet belongs and control it, thereby ensuring the accuracy of transmission control. In conjunction with Figure 6, taking the terminal as UE, the first core network element as UPF, and the second core network element including SMF and PCF as an example, an exemplary description of the above communication method is given: Step 601a, the UE requests the PCF located in the core network to transmit a specific service data flow. The UE may directly send a message requesting the transmission of a specific service data flow to the PCF, or the UE may forward the message requesting the transmission of a specific service data flow to the PCF through other network elements (e.g., NEF, AMF, SMF). Step 601b, AF requests PCF located in the core network to transmit a specific service data flow. AF may directly send a message requesting transmission of a specific service data flow to PCF, or AF may forward the message requesting transmission of a specific service data flow to PCF through other network elements (e.g., NEF, AMF, SMF). Any one of the above steps 601a and 601b can be executed, that is, in actual processing, either step 601a or step 601b can be executed. The message requesting the transmission of a specific service data stream in step 601a or step 601b may be the transmission request message in the aforementioned embodiment, and the specific service data stream may include at least the first service data stream in the aforementioned embodiment. Specifically, the message requesting the transmission of a specific service data stream carries the description information of the first service data stream (i.e., the filter of the first service data stream); wherein, the description information of the first service data stream may be the identifier of the first service data stream, and / or the identifier of the tethered device for data transmission through the UE (i.e., the identifier of the first device in the aforementioned embodiment is alternatively referred to as the identifier of the tethered device in this example); or, the description information of the first service data stream may be the identifier of the first service data stream / the identifier of the tethered device, combined with the existing defined service data stream filter fields (e.g., IP address, port number, MAC address, etc.). In addition, before executing step 601a and step 601b, the AF may interact with the UE through the application layer to determine the first service data flow identifier and the tethered device identifier. For example, for transmission protocols (unstructured data) that cannot be recognized by the 3GPP network, the AF or UE assigns a service data flow identifier to each service data flow, and the service data flow identifier is synchronously assigned between the AF and the UE through application layer interaction. For example, the AF or UE takes the flow identifier in the upper layer protocol as the service data flow identifier. For example, the stream id in the QUIC (Quick UDP Internet Connection) protocol is taken as the service data flow identifier. Among them, QUIC is an encrypted transmission protocol, and the network elements in the operator network cannot parse the information that the QUIC data packet has been encrypted. For example, the UE determines the identifier of the tethered device, and the AF obtains the identifier of the tethered device determined by the UE through application layer interaction. The UE may obtain the identifier of the tethered device from the tethered device, or the UE allocates an identifier to the tethered device. In step 602 to step 604, the PCF sends the description information of the first service data flow to the UPF and / or UE via the SMF. Specifically, step 602: PCF sends the description information of the authorized first service data flow to SMF. Step 603: SMF sends the description information of the first service data flow to UPF. Step 604: SMF sends the description information of the first service data flow to UE. Furthermore, the PCF may also provide the first service data flow description information and control information of the first service data flow to the UPF and / or UE through the SMF. The control information may include, for example, QoS parameters, gating parameters, billing parameters, a network-assigned flow identifier (i.e., the data flow identifier associated with the first service data flow in the aforementioned embodiment), etc. Step 611: For downlink data, the AF adds the service data flow identifier and / or device identifier to the header of the downlink data packet and sends it to the UPF. In this step, the downlink data packet may be sent from the AF to the UPF, or the AF may receive the downlink data packet from other devices and send it to the UPF. Therefore, the source of the downlink data packet 611 in Figure 6 does not originate from the AF. In step 612, UPF determines that the service data flow to which the downlink data packet belongs is the first service data flow, and UPF performs corresponding data transmission control based on the control information associated with the first service data flow, and sends the downlink data packet to the terminal through the access network device. Specifically, the UPF determines that the service data flow to which the downlink data packet belongs is the first service data flow, which may include: the UPF may read the service data flow identifier carried in the header of the downlink data packet to determine the service data flow to which the data packet belongs, for example, the UPF reads the service data flow identifier carried in the header of the downlink data packet, determines that the service data flow identifier carried in the header of the downlink data packet is the same as the identifier of the first service data flow, and then determines that the service data flow to which the downlink data packet belongs is the first service data flow. Alternatively, the UPF determines that the service data flow to which the downlink data packet belongs is the first service data flow, which may include: the UPF may match the received downlink data packet according to the first service data flow description information sent by the SMF to determine the service data flow to which the data packet belongs, for example, the UPF reads the service data flow identifier and / or the device identifier carried in the header of the downlink data packet, if it is determined that the service data flow identifier carried in the header of the downlink data packet is the same as the identifier of the first service data flow in the description information of the first service data flow and / or the device identifier carried in the header of the downlink data packet is the same as the identifier of the tethered device in the description information of the first service data flow, then determines that the service data flow to which the downlink data packet belongs is the first service data flow. The above-mentioned UPF determines that the service data flow to which the downlink data packet belongs is the processing of the first service data flow, which can also be called the verification of the downlink data. The packet belongs to the processing of valid business data flow. The UPF performs corresponding data transmission control based on the control information associated with the first business data flow, and sends the downlink data packet to the terminal through the access network device, which may include: the UPF performs QoS control, bit rate control, billing control, and Gating control based on the control information associated with the first business data flow, and marks the downlink data packet with a network-assigned flow identifier and sends it to the access network device, and the access network device sends the downlink data packet to the terminal. Step 621, for uplink data, the UE determines that the service data flow to which the uplink data packet belongs is the first service data flow, performs corresponding data transmission control based on the control information associated with the first service data flow, and sends the uplink data packet to the UPF through the access network device. Specifically, the UE determines that the service data flow to which the uplink data packet belongs is the first service data flow, which may include: the UE reads the service data flow identifier carried in the header of the uplink data packet provided by the upload protocol unit to determine the service data flow to which the data packet belongs, for example, the UE reads the service data flow identifier carried in the header of the uplink data packet provided by the upload protocol unit, and if it is determined that the service data flow identifier carried in the header of the uplink data packet is the same as the identifier of the first service data flow, then the service data flow to which the uplink data packet belongs is determined to be the first service data flow. Alternatively, the UE determines that the service data flow to which the uplink data packet belongs is the first service data flow, which may include: the UE matches the uplink data packet according to the first service data flow description information sent by the SMF to determine the service data flow to which the data packet belongs, for example, the UE reads the service data flow identifier carried in the header of the uplink data packet and / or the identifier of the tethered device, and if it is determined that the service data flow identifier carried in the header of the uplink data packet is the same as the identifier of the first service data flow in the description information of the first service data flow and / or the description information of the first service data flow includes the identifier of the tethered device, then the service data flow to which the uplink data packet belongs is determined to be the first service data flow. The above-mentioned process of the UE determining that the service data flow to which the uplink data packet belongs is the first service data flow may also be referred to as the process of verifying that the uplink data packet belongs to a valid service data flow. Performing corresponding data transmission control based on the control information associated with the first business data flow, and sending uplink data packets to the user plane function through the access network device, may include: the UE sends a specific first business data flow to the access network device through corresponding wireless resources based on the control information associated with the first business data flow, and performs bit rate control. Optionally, the header of the uplink data packet sent by the UE to the network may include the first service data flow identifier and / or the tethered device identifier. In this case, step 622 may be further performed. Step 622 (optional), after receiving the uplink data packet from the access network device, the UPF can determine that the service data flow to which the uplink data packet belongs is the first service data flow according to the service data flow identifier and / or the tethered device identifier in the packet header of the uplink data packet, perform transmission control on the uplink data packet, and transmit the uplink data packet to the AF. In this step, the uplink data packet sent by the UPF may be sent directly to the AF, or may be sent by the UPF to other devices through the AF, so the arrow pointing to the uplink data packet in 622 in Figure 6 does not end at the AF. For example, UPF reads the service data flow identifier of the uplink data packet header to determine the service data flow to which the uplink data packet belongs (i.e., when the service data flow identifier carried in the header of the uplink data packet is the same as the identifier of the first service data flow, it is determined that the uplink data packet belongs to the first service data flow), or matches the received uplink data packet according to the service data flow description information obtained from SMF to determine the service data flow to which the data packet belongs (i.e., when the service data flow identifier carried in the header of the uplink data packet is the same as the identifier of the first service data flow and / or the device identifier carried in the header of the uplink data packet is the same as the identifier of the tethered device, it is determined that the uplink data packet belongs to the first service data flow). UPF performs rate control, billing control, Gating control on the uplink data, verifies that the uplink data packet belongs to a valid service data flow (i.e., when it is verified that the uplink data packet belongs to the first service data flow, it is verified that the uplink data packet belongs to a valid service data flow), etc. In the above example, the description information of the service data flow (such as the first service data flow) includes at least one of the identifier of the service data flow and the identifier of the tethered device. The application server AF adds the service data flow identifier and the tethered device identifier to the header of the downlink data packet and sends it to the UPF. The UPF determines the service data flow to which the downlink data belongs and performs corresponding transmission control. The UE determines the service data flow to which the uplink data packet belongs and performs corresponding transmission control. The header of the uplink data packet includes at least one of the service data flow identifier and the tethered device identifier. In this way, by adding at least one of the service data flow identifier and the tethered device identifier to the description information of the service data flow, the data packet header is required to carry the service data flow identifier and the tethered device identifier, so that the data packet header and the service data flow description information can be matched to determine the service data flow to which the data belongs. For the case of a transmission protocol (unstructured data) that cannot be recognized by the 3GPP network, or for the case where the application packages multiple service flows together and encrypts them for transmission, or for the case where multiple tethered devices access the network through the same UE, by adopting the above scheme, the network (such as the operator network) can distinguish the service data flows and control them. Fig. 7 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. S710. The terminal transmits an uplink data packet through a first tunnel, wherein a header of the uplink data packet carries description information of the first tunnel, and the first tunnel is a tunnel between the terminal and a first core network element. Fig. 8 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. S810. The first core network element receives an uplink data packet, wherein a header of the uplink data packet carries description information of a first tunnel, and the first tunnel is a tunnel between a terminal and the first core network element; S820. The first core network element transmits the uplink data packet through a second tunnel, wherein a header of the uplink data packet carries description information of the second tunnel, and the second tunnel is a tunnel between the first core network element and an application server. Fig. 9 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. S910. The first core network element receives a downlink data packet, wherein a header of the downlink data packet carries description information of a second tunnel, and the second tunnel is a tunnel between the first core network element and an application server; S920. The first core network element transmits a downlink data packet through a first tunnel, wherein a header of the downlink data packet carries description information of the first tunnel, and the first tunnel is a tunnel between a terminal and the first core network element. Here, the first core network element may include a user plane network element. In some possible implementations, before the terminal transmits an uplink data packet through the first tunnel, the terminal first establishes the first tunnel, and the application server establishes the second tunnel. Specifically, the first tunnel is established between the terminal and the first core network element of the core network, and the second tunnel is established between the application server and the first core network element of the core network, and both the first tunnel and the second tunnel are used to transmit the first service data flow. For example, the terminal is UE, and the first core network element is UPF, that is, tunnel 1 (first tunnel) is established between UE and UPF of the core network, and tunnel 2 (second tunnel) is established between the application server and UPF of the core network. For example, UE and application server can establish tunnel 1 and tunnel 2 with UPF respectively based on MASQUE (Multiplexed Application Substrate over QUIC Encryption) protocol, and tunnel 1 and tunnel 2 are used to transmit a specific first service data flow, that is, the service data flow indicated by the description information of the first service data flow. In this implementation manner, the identifier of the first service data flow and the identifier of the first device included in the description information of the first service data flow are the same as those in the above-mentioned embodiment, and thus are not described repeatedly. In addition, the terminal and AF need to synchronize the description information of the first service data flow. Here, the relationship between AF and application server is: the application server can be DN, AF is the control plane network element, AF and application server may be the same device, but it is called AF when doing control plane interaction, and it is called application server when doing user plane data transmission. The description information of the first service data stream synchronized between the terminal and the AF may include an identifier of the first service data stream synchronized between the terminal and the AF and / or an identifier of the first device synchronized between the terminal and the AF. The specific processing methods of the identifier of the first service data stream synchronized between the terminal and the AF and the identifier of the first device synchronized between the terminal and the AF are the same as those in the aforementioned embodiment, so they are not described in detail. After establishing a first tunnel between a terminal and a first core network element of a core network and before the terminal transmits an uplink data packet through the first tunnel, the method may further include: the terminal sends first information to a second core network element, wherein the first information is used to indicate an association between description information of the first service data flow and description information of the first tunnel. Correspondingly, the processing of the second core network element may include: the second core network element receives the first information sent by the terminal. The second core network element may include at least one of the following: a mobility management element, a session management element, and a policy control element. The mobility management element may include an AMF; the session management element may include an SMF; and the policy control element may include a PCF. Optionally, the first information may include description information of the first service data flow and description information of the first tunnel. In this case, the terminal may indicate that the description information of the first service data flow and the description information of the first tunnel have an association relationship through the first information including the description information of the first service data flow and the description information of the first tunnel. That is to say, after receiving the first information including the description information of the first service data flow and the description information of the first tunnel, the second core network element may obtain the description information of the first service data flow and the description information of the first tunnel, and determine the association relationship between the description information of the first service data flow and the description information of the first tunnel. Optionally, the first information may include description information of the first service data flow, description information of the first tunnel, and association indication information between the description information of the first service data flow and the description information of the first tunnel. The association indication information may be an association identifier. For example, if the association identifier is 1, it indicates that there is an association relationship between the two description information included in the first information. It should be understood that this is only an exemplary description, and the possible content of the association indication information is not exhaustive or limited. In this case, after receiving the first information, the second core network element can directly obtain the description information of the first service data flow, the description information of the first tunnel, and the association between the description information of the first service data flow and the description information of the first tunnel. After establishing a second tunnel between the application server and the first core network element of the core network and before the application server transmits a downlink data packet through the second tunnel, the method may further include: the application server sends sixth information to the second core network element, wherein the sixth information is used to indicate the association between the description information of the first service data flow and the description information of the second tunnel. Correspondingly, the processing of the second core network element may include: the second core network element receives the sixth information sent by the application server. The manner in which the sixth information indicates the association between the description information of the first service data flow and the description information of the second tunnel is similar to the manner in which the first information indicates the association between the description information of the first service data flow and the description information of the first tunnel, so it is not elaborated here. The description information of the first tunnel includes at least one of the following: an Internet Protocol IP quintuple corresponding to the first tunnel, and an IP triplet corresponding to the first tunnel. The description information of the second tunnel includes at least one of the following: an Internet Protocol IP quintuple corresponding to the second tunnel, and an IP triplet corresponding to the second tunnel. Exemplarily, the description information of the first tunnel may also be referred to as the filter of the first tunnel, or the packet filter set of the first tunnel, and the description information of the second tunnel may also be referred to as the filter of the second tunnel, or the packet filter set of the second tunnel. In some possible implementations, before the terminal transmits an uplink data packet through the first tunnel, the step further includes: the terminal receives second information sent by a second core network element, wherein the second information includes: control information of the first tunnel, and an association between the control information of the first tunnel and description information of the first tunnel. Accordingly, the processing of the second core network element may include: the second core network element sends the second information to the terminal. The manner in which the second core network element specifically determines the control information of the first tunnel is not limited in this embodiment. Before the first core network element receives the uplink data packet, it also includes: the first core network element receives fifth information sent by the second core network element, wherein the fifth information includes: control information of the first tunnel, and the association between the control information of the first tunnel and the description information of the first tunnel. Alternatively, before the first core network element receives the downlink data packet, it also includes: the first core network element receives fifth information sent by the second core network element, wherein the fifth information includes: control information of the first tunnel, and the association between the control information of the first tunnel and the description information of the first tunnel. Correspondingly, the processing of the second core network element may include: the second core network element sends the fifth information to the terminal. The manner in which the second core network element specifically determines the control information of the first tunnel is not limited in this embodiment. The control information of the first tunnel includes at least one of the following: wireless resources associated with the first tunnel, a bit rate associated with the first tunnel, a quality of service QoS parameter associated with the first tunnel, a gateway parameter associated with the first tunnel, a billing parameter associated with the first tunnel, and a data flow identifier associated with the first tunnel. The wireless resources may include time domain resources and / or frequency domain resources. The gateway parameter may be a gateway control parameter. The data flow identifier associated with the first tunnel includes a QoS flow identifier associated with the first tunnel. Optionally, the control information of the first tunnel sent by the second core network element to the terminal and the control information of the first tunnel sent by the second core network element to the first core network element may be the same. For example, the control information of the first tunnel sent by the second core network element to the terminal and the control information of the first tunnel sent by the second core network element to the first core network element may include some or all of the above parameters. Optionally, the control information of the first tunnel sent by the second core network element to the terminal and the control information of the first tunnel sent by the second core network element to the first core network element may be at least partially different. For example, the control information of the first tunnel sent by the second core network element to the terminal may include at least one of the following: the wireless resources associated with the first tunnel, the code rate associated with the first tunnel, the data flow identifier associated with the first tunnel, etc. It should be understood that the above is only an exemplary description, and the parameters that may be included in the control information of the first tunnel sent by the second core network element to the terminal are not limited or exhaustive. The control information of the first tunnel sent by the second core network element to the first core network element may include at least one of the following: the code rate associated with the first tunnel, the quality of service QoS parameter associated with the first tunnel, the gateway parameter associated with the first tunnel, the charging parameter associated with the first tunnel, the data flow identifier associated with the first tunnel, etc. It should be understood that the above is only an exemplary description, and the parameters that may be included in the control information of the first tunnel sent by the second core network element to the first core network element are not limited or exhaustive. The following contents can be obtained or saved in the terminal: description information of the first tunnel, control information of the first tunnel, description information of the first business data flow, association between the control information of the first tunnel and the description information of the first tunnel, and association between the description information of the first tunnel and the description information of the first business data flow. In some possible implementations, before the first core network element receives the uplink data packet, the method further includes: the first core network element receives third information sent by the second core network element, wherein the third information is used to indicate the association relationship between the description information of the first tunnel and the description information of the second tunnel. Alternatively, before the first core network element receives the downlink data packet, the method further includes: the first core network element receives third information sent by the second core network element, wherein the third information is used to indicate the association relationship between the description information of the first tunnel and the description information of the second tunnel. Correspondingly, the processing of the second core network element may also include: the second core network element sends third information to the first core network element. Optionally, the third information may include description information of the first tunnel and description information of the second tunnel. In this case, the second core network element may indicate that the description information of the first tunnel and the description information of the second tunnel have an associated relationship through the third information including the description information of the first tunnel and the description information of the second tunnel. That is, after receiving the third information including the description information of the first tunnel and the description information of the second tunnel, the first core network element may obtain the description information of the first tunnel and the description information of the second tunnel, and determine the associated relationship between the description information of the first tunnel and the description information of the second tunnel. Optionally, the third information may include description information of the first tunnel, description information of the second tunnel, and association indication information between the description information of the first tunnel and the description information of the second tunnel. In this case, after receiving the third information, the first core network element can directly obtain the description information of the first tunnel, the description information of the second tunnel, and the description information of the first tunnel. The association relationship between the description information of the second tunnel and the description information of the second tunnel. Through the above processing, the following contents can be obtained or saved in the first core network network element: description information of the first tunnel, description information of the second tunnel, control information of the first tunnel, the association relationship between the description information of the first tunnel and the description information of the second tunnel, and the association relationship between the control information of the first tunnel and the description information of the first tunnel. In some possible implementations, before the first core network element receives the uplink data packet, the method further includes: the first core network element receives fourth information sent by the second core network element, wherein the fourth information is used to indicate the association relationship between the description information of the second tunnel and the description information of the first service data flow, and the association relationship between the description information of the first tunnel and the description information of the first service data flow. Alternatively, before the first core network element receives the downlink data packet, the method further includes: the first core network element receives fourth information sent by the second core network element, wherein the fourth information is used to indicate the association relationship between the description information of the second tunnel and the description information of the first service data flow, and the association relationship between the description information of the first tunnel and the description information of the first service data flow. Correspondingly, the processing of the second core network network element may also include: the second core network network element sends fourth information to the first core network network element. Optionally, the fourth information may include description information of the first tunnel, description information of the second tunnel, and description information of the first service data flow, and the fourth information may also include association indication information between the description information of the first tunnel and the description information of the first service data flow, and association indication information between the description information of the second tunnel and the description information of the first service data flow. In this case, after receiving the fourth information, the first core network element can obtain the description information of the first tunnel, the description information of the second tunnel, the description information of the first service data flow, the association relationship between the description information of the second tunnel and the description information of the first service data flow, and the association relationship between the description information of the first tunnel and the description information of the first service data flow. Optionally, the fourth information may include {description information of the first tunnel, description information of the first service data flow}, {description information of the second tunnel, description information of the first service data flow}, such two pairs of associated content. In this case, after receiving the third information, the first core network element can directly obtain the description information of the first tunnel, the description information of the second tunnel, the description information of the first service data flow, the association between the description information of the second tunnel and the description information of the first service data flow, and the association between the description information of the first tunnel and the description information of the first service data flow. Through the above processing, the following contents can be obtained or saved in the first core network network element: description information of the first tunnel, description information of the second tunnel, description information of the first business data flow, control information of the first tunnel, the association relationship between the description information of the second tunnel and the description information of the first business data flow, and the association relationship between the description information of the first tunnel and the description information of the first business data flow. In some possible implementations, before the terminal transmits an uplink data packet through the first tunnel, it also includes: the terminal determines that the uplink data packet belongs to the first business data flow based on the description information of the first business data flow; the terminal determines that the uplink data packet corresponds to the first tunnel based on the association between the description information of the first business data flow and the description information of the first tunnel, wherein the description information of the first business data flow includes at least one of the following: an identifier of the first business data flow and an identifier of the first device. Among them, the terminal determines that the uplink data packet belongs to the first business data flow based on the description information of the first business data flow, including at least one of the following: the terminal receives an uplink data packet sent by the first device, and determines that the uplink data packet belongs to the first business data flow when the description information of the first business data flow includes the identifier of the first device; the terminal determines that the uplink data packet belongs to the first business data flow when the flow identifier carried by the uplink data packet matches the identifier of the first business data flow in the description information of the first business data flow. In this implementation, the description information of the first business data flow, the identifier of the first business data flow, the first device, the identifier of the first device, the specific processing method for the terminal to determine that the uplink data packet belongs to the first business data flow based on the description information of the first business data flow, etc. are all the same as those in the previous embodiment, and therefore will not be repeated. The terminal transmits an uplink data packet through a first tunnel, including: the terminal transmits an uplink data packet through the first tunnel based on control information of the first tunnel. Specifically, the terminal transmitting an uplink data packet through the first tunnel based on the control information of the first tunnel may include: the terminal determining the control information of the first tunnel based on the description information of the first tunnel and the association between the description information of the first tunnel and the control information of the first tunnel; the terminal transmitting an uplink data packet through the first tunnel based on the control information of the first tunnel. It should be noted that the processing of transmitting an uplink data packet through the first tunnel may include: adding the description information of the first tunnel to the header of the uplink data packet, and transmitting the uplink data packet through the first tunnel. For example, the terminal transmits the uplink data packet through the first tunnel based on the control information of the first tunnel, which can be: the terminal controls the transmission of the uplink data packet through the first tunnel to the first core network element via the access network device based on the wireless resources and code rate associated with the first tunnel. It should be understood that this is only an exemplary description, and the control information of the first tunnel received by the terminal in actual processing may not only include the above parameters, which are not limited or exhaustive here. In some possible implementations, the first core network element receiving the uplink data packet may include: the first core network element receiving the uplink data packet via the first core network element A tunnel receives an uplink data packet sent by a terminal. Before the first core network element transmits the uplink data packet through the second tunnel, it also includes: the first core network element replaces the description information of the first tunnel carried in the header of the uplink data packet with the description information of the second tunnel. The aforementioned implementation method has explained that when the terminal transmits an uplink data packet through the first tunnel, the description information of the first tunnel will be carried in the header of the uplink data packet; accordingly, after receiving the uplink data packet, the first core network element can extract the description information of the first tunnel carried in the header of the uplink data packet, and then determine the description information of the second tunnel, and replace the description information of the first tunnel carried in the header of the uplink data packet with the description information of the second tunnel. In one embodiment, the first core network element stores an association relationship between the description information of the first tunnel and the description information of the second tunnel. Accordingly, the second tunnel is determined based on the association relationship between the description information of the first tunnel and the description information of the second tunnel. Specifically, the manner in which the first core network element determines the second tunnel may include: the first core network element extracts the description information of the first tunnel carried in the header of the uplink data packet, and determines the second tunnel according to the association relationship between the description information of the first tunnel and the description information of the second tunnel. In one embodiment, the first core network element stores the association relationship between the description information of the second tunnel and the description information of the first service data flow, and the association relationship between the description information of the first tunnel and the description information of the first service data flow. Accordingly, the second tunnel is determined based on the first service data flow to which the uplink data packet belongs, the association relationship between the description information of the second tunnel and the description information of the first service data flow, wherein the first service data flow is determined based on the association relationship between the description information of the first tunnel and the description information of the first service data flow. Specifically, the manner in which the first core network element determines the second tunnel may include: the first core network element extracts the description information of the first tunnel carried in the header of the uplink data packet, and determines that the service data flow to which the uplink data packet belongs is the first service data flow according to the association relationship between the description information of the first tunnel and the description information of the first service data flow; and determines the second tunnel based on the association relationship between the first service data flow to which the uplink data packet belongs, the description information of the second tunnel and the description information of the first service data flow. The first core network element transmits an uplink data packet through the second tunnel, including: the first core network element transmits the uplink data packet through the second tunnel based on the control information of the first tunnel. For example, the first core network element transmits the uplink data packet through the second tunnel based on the control information of the first tunnel can be: the first core network element controls the transmission of the uplink data packet to the application server through the second tunnel based on the bit rate, billing parameters, and gateway parameters associated with the first tunnel. It should be understood that this is only an exemplary description, and in actual processing, the control information of the first tunnel received by the first core network element may not only include the above parameters, which are not limited or exhaustive here. In some possible implementations, the first core network element receiving the downlink data packet may include: the first core network element receiving the downlink data packet through the second tunnel. Specifically, the downlink data packet received by the first core network network element is sent by an application server, and the processing of the downlink data packet sent by the application server may include: before sending the downlink data packet, the application server determines whether the downlink data packet belongs to the first business data flow based on the description information of the first business data flow, the identifier of the business data flow carried in the header of the downlink data packet and / or the identifier of the device to which the downlink data packet is to be sent; when the application server determines that the downlink data packet belongs to the first business data flow, the second tunnel is determined based on the association between the description information of the first business data flow and the description information of the second tunnel; the application server adds the description information of the second tunnel to the downlink data packet, and sends the downlink data packet to the first core network element through the second tunnel. Before the first core network element transmits the downlink data packet through the first tunnel, the first core network element also includes: the first core network element replaces the description information of the second tunnel carried in the header of the downlink data packet with the description information of the first tunnel. That is, after the first core network element receives the downlink data packet, the first core network element extracts the description information of the second tunnel carried in the header of the downlink data packet, then determines the description information of the first tunnel, and replaces the description information of the second tunnel carried in the header of the downlink data packet with the description information of the first tunnel. In one embodiment, the first core network element stores an association relationship between the description information of the first tunnel and the description information of the second tunnel. Accordingly, the first tunnel is determined based on the association relationship between the description information of the first tunnel and the description information of the second tunnel. Specifically, the manner in which the first core network element determines the first tunnel may include: after the first core network element extracts the description information of the second tunnel carried in the header of the downlink data packet, the first core network element determines the first tunnel based on the association relationship between the description information of the first tunnel and the description information of the second tunnel. In one embodiment, the first core network network element stores an association relationship between the description information of the second tunnel and the description information of the first service data flow, and an association relationship between the description information of the first tunnel and the description information of the first service data flow. Accordingly, the first tunnel is determined based on the first service data flow to which the downlink data packet belongs, and the association relationship between the description information of the first tunnel and the description information of the first service data flow, wherein the first service data flow is determined based on the association relationship between the description information of the second tunnel and the description information of the first service data flow. Specifically, the manner in which the first core network network element determines the first tunnel may include: the first core network network element extracts the description information of the second tunnel carried in the header of the downlink data packet, and determines the service data flow to which the downlink data packet belongs according to the association relationship between the description information of the second tunnel and the description information of the first service data flow. The data flow is the first business data flow; and the first tunnel is determined based on the association relationship between the first business data flow to which the downlink data packet belongs, the description information of the first tunnel, and the description information of the first business data flow. The first core network element transmits a downlink data packet through the first tunnel, including: the first core network element transmits a downlink data packet through the first tunnel based on the control information of the first tunnel. For example, the first core network element transmits a downlink data packet through the first tunnel based on the control information of the first tunnel as follows: the first core network element marks the downlink data packet with a data flow identifier associated with the first tunnel, and controls the transmission of the downlink data packet to the terminal through the first tunnel based on the QoS parameters, bit rate, billing parameters, and gateway parameters associated with the first tunnel. It should be understood that this is only an exemplary description, and in actual processing, the control information of the first tunnel received by the first core network element may not only include the above parameters, which are not limited or exhaustive here. It should be understood that the above description is for the transmission of uplink data packets and / or downlink data packets belonging to the first service data flow by the terminal and the first core network element through the first tunnel and the second tunnel. In actual processing, if the terminal and the first core network element both obtain the description information of each tunnel in a pair of tunnels of each service data flow in multiple service data flows and the control information of each tunnel, then the terminal and the first core network element can also perform corresponding transmission control on the uplink data packets and / or downlink data packets belonging to each service data flow. In this case, the transmission control of the uplink data packets and / or downlink data packets belonging to each service data flow is the same as the transmission control method of the uplink data packets and / or downlink data packets belonging to the first service data flow transmitted through the first tunnel and the second tunnel. Therefore, for the sake of brevity, this application will no longer repeat the transmission control of the uplink data packets and / or downlink data packets of each service data flow one by one. By adopting the above solution, a specific business data flow is transmitted through a specific tunnel, so that the 3GPP network only needs to identify the tunnel to know the business data flow to which the data transmitted in the tunnel belongs. For the case of a transmission protocol (unstructured data) that the 3GPP network cannot recognize, or for the case where an application packages multiple business flows together and encrypts them for transmission, or for the case where multiple tethered devices access the network through the same UE, the purpose of distinguishing and controlling the business data flow can be achieved by controlling each tunnel, thereby ensuring the accuracy of data packet transmission control. In conjunction with FIG. 10 and FIG. 11, taking the terminal as a UE, the first core network element as a UPF, and the second core network element including an SMF and a PCF as an example, an exemplary description of the above communication method is given: Step 1000: Tunnel 1 (ie, the first tunnel) is established between the UE and the UPF of the core network, and tunnel 2 (ie, the second tunnel) is established between the application server (Server) and the UPF of the core network. With reference to Figure 11, in this example, tunnel 1 is established between the UE and the UPF of the core network, and tunnel 2 is established between the application server and the UPF of the core network, for example, tunnels 1 and 2 are established based on the MASQUE protocol, and tunnels 1 and 2 are used to transmit specific service data flows (SDF, Service data flow), that is, the service data flow indicated by the description information of the specific service data flow. Here, the specific service data flow includes the first service data flow of the aforementioned embodiment. The "service data flow" or "specific service data flow" involved in the following steps has the same meaning as the first service data flow in the aforementioned embodiment, and will not be explained again. Step 1001: UE provides the policy control function PCF in the core network with the association between the description information of the service data flow and the description information of tunnel 1. Here, the correspondence between the description information of the service data flow and the description information of tunnel 1 can be carried by a request message (such as a transmission request message), which is not limited in this step. Step 1002: AF provides the policy control function PCF in the core network with the association between the description information of the service data flow and the description information of tunnel 2. Here, the correspondence between the description information of the service data flow and the description information of tunnel 2 can be carried by a request message (such as a transmission request message), which is not limited in this step. In the above steps 1001 to 1002, the request message of the AF or UE can be sent directly to the PCF, or forwarded to the PCF through other network elements, such as NEF, AMF, SMF. The description information of tunnel 1 and the description information of tunnel 2 are the same as the packet filter set defined in the current 3GPP network, for example, the IP quintuple, IP triplet, etc. used by tunnel 1 and tunnel 2. It should be noted that when executing steps 1001 to 1002, or before executing steps 1001 to 1002, the AF can synchronize the service data flow identifier and the tethered device identifier (ie, the identifier of the first device) with the UE through application layer interaction, which is not elaborated here. In addition, the execution order of the above steps 1001 and 1002 is not limited in this embodiment. Step 1003 to step 1006: PCF sends the description information of tunnel 1 to UPF and / or UE via SMF. Specifically, PCF sends the description information of tunnel 1 to UPF and / or UE via SMF, which may include: PCF sends the description information of tunnel 1 and control information of tunnel 1 to UPF and / or UE via SMF. Because the tunnel in this example is associated with a specific service data flow, the network controls the data belonging to tunnel 1, which is equivalent to controlling the specific service data flow corresponding to the tunnel. Specifically, step 1003: PCF determines the control information of tunnel 1 according to the description information of the service data flow; step 1004: PCF sends the description information of tunnel 1 and the control information of tunnel 1 to SMF. Step 1005: SMF sends the description information of tunnel 1 and the control information of tunnel 1 to UPF. Step 1006: SMF sends the description information of tunnel 1 and the control information of tunnel 1 to UE. The control information may include at least one of QoS parameters, gating parameters, billing parameters, and a flow identifier assigned by the network. For example, when the PCF determines the control information of tunnel 1 according to the description information of the service data flow, the PCF may set different tunnels corresponding to different service data flow identifiers or different tethered device identifiers according to the description information of different service data flows. QoS parameters, etc. Step 1011: For downlink data, the application server carries the description information of tunnel 2 in the header of the downlink data packet and sends it to the UPF. Step 1012: UPF determines the tunnel 1 corresponding to the downlink data packet according to the correspondence between the description information of tunnel 2, the description information of tunnel 1 and the description information of tunnel 2 carried in the header of the downlink data packet. It should also be pointed out that in another possible example, step 1012 can be replaced by: UPF determines the business data flow to which the downlink data packet belongs based on the correspondence between the description information of tunnel 2 carried in the header of the downlink data packet, the description information of the business data flow and the description information of tunnel 2; and determines tunnel 1 corresponding to the downlink data packet based on the association between the business data flow described in the downlink data packet and the description information of tunnel 1. The processing of the above step 1012 may also be referred to as the processing of verifying that the downlink data packet belongs to a valid service data flow. Step 1013: UPF sends the received downlink data packet to the UE through tunnel 1, removes the description information of tunnel 2 in the packet header of the downlink data packet, and adds the description information of tunnel 1 to the packet header of the downlink data packet. UPF performs corresponding data transmission control on the downlink data packet transmitted by tunnel 1, such as QoS control, bit rate control, billing control, and Gating control, and sends the downlink data packet to the terminal through the access network device. In the processing of step 1013, before the UPF performs corresponding data transmission control on the downlink data packet transmitted by tunnel 1, the UPF may also mark the downlink data packet with a flow identifier assigned by the network. Step 1021: For uplink data, the UE determines the service data flow to which the uplink data packet belongs, adds the description information of tunnel 1 to the packet header of the uplink data packet, and performs corresponding data transmission control according to the description information of tunnel 1 obtained from the SMF, such as sending the data of tunnel 1 to the access network device through the corresponding wireless resources (the access network device sends the uplink data packet to the UPF), such as rate control. After the UE determines the service data flow to which the uplink data packet belongs, the following may further be included: the UE verifies that the uplink data packet belongs to a valid service data flow, and so on. Step 1022: After receiving the uplink data packet, UPF determines the tunnel 2 corresponding to the uplink data packet based on the description information of tunnel 1 in the packet header of the uplink data packet and the association between the description information of tunnel 1 and the description information of tunnel 2, removes the description information of tunnel 1 in the packet header of the uplink data packet and adds the description information of tunnel 2. UPF performs corresponding transmission control and sends the received uplink data packet to the application server through tunnel 2. Among them, UPF performs corresponding transmission control including bit rate control, billing control, Gating control, verification that the data packet belongs to a valid business data flow, etc. It should also be pointed out that in another possible example, step 1022 can be replaced by: after receiving the uplink data packet, UPF determines the service data flow to which the uplink data packet belongs based on the description information of tunnel 1 in the header of the uplink data packet, determines the tunnel 2 corresponding to the uplink data packet based on the association between the description information of the service data flow and the description information of tunnel 2, removes the description information of tunnel 1 in the header of the uplink data packet, adds the description information of tunnel 2, and UPF performs corresponding transmission control to send the received uplink data packet to the application server through tunnel 2. In the above example, UE / application server (AF) establishes tunnels with UPF respectively, and UE / AF provides PCF with the corresponding relationship between the service data flow description information and the description information of tunnel 1 and the description information of tunnel 2 respectively. The application server carries the description information of tunnel 2 in the header of the downlink data packet and sends it to UPF. UPF determines the service data flow to which the data belongs, removes the header of tunnel 2, and adds the header of tunnel 1. UPF performs corresponding transmission control on the downlink data packet transmitted by tunnel 1. UE determines the service data flow to which the uplink data packet belongs, performs corresponding transmission control, and adds the description information of tunnel 1 to the header of the uplink data packet; UPF determines the service data flow to which the uplink data packet belongs, removes the description information of tunnel 1 carried in the header of the uplink data packet, and adds the description information of tunnel 2. In this way, a specific business data flow is transmitted through a specific tunnel. The control of the tunnel is the control of the business data flow. The 3GPP network only needs to identify the tunnel to know the business data flow to which the data transmitted in the tunnel belongs. For the transmission protocol (unstructured data) that the 3GPP network cannot recognize, or for the application that packages multiple business flows together and encrypts them for transmission, or for multiple tethered devices accessing the network through the same UE, the purpose of distinguishing the business data flows and controlling them can be achieved by controlling each tunnel. FIG12 is a schematic diagram of a structure of a terminal according to an embodiment of the present application, including: The first processing unit 1201 is configured to determine, based on description information of a first service data flow, that an uplink data packet belongs to the first service data flow, wherein the description information of the first service data flow includes at least one of the following: an identifier of the first service data flow and an identifier of a first device; The first communication unit 1202 is used to transmit the uplink data packet to the first core network element. The first processing unit is used to perform at least one of the following: receiving an uplink data packet sent by the first device through the first communication unit, and determining that the uplink data packet belongs to the first business data flow when the description information of the first business data flow includes the identifier of the first device; and determining that the uplink data packet belongs to the first business data flow when the flow identifier carried by the uplink data packet matches the identifier of the first business data flow in the description information of the first business data flow. The first processing unit is used to add at least one of the following to the header of the uplink data packet: an identifier of the first service data flow and an identifier of the first device. The first communication unit is used to receive a filter of a first service data flow sent by a second core network network element. The first communication unit is used to send a transmission request message of the first service data flow to the second core network element, and the transmission request message carries the filter of the first service data flow. The filter of the first service data flow includes description information of the first service data flow. The first communication unit is used to transmit the uplink data packet to the first core network element based on control information associated with the first service data flow. The first communication unit is used to receive control information associated with the first service data flow sent by the second core network network element. The control information associated with the first business data flow includes at least one of the following: wireless resources associated with the first business data flow, the bit rate associated with the first business data flow, the quality of service QoS parameters associated with the first business data flow, the gateway parameters associated with the first business data flow, the billing parameters associated with the first business data flow, and the data flow identifier associated with the first business data flow. The data flow identifier associated with the first service data flow includes at least one of the following: an identifier of the first service data flow, and a QoS flow identifier associated with the first service data flow. The second core network element includes at least one of the following: a mobility management network element, a session management network element, and a policy control network element. The first core network element includes a user plane network element. FIG13 is a schematic diagram of a composition structure of a first core network element according to an embodiment of the present application, including: The second communication unit 1301 is used to receive a data packet and transmit the data packet; The second processing unit 1302 is used to determine that the data packet belongs to the first business data flow based on the description information of the first business data flow, wherein the description information of the first business data flow includes at least one of the following: an identifier of the first business data flow and an identifier of the first device. The second processing unit is used to perform at least one of the following: determining that the data packet belongs to the first business data flow when the identifier of the business data flow carried in the packet header of the data packet is the same as the identifier of the first business data flow in the description information of the first business data flow; determining that the data packet belongs to the first business data flow when the identifier of the device carried in the packet header of the data packet is the same as the identifier of the first device in the description information of the first business data flow. The second communication unit is used to receive a filter of a first service data flow sent by a second core network network element, wherein the filter of the first service data flow includes description information of the first service data flow. The data packet is an uplink data packet. The second communication unit is used to receive the uplink data packet transmitted by the terminal; and transmit the uplink data packet to the application server based on the control information associated with the first service data flow. The data packet is a downlink data packet. The second communication unit is used to receive the downlink data packet transmitted by the application server; and transmit the downlink data packet to the terminal based on the control information associated with the first service data flow. The second communication unit is used to receive control information associated with the first service data flow sent by the second core network network element. The control information associated with the first business data flow includes at least one of the following: wireless resources associated with the first business data flow, the bit rate associated with the first business data flow, the quality of service QoS parameters associated with the first business data flow, the gateway parameters associated with the first business data flow, the billing parameters associated with the first business data flow, and the data flow identifier associated with the first business data flow. The data flow identifier associated with the first service data flow includes at least one of the following: an identifier of the first service data flow, and a QoS flow identifier associated with the first service data flow. The second core network element includes at least one of the following: a mobility management network element, a session management network element, and a policy control network element. The first core network element includes a user plane network element. The present application also provides a terminal, including: The first communication unit is used to transmit an uplink data packet through a first tunnel, wherein a header of the uplink data packet carries description information of the first tunnel, and the first tunnel is a tunnel between the terminal and a first core network element. The terminal also includes: a first processing unit, used to determine that the uplink data packet belongs to the first business data flow based on the description information of the first business data flow; based on the association between the description information of the first business data flow and the description information of the first tunnel, determine that the uplink data packet corresponds to the first tunnel, wherein the description information of the first business data flow includes at least one of the following: an identifier of the first business data flow and an identifier of the first device. The first processing unit is used to perform at least one of the following: receiving an uplink data packet sent by the first device through the first communication unit, and determining that the uplink data packet belongs to the first business data flow when the description information of the first business data flow includes the identifier of the first device; and determining that the uplink data packet belongs to the first business data flow when the flow identifier carried by the uplink data packet matches the identifier of the first business data flow in the description information of the first business data flow. The first communication unit is used to send first information to the second core network element, wherein the first information is used to indicate the association relationship between the description information of the first service data flow and the description information of the first tunnel. The first communication unit is used to transmit an uplink data packet through the first tunnel based on control information of the first tunnel. The first communication unit is used to receive second information sent by a second core network element, wherein the second information includes: control information of the first tunnel, and an association relationship between the control information of the first tunnel and description information of the first tunnel. The control information of the first tunnel includes at least one of the following: wireless resources associated with the first tunnel, a bit rate associated with the first tunnel, a quality of service QoS parameter associated with the first tunnel, a gateway parameter associated with the first tunnel, a billing parameter associated with the first tunnel, and a data flow identifier associated with the first tunnel. The description information of the first tunnel includes at least one of the following: an Internet Protocol IP quintuple corresponding to the first tunnel, and an IP triplet corresponding to the first tunnel. The second core network element includes at least one of the following: a mobility management network element, a session management network element, and a policy control network element. The first core network element includes a user plane network element. The embodiment of the present application further provides a first core network element, including: A second communication unit is used to receive an uplink data packet, wherein a header of the uplink data packet carries description information of a first tunnel, and the first tunnel is a tunnel between a terminal and the first core network element; and transmit the uplink data packet through a second tunnel, wherein a header of the uplink data packet carries description information of the second tunnel, and the second tunnel is a tunnel between the first core network element and an application server. The first core network element further includes: a second processing unit, configured to replace the description information of the first tunnel carried in the header of the uplink data packet with the description information of the second tunnel. The second tunnel is determined based on an association relationship between the description information of the first tunnel and the description information of the second tunnel. The second communication unit is used to receive third information sent by a second core network element, wherein the third information is used to indicate an association relationship between the description information of the first tunnel and the description information of the second tunnel. The second tunnel is determined based on the first business data flow to which the uplink data packet belongs, and the association between the description information of the second tunnel and the description information of the first business data flow, wherein the first business data flow is determined based on the association between the description information of the first tunnel and the description information of the first business data flow. The second communication unit is used to receive fourth information sent by a second core network network element, wherein the fourth information is used to indicate an association relationship between the description information of the second tunnel and the description information of the first service data flow, and an association relationship between the description information of the first tunnel and the description information of the first service data flow. The description information of the first service data flow includes at least one of the following: an identifier of the first service data flow and an identifier of the first device. The description information of the first tunnel includes at least one of the following: an Internet Protocol IP quintuple corresponding to the first tunnel, an IP triplet corresponding to the first tunnel; The description information of the second tunnel includes at least one of the following: an Internet Protocol IP quintuple corresponding to the second tunnel, and an IP triplet corresponding to the second tunnel. The second communication unit is used to transmit the uplink data packet through the second tunnel based on the control information of the first tunnel. The second communication unit is used to receive fifth information sent by the second core network element, wherein the fifth information includes: control information of the first tunnel, and an association relationship between the control information of the first tunnel and description information of the first tunnel. The control information of the first tunnel includes at least one of the following: wireless resources associated with the first tunnel, a bit rate associated with the first tunnel, a quality of service QoS parameter associated with the first tunnel, a gateway parameter associated with the first tunnel, a billing parameter associated with the first tunnel, and a data flow identifier associated with the first tunnel. The second core network element includes at least one of the following: a mobility management network element, a session management network element, and a policy control network element. The first core network element includes a user plane network element. The embodiment of the present application further provides a first core network element, including: The second communication unit is used to receive a downlink data packet, wherein the header of the downlink data packet carries description information of a second tunnel, and the second tunnel is a tunnel between the first core network element and the application server; and transmit a downlink data packet through the first tunnel, wherein the header of the downlink data packet carries description information of the first tunnel, and the first tunnel is a tunnel between a terminal and the first core network element. The first core network element further includes: a second processing unit, configured to replace the description information of the second tunnel carried in the header of the downlink data packet with the description information of the first tunnel. The first tunnel is determined based on an association relationship between the description information of the first tunnel and the description information of the second tunnel. The second communication unit is used to receive third information sent by a second core network element, wherein the third information is used to indicate an association relationship between the description information of the first tunnel and the description information of the second tunnel. The first tunnel is determined based on the association between the first service data flow to which the downlink data packet belongs, the description information of the first tunnel and the description information of the first service data flow, wherein the first service data flow is determined based on the description information of the second tunnel. The information is determined by the association relationship between the information and the description information of the first business data flow. The second communication unit is used to receive fourth information sent by a second core network network element, wherein the fourth information is used to indicate an association relationship between the description information of the second tunnel and the description information of the first service data flow, and an association relationship between the description information of the first tunnel and the description information of the first service data flow. The description information of the first service data flow includes at least one of the following: an identifier of the first service data flow and an identifier of the first device. The description information of the first tunnel includes at least one of the following: an Internet Protocol IP quintuple corresponding to the first tunnel, an IP triplet corresponding to the first tunnel; The description information of the second tunnel includes at least one of the following: an Internet Protocol IP quintuple corresponding to the second tunnel, and an IP triplet corresponding to the second tunnel. The second communication unit is used to transmit a downlink data packet through the first tunnel based on the control information of the first tunnel. The second communication unit is used to receive fifth information sent by the second core network element, wherein the fifth information includes: control information of the first tunnel, and an association relationship between the control information of the first tunnel and description information of the first tunnel. The control information of the first tunnel includes at least one of the following: wireless resources associated with the first tunnel, a bit rate associated with the first tunnel, a quality of service QoS parameter associated with the first tunnel, a gateway parameter associated with the first tunnel, a billing parameter associated with the first tunnel, and a data flow identifier associated with the first tunnel. The second core network element includes at least one of the following: a mobility management network element, a session management network element, and a policy control network element. The first core network element includes a user plane network element. The device of the embodiment of the present application can implement the corresponding functions of each device in the aforementioned authentication method embodiment. The processes, functions, implementation methods and beneficial effects corresponding to each module (sub-module, unit or component, etc.) in the terminal or the first core network 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 of the embodiment of the application or each module (sub-module, unit or component, etc.) in the first core network network element can be implemented by different modules (sub-module, unit or component, etc.) or by the same module (sub-module, unit or component, etc.). FIG. 14 is a schematic structural diagram of a communication device 1400 according to an embodiment of the present application. The communication device 1400 includes a processor 1410, and the processor 1410 can call and run a computer program from a memory so that the communication device 1400 implements the method in the embodiment of the present application. In a possible implementation, the communication device 1400 may also include a memory 1420. Among them, the processor 1410 can call and run a computer program from the memory 1420 so that the communication device 1400 implements the method in the embodiment of the present application. Among them, the memory 1420 may be a separate device independent of the processor 1410, or it may be integrated in the processor 1410. In a possible implementation, the communication device 1400 may also include a transceiver 1430, and the processor 1410 may control the transceiver 1430 to communicate with other devices, specifically, it may send information or data to other devices, or receive information or data sent by other devices. Among them, the transceiver 1430 may include a transmitter and a receiver. The transceiver 1430 may further include an antenna, and the number of antennas may be one or more. In one possible implementation, the communication device 1400 may be a terminal of an embodiment of the present application, or a first core network element, and the communication device 1400 may implement the corresponding processes implemented by the terminal or the first core network element in each method of the embodiment of the present application, which will not be repeated here for the sake of brevity. FIG15 is a schematic structural diagram of a chip 1500 according to an embodiment of the present application. The chip 1500 includes a processor 1510, and the processor 1510 can call and run a computer program from a memory to implement the method in the embodiment of the present application. In a possible implementation, the chip 1500 may also include a memory 1520. Among them, the processor 1510 can call and run a computer program from the memory 1520 to implement the method executed by the terminal or the first core network element in the embodiment of the present application. Among them, the memory 1520 can be a separate device independent of the processor 1510, or it can be integrated in the processor 1510. In a possible implementation, the chip 1500 may also include an input interface 1530. Among them, the processor 1510 can control the input interface 1530 to communicate with other devices or chips, specifically, it can obtain information or data sent by other devices or chips. In a possible implementation, the chip 1500 may also include an output interface 1540. The processor 1510 may control the output interface 1540 to communicate with other devices or chips, and specifically, may output information or data to other devices or chips. In a possible implementation, the chip can be applied to the terminal or the first core network element in the embodiment of the present application, and the chip can implement the corresponding processes implemented by the terminal or the first core network element in each method of the embodiment of the present application. For the sake of brevity, it will not be repeated 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 above-mentioned processor can be a general-purpose processor, a digital signal processor (digital signal processor, DSP), a field programmable gate array (field programmable gate array, FPGA), an application specific integrated circuit (application specific integrated circuit, ASIC) or other programmable logic devices, transistor logic devices, discrete hardware components, etc. Among them, the above-mentioned general-purpose processor can be a microprocessor or any conventional processor, etc. The above-mentioned memory 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 (read-only memory, ROM), a programmable read-only memory (programmable ROM, PROM), an erasable Programmable read-only memory (erasable PROM, EPROM), electrically erasable programmable read-only memory (electrically EPROM, EEPROM) or flash memory. Volatile memory can be random access memory (random access memory, RAM). It should be understood that the above memory is exemplary but not restrictive. For example, the memory in the embodiment of the present application can also be static random access memory (static RAM, SRAM), dynamic random access memory (dynamic RAM, DRAM), synchronous dynamic random access memory (synchronous DRAM, SDRAM), double data rate synchronous dynamic random access memory (double data rate SDRAM, DDR SDRAM), enhanced synchronous dynamic random access memory (enhanced SDRAM, ESDRAM), synchronous link dynamic random access memory (synch link DRAM, SLDRAM) and direct memory bus random access memory (Direct Rambus RAM, DR RAM) and the like. That is to say, 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. FIG16 is a schematic block diagram of a communication system 1600 according to an embodiment of the present application. The communication system 1600 includes a terminal 1610 and a first core network element 1620. The terminal 1610 can be used to implement the corresponding functions implemented by the terminal in the above method. The first core network element 1620 can be used to implement the corresponding functions implemented by the first core network element in the above method. For the sake of brevity, it will not be repeated here. In the above embodiments, it can be implemented in whole or in part by software, hardware, firmware or any combination thereof. When implemented using software, 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 instruction is 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 instruction 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 instruction can be transmitted from a website site, computer, server or data center by wired (e.g., coaxial cable, optical fiber, digital subscriber line (Digital Subscriber Line, DSL)) or wireless (e.g., infrared, wireless, microwave, etc.) mode to another website site, 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, data center, etc. that contains 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)). It should be understood that in various embodiments of the present application, the size of the sequence number of each process 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 simplicity 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 technician familiar with the technical field can easily think of changes or replacements within the technical scope disclosed in the present application, which should be covered within 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 determines, based on the description information of the first service data flow, that the uplink data packet belongs to the first service data flow, wherein the description information of the first service data flow includes at least one of the following: an identifier of the first service data flow and an identifier of the first device; The terminal transmits the uplink data packet to the first core network element.

2. The method according to claim 1, wherein: The terminal determines, based on the description information of the first service data flow, that the uplink data packet belongs to the first service data flow, including at least one of the following: The terminal receives an uplink data packet sent by a first device, and determines that the uplink data packet belongs to the first service data flow when the description information of the first service data flow includes an identifier of the first device; The terminal determines that the uplink data packet belongs to the first service data flow when the flow identifier carried by the uplink data packet matches the identifier of the first service data flow in the description information of the first service data flow.

3. The method according to claim 1 or 2, wherein: Before the terminal transmits the uplink data packet to the first core network element, the method further includes: The terminal adds at least one of the following to the header of the uplink data packet: an identifier of the first service data flow and an identifier of the first device.

4. The method according to any one of claims 1 to 3, wherein: Before the terminal determines, based on the description information of the first service data flow, that the uplink data packet belongs to the first service data flow, the method further includes: The terminal receives a filter for a first service data flow sent by a second core network network element.

5. The method according to any one of claims 1 to 4, wherein: Before the terminal determines, based on the description information of the first service data flow, that the uplink data packet belongs to the first service data flow, the method further includes: The terminal sends a transmission request message of the first service data flow to the second core network element, and the transmission request message carries the filter of the first service data flow.

6. The method according to claim 4 or 5, wherein: The filter of the first service data flow includes description information of the first service data flow.

7. The method according to any one of claims 1 to 6, wherein: The terminal transmits an uplink data packet to the first core network element, including: The terminal transmits the uplink data packet to the first core network element based on the control information associated with the first service data flow.

8. The method according to any one of claims 1 to 7, wherein: Before the terminal determines, based on the description information of the first service data flow, that the uplink data packet belongs to the first service data flow, the method further includes: The terminal receives control information associated with the first service data flow sent by the second core network network element.

9. The method according to claim 7 or 8, wherein: The control information associated with the first business data flow includes at least one of the following: wireless resources associated with the first business data flow, the bit rate associated with the first business data flow, the quality of service QoS parameters associated with the first business data flow, the gateway parameters associated with the first business data flow, the billing parameters associated with the first business data flow, and the data flow identifier associated with the first business data flow.

10. The method according to claim 9, wherein: The data flow identifier associated with the first service data flow includes at least one of the following: an identifier of the first service data flow, and a QoS flow identifier associated with the first service data flow.

11. The method according to any one of claims 4 to 6 and 8, wherein: The second core network element includes at least one of the following: a mobility management network element, a session management network element, and a policy control network element.

12. The method according to any one of claims 1 to 11, wherein: The first core network element includes a user plane network element.

13. A communication method, comprising: The first core network element receives the data packet; The first core network element determines, based on the description information of the first service data flow, that the data packet belongs to the first service data flow, wherein the description information of the first service data flow includes at least one of the following: an identifier of the first service data flow and an identifier of the first device; The first core network element transmits the data packet.

14. The method according to claim 13, wherein: The first core network element determines, based on the description information of the first service data flow, that the data packet belongs to the first service data flow, including at least one of the following: The first core network network element determines, when the identifier of the service data flow carried in the header of the data packet is the same as the identifier of the first service data flow in the description information of the first service data flow, that the data packet belongs to the first service data flow; The first core network network element determines that the data packet belongs to the first service data flow when the device identifier carried in the header of the data packet is the same as the identifier of the first device in the description information of the first service data flow.

15. The method according to claim 13 or 14, wherein: Before the first core network element receives the data packet, the method further includes: The first core network element receives a filter for a first service data flow sent by a second core network element, wherein the first service The filter of the data flow includes description information of the first service data flow.

16. The method according to any one of claims 13 to 15, wherein: The data packet is an uplink data packet.

17. The method according to claim 16, wherein: The first core network network element receiving the data packet includes: the first core network network element receiving the uplink data packet transmitted by the terminal; The first core network network element transmits the data packet, including: the first core network network element transmits the uplink data packet to the application server based on control information associated with the first service data flow.

18. The method according to any one of claims 13 to 15, wherein: The data packet is a downlink data packet.

19. The method according to claim 18, wherein: The first core network element receiving the data packet includes: the first core network element receiving the downlink data packet transmitted by the application server; The first core network element transmits the data packet, including: the first core network element transmits the downlink data packet to the terminal based on control information associated with the first service data flow.

20. The method according to any one of claims 13 to 19, wherein: Before the first core network element receives the data packet, the method further includes: The first core network network element receives control information associated with a first service data flow sent by a second core network network element.

21. The method according to any one of claims 17, 19 and 20, wherein: The control information associated with the first business data flow includes at least one of the following: wireless resources associated with the first business data flow, the bit rate associated with the first business data flow, the quality of service QoS parameters associated with the first business data flow, the gateway parameters associated with the first business data flow, the billing parameters associated with the first business data flow, and the data flow identifier associated with the first business data flow.

22. The method according to claim 21, wherein: The data flow identifier associated with the first service data flow includes at least one of the following: an identifier of the first service data flow, and a QoS flow identifier associated with the first service data flow.

23. The method according to claim 15 or 21, wherein: The second core network element includes at least one of the following: a mobility management network element, a session management network element, and a policy control network element.

24. The method according to any one of claims 13 to 23, wherein: The first core network element includes a user plane network element.

25. A communication method, comprising: The terminal transmits an uplink data packet through a first tunnel, wherein a header of the uplink data packet carries description information of the first tunnel, and the first tunnel is a tunnel between the terminal and a first core network element.

26. The method according to claim 25, wherein: Before the terminal transmits the uplink data packet through the first tunnel, the method further includes: The terminal determines, based on the description information of the first service data flow, that the uplink data packet belongs to the first service data flow; The terminal determines that the uplink data packet corresponds to the first tunnel based on the association between the description information of the first business data flow and the description information of the first tunnel, wherein the description information of the first business data flow includes at least one of the following: an identifier of the first business data flow and an identifier of the first device.

27. The method according to claim 26, wherein: The terminal determines, based on the description information of the first service data flow, that the uplink data packet belongs to the first service data flow, including at least one of the following: The terminal receives an uplink data packet sent by a first device, and determines that the uplink data packet belongs to the first service data flow when the description information of the first service data flow includes an identifier of the first device; The terminal determines that the uplink data packet belongs to the first service data flow when the flow identifier carried by the uplink data packet matches the identifier of the first service data flow in the description information of the first service data flow.

28. The method according to claim 26 or 27, wherein: Before the terminal transmits the uplink data packet through the first tunnel, the method further includes: The terminal sends first information to the second core network element, wherein the first information is used to indicate an association relationship between the description information of the first service data flow and the description information of the first tunnel.

29. The method according to any one of claims 25 to 28, wherein: The terminal transmits an uplink data packet through a first tunnel, including: The terminal transmits an uplink data packet through the first tunnel based on the control information of the first tunnel.

30. The method according to any one of claims 25 to 29, wherein: Before the terminal transmits the uplink data packet through the first tunnel, the method further includes: The terminal receives second information sent by a second core network element, wherein the second information includes: control information of the first tunnel, and an association relationship between the control information of the first tunnel and description information of the first tunnel.

31. The method according to claim 29 or 30, wherein: The control information of the first tunnel includes at least one of the following: wireless resources associated with the first tunnel, a bit rate associated with the first tunnel, a quality of service QoS parameter associated with the first tunnel, a gateway parameter associated with the first tunnel, a billing parameter associated with the first tunnel, and a data flow identifier associated with the first tunnel.

32. The method according to any one of claims 25 to 31, wherein: The description information of the first tunnel includes at least one of the following: an Internet Protocol IP quintuple corresponding to the first tunnel, and an IP triplet corresponding to the first tunnel.

33. The method according to claim 28 or 30, wherein: The second core network element includes at least one of the following: a mobility management network element, a session management network element, and a policy control network element.

34. The method according to any one of claims 25 to 33, wherein: The first core network element includes a user plane network element.

35. A communication method, comprising: The first core network element receives an uplink data packet, wherein a header of the uplink data packet carries description information of a first tunnel, and the first tunnel is a tunnel between a terminal and the first core network element; The first core network element transmits the uplink data packet through a second tunnel, wherein a header of the uplink data packet carries description information of the second tunnel, and the second tunnel is a tunnel between the first core network element and an application server.

36. The method of claim 35, wherein: Before the first core network element transmits the uplink data packet through the second tunnel, the method further includes: The first core network element replaces the description information of the first tunnel carried in the header of the uplink data packet with the description information of the second tunnel.

37. The method according to claim 35 or 36, wherein: The second tunnel is determined based on an association relationship between the description information of the first tunnel and the description information of the second tunnel.

38. The method according to any one of claims 35 to 37, wherein: Before the first core network element receives the uplink data packet, the method further includes: The first core network element receives third information sent by the second core network element, wherein the third information is used to indicate an association relationship between the description information of the first tunnel and the description information of the second tunnel.

39. The method according to claim 37 or 38, wherein: The second tunnel is determined based on the first business data flow to which the uplink data packet belongs, and the association between the description information of the second tunnel and the description information of the first business data flow, wherein the first business data flow is determined based on the association between the description information of the first tunnel and the description information of the first business data flow.

40. The method according to any one of claims 35, 36 and 39, wherein: Before the first core network element receives the uplink data packet, the method further includes: The first core network element receives fourth information sent by the second core network element, wherein the fourth information is used to indicate an association relationship between the description information of the second tunnel and the description information of the first service data flow, and an association relationship between the description information of the first tunnel and the description information of the first service data flow.

41. The method according to claim 39 or 40, wherein: The description information of the first service data flow includes at least one of the following: an identifier of the first service data flow and an identifier of the first device.

42. The method according to any one of claims 35 to 41, wherein: The description information of the first tunnel includes at least one of the following: an Internet Protocol IP quintuple corresponding to the first tunnel, an IP triplet corresponding to the first tunnel; The description information of the second tunnel includes at least one of the following: an Internet Protocol IP quintuple corresponding to the second tunnel, and an IP triplet corresponding to the second tunnel.

43. The method according to any one of claims 35 to 42, wherein: The first core network element transmitting an uplink data packet through the second tunnel includes: The first core network element transmits the uplink data packet through the second tunnel based on the control information of the first tunnel.

44. The method according to any one of claims 35 to 43, wherein: Before the first core network element receives the uplink data packet, the method further includes: The first core network element receives fifth information sent by the second core network element, wherein the fifth information includes: control information of the first tunnel, and an association between the control information of the first tunnel and description information of the first tunnel.

45. The method according to claim 43 or 44, wherein: The control information of the first tunnel includes at least one of the following: wireless resources associated with the first tunnel, a bit rate associated with the first tunnel, a quality of service QoS parameter associated with the first tunnel, a gateway parameter associated with the first tunnel, a billing parameter associated with the first tunnel, and a data flow identifier associated with the first tunnel.

46. ​​The method according to any one of claims 38, 40, and 44, wherein: The second core network element includes at least one of the following: a mobility management network element, a session management network element, and a policy control network element.

47. The method according to any one of claims 35 to 46, wherein: The first core network element includes a user plane network element.

48. A communication method, comprising: The first core network element receives a downlink data packet, wherein a header of the downlink data packet carries description information of a second tunnel, and the second tunnel is a tunnel between the first core network element and an application server; The first core network element transmits a downlink data packet through a first tunnel, wherein a header of the downlink data packet carries description information of the first tunnel, and the first tunnel is a tunnel between a terminal and the first core network element.

49. The method of claim 48, wherein: Before the first core network element transmits the downlink data packet through the first tunnel, the method further includes: The first core network element replaces the description information of the second tunnel carried in the header of the downlink data packet with the description information of the first tunnel.

50. The method of claim 48 or 49, wherein: The first tunnel is determined based on an association relationship between the description information of the first tunnel and the description information of the second tunnel.

51. The method according to any one of claims 48 to 50, wherein: Before the first core network element receives the downlink data packet, the method further includes: The first core network element receives third information sent by the second core network element, wherein the third information is used to indicate an association relationship between the description information of the first tunnel and the description information of the second tunnel.

52. The method of claim 48 or 49, wherein: The first tunnel is determined based on the first business data flow to which the downlink data packet belongs, and the association between the description information of the first tunnel and the description information of the first business data flow, wherein the first business data flow is determined based on the association between the description information of the second tunnel and the description information of the first business data flow.

53. The method according to any one of claims 48, 49 and 52, wherein: Before the first core network element receives the downlink data packet, the method further includes: The first core network element receives fourth information sent by the second core network element, wherein the fourth information is used to indicate an association relationship between the description information of the second tunnel and the description information of the first service data flow, and an association relationship between the description information of the first tunnel and the description information of the first service data flow.

54. The method of claim 52 or 53, wherein: The description information of the first service data flow includes at least one of the following: an identifier of the first service data flow and an identifier of the first device.

55. The method according to any one of claims 48 to 54, wherein: The description information of the first tunnel includes at least one of the following: an Internet Protocol IP quintuple corresponding to the first tunnel, an IP triplet corresponding to the first tunnel; The description information of the second tunnel includes at least one of the following: an Internet Protocol IP quintuple corresponding to the second tunnel, and an IP triplet corresponding to the second tunnel.

56. The method according to any one of claims 48 to 55, wherein: The first core network element transmits a downlink data packet through a first tunnel, including: The first core network element transmits a downlink data packet through the first tunnel based on the control information of the first tunnel.

57. The method according to any one of claims 48 to 56, wherein: Before the first core network element receives the downlink data packet, the method further includes: The first core network element receives fifth information sent by the second core network element, wherein the fifth information includes: control information of the first tunnel, and an association between the control information of the first tunnel and description information of the first tunnel.

58. The method according to any one of claims 48 to 57, wherein: The control information of the first tunnel includes at least one of the following: wireless resources associated with the first tunnel, a bit rate associated with the first tunnel, a quality of service QoS parameter associated with the first tunnel, a gateway parameter associated with the first tunnel, a billing parameter associated with the first tunnel, and a data flow identifier associated with the first tunnel.

59. The method according to any one of claims 51, 53, and 57, wherein: The second core network element includes at least one of the following: a mobility management network element, a session management network element, and a policy control network element.

60. The method according to any one of claims 48 to 59, wherein: The first core network element includes a user plane network element.

61. A terminal, comprising: A first processing unit, configured to determine, based on description information of a first service data flow, that an uplink data packet belongs to the first service data flow, wherein the description information of the first service data flow includes at least one of the following: an identifier of the first service data flow and an identifier of a first device; The first communication unit is used to transmit the uplink data packet to the first core network element.

62. The terminal according to claim 61, wherein: The first processing unit is configured to perform at least one of the following: receiving an uplink data packet sent by a first device through the first communication unit, and determining that the uplink data packet belongs to the first service data flow when the description information of the first service data flow includes an identifier of the first device; When the flow identifier carried by the uplink data packet matches the identifier of the first service data flow in the description information of the first service data flow, it is determined that the uplink data packet belongs to the first service data flow.

63. The terminal according to claim 61 or 62, wherein: The first processing unit is used to add at least one of the following to the header of the uplink data packet: an identifier of the first service data flow and an identifier of the first device.

64. The terminal according to any one of claims 61 to 63, wherein: The first communication unit is used to receive a filter of a first service data flow sent by a second core network network element.

65. The terminal according to any one of claims 61 to 64, wherein: The first communication unit is used to send a transmission request message of the first service data flow to the second core network element, and the transmission request message carries the filter of the first service data flow.

66. The terminal according to claim 64 or 65, wherein: The filter of the first service data flow includes description information of the first service data flow.

67. The terminal according to any one of claims 61 to 66, wherein: The first communication unit is used to transmit the uplink data packet to the first core network element based on control information associated with the first service data flow.

68. The terminal according to any one of claims 61 to 67, wherein: The first communication unit is used to receive control information associated with the first service data flow sent by the second core network network element.

69. The terminal according to claim 67 or 68, wherein: The control information associated with the first business data flow includes at least one of the following: wireless resources associated with the first business data flow, the bit rate associated with the first business data flow, the quality of service QoS parameters associated with the first business data flow, the gateway parameters associated with the first business data flow, the billing parameters associated with the first business data flow, and the data flow identifier associated with the first business data flow.

70. The terminal according to claim 69, wherein: The data flow identifier associated with the first service data flow includes at least one of the following: an identifier of the first service data flow, and a QoS flow identifier associated with the first service data flow.

71. The terminal according to any one of claims 64-66 and 68, wherein: The second core network element includes at least one of the following: a mobility management network element, a session management network element, and a policy control network element.

72. The terminal according to any one of claims 61 to 71, wherein: The first core network element includes a user plane network element.

73. A first core network element, comprising: A second communication unit, configured to receive a data packet; transmitting the data packet; The second processing unit is used to determine that the data packet belongs to the first business data flow based on the description information of the first business data flow, wherein the description information of the first business data flow includes at least one of the following: an identifier of the first business data flow and an identifier of the first device.

74. The first core network element according to claim 73, wherein: The second processing unit is configured to perform at least one of the following: determining that the data packet belongs to the first business data flow when the identifier of the business data flow carried in the header of the data packet is the same as the identifier of the first business data flow in the description information of the first business data flow; When the device identifier carried in the header of the data packet is the same as the identifier of the first device in the description information of the first service data flow, it is determined that the data packet belongs to the first service data flow.

75. The first core network element according to claim 73 or 74, wherein: The second communication unit is used to receive a filter of a first service data flow sent by a second core network network element, wherein the filter of the first service data flow includes description information of the first service data flow.

76. The first core network element according to any one of claims 73 to 75, wherein: The data packet is an uplink data packet.

77. The first core network element according to claim 76, wherein: The second communication unit is used to receive the uplink data packet transmitted by the terminal; and transmit the uplink data packet to the application server based on the control information associated with the first service data flow.

78. The first core network element according to any one of claims 73 to 75, wherein: The data packet is a downlink data packet.

79. The first core network element according to claim 78, wherein: The second communication unit is used to receive the downlink data packet transmitted by the application server; and transmit the downlink data packet to the terminal based on the control information associated with the first service data flow.

80. The first core network element according to any one of claims 73 to 79, wherein: The second communication unit is used to receive control information associated with the first service data flow sent by the second core network network element.

81. The first core network element according to any one of claims 77, 79 and 80, wherein: The control information associated with the first business data flow includes at least one of the following: wireless resources associated with the first business data flow, the bit rate associated with the first business data flow, the quality of service QoS parameters associated with the first business data flow, the gateway parameters associated with the first business data flow, the billing parameters associated with the first business data flow, and the data flow identifier associated with the first business data flow.

82. The first core network element according to claim 81, wherein: The data flow identifier associated with the first service data flow includes at least one of the following: an identifier of the first service data flow, and a QoS flow identifier associated with the first service data flow.

83. The first core network element according to claim 75 or 81, wherein: The second core network element includes at least one of the following: a mobility management network element, a session management network element, and a policy control network element.

84. The first core network element according to any one of claims 73 to 83, wherein: The first core network element includes a user plane network element.

85. A terminal comprising: The first communication unit is used to transmit an uplink data packet through a first tunnel, wherein a header of the uplink data packet carries description information of the first tunnel, and the first tunnel is a tunnel between the terminal and a first core network element.

86. The terminal according to claim 85, wherein: The terminal further includes: The first processing unit is configured to determine, based on the description information of the first service data flow, that the uplink data packet belongs to the first service data flow; and determine, based on the association between the description information of the first service data flow and the description information of the first tunnel, that the uplink data packet belongs to the first service data flow. The data packet corresponds to the first tunnel, wherein the description information of the first service data flow includes at least one of the following: an identifier of the first service data flow and an identifier of the first device.

87. The terminal according to claim 86, wherein: The first processing unit is configured to perform at least one of the following: receiving an uplink data packet sent by a first device through the first communication unit, and determining that the uplink data packet belongs to the first service data flow when the description information of the first service data flow includes an identifier of the first device; When the flow identifier carried by the uplink data packet matches the identifier of the first service data flow in the description information of the first service data flow, it is determined that the uplink data packet belongs to the first service data flow.

88. The terminal according to claim 86 or 87, wherein: The first communication unit is used to send first information to the second core network element, wherein the first information is used to indicate the association relationship between the description information of the first service data flow and the description information of the first tunnel.

89. The terminal according to any one of claims 85 to 88, wherein: The first communication unit is used to transmit an uplink data packet through the first tunnel based on control information of the first tunnel.

90. The terminal according to any one of claims 85 to 89, wherein: The first communication unit is used to receive second information sent by a second core network element, wherein the second information includes: control information of the first tunnel, and an association relationship between the control information of the first tunnel and description information of the first tunnel.

91. The terminal according to claim 89 or 90, wherein: The control information of the first tunnel includes at least one of the following: wireless resources associated with the first tunnel, a bit rate associated with the first tunnel, a quality of service QoS parameter associated with the first tunnel, a gateway parameter associated with the first tunnel, a billing parameter associated with the first tunnel, and a data flow identifier associated with the first tunnel.

92. The terminal according to any one of claims 85 to 91, wherein: The description information of the first tunnel includes at least one of the following: an Internet Protocol IP quintuple corresponding to the first tunnel, and an IP triplet corresponding to the first tunnel.

93. The terminal according to claim 88 or 90, wherein: The second core network element includes at least one of the following: a mobility management network element, a session management network element, and a policy control network element.

94. The terminal according to any one of claims 85 to 93, wherein: The first core network element includes a user plane network element.

95. A first core network element, comprising: A second communication unit is used to receive an uplink data packet, wherein a header of the uplink data packet carries description information of a first tunnel, and the first tunnel is a tunnel between a terminal and the first core network element; and transmit the uplink data packet through a second tunnel, wherein a header of the uplink data packet carries description information of the second tunnel, and the second tunnel is a tunnel between the first core network element and an application server.

96. The first core network element according to claim 95, wherein: Also includes: The second processing unit is configured to replace the description information of the first tunnel carried in the header of the uplink data packet with the description information of the second tunnel.

97. The first core network element according to claim 95 or 96, wherein: The second tunnel is determined based on an association relationship between the description information of the first tunnel and the description information of the second tunnel.

98. The first core network element according to any one of claims 95-97, wherein: The second communication unit is used to receive third information sent by a second core network element, wherein the third information is used to indicate an association relationship between the description information of the first tunnel and the description information of the second tunnel.

99. The first core network element according to claim 97 or 98, wherein: The second tunnel is determined based on the first business data flow to which the uplink data packet belongs, and the association between the description information of the second tunnel and the description information of the first business data flow, wherein the first business data flow is determined based on the association between the description information of the first tunnel and the description information of the first business data flow.

100. The first core network element according to any one of claims 95, 96 and 99, wherein: The second communication unit is used to receive fourth information sent by a second core network network element, wherein the fourth information is used to indicate an association relationship between the description information of the second tunnel and the description information of the first service data flow, and an association relationship between the description information of the first tunnel and the description information of the first service data flow.

101. The first core network element according to claim 99 or 100, wherein: The description information of the first service data flow includes at least one of the following: an identifier of the first service data flow and an identifier of the first device.

102. The first core network element according to any one of claims 95 to 101, wherein: The description information of the first tunnel includes at least one of the following: an Internet Protocol IP quintuple corresponding to the first tunnel, an IP triplet corresponding to the first tunnel; The description information of the second tunnel includes at least one of the following: an Internet Protocol IP quintuple corresponding to the second tunnel, and an IP triplet corresponding to the second tunnel.

103. The first core network element according to any one of claims 95 to 102, wherein: The second communication unit is used to transmit the uplink data packet through the second tunnel based on the control information of the first tunnel.

104. The first core network element according to any one of claims 95 to 103, wherein: The second communication unit is used to receive fifth information sent by the second core network element, wherein the fifth information includes: control information of the first tunnel, and an association relationship between the control information of the first tunnel and description information of the first tunnel.

105. The first core network element according to claim 103 or 104, wherein: The control information of the first tunnel includes at least one of the following: wireless resources associated with the first tunnel, a bit rate associated with the first tunnel, a quality of service QoS parameter associated with the first tunnel, a gateway parameter associated with the first tunnel, a billing parameter associated with the first tunnel, and a data flow identifier associated with the first tunnel.

106. The first core network element according to any one of claims 98, 100, and 104, wherein: The second core network element includes at least one of the following: a mobility management network element, a session management network element, and a policy control network element.

107. The first core network element according to any one of claims 95 to 106, wherein: The first core network element includes a user plane network element.

108. A first core network element, comprising: The second communication unit is used to receive a downlink data packet, wherein the header of the downlink data packet carries description information of a second tunnel, and the second tunnel is a tunnel between the first core network element and the application server; and transmit a downlink data packet through the first tunnel, wherein the header of the downlink data packet carries description information of the first tunnel, and the first tunnel is a tunnel between a terminal and the first core network element.

109. The first core network element according to claim 108, wherein: Also includes: The second processing unit is configured to replace the description information of the second tunnel carried in the header of the downlink data packet with the description information of the first tunnel.

110. The first core network element according to claim 108 or 109, wherein: The first tunnel is determined based on an association relationship between the description information of the first tunnel and the description information of the second tunnel.

111. The first core network element according to any one of claims 108 to 110, wherein: The second communication unit is used to receive third information sent by a second core network element, wherein the third information is used to indicate an association relationship between the description information of the first tunnel and the description information of the second tunnel.

112. The first core network element according to claim 108 or 109, wherein: The first tunnel is determined based on the first business data flow to which the downlink data packet belongs, and the association between the description information of the first tunnel and the description information of the first business data flow, wherein the first business data flow is determined based on the association between the description information of the second tunnel and the description information of the first business data flow.

113. The first core network element according to any one of claims 108, 109, and 112, wherein: The second communication unit is used to receive fourth information sent by a second core network network element, wherein the fourth information is used to indicate an association relationship between the description information of the second tunnel and the description information of the first service data flow, and an association relationship between the description information of the first tunnel and the description information of the first service data flow.

114. The first core network element according to claim 112 or 113, wherein: The description information of the first service data flow includes at least one of the following: an identifier of the first service data flow and an identifier of the first device.

115. The first core network element according to any one of claims 108 to 114, wherein: The description information of the first tunnel includes at least one of the following: an Internet Protocol IP quintuple corresponding to the first tunnel, an IP triplet corresponding to the first tunnel; The description information of the second tunnel includes at least one of the following: an Internet Protocol IP quintuple corresponding to the second tunnel, and an IP triplet corresponding to the second tunnel.

116. The first core network element according to any one of claims 108 to 115, wherein: The second communication unit is used to transmit a downlink data packet through the first tunnel based on the control information of the first tunnel.

117. The first core network element according to any one of claims 108 to 116, wherein: The second communication unit is used to receive fifth information sent by the second core network element, wherein the fifth information includes: control information of the first tunnel, and an association relationship between the control information of the first tunnel and description information of the first tunnel.

118. The first core network element according to any one of claims 108 to 117, wherein: The control information of the first tunnel includes at least one of the following: wireless resources associated with the first tunnel, a bit rate associated with the first tunnel, a quality of service QoS parameter associated with the first tunnel, a gateway parameter associated with the first tunnel, a billing parameter associated with the first tunnel, and a data flow identifier associated with the first tunnel.

119. The first core network element according to any one of claims 111, 113, and 117, wherein: The second core network element includes at least one of the following: a mobility management network element, a session management network element, and a policy control network element.

120. The first core network element according to any one of claims 108-119, wherein: The first core network element includes a user plane network element.

121. A terminal comprising: A transceiver, a processor and a memory, the memory being used to store a computer program, the transceiver being used to communicate with other devices, and the processor being used to call and run the computer program stored in the memory so that the terminal executes the method as described in any one of claims 1 to 12 or claims 25 to 34.

122. A first core network element, comprising: A transceiver, a processor and a memory, the memory being used to store a computer program, the transceiver being used to communicate with other devices, and the processor being used to call and run the computer program stored in the memory so that the first core network element executes the method as described in any one of claims 13 to 24, or claims 35 to 47, or claims 48 to 60.

123. A chip, comprising: A processor for calling and running a computer program from a memory so that a device equipped with the chip performs a method as described in any one of claims 1 to 12, or claims 13 to 24, or claims 25 to 34, or claims 35 to 47, or claims 48 to 60.

124. A computer-readable storage medium for storing a computer program, which, when executed by a device, causes the device to perform the method described in any one of claims 1 to 12, or claims 13 to 24, or claims 25 to 34, or claims 35 to 47, or claims 48 to 60.

125. A computer program product comprising computer program instructions, the computer program instructions causing a computer to perform the method of any one of claims 1 to 12, or claims 13 to 24, or claims 25 to 34, or claims 35 to 47, or claims 48 to 60.

126. A computer program causing a computer to perform the method of any one of claims 1 to 12, or claims 13 to 24, or claims 25 to 34, or claims 35 to 47, or claims 48 to 60.

Images