Data transmission method and device and storage medium

Abstract

The application of the invention is a divisional application of 202080094819.2. The invention discloses a data transmission method, which comprises the following steps that: a network element of a mobile network sends a first identifier to electronic equipment, and the first identifier is used for transmitting a data packet between the electronic equipment and the network element corresponding to the first identifier. The invention further discloses another data transmission method and device and a storage medium.

Description

[0001] This application is a divisional application. The application number of the parent application is 202080094819.2, the application date is May 29, 2020, and the name of the invention is “A data transmission method, device and storage medium”. Technical Field

[0002] The present application relates to the field of wireless communication technology, and in particular to a data transmission method, device and storage medium. Background Art

[0003] In the related art, user plane data needs to be sent to an external application server through the network protocol address of the application server, which limits the application scope of the user plane data. Summary of the invention

[0004] The embodiments of the present application provide a data transmission method, device, and storage medium, which can expand the application scope of user plane data.

[0005] In a first aspect, an embodiment of the present application provides a data transmission method, including: a mobile network element sends a first identifier to an electronic device, where the first identifier is used to transmit a data packet between the electronic device and the network element corresponding to the first identifier.

[0006] In a second aspect, an embodiment of the present application provides a data transmission method, including: an electronic device receives a first identifier; the first identifier is used to transmit a data packet between the electronic device and a network element corresponding to the first identifier; and the electronic device adds the first identifier to the data packet.

[0007] In a third aspect, an embodiment of the present application provides a data transmission method, including: a user plane function entity receives a data packet carrying a first identifier, where the first identifier is used to transmit the data packet between the user plane function entity and a network element corresponding to the first identifier;

[0008] The user plane function entity sends the data packet to the network element according to the first identifier.

[0009] In a fourth aspect, an embodiment of the present application provides a mobile network element, comprising: a first sending unit, configured to send a first identifier to an electronic device, wherein the first identifier is used to transmit data packets between the electronic device and the network element corresponding to the first identifier.

[0010] In a fifth aspect, an embodiment of the present application provides an electronic device, comprising: a third receiving unit, configured to receive a first identifier; the first identifier is used to transmit data packets between the electronic device and a network element corresponding to the first identifier.

[0011] The processing unit is configured to add the first identifier to the data packet.

[0012] In a sixth aspect, an embodiment of the present application provides a user plane function entity, the user plane function entity comprising: a fourth receiving unit, configured to receive a data packet carrying a first identifier, the first identifier being used to transmit a data packet between the user plane function entity and a network element corresponding to the first identifier;

[0013] A fifth sending unit is configured to send the data packet to the network element according to the first identifier.

[0014] In the seventh aspect, an embodiment of the present application provides a mobile network element, comprising a processor and a memory for storing a computer program that can be run on the processor, wherein the processor, when used to run the computer program, executes the steps of the data transmission method performed by the above-mentioned mobile network element.

[0015] In an eighth aspect, an embodiment of the present application provides an electronic device, comprising a processor and a memory for storing a computer program that can be run on the processor, wherein the processor, when being used to run the computer program, executes the steps of the data transmission method performed by the above-mentioned electronic device.

[0016] In the ninth aspect, an embodiment of the present application provides a user plane functional entity, comprising a processor and a memory for storing a computer program that can be run on the processor, wherein the processor, when running the computer program, executes the steps of the data transmission method performed by the above-mentioned user plane functional entity.

[0017] In the tenth aspect, an embodiment of the present application provides a chip, including: a processor, used to call and run a computer program from a memory, so that a device equipped with the chip executes the data transmission method executed by the above-mentioned mobile network element.

[0018] In an eleventh aspect, an embodiment of the present application provides a chip, comprising: a processor, configured to call and run a computer program from a memory, so that a device equipped with the chip executes the data transmission method executed by the above-mentioned electronic device.

[0019] In a twelfth aspect, an embodiment of the present application provides a chip, comprising: a processor, configured to call and run a computer program from a memory, so that a device equipped with the chip executes the data transmission method executed by the above-mentioned user plane functional entity.

[0020] In a thirteenth aspect, an embodiment of the present application provides a storage medium storing an executable program, which, when executed by a processor, implements the data transmission method executed by the above-mentioned mobile network element.

[0021] In a fourteenth aspect, an embodiment of the present application provides a storage medium storing an executable program, which, when executed by a processor, implements the data transmission method executed by the above-mentioned electronic device.

[0022] In a fifteenth aspect, an embodiment of the present application provides a storage medium storing an executable program, which, when executed by a processor, implements the data transmission method performed by the above-mentioned user plane functional entity.

[0023] In a sixteenth aspect, an embodiment of the present application provides a computer program product, including computer program instructions, which enable a computer to execute the data transmission method executed by the above-mentioned mobile network element.

[0024] In the seventeenth aspect, an embodiment of the present application provides a computer program product, including computer program instructions, which enable a computer to execute the data transmission method executed by the above-mentioned electronic device.

[0025] In an eighteenth aspect, an embodiment of the present application provides a computer program product, comprising computer program instructions, which enable a computer to execute the data transmission method performed by the above-mentioned user plane functional entity.

[0026] In the nineteenth aspect, an embodiment of the present application provides a computer program, which enables a computer to execute the data transmission method executed by the above-mentioned mobile network element.

[0027] In the twentieth aspect, an embodiment of the present application provides a computer program, which enables a computer to execute the data transmission method executed by the above-mentioned electronic device.

[0028] In a twenty-first aspect, an embodiment of the present application provides a computer program, which enables a computer to execute the data transmission method performed by the above-mentioned user plane functional entity.

[0029] The data transmission method, device and storage medium provided in the embodiments of the present application include: sending a first identifier to a terminal device (User Equipment, UE), or a network device or a UPF entity through a mobile network network element, so that the terminal device, or the network device or the UPF entity can know the purpose (function) of the first identifier, and then the terminal device, or the network device or the UPF entity can transmit data packets between the network elements corresponding to the first identifier, so that the mobile network network element can realize data applications such as big data analysis and network status monitoring based on user plane data, thereby improving the application scope of the data. BRIEF DESCRIPTION OF THE DRAWINGS

[0030] Figure 1 A schematic diagram of the terminal device of this application sending uplink data;

[0031] Figure 2 This is a schematic diagram of the binding process of QoS data flow in the PDU session for this application;

[0032] Figure 3 A schematic diagram of the user plane protocol stack for this application;

[0033] Figure 4 A schematic diagram of the process of sending a data packet through a PUD session by a terminal device of this application;

[0034] Figure 5 A schematic diagram of the structure of the communication system according to an embodiment of the present application;

[0035] Figure 6 A schematic diagram of an optional processing flow of the data transmission method according to an embodiment of the present application;

[0036] Figure 7 This is another optional processing flow diagram of the data transmission method according to an embodiment of the present application;

[0037] Figure 8 A schematic diagram of another optional processing flow of the data transmission method according to an embodiment of the present application;

[0038] Fig. 9 A detailed processing flow diagram of the data transmission method according to an embodiment of the present application;

[0039] Fig.10 This is a schematic diagram of a data transmission method for scenario 1 according to an embodiment of the present application;

[0040] Fig.11 This is a schematic diagram of a data transmission method for scenario 2 according to an embodiment of the present application;

[0041] Fig.12 This is a schematic diagram of a data transmission method for scenario three according to an embodiment of the present application;

[0042] Fig.13 This is a schematic diagram of a data transmission method for scenario 4 according to an embodiment of the present application;

[0043] Fig.14 A schematic diagram of an optional composition structure of a mobile network element according to an embodiment of the present application;

[0044] Fig.15 A schematic diagram of an optional structure of an electronic device according to an embodiment of the present application;

[0045] Fig.16 This is a schematic diagram of an optional composition structure of a user plane functional entity in an embodiment of the present application;

[0046] Fig.17 This is a schematic diagram of the hardware composition structure of the device according to the embodiment of the present application. DETAILED DESCRIPTION

[0047] In order to enable a more detailed understanding of the features and technical contents of the embodiments of the present application, the implementation of the embodiments of the present application is described in detail below in conjunction with the accompanying drawings. The attached drawings are for reference only and are not used to limit the embodiments of the present application.

[0048] In the related art, the terminal device establishes a protocol data unit (PDU) session by interacting with the core network control plane network element, that is, the connection between the terminal device and the user plane function (UPF) entity. Figure 1 As shown, when the terminal device sends uplink data, it can be sent to the UPF entity through the protocol of the PDU session. The UPF entity performs next-hop routing according to the Internet Protocol (IP) address of the target server, and finally sends the data packet to the application server, such as the server on the data network (DN). For downlink data, after the UPF entity receives the data packet from the DN, it determines the binding to the corresponding PDU session according to the downlink target IP address, and sends the data to the terminal device through the PDU session.

[0049] In order to ensure data transmission, mobile networks usually use the Quality of Service (QoS) mechanism; a set of QoS parameters can be used for data transmission of one or more QoS data flows or bearers; therefore, it is necessary to bind the QoS data flow to the DRB. The binding process of QoS data flow in PDU session, such as Figure 2 As shown, one or more QoS flows can be mapped to a data radio bearer (DRB) for transmission; Figure 2 The connection between the terminal device and the access network (AN) device (such as a network device) shown can be called a DRB transmission.

[0050] When binding QoS data flows, the uplink QoS data flows are bound by the terminal device; the terminal device determines which QoS data flow different data packets need to be bound to for transmission according to the QoS rule. The downlink QoS data flows are bound by the UPF entity; the UPF entity determines which QoS data flow different data packets need to be bound to for transmission according to the PDR rule.

[0051] Among them, the schematic diagram of the user plane protocol stack is as follows: Figure 3As shown, replication / de-duplication is performed at the tunneling protocol (GPRSTunnellingProtocol, GTP-U) layer on the UPF; replication / de-duplication is performed at the service data convergence protocol (ServiceDataAdaptationProtocol, SDAP) or packet data convergence protocol (Packet DataConvergence Protocol, PDCP) layer on the terminal device side; the AN device needs to perform protocol conversion operations.

[0052] The QoS flow identifier (Identify, ID) is added to the SDAP header between the terminal device and the AN device, and the QFI identifier is added to the GTP-U header between the AN device and the UPF entity. Therefore, the terminal device, AN device and UPF entity can all know which QoS flow the data packet corresponds to. In some cases, the corresponding QoS flow can be known between the terminal device and the AN device based on the mapping relationship between DRB and QoS flow. In this scenario, the SDAP header does not need to explicitly add the QFI identifier.

[0053] With the increasing demand for big data in operator networks and the rise of edge computing (EC) and other services, the applicant has found that some user-side data packets need to be forwarded to the core network control plane network element instead of being sent to external application servers. These data can be used for big data analysis, network status monitoring, etc. The process of a terminal device sending a data packet through a PUD session, such as Figure 4 As shown, when the user plane data packet needs to be forwarded to the core network control plane network element, the terminal device can send the data packet to different core network network elements through the PDU session, such as the session management function (Session Management Function, SMF) entity, the network exposure function (Network Exposure Function, NEF) entity or the network data analysis function (Network Data Analysis Function, NWDAF) entity.

[0054] The technical solutions of the embodiments of the present application can be applied to various communication systems, such as: global system of mobile communication (GSM) system, code division multiple access (CDMA) system, wideband code division multiple access (WCDMA) system, general packet radio service (GPRS), long term evolution (LTE) system, LTE frequency division duplex (FDD) system, LTE time division duplex (TDD) system, advanced long term evolution (LTE-A) system, new radio (NR) system, NR system evolution system, LTE on unlicensed band (LTE-based access to unlicensed spectrum, LTE-U) system, NR on unlicensed band (NR-based access to unlicensed spectrum, NR-U) system, universal mobile telecommunication system (UMTS), global interoperability for microwave access (worldwide interoperability for microwave access, WiMAX) communication system, wireless local area networks (WLAN), wireless fidelity (WiFi), next generation communication system or other communication systems, etc.

[0055] The system architecture and business scenarios described in the embodiments of the present application are intended to more clearly illustrate the technical solutions of the embodiments of the present application, and do not constitute a limitation on the technical solutions provided in the embodiments of the present application. A person of ordinary skill in the art can appreciate that with the evolution of network architecture and the emergence of new business scenarios, the technical solutions provided in the embodiments of the present application are also applicable to similar technical problems.

[0056] The network equipment involved in the embodiments of the present application may be an ordinary base station (such as NodeB or eNB or gNB), a new radio controller (new radio controller, NR controller), a centralized unit, a new wireless base station, a radio frequency remote module, a micro base station, a relay, a distributed unit, a transmission reception point (TRP), a transmission point (TP) or any other device. The embodiments of the present application do not limit the specific technology and specific device form adopted by the network equipment. For the convenience of description, in all embodiments of the present application, the above-mentioned devices that provide wireless communication functions for terminal devices are collectively referred to as network devices.

[0057] In the embodiment of the present application, the terminal device may be any terminal, for example, the terminal device may be a user device for machine type communication. That is to say, the terminal device may also be referred to as a user equipment UE, a mobile station (MS), a mobile terminal, a terminal, etc. The terminal device may communicate with one or more core network elements via a radio access network (RAN). For example, the terminal device may be a mobile phone (or a "cellular" phone), a computer with a mobile terminal, etc. For example, the terminal device may also be a portable, pocket-sized, handheld, computer-built-in or vehicle-mounted mobile device, which exchanges language and / or data with a radio access network. This is not specifically limited in the embodiment of the present application.

[0058] Optionally, the network device and the terminal device can be deployed on land, including indoors or outdoors, handheld or vehicle-mounted; can also be deployed on the water surface; can also be deployed on aircraft, balloons and artificial satellites in the air. The embodiments of the present application do not limit the application scenarios of the network device and the terminal device.

[0059] Optionally, the network device and the terminal device, and the terminal device and the terminal device may communicate through a licensed spectrum, or may communicate through an unlicensed spectrum, or may communicate through both a licensed spectrum and an unlicensed spectrum. The network device and the terminal device, and the terminal device and the terminal device may communicate through a spectrum below 7 gigahertz (GHz), or may communicate through a spectrum above 7 GHz, or may communicate using a spectrum below 7 GHz and a spectrum above 7 GHz at the same time. The embodiments of the present application do not limit the spectrum resources used between the network device and the terminal device.

[0060] Generally speaking, traditional communication systems support a limited number of connections and are easy to implement. However, with the development of communication technology, mobile communication systems will not only support traditional communications, but will also support, for example, device to device (D2D) communication, machine to machine (M2M) communication, machine type communication (MTC), and vehicle to vehicle (V2V) communication, etc. The embodiments of the present application can also be applied to these communication systems.

[0061] For example, the communication system 100 used in the embodiment of the present application is as follows: Figure 5 As shown. The communication system 100 may include a network device 110, which may be a device that communicates with a terminal device 120 (or referred to as a communication terminal or terminal). The network device 110 may provide communication coverage for a specific geographical area, and may communicate with terminal devices located in the coverage area. Optionally, the network device 110 may be a base station (Base Transceiver Station, BTS) in a GSM system or a CDMA system, or a base station (NodeB, NB) in a WCDMA system, or an evolved base station (Evolutional Node B, eNB or eNodeB) in an LTE system, or a wireless controller in a cloud radio access network (Cloud Radio Access Network, CRAN), or the network device may be a mobile switching center, a relay station, an access point, a vehicle-mounted device, a wearable device, a hub, a switch, a bridge, a router, a network-side device in a 5G network, or a network device in a future evolved public land mobile network (Public Land Mobile Network, PLMN), etc.

[0062] The communication system 100 also includes at least one terminal device 120 located within the coverage of the network device 110. As used herein, "terminal device" includes but is not limited to connection via a wired line, such as via a Public Switched Telephone Networks (PSTN), a Digital Subscriber Line (DSL), a digital cable, a direct cable connection; and / or another data connection / network; and / or via a wireless interface, such as, for a cellular network, a Wireless Local Area Network (WLAN), a digital television network such as a DVB-H network, a satellite network, an AM-FM broadcast transmitter; and / or a device of another terminal device configured to receive / send communication signals; and / or an Internet of Things (IoT) device. A terminal device configured to communicate via a wireless interface may be referred to as a "wireless communication terminal", "wireless terminal" or "mobile terminal". Examples of mobile terminals include, but are not limited to, satellite or cellular telephones; Personal Communications System (PCS) terminals that may combine cellular radiotelephones with data processing, fax, and data communications capabilities; PDAs that may include radiotelephones, pagers, Internet / Intranet access, Web browsers, notepads, calendars, and / or Global Positioning System (GPS) receivers; and conventional laptop and / or palmtop receivers or other electronic devices that include radiotelephone transceivers. Terminal equipment may refer to access terminals, user equipment subscriber units, user stations, mobile stations, mobile stations, remote stations, remote terminals, mobile devices, user terminals, terminals, wireless communication devices, user agents, or user devices. The access terminal can be a cellular phone, a cordless phone, a Session Initiation Protocol (SIP) phone, a Wireless Local Loop (WLL) station, a Personal Digital Assistant (PDA), a handheld device with wireless communication capabilities, a computing device or other processing device connected to a wireless modem, a vehicle-mounted device, a wearable device, a terminal device in a 5G network, or a terminal device in a future evolved PLMN, etc.

[0063] Optionally, terminal devices 120 may perform device-to-device (D2D) communication with each other.

[0064] Optionally, the 5G system or 5G network may also be referred to as a New Radio (NR) system or NR network.

[0065] Figure 5 One network device and two terminal devices are shown exemplarily. Optionally, the communication system 100 may include multiple network devices and each network device may include another number of terminal devices within its coverage area, which is not limited in the embodiments of the present application.

[0066] Optionally, the communication system 100 may also include other network entities such as a network controller and a mobility management entity, which is not limited in the embodiments of the present application.

[0067] It should be understood that the device with communication function in the network / system in the embodiment of the present application can be referred to as a communication device. Figure 5 Taking the communication system 100 shown as an example, the communication equipment may include a network device 110 and a terminal device 120 with communication functions. The network device 110 and the terminal device 120 may be the specific devices described above and will not be repeated here. The communication equipment may also include other devices in the communication system 100, such as a network controller, a mobile management entity and other network entities, which is not limited in the embodiments of the present application.

[0068] An optional processing flow of the data transmission method provided in the embodiment of the present application is as follows: Figure 6 As shown, the following steps may be included:

[0069] Step S201: A network element of a mobile network sends a first identifier to an electronic device, where the first identifier is used to transmit a data packet between the electronic device and the network element corresponding to the first identifier.

[0070] In some embodiments, the electronic device can add the first identifier to the data packet and send it to the UPF entity, and the UPF entity sends it to the corresponding network element according to the first identifier. In other embodiments, when the UPF entity receives a data packet sent by the corresponding network element, it determines the first identifier according to the network element that sends the data packet, adds it to the data packet (such as the header of a certain protocol layer of the data packet), and sends it to the electronic device.

[0071] In some embodiments, the first identifier may be an existing identifier, such as a QoS Flow ID and / or a PDU Session ID, or a new identifier, such as a service identifier, a server identifier, etc.

[0072] In some embodiments, the first identifier is carried in a QoS parameter; wherein the QoS parameter may be content in a QoS Profile, that is, the first identifier may be part of a QoS Profile. The first identifier may be part of a QoS parameter; the first identifier may also be indirectly determined based on the QoS parameter, such as the first identifier being a QFI determined based on a 5G QoS Index (5G QoS Index, 5QI) parameter in a QoS Profile.

[0073] In some embodiments, the QoS parameters may include, but are not limited to, one or more of the following: packet filter, guaranteed bitrate, non-garanteed bitrate, maximum bit rate, packet delay budget, packet error rate, 5QI, and preemption priority parameters. The packet filter may include one or more of the following: IP5 tuple, Type Of Service (IPV4) / Traffic class (IPV6), and data flow direction.

[0074] In some embodiments, the first identifier is sent as a parameter independent of the QoS parameter, that is, the first identifier is not a content in the QoS Profile.

[0075] In some embodiments, the purpose (function) of the first identifier can be configured dynamically or statically, that is, the mobile network element can configure the purpose of the first identifier to the electronic device in a dynamic or static manner. Alternatively, the purpose of the first identifier can also be default. In the case where the purpose of the first identifier is default, the purpose of the first identifier can be determined by negotiation between the devices, or pre-agreed, or defined by standard protocols such as 3GPP. Among them, the purpose of the first identifier includes transmitting data between the electronic device and a specific network element according to the first identifier; or the purpose of the first identifier includes executing a specific service according to the first identifier, and sending data to the corresponding network element according to the service, such as the electronic device sends data to the UPF entity, the UPF entity sends data to the SMF entity according to the first identifier, and the SMF entity sends the data to the EC server; or the electronic device sends data to the UPF entity, the UPF entity sends data to the NEF entity according to the first identifier, and the NEF entity sends data to the EC server; or the electronic device sends data to the NWDAF entity; the NWDAF entity processes the data, such as data analysis, hash mapping, etc.; or the electronic device sends data to the Domain Name System (DNS) entity, and the DNS entity can be used for DNS query services.

[0076] In some embodiments, the first identifier is carried in an N2 message and / or a NAS message. The N2 message may be a message used to transmit information between a core network element and a RAN node; the NAS message may be a message used to transmit information between a core network element and a terminal device, and the message may be transparently transmitted to the terminal device via the RAN.

[0077] In some embodiments, the network element includes at least any one of the following: an NWDAF entity, an NEF entity, a PCF entity, an NWDAF entity corresponding to the first network slice, and a User Data Management (UDM) entity. The electronic device may be at least one of a terminal device, a wireless network device, a core network device, and a UPF entity. The mobile network element may be a core network element, and the core network element may be an SMF entity, an AMF entity, a PCF entity, or the like.

[0078] Among them, the NWDAF entity can be used for big data collection, big data analysis and distribution of analysis results. The NEF entity can be used for network capability opening, and the information of the mobile network can be interacted with the medical server through the NEF entity. The PCF entity can be used for policy management on the terminal device side and the network device side; the UDM entity can be used for the management of user contract information. The SMF entity can be used for session management; the AMF entity can be used for mobility management.

[0079] In some embodiments, the method may further include:

[0080] Step S200: The mobile network element receives a first request message, where the first request message is used to request to obtain the first identifier.

[0081] In some embodiments, the mobile network element receives a first request message sent by an electronic device, where the first request message is used to request the mobile network element to send the first identifier to the electronic device.

[0082] In some embodiments, the method may further include:

[0083] Step S202, the mobile network element sends the first corresponding relationship to the electronic device.

[0084] In some embodiments, the mobile network element sends the first corresponding relationship to an electronic device, and the electronic device may be at least one of a terminal device, a network device, and a UPF entity.

[0085] In some embodiments, the first correspondence may be carried in a QoS parameter; wherein the QoS parameter may be content in a QoS Profile, that is, the first identifier may be a part of the QoS Profile. The first correspondence is a part of the QoS parameter; the first correspondence may also be indirectly determined based on the QoS parameter, such as the first correspondence is a QFI determined based on a 5QI parameter in the QoS Profile. Alternatively, the first correspondence is sent as a parameter independent of the QoS parameter.

[0086] In some embodiments, the first correspondence is carried in an N2 message and / or a NAS message. The N2 message may be a message used to transmit information between a core network element and a RAN node; the NAS message may be a message used to transmit information between a core network element and a terminal device, and the message may be transparently transmitted to the terminal device via the RAN.

[0087] In some embodiments, the first corresponding relationship includes: a corresponding relationship between the first identifier and the network element, and / or a corresponding relationship between the first identifier and the service.

[0088] Regarding the correspondence between the first identifier and the network element, it can be that identifier-1 corresponds to the NWDAF entity, identifier-2 corresponds to the NEF entity, identifier-3 corresponds to the PCF entity, identifier-4 corresponds to the NWDAF entity of the first network slice, and identifier-5 corresponds to the NWDAF entity of the second network slice, etc. Among them, the NWDAF entity can exist alone or be combined with other existing network elements, such as one of the UPF entity, the SMF entity, and the NEF entity; the NEF entity can exist alone or be combined with other existing network elements, such as the UPF entity.

[0089] Regarding the correspondence between the first identifier and the service, identifier-1 may correspond to data analysis service (Dataanalytics Service), identifier-2 may correspond to local area network (LAN) service, identifier-3 may correspond to edge computing service, identifier-4 may correspond to DNS service, and identifier-5 may correspond to network information notification service.

[0090] In some embodiments, the method may further include:

[0091] Step S202': the mobile network element receives a second request message, where the second request message is used to request to obtain the first corresponding relationship.

[0092] In some embodiments, the mobile network element receives a second request message sent by the electronic device, where the second request message is used to request the mobile network element to send the first corresponding relationship to the electronic device.

[0093] It should be noted that the data transmission method provided in the embodiment of the present application can be applied to scenarios such as the PDU session establishment process, the PDU session modification process, the registration process, and the service request process.

[0094] Another optional processing flow of the data transmission method provided in the embodiment of the present application is as follows: Figure 7 As shown, the following steps are included:

[0095] Step S301: An electronic device receives a first identifier, where the first identifier is used to transmit a data packet between the electronic device and a network element corresponding to the first identifier.

[0096] In some embodiments, the electronic device receives a first identifier sent by a mobile network element.

[0097] In some embodiments, the electronic device may be a terminal device and / or a network device, and the mobile network element may be an SMF entity, an AMF entity, a PCF entity, etc.

[0098] In some embodiments, the first identifier may be an existing identifier, such as a QoS Flow ID and / or a PDUSession ID. Alternatively, the first identifier may be a new identifier, such as a service identifier, a server identifier, and the like.

[0099] In some embodiments, the first identifier is carried in the QoS parameters; wherein the QoS parameters may be the content in the QoS Profile, that is, the first identifier may be a part of the QoS Profile. The first identifier may be explicitly carried in the QoS parameters; the first identifier may also be indirectly determined based on the QoS parameters, such as the first identifier is a QFI determined based on the 5QI parameters in the QoS Profile.

[0100] In some embodiments, the electronic device may indirectly determine the service or server corresponding to the data stream based on the QoS parameters. For example, the service or server corresponding to the data stream is determined based on the 5QI parameters in the QoS profile, and the corresponding relationship may be configured by default on the electronic device (such as by means of standardization or pre-configuration).

[0101] In some embodiments, the first identifier is sent as a parameter independent of the QoS parameter, that is, the first identifier is not a content in the QoS Profile.

[0102] In some embodiments, the QoS parameters may include, but are not limited to, one or more of the following: packet filter, Garanteed Biterate, Non-Garanteed Biterate, Maximum Bit Rate, Packet Delay Budget, Packet Error Rate, 5QI, and preemption priority parameters. The packet filter may include one or more of the following: IP5 tuple, Type Of Service (IPV4) / Traffic class (IPV6), and data flow direction.

[0103] In some embodiments, the purpose (function) of the first identifier can be configured dynamically or statically, that is, the mobile network element can configure the purpose of the first identifier to the electronic device in a dynamic or static manner. Alternatively, the purpose of the first identifier can also be a default. In the case where the purpose of the first identifier is a default, the purpose of the first identifier can be determined by negotiation between the devices, or pre-agreed, or defined by standard protocols such as 3GPP. Among them, the purpose of the first identifier includes transmitting data between a specific network element according to the first identifier; or the purpose of the first identifier includes executing a specific service according to the first identifier, and sending data to the corresponding network element according to the service, such as the electronic device sending data to the UPF entity, the UPF entity sending data to the SMF entity according to the first identifier, and the SMF entity sending data to the EC server; or the electronic device sends data to the UPF entity, the UPF entity sends data to the NEF entity according to the first identifier, and the NEF entity sends data to the EC server; or the electronic device sends data to the NWDAF entity; the NWDAF entity processes the data, such as data analysis, hash mapping, etc.; or the electronic device sends data to the DNS entity, and the DNS entity can be used for DNS query services.

[0104] In some embodiments, the first identifier is carried in an N2 message and / or a NAS message. The N2 message may be a message used to transmit information between a core network element and a RAN node; the NAS message may be a message used to transmit information between a core network element and a terminal device, and the message may be transparently transmitted to the terminal device via the RAN.

[0105] In some embodiments, the network element includes at least any one of the following: an NWDAF entity, an NEF entity, a PCF entity, an NWDAF entity corresponding to the first network slice, and an UDM entity. The electronic device may be at least one of a terminal device, a network device, and a UPF entity. The mobile network element may be an SMF entity, an AMF entity, or a PCF entity, etc.

[0106] Among them, the NWDAF entity can be used for big data collection, big data analysis and distribution of analysis results. The NEF entity can be used for network capability opening, and the information of the mobile network can be interacted with the medical server through the NEF entity. The PCF entity can be used for policy management on the terminal device side and the network device side; the UDM entity can be used for the management of user contract information. The SMF entity can be used for session management; the AMF entity can be used for mobility management.

[0107] Regarding the transmission of data packets between the electronic device and the network element corresponding to the first identifier, in some embodiments, the electronic device may add the first identifier to the data packet and send it to the UPF entity, and the UPF entity sends it to the corresponding network element according to the first identifier. In other embodiments, when the UPF entity receives a data packet sent by the corresponding network element, it determines the first identifier according to the network element sending the data packet, adds it to the data packet (such as a header of a certain protocol layer of the data packet), and sends it to the electronic device.

[0108] Step S302: The electronic device adds the first identifier to the data packet.

[0109] In some embodiments, the electronic device adds the first identifier to the data packet and sends the data packet to the UPF entity. The UPF entity sends the data packet to the corresponding network element based on the first identifier, such as a mobile network element (core network element), a terminal device, a network device, a functional module inside the UPF entity, an entity jointly established with the UPF entity, or another UPF entity other than the UPF entity.

[0110] In some embodiments, the method may further include:

[0111] Step S300a: The electronic device sends a first request message to a mobile network element, where the first request message is used to request to obtain the first identifier.

[0112] In some embodiments, the first request message is used to request the mobile network element to send the first identifier to the electronic device.

[0113] In some embodiments, the method may further include:

[0114] Step S300b: the electronic device receives a first corresponding relationship.

[0115] In some embodiments, the electronic device receives the first corresponding relationship sent by a mobile network element, and the first corresponding relationship includes: a corresponding relationship between the first identifier and the network element, and / or a corresponding relationship between the first identifier and the service.

[0116] In some embodiments, the first correspondence may be carried in a QoS parameter; wherein the QoS parameter may be content in a QoS Profile, that is, the first identifier may be a part of the QoS Profile. The first correspondence may be a part of a QoS parameter; the first correspondence may also be indirectly determined based on the QoS parameter, such as the first correspondence is a QFI determined based on a 5QI parameter in the QoS Profile. Alternatively, the first correspondence is sent as a parameter independent of the QoS parameter.

[0117] In some embodiments, the first correspondence is carried in an N2 message and / or a NAS message. The N2 message may be a message used to transmit information between a core network element and a RAN node; the NAS message may be a message used to transmit information between a core network element and a terminal device, and the message may be transparently transmitted to the terminal device via the RAN.

[0118] In some embodiments, the first corresponding relationship includes: a corresponding relationship between the first identifier and the network element, and / or a corresponding relationship between the first identifier and the service.

[0119] Regarding the correspondence between the first identifier and the network element, it can be that identifier-1 corresponds to the NWDAF entity, identifier-2 corresponds to the NEF entity, identifier-3 corresponds to the PCF entity, identifier-4 corresponds to the NWDAF entity of the first network slice, and identifier-5 corresponds to the NWDAF entity of the second network slice, etc. Among them, the NWDAF entity can exist alone or be combined with other existing network elements, such as one of the UPF entity, the SMF entity, and the NEF entity; the NEF entity can exist alone or be combined with other existing network elements, such as the UPF entity.

[0120] Regarding the correspondence between the first identifier and the service, identifier-1 may correspond to data analysis service (Dataanalytics Service), identifier-2 may correspond to local area network (LAN) service, identifier-3 may correspond to edge computing service, identifier-4 may correspond to DNS service, and identifier-5 may correspond to network information notification service.

[0121] Step S300b': the electronic device sends a second request message to the mobile network element, where the second request message is used to request to obtain the first corresponding relationship.

[0122] In some embodiments, the second request message is used to request the mobile network element to send the first corresponding relationship to the electronic device.

[0123] It should be noted that the data transmission method provided in the embodiment of the present application can be applied to scenarios such as the PDU session establishment process, the PDU session modification process, the registration process, and the service request process.

[0124] Another optional processing flow of the data transmission method provided in the embodiment of the present application is as follows: Figure 8 As shown, the following steps are included:

[0125] Step S401: A UPF entity receives a data packet carrying a first identifier, where the first identifier is used to transmit the data packet between the UPF entity and a network element corresponding to the first identifier.

[0126] In some embodiments, the UPF entity receives a data packet carrying a first identifier sent by a network device or a terminal device.

[0127] In some embodiments, the first identifier may be an existing identifier, such as a QoS Flow ID and / or a PDUSession ID. Alternatively, the first identifier may be a new identifier, such as a service identifier, a server identifier, and the like.

[0128] In some embodiments, the first identifier is carried in a QoS parameter; wherein the QoS parameter may be content in a QoSProfile, i.e., the first identifier may be a part of a QoS Profile. The first identifier may be a part of a QoS parameter; the first identifier may also be indirectly determined based on the QoS parameter, such as the first identifier being a QFI determined based on a 5QI parameter in a QoSProfile.

[0129] In some embodiments, the first identifier is sent as a parameter independent of the QoS parameter, that is, the first identifier is not a content in the QoS Profile.

[0130] In some embodiments, the QoS parameters may include, but are not limited to, one or more of the following: packet filter, Garanteed Biterate, Non-Garanteed Biterate, Maximum Bit Rate, Packet Delay Budget, Packet Error Rate, 5QI, and preemption priority parameters. The packet filter may include one or more of the following: IP5 tuple, Type Of Service (IPV4) / Traffic class (IPV6), and data flow direction.

[0131] In some embodiments, the purpose (function) of the first identifier can be configured dynamically or statically, that is, the mobile network element configures the purpose of the first identifier to the network device or terminal device in a dynamic or static manner. Alternatively, the purpose of the first identifier can also be a default. In the case where the purpose of the first identifier is a default, the purpose of the first identifier can be determined by negotiation between the devices, or pre-agreed, or defined by standard protocols such as 3GPP. Among them, the purpose of the first identifier includes transmitting data between a specific network element according to the first identifier; or the purpose of the first identifier includes executing a specific service according to the first identifier, and sending data to the corresponding network element according to the service, such as an electronic device sending data to a UPF entity, and the UPF entity sending data to an SMF entity according to the first identifier, and the SMF entity sending data to an EC server; or an electronic device sending data to a UPF entity, and the UPF entity sending data to a NEF entity according to the first identifier, and the NEF entity sending data to an EC server; or an electronic device sending data to a NWDAF entity; the NWDAF entity processes the data, such as data analysis, hash mapping, etc.; or an electronic device sending data to a DNS entity, and the DNS entity can be used for DNS query services.

[0132] Regarding the transmission of data packets between the UPF entity and the network element corresponding to the first identifier, in some embodiments, the electronic device can add the first identifier to the data packet and send it to the UPF entity, and the UPF entity sends it to the corresponding network element according to the first identifier. In other embodiments, when the UPF entity receives a data packet sent by the corresponding network element, it determines the first identifier according to the network element sending the data packet, adds it to the data packet (such as in the header of a certain protocol layer of the data packet), and sends it to the electronic device.

[0133] In some embodiments, the method may further include:

[0134] Step S400: The UPF entity sends a third request message to a mobile network element, where the third request message is used to request to obtain a first identifier and / or a first corresponding relationship.

[0135] In some embodiments, the first correspondence may be carried in a QoS parameter; wherein the QoS parameter may be content in a QoS Profile, i.e., the first identifier may be a part of a QoS Profile. The first correspondence may be a part of a QoS parameter; the first correspondence may also be indirectly determined based on the QoS parameter, such as the first correspondence being a QFI determined based on a 5QI parameter in a QoS Profile. Alternatively, the first correspondence is sent as a parameter independent of the QoS parameter.

[0136] In some embodiments, the first correspondence is carried in an N2 message and / or a NAS message. The N2 message may be a message used to transmit information between a core network element and a RAN node; the NAS message may be a message used to transmit information between a core network element and a terminal device, and the message may be transparently transmitted to the terminal device via the RAN.

[0137] In some embodiments, the first corresponding relationship includes: a corresponding relationship between the first identifier and the network element, and / or a corresponding relationship between the first identifier and the service.

[0138] Regarding the correspondence between the first identifier and the network element, identifier-1 may correspond to the NWDAF entity, identifier-2 may correspond to the NEF entity, identifier-3 may correspond to the PCF entity, identifier-4 may correspond to the NWDAF entity of the first network slice, and identifier-5 may correspond to the NWDAF entity of the second network slice, etc.; wherein, the NWDAF entity may exist alone or be combined with other existing network elements, such as one of the UPF entity, the SMF entity, and the NEF entity; the NEF entity may exist alone or be combined with other existing network elements, such as a UPF entity.

[0139] Regarding the correspondence between the first identifier and the service, identifier-1 may correspond to Data analytics Service, identifier-2 may correspond to LAN service, identifier-3 may correspond to edge computing service, identifier-4 may correspond to DNS service, and identifier-5 may correspond to network information notification service.

[0140] Step S402: The UPF entity sends the data packet to the network element according to the first identifier.

[0141] In some embodiments, the network element includes at least one of the following: a mobile network element (core network element), a terminal device, a network device, a functional module inside a UPF entity, an entity co-established with a UPF entity, or another UPF entity other than the UPF entity.

[0142] It should be noted that the data transmission method provided in the embodiment of the present application can be applied to scenarios such as the PDU session establishment process, the PDU session modification process, the registration process, and the service request process.

[0143] Taking the PDU session establishment process as an example, during the PDU session establishment (or modification) process, the mobile network element, such as the core network element, informs the terminal device or network device of the first identifier and / or the first correspondence. The first identifier needs to be added to the header of the user plane data packet so that the UPF entity can detect the first identifier and forward the data packet to the corresponding network element. Prior to this, optionally, the terminal device can add the requested first identifier and / or the first correspondence in the PDU session request message. The detailed processing flow of the data transmission method provided in the embodiment of the present application is as follows: Fig. 9 As shown, including:

[0144] Step S501: The terminal device sends a session establishment request to the SMF entity, where the session establishment request carries a first identifier and / or a first corresponding relationship of the request.

[0145] Step S502: The SMF entity sends a setup request to the UPF entity.

[0146] In some embodiments, when the SMF entity sends an establishment request to the UPF entity, the first identifier and / or the first correspondence may be carried.

[0147] Step S503: The SMF entity sends a session establishment request to the RAN network element, where the session establishment request carries the first identifier and / or the first corresponding relationship requested.

[0148] In some embodiments, the session establishment request may carry a NAS message.

[0149] Step S504: air interface resources are established and NAS message is transmitted between the RAN network element and the terminal device, and the NAS message carries the first identifier and / or the first corresponding relationship.

[0150] The data transmission method provided in the embodiments of the present application is described below with respect to different scenarios.

[0151] Scene 1

[0152] like Fig.10As shown, during the PDU session establishment process, the terminal device obtains three first identifiers, namely QFI=1, QFI=2 and QFI=3, from the mobile network element (such as the core network element). The terminal device sends a data packet to the UPF entity, and binds the data packets sent to different mobile network elements (such as the core network control plane element) to different QoS Flows; wherein, multiple QoS Flows can be in the same PDU session or in different PDU sessions. The UPF entity parses the QFI in the data packet and forwards different data packets to different network elements according to the QFI. For example, the data packet bound to the Qos Flow with QFI=1 is sent to the SMF entity, the data packet bound to the Qos Flow with QFI=2 is sent to the NEF entity, and the data packet bound to the Qos Flow with QFI=3 is sent to the NWDAF entity.

[0153] Scene 2

[0154] like Fig.11 As shown, the network device (AN node) preconfigures the data flow of QFI=1 of the first PDU session for sending network status information to the EC server, and the network status information is sent to the NEF entity through the UPF entity, and then sent to the EC server by the NEF entity. The first PDU session can be a session corresponding to a specific network slice and / or DNN, such as a PDU session corresponding to S-NSSAI=1.

[0155] The network device sends data to the UPF entity, and the data can be used to notify the EC server of the network status (such as changes in QoS). The UPF entity sends the data packet to the NEF entity according to the QFI=1 identifier carried in the data packet, and the NEF entity forwards the received data packet to the EC server; or, the network device sends the data packet to the UPF entity, and the UPF entity sends the data packet to the SMF entity according to the QFI=1 identifier, and the SMF entity sends the data packet to the EC server; or the network device sends the data packet to the UPF entity, and the UPF entity sends the data packet to the NEF entity according to the QFI=1 identifier, and the NEF entity sends the data packet to the EC server; or the network device directly sends the data packet to the EC server according to the QFI=1 identifier; after receiving the data packet, the EC server processes the data, such as data analysis. Therefore, in the embodiment of the present application, the UPF entity can send data to different mobile network elements (such as SMF entity, NEF entity, etc.), and the mobile network element sends it to the EC server. The UPF entity can also send data directly to the EC server.

[0156] Scene 3

[0157] like Fig.12As shown, during the PDU session establishment process, the mobile network element (such as the core network element) notifies the terminal device that the first identifier is "Data collection", and the data packet carrying the identifier "Data collection" can be used by the terminal device to collect data, such as collecting the policy execution status of the terminal device, terminal location information, and air interface channel quality related parameters.

[0158] When a terminal device needs to send data, the terminal device carries an identifier in the data packet header carrying the data: "Data collection". The UPF entity forwards the data packet to a mobile network element, such as an NWDAF entity, based on the identifier; the NWDAF entity can perform data analysis after collecting the terminal data.

[0159] The identifier can be carried in a data packet header of a certain layer of the air interface (such as an SDAP data packet header) and sent to the network device. Alternatively, the network device obtains the service identifier corresponding to the data packet based on the relationship between the DRB and the QoS flow, and the network device then adds the QoS Flow identifier to the GTP-U header and sends it to the UPF entity. Alternatively, a new protocol layer is introduced between the terminal device and the network element (such as the UPF entity), and the identifier is placed in the header of the new protocol layer and sent to the UPF entity.

[0160] Scene 4

[0161] like Fig.13 As shown, during the PDU session establishment process, the network device informs the terminal device that the first identifier is "LAN", and the data packet carrying the identifier "LAN" is used for local area network data transmission.

[0162] When the first terminal device (UE-1) needs to send relevant data, UE-1 carries the identifier "LAN" in the data packet header carrying the relevant data, and the first UPF entity (UPF-1) forwards the data packet to the second UPF entity (UPF-2) according to the identifier, and UPF-2 can further send the data packet to the second terminal device (UE-2). Or UPF-1 directly forwards the data packet to UE-2 according to the identifier.

[0163] The data transmission method provided in the embodiment of the present application sends a first identifier to a terminal device, or a network device, or a UPF entity through a mobile network network element (such as a core network network element), so that the terminal device, or the network device, or the UPF entity can learn the purpose (function) of the data packet identified by the first identifier, and then the terminal device, or the network device, or the UPF entity can transfer the data packet between the network elements corresponding to the first identifier, so that the core network control plane network elements can realize data applications such as big data analysis and network status monitoring based on user plane data, thereby improving the application scope of the data.

[0164] It should be understood that in the various embodiments of the present application, the size of the serial numbers of the above-mentioned processes does not mean the order of execution. 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 embodiments of the present application.

[0165] To implement the above data transmission method, the embodiment of the present application provides a mobile network element, an optional structural diagram of the mobile network element 600, as shown in FIG. Fig.14 As shown, including:

[0166] The first sending unit 601 is configured to send a first identifier to an electronic device, where the first identifier is used to transmit a data packet between the electronic device and a network element corresponding to the first identifier.

[0167] In some embodiments, the mobile network element further includes: a first receiving unit 602, configured to receive a first request message, where the first request message is used to request to obtain the first identifier.

[0168] In some embodiments, the first sending unit 601 is further configured to send a first corresponding relationship; the first corresponding relationship includes: a corresponding relationship between the first identifier and the network element, and / or a corresponding relationship between the first identifier and the service.

[0169] In some embodiments, the mobile network element further includes:

[0170] The second receiving unit 603 is configured to receive a second request message, where the second request message is used to request to obtain the first corresponding relationship.

[0171] In some embodiments, the network element includes at least any one of the following: a NWDAF entity, a NEF entity, a PCF entity, and a NWDAF entity corresponding to the first network slice.

[0172] In some embodiments, the service includes at least any one of the following: data analysis service and LAN service.

[0173] In some embodiments, the first correspondence is carried in a QoS parameter; or, the first correspondence is sent as a parameter independent of the QoS parameter.

[0174] In some embodiments, when the first correspondence is carried in the QoS parameters, the first correspondence is determined according to a first parameter in the QoS parameters.

[0175] In some embodiments, the QoS parameters may include, but are not limited to, one or more of the following: packet filter, Garanteed Biterate, Non-Garanteed Biterate, Maximum Bit Rate, Packet Delay Budget, Packet Error Rate, 5QI, and preemption priority parameters. The packet filter may include one or more of the following: IP5 tuple, Type Of Service (IPV4) / Traffic class (IPV6), and data flow direction.

[0176] In some embodiments, the first corresponding relationship is carried in an N2 message and / or a NAS message.

[0177] In some embodiments, the purpose of the first identifier is configured dynamically or statically; or, the purpose of the first identifier is default.

[0178] In some embodiments, the first identifier is carried in a QoS parameter; or, the first identifier is sent as a parameter independent of the QoS parameter.

[0179] In some embodiments, the first identifier is carried in an N2 message and / or a NAS message.

[0180] In some embodiments, the first identifier includes at least any one of the following: a quality of service flow identifier and / or a protocol data unit session identifier, a service identifier, and a server identifier.

[0181] In some embodiments, the mobile network element includes at least any one of the following: an AMF entity, an SMF entity, and a PCF entity.

[0182] In some embodiments, the electronic device includes at least one of the following: a terminal device, a wireless network device, a core network device, and a user plane functional entity.

[0183] In some embodiments, the mobile network element is applied to at least one of the following: a PDU session establishment process, a PDU session modification process, a registration process, and a service request process.

[0184] To implement the above data transmission method, an embodiment of the present application provides an electronic device, an optional structural diagram of the electronic device 800, as shown in FIG. Fig.15 As shown, including:

[0185] The third receiving unit 801 is configured to receive a first identifier; the first identifier is used to transmit a data packet between the electronic device and a network element corresponding to the first identifier.

[0186] The processing unit 802 is configured to add the first identifier to the data packet.

[0187] In some embodiments, the electronic device 800 further includes:

[0188] The second sending unit 803 is configured to send a first request message to the mobile network element, where the first request message is used to request to obtain the first identifier.

[0189] In some embodiments, the third receiving unit 801 is configured to receive a first corresponding relationship;

[0190] The first corresponding relationship includes: a corresponding relationship between the first identifier and the network element, and / or a corresponding relationship between the first identifier and the service.

[0191] In some embodiments, the electronic device 800 further includes:

[0192] The third sending unit 804 is configured to send a second request message to the mobile network element, where the second request message is used to request to obtain the first corresponding relationship.

[0193] In some embodiments, the service includes at least any one of the following: data analysis service and local area network (LAN) service.

[0194] In some embodiments, the first correspondence is carried in a QoS parameter; or, the first correspondence is sent as a parameter independent of the QoS parameter.

[0195] In some embodiments, when the first correspondence is carried in the QoS parameters, the first correspondence is determined according to a first parameter in the QoS parameters.

[0196] In some embodiments, the QoS parameters may include, but are not limited to, one or more of the following: packet filter, Garanteed Biterate, Non-Garanteed Biterate, Maximum Bit Rate, Packet Delay Budget, Packet Error Rate, 5QI, and preemption priority parameters. The packet filter may include one or more of the following: IP5 tuple, Type Of Service (IPV4) / Traffic class (IPV6), and data flow direction.

[0197] In some embodiments, the first corresponding relationship is carried in an N2 message and / or a NAS message.

[0198] In some embodiments, the network element includes at least any one of the following: a NWDAF entity, a NEF entity, a PCF entity, and a NWDAF entity corresponding to the first network slice.

[0199] In some embodiments, the purpose of the first identifier is configured dynamically or statically; or, the purpose of the first identifier is default.

[0200] In some embodiments, the first identifier is carried in a QoS parameter; or, the first identifier is sent as a parameter independent of the QoS parameter.

[0201] In some embodiments, the first identifier is carried in an N2 message and / or a NAS message.

[0202] In some embodiments, the first identifier includes at least any one of the following: a quality of service flow identifier and / or a protocol data unit session identifier, a service identifier, and a server identifier.

[0203] In some embodiments, the electronic device 800 further includes:

[0204] The fourth sending unit 805 is configured to send the data packet to a user plane function entity, so that the user plane function entity sends the data packet to the network element according to the first identifier.

[0205] In some embodiments, the electronic device 800 includes: a terminal device and / or a network device.

[0206] In some embodiments, the electronic device is applied to at least one of the following: a PDU session establishment process, a PDU session modification process, a registration process, and a service request process.

[0207] To implement the above data transmission method, the embodiment of the present application provides a user plane functional entity, an optional structural diagram of the user plane functional entity 900, as shown in FIG. Fig.16 As shown, including:

[0208] The fourth receiving unit 901 is configured to receive a data packet carrying a first identifier, where the first identifier is used to transmit a data packet between the UPF entity and a network element corresponding to the first identifier;

[0209] The fifth sending unit 902 is configured to send the data packet to the network element according to the first identifier.

[0210] In some embodiments, the fifth sending unit 902 is configured to send a third request message to the mobile network element, where the third request message is used to request to obtain the first identifier and / or the first corresponding relationship.

[0211] In some embodiments, the first corresponding relationship includes: a corresponding relationship between the first identifier and the network element, and / or a corresponding relationship between the first identifier and the service.

[0212] In some embodiments, the service includes at least any one of the following: data analysis service and LAN service.

[0213] In some embodiments, the first correspondence is carried in a QoS parameter; or, the first correspondence is sent as a parameter independent of the QoS parameter.

[0214] In some embodiments, when the first correspondence is carried in the QoS parameters, the first correspondence is determined according to a first parameter in the QoS parameters.

[0215] In some embodiments, the QoS parameters may include, but are not limited to, one or more of the following: packet filter, Garanteed Biterate, Non-Garanteed Biterate, Maximum Bit Rate, Packet Delay Budget, Packet Error Rate, 5QI, and preemption priority parameters. The packet filter may include one or more of the following: IP5 tuple, Type Of Service (IPV4) / Traffic class (IPV6), and data flow direction.

[0216] In some embodiments, the first corresponding relationship is carried in an N2 message and / or a NAS message.

[0217] In some embodiments, the first identifier is carried in a QoS parameter; or, the first identifier is sent as a parameter independent of the QoS parameter.

[0218] In some embodiments, the purpose of the first identifier is configured dynamically or statically; or, the purpose of the first identifier is default.

[0219] In some embodiments, the first identifier is carried in an N2 message and / or a NAS message.

[0220] In some embodiments, the first identifier includes at least any one of the following: a quality of service flow identifier and / or a protocol data unit session identifier, a service identifier, and a server identifier.

[0221] In some embodiments, the network element includes at least one of the following: a core network element, a terminal device, a network device, a functional module inside a UPF entity, an entity co-established with a UPF entity, or another user plane functional entity other than the user plane functional entity.

[0222] In some embodiments, the user plane functional entity is applied to at least one of the following: a PDU session establishment process, a PDU session modification process, a registration process, and a service request process.

[0223] The embodiment of the present application also provides a mobile network element device for executing the steps of the data transmission method executed by the above-mentioned mobile network element when running the computer program.

[0224] An embodiment of the present application also provides an electronic device, including a processor and a memory for storing a computer program that can be run on the processor, wherein the processor is used to execute the steps of the data transmission method executed by the above-mentioned electronic device when running the computer program.

[0225] An embodiment of the present application also provides a user plane functional entity, including a processor and a memory for storing a computer program that can be run on the processor, wherein the processor is used to execute the steps of the data transmission method performed by the above-mentioned user plane functional entity when running the computer program.

[0226] An embodiment of the present application also provides a chip, including: a processor, used to call and run a computer program from a memory, so that a mobile network element equipped with the chip executes the data transmission method executed by the above-mentioned terminal device.

[0227] An embodiment of the present application also provides a chip, including: a processor, used to call and run a computer program from a memory, so that an electronic device equipped with the chip executes the data transmission method executed by the above-mentioned network device.

[0228] An embodiment of the present application also provides a chip, including: a processor, used to call and run a computer program from a memory, so that a user plane functional entity installed with the chip executes the data transmission method executed by the above-mentioned network device.

[0229] The embodiment of the present application further provides a storage medium storing an executable program, and when the executable program is executed by a processor, the data transmission method executed by the mobile network element is implemented.

[0230] An embodiment of the present application further provides a storage medium storing an executable program, which, when executed by a processor, implements the data transmission method executed by the above-mentioned electronic device.

[0231] The embodiment of the present application further provides a storage medium storing an executable program, and when the executable program is executed by a processor, the data transmission method executed by the user plane functional entity is implemented.

[0232] An embodiment of the present application also provides a computer program product, including computer program instructions, which enable a computer to execute the data transmission method executed by the mobile network element.

[0233] An embodiment of the present application also provides a computer program product, including computer program instructions, which enable a computer to execute the data transmission method executed by the above electronic device.

[0234] An embodiment of the present application also provides a computer program product, including computer program instructions, which enable a computer to execute the data transmission method performed by the above-mentioned user plane functional entity.

[0235] An embodiment of the present application also provides a computer program, which enables a computer to execute the data transmission method executed by the mobile network element.

[0236] An embodiment of the present application also provides a computer program, which enables a computer to execute the data transmission method executed by the above electronic device.

[0237] The embodiment of the present application also provides a computer program, which enables a computer to execute the data transmission method performed by the above-mentioned user plane functional entity.

[0238] Fig.17 700 is a schematic diagram of the hardware structure of a device (mobile network element, electronic device or user plane functional entity) in an embodiment of the present application. The device 700 includes: at least one processor 701, a memory 702 and at least one network interface 704. The various components in the device 700 are coupled together through a bus system 705. It can be understood that the bus system 705 is used to realize the connection and communication between these components. In addition to the data bus, the bus system 705 also includes a power bus, a control bus and a status signal bus. However, for the sake of clarity, Fig.17 Various buses are labeled as bus system 705.

[0239] It can be understood that the memory 702 can be a volatile memory or a non-volatile memory, and can also include both volatile and non-volatile memories. Among them, the non-volatile memory can be ROM, programmable read-only memory (PROM), erasable programmable read-only memory (EPROM), electrically erasable programmable read-only memory (EEPROM), magnetic random access memory (FRAM), ferromagnetic random access memory, flash memory, magnetic surface memory, optical disk, or compact disc read-only memory (CD-ROM); the magnetic surface memory can be a disk memory or a tape memory. The volatile memory can be a random access memory (RAM), which is used as an external cache. By way of example but not limitation, many forms of RAM are available, such as static random access memory (SRAM), synchronous static random access memory (SSRAM), dynamic random access memory (DRAM), synchronous dynamic random access memory (SDRAM), double data rate synchronous dynamic random access memory (DDRSDRAM), enhanced synchronous dynamic random access memory (ESDRAM), synchronous link dynamic random access memory (SLDRAM), direct memory bus random access memory (DRRAM). The memory 702 described in the embodiments of the present application is intended to include but is not limited to these and any other suitable types of memory.

[0240] The memory 702 in the embodiment of the present application is used to store various types of data to support the operation of the device 700. Examples of such data include: any computer program for operating on the device 700, such as the application 7022. The program for implementing the method of the embodiment of the present application may be included in the application 7022.

[0241] The method disclosed in the above embodiment of the present application can be applied to the processor 701, or implemented by the processor 701. The processor 701 may be an integrated circuit chip with signal processing capabilities. In the implementation process, each step of the above method can be completed by the hardware integrated logic circuit in the processor 701 or the instruction in the form of software. The above processor 701 may be a general processor, a digital signal processor (DSP, Digital Signal Processor), or other programmable logic devices, discrete gates or transistor logic devices, discrete hardware components, etc. The processor 701 can implement or execute the methods, steps and logic block diagrams disclosed in the embodiments of the present application. The general processor may be a microprocessor or any conventional processor, etc. In combination with the steps of the method disclosed in the embodiment of the present application, it can be directly embodied as a hardware decoding processor to execute, or it can be executed by a combination of hardware and software modules in the decoding processor. The software module can be located in a storage medium, which is located in the memory 702, and the processor 701 reads the information in the memory 702 and completes the steps of the above method in combination with its hardware.

[0242] In an exemplary embodiment, the device 700 can be implemented by one or more application specific integrated circuits (ASICs), DSPs, programmable logic devices (PLDs), complex programmable logic devices (CPLDs), FPGAs, general-purpose processors, controllers, MCUs, MPUs, or other electronic components to perform the aforementioned method.

[0243] The present application is described with reference to the flowcharts and / or block diagrams of the methods, devices (systems), and computer program products according to the embodiments of the present application. It should be understood that each process and / or box in the flowchart and / or block diagram, as well as the combination of the processes and / or boxes in the flowchart and / or block diagram, can be implemented by computer program instructions. These computer program instructions can be provided to a processor of a general-purpose computer, a special-purpose computer, an embedded processor, or other programmable data processing device to generate a machine, so that the instructions executed by the processor of the computer or other programmable data processing device generate instructions for implementing the processes in the flowchart and / or block diagram. Figure 1 A process or multiple processes and / or boxes Figure 1 A device that provides the functions specified in a block or multiple blocks.

[0244] These computer program instructions may also be stored in a computer-readable memory capable of directing a computer or other programmable data processing device to operate in a specific manner, so that the instructions stored in the computer-readable memory produce an article of manufacture including an instruction device, which implements the process Figure 1 A process or multiple processes and / or boxes Figure 1 A function specified in one or more boxes.

[0245] These computer program instructions can also be loaded onto a computer or other programmable data processing device so that a series of operating steps are executed on the computer or other programmable device to produce a computer-implemented process, thereby providing instructions for implementing the process. Figure 1 A process or multiple processes and / or boxes Figure 1 A step that specifies a function in one or more boxes.

[0246] It should be understood that the terms "system" and "network" are often used interchangeably in this application. The term "and / or" in this application 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 application generally indicates that the associated objects before and after are in an "or" relationship.

[0247] The above is only a preferred embodiment of the present application and is not intended to limit the scope of protection of the present application. Any modifications, equivalent substitutions and improvements made within the spirit and principles of the present application should be included in the scope of protection of the present application.

Claims

1. A data transmission method, the method comprising: A mobile network element sends a first identifier to an electronic device, where the first identifier is used to transmit a data packet between the electronic device and the network element corresponding to the first identifier.

2. The method according to claim 1, wherein: The purpose of the first identifier is statically configured to the electronic device by the mobile network element.

3. The method according to claim 2, wherein: The first identifier may be used for: Transmitting data with a specific network element according to the first identifier; or, A specific service is executed according to the first identifier, and data is sent to a corresponding network element according to the service.

4. The method according to any one of claims 1 to 3, wherein: The method further comprises: The mobile network element receives a first request message, where the first request message is used to request to obtain the first identifier.

5. The method according to any one of claims 1 to 3, wherein: The method further includes: the mobile network element sending a first corresponding relationship; The first corresponding relationship includes: a corresponding relationship between the first identifier and the network element, and / or a corresponding relationship between the first identifier and the service.

6. The method according to claim 5, wherein: The method further comprises: The mobile network element receives a second request message, where the second request message is used to request to obtain the first corresponding relationship.

7. The method according to claim 5 or 6, wherein: The first correspondence relationship is carried in the QoS parameters; or, the first correspondence relationship is sent as a parameter independent of the QoS parameters.

8. The method according to any one of claims 1 to 3, wherein: The first identifier includes at least one of the following: Quality of service flow identifier and / or protocol data unit session identifier; Business logo; Server ID.

9. The method according to any one of claims 1 to 3, wherein: The mobile network element includes at least any one of the following: an access and mobility management function AMF entity, a session management function SMF entity and a policy control function PCF entity; and / or, The electronic device includes at least one of the following: terminal equipment, wireless network equipment, core network equipment and user plane functional entity.

10. A data transmission method, the method comprising: The electronic device receives a first identifier sent by a mobile network element; The first identifier is used to transmit data packets between the electronic device and a network element corresponding to the first identifier.

11. The method according to claim 10, wherein: The method further comprises: The electronic device sends a first request message to the mobile network element, where the first request message is used to request to obtain the first identifier.

12. The method according to claim 10 or 11, wherein: The method further includes: the electronic device receiving a first corresponding relationship; The first corresponding relationship includes: a corresponding relationship between the first identifier and the network element, and / or a corresponding relationship between the first identifier and the service.

13. The method according to claim 12, wherein: The method further comprises: The electronic device sends a second request message to the mobile network element, where the second request message is used to request to obtain the first corresponding relationship.

14. The method according to claim 12 or 13, wherein: The first corresponding relationship is carried in a quality of service QoS parameter; or, the first corresponding relationship is sent as a parameter independent of the QoS parameter.

15. The method according to any one of claims 10 to 14, wherein: The first identifier includes at least one of the following: Quality of service flow identifier and / or protocol data unit session identifier; Business logo; Server ID.

16. The method according to any one of claims 10 to 14, wherein: The mobile network element includes at least any one of the following: an access and mobility management function AMF entity, a session management function SMF entity and a policy control function PCF entity; and / or, The electronic device includes at least one of the following: terminal equipment, wireless network equipment, core network equipment and user plane functional entity.

17. A mobile network element, comprising: The first sending unit is configured to send a first identifier to an electronic device, where the first identifier is used to transmit a data packet between the electronic device and a network element corresponding to the first identifier.

18. An electronic device, comprising: A third receiving unit, configured to receive a first identifier; The first identifier is used to transmit data packets between the electronic device and a network element corresponding to the first identifier.

19. A mobile network element, comprising a processor and a memory for storing a computer program that can be run on the processor, wherein: When the processor is used to run the computer program, the processor executes the steps of the data transmission method according to any one of claims 1 to 9.

20. An electronic device comprising a processor and a memory for storing a computer program that can be run on the processor, wherein: When the processor is used to run the computer program, the processor executes the steps of the data transmission method according to any one of claims 10 to 16.

Images