Data transmission method, device, communication equipment and readable storage medium

Abstract

This application discloses a data transmission method, apparatus, communication device, and readable storage medium, belonging to the field of communication technology. A specific implementation scheme includes: a first functional entity obtains an IP flow and, based on the QoS characteristics of the IP flow, maps the IP flow to a corresponding access layer AS bearer and transmits it to a second functional entity; wherein the first functional entity is a user plane functional entity in layer 3 of the AS on the transmitting end; the second functional entity is a functional entity in layer 2 of the AS; and the AS bearer is a data packet bearer characterized by QoS.

Description

Technical Field

[0001] The present application belongs to the field of communication technology, and specifically relates to a data transmission method, apparatus, communication equipment and readable storage medium. Background Art

[0002] In existing technologies, data transmission between Layer 3 (L3) and Layer 2 of the Access Stratum (AS) is typically classified based on the service of the data packet and transmitted end-to-end. However, because the service classification does not accurately reflect the transmission requirements of the corresponding data packet, the data packet cannot be transmitted on demand. Summary of the Invention

[0003] The purpose of the embodiments of the present application is to provide a data transmission method, apparatus, communication equipment and readable storage medium to solve the problem that existing data packets cannot be transmitted on demand.

[0004] In order to solve the above technical problems, this application is implemented as follows:

[0005] In a first aspect, an embodiment of the present application provides a data transmission method, applied to a sending end, comprising:

[0006] The first functional entity obtains the IP flow; wherein the first functional entity is a user plane functional entity in layer 3 of the AS of the sending end;

[0007] The first functional entity maps the IP flow to the corresponding AS bearer and transmits it to the second functional entity based on the quality of service QoS characteristics of the IP flow; wherein the second functional entity is a functional entity in layer 2 of the AS; and the AS bearer is a data packet bearer characterized by QoS.

[0008] In a second aspect, an embodiment of the present application provides a data transmission method, applied to a receiving end, comprising:

[0009] The fourth functional entity obtains the data packet; wherein the fourth functional entity is a functional entity in layer 2 of the AS of the receiving end;

[0010] The fourth functional entity transmits the data packet to the fifth functional entity through the AS bearer corresponding to the data packet; wherein the fifth functional entity is the user plane functional entity in layer 3 of the AS of the receiving end; the AS bearer is a data packet bearer characterized by QoS.

[0011] In a third aspect, an embodiment of the present application provides a data transmission device, applied to a transmitting end, comprising: a first functional entity and a second functional entity;

[0012] The first functional entity is configured to: obtain an IP flow, and according to the QoS characteristics of the IP flow, map the IP flow to a corresponding AS bearer and transmit the IP flow to the second functional entity;

[0013] The first functional entity is a user plane functional entity in layer 3 of the AS of the transmitting end; the second functional entity is a functional entity in layer 2 of the AS; and the AS bearer is a data packet bearer characterized by QoS.

[0014] In a fourth aspect, an embodiment of the present application provides a data transmission device, applied to a receiving end, including: a fourth functional entity and a fifth functional entity;

[0015] The fourth functional entity is configured to: obtain a data packet, and transmit the data packet to the fifth functional entity via an AS bearer corresponding to the data packet;

[0016] Among them, the fourth functional entity is a functional entity in layer 2 of the AS of the receiving end; the fifth functional entity is a user plane functional entity in layer 3 of the AS of the receiving end; and the AS bearer is a data packet bearer characterized by QoS.

[0017] In a fifth aspect, an embodiment of the present application provides a communication device, which includes a processor, a memory, and a program or instruction stored on the memory and runnable on the processor, wherein the program or instruction, when executed by the processor, implements the steps of the method described in the first aspect, or the steps of the method described in the second aspect.

[0018] In a sixth aspect, an embodiment of the present application provides a readable storage medium, on which a program or instruction is stored. When the program or instruction is executed by a processor, the steps of the method described in the first aspect or the steps of the method described in the second aspect are implemented.

[0019] In this embodiment of the present application, after obtaining an IP flow, the first functional entity can map the IP flow to a corresponding AS bearer based on the QoS characteristics of the IP flow and transmit it to the second functional entity. The first functional entity is the user plane functional entity in Layer 3 of the AS on the transmitting end, and the second functional entity is the functional entity in Layer 2 of the AS. The AS bearer is a data packet bearer characterized by QoS. As a result, the L3UP functional entity can select the appropriate L2 for data transmission based on the transmission requirements of the data packet, thereby achieving flexible connection between L3 and L2 based on data packet transmission requirements, thereby realizing on-demand data packet transmission. BRIEF DESCRIPTION OF THE DRAWINGS

[0020] Figure 1 This is a flow chart of a data transmission method provided by an embodiment of the present application;

[0021] Figure 2 This is a schematic diagram of the connection between the L3UP functional entity and L2 in an embodiment of the present application;

[0022] Figure 3 This is a flowchart of another data transmission method provided by an embodiment of the present application;

[0023] Figure 4 This is a schematic diagram of end-to-end transmission between the L3UP and MAC layers in an embodiment of the present application;

[0024] Figure 5 This is a structural diagram of a data transmission device provided in an embodiment of the present application;

[0025] Figure 6 is a structural diagram of another data transmission device provided in an embodiment of the present application;

[0026] Figure 7 It is a structural diagram of a communication device provided in an embodiment of the present application. DETAILED DESCRIPTION

[0027] The following will be combined with the drawings in the embodiments of this application to clearly and completely describe the technical solutions in the embodiments of this application. Obviously, the embodiments described are part of the embodiments of this application, not all of them. Based on the embodiments in this application, all other embodiments obtained by ordinary technicians in this field without making creative efforts are within the scope of protection of this application.

[0028] The terms "first," "second," and the like in the specification and claims of this application are used to distinguish similar objects, and are not used to describe a specific order or precedence. It should be understood that the terms used in this manner are interchangeable where appropriate, so that the embodiments of this application can be implemented in an order other than that illustrated or described herein, and that the objects distinguished by "first," "second," and the like are generally of the same type, and do not limit the number of objects; for example, the first object can be one or more. In addition, the term "and / or" in the specification and claims refers to at least one of the connected objects, and the character " / " generally indicates that the objects connected are in an "or" relationship.

[0029] To address the issue of existing data packets being unable to be transmitted on demand, embodiments of the present application introduce a user plane (UP) functional entity, namely the L3UP functional entity, at Layer 3 (L3) of the access layer (AS). This L3UP functional entity has data interleaving and deinterleaving capabilities to support packet-oriented processing. The L3UP functional entity has the ability to transmit data packets (such as IP packets) and can map and transmit them on a per-packet basis. The IP flows within the L3UP functional entity (i.e., data flows carrying IP packets) can be mapped to corresponding AS bearers for transmission to functional entities at Layer 2 (Layer 2). The AS bearer is a data packet carrier characterized by Quality of Service (QoS). Thus, the L3UP functional entity, acting as the data anchor for the AS, can select the appropriate L2 for data transmission based on the data packet transmission requirements (such as QoS parameter requirements), thereby achieving flexible connection between L3 and L2 based on data packet transmission requirements, thereby enabling on-demand data packet transmission.

[0030] The data transmission method, apparatus, communication device, and readable storage medium provided in the embodiments of the present application are described in detail below with reference to specific embodiments and their application scenarios in conjunction with the accompanying drawings.

[0031] See Figure 1 , Figure 1 This is a flow chart of a data transmission method provided by an embodiment of the present application. The method is applied to a sending end, which can be a terminal or a network side device, such as a base station. Figure 1 As shown, the method includes the following steps:

[0032] Step 11: The first functional entity obtains the IP flow.

[0033] In this embodiment, the first functional entity is a user plane functional entity in layer 3 of the AS of the transmitting end, ie, an L3UP functional entity. An IP flow can be expressed as an IP flow or an IP Flow, which can be understood as a data flow carrying data packets such as IP packets.

[0034] In some embodiments, the L3UP functional entity may receive IP flow from the Non Access Stratum (NAS) or the core network, that is, the L3UP of the AS may interact directly with its upper layer through the IP flow.

[0035] Step 12: The first functional entity maps the IP flow to the corresponding AS bearer according to the QoS characteristics of the IP flow and transmits it to the second functional entity.

[0036] In this embodiment, the second functional entity is a functional entity in layer 2 of the sending AS. After the AS L3UP functional entity obtains the IP flow, it can select a suitable AS Bearer according to QoS requirements and send it to the L2 functional entity after L3UP interleaving and QoS control.

[0037] AS Bearer is the bearer connecting the L3UP functional entity and the L2 functional entity, representing the data packet bearer characterized by QoS. When using AS Bearer to implement data transmission between L3 and L2, data packets can be classified based on their QoS requirements rather than based on the service they are used for. This allows data packets with the same QoS requirements (for example, belonging to different services) to be carried on the same AS Bearer for transmission, thus achieving on-demand data packet transmission.

[0038] In the data transmission method of the embodiment of the present application, after a first functional entity obtains an IP flow, it can map the IP flow to a corresponding AS bearer based on the QoS characteristics of the IP flow and transmit it to a second functional entity. The first functional entity is a user plane functional entity in Layer 3 of the AS on the transmitting end, and the second functional entity is a functional entity in Layer 2 of the AS. The AS bearer is a data packet bearer characterized by QoS. Thus, the L3UP functional entity can select an appropriate L2 for data transmission based on the transmission requirements of the data packet, thereby achieving flexible connection between L3 and L2 based on data packet transmission requirements, thereby realizing on-demand data packet transmission and reducing data packet overhead.

[0039] In an embodiment of the present application, the first functional entity, namely the L3UP functional entity, may process the IP flow in the following two ways: 1) mapping the entire IP flow to one or more AS bearers of L2 on an IP flow basis. In this case, the same IP flow can be mapped to different AS bearers at the same time; 2) mapping the IP packets in the IP flow to one or more AS bearers of L2 based on the QoS characteristics of the IP packets on an IP flow basis. In this case, the IP packets in the IP flow can be mapped to different or the same AS bearers at the same time.

[0040] Optionally, mapping the IP flow to a corresponding AS bearer based on the QoS characteristics of the IP flow and transmitting the IP flow to the second functional entity may include: the first functional entity mapping the IP packets in the IP flow to a corresponding AS bearer based on the QoS characteristics of the IP packets in the IP flow and transmitting the IP packets to the second functional entity. This can implement bearer mapping based on a single IP packet, thereby meeting on-demand data packet transmission at a finer granularity.

[0041] In some embodiments, each IP flow to L2 connection is simultaneously mapped to one or more AS bearers according to the QoS characteristics of each data packet (such as IP packet) or IP flow.

[0042] In some embodiments, IP flows carried on an AS bearer may belong to the same protocol data unit (PDU) session or to different PDU sessions.

[0043] In some embodiments, the IP flow belongs to a PDU Session of the terminal. The AS Bearer can simultaneously carry data packets (such as IP packets) on one or more IP flows of a PDU Session, and can also simultaneously carry data packets (such as IP packets) on multiple IP flows of multiple PDU Sessions.

[0044] Optionally, the correspondence between the first functional entity and the second functional entity is one-to-one or one-to-many. For example, if the transmitting end is a terminal, the L2 functional entity corresponding to the L3UP functional entity is located within the same terminal. For another example, if the transmitting end is a base station, the L2 functional entity corresponding to the L3UP functional entity can be located within the same base station or in different base stations, enabling network-side L3UP to connect to the terminal via multiple connections.

[0045] For example, see Figure 2 As shown in the figure, the L3UP functional entity can process the received IP flows, either in units of IP flows or IP packets. The L3UP functional entity can select the appropriate AS Bearer to send to the L2 functional entity for IP flows according to QoS requirements. An IP flow can be mapped to one or more AS Bearers at the same time. Figure 2 As shown, the connection between L3UP and L2 is diverse, including one-to-one connection (such as Figure 2 There are also one-to-many connections (such as Figure 2 On the network side, the L3UP and L2 connections of a terminal can be within the same base station or in different base stations. Figure 2 As shown, Figure 2 The cells in the k , cell n ) represents a transmission channel capable of wireless air interface coverage, including the L2 protocol stack, physical layer channel, and corresponding functions. When the terminal moves and causes the cell to change, link switching is required.

[0046] In the embodiment of the present application, L2 can be a traditional L2 protocol stack, including protocol sublayers such as Service Data Adaptation Protocol (SDAP), Packet Data Convergence Protocol (PDCP), Radio Link Control (RLC) and Medium Access Control (MAC), or it can only include the MAC protocol sublayer (abbreviated as: MAC layer).

[0047] Optionally, the second functional entity mentioned above may be a MAC layer entity in L2.

[0048] In some embodiments, when L2 only includes the MAC layer, L3UP is directly connected to the MAC layer.

[0049] In some embodiments, when L2 includes protocol sublayers other than the MAC layer, L3UP can be connected to the SDAP layer, and transparent mode (TM) can be defined separately at the SDAP layer, PDCP layer, RLC layer and other protocol sublayers. That is, when a data packet passes through SDAP / PDCP / RLC, each protocol sublayer does not process the data packet in any way and directly sends it to its lower layer (Lower Layer) or its upper layer (Upper Layer), which is logically equivalent to a direct connection between L3UP and the MAC layer.

[0050] Optionally, the above-mentioned mapping the IP flow to the corresponding AS bearer and transmitting it to the second functional entity according to the QoS characteristics of the IP flow may include: the first functional entity maps the IP flow to the corresponding AS bearer and transmits it to the third functional entity according to the QoS characteristics of the IP flow, and the third functional entity transmits the IP flow to the MAC layer entity; wherein the third functional entity is one of the functional entities in layer 2 other than the MAC layer entity, such as the SDAP layer entity.

[0051] Furthermore, after the MAC layer entity receives the MAC service data unit (SDU) on the AS bearer, it can first construct a corresponding MAC protocol data unit (PDU) based on the QoS parameters of the AS bearer; the MAC PDU includes the identifier of the AS bearer, so that the receiving end can determine the corresponding AS bearer based on the identifier; then, the MAC PDU is sent to the MAC layer entity at the receiving end to achieve low-latency and high-determinism on-demand transmission of data packets on the air interface.

[0052] See Figure 3 , Figure 3 This is a flowchart of a data transmission method provided by an embodiment of the present application. The method is applied to the receiving end, which can be a terminal or a network side device, such as a base station. For example, when the sending end is a terminal, the receiving end is a base station; or when the sending end is a base station, the receiving end is a terminal. Figure 3 As shown, the method includes the following steps:

[0053] Step 31: The fourth functional entity obtains the data packet.

[0054] In this embodiment, the fourth functional entity is a functional entity in layer 2 of the AS of the receiving end.

[0055] Step 32: The fourth functional entity transmits the data packet to the fifth functional entity through the AS bearer corresponding to the data packet.

[0056] In this embodiment, the fifth functional entity is the user plane functional entity in Layer 3 of the receiving AS, namely the L3UP functional entity. AS bearers carry data packets with QoS features. After receiving data packets from Layer 2 via the AS Bearer, the AS L3UP functional entity deinterleaves the packets to determine the IP flow corresponding to the packets. The packets are then sorted according to the IP flow and delivered to upper layers in order.

[0057] In the data transmission method of the embodiment of the present application, after the fourth functional entity obtains a data packet, it can transmit the data packet to the fifth functional entity via the AS bearer corresponding to the data packet. The fourth functional entity is a functional entity in Layer 2 of the receiving AS, and the fifth functional entity is a user plane functional entity in Layer 3 of the receiving AS. The AS bearer is a data packet bearer characterized by QoS. Thus, the L3UP functional entity can receive data from L2 according to the data packet transmission requirements, thereby achieving flexible connection between L3 and L2 based on data packet transmission requirements, thereby achieving on-demand data packet transmission and reducing data packet overhead.

[0058] Optionally, after receiving the data packet, the L3UP functional entity of the AS can parse the data packet to obtain the IP flow corresponding to each IP packet in the data packet; then, according to the order of each IP packet on the IP flow, each IP packet can be mapped to the corresponding IP flow and transmitted to the upper layer.

[0059] Optionally, the fourth functional entity may be a MAC layer entity. In this case, the MAC layer entity may receive a MAC PDU from a transmitting MAC layer entity; the MAC PDU includes an AS bearer identifier; then, the MAC PDU is parsed to obtain a MAC SDU and the corresponding AS bearer; and the MAC SDU is transmitted to the L3UP functional entity via the AS bearer corresponding to the MAC SDU. In this way, end-to-end L3UP and MAC layer data transmission enables low-latency, highly deterministic, on-demand transmission of data packets over the air interface.

[0060] The following combination Figure 4 The end-to-end transmission of L3UP and MAC layer in the example of this application is described.

[0061] In the example of the present application, the transmitting end may be a terminal or a base station NB, and correspondingly, the receiving end may be a base station NB or a terminal.

[0062] For the sending end, such as Figure 4 As shown, an IP flow can send corresponding IP packets directly from the NAS or core network to the AS or base station. That is, the AS's L3UP interacts directly with its upper layer through the IP flow. First, the L3UP functional entity on the sending end can use the interleaving function to map the IP packets on the IP flow to different AS Bearers and send them to the MAC layer entity. Second, after receiving the MAC SDU from the AS Bearer, the MAC layer entity on the sending end can determine the scheduling strategy for the MAC SDU based on the QoS guarantee indicators of the AS Bearer, including resource allocation method, MAC PDU construction method (for example, whether to split it into multiple segments for transmission, whether to construct a MAC PDU for high- and low-priority radio bearer RB packets, etc.), Hybrid Automatic Repeat reQuest (HARQ) mode or HARQ process mode and number of HARQ processes, physical channel parameters such as bit rate, coding, and modulation scheme, etc., and construct a MAC PDU. The constructed MAC PDU carries the AS Bearer ID. The MAC layer entity on the sending end then sends the constructed MAC PDU to the MAC layer entity on the receiving end via the Uu interface.

[0063] For the receiving end, such as Figure 4As shown in the figure, first, after the MAC layer entity at the receiving end receives the MAC PDU, it can parse the MAC PDU to obtain the MAC SDU and its corresponding AS Bearer, and deliver the parsed MAC SDU to the L3UP functional entity through its corresponding AS Bearer; then, after the L3UP functional entity at the receiving end receives the data packet through different AS Bearers, it parses the L3UP PDU to obtain the IP flow corresponding to each IP packet, and sorts the IP packets on each IP Flow and delivers them to the upper layer in order.

[0064] It should be noted that the data transmission method provided in the embodiments of the present application can be executed by a data transmission device or a control module in the data transmission device for executing the data transmission method. In the embodiments of the present application, the data transmission device provided in the embodiments of the present application is described by taking the data transmission method executed by the data transmission device as an example.

[0065] See Figure 5 , Figure 5 This is a structural diagram of a data transmission device provided by an embodiment of the present application. The device is applied to a sending end, which can be a terminal or a network side device, such as a base station. Figure 5 As shown, the data transmission device 50 includes: a first functional entity 51 and a second functional entity 52.

[0066] The first functional entity 51 is configured to obtain an IP flow, map the IP flow to a corresponding AS bearer based on the QoS characteristics of the IP flow, and transmit the IP flow to the second functional entity 52. ​​The first functional entity 51 is a user plane functional entity in layer 3 of the AS on the transmitting end. The second functional entity 52 is a functional entity in layer 2 of the AS. An AS bearer is a data packet bearer characterized by QoS.

[0067] Optionally, the first functional entity 51 is further configured to: map the IP packets in the IP flow to corresponding AS bearers according to QoS characteristics of the IP packets in the IP flow, and transmit the IP packets to the second functional entity.

[0068] Optionally, the second functional entity 52 is a MAC layer entity.

[0069] Optionally, the first functional entity 51 is also used to: map the IP flow to the corresponding AS bearer and transmit it to the third functional entity according to the QoS characteristics of the IP flow, and the third functional entity transmits the IP flow to the MAC layer entity; wherein the third functional entity is one of the functional entities in the layer 2 except the MAC layer entity.

[0070] Optionally, the MAC layer entity is used to: after receiving the MAC SDU on the AS bearer, construct a corresponding MAC PDU according to the QoS parameters of the AS bearer, and send the MAC PDU to the MAC layer entity at the receiving end; wherein the MAC PDU includes the identifier of the AS bearer.

[0071] Optionally, the IP flows carried on an AS bearer belong to the same PDU session, or the IP flows carried on an AS bearer belong to different PDU sessions;

[0072] And / or, the correspondence between the first functional entity 51 and the second functional entity 52 is one-to-one or one-to-many.

[0073] The data transmission device 50 of the embodiment of the present application can realize the above Figure 1 The various processes of the method embodiment shown can achieve the same technical effect, and to avoid repetition, they will not be described again here.

[0074] See Figure 6 , Figure 6 This is a structural diagram of a data transmission device provided by an embodiment of the present application. The device is applied to a receiving end, which can be a terminal or a network side device, such as a base station. Figure 6 As shown, the data transmission device 60 includes: a fourth functional entity 61 and a fifth functional entity 62.

[0075] The fourth functional entity 61 is configured to obtain a data packet and transmit it to the fifth functional entity 62 via the AS bearer corresponding to the data packet. The fourth functional entity 61 is a layer 2 functional entity in the receiving AS. The fifth functional entity 62 is a layer 3 user plane functional entity in the receiving AS. The AS bearer is a data packet bearer characterized by QoS.

[0076] Optionally, the fifth functional entity 62 is used to: after receiving the data packet, parse the data packet, obtain the IP stream corresponding to each IP packet in the data packet, and map each IP packet to the corresponding IP stream according to the order of each IP packet on the IP stream and transmit it to the upper layer.

[0077] Optionally, the fourth functional entity 61 is a MAC layer entity; the MAC layer entity is used to: receive a MAC PDU from the MAC layer entity of the sending end, parse the MAC PDU, obtain a MAC SDU and a corresponding AS bearer, and transmit the MAC SDU to the fifth functional entity 62 through the AS bearer corresponding to the MAC SDU; the MAC PDU includes an identifier of the AS bearer.

[0078] The data transmission device 60 of the embodiment of the present application can realize the above Figure 1 The various processes of the method embodiment shown can achieve the same technical effect, and to avoid repetition, they will not be described again here.

[0079] Optional, such as Figure 7 As shown, the embodiment of the present application further provides a communication device 70, including a processor 71, a memory 72, and a program or instruction stored in the memory 72 and executable on the processor 71. For example, when the communication device 70 is a transmitting end, the program or instruction is executed by the processor 71 to implement the various processes of the above-mentioned data transmission method embodiment and achieve the same technical effect. When the communication device 70 is a receiving end, the program or instruction is executed by the processor 71 to implement the various processes of the above-mentioned data transmission method embodiment and achieve the same technical effect. To avoid repetition, it will not be repeated here.

[0080] The embodiment of the present application also provides a readable storage medium on which a program or instruction is stored, which can achieve the above-mentioned Figure 1 or Figure 3 The various processes of the method embodiment shown can achieve the same technical effect, and to avoid repetition, they will not be described here.

[0081] Computer-readable media includes both permanent and non-permanent, removable and non-removable media, and can be implemented using any method or technology for information storage. Information can be computer-readable instructions, data structures, program modules, or other data. Examples of computer storage media include, but are not limited to, phase-change RAM (PRAM), static random access memory (SRAM), dynamic random access memory (DRAM), other types of random access memory (RAM), read-only memory (ROM), electrically erasable programmable read-only memory (EEPROM), flash memory or other memory technologies, compact disc read-only memory (CD-ROM), digital versatile disc (DVD) or other optical storage, magnetic cassettes, magnetic tape, magnetic disk storage or other magnetic storage devices, or any other non-transmission media that can be used to store information that can be accessed by a computing device. As defined herein, computer-readable media does not include transitory computer-readable media, such as modulated data signals and carrier waves.

[0082] It should be noted that, in this document, the terms "comprises," "includes," or any other variations thereof are intended to encompass non-exclusive inclusion, such that a process, method, article, or apparatus comprising a series of elements includes not only those elements but also other elements not explicitly listed, or elements inherent to such process, method, article, or apparatus. In the absence of further limitations, an element defined by the phrase "comprising a ..." does not exclude the presence of other identical elements in the process, method, article, or apparatus comprising the element.

[0083] The serial numbers of the above-mentioned embodiments of the present application are for description only and do not represent the advantages or disadvantages of the embodiments.

[0084] Through the description of the above implementation methods, those skilled in the art can clearly understand that the above-mentioned embodiment methods can be implemented by means of software plus the necessary general hardware platform, and of course can also be implemented by hardware, but in many cases the former is a better implementation method. Based on this understanding, the technical solution of the present application, or the part that contributes to the prior art, can be embodied in the form of a software product, which is stored in a storage medium (such as ROM / RAM, magnetic disk, optical disk), and includes a number of instructions for enabling a service classification device (which can be a mobile phone, computer, server, air conditioner, or network device, etc.) to execute the methods described in each embodiment of the present application.

[0085] The above is only a preferred embodiment of the present application. It should be pointed out that for ordinary technicians in this technical field, several improvements and modifications can be made without departing from the principles of the present application. These improvements and modifications should also be regarded as the scope of protection of the present application.

Claims

1. A data transmission method, applied to a sending end, characterized in that: include: The first functional entity obtains the IP flow; wherein the first functional entity is a user plane functional entity in layer 3 of the access layer AS of the sending end; The first functional entity maps the IP flow to the corresponding AS bearer and transmits it to the second functional entity based on the quality of service QoS characteristics of the IP flow; wherein the second functional entity is the media access control MAC layer entity in layer 2 of the AS; the AS bearer is a data packet bearer characterized by QoS; the correspondence between the first functional entity and the second functional entity is one-to-one or one-to-many.

2. The method according to claim 1, characterized in that The step of mapping the IP flow to a corresponding AS bearer and transmitting the IP flow to the second functional entity according to the QoS characteristics of the IP flow includes: The first functional entity maps the IP packets in the IP flow to the corresponding AS bearer according to the QoS characteristics of the IP packets in the IP flow and transmits them to the second functional entity.

3. The method according to claim 1, characterized in that The step of mapping the IP flow to a corresponding AS bearer and transmitting the IP flow to the second functional entity according to the QoS characteristics of the IP flow includes: The first functional entity maps the IP flow to the corresponding AS bearer and transmits it to the third functional entity based on the QoS characteristics of the IP flow, and the third functional entity transparently transmits the IP flow to the MAC layer entity; wherein, the third functional entity is one of the functional entities in the layer 2 except the MAC layer entity.

4. The method according to claim 1, wherein The method further comprises: After receiving the MAC service data unit SDU on the AS bearer, the MAC layer entity constructs a corresponding MAC protocol data unit PDU according to the QoS parameters of the AS bearer; wherein the MAC PDU includes the identifier of the AS bearer; The MAC layer entity sends the MAC PDU to a MAC layer entity at a receiving end.

5. The method according to any one of claims 1 to 4, characterized in that The IP flows carried on an AS bearer belong to the same PDU session, or the IP flows carried on an AS bearer belong to different PDU sessions.

6. A data transmission method, applied to a receiving end, characterized in that: include: The fourth functional entity obtains the data packet; wherein the fourth functional entity is a MAC layer entity in layer 2 of the AS of the receiving end; The fourth functional entity transmits the data packet to the fifth functional entity through the AS bearer corresponding to the data packet; wherein the fifth functional entity is the user plane functional entity in layer 3 of the AS of the receiving end; the AS bearer is a data packet bearer characterized by QoS; the correspondence between the fifth functional entity and the fourth functional entity is one-to-one or one-to-many.

7. The method according to claim 6, characterized in that The method further comprises: After receiving the data packet, the fifth functional entity parses the data packet to obtain the IP flow corresponding to each IP packet in the data packet; The fifth functional entity maps each IP packet to the corresponding IP flow according to the order of each IP packet on the IP flow and transmits it to the upper layer.

8. The method according to claim 6, characterized in that The obtaining of the data packet comprises: The MAC layer entity receives a MAC PDU from a MAC layer entity of a transmitting end; wherein the MAC PDU includes an identifier of the AS bearer; The transmitting the data packet to the fifth functional entity through the AS bearer corresponding to the data packet includes: The MAC layer entity parses the MAC PDU to obtain a MAC SDU and a corresponding AS bearer; The MAC layer entity transmits the MAC SDU to the fifth functional entity through the AS bearer corresponding to the MAC SDU.

9. A data transmission device, applied to a sending end, characterized in that: include: a first functional entity and a second functional entity; The first functional entity is configured to: obtain an IP flow, and according to the QoS characteristics of the IP flow, map the IP flow to a corresponding AS bearer and transmit the IP flow to the second functional entity; Among them, the first functional entity is the user plane functional entity in layer 3 of the AS of the sending end; the second functional entity is the MAC layer entity in layer 2 of the AS; the AS bearer is a data packet bearer characterized by QoS; the correspondence between the first functional entity and the second functional entity is one-to-one or one-to-many.

10. The device according to claim 9, characterized in that The first functional entity is further configured to: map the IP packets in the IP flow to corresponding AS bearers according to QoS characteristics of the IP packets in the IP flow, and transmit the IP packets to the second functional entity.

11. The device according to claim 9, characterized in that The first functional entity is also used to: map the IP flow to the corresponding AS bearer and transmit it to the third functional entity according to the QoS characteristics of the IP flow, and the third functional entity transmits the IP flow to the MAC layer entity; wherein the third functional entity is one of the functional entities in the layer 2 except the MAC layer entity.

12. The device according to claim 9, characterized in that The MAC layer entity is used to: after receiving the MAC SDU on the AS bearer, build a corresponding MAC PDU according to the QoS parameters of the AS bearer, and send the MAC PDU to the MAC layer entity of the receiving end; wherein the MAC PDU includes the identifier of the AS bearer.

13. The device according to any one of claims 9 to 12, characterized in that The IP flows carried on an AS bearer belong to the same PDU session, or the IP flows carried on an AS bearer belong to different PDU sessions.

14. A data transmission device, applied to a receiving end, characterized in that: include: a fourth functional entity and a fifth functional entity; The fourth functional entity is configured to: obtain a data packet, and transmit the data packet to the fifth functional entity via an AS bearer corresponding to the data packet; Among them, the fourth functional entity is the MAC layer entity in layer 2 of the AS of the receiving end; the fifth functional entity is the user plane functional entity in layer 3 of the AS of the receiving end; the AS bearer is a data packet bearer characterized by QoS; the correspondence between the fifth functional entity and the fourth functional entity is one-to-one or one-to-many.

15. The device according to claim 14, characterized in that The fifth functional entity is used to: after receiving the data packet, parse the data packet, obtain the IP stream corresponding to each IP packet in the data packet, and map each IP packet to the corresponding IP stream according to the order of each IP packet on the IP stream and transmit it to the upper layer.

16. The device according to claim 14, characterized in that The MAC layer entity is used to: receive a MAC PDU from the MAC layer entity of the sending end, parse the MAC PDU, obtain a MAC SDU and a corresponding AS bearer, and transmit the MAC SDU to the fifth functional entity through the AS bearer corresponding to the MAC SDU; wherein the MAC PDU includes an identifier of the AS bearer.

17. A communication device, characterized in that: The method comprises a processor, a memory, and a program or instruction stored in the memory and executable on the processor, wherein the program or instruction, when executed by the processor, implements the steps of the data transmission method according to any one of claims 1 to 5, or the steps of the data transmission method according to any one of claims 6 to 8.

18. A readable storage medium, characterized in that: The readable storage medium stores a program or instruction, and when the program or instruction is executed by the processor, the steps of the data transmission method according to any one of claims 1 to 6, or the steps of the data transmission method according to any one of claims 6 to 8 are implemented.

Images