Patent Description:
In the related art, the 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.

Documents <CIT> and <CIT> disclose RAN entities using identifier for data packet transmission.

Embodiments of the present application provide a data transmission method and device, which can expand the application scope of user plane data.

The data transmission method and device provided by the embodiments of the present application include: transmitting, by a mobile network element, a first identifier to a terminal device (User Equipment, UE), or a network device, or a UPF entity, so that the terminal device, or 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 transfer data packets with the network element corresponding to the first identifier, so that the mobile network element can realizes data applications such as big data analysis and network status monitoring according to the user plane data, which improves the application scope of the data.

In order to be able to understand the features and technical contents of the embodiments of the present application in more detail, the implementation of the embodiments of the present application will be described in detail below with reference to the accompanying drawings.

In the related art, a terminal device establishes a protocol data unit (Protocol Data Unit, PDU) session by interacting with the control plane network element of the core network, that is, establishes a connection between the terminal device and a user plane function (User Plane Function, UPF) entity. As shown in <FIG>, when the terminal device transmits 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 transmits the data packet to an application server, such as a server on a Data Network (DN). For downlink data, after receiving the data packet from the DN, the UPF entity determines to bind to the corresponding PDU session according to the downlink target IP address, and sends data to the terminal device through the PDU session.

In order to guarantee data transmission, mobile networks usually use Quality of Service (QoS) mechanisms. 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 and the DRB. The binding process of the QoS data flow in the PDU session is shown in <FIG>. One or more QoS flows can be mapped to a data radio bearer (DRB) for transmission. The connection between the terminal device and the access network (AN) device (e.g., a network device) as shown in <FIG> may be referred to as a DRB transmission.

When binding the QoS data flow, the uplink QoS data flow is 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 QoS rules. The downlink QoS data flow is 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.

The schematic diagram of the user plane protocol stack is shown in <FIG>, duplication/de-duplication is performed at the GPRS Tunnelling Protocol (GTP-U) layer on the UPF. The terminal side performs duplication/de-duplication at the service data adaptation protocol (SDAP) or packet data convergence protocol (PDCP) layer. AN device needs to perform protocol conversion operations.

The QoS flow identifier (Identify, ID) is added between the terminal device and the AN device through the SDAP header, and the QFI identifier is added to the GTP-U header between the AN device and the UPF entity. Therefore, the terminal device, the AN device and the 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 according to the mapping relationship between the DRB and the QoS flow. In this scenario, it is unnecessary to explicitly add the QFI identifier to the SDAP packet header.

With the increasing demand for big data in operator networks and the rise of edge computing (EC) services, the applicant found that some user plane data packets are required to be forwarded to the core network control plane network elements instead of being transmitted to the external application server. These data can be used for big data analysis, network status monitoring and other purposes. The process of sending data packets through a PUD session by a terminal device is shown in <FIG>. When the user plane data packet is required to be forwarded to the core network control plane network element, the terminal device can send the data packet by a PDU session to different core network elements, such as session management function (SMF) entity, network exposure function (NEF) entity, or network data analysis function (NWDAF) entity.

The technical solutions of the embodiments of the present application can be applied to various communication systems, for example: 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) systems, advanced long term evolution (LTE-A) systems, new radio (NR) systems, evolution systems for NR systems, LTE-based access to unlicensed spectrum (LTE-U) system, NR-based access to unlicensed spectrum (NR-U) system, universal mobile telecommunication system (UMTS), global Worldwide interoperability for microwave access (WiMAX) communication systems, wireless local area networks (WLAN), wireless fidelity (WiFi), next-generation communication systems or other communication systems, etc..

The system architecture and service scenarios described in the embodiments of the present application are for the purpose of illustrating the technical solutions of the embodiments of the present application more clearly. With the evolution of the 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.

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

In this embodiment of the present application, the terminal device may be any terminal, for example, the terminal device may be user equipment of machine type communication. That is to say, the terminal device may also be referred to as user equipment UE, mobile station (MS), mobile terminal (mobile terminal), terminal, etc. The terminal device may communicate with one or more core network elements through the radio access network (RAN). For example, the terminal device may be a mobile phone (or "cellular" phone), a computer with a mobile terminal, etc., and for example, the terminal device may also be a portable, packetable, handheld, computer built-in or vehicle mounted mobile devices that exchange language and/or data with the radio access network. There is no specific limitation in the embodiments of the present application.

Optionally, network device and terminal device can be deployed on land, including indoor or outdoor, handheld or vehicle-mounted. They can also be deployed on surface, or in air such as on aircraft, balloons and artificial satellites. The embodiments of the present application do not limit the application scenarios of the network device and the terminal device.

Optionally, communication between a network device and a terminal device and between a terminal device and a terminal device can be performed through licensed spectrum (licensed spectrum), or through unlicensed spectrum (unlicensed spectrum), or through both licensed spectrum and unlicensed spectrum. Communication between network device and terminal device and between terminal device and terminal device can be carried out through the spectrum below <NUM> gigahertz (GHz), or through the frequency spectrum above <NUM>, or both the frequency spectrum below <NUM> and the frequency spectrum above <NUM> 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.

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 communication, but 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 system.

Exemplarily, the communication system <NUM> applied in this embodiment of the present application is shown in <FIG>. The communication system <NUM> may include a network device <NUM>, and the network device <NUM> may be a device that communicates with a terminal device <NUM> (or referred to as a communication terminal, a terminal). The network device <NUM> may provide communication coverage for a particular geographic area and may communicate with terminal devices located within the coverage area. Optionally, the network device <NUM> may be a base station (Base Transceiver Station, BTS) in a GSM system or a CDMA system, a base station (NodeB, NB) in a WCDMA system, or an evolved base station in an LTE system (Evolutional Node B, eNB or eNodeB), or a wireless controller in a cloud radio access network (CRAN), or the network device can be a mobile switching center, relay station, access point, on-board equipment, wearable devices, hubs, switches, bridges, routers, network-side devices in <NUM> networks, or network devices in the future evolved Public Land Mobile Network (PLMN), etc..

The communication system <NUM> also includes at least one terminal device <NUM> located within the coverage of the network device <NUM>. "Terminal device" as used herein includes, but is not limited to, a device configured to receive/transmit communication signal through a wired line such as public switched telephone networks (PSTN), digital subscriber line (DSL), digital cable, direct cable connections and/or another data connection/network; and/or through wireless interface such as cellular network, wireless local area network (WLAN), digital television network such as DVB-H network, satellite network, AM-FM broadcast transmitter, and/or another terminal device; and/or an Internet of Things (IoT) device. The terminal device configured to communicate via the 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, a satellite or cellular telephone; a personal communications system (PCS) terminal that may combine cellular radio telephones with data processing, facsimile, and data communications capabilities; a PDA that may include radio telephones, pagers, Internet/Intranet access, web browser, memo pad, calendar, and/or global positioning system (GPS) receiver; and conventional laptop and/or palmtop receivers or other electronic devices including radiotelephone transceiver. The terminal device may refer to an access terminal, user equipment subscriber unit, subscriber station, mobile site, mobile station, remote station, remote terminal, mobile device, user terminal, terminal, wireless communication device, user agent, or user equipment. The access terminal may 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 wireless handheld device with communication function, a computing device or other processing device connected to wireless modems, in-vehicle devices, wearable devices, terminal devices in <NUM> networks or in future evolved PLMNs, etc..

Optionally, device to device (D2D) communication may be performed between the terminal devices <NUM>.

Optionally, the <NUM> system or <NUM> network may also be referred to as a new radio (New Radio, NR) system or an NR network.

<FIG> exemplarily shows one network device and two terminal devices. Optionally, the communication system <NUM> may include multiple network devices and the coverage of each network device may include other numbers of terminal devices, which is not limited by the embodiment of the present application.

Optionally, the communication system <NUM> may further include other network entities such as a network controller and a mobility management entity, which are not limited in this embodiment of the present application.

It should be understood that, in the embodiments of the present application, a device having a communication function in the network/system may be referred to as a communication device. Taking the communication system <NUM> shown in <FIG> as an example, the communication device may include a network device <NUM> and a terminal device <NUM> with a communication function, and the network device <NUM> and the terminal device <NUM> may be the specific devices described above, which will not be repeated here. The communication device may also include other devices in the communication system <NUM>, such as other network entities such as a network controller, a mobility management entity, etc., which are not limited in this embodiment of the present application.

An optional processing flow of the data transmission method provided by an example not claimed by the invention, as shown in <FIG>, may include the following steps.

Step S201, transmitting, by a mobile network element, a first identifier to an electronic device, wherein the first identifier is used for transmitting a data packet between the electronic device and a network element corresponding to the first identifier.

In some embodiments, the electronic device may add the first identifier to the data packet, and transmit it to the UPF entity, and the UPF entity transmits the first identifier to the corresponding network element according to the first identifier. In other embodiments, when the UPF entity receives the data packet transmitted by the corresponding network element, the first identifier is determined according to the network element that transmits the data packet, and is added to the data packet (for example, packet header of a certain protocol layer of the data packet) and transmitted to the electronic device.

In some embodiments, the first identifier may be an existing identifier, such as a quality of service flow identifier (QoS Flow ID) and/or a protocol data unit session identifier (PDU Session ID). Alternatively, the first identifier is a new identifier, such as a service identifier, a server identifier, and the like.

In some embodiments, the first identifier is carried in a QoS parameter. The QoS parameter may be the content in a QoS profile, that is, the first identifier may be used as a part of the QoS profile. The first identifier may be a part of the QoS parameter, and the first identifier may also be indirectly determined according to the QoS parameter. For example, the first identifier is the QFI determined according to the <NUM> QoS Index (5QI) parameter in the QoS Profile.

In some embodiments, the QoS parameter may include but not limited to, one or more of the following: a packet filter, a guaranteed rate (Garanteed Biterate), and a non-guaranteed rate (Non-Garanteed Biterate), a maximum bit Rate, a packet delay budget, a packet error rate, a 5QI and a preemption priority parameter. The packet filter may include one or more of the following: IP5 tuple, Type of Service (IPV4)/Traffic class (IPV6), and data flow direction.

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

In some embodiments, the usage (function) of the first identifier may be configured in a dynamic or static manner, that is, a mobile network element may configure the usage of the first identifier to the electronic device in a dynamic or static manner. Alternatively, the usage of the first identifier may also be default. In the case where the usage of the first identifier is a default, the usage of the first identifier may be determined through negotiation between devices, or pre-agreed, or defined through a standard protocol such as 3GPP. The usage of the first identification includes transmitting data between the electronic device and a specific network element according to the first identification; or the usage of the first identification includes executing a specific service according to the first identification, and transmitting data to the corresponding network element according to the service, such as the electronic device transmitting the data to the UPF entity, the UPF entity transmitting the data to the SMF entity according to the first identifier, and the SMF entity transmitting the data to the EC server; or the electronic device transmitting the data to the UPF entity, the UPF entity transmitting the data to the NEF entity according to the first identifier, and the NEF entity transmitting the data to the EC server; or the electronic device transmitting the data to the NWDAF entity, and the NWDAF entity processes the data, such as data analysis, hash mapping, etc.; or the electronic device transmitting the data to a domain name system (DNS) entity, and the DNS entity being used for DNS query services.

In some embodiments, the first identifier is carried in the N2 message and/or the NAS message. The N2 message may be a message used for transmitting information between the core network element and the RAN node. The NAS message may be a message used for transmitting information between the core network element and the terminal device, and the message may be pass-through to the terminal device through the RAN.

In some embodiments, the network element includes an NEF entity, and in other examples not covered by the invention, the network element may also include at least any one of the following: an NWDAF entity, a PCF entity, an NWDAF entity corresponding to a 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 is an SMF entity, and in other examples not covered by the invention, the core network element may also be an AMF entity, or a PCF entity or the like.

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 interaction between the information of the mobile network and a medical server can be realized 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 subscription information. The SMF entity can be used for session management. The AMF entity can be used for mobility management.

In some embodiments, the method may further include:.

Step S200, receiving, by the mobile network element, a first request message, wherein the first request message is used to request to acquire the first identifier.

In some embodiments, the mobile network element receives the first request message sent by the electronic device, where the first request message is used to request the mobile network element to transmit the first identifier to the electronic device.

Step S202, transmitting, by the mobile network element, a first correspondence to the electronic device.

In some embodiments, the mobile network element transmits the first correspondence to the electronic device, and the electronic device may be at least one of a terminal device, a network device, and a UPF entity.

In some embodiments, the first correspondence may be carried in a QoS parameter. The QoS parameter may be content in a QoS profile, that is, the first correspondence may be used as a part of the QoS profile. The first correspondence is a part of the QoS parameter, and the first correspondence may also be indirectly determined according to the QoS parameter. For example, the first correspondence is the QFI determined according to the 5QI parameter in the QoS profile. Alternatively, the first correspondence is sent as a parameter independent of the QoS parameter.

In some embodiments, the first correspondence is carried in the N2 message and/or the NAS message. The N2 message may be a message used for transmitting information between the core network element and the RAN node, and the NAS message may be a message used for transmitting information between the core network element and the terminal device, which may be pass-through to the terminal device through the RAN.

In some embodiments, the first correspondence includes: a correspondence between the first identifier and the network element, and/or a correspondence between the first identifier and a service.

For the correspondence between the first identifier and the network element, it may be that the identifier-<NUM> corresponds to the NWDAF entity, the identifier-<NUM> corresponds to the NEF entity, the identifier-<NUM> corresponds to the PCF entity, the identifier-<NUM> corresponds to the NWDAF entity of the first network slice, and the identifier-<NUM> corresponds to the NWDAF entity of the second network slice, and the like. The NWDAF entity can exist alone, or can be co-located with other existing network elements, such as co-located with one of UPF entity, SMF entity, and NEF entity. The NEF entity can exist alone, or can be co-located with other existing network elements, such as co- located with the UPF entity.

For the correspondence between the first identifier and the service, it may be that the identifier-<NUM> corresponds to the data analytics service, the identifier-<NUM> corresponds to the local area network (LAN) service, the identifier-<NUM> corresponds to the edge computing service, the identifier-<NUM> corresponds to DNS service, and the identifier-<NUM> corresponds to network information notification service.

Step S202', receiving, by the mobile network element, a second request message, wherein the second request message is used to request to acquire the first correspondence.

In some embodiments, the mobile network element receives the second request message sent by the electronic device, wherein the second request message is used to request the mobile network element to send the first correspondence to the electronic device.

It should be noted that the data transmission method provided by the embodiments of the present application can be applied to scenarios such as a PDU session establishment process, a PDU session modification process, a registration process, and a service request process.

Another optional processing flow of the data transmission method provided by the embodiment of the present application, as shown in <FIG>, includes the following steps:.

Step S301, receiving, by the electronic device, a first identifier, wherein the first identifier is used for transmitting a data packet between the electronic device and a network element corresponding to the first identifier.

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

In some embodiments, the electronic device may be a terminal device and/or a network device, and the mobile network element is an SMF entity, and in other examples not covered by the invention, the mobile network element may also be an AMF entity, or a PCF entity, or the like.

In some embodiments, the first identifier may be an existing identifier, such as QoS Flow ID and/or PDU Session ID. Alternatively, the first identifier is a new identifier, such as a service identifier, a server identifier, and the like.

In some embodiments, the first identifier is carried in a QoS parameter. The QoS parameter may be the content in a QoS profile, that is, the first identifier may be used as a part of the QoS profile. The first identifier may be explicitly carried in the QoS parameter, and the first identifier may also be indirectly determined according to the QoS parameter. For example, the first identifier is the QFI determined according to the 5QI parameter in the QoS profile.

In some embodiments, the electronic device may indirectly determine the service or server corresponding to the data flow according to the QoS parameter. For example, the service or server corresponding to the data flow is determined according to the 5QI parameter in the QoS profile. The corresponding relationship may be configured on the electronic device by default (for example, by means of standardized definition or pre-configuration).

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 parameter. The packet filter may include one or more of the following: IP5 tuple, Type Of Service (IPV4)/Traffic class (IPV6), and data flow direction.

In some embodiments, the usage (function) of the first identifier may be configured in a dynamic or static manner, that is, a mobile network element may configure the usage of the first identifier to the electronic device in a dynamic or static manner. Alternatively, the usage of the first identifier may also be default. In the case where the usage of the first identifier is a default, the usage of the first identifier may be determined through negotiation between devices, or pre-agreed, or defined through a standard protocol such as 3GPP. The usage of the first identification includes transmitting data with a specific network element according to the first identification; or the usage of the first identification includes executing a specific service according to the first identification, and transmitting data to the corresponding network element according to the service, such as the electronic device transmitting the data to the UPF entity, the UPF entity transmitting the data to the SMF entity according to the first identifier, and the SMF entity transmitting the data to the EC server; or the electronic device transmitting the data to the UPF entity, the UPF entity transmitting the data to the NEF entity according to the first identifier, and the NEF entity transmitting the data to the EC server; or the electronic device transmitting the data to the NWDAF entity, and the NWDAF entity processes the data, such as data analysis, hash mapping, etc.; or the electronic device transmitting the data to a DNS entity, and the DNS entity being used for DNS query services.

In some embodiments, the network element includes an NEF entity, and in other examples not covered by the invention, the network element may also include at least any one of the following: an NWDAF entity, a PCF entity, an NWDAF entity corresponding to a first network slice, and a 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 is an SMF entity, and in other examples not covered by the invention, the mobile network element may also be an AMF entity, or a PCF entity or the like.

For 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 transmit it to the UPF entity, and the UPF entity may, according to the first identifier, transmit it to the corresponding network element. In other embodiments, when the UPF entity receives the data packet transmitted by the corresponding network element, the first identifier is determined according to the network element that transmits the data packet, and is added to the data packet (packet header of a certain protocol layer of the data packet) and transmitted to the electronic device.

Step S302, adding, by the electronic device, the first identifier to the data packet.

In some embodiments, the electronic device adds the first identifier to the data packet, and transmits the data packet to a UPF entity, and the UPF entity transmits the data packet according to the first identification to the corresponding network element, such as a mobile network element (core network element), a terminal device, a network device, a functional module inside the UPF entity, an entity co-located with the UPF entity, or another UPF entity other than the UPF entity.

Step S300a, transmitting, by the electronic device, a first request message to a mobile network element, wherein the first request message is used to request to acquire the first identifier.

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

In some embodiments, the method may further include:
Step S300b, receiving, by the electronic device, the first correspondence.

In some embodiments, the electronic device receives the first correspondence sent by a mobile network element, wherein the first correspondence includes: a correspondence between the first identifier and the network element, and/or a correspondence between the first identifier and a service.

In some embodiments, the first correspondence may be carried in a QoS parameter. The QoS parameter may be content in a QoS profile, that is, the first correspondence may be used as a part of the QoS profile. The first correspondence may be a part of the QoS parameter, and the first correspondence may also be indirectly determined according to the QoS parameter. For example, the first correspondence is the QFI determined according to the 5QI parameter in the QoS profile. Alternatively, the first correspondence is sent as a parameter independent of the QoS parameter.

Step S300b', transmitting, by the electronic device, a second request message to the mobile network element, wherein the second request message is used to request to acquire the first correspondence.

In some embodiments, the second request message is used to request the mobile network element to send the first correspondence to the electronic device.

Another optional processing flow of the data transmission method provided by an example not claimed by the invention, as shown in <FIG>, includes the following steps:
Step S401, receiving, by a UPF entity, a data packet carrying a first identifier, wherein the first identifier is used for transmitting the data packet between the UPF entity and a network element corresponding to the first identifier.

In some embodiments, the UPF entity receives a data packet transmitted by a network device or a terminal device and carrying the first identifier.

In some embodiments, the first identifier is carried in a QoS parameter. The QoS parameter may be the content in a QoS profile, that is, the first identifier may be used as a part of the QoS profile. The first identifier may be a part of the QoS parameter, and the first identifier may also be indirectly determined according to the QoS parameter. For example, the first identifier is the QFI determined according to the 5QI parameter in the QoS profile.

For the data packet transmission between the UPF entity 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 transmit it to the UPF entity, and the UPF entity may, according to the first identifier, transmit it to the corresponding network element. In other embodiments, when the UPF entity receives the data packet transmitted by the corresponding network element, the first identifier is determined according to the network element that transmits the data packet, and is added to the data packet (packet header of a certain protocol layer of the data packet) and transmitted to the electronic device.

In some embodiments, the method may further include:
Step S400, transmitting, by the UPF entity, a third request message to the mobile network element, wherein the third request message is used to request to acquire the first identifier and/or the first correspondence.

Step S402, transmitting, by the UPF entity, the data packet to the network element according to the first identifier.

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 the UPF entity, an entity co-located with the UPF entity, or another UPF entity other than said UPF entity.

Hereinafter, the PDU session establishment process is taken 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, and the first identifier is required to be added to the packet header of the user plane data packet, so that after the UPF entity detects the first identifier, the data packet is forwarded to the corresponding network element. Before this, optionally, the terminal device may 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 by the embodiment of the present application, as shown in <FIG>, includes:
Step S501, transmitting, by the terminal device, a session establishment request to the SMF entity, wherein the session establishment request carries the requested first identifier and/or first correspondence.

Step S502, transmitting, by the SMF entity, an establishing request to the UPF entity.

In some embodiments, in the process of transmitting, by the SMF entity, the establishment request to the UPF entity, the first identifier and/or the first correspondence may be carried.

Step S503, transmitting, by the SMF entity, a session establishment request to the RAN network element, wherein the session establishment request carries the requested first identifier and/or the first correspondence.

In some embodiments, the session establishment request may carry an NAS message.

Step S504, performing, between the RAN network element and the terminal device, air interface resource establishment and NAS message transmission, wherein the NAS message carries the first identifier and/or the first correspondence.

The data transmission methods provided by the embodiments of the present application are described below for different scenarios.

As shown in <FIG>, in the process of establishing a PDU session, the terminal device obtains three first identifiers from a mobile network element (such as a core network element), which are QFI=<NUM>, QFI=<NUM> and QFI=<NUM> respectively. The terminal device transmits data packets to the UPF entity, and binds the data packets sent to different mobile network elements (such as core network control plane network elements) to different QoS flows. In this embodiment, multiple QoS flows may be in a same PDU session or may be 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, transmit the data packet bound to the QoS flow with QFI=<NUM> to the SMF entity, transmit the data packet bound to the QoS flow with QFI=<NUM> to the NEF entity, and transmit the data packet bound to the QoS flow with QFI=<NUM> to the NWDAF entity.

As shown in <FIG>, the network device (AN node) preconfigures that the data flow of QFI=<NUM> of the first PDU session is used to transmit the network status information to the EC server. After the network status information is transmitted to the NEF entity through the UPF entity, the information is transmitted by the NEF entity to the EC server. The first PDU session may be a session corresponding to a specific network slice and/or DNN, such as a PDU session corresponding to S-NSSAI=<NUM>.

The network device transmits data to the UPF entity, the data can be used to notify the EC server of the network status (such as QoS changes). The UPF entity transmits the data packet to the NEF entity according to the identifier of QFI=<NUM> carried in the data packet, and the NEF entity forwards the received data packet to the EC server; or, the network device transmits the data to the UPF entity, the UPF entity transmits the data packet to the SMF entity according to the identifier of QFI=<NUM>, and the SMF entity transmits the data packet to the EC server; or the network device transmits the data packet to the UPF entity, the UPF entity transmits the data packet to the NEF entity according to the identifier of QFI=<NUM>, and the NEF entity transmits the data packet to the EC server; or the network device directly transmits the data packet to the EC server according to the identifier of QFI=<NUM>. The EC server processes the data, such as data analysis after receiving the data packet. Therefore, in the embodiment of the present application, the UPF entity may transmit data to different mobile network elements (e.g., SMF entity, NEF entity, etc.), and the mobile network element transmits the data to the EC server. The UPF entity can also transmit data directly to the EC server.

As shown in <FIG>, during the establishment of the PDU session, 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 the policy implementation of terminal equipment, terminal location information, and parameters related to air interface channel quality.

When the terminal device needs to transmit data, the terminal device carries an identifier: "Data collection" in the header of the data packet carrying the data. The UPF entity forwards the data packet to the mobile network element according to the identifier, such as the NWDAF entity. The NWDAF collects the terminal data and then uses the data for data analysis.

The identifier may be carried in a data packet header (e.g., SDAP data packet header) of a certain layer of the air interface and transmitted to the network device. Alternatively, the network device obtains the service identifier corresponding to the data packet according to the relationship between the DRB and the QoS flow, and the network device adds the QoS flow identifier to the GTP-U packet header and transmit 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 transmitted to the UPF entity.

As shown in <FIG>, during the establishment of the PDU session, the network device informs the terminal device that the first identifier is "LAN", and the data packet carrying the identifier "LAN" is used for data transmission in the local area network.

When the first terminal device (UE-<NUM>) needs to transmit related data, the UE-<NUM> carries the identifier "LAN" in the header of the data packet carrying the related data, and the first UPF entity (UPF-<NUM>) forwards the data packet to the second UPF entity (UPF-<NUM>) according to the identifier "LAN". The UPF-<NUM> may further forward the data packet to the second terminal device (UE-<NUM>). Alternatively, the UPF-<NUM> directly forwards the data packet to UE-<NUM> according to the identifier.

In the data transmission method provided by the embodiments of the present application, the first identifier is transmitted by the mobile network element to the terminal device or the network device or the UPF entity, so that the terminal device, or network device, or the UPF entity can know the purpose (function) of the data packet of first identifier, and then the terminal device, or the network device, or the UPF entity can transfer data packets with the network element corresponding to the first identifier, so that the core network control plane network element can realizes data applications such as big data analysis and network status monitoring according to the user plane data, which improves the application scope of the data.

It should be understood that, in various embodiments of the present application, the size of the sequence numbers of the above-mentioned processes does not mean the order of execution, and the execution order of each process should be determined by its functions and internal logic, and shall not constitute any limitation to the process of implementation of the embodiments of the present application.

To implement the above data transmission method, an example not claimed by the invention provides a mobile network element. An optional structural schematic diagram of the mobile network element <NUM>, as shown in <FIG>, includes:
a first transmitting unit <NUM>, configured to transmit a first identifier to an electronic device, wherein the first identifier is used for transmitting a data packet between the electronic device and a network element corresponding to the first identifier.

In some embodiments, the mobile network element further includes: a first receiving unit <NUM>, configured to receive a first request message, wherein the first request message is used to request to acquire the first identifier.

In some embodiments, the first transmitting unit <NUM> is further configured to transmit a first correspondence, wherein the first correspondence comprises: a correspondence between the first identifier and the network element, and/or a correspondence between the first identifier and a service.

In some embodiments, the mobile network element further includes:
a second receiving unit <NUM>, configured to receive a second request message, wherein the second request message is used to request to acquire the first correspondence.

In some embodiments, the network element includes an NEF entity, and in other examples not covered by the invention, the network element may also include at least any one of: an NWDAF entity, a PCF entity, and an NWDAF entity corresponding to a first network slice.

In some embodiments, the service includes at least any one of: a data analysis services and a LAN services.

In some embodiments, the first correspondence is carried in a QoS parameter; or the first correspondence is transmitted as a parameter independent of the QoS parameter.

In some embodiments, in a case where the first correspondence is carried in the QoS parameter, the first correspondence is determined according to a first parameter in the QoS parameter.

In some embodiments, the first correspondence is carried in an N2 message and/or an NAS message.

In some embodiments, a usage of the first identifier is configured in a dynamic or static manner; or the usage of the first identifier is default.

In some embodiments, the first identifier is carried in a QoS parameter; or the first identifier is transmitted as a parameter independent of the QoS parameter.

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

In some embodiments, the first identifier includes at least any one of: a QoS flow ID and/or a PDU session ID; a service ID; and a server ID.

In some embodiments, the mobile network element includes is an SMF entity, and in other examples not covered by the invention, the mobile network element may also be at least any one of: an AMF entity and a PCF entity.

In some embodiments, the electronic device include a user plane functional entity UPF, and in other examples not covered by the invention, the electronic device may also include at least one of: a terminal device, a wireless network device, a core network device.

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

To implement the above data transmission method, an embodiment of the present application provides an electronic device. An optional structural schematic diagram of the electronic device <NUM>, as shown in <FIG>, includes:.

In some embodiments, the electronic device <NUM> further includes:
a second transmitting unit <NUM>, configured to transmit a first request message to the mobile network element, wherein the first request message is used to request to acquire the first identifier.

In some embodiments, the third receiving unit <NUM> is configured to receive a first correspondence,
wherein the first correspondence includes: a correspondence between the first identifier and the network element, and/or a correspondence between the first identifier and a service.

In some embodiments, the electronic device <NUM> further includes:
a third transmitting unit <NUM>, configured to transmit a second request message to the mobile network element, wherein the second request message is used to request to acquire the first correspondence.

In some embodiments, the electronic device <NUM> further includes:
a fourth transmitting unit <NUM>, configured to transmit the data packet to a user plane functional entity, so that the user plane functional entity transmits the data packet to the network element according to the first identifier.

In some embodiments, the electronic device <NUM> includes: a terminal device and/or a network device.

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

To implement the above data transmission method, an example not claimed by the invention provides a user plane functional entity. An optional structural schematic diagram of the user plane functional entity <NUM>, as shown in <FIG>, includes:.

In some embodiments, the fifth transmitting unit <NUM> is configured to transmit a third request message to the mobile network element, wherein the third request message is used to request to acquire the first identifier and/or a first correspondence.

In some embodiments, the first correspondence is carried in an N2 message and/or a non-access stratum NAS message.

In some embodiments, the network element includes at least one of: a network element of core network, a terminal device, a network device, a functional module in the user plane functional entity, an entity co-located with the user plane functional entity, and another user plane functional entity other than the user plane functional entity.

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

<FIG> is a schematic diagram of a hardware structure of a device (the mobile network element, the electronic device, or the user plane functional entity) according to an example not claimed by the invention. The device <NUM> includes: at least one processor <NUM>, a memory <NUM>, and at least one network interface <NUM>. The various components in device <NUM> are coupled together by bus system <NUM>. It can be understood that the bus system <NUM> is used to implement the connection communication between these components. In addition to a data bus, the bus system <NUM> also includes a power bus, a control bus and a status signal bus. However, for the sake of clarity, the various buses are labeled as bus system <NUM> in <FIG>.

It will be appreciated that memory <NUM> may be volatile memory or non-volatile memory, and may include both volatile and non-volatile memories. The non-volatile memory may be ROM, programmable read-only memory (PROM), erasable programmable read-only memory (EPROM), electrically erasable programmable read-only memory (EEPROM), ferromagnetic random access memory (FRAM), flash memory, magnetic surface memory, optical disc, or compact disc read-only memory (CD-ROM), wherein magnetic surface memory can be disk memory or tape memory. The volatile memory may be random access memory (RAM), which is used as an external cache memory. By way of example and 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), synclink dynamic random access memory (SLDRAM), direct rambus random access memory (DRRAM). The memory <NUM> described in the embodiments of the present disclosure is intended to include, but not limited to, these and any other suitable types of memory.

The memory <NUM> in this embodiment of the present disclosure is used to store various types of data to support the operation of the device <NUM>. Examples of such data include: any computer program used to operate on device <NUM>, such as application program <NUM>. The program for implementing the method of the embodiment of the present disclosure may be included in the application program <NUM>.

The methods disclosed in the above embodiments of the present disclosure may be applied to the processor <NUM> or implemented by the processor <NUM>. The processor <NUM> may be an integrated circuit chip with signal processing capability. In the implementation process, each step of the above-mentioned method can be completed by an integrated logic circuit of hardware in the processor <NUM> or an instruction in the form of software. The above-mentioned processor <NUM> may be a general-purpose processor, a digital signal processor (DSP), or other programmable logic devices, discrete gate or transistor logic devices, discrete hardware components, and the like. The processor <NUM> may implement or execute the methods, steps, and logical block diagrams disclosed in the embodiments of this disclosure. A general-purpose processor may be a microprocessor or any conventional processor or the like. The steps of the method disclosed in the embodiments of the present disclosure can be directly embodied as being executed by a hardware decoding processor, or executed by a combination of hardware and software modules in the decoding processor. The software module may be located in a storage medium, and the storage medium is located in the memory <NUM>, and the processor <NUM> reads the information in the memory <NUM>, and completes the steps of the foregoing method in combination with its hardware.

In an exemplary embodiment, the device <NUM> may be implemented by one or more application specific integrated circuit (ASIC), DSP, programmable logic device (PLD), complex programmable logic device (CPLD), FPGA, general-purpose processor, controller, MCU, MPU, or other electronic component implementation for performing the above method.

The present disclosure is described with reference to flowchart illustrations and/or block diagrams of methods, apparatus (systems), and computer program products according to embodiments of the present disclosure. It will be understood that each process and/or block in the flowchart illustrations and/or block diagrams, and combinations of processes and/or blocks in the flowchart illustrations and/or block diagrams, can be implemented by computer program instructions. These computer program instructions may be provided to the processor of a general purpose computer, dedicated computer, embedded processor or other programmable data processing device to produce a machine such that the instructions executed by the processor of the computer or other programmable data processing device produce a means for implementing the functions specified in one process or multiple processes in the flowchart and/or one block or multiple blocks in the block diagram.

These computer program instructions may also be stored in a computer-readable memory capable of directing a computer or other programmable data processing apparatus to function in a particular manner, such that the instructions stored in the computer-readable memory result in an article of manufacture including instruction means, wherein the instruction means implements the functions specified in one process or multiple processes in the flowchart and/or one block or multiple blocks in the block diagram.

These computer program instructions can also be loaded on a computer or other programmable data processing device to cause a series of operational steps to be performed on the computer or other programmable device to produce a computer-implemented process such that the instructions provide steps for implementing the functions specified in one process or multiple processes in the flowchart and/or one block or multiple blocks in the block diagram.

Claim 1:
A method for data transmission, the method comprising:
receiving (S301), by an electronic device, a first identifier from a mobile network element, wherein the first identifier is used for transmitting a data packet between the electronic device and a network exposure function, NEF, entity corresponding to the first identifier; and
adding (S302), by the electronic device, the first identifier to the data packet,
wherein the mobile network element comprises a session management function, SMF, entity, and wherein the electronic device comprises a user plane functional, UPF, entity.