CN107979853B

CN107979853B - Data transmission method and device, user equipment and base station

Info

Publication number: CN107979853B
Application number: CN201610941970.0A
Authority: CN
Inventors: 谢峰; 王丽萍; 王明月
Original assignee: ZTE Corp
Current assignee: ZTE Corp
Priority date: 2016-10-25
Filing date: 2016-10-25
Publication date: 2022-08-02
Anticipated expiration: 2036-10-25
Also published as: CN107979853A; WO2018077043A1

Abstract

The invention provides a data transmission method and device, user equipment and a base station. Wherein, the method comprises the following steps: a base station sends configuration information of a wireless data bearer DRB to user equipment, wherein the configuration information comprises a Radio Network Temporary Identifier (RNTI), and the RNTI is specially used for the DRB; and the base station receives and transmits user interface air interface data of the user equipment, and the user interface air interface data is borne on the DRB. The invention solves the technical problem of larger delay of transmitting the user plane data in the related technology.

Description

Data transmission method and device, user equipment and base station

Technical Field

The present invention relates to the field of communications, and in particular, to a data transmission method and apparatus, a user equipment, and a base station.

Background

With the continuous development of wireless mobile communication technology, higher and more diversified requirements are put on a new generation of wireless communication technology, such as enhanced mobile bandwidth, large-scale mass connection, low latency and high reliability, and the like. The requirements of the new generation technology on low delay are as follows: on the premise of high reliability guarantee, millisecond-level end-to-end time delay is provided for a user, namely the time delay from a base station PDCP (Packet Data Convergence Protocol) to a terminal PDCP is 1 ms. For example, in application scenarios such as virtual reality, remote industrial control, and automatic driving, the requirement for time delay is very strict.

Fig. 1 shows a user plane Protocol stack of an LTE system, where at a base station eNB, a higher layer of a user plane may be divided into three sublayers, namely, a PDCP layer (Packet Data Convergence Protocol), an RLC layer (Radio Link Control), and an MAC layer (Medium Access Control). The PDCP layer provides a service of header compression/decompression, ciphering/deciphering. The RLC layer provides services of segmentation, concatenation, reassembly of RLC SDUs (Service Data units), reordering, and duplicate packet detection, and the MAC layer provides mapping from a logical channel to a transport channel, multiplexing/demultiplexing MAC SDUs of one or more logical channels, scheduling information reporting, error detection through HARQ (Hybrid Automatic Repeat Request), processing of logical channel priority of one UE, priority processing of each UE through dynamic scheduling, transmission mode selection, and Padding (i.e., Padding) added services. The format of the MAC PDU of the MAC layer is shown in fig. 2: a MAC PDU (protocol Data unit) consists of a MAC header and a payload MAC payload. The MAC payload consists of several MAC SDUs, MAC CEs and Padding. The MAC header is composed of one or more MAC subheaders (i.e., MAC subheaders), each subheader corresponding to one MAC SDU or multiple MAC SDUs, or one MAC CE, or one padding.

The data transmission processing steps of the user plane are more, the complexity is higher, the time consumption is longer, and the requirement of low-delay service on the time delay is difficult to meet.

For the technical problem of large delay in transmitting user plane data in the related art, no effective solution is provided at present.

Disclosure of Invention

The embodiment of the invention provides a data transmission method and device, user equipment and a base station, which are used for at least solving the technical problem of larger delay of transmitting user plane data in the related technology.

According to an aspect of an embodiment of the present invention, there is provided a data transmission method, including: a base station sends configuration information of a wireless data bearer (DRB) to user equipment, wherein the configuration information comprises a Radio Network Temporary Identifier (RNTI), and the RNTI is specially used for the DRB; and the base station receives and transmits user interface air interface data of the user equipment, wherein the user interface air interface data is borne on the DRB.

Optionally, a data transmission format of the user plane air interface data in a medium access control MAC layer of the base station is a transparent protocol data unit MAC PDU, where the transparent MAC PDU includes a service data unit MAC SDU for carrying the user plane air interface data.

Optionally, a transport TB block used for transporting user plane air interface data in a physical PHY layer of the base station includes padding bits.

Optionally, the base station side logical channel corresponding to the DRB has a one-to-one correspondence relationship with a first transport channel through which user plane air interface data passes, where the first transport channel is a channel between an MAC layer and a PHY layer of the base station.

Optionally, a transmission mode adopted by the user plane air interface data in the radio link control RLC layer of the base station is a transparent transmission TM mode.

According to an aspect of the embodiments of the present invention, there is also provided a data transmission method, including: the method comprises the steps that user equipment receives configuration information of a radio data bearer (DRB) sent by a base station, wherein the configuration information comprises a Radio Network Temporary Identifier (RNTI), and the RNTI is specially used for the DRB; and the user equipment receives and transmits user plane air interface data of the base station, wherein the user plane air interface data is borne on the DRB.

Optionally, a data transmission format of the user plane air interface data in a medium access control MAC layer of the user equipment is a transparent protocol data unit MAC PDU, where the transparent MAC PDU includes a service data unit MAC SDU for carrying the user plane air interface data.

Optionally, a transport TB block used for transporting user plane air interface data in a physical PHY layer of the user equipment includes padding bits.

Optionally, the user equipment side logical channel corresponding to the DRB has a one-to-one correspondence relationship with a second transport channel through which the user plane air interface data passes, where the second transport channel is a channel between an MAC layer and a PHY layer of the user equipment.

Optionally, a transmission mode of the user plane air interface data adopted in the radio link control RLC layer of the user equipment is a transparent transmission TM mode.

According to another aspect of the embodiments of the present invention, there is provided an apparatus for transmitting data, which is applied to a base station, the apparatus including: a sending unit, configured to send configuration information of a radio data bearer DRB to a user equipment, where the configuration information includes a radio network temporary identifier RNTI, and the RNTI is dedicated to the DRB; and the first transmission unit is used for receiving and transmitting user interface air interface data of the user equipment, wherein the user interface air interface data is borne on the DRB.

According to another aspect of the embodiments of the present invention, there is also provided a base station, including any one of the above-mentioned data transmission apparatuses.

According to another aspect of the embodiments of the present invention, there is also provided a data transmission apparatus, including: a receiving unit, configured to receive configuration information of a DRB carried by radio data sent by a base station, where the configuration information includes a radio network temporary identifier RNTI and the RNTI is dedicated to the DRB; and a second transmission unit, configured to receive and transmit user plane air interface data of the base station, where the user plane air interface data is borne on the DRB.

According to another aspect of the embodiment of the present invention, there is also provided a user equipment, which includes any one of the above-mentioned data transmission apparatuses.

According to another aspect of the embodiments of the present invention, there is provided a base station, including: a first processor; a first memory for storing first processor-executable instructions; first transmission means for performing information transceiving communication according to control of the first processor; wherein the first processor is configured to perform the following operations: sending configuration information of a radio data bearer (DRB) to user equipment, wherein the configuration information comprises a Radio Network Temporary Identifier (RNTI), and the RNTI is specially used for the DRB; and receiving and transmitting user interface air interface data of the user equipment, wherein the user interface air interface data is borne on the DRB.

According to another aspect of the embodiments of the present invention, there is provided a user equipment, including: a second processor; a second memory for storing second processor-executable instructions; second transmission means for performing information transceiving communication according to control of the second processor; wherein the second processor is configured to perform the following operations: receiving configuration information of a radio data bearer (DRB) sent by a base station, wherein the configuration information comprises a Radio Network Temporary Identifier (RNTI) which is specially used for the DRB; and receiving and transmitting user interface air interface data of the base station, wherein the user interface air interface data is borne on the DRB.

According to another embodiment of the present invention, there is provided a storage medium that may be configured to store program code for performing the steps of: sending configuration information of a radio data bearer (DRB) to user equipment, wherein the configuration information comprises a Radio Network Temporary Identifier (RNTI), and the RNTI is specially used for the DRB; and receiving and transmitting user interface air interface data of the user equipment, wherein the user interface air interface data is borne on the DRB.

According to another embodiment of the present invention, there is also provided a storage medium that may be configured to store program code for performing the steps of: receiving configuration information of a radio data bearer (DRB) sent by a base station, wherein the configuration information comprises a Radio Network Temporary Identifier (RNTI) which is specially used for the DRB; and receiving and transmitting user interface air interface data of the base station, wherein the user interface air interface data is borne on the DRB.

Through the embodiment, the base station sends the configuration information of the wireless data bearer DRB to the user equipment, wherein the configuration information comprises the radio network temporary identifier RNTI which is specially used for the DRB; the base station receives and transmits user interface air interface data of the user equipment, wherein the user interface air interface data is borne on the DRB, so that the technical problem of large delay of user interface data transmission in the related technology is solved, and the technical effect of reducing the transmission delay of the user interface data is realized.

Drawings

The accompanying drawings, which are included to provide a further understanding of the invention and are incorporated in and constitute a part of this application, illustrate embodiment(s) of the invention and together with the description serve to explain the invention without limiting the invention. In the drawings:

fig. 1 is a schematic diagram of an alternative LTE system user plane protocol stack in the related art;

fig. 2 is a schematic diagram of an alternative protocol data unit in the related art;

FIG. 3 is a schematic diagram of an alternative computer terminal according to an embodiment of the present invention;

FIG. 4 is a flow chart of an alternative method of data transmission according to an embodiment of the present invention;

FIG. 5 is a flow chart of an alternative method of data transmission according to an embodiment of the present invention;

FIG. 6 is a schematic diagram of a user plane protocol stack layer structure according to an embodiment of the invention;

FIG. 7 is a schematic diagram of an alternative business model according to an embodiment of the present invention;

fig. 8 is a flow chart of an alternative downstream data transmission according to an embodiment of the present invention;

fig. 9 is a flow chart of an alternative uplink data transmission according to an embodiment of the present invention;

fig. 10 is a flow diagram of an alternative set up dedicated bearer according to an embodiment of the present invention;

fig. 11 is a flow diagram of an alternative set up dedicated bearer according to an embodiment of the present invention;

fig. 12 is a flow diagram of an alternative set up dedicated bearer according to an embodiment of the present invention;

FIG. 13 is a schematic diagram of an alternative business model according to an embodiment of the present invention;

FIG. 14 is a schematic diagram of an alternative business model according to an embodiment of the present invention;

FIG. 15 is a schematic diagram of an alternative business model according to an embodiment of the present invention;

fig. 16 is a flow diagram of an alternative set up dedicated bearer according to an embodiment of the present invention;

fig. 17 is a flow diagram of an alternative set up dedicated bearer according to an embodiment of the present invention;

FIG. 18 is a schematic diagram of an alternative data transmission arrangement according to an embodiment of the present invention;

FIG. 19 is a schematic diagram of an alternative data transmission arrangement according to an embodiment of the present invention;

FIG. 20 is a schematic diagram of a user equipment according to an embodiment of the present invention;

fig. 21 is a schematic diagram of a base station according to an embodiment of the present invention.

Detailed Description

The invention will be described in detail hereinafter with reference to the accompanying drawings in conjunction with embodiments. It should be noted that the embodiments and features of the embodiments in the present application may be combined with each other without conflict.

It should be noted that the terms "first," "second," and the like in the description and claims of the present invention and in the drawings described above are used for distinguishing between similar elements and not necessarily for describing a particular sequential or chronological order.

Example 1

The method provided in the first embodiment of the present application may be executed in a mobile terminal (e.g., a user equipment, a small base station), a computer terminal (e.g., a control component on the user equipment or a control component of the base station), or a similar computing device. Taking the example of being run on a computer terminal, as shown in fig. 3, the computer terminal may include one or more (only one shown) processors 301 (the processors 301 may include, but are not limited to, a processing device such as a microprocessor MCU or a programmable logic device FPGA), a memory 303 for storing data, and a transmission device 305 for communication functions. It will be understood by those skilled in the art that the structure shown in fig. 3 is only an illustration and is not intended to limit the structure of the electronic device.

The memory 303 may be used to store software programs and modules of application software, such as program instructions/modules corresponding to the control method of the device in the embodiment of the present invention, and the processor 301 executes various functional applications and data processing by running the software programs and modules stored in the memory 303, so as to implement the method described above. The memory may include high speed random access memory, and may also include non-volatile memory, such as one or more magnetic storage devices, flash memory, or other non-volatile solid-state memory. In some examples, the memory may further include memory located remotely from the processor, and these remote memories may be connected to the computer terminal through a network. Examples of such networks include, but are not limited to, the internet, intranets, local area networks, mobile communication networks, and combinations thereof.

The transmission device is used for receiving or transmitting data via a network. Specific examples of the network described above may include a wireless network provided by a communication provider of the computer terminal. In one example, the transmission device includes a Network adapter (NIC) that can be connected to other Network devices through a base station to communicate with the internet. In one example, the transmission device may be a Radio Frequency (RF) module, which is used for communicating with the internet in a wireless manner.

In accordance with an embodiment of the present invention, there is provided a method embodiment of a method for transmitting data, it being noted that the steps illustrated in the flowchart of the figure may be performed in a computer system such as a set of computer-executable instructions, and that while a logical order is illustrated in the flowchart, in some cases the steps illustrated or described may be performed in an order different than here.

Fig. 4 is a flow chart of an alternative data transmission method according to an embodiment of the present invention, as shown in fig. 4, the method includes the following steps:

step S401, a base station sends configuration information of a wireless data bearer DRB to user equipment, wherein the configuration information comprises a radio network temporary identifier RNTI which is specially used for the DRB.

After receiving the configuration information, the user equipment UE (also called a terminal) may determine a DRB corresponding to the configuration information through the RNTI, where the DRB is dedicated for transmitting air interface data of the user plane, or is dedicated for transmitting air interface data of a certain type of user plane.

Step S402, the base station receives and transmits the user interface air interface data of the user equipment, and the user interface air interface data is loaded on the DRB.

Because the user equipment can determine the corresponding DRB and the user plane air interface data corresponding to the DRB through the RNTI, that is, the user equipment can determine what data needs to be sent or received without excessive data processing, and the purpose of reducing the delay can be achieved.

Through the embodiment, the base station sends the configuration information of the radio data bearer DRB to the user equipment, wherein the configuration information comprises the radio network temporary identifier RNTI which is specially used for the DRB; the base station receives and transmits user interface air interface data of the user equipment, wherein the user interface air interface data is borne on the DRB, so that the technical problem of large delay of user interface data transmission in the related technology is solved, and the technical effect of reducing the transmission delay of the user interface data is realized.

In the embodiment of step S401, when the base station sends the configuration information of the radio data bearer DRB to the user equipment, the configuration information includes a radio network temporary identifier RNTI, and the RNTI is dedicated to the DRB, that is, the RNTI is dedicated for transmission of the DRB.

The base station in step S402 receives and transmits user plane air interface data of the user equipment, which includes at least one of: the base station sends the air interface data of the user interface to the user equipment; and the base station receives user interface air interface data sent by the user equipment.

Optionally, a Data transmission format of the air interface Data of the user plane at a medium access control MAC layer of the base station is a transparent protocol Data Unit MAC PDU, where the transparent MAC PDU includes a Service Data Unit MAC SDU (Service Data Unit) for carrying the air interface Data of the user plane. For example, before the base station sends the user plane air interface data of the user equipment, the MAC (Media Access Control) Layer entity of the base station transmits the user plane air interface data to a PHY (Physical Layer Protocol) Layer entity of the sending end by using a transparent MAC PDU (MAC Protocol data unit).

It should be noted that, as shown in fig. 2, a MAC PDU in the existing LTE system includes a MAC header, a MAC payload, and other components, which both cause extra resource overhead for a packet sending object and a packet receiving object, and further affect the efficiency of sending and receiving, and a transparent MAC PDU is adopted, which does not include the MAC header, a MAC CE, Padding, and other components in the MAC payload, and thus the resource overhead of the packet sending object and the packet receiving object can be reduced, and meanwhile, the group/decapsulation head, and group/decapsulation tail processing on data are reduced, so as to achieve the effect of reducing the system processing delay.

Optionally, when the MAC layer entity of the base station transmits the user plane air interface data to the PHY layer entity of the base station by using the transparent MAC PDU, the MAC layer entity transmits the transparent MAC PDU to the PHY layer entity on a transmission channel for transmitting data to the PHY layer entity.

The base station side logical channel corresponding to the DRB has a one-to-one correspondence relationship with a first transmission channel through which the user plane air interface data passes, wherein the first transmission channel is a channel between an MAC layer and a PHY layer of the base station.

Optionally, before the MAC layer entity of the base station transmits the user plane air interface data to the PHY layer entity by using the transparent MAC PDU, the RLC layer entity of the base station transmits the user plane air interface data to the MAC layer entity by using a transparent transmission mode.

Optionally, a transport TB block used for transporting user plane air interface data in a physical PHY layer of the base station includes padding bits. For example, after the MAC layer entity transmits the user plane air interface data to the PHY layer entity by using the transparent MAC PDU, the PHY layer entity fills a transport block tb (transport block) according to the size of the supported transport block, and the transport block carries the user plane air interface data; after performing the padding step, the PHY layer entity may add a CRC (Cyclic Redundancy Check) Check code to the transport block.

According to an embodiment of the present invention, there is further provided a method embodiment of a data transmission method, and fig. 5 is a flowchart of an optional data transmission method according to an embodiment of the present invention, as shown in fig. 5, the method includes the following steps:

step S501, the user equipment receives configuration information of a radio data bearer DRB sent by a base station, wherein the configuration information comprises a Radio Network Temporary Identifier (RNTI), and the RNTI is specially used for the DRB.

Step S502, the user equipment receives and transmits the user interface air interface data of the base station, and the user interface air interface data is loaded on the DRB.

Through the embodiment, the user equipment receives the configuration information of the radio data bearer DRB sent by the base station, wherein the configuration information comprises the radio network temporary identifier RNTI which is specially used for the DRB; the user equipment receives and transmits user interface air interface data of the base station, wherein the user interface air interface data is borne on the DRB, so that the technical problem of large delay of user interface data transmission in the related technology is solved, and the technical effect of reducing the transmission delay of the user interface data is realized.

The ue in step S502 receives and transmits user plane air interface data of the base station, where the user plane air interface data includes at least one of the following data: user equipment sends user interface air interface data to a base station; and the user equipment receives user interface air interface data sent by the base station.

Optionally, a data transmission format of the user plane air interface data at a medium access control MAC layer of the user equipment is a transparent protocol data unit MAC PDU, where the transparent MAC PDU only includes a service data unit MAC SDU for carrying the user plane air interface data.

The following detailed description of embodiments of the present application refers to specific implementation scenarios:

scene 1

And the MAC transparent transmission scheme of the URLLC service in the unicast scene.

The structure of the user plane protocol stack layer of the LTE system is shown in fig. 6, which depicts the structure of the uplink and downlink user planes of the PDCP layer, the RLC layer, and the MAC layer. The layers interact with each other through sap (service Access points), a transport channel is between the MAC Layer and the PHY Layer (the lowest Physical Layer of OSI), and a logical channel is between the MAC Layer and the RLC Layer. The MAC layer provides a service of multiplexing a plurality of logical channels (i.e., radio bearers) to the same transport channel.

Fig. 6 is divided into two types of data bearers: common service bearer and URLLC (Low Latency high reliability URLLC is collectively called Ultra Reliable Low Latency Communication) service dedicated bearer.

As can be seen from fig. 6, the common service bearer is subjected to PDCP layer ciphering and header compression, RLC layer segmentation/concatenation processing is mapped to a corresponding logical channel DTCH, and the MAC layer performs scheduling, multiplexing and HARQ (Hybrid Automatic Repeat reQuest) operation on each logical channel data, and maps the logical channels to one for many on transport channels (e.g., downlink transport channel DL-SCH, uplink transport channel UL-SCH). The dedicated bearer for URLLC service is processed through PDCP layer ciphering and header compression (period ROHC/ciphering) (the dashed boxes in fig. 6 indicate that ciphering and header compression may not be performed optionally), RLC layer transparent transmission is mapped onto the dedicated logical channel, and the MAC layer performs scheduling and HARQ operations on the dedicated logical channel for URLLC service, but does not multiplex the logical channels, but maps them onto transport channels one-to-one.

In this embodiment, a MAC transparent transmission scheme of URLLC service in a unicast scenario is mainly described, and a service model thereof is shown in fig. 7, where a user equipment UE performs data interaction with a base station. Under the unicast scene, the data of the downlink URLLC service is divided into two types: first packet data of dynamic Scheduling or SPS Scheduling (Semi-Persistent Scheduling); the non-first packet of the SPS schedule periodically schedules data. The downlink data transmission process is shown in fig. 8.

Sub-scene A

The downlink URLLC service belongs to the first packet of data of dynamic scheduling or SPS scheduling, and the specific transmission steps are as follows:

step S801, downlink URLLC service data arrives at the base station from the gateway X-GW, and the base station determines to issue the service data through the dedicated bearer of the URLLC service.

Step S802, the PDCP layer of the base station can directly transmit the URLLC service to RLC without ROHC header compression and encryption processing; or the URLLC service is processed in the same way as ordinary service data.

Step S803, the RLC layer of the base station transparently transfers the RLC SDU, that is, does not perform segmentation/concatenation processing, and notifies the MAC layer.

Step S804 determines whether the data is the first packet data of the dynamic scheduling or the SPS scheduling, if so, step S805 is executed, otherwise, step S808 is executed.

Step S805, the MAC layer of the base station carries out downlink dynamic scheduling, sends the scheduling result to the PHY layer, and simultaneously directly transmits the MAC SDU as the MAC PDU to the PHY layer (the MAC layer maps the DTCH of the special logic channel of the URLLC service to the transmission channel one-to-one without multiplexing, and neither MAC header nor padding is added to the MAC SDU.

In step S806, the PHY of the base station processes the downlink control information and a TB Block (Transport Block) and transmits the processed information and the TB Block over the air interface. In the above process, the PHY may process the PDCCH and the PDSCH with the dedicated RNTI configured during the URLLC service bearer establishment, and when the TBsize (data block size) supported by the physical layer is larger than the service data packet size, the physical layer pads (i.e., fills) the TB block before CRC addition.

In step S807, the terminal UE resolves the corresponding PDCCH with a dedicated RNTI (Cell Radio Network Temporary Identifier) configured when the URLLC service bearer is established, and receives data.

In step S812, the PHY of the terminal performs processing to transfer the TB block to the MAC layer.

In step S813, the MAC layer of the terminal passes through the transparent MAC PDU to the RLC (the MAC layer does not need to decapsulate and depacketize).

In step S814, the RLC layer of the terminal passes the RLC PDU through to the PDCP layer.

Step S815, the PDCP layer of the terminal performs no processing on the PDCP PDU, and directly passes through the PDCP PDU, or performs the same processing as the normal service data, that is, header decompression and decryption processing.

Sub scene B

The downlink URLLC service belongs to non-first-packet periodic scheduling data scheduled by SPS, and the specific transmission steps are as follows:

the first four steps of this scenario are the same as steps S801 to S804 in the previous embodiment.

Step S808, determining whether the SPS period data is acquired, if so, performing step S809, otherwise, ending.

Step S809, the MAC layer of the base station directly transfers the MAC SDU to the PHY as a MAC PDU. The MAC layer maps the DTCH of the dedicated logical channel of the URLLC service to the transmission channel one by one without multiplexing. Neither MAC header nor padding is added to the MAC SDU.

In step S810, the PHY of the base station processes the TB block and transmits it over the air interface. In the above process, the PHY may process the PDSCH with the dedicated RNTI configured when the URLLC service bearer is established, and when the TBsize supported by the physical layer is larger than the size of the service data packet, the physical layer pads the TB block before CRC addition.

In step S811, the terminal UE receives data.

The remaining steps are the same as steps S812 to S815.

In a unicast scenario, data of an uplink URLLC service is divided into two types: first packet data of dynamic scheduling or SPS scheduling; the non-first packet of the SPS scheduling periodically schedules data. The uplink data transmission process is shown in fig. 9.

Sub scene C

The uplink URLLC service belongs to the first packet of data of dynamic Scheduling or SPS Scheduling, and does not include BSR (Buffer Status Reports) information in a dedicated SR (Scheduling Request SR is fully called Scheduling Request), and can be executed according to the following steps:

step S901, the uplink URLLC service data arrives at the terminal, and the terminal determines to transmit the service data through the URLLC service dedicated bearer.

Step S902, PDCP layer of terminal does not process ROHC head compression and encryption process to URLLC business, and transmits to RLC layer; or the URLLC service is processed in the same way as ordinary service data, namely header compression and encryption processing are carried out.

Step S903, the RLC layer of the terminal transparently transfers the RLC SDU, that is, does not perform segmentation/concatenation processing, and notifies the MAC layer that uplink data arrives.

Step S904, determining whether the data is the first packet data of the dynamic scheduling or the SPS scheduling, if so, performing step S905, otherwise, performing step S912.

Step S905, the terminal sends the dedicated scheduling request SR of the uplink URLLC service to the base station.

Step S906, determining whether the dedicated scheduling request SR carries BSR information, if yes, performing step S910, otherwise, performing step S907.

Step S907, the base station sends a small uplink grant to the terminal, so that the terminal reports a data buffer report BSR to the base station.

Step S908, the terminal sends BSR dedicated to the uplink URLLC service to the base station.

In step S909, the base station MAC layer performs uplink scheduling and transmits the scheduling result to the PHY of the terminal.

And the PHY layer at the base station side processes the uplink scheduling result and sends the uplink scheduling result to the terminal through an air interface. In the above process, the PHY may use the dedicated RNTI configured when the URLLC service bearer is established when processing the PDCCH.

And the PHY layer of the terminal uses the special RNTI configured during the establishment of the URLLC service bearer to solve the uplink authorization information.

Step S913, the MAC layer of the terminal obtains the MAC SDU from the RLC layer, the MAC layer directly transfers (transparently transfers) the MAC SDU to the PHY as a MAC PDU, and the MAC layer maps the DTCH, which is a dedicated logical channel of the URLLC service, to a transport channel in a one-to-one manner without multiplexing. Neither MAC header nor padding is added to the MAC SDU.

Step S914, the terminal PHY layer processes the TB block and sends the PUSCH carrying the uplink data to the base station, and when the TBsize supported by the physical layer is larger than the size of the service data packet, the physical layer pads the TB block before CRC addition.

Step S915, the PHY layer on the base station side receives and processes the uplink data, and then sends the TB block to the MAC layer. The procedure is descrambled using the private RNTI.

In step S916, the MAC layer of the base station does not process the transparent MAC PDU and passes it to the RLC layer. The MAC layer does not need to decapsulate and depacketize.

In step S917, the RLC layer of the base station does not process the transparent RLC PDU and passes it to the PDCP layer.

In step S918, the PDCP layer of the base station may perform transparent transmission processing or the same processing as the normal service data, i.e., header compression and ciphering processing, on the PDCP PDU.

In case that the dedicated SR contains BSR information (the traffic packet size is fixed), it can be performed as follows:

the first four steps are the same as steps S901 to S904.

In step S910, the terminal sends a dedicated scheduling request SR for uplink URLLC service (including BSR information) to the base station.

Step S911, the base station side MAC layer obtains BSR information from the dedicated scheduling request SR to perform uplink scheduling, and sends the scheduling result to the PHY.

The remaining steps are the same as steps S913 to S918.

If the determination result in step S904 is no, step S912 is executed.

In step S912, it is determined whether the SPS period data is acquired, if so, step S913 is executed, otherwise, the process is ended.

Sub-scene D

The uplink URLLC service belongs to non-first packet periodic scheduling data scheduled by SPS, and the specific steps are as follows:

in step S11, the uplink URLLC service data arrives at the terminal, and the terminal determines to transmit the service data through the URLLC service dedicated bearer.

Step S12, the PDCP layer of the terminal does not carry out ROHC head compression and encryption processing on the URLLC service, and transmits the ROHC head compression and encryption processing to the RLC layer; or the URLLC service is processed in the same way as ordinary service data.

In step S13, the RLC layer of the terminal transparently transfers the RLC SDU, i.e., does not perform segmentation/concatenation processing, and notifies the MAC layer.

Step S14, the MAC layer of the terminal obtains MAC SDUs from the RLC layer, the MAC layer directly transfers the MAC SDUs as MAC PDUs to the PHY, and the MAC layer maps the DTCH of the dedicated logical channel of the URLLC service to the transport channel one-to-one without multiplexing. Neither MAC header nor padding is added to the MAC SDU.

And step S15, the terminal PHY layer processes the TB block and sends the PUSCH carrying the uplink data to the base station, and when the TBsize supported by the physical layer is larger than the size of the service data packet, the physical layer pads the TB block before CRC is added.

Step S16, the base station receives the uplink data, and after the PHY layer processes the uplink data, the TB block is sent to the MAC layer. The procedure is descrambled using the private RNTI.

Step S17, the MAC layer of the base station does not process the transparent MAC PDU and passes it to the RLC layer. No de-header and de-padding is required.

In step S18, the RLC layer of the base station does not process the transparent RLC PDU and passes it to the PDCP layer.

In step S19, the PDCP layer of the base station may transparently transmit the PDCP PDUs. (or the same processing as that of the general service data is performed.

It should be noted that, when the URLLC service and the common service exist simultaneously, the common service is processed according to the transmission process of the common service, the scheme does not affect the transmission process of the common service, and there is a difference only in priority, the priority of the common service is lower than that of the URLLC service, and the common service and the URLLC service cannot be multiplexed in one MAC PDU.

In the control plane processing of this embodiment, the above is a data transmission process of the downlink URLLC service in the unicast scenario, and the control plane of the URLLC service also needs to be specially configured. When the system configures a data radio bearer DRB, DRB configuration information includes a URLLC service private radio network temporary identity RNTI, and the role of the private RNTI includes two aspects, namely, on one hand, identifying the service bearer, and on the other hand, it is used for the physical layer to process control information and data information of the URLLC service and receive the terminal. Therefore, the special RNTI field is required to be added into the relevant information cells of the data radio bearer, corresponding conditions are set, and the special RNTI field is configured to the base station and the terminal through the special data radio bearer. In addition, in the application, the RLC and MAC layers of the receiving end and the transmitting end of the user plane both adopt a transparent transmission mode, and the configuration of the system for the radio bearer DR B of the URLLC service data needs to be matched with the user plane. The signaling interaction of the establishment, modification and release of the URLLC service bearer is as follows:

1. the dedicated bearer establishment procedure of URLLC is as shown in fig. 10:

in step S1001, the EPC transmits a URLLC dedicated bearer establishment REQUEST (E-RAB SETUP REQUEST) to the base station.

In step S1002, the base station eNB transmits the URLLC dedicated bearer message to the UE through a reconfiguration message (RRCConnectionReconfiguration), where the reconfiguration message needs to be configured with the dedicated RNTI identifying the URLLC.

Step S1003, the UE successfully establishes the dedicated bearer, and returns an rrcconnectionreconfiguration complete message (the message carries the dedicated RNTI).

In step S1004, the base station sends an E-RAB SETUP RESPONSE message to the EPC indicating that the radio bearer establishment is successful.

2. URLLC dedicated bearer modification procedure as shown in fig. 11:

in step S1101, the EPC transmits a URLLC dedicated bearer modification message to the eNB through E-RAB MODIFY RESPONSE.

In step S1102, the eNB transmits the URLLC dedicated bearer modification message indicated by the dedicated RNTI to the UE through a reconfiguration message (RRCConnectionReconfiguration).

Step S1103, the UE successfully establishes the dedicated bearer, and returns an rrcconnectionreconfiguration complete message (the message carries the dedicated RNTI), which indicates that the bearer modification is successful.

In step S1104, the eNB sends an E-RAB MODIFY RESPONSE message to the EPC indicating that the radio bearer modification is successful.

3. The URLLC dedicated bearer release procedure is as shown in fig. 12:

step S1201, EPC sends E-RAB Release Command message to eNB, releases URLLC special bearing.

Step S1202, the eNB starts a bearer release procedure, sends RRCConnectionReconfiguration to the UE, and the reconfiguration message needs to carry the dedicated RNTI of the identifier URLLC.

In step S1203, the UE receives the reconfiguration message RRCConnectionReconfiguration and then releases the relevant bearer resources, and sends an RRCConnectionReconfiguration complete message to the base station, indicating that the radio bearer release is successful.

Step S1204, the eNB receives the RRCConnectionReconfigurationComplete message, and then sends an E-RAB RELEASE RESPONSE message to the EPC, indicating that the radio bearer RELEASE is successful.

Scene 2

And the MAC transparent transmission scheme of the URLLC service in the CoMP scene.

This embodiment mainly describes an MAC transparent Transmission scheme of URLLC service in a CoMP (Coordinated Multiple Points Transmission/Reception) scenario, and a service model thereof is as shown in fig. 13. In this embodiment, a DPS data transmission model is adopted for downlink in the CoMP scenario, that is, only one base station in the CoMP coordination point set (multiple CoMP coordination base stations) transmits data to the UE at the same time, and other coordination points (base stations) do not transmit data to the UE. In fig. 13, the main serving cell a mainly performs scheduling and decision transmission of a cell of a downlink TB block, and the cells B and C are cooperative cells, and transmit a corresponding TB block to the terminal UE according to an indication of the main serving cell a.

Under a CoMP scene, data of a downlink URLLC service is divided into two types: first packet data of dynamic scheduling or SPS scheduling; the non-first packet of the SPS schedule periodically schedules data.

Sub-scene A

step S21, the downlink URLLC service data arrives at the base station a from the X-GW, and the base station a determines to issue the service data through the URLLC service dedicated bearer.

In step S22, the PDCP layer of the base station a may not perform ROHC header compression and ciphering on the URLLC service, and passes it to the RLC, or performs the same processing as that of the normal service data on the URLLC service.

In step S23, the RLC layer of the base station a does not perform segmentation/concatenation processing on the RLC SDU, and notifies the MAC layer.

In step S24, the MAC layer of the base station a performs downlink dynamic scheduling, and decides a cell currently suitable for data transmission with the terminal according to CoMP (here, the tentatively decided cell is the cooperative cell B). And the base station A sends the downlink scheduling result and the TB block of the downlink URLLC service to a PHY layer of the base station B. The MAC layer maps the DTCH of the dedicated logical channel of the URLLC service to the transmission channel one by one without multiplexing. Neither MAC header nor padding is added to the MAC SDU.

The next steps refer to the steps after step S805 in sub-scene a of scene 1.

Sub scene B

in step S31, the PDCP layer of the base station a may not perform ROHC header compression and ciphering on the URLLC service, but pass it to the RLC (or perform the same processing as that of the normal service data on the URLLC service).

In step S32, the RLC layer of the base station a does not perform segmentation/concatenation processing on the RLC SDU, and notifies the MAC layer.

In step S33, the MAC layer of the base station a determines a cell currently suitable for data transmission with the terminal according to CoMP, where the tentatively determined cell is the cooperative cell B. And the base station A sends the TB block of the downlink URLLC service to the PHY layer of the base station B. The MAC layer maps the DTCH of the dedicated logical channel of the URLLC service to the transmission channel one by one without multiplexing. Neither MAC header nor padding is added to the MAC SDU.

The next steps refer to the steps after step S805 in sub-scene a of scene 1.

It should be noted that: in the above two sub-scenarios, if the cell determined by the serving base station a according to CoMP is the cooperative cell C or the serving cell a, the procedure is as above.

The uplink of the CoMP scene mainly adopts a CS/CB data transmission model, that is, at the same time, the terminal UE transmits uplink data only to one base station with the best reception capability in the CoMP coordination point set (multiple CoMP coordination base stations) and does not transmit data to other coordination points (base stations) at the same time. Assume that base station a is selected at the current time.

The specific steps of the data transmission process of the uplink base station side and the terminal side refer to the data transmission step of the uplink URLLC service in scene 1.

Regarding control plane processing, the control plane specific configuration in the CoMP scenario handles the processing procedure of the control plane with reference to scenario 1.

Scene 3

And switching the MAC transparent transmission scheme of the URLLC service under the scene.

This embodiment mainly describes a MAC transparent transmission scheme of URLLC service in a seamless handover scenario, and a service model thereof is as shown in fig. 14. That is, in the RRC _ CONNECTED state, the terminal UE is handed over from the source cell a to the target cell B.

The specific steps of downlink URLLC service data transmission in this scenario are as follows:

step S41, when the terminal receives the switch command of the source base station cell A, it switches to the target base station, and at the same time, the data transmission with the source base station is interrupted, the source base station sends the non-transmitted downlink data to the target base station through the X2 port, and discards the non-successfully transmitted downlink data. The terminal starts to receive the downlink data of the target cell.

The remaining steps refer to scenario 1 downlink URLLC traffic transmission steps.

The specific steps of the uplink URLLC service data transmission of the switching scene are as follows:

step S51, the terminal switches to the target base station B, and the source base station a sends the uplink data that is successfully received to the gateway, and discards the uplink data that is not successfully received. And when the uplink between the terminal and the target base station B is successfully established, starting to transmit uplink data to the target base station B.

The remaining steps refer to scenario 1 uplink URLLC traffic transmission steps.

And control plane processing, namely switching the control plane special configuration processing of the terminal and the target base station under the scene to participate in the processing process of the control plane of the scene 1.

Scene 4

And the MAC transparent transmission scheme of the downlink URLLC service under the multicast scene.

This embodiment mainly describes an MAC transparent transmission scheme of a downlink URLLC service in a multicast scenario, and a service model is shown in fig. 15. The multicast scenario in this embodiment refers to a single-cell MBMS transmission scenario, i.e., SC-PTM transmission.

The downlink URLLC service data transmission mode in this scenario is as follows:

downlink URLLC service data arrives at an MBMS gateway from a user plane of a multicast/broadcast service center (BM-SC), the MBMS gateway determines to transmit the service data through a dedicated bearer of the URLLC service and is responsible for carrying out packet and header compression processing (or not carrying out PDCP layer processing) on the data, and the data arrives at a base station eNB through an M1 port. And the base station starts to receive the data of the MBMS user plane after joining the IP multicast group. Data interaction is performed with user terminals (e.g., UE 1-UE 3) through service group 1.

The remaining steps refer to the data transmission steps (the base station starts with the RLC layer processing) of the downlink URLLC service in scenario 1.

Control plane, control plane specific configuration in multicast scenarios handles the control plane of reference scenario 1. However, the bearer establishment and release of MBMS and the unicast scenario are slightly different, as follows.

1. The dedicated bearer establishment process of URLLC in MBMS scenario is shown in fig. 16:

step S1601, MME sends "MBMS session start request" message to MCE to start MBMS bearer establishment process, the message includes IP multicast address, message attribute and the shortest time waiting for the first packet data and available cell information.

Step S1602, the MCE decides to carry the MBMS bearer in the air interface by adopting an SC-PTM mode. And simultaneously, the MCE sends an 'MBMS Session Start Request' message to the base station eNB, and in the message, the MCE sends the cell information and the loaded QoS information acquired from the MME message to the base station.

In step S1603, the base station checks whether there are enough radio resources to establish a new MBMS service bearer, and if there are insufficient resources, the base station may give up establishing the bearer or acquire radio resources from other radio bearers in a preemption manner according to ARP to establish the bearer. Meanwhile, the base station replies a 'MBMS Session Start Response' message to the MCE.

Step S1604, after receiving the "MBMS Session Start Response" message replied by the base station, the MCE replies the "MBMS Session Start Response" message to the MME.

Step S1605, the base station sends "MBMS session start" message to the UE for notifying the UE about MCCH change and update indication information, wherein the information carries relevant configuration information of MBMS service.

It should be noted that the message of the MBMS bearer setup procedure carries the URLLC service dedicated RNTI.

2. Dedicated bearer establishment procedure for URLLC in MBMS scene as shown in figure 17

In step S1701, the MME transmits an "MBMS session stop request" message to the MCE.

In step S1702, the MCE replies an "MBMS Session stop" message to the MME.

Step S1703, the MCE sends an 'MBMS session stop request' message to the eNB base station.

In step S1704, the eNB replies an "MBMS Session stop" message to the MCE.

Step S1705, the eNB base station sends an 'MBMS session stop' message to the UE, and deletes the relevant MBMS service configuration information through the MCCH message.

The E-RAB bearer for the associated MBMS is released while the eNB leaves the IP multicast group.

It should be noted that the message in the MBMS bearer release procedure carries the URLLC service dedicated RNTI.

According to the technical scheme, when the low-delay service is transmitted, the MAC layer of the user plane transmits data by adopting the transparent MAC PDU, so that the time delay of adding/removing a header and adding/removing Padding to/from the MAC PDU by the MAC layer of the network side and the MAC layer of the terminal side can be saved. In addition, the MAC layer maps the dedicated logical channels corresponding to the low-delay service DRB to the transmission channels one to one, so that the multiplexing delay of the logical channels can be saved. The RLC layer of the user plane adopts a TM mode (namely a transparent transmission mode), so that the time delay of the RLC layers of the network side and the terminal side in segmentation, cascade connection, RLC SDUs recombination and reordering can be saved. Therefore, the requirement of low-delay service on delay can be met.

Through the above description of the embodiments, those skilled in the art can clearly understand that the method according to the above embodiments can be implemented by software plus a necessary general hardware platform, and certainly can also be implemented by hardware, but the former is a better implementation mode in many cases. Based on such understanding, the technical solutions of the present invention may be embodied in the form of a software product, which is stored in a storage medium (e.g., ROM/RAM, magnetic disk, optical disk) and includes instructions for enabling a terminal device (e.g., a mobile phone, a computer, a server, or a network device) to execute the method according to the embodiments of the present invention.

Example 2

The embodiment of the invention also provides a data transmission device. The device is used for implementing the above embodiments and preferred embodiments, and the description of the device is omitted. As used below, the term "module" may be a combination of software and/or hardware that implements a predetermined function. Although the means described in the embodiments below are preferably implemented in software, an implementation in hardware, or a combination of software and hardware is also possible and contemplated.

Fig. 18 is a schematic diagram of an alternative data transmission arrangement according to an embodiment of the invention. As shown in fig. 18, the apparatus may include: a transmitting unit 181 and a first transmitting unit 183.

A sending unit 181, configured to send configuration information of a DRB carried by radio data to a user equipment, where the configuration information includes a radio network temporary identifier RNTI, and the RNTI is dedicated to the DRB;

after receiving the configuration information, the user equipment may determine a DRB corresponding to the configuration information through the RNTI, where the DRB is dedicated for transmitting user plane air interface data or is dedicated for transmitting some type of user plane air interface data.

The first transmission unit 183 is configured to receive and transmit user plane air interface data of the user equipment, where the user plane air interface data is loaded on the DRB.

Through the embodiment, the sending unit sends the configuration information of the radio data bearer DRB to the user equipment, wherein the configuration information comprises the radio network temporary identifier RNTI which is specially used for the DRB; the first transmission unit receives and transmits user interface air interface data of the user equipment, wherein the user interface air interface data is borne on the DRB, so that the technical problem of large delay of user interface data transmission in the related technology is solved, and the technical effect of reducing the transmission delay of the user interface data is realized.

It should be noted that, as shown in fig. 2, the existing MAC PDU includes components such as a MAC header and a MAC payload, which may cause additional resource overhead for both a packet sending object and a packet receiving object, and further may affect efficiency of sending and receiving, and the transparent MAC PDU is adopted without including components such as a MAC header, a MAC CE in the MAC payload, and Padding, which may further reduce resource overhead for the packet sending object and the packet receiving object.

The embodiment of the invention also provides a data transmission device. Fig. 19 is a schematic diagram of an alternative data transmission arrangement according to an embodiment of the invention. As shown in fig. 19, the apparatus may include: a receiving unit 191 and a second transmitting unit 193.

A receiving unit 191, configured to receive configuration information of a DRB carried by radio data sent by a base station, where the configuration information includes a radio network temporary identifier RNTI and the RNTI is dedicated to the DRB;

a second transmission unit 193, configured to receive and send user plane air interface data of a base station, where the user plane air interface data is carried on the DRB.

According to the technical scheme, when the low-delay service is transmitted, the MAC layer of the user plane transmits data by adopting the transparent MAC PDU, so that the time delay of adding/removing a header and adding/removing Padding to/from the MAC PDU by the MAC layer of the network side and the MAC layer of the terminal side can be saved. In addition, the MAC layer maps the dedicated logical channels corresponding to the low-latency service DRB to the transmission channels in a one-to-one manner, so that the multiplexing delay of the logical channels can be saved. The RLC layer of the user plane adopts a TM mode (namely a transparent transmission mode), so that the time delay of the RLC layers of the network side and the terminal side in segmentation, cascade connection, RLC SDUs recombination and reordering can be saved. Therefore, the requirement of low-delay service on delay can be met.

It should be noted that, the above modules may be implemented by software or hardware, and for the latter, the following may be implemented, but not limited to: the modules are all positioned in the same processor; alternatively, the modules are respectively located in different processors in any combination.

Example 3

A base station is further provided in the embodiment of the present invention, and fig. 20 is a schematic diagram of the base station according to the embodiment of the present invention. As shown in fig. 20, the base station may include: a first processor 201, a first memory 203, and a first transmission device 205.

The first memory 203 is used for storing executable instructions of the first processor 201;

the first transmission means 205 is used for information transceiving communication according to the control of the first processor.

The first processor is configured to perform the following operations: sending configuration information of a radio data bearer (DRB) to user equipment, wherein the configuration information comprises a Radio Network Temporary Identifier (RNTI), and the RNTI is specially used for the DRB; and receiving and transmitting user interface air interface data of the user equipment, wherein the user interface air interface data is borne on the DRB.

In the above embodiment, when transmitting the low latency service, the MAC layer of the user plane transmits data by using the transparent MAC PDU, so that the group/unpacking delays of adding/removing the header and adding/removing Padding to/from the MAC PDU by the MAC layers of the network side and the terminal side can be omitted. In addition, the MAC layer maps the dedicated logical channels corresponding to the low-delay service DRB to the transmission channels one to one, so that the multiplexing delay of the logical channels can be saved. The RLC layer of the user plane adopts a TM mode (namely a transparent transmission mode), so that the time delay of the RLC layers of the network side and the terminal side in segmentation, cascade connection, RLC SDUs recombination and reordering can be saved. Therefore, the requirement of low-delay service on delay can be met.

Example 4

The embodiment of the present invention further provides a user equipment, and fig. 21 is a schematic diagram of the user equipment according to the embodiment of the present invention. As shown in fig. 21, the base station may include: a second processor 211, a second memory 213, and a second transmission device 215.

The second memory 213 is used for storing executable instructions of the second processor 211;

the second transmission means 215 is for performing information transceiving communication according to the control of the second processor.

The second processor is configured to perform the following operations: receiving configuration information of a radio data bearer (DRB) sent by a base station, wherein the configuration information comprises a Radio Network Temporary Identifier (RNTI) which is specially used for the DRB; and receiving and transmitting user interface air interface data of the base station, wherein the user interface air interface data is borne on the DRB.

Example 5

The embodiment of the invention also provides a storage medium. Alternatively, in the present embodiment, the storage medium may be configured to store program codes for performing the following steps:

s1, receiving configuration information of DRB carried by wireless data sent by a base station, wherein the configuration information comprises a Radio Network Temporary Identifier (RNTI), and the RNTI is dedicated for the DRB;

and S2, receiving and transmitting user interface data of the base station, wherein the user interface data is loaded on the DRB.

Optionally, the storage medium is further arranged to store program code for performing the steps of:

s3, sending configuration information of the DRB carried by the wireless data to the user equipment, wherein the configuration information comprises a Radio Network Temporary Identifier (RNTI), and the RNTI is specially used for the DRB;

and S4, receiving and transmitting user interface data of the user equipment, wherein the user interface data is loaded on the DRB.

Optionally, in this embodiment, the storage medium may include, but is not limited to: a U-disk, a Read-Only Memory (ROM), a Random Access Memory (RAM), a removable hard disk, a magnetic or optical disk, and other various media capable of storing program codes.

Optionally, in this embodiment, the processor executes, according to the program code stored in the storage medium: sending configuration information of a radio data bearer (DRB) to user equipment, wherein the configuration information comprises a Radio Network Temporary Identifier (RNTI), and the RNTI is specially used for the DRB; and receiving and transmitting user interface air interface data of the user equipment, wherein the user interface air interface data is borne on the DRB.

Optionally, in this embodiment, the processor executes according to program codes stored in the storage medium, receiving configuration information of a radio data bearer DRB sent by the base station, where the configuration information includes a radio network temporary identity RNTI, and the RNTI is dedicated to the DRB; and receiving and transmitting user interface air interface data of the base station, wherein the user interface air interface data is borne on the DRB.

Optionally, the specific examples in this embodiment may refer to the examples described in the above embodiments and optional implementation manners, and this embodiment is not described herein again.

It will be apparent to those skilled in the art that the modules or steps of the present invention described above may be implemented by a general purpose computing device, they may be centralized on a single computing device or distributed across a network of multiple computing devices, and alternatively, they may be implemented by program code executable by a computing device, such that they may be stored in a storage device and executed by a computing device, and in some cases, the steps shown or described may be performed in an order different than that described herein, or they may be separately fabricated into individual integrated circuit modules, or multiple ones of them may be fabricated into a single integrated circuit module. Thus, the present invention is not limited to any specific combination of hardware and software.

The above description is only a preferred embodiment of the present invention and is not intended to limit the present invention, and various modifications and changes may be made by those skilled in the art. Any modification, equivalent replacement, or improvement made within the spirit and principle of the present invention should be included in the protection scope of the present invention.

Claims

1. A method for transmitting data, comprising:

a base station sends configuration information of a radio data bearer (DRB) to user equipment, wherein the configuration information comprises a Radio Network Temporary Identifier (RNTI), and the RNTI is specially used for the DRB;

the base station receives and transmits user interface air interface data of the user equipment, wherein the user interface air interface data is borne on the DRB;

wherein, the DRB is dedicated to transmit the user plane air interface data, or is dedicated to transmit a type of the user plane air interface data;

and the data transmission format of the user plane air interface data in a medium access control MAC layer of the base station is a transparent protocol data unit (MAC PDU), wherein the transparent MAC PDU comprises a service data unit (MAC SDU) used for carrying the user plane air interface data.

2. The method of claim 1, wherein a transport TB block used for transporting the user plane air interface data in a physical PHY layer of the base station comprises padding bits.

3. The method of claim 1, wherein the base station side logical channel corresponding to the DRB has a one-to-one correspondence relationship with a first transport channel through which the user plane air interface data passes, wherein the first transport channel is a channel between a MAC layer and a PHY layer of the base station.

4. The method according to any one of claims 1 to 3, wherein the transmission mode adopted by the user plane air interface data in the Radio Link Control (RLC) layer of the base station is a transparent Transmission (TM) mode.

5. A method for transmitting data, comprising:

the method comprises the steps that user equipment receives configuration information of a radio data bearer (DRB) sent by a base station, wherein the configuration information comprises a Radio Network Temporary Identifier (RNTI), and the RNTI is specially used for the DRB;

the user equipment receives and transmits user interface air interface data of the base station, wherein the user interface air interface data is borne on the DRB;

and the data transmission format of the user plane air interface data on a Medium Access Control (MAC) layer of the user equipment is a transparent protocol data unit (MAC PDU), wherein the transparent MAC PDU comprises a service data unit (MAC SDU) used for carrying the user plane air interface data.

6. The method according to claim 5, wherein a transport TB block in a physical PHY layer of the UE, for transmitting the user plane air interface data, includes padding bits.

7. The method of claim 5, wherein the user equipment side logical channel corresponding to the DRB has a one-to-one correspondence relationship with a second transport channel through which the user plane air interface data passes, wherein the second transport channel is a channel between a MAC layer and a PHY layer of the user equipment.

8. The method according to any one of claims 5 to 7, wherein a transmission mode adopted by the user plane air interface data in a Radio Link Control (RLC) layer of the user equipment is a transparent Transmission (TM) mode.

9. A data transmission apparatus, applied to a base station, comprising:

a sending unit, configured to send configuration information of a radio data bearer DRB to a user equipment, where the configuration information includes a radio network temporary identifier RNTI, and the RNTI is dedicated to the DRB;

a first transmission unit, configured to receive and transmit user plane air interface data of the user equipment, where the user plane air interface data is borne on the DRB;

10. The apparatus of claim 9, wherein a transport TB block used for transmitting the user plane air interface data in a physical PHY layer of the base station comprises padding bits.

11. The apparatus of claim 9, wherein the base station side logical channel corresponding to the DRB has a one-to-one correspondence relationship with a first transport channel through which the user plane air interface data passes, wherein the first transport channel is a channel between a MAC layer and a PHY layer of the base station.

12. A base station, characterized in that it comprises means for transmitting data according to any one of claims 9 to 11.

13. A data transmission apparatus, applied to a user equipment, comprising:

a receiving unit, configured to receive configuration information of a radio data bearer DRB sent by a base station, where the configuration information includes a radio network temporary identifier RNTI, and the RNTI is dedicated to the DRB;

a second transmission unit, configured to receive and transmit user plane air interface data of the base station, where the user plane air interface data is borne on the DRB;

and the data transmission format of the user plane air interface data at a medium access control MAC layer of the user equipment is a transparent protocol data unit (MAC PDU), wherein the transparent MAC PDU comprises a service data unit (MAC SDU) used for carrying the user plane air interface data.

14. The apparatus of claim 13, wherein a transport TB block used for transmitting the user plane air interface data in a physical PHY layer of the user equipment includes padding bits.

15. A user equipment comprising the data transmission device of any one of claims 13 to 14.

16. A base station, comprising:

a first processor;

a first memory for storing the first processor-executable instructions;

first transmission means for performing information transceiving communication according to control of the first processor;

wherein the first processor is configured to: sending configuration information of a radio data bearer (DRB) to user equipment, wherein the configuration information comprises a Radio Network Temporary Identifier (RNTI), and the RNTI is specially used for the DRB; receiving and transmitting user interface air interface data of the user equipment, wherein the user interface air interface data is borne on the DRB;

17. A user device, comprising:

a second processor;

a second memory for storing the second processor-executable instructions;

second transmission means for performing information transceiving communication according to control of the second processor;

wherein the second processor is configured to: receiving configuration information of a radio data bearer (DRB) sent by a base station, wherein the configuration information comprises a Radio Network Temporary Identifier (RNTI), and the RNTI is specially used for the DRB; receiving and transmitting user interface air interface data of the base station, wherein the user interface air interface data is borne on the DRB;