CN117295111A

CN117295111A - Data transmission method and device, UPF entity and communication entity

Info

Publication number: CN117295111A
Application number: CN202210695791.9A
Authority: CN
Inventors: 孙军帅
Original assignee: China Mobile Communications Group Co Ltd; China Mobile Communications Ltd Research Institute
Current assignee: China Mobile Communications Group Co Ltd; China Mobile Communications Ltd Research Institute
Priority date: 2022-06-20
Filing date: 2022-06-20
Publication date: 2023-12-26

Abstract

The application discloses a data transmission method, a data transmission device, a UPF entity and a communication entity, and relates to the technical field of communication. The method is applied to a user plane function UPF entity and comprises the following steps: transmitting IP data packets with a first communication entity through an IP flow connected with the first communication entity; wherein there are one or more protocol data unit, PDU, sessions between the UPF entity and the first communication entity, each PDU session comprising one or more IP flows; the first communication entity is a layer three user plane L3UP functional entity or a service data adaptation protocol SDAP entity. According to the scheme, the UPF entity transmits the IP data packet with the L3UP functional entity or the SDAP entity through the IP flow connected with the L3UP functional entity or the SDAP entity; thereby enabling communication between the UPF and the L3UP or SDAP.

Description

Data transmission method and device, UPF entity and communication entity

Technical Field

The application belongs to the technical field of communication, and particularly relates to a data transmission method, a data transmission device, a UPF entity and a communication entity.

Background

In the current 5G system, a user plane function (User Plane Function, UPF) connects with a service data adaptation protocol (Service Data Adaptation Protocol, SDAP) layer through a quality of service Flow (QoS Flow) (the SDAP layer is responsible for mapping and demapping of QoS Flow and a Data Radio Bearer (DRB), and optional reflection mapping function (Reflective QoS Flow to DRB mapping)), and a data transmission manner based on QoS Flow is that a Core Network (CN) filters an IP Flow through a 5G QoS Identifier (5 QI) to form a data Flow. According to the definition of QoS flows, one IP Flow is mapped to only one QoS Flow, and one QoS Flow can simultaneously carry multiple IP flows.

After the new definition layer 3 user plane (L3 UP) function, as shown in fig. 1, how to implement communication between the UPF and the L3UP or SDAP is not defined.

In fig. 1, CP is a Control Plane (Control Plane), and is a generic term for related functions of signaling and Control processing. UP is a User Plane (User Plane), which is a generic term for related functions that process data. The Medium Access Control (MAC) Layer located in Layer2 (Layer 2) has both data processing function and control function, i.e., MAC has both CP and UP functions; the CP of the MAC is mainly oriented to the real-time control of the air interface wireless resource, namely the function of the MAC scheduler; and the UP of the MAC is oriented to an air interface, and the receiving and transmitting of air interface data are realized under the instruction of a scheduler. The Radio Resource Control (RRC) located in layer 3 is the control function. The newly introduced UP of layer 3 is the data processing function of layer 3.

Disclosure of Invention

The embodiment of the application provides a data transmission method, a data transmission device, a UPF entity and a communication entity, which can realize communication between UPF and L3UP or SDAP.

In order to solve the above technical problems, an embodiment of the present application provides a data transmission method, applied to a user plane function UPF entity, including:

transmitting IP data packets with a first communication entity through an IP flow connected with the first communication entity;

Wherein there are one or more protocol data unit, PDU, sessions between the UPF entity and the first communication entity, each PDU session comprising one or more IP flows;

the first communication entity is a layer three user plane L3UP functional entity or a service data adaptation protocol SDAP entity.

Optionally, the IP packet includes: the identification corresponding to the IP flow and the identification of the PDU session corresponding to the IP flow.

Optionally, the first communication entity does not belong to any one PDU session.

Optionally, the transmitting the IP data packet with the first communication entity through the IP flow connected with the first communication entity includes:

and according to the QoS transmission requirement corresponding to the IP data packet, the IP data packet is transmitted with the first communication entity through the IP flow connected with the first communication entity.

receiving data volume demand information sent by the first communication entity, wherein the data volume demand information is used for indicating: the granularity of the flow application is PDU conversation or at least one IP flow of PDU conversation;

and according to the data volume demand information, transmitting the IP data packet with the first communication entity through an IP flow connected with the first communication entity.

Optionally, the method further comprises:

transmitting an IP packet with a second communication entity through an IP flow connected to the second communication entity when the connection with the first communication entity is switched to the connection with the second communication entity;

the second communication entity is an L3UP functional entity or an SDAP entity;

the identity of the PDU session corresponding to the IP flow to which the UPF entity is connected to the second communication entity is different from the identity of the PDU session corresponding to the IP flow to which the UPF entity is connected to the first communication entity.

Optionally, the identifier corresponding to the IP flow to which the UPF entity is connected to the second communication entity is the same as the identifier corresponding to the IP flow to which the UPF entity is connected to the first communication entity.

The embodiment of the application also provides a data transmission method, which is applied to a first communication entity, wherein the first communication entity is a layer three-purpose interface (L3 UP) functional entity or a Service Data Adaptation Protocol (SDAP) entity, and comprises the following steps:

transmitting IP data packets with a UPF entity through an IP flow connected with the UPF entity;

wherein there are one or more protocol data unit, PDU, sessions between the UPF entity and the first communication entity, each PDU session comprising one or more IP flows.

Optionally, the IP packet includes: the identification corresponding to the IP flow and the identification of the protocol data unit PDU session corresponding to the IP flow.

Optionally, after the transmission of the IP packet with the UPF entity through the IP flow connected to the user plane function UPF entity, the method further includes:

constructing a target PDU based on the IP data packet;

transmitting the target PDU;

the destination PDU includes data packets of at least one IP flow of at least one PDU session.

Optionally, the constructing the target PDU based on the IP data packet includes:

determining a target PDU based on a first processing of the IP data packet;

wherein the first process comprises at least one of:

updating route information;

compression of IP header and security processing, the security processing comprising: encryption and/or decryption;

determining wireless service quality QoS guarantee of a target PDU;

a retransmission mode of the target PDU is selected.

The embodiment of the application also provides a data transmission device, which is applied to a user plane function UPF entity and comprises:

the first transmission module is used for transmitting the IP data packet with the first communication entity through the IP flow connected with the first communication entity;

The embodiment of the application also provides a UPF entity, which comprises a transceiver and a processor;

the transceiver is used for: transmitting IP data packets with a first communication entity through an IP flow connected with the first communication entity;

The embodiment of the application also provides a UPF entity, which comprises a memory, a processor and a computer program stored in the memory and capable of running on the processor, wherein the processor realizes the steps of the data transmission method when executing the program.

The embodiment of the application also provides a data transmission device, which is applied to a first communication entity, wherein the first communication entity is a layer three-purpose interface L3UP functional entity or a service data adaptation protocol SDAP entity, and includes:

the second transmission module is used for transmitting the IP data packet with the UPF entity through the IP flow connected with the UPF entity;

The embodiment of the application also provides a communication entity, wherein the communication entity is a first communication entity, and the first communication entity is a layer three user plane L3UP functional entity or a service data adaptation protocol SDAP entity, and comprises a transceiver and a processor;

the transceiver is used for: transmitting IP data packets with a UPF entity through an IP flow connected with the UPF entity;

The embodiment of the application further provides a communication entity, wherein the communication entity is a first communication entity, the first communication entity is a layer three user plane L3UP functional entity or a service data adaptation protocol SDAP entity, the communication entity comprises a memory, a processor and a computer program stored on the memory and capable of running on the processor, and the processor realizes the steps of the data transmission method when executing the program.

The embodiments of the present application also provide a readable storage medium having stored thereon a computer program which, when executed by a processor, performs the steps of the method described above.

The beneficial effects of this application are:

according to the scheme, the UPF entity transmits the IP data packet with the L3UP functional entity or the SDAP entity through the IP flow connected with the L3UP functional entity or the SDAP entity; thereby enabling communication between the UPF and the L3UP or SDAP.

Drawings

FIG. 1 is a functional schematic diagram of a newly defined AS layer protocol stack;

FIG. 2 is a schematic flow chart of a data transmission method according to an embodiment of the present application;

FIG. 3 is a schematic diagram of an IP flow connection for UPF and AS layer user plane;

FIG. 4 is a second flow chart of a data transmission method according to the embodiment of the present application;

FIG. 5 is one of the block diagrams of the data transmission device according to the embodiment of the present application;

FIG. 6 illustrates a block diagram of a UPF entity of an embodiment of the present application;

fig. 7 is a second schematic block diagram of the data transmission device according to the embodiment of the present application.

Detailed Description

The following description of the embodiments of the present application will be made clearly and fully with reference to the accompanying drawings, in which it is evident that the embodiments described are some, but not all, of the embodiments of the present application. All other embodiments, which can be made by one of ordinary skill in the art based on the embodiments herein without making any inventive effort, are intended to be within the scope of the present application.

The terms first, second and the like in the description and in the claims, are used for distinguishing between similar objects and not necessarily for describing a particular sequential or chronological order. It is to be understood that the data so used may be interchanged, as appropriate, such that embodiments of the present application may be implemented in sequences other than those illustrated or described herein, and that the objects identified by "first," "second," etc. are generally of a type and not limited to the number of objects, e.g., the first object may be one or more. Furthermore, in the description and claims, "and/or" means at least one of the connected objects, and the character "/", generally means that the associated object is an "or" relationship.

The data transmission method, the device, the UPF entity and the communication entity provided by the embodiment of the application are described in detail through specific embodiments and application scenes thereof with reference to the accompanying drawings.

As shown in fig. 2, at least one embodiment of the present application provides a data transmission method, applied to a UPF entity, including:

step 201, transmitting IP data packets with a first communication entity through an IP flow connected with the first communication entity;

Wherein there are one or more Protocol Data Unit (PDU) sessions (PDU sessions) between the UPF entity and the first communication entity, each PDU Session comprising one or more IP flows (IP flows);

the first communication entity is a layer three user plane (L3 UP) function entity or a Service Data Adaptation Protocol (SDAP) entity.

It should be noted that, the UPF entity is a functional entity at the core network side, the L3UP functional entity and the SDAP entity are both a terminal side and an access network side functional entity, which are user plane functional entities, the UPF entity is connected with the L3UP functional entity or the SDAP entity at the access network side through Ng interface, and the L3UP functional entity or the SDAP entity at the access network side is connected with the L3UP functional entity or the SDAP entity at the terminal side through Uu interface. It should be noted that, the L3UP functional entity or the SDAP entity at the access network side (e.g., the base station) is directly connected to the UPF entity through IP flow. Multiple PDU sessions may be established between the UPF entity and the L3UP functional entity or the SDAP entity simultaneously, each PDU Session containing one or more IP flows, and one L3UP functional entity or the SDAP entity simultaneously serving the IP flows of one or more PDU sessions. For example, in the case where the first communication entity is an L3UP functional entity, the L3UP functional entity does not belong to any one PDU Session, which may serve multiple PDU sessions simultaneously; in the case where the first communication entity is an SDAP entity, the SDAP entity does not belong to any one PDU Session, and can serve multiple PDU sessions simultaneously.

It should be further noted that, when the L3UP functional entity or the SDAP entity is established, PDU Session between the UPF and the UE and the IP flow included therein may be independently established, and then mapped to the corresponding L3UP functional entity or SDAP entity as needed.

It should be noted that, in order to explicitly transmit data for which PDU session and IP flow, optionally, the IP packet includes: an identification corresponding to an IP flow (e.g., an IP flow ID) and an identification of a PDU Session corresponding to the IP flow (e.g., a PDU Session ID).

Optionally, in at least one embodiment of the present application, an optional implementation of step 201:

and according to the quality of service (QoS) transmission requirement corresponding to the IP data packet, the IP data packet is transmitted with the first communication entity through the IP flow connected with the first communication entity.

That is, the Ng interface between the UPF entity and the first communication entity needs to perform QoS formulation, that is, the transport layer of the Ng interface needs to set QoS transmission requirements corresponding to each IP packet for each IP flow of each PDU Session, and the Ng interface provides transmission meeting QoS guarantee requirements for the IP packets.

It should be noted that, the data volume requirement information is used to limit the data volume between the L3UP functional entity or the SDAP entity and the UPF entity, and the L3UP functional entity or the SDAP entity sends the data volume requirement information to the UPF entity, and when the UPF entity transmits the data packet, the UPF entity transmits the data volume requirement information strictly according to the data volume requirement information, so as to realize that the UPF entity sends the IP packet meeting the low-layer data volume requirement to the L3UP functional entity or the SDAP entity. When the L3UP functional entity or the SDAP entity applies for the IP data packet, the IP data packet can be applied by taking PDU Session as a unit, and one or more IP flow applications based on one PDU Session can be also applied; when the UPF distributes IP data packets, the UPF sends the data to an L3UP functional entity or an SDAP entity by taking the IP flow as a unit.

Optionally, the UPF entity performs transmission of an IP packet with the second communication entity through an IP flow connected with the second communication entity in the case of switching from connection with the first communication entity to connection with the second communication entity;

The second communication entity is an L3UP functional entity or an SDAP entity;

In this case, when Ng interface is switched, only PDU Session may be switched, and IP flow may be kept unchanged (i.e. one PDU Session is built first and then IP flow is built as needed) or moved as a whole based on PDU Session (i.e. one PDU Session is built first and then all IP flows are moved). Such as: when the UE switches from the source base station to the target base station, the ID of the PDU Session changes, but all the IP flow IDs that have been established may remain unchanged (equivalent to IP flow not being switched, or being moved in its entirety based on the PDU Session). It should be noted that, this way can reduce the complexity of the handover and realize the fast handover of the IP flow.

Alternatively, in another implementation, both PDU Session and IP flow may be switched, i.e. the identity of the PDU Session and the identity corresponding to the IP flow are changed, i.e. in this case, the PDU Session and the IP flow are re-established.

Optionally, after receiving the IP data packet, the first communication entity needs to construct a target PDU based on the IP data packet, and send the target PDU;

determining a target PDU based on a first processing of the IP data packet;

wherein the first process comprises at least one of:

updating route information;

determining wireless QoS guarantee of a target PDU;

a retransmission mode of the target PDU is selected.

It should be noted that, in the case that the first communication entity is an L3UP functional entity, the target PDU is an L3UP PDU; in the case where the first communication entity is an SDAP entity, the target PDU is an SDAP PDU. That is, after the L3UP functional entity or the SDAP entity processes the IP flow of each PDU Session, an L3UP PDU or an SDAP PDU is constructed, and then the L3UP PDU or the SDAP PDU is sent to the receiving end according to the wireless QoS guarantee and/or retransmission mode requirement of the PDU (for example, the sending end is the L3UP functional entity or the SDAP entity on the terminal side, the receiving end is the L3UP functional entity or the SDAP entity on the access network side, or the sending end is the L3UP functional entity or the SDAP entity on the access network side, the receiving end is the L3UP functional entity or the SDAP entity on the terminal side).

For example, when the first communication entity is a communication entity at the access network side, after receiving the IP data packet sent by the UPF entity, the first communication entity needs to build a target PDU, and then sends the target PDU to the communication entity at the terminal side; when the first communication entity is a communication entity at the terminal side, after receiving the IP data packet sent by the higher layer, the first communication entity needs to build a target PDU, and then sends the target PDU to the communication entity at the access network side. Fig. 3 is a schematic diagram of IP flow connection of the user plane of the UPF and AS layers.

It should be noted that, in the embodiment of the present application, by defining the interaction between the L3UP functional entity or the SDAP entity and its lower layer and upper layer, the forwarding of the data packet in the L3UP functional entity or the SDAP entity is implemented.

Specifically, an L3UP functional entity or an SDAP entity is connected with an upper layer thereof through different IP flows; the L3UP functional entity or the SDAP entity is connected with the lower layer through different QoS flows; the L3UP functional entity or the SDAP entity forms different QoS classifications according to QoS guarantee requirements of air interface receiving and sending of IP data packets borne on different IP flows, and each QoS classification corresponds to one QoS flow.

It should be specifically noted that, in the embodiment of the present application, if an SDAP entity is used, the SDAP entity is completely different from the SDAP entity defined in 5G. The SDAP entity in 5G establishes a SDAP entity (i.e., SDAP protocol functionality) for a PDU Session. The SDAP entity in at least one embodiment of the present application does not belong to any PDU Session alone, whereas multiple PDU sessions require one SDAP entity service, and one terminal only needs to logically establish one SDAP entity (if for calculating the split, one terminal establishes multiple SDAP entities, at this time, one SDAP entity is logically deployed on different computing resources).

In summary, the following beneficial effects can be achieved in at least one embodiment of the present application:

1. communication between the UPF entity and the L3UP functional entity or the SDAP entity is realized;

2. a new switching mechanism of Ng switching is provided;

3. lossless switching can be realized, namely, lossless transmission of data packets in the switching process is realized through unlimited and data retransmission functions controlled according to QoS and low-level scheduling.

As shown in fig. 4, at least one embodiment of the present application further provides a data transmission method, which is applied to a first communication entity, where the first communication entity is an L3UP functional entity or an SDAP entity, and includes:

step 401, transmitting IP data packet with UPF entity through IP flow connected with UPF entity;

Constructing a target PDU based on the IP data packet;

transmitting the target PDU;

determining a target PDU based on a first processing of the IP data packet;

wherein the first process comprises at least one of:

updating route information;

determining wireless service quality QoS guarantee of a target PDU;

a retransmission mode of the target PDU is selected.

Optionally, in at least one embodiment of the present application, further includes:

transmitting data volume requirement information to a UPF entity, wherein the data volume requirement information is used for indicating: the granularity of the traffic application is the PDU session or at least one IP flow of the PDU session.

It should be noted that, in the above embodiments, all descriptions about the first communication entity are applicable to the embodiments of the data transmission method applied to the first communication entity, and the same technical effects can be achieved, which are not repeated herein.

As shown in fig. 5, at least one embodiment of the present application further provides a data transmission apparatus 500, applied to a UPF entity, including:

A first transmission module 501, configured to perform transmission of an IP packet with a first communication entity through an IP flow connected to the first communication entity;

Optionally, the first transmission module 501 is configured to:

Optionally, the first transmission module 501 includes:

a receiving unit, configured to receive data volume requirement information sent by the first communication entity, where the data volume requirement information is used to indicate: the granularity of the flow application is PDU conversation or at least one IP flow of PDU conversation;

and the transmission unit is used for transmitting the IP data packet with the first communication entity through the IP flow connected with the first communication entity according to the data volume demand information.

Optionally, the apparatus further comprises:

a third transmission module, configured to transmit an IP packet with a second communication entity through an IP flow connected to the second communication entity when the connection with the first communication entity is switched to the connection with the second communication entity;

the second communication entity is an L3UP functional entity or an SDAP entity;

It should be noted that, the apparatus provided in at least one embodiment of the present application is an apparatus capable of executing the data transmission method, and all embodiments of the data transmission method are applicable to the apparatus, and achieve the same or similar beneficial effects.

At least one embodiment of the present application further provides a data transmission apparatus, applied to a UPF entity, including a transceiver and a processor;

Optionally, the transceiver is configured to: and according to the QoS transmission requirement corresponding to the IP data packet, the IP data packet is transmitted with the first communication entity through the IP flow connected with the first communication entity.

Optionally, the transceiver is configured to: receiving data volume demand information sent by the first communication entity, wherein the data volume demand information is used for indicating: the granularity of the flow application is PDU conversation or at least one IP flow of PDU conversation;

Optionally, the transceiver is further configured to: transmitting an IP packet with a second communication entity through an IP flow connected to the second communication entity when the connection with the first communication entity is switched to the connection with the second communication entity;

the second communication entity is an L3UP functional entity or an SDAP entity;

As shown in fig. 6, the embodiment of the present invention further provides a UPF entity, including a processor 600, a transceiver 610, a memory 620, and a program stored on the memory 620 and executable on the processor 600; the transceiver 610 is connected to the processor 600 and the memory 620 through a bus interface, where the processor 600 is configured to read a program in the memory, and perform the following procedures:

transmitting, by transceiver 610, IP packets with a first communication entity via an IP flow connected to the first communication entity;

A transceiver 610 for receiving and transmitting data under the control of the processor 600.

Wherein in fig. 6, a bus architecture may comprise any number of interconnected buses and bridges, and in particular one or more processors represented by processor 600 and various circuits of memory represented by memory 620, linked together. The bus architecture may also link together various other circuits such as peripheral devices, voltage regulators, power management circuits, etc., which are well known in the art and, therefore, will not be described further herein. The bus interface provides an interface. The transceiver 610 may be a number of elements, i.e., including a transmitter and a receiver, providing a means for communicating with various other apparatus over transmission media, including wireless channels, wired channels, optical cables, etc.

The processor 600 is responsible for managing the bus architecture and general processing, and the memory 620 may store data used by the processor 600 in performing operations.

Alternatively, the processor 600 may be a CPU (Central processing Unit), ASIC (Application Specific Integrated Circuit ), FPGA (Field-Programmable Gate Array, field programmable Gate array) or CPLD (Complex Programmable Logic Device ), and the processor may also employ a multi-core architecture.

The processor is configured to execute any of the methods provided in the embodiments of the present application by invoking a computer program stored in a memory in accordance with the obtained executable instructions. The processor and the memory may also be physically separate.

Further, the processor 600 implements the following steps when executing the program:

according to the QoS transmission requirements corresponding to the IP packets, the transceiver 610 performs IP packet transmission with the first communication entity through the IP flow connected to the first communication entity.

receiving, by the transceiver 610, data volume requirement information sent by the first communication entity, the data volume requirement information indicating: the granularity of the flow application is PDU conversation or at least one IP flow of PDU conversation;

According to the data volume demand information, the transceiver 610 is used for transmitting IP data packets with the first communication entity through an IP flow connected with the first communication entity.

Further, the processor 600, when executing the program, further performs the following steps:

in the case of switching from connection with the first communication entity to connection with a second communication entity, transmitting an IP packet with the second communication entity through an IP flow connected with the second communication entity by the transceiver 610;

the second communication entity is an L3UP functional entity or an SDAP entity;

At least one embodiment of the present application further provides a UPF entity, including a memory, a processor, and a computer program stored in the memory and capable of running on the processor, where the processor implements each process in the data transmission method embodiment when executing the program, and the process can achieve the same technical effect, so that repetition is avoided, and no further description is given here.

At least one embodiment of the present application further provides a computer readable storage medium, on which a computer program is stored, where the program when executed by a processor implements each process in the data transmission method embodiment applied to a UPF entity as described above, and the same technical effects can be achieved, and for avoiding repetition, a description is omitted herein. Wherein the computer readable storage medium is selected from Read-Only Memory (ROM), random access Memory (Random Access Memory, RAM), magnetic disk or optical disk.

As shown in fig. 7, at least one embodiment of the present application further provides a data transmission apparatus 700, applied to a first communication entity, where the first communication entity is an L3UP functional entity or an SDAP entity, including:

a second transmission module 701, configured to perform transmission of an IP packet with a UPF entity through an IP flow connected to the user plane function UPF entity;

Optionally, after the second transmission module 701 performs transmission of IP packets with the UPF entity through an IP flow connected to the user plane function UPF entity, the method further includes:

the building module is used for building a target PDU based on the IP data packet;

a first transmitting module, configured to transmit the target PDU;

Optionally, the building module is configured to:

determining a target PDU based on a first processing of the IP data packet;

wherein the first process comprises at least one of:

updating route information;

determining wireless service quality QoS guarantee of a target PDU;

a retransmission mode of the target PDU is selected.

Optionally, the apparatus further comprises:

the second sending module is configured to send data volume requirement information to the UPF entity, where the data volume requirement information is used to indicate: the granularity of the traffic application is the PDU session or at least one IP flow of the PDU session.

At least one embodiment of the present application further provides a data transmission device, which is applied to a first communication entity, where the first communication entity is an L3UP functional entity or an SDAP entity, and includes a transceiver and a processor;

Optionally, the processor is configured to:

constructing a target PDU based on the IP data packet;

the transceiver is further configured to: transmitting the target PDU;

Optionally, the processor is configured to:

determining a target PDU based on a first processing of the IP data packet;

wherein the first process comprises at least one of:

updating route information;

Determining wireless service quality QoS guarantee of a target PDU;

a retransmission mode of the target PDU is selected.

Optionally, the transceiver is further configured to:

The embodiment of the present application further provides a communication entity, where the communication entity is a first communication entity, and the first communication entity is an L3UP functional entity or an SDAP entity, and the structure of the communication entity is similar to that of the UPF entity shown in fig. 6, which is not described herein again.

Wherein the processor is configured to read the program in the memory, and execute the following procedure:

transmitting IP data packets with a UPF entity through an IP flow connected with the UPF entity of a user plane function by a transceiver;

Further, the processor, when executing the program, also implements the following steps:

Constructing a target PDU based on the IP data packet;

transmitting the target PDU through a transceiver;

Further, the processor, when executing the program, performs the steps of:

determining a target PDU based on a first processing of the IP data packet;

wherein the first process comprises at least one of:

updating route information;

determining wireless service quality QoS guarantee of a target PDU;

a retransmission mode of the target PDU is selected.

transmitting, by the transceiver, data volume requirement information to the UPF entity, the data volume requirement information indicating: the granularity of the traffic application is the PDU session or at least one IP flow of the PDU session.

At least one embodiment of the present application further provides a communication entity, where the communication entity is a first communication entity, and the first communication entity is an L3UP functional entity or an SDAP entity, including a memory, a processor, and a computer program stored in the memory and capable of running on the processor, where the processor implements each process in the data transmission method embodiment when executing the program, and the process can achieve the same technical effect, so that repetition is avoided, and no further description is given here.

At least one embodiment of the present application further provides a computer readable storage medium, on which a computer program is stored, where the program when executed by a processor implements each process in the data transmission method embodiment applied to the first communication entity as described above, and the same technical effects can be achieved, and for avoiding repetition, a description is omitted herein. Wherein the computer readable storage medium is selected from Read-Only Memory (ROM), random access Memory (Random Access Memory, RAM), magnetic disk or optical disk.

It should be noted that, in this document, the terms "comprises," "comprising," or any other variation thereof, are intended to cover a non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements does not include only those elements but may include other elements not expressly listed or inherent to such process, method, article, or apparatus. Without further limitation, an element defined by the phrase "comprising one … …" does not exclude the presence of other like elements in a process, method, article, or apparatus that comprises the element. Furthermore, it should be noted that the scope of the methods and apparatus in the embodiments of the present application is not limited to performing the functions in the order shown or discussed, but may also include performing the functions in a substantially simultaneous manner or in an opposite order depending on the functions involved, e.g., the described methods may be performed in an order different from that described, and various steps may also be added, omitted, or combined. Additionally, features described with reference to certain examples may be combined in other examples.

From the above description of the embodiments, it will be clear to those skilled in the art that the above-described embodiment method may be implemented by means of software plus a necessary general hardware platform, but of course may also be implemented by means of hardware, but in many cases the former is a preferred embodiment. Based on such understanding, the technical solution of the present application may be embodied essentially or in a part contributing to the prior art in the form of a software product stored in a storage medium (such as ROM/RAM, magnetic disk, optical disk), including several instructions for causing a terminal (which may be a mobile phone, a computer, a server, an air conditioner, or a network device, etc.) to perform the method described in the embodiments of the present application.

The embodiments of the present application have been described above with reference to the accompanying drawings, but the present application is not limited to the above-described embodiments, which are merely illustrative and not restrictive, and many forms may be made by those of ordinary skill in the art without departing from the spirit of the present application and the scope of the claims, which are also within the protection of the present application.

Claims

1. A data transmission method applied to a user plane function UPF entity, comprising:

2. The method according to claim 1, wherein the IP packet includes: the identification corresponding to the IP flow and the identification of the PDU session corresponding to the IP flow.

3. The method of claim 1, wherein the first communication entity does not belong to any one PDU session.

4. The method of claim 1, wherein the transmitting of IP packets with the first communication entity via the IP flow connected to the first communication entity comprises:

5. The method of claim 1, wherein the transmitting of IP packets with the first communication entity via the IP flow connected to the first communication entity comprises:

6. The method as recited in claim 1, further comprising:

the second communication entity is an L3UP functional entity or an SDAP entity;

7. The method of claim 6, wherein the identity of the UPF entity corresponding to the IP flow to which the second communication entity is connected is the same as the identity of the UPF entity corresponding to the IP flow to which the first communication entity is connected.

8. The data transmission method is applied to a first communication entity, wherein the first communication entity is a layer three user plane L3UP functional entity or a service data adaptation protocol SDAP entity, and is characterized by comprising the following steps:

9. The method of claim 8, further comprising, after the transmitting of the IP packet with the UPF entity via the IP flow connected to the user plane function UPF entity:

constructing a target PDU based on the IP data packet;

transmitting the target PDU;

10. The method of claim 9, wherein the constructing the target PDU based on the IP data packet comprises:

determining a target PDU based on a first processing of the IP data packet;

wherein the first process comprises at least one of:

updating route information;

Determining wireless service quality QoS guarantee of a target PDU;

a retransmission mode of the target PDU is selected.

11. A data transmission apparatus for use in a user plane function UPF entity, comprising:

12. A UPF entity comprising a transceiver and a processor;

13. A UPF entity comprising a memory, a processor and a computer program stored on the memory and executable on the processor, the processor implementing the steps of the data transmission method according to any one of claims 1 to 7 when the program is executed.

14. A data transmission device, applied to a first communication entity, where the first communication entity is a layer three user plane L3UP functional entity or a service data adaptation protocol SDAP entity, and is characterized by comprising:

15. A communication entity, the communication entity being a first communication entity, the first communication entity being a layer three purpose plane L3UP functional entity or a service data adaptation protocol, SDAP, entity, characterized by comprising a transceiver and a processor;

16. A communication entity being a first communication entity being a layer three user plane L3UP functional entity or a service data adaptation protocol, SDAP, entity, characterized by comprising a memory, a processor and a computer program stored on the memory and executable on the processor, the processor implementing the steps of the data transmission method according to any of claims 8 to 10 when the program is executed.

17. A readable storage medium, on which a computer program is stored, characterized in that the program, when being executed by a processor, implements the steps of the method according to any one of claims 1 to 10.