WO2018145521A1 - 一种数据传输方法、通信设备、终端和基站 - Google Patents

一种数据传输方法、通信设备、终端和基站 Download PDF

Info

Publication number
WO2018145521A1
WO2018145521A1 PCT/CN2017/117540 CN2017117540W WO2018145521A1 WO 2018145521 A1 WO2018145521 A1 WO 2018145521A1 CN 2017117540 W CN2017117540 W CN 2017117540W WO 2018145521 A1 WO2018145521 A1 WO 2018145521A1
Authority
WO
WIPO (PCT)
Prior art keywords
data packet
attribute
terminal
data
communication device
Prior art date
Application number
PCT/CN2017/117540
Other languages
English (en)
French (fr)
Inventor
刘菁
韩立锋
Original Assignee
华为技术有限公司
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by 华为技术有限公司 filed Critical 华为技术有限公司
Priority to JP2019542550A priority Critical patent/JP6907444B2/ja
Priority to RU2019128270A priority patent/RU2753372C2/ru
Priority to EP17895664.5A priority patent/EP3570590B1/en
Publication of WO2018145521A1 publication Critical patent/WO2018145521A1/zh
Priority to US16/535,772 priority patent/US11190626B2/en

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W28/00—Network traffic management; Network resource management
    • H04W28/16—Central resource management; Negotiation of resources or communication parameters, e.g. negotiating bandwidth or QoS [Quality of Service]
    • H04W28/18—Negotiating wireless communication parameters
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L1/00—Arrangements for detecting or preventing errors in the information received
    • H04L1/0001—Systems modifying transmission characteristics according to link quality, e.g. power backoff
    • H04L1/0023—Systems modifying transmission characteristics according to link quality, e.g. power backoff characterised by the signalling
    • H04L1/0027—Scheduling of signalling, e.g. occurrence thereof
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L1/00—Arrangements for detecting or preventing errors in the information received
    • H04L1/12—Arrangements for detecting or preventing errors in the information received by using return channel
    • H04L1/16—Arrangements for detecting or preventing errors in the information received by using return channel in which the return channel carries supervisory signals, e.g. repetition request signals
    • H04L1/18—Automatic repetition systems, e.g. Van Duuren systems
    • H04L1/1812—Hybrid protocols; Hybrid automatic repeat request [HARQ]
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L1/00—Arrangements for detecting or preventing errors in the information received
    • H04L1/12—Arrangements for detecting or preventing errors in the information received by using return channel
    • H04L1/16—Arrangements for detecting or preventing errors in the information received by using return channel in which the return channel carries supervisory signals, e.g. repetition request signals
    • H04L1/18—Automatic repetition systems, e.g. Van Duuren systems
    • H04L1/1867—Arrangements specially adapted for the transmitter end
    • H04L1/1874—Buffer management
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L1/00—Arrangements for detecting or preventing errors in the information received
    • H04L1/12—Arrangements for detecting or preventing errors in the information received by using return channel
    • H04L1/16—Arrangements for detecting or preventing errors in the information received by using return channel in which the return channel carries supervisory signals, e.g. repetition request signals
    • H04L1/18—Automatic repetition systems, e.g. Van Duuren systems
    • H04L1/1867—Arrangements specially adapted for the transmitter end
    • H04L1/1887—Scheduling and prioritising arrangements
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L47/00—Traffic control in data switching networks
    • H04L47/10—Flow control; Congestion control
    • H04L47/24—Traffic characterised by specific attributes, e.g. priority or QoS
    • H04L47/2425—Traffic characterised by specific attributes, e.g. priority or QoS for supporting services specification, e.g. SLA
    • H04L47/2433—Allocation of priorities to traffic types
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L47/00—Traffic control in data switching networks
    • H04L47/10—Flow control; Congestion control
    • H04L47/24—Traffic characterised by specific attributes, e.g. priority or QoS
    • H04L47/2441—Traffic characterised by specific attributes, e.g. priority or QoS relying on flow classification, e.g. using integrated services [IntServ]
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L47/00—Traffic control in data switching networks
    • H04L47/10—Flow control; Congestion control
    • H04L47/24—Traffic characterised by specific attributes, e.g. priority or QoS
    • H04L47/2466—Traffic characterised by specific attributes, e.g. priority or QoS using signalling traffic
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L47/00—Traffic control in data switching networks
    • H04L47/10—Flow control; Congestion control
    • H04L47/32—Flow control; Congestion control by discarding or delaying data units, e.g. packets or frames
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W28/00—Network traffic management; Network resource management
    • H04W28/02—Traffic management, e.g. flow control or congestion control
    • H04W28/06—Optimizing the usage of the radio link, e.g. header compression, information sizing, discarding information
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W72/00—Local resource management
    • H04W72/50—Allocation or scheduling criteria for wireless resources
    • H04W72/56—Allocation or scheduling criteria for wireless resources based on priority criteria
    • H04W72/566—Allocation or scheduling criteria for wireless resources based on priority criteria of the information or information source or recipient
    • H04W72/569—Allocation or scheduling criteria for wireless resources based on priority criteria of the information or information source or recipient of the traffic information
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W8/00—Network data management
    • H04W8/02—Processing of mobility data, e.g. registration information at HLR [Home Location Register] or VLR [Visitor Location Register]; Transfer of mobility data, e.g. between HLR, VLR or external networks
    • H04W8/04—Registration at HLR or HSS [Home Subscriber Server]
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L69/00—Network arrangements, protocols or services independent of the application payload and not provided for in the other groups of this subclass
    • H04L69/22—Parsing or analysis of headers

Definitions

  • the embodiments of the present invention relate to the field of communications, and in particular, to a data transmission method, a communication device, a terminal, and a base station.
  • the decodable data frame types in the video coding standard can be classified into intra-coded frames (I-Frames), intra-coded frames (I-frames), unidirectional predictive coded frames (P-Frames), and bidirectional predictive coding.
  • I-Frames intra-coded frames
  • I-frames intra-coded frames
  • P-Frames unidirectional predictive coded frames
  • B-Frame Bi-directional predicted frames, B-frame.
  • the I frame is a complete picture
  • the P frame and the B frame record the changes of the P frame and the B frame with respect to the I frame.
  • the I frame has the function of truncation error propagation
  • the P frame is often used as the reference frame of other inter-coded frames, which is second to the I frame. Since B frames are usually not used as reference frames, their loss has less impact on video decoding quality. If an I frame is corrupted during transmission, the P frame and the B frame cannot be decoded. Therefore, it is very important to distinguish different frame types of data streams in video transmission applications.
  • the embodiments of the present invention provide a data transmission method, a communication device, a terminal, and a base station, which are used to improve the reliability of a transport packet with high importance, thereby reducing the transmission quality of the service to be transmitted due to the occurrence of network congestion. Impact.
  • an embodiment of the present invention provides a data transmission method, including: a communication device determining an attribute of a data packet to be transmitted, an attribute of the data packet is used to indicate an importance of the data packet, and the communication device adopts an attribute corresponding to the data packet.
  • Configuration parameters transfer packets.
  • the embodiment of the invention provides a data transmission method, which determines the attribute of the data packet to be transmitted, and then transmits the data packet by using the configuration parameter corresponding to the attribute of the data packet.
  • the configuration parameters used for the data packet transmission are also different.
  • each data packet of the same to-be-transmitted service is transmitted by using the same configuration parameter.
  • the data packets included in the transmission service according to the attribute are transmitted by using the configuration parameters corresponding to each data packet, so that the data packets of different attributes correspond to different configuration parameters, and the data packets with different attributes can be treated differently to improve the importance.
  • the high reliability of the transmitted data packet reduces the impact of the quality of the transmission service to be transmitted due to the occurrence of network congestion.
  • the method provided by the embodiment of the present invention further includes: the communications device according to the data packet Attributes that determine the configuration parameters of the packet.
  • the attribute is an important attribute or a non-important attribute
  • the configuration parameter is a hybrid automatic repeat request HARQ parameter
  • the communication device determines the configuration parameter of the data packet according to the attribute of the data packet, including: the communication device determines that the configuration parameter of the data packet is the first HARQ parameter or the second HARQ parameter, where the first HARQ parameter is a configuration corresponding to the important attribute.
  • the communication device determines the configuration of the data packet according to the attribute of the data packet.
  • the parameter includes: the communication device determines that the configuration parameter of the data packet is the first discarding timing length or the second discarding timing length, where the first discarding timing length is a configuration parameter corresponding to the important attribute, and the second discarding timing length is a non-essential attribute corresponding to the parameter.
  • the configuration parameter, the first discarding timing length is greater than the second discarding timing length.
  • different HARQ parameters such as the first HARQ parameter and the second HARQ parameter
  • the data packets of the important attributes can be transmitted several times to Ensure that packets of important attributes are transmitted as successfully as possible.
  • different packet timing lengths eg, first discarding timing length and second discarding timing length
  • important packets are used when packets of different attributes reach their respective discarding timing lengths.
  • the corresponding second discarding timing length is greater than the first discarding timing length corresponding to the non-important attribute, so that the data packet of the non-essential attribute can be discarded even if the network resource is unchanged, so as to avoid the packet occupying the non-essential attribute too. Multi-network resources, thus ensuring reliable transmission of data packets of important attributes.
  • the communications device determines an attribute of the data packet to be transmitted, including: the communications device passes a media access control MAC entity, the first indication information that is sent by the packet data aggregation protocol PDCP entity of the communication device to the MAC entity for indicating the data packet received by the terminal; the communication device determines the data packet according to the first indication information. Or the communication device controls the RLC header according to the radio link of the data packet to determine the attribute of the data packet, wherein the RLC header carries an identifier that uniquely identifies the data packet attribute.
  • the communications device determines an attribute of the data packet to be transmitted, including: the communications device The attribute of the data packet acquired through the first logical channel is determined to be an important attribute, and the attribute of the data packet acquired through the second logical channel is determined as a non-critical attribute.
  • the communication device is a terminal, and the communication device determines the attribute of the data packet to be transmitted before
  • the method provided by the embodiment of the present invention further includes: receiving, by the terminal, second indication information that is sent by the base station to indicate a correspondence between a data packet of different attributes and a logical channel for transmitting the data packet.
  • the terminal receives the data packet through the first logical channel, it can determine that the attribute of the data packet is an important attribute, and when the data packet is received through the second logical channel, the attribute of the data packet can be determined to be a non-critical attribute.
  • the communications device determines the configuration parameter of the data packet according to the attribute of the data packet
  • the method provided by the embodiment of the present invention further includes: receiving, by the terminal, first configuration indication information that is sent by the base station to indicate that the terminal configures different configuration parameters for the data packets of different attributes.
  • the communications device is a base station
  • the method provided by the embodiment of the present invention further includes: The base station sends, to the terminal, first configuration indication information for instructing the terminal to configure different configuration parameters for the data packets of different attributes.
  • an embodiment of the present invention provides a communication device, including: a determining unit, configured to determine an attribute of a data packet to be transmitted, an attribute of the data packet is used to indicate an importance of the data packet, and a transmission unit is configured to adopt the The configuration parameter of the packet's attribute corresponds to the transport packet.
  • the determining unit is further configured to: determine a configuration parameter of the data packet according to an attribute of the data packet.
  • the attribute is an important attribute or a non-important attribute
  • the configuration parameter is a hybrid automatic repeat request HARQ parameter.
  • the determining unit is specifically configured to: determine that the configuration parameter of the data packet is a first HARQ parameter or a second HARQ parameter, where the first HARQ parameter is a configuration parameter corresponding to the important attribute, and the configuration of the second HARQ parameter is corresponding to the non-important attribute.
  • the parameter, the value of the first HARQ parameter is greater than the value of the second HARQ parameter;
  • the configuration parameter is the discarding timing length, and the determining unit is further configured to: determine that the configuration parameter of the data packet is the first discarding timing length or the second discarding timing length,
  • the first discarding timing length is a configuration parameter corresponding to the important attribute
  • the second discarding timing length is a configuration parameter corresponding to the non-essential attribute
  • the first discarding timing length is greater than the second discarding timing length.
  • the communications device includes: a first receiving unit, configured to be used by the communications device a MAC entity, the first indication information that is sent by the PDCP entity of the communication device to the MAC entity to indicate the attribute of the data packet received by the terminal; the determining unit is further configured to: determine the attribute of the data packet according to the first indication information; or The determining unit is further configured to determine an attribute of the data packet according to the RLC packet header of the data packet, where the RLC packet header carries an identifier that uniquely identifies the data packet attribute.
  • the determining unit is configured to use the data acquired by using the first logical channel.
  • the attributes of the package are determined to be important attributes; and the attributes of the data packets acquired through the second logical channel are determined to be non-critical attributes.
  • the communications device further includes: a second receiving unit, configured to receive, send, by the base station Second indication information for indicating a correspondence between a data packet of a different attribute and a logical channel for transmitting the data packet.
  • the communications device further includes: a second receiving unit, configured to receive, send, by the base station The first configuration indication information for indicating that the terminal configures different configuration parameters for the data packets of different attributes.
  • the base station further includes: a sending unit, configured to send, to the terminal, an indication The terminal configures first configuration indication information of different configuration parameters for the data packets of different attributes.
  • an embodiment of the present invention provides a terminal, where the terminal includes a processor, a memory, a system bus, and a communication interface.
  • the memory is used to store a computer execution instruction, and the processor and the memory are connected through the system bus.
  • the processor executes a memory-stored computer-executable instruction to cause the terminal to perform the data transfer as described in any one of the possible implementations of the first aspect to the first aspect of the first aspect of the first aspect. method.
  • an embodiment of the present invention provides a base station, where the base station includes a processor, a memory, a system bus, and a communication interface.
  • the memory is used to store a computer to execute an instruction, and the processor and the memory are connected through a system bus, when the base station is running.
  • the processor executing the memory-stored computer-executable instructions to cause the base station to perform any one of the fourth possible implementation of the first aspect to the first aspect and the seventh possible implementation of the first aspect Data transmission method.
  • an embodiment of the present invention provides a computer readable storage medium, where the computer readable storage medium stores instructions, when the computer readable storage medium is run on a computer, causing the terminal to perform the first aspect to the first aspect.
  • an embodiment of the present invention provides a computer readable storage medium, where the computer readable storage medium stores instructions, when the computer readable storage medium is run on a computer, causing the base station to perform the first aspect to the first aspect.
  • an embodiment of the present invention provides a computer program product comprising instructions, when executed on a base station, causing a base station to perform any one of the fourth possible implementation manners of the first aspect to the first aspect and A method of the data transmission method described in the seventh possible implementation of the first aspect.
  • the embodiment of the present invention provides a computer program product, including instructions, when the terminal is executed on the terminal, causing the terminal to perform the sixth possible implementation manner of the first aspect of the first aspect to the first aspect.
  • an embodiment of the present invention provides a chip system, which is applied to a base station, where the chip system includes at least one processor and an interface circuit, and the interface circuit and the at least one processor are interconnected by a line, and the processor is used by the processor.
  • an embodiment of the present invention provides a chip system, which is applied to a terminal, where the chip system includes at least one processor and an interface circuit, and the interface circuit and the at least one processor are interconnected by a line, and the processor is used by the processor.
  • the embodiment of the present invention further provides a communication system, which includes the terminal described in any one of the possible implementations of the third aspect to the third aspect, and any possible implementation manner of the fourth aspect or the fourth aspect. Described base station.
  • any of the terminals, base stations or computer storage media provided above are used to perform the corresponding data transmission methods provided above, and therefore, the beneficial effects that can be achieved can be referred to the corresponding ones provided above.
  • the beneficial effects in the method are not described here.
  • FIG. 1a is a structural diagram of a communication system according to an embodiment of the present invention.
  • FIG. 1b is a structural diagram of another communication system according to an embodiment of the present invention.
  • FIG. 2a is a schematic structural diagram 1 of a terminal according to an embodiment of the present invention.
  • 2b is a schematic diagram 1 of a structure of a NALU according to an embodiment of the present invention.
  • 2c is a schematic diagram 2 of a structure of a NALU according to an embodiment of the present invention.
  • FIG. 2 is a schematic diagram 3 of a structure of a NALU according to an embodiment of the present invention.
  • 2 e is a schematic structural diagram 2 of a terminal according to an embodiment of the present invention.
  • 2f is a schematic structural diagram 3 of a terminal according to an embodiment of the present invention.
  • 2g is a schematic structural diagram 2 of a base station according to an embodiment of the present invention.
  • 2h is a schematic structural diagram 3 of a base station according to an embodiment of the present invention.
  • FIG. 3 is a schematic flowchart 1 of a data transmission method according to an embodiment of the present disclosure
  • FIG. 4 is a schematic flowchart 2 of a data transmission method according to an embodiment of the present invention.
  • FIG. 5 is a schematic flowchart 3 of a data transmission method according to an embodiment of the present disclosure.
  • FIG. 6 is a schematic flowchart 4 of a data transmission method according to an embodiment of the present disclosure.
  • FIG. 7 is a schematic diagram of another transmission architecture according to an embodiment of the present invention.
  • FIG. 8 is a schematic flowchart 5 of a data transmission method according to an embodiment of the present disclosure.
  • FIG. 9 is a schematic structural diagram of another terminal according to an embodiment of the present disclosure.
  • FIG. 9 is a schematic structural diagram of another terminal according to an embodiment of the present disclosure.
  • FIG. 9c is a schematic structural diagram of still another terminal according to an embodiment of the present disclosure.
  • FIG. 10 is a schematic structural diagram of still another terminal according to an embodiment of the present disclosure.
  • FIG. 10b is another schematic structural diagram of a terminal according to an embodiment of the present disclosure.
  • FIG. 10c is a schematic structural diagram of still another terminal according to an embodiment of the present invention.
  • the words “first”, “second” and the like are used to distinguish the same or similar items whose functions and functions are substantially the same, in the field.
  • the skilled person will understand that the words “first”, “second” and the like do not limit the quantity and order of execution.
  • the Hybrid Automatic Repeat ReQuest (HARQ) parameter in the embodiment of the present invention is the maximum number of uplink retransmissions, and is used to limit the maximum number of uplink data retransmissions of the terminal.
  • the length of the discarding timer in the embodiment of the present invention is the length of the discarding timer corresponding to the PDCP SDU.
  • the PDCP entity After receiving a PDCP SDU, the PDCP entity starts a timer corresponding to the PDCP SDU. When the timer expires, the PDCP entity The PDCP SDU and the corresponding PDCP PDU are discarded.
  • the to-be-transmitted service sent by the terminal to the base station may include multiple data packets with different attributes (the video transmission service is taken as an example), and the terminal generally encodes consecutive images in the video transmission service into I frames, P frames, and B frames. Three frame types.
  • the I frame adopts intra prediction coding, and can be decompressed into a single complete image by the video decompression algorithm, that is, the I frame can be decoded independently without reference to other frame data.
  • I frames are compressed by removing image space redundancy information as much as possible.
  • the P frame compresses the encoded image of the amount of transmitted data, also called the predicted frame, by substantially reducing the temporal redundancy information with the previously encoded frame in the sequence of images.
  • the P frame is predicted by the P frame or the I frame in front of it, and the P frame compresses the frame data according to the difference between the current frame and the adjacent previous frame or several frames.
  • the P frame belongs to the inter prediction of the forward prediction.
  • the P frame refers only to I frames or P frames that are located before the P frame and are close to the P frame.
  • a B frame may also be referred to as a bidirectional prediction frame.
  • the B frame compresses the B frame according to different points of the first few frames of the B frame, the current frame, and the subsequent frames of data. That is, only the difference between the B frame and the previous and subsequent frames adjacent to the B frame is recorded.
  • the B-frame compressed image can achieve an ultra-high compression ratio.
  • I frame compression is the lowest, P frame is higher, and B frame is the highest.
  • an I frame is a complete picture, while a P frame and a B frame record changes relative to an I frame. Without an I frame, P frames and B frames may not be decoded. Therefore, when transmitting the video transmission service, the communication device can use the I frame as a data packet whose attribute in the video transmission service is an important attribute (which can be called an important data packet), and use the P frame and the B frame as a video transmission service.
  • a packet whose attribute is a non-critical attribute can be called: a non-critical packet).
  • the non-adaptive retransmission is adopted, that is, the data packet of different attributes in the same to-be-transmitted service usually adopts the same configuration parameter.
  • the terminal receives the HARQ parameter configured by the base station for the terminal, that is, the maximum uplink retransmission parameter, by using a radio resource control (RRC) message.
  • RRC radio resource control
  • the terminal transmits the service to be transmitted to the base station according to the configured maximum hybrid automatic repeat request.
  • the terminal fails to transmit the service to be transmitted, the terminal transmits the to-be-transmitted service by using the maximum hybrid automatic repeat request corresponding to the to-be-transmitted service.
  • the terminal discards the to-be-transmitted service.
  • the base station configures a discarding timer duration for the discard timer (DT) corresponding to each to-be-transmitted service of the terminal.
  • the terminal After receiving a PDCP SDU, the terminal starts the discard timer corresponding to the to-be-transmitted service.
  • the terminal determines that the discarding timer corresponding to the to-be-transmitted service exceeds the discarding timer duration configured by the discarding timer, the terminal discards the PDCP SDU and the corresponding PDCP PDU.
  • the foregoing method uses the same configuration parameters for all data packets of the same to-be-transmitted service uploaded by the terminal. Therefore, multiple data packets of different importance included in the same to-be-transmitted service also adopt the same configuration parameter, that is, the important data packet and the non-critical data packet correspond to the same uplink maximum retransmission times or corresponding to the same discard timer. In this way, when the network is congested, since the important data packets and the non-critical data packets are not treated differently, once the important data packet transmission fails, (for example, if the I frame transmission fails during the transmission, the P frame and the B frame cannot be decoded. ) thus affecting the transmission quality of the entire service to be transmitted.
  • different data packets included in the service to be transmitted are differentiated according to importance, and different configuration parameters are configured for data packets of different attributes, so that when the same to-be-transmitted service includes multiple data packets with different attributes, Therefore, the data packets corresponding to different attributes are transmitted with different configuration parameters, thereby avoiding the occurrence of important data packet transmission failures as much as possible, thereby reducing the impact on the transmission quality of the service to be transmitted.
  • GSM global system of mobile communication
  • CDMA code division multiple access
  • WCDMA Wideband code division multiple access
  • GPRS general packet radio service
  • LTE long term evolution
  • FDD LTE frequency division duplex
  • TDD LTE time division duplex
  • UMTS universal mobile telecommunication system
  • WiMAX worldwide interoperability for microwave access
  • a base station may be a device that communicates with a terminal or other communication station, such as a relay station, and the base station may provide communication coverage of a specific physical area.
  • the base station may be a base transceiver station (BTS) or a base station controller (BSC) in GSM or CDMA; or a node B (NB) or UMTS in UMTS.
  • Radio network controller may also be an evolved Node B (eNB or eNodeB) in LTE; or may be other access in the wireless communication network providing access services
  • the network device is not limited in the embodiment of the present invention.
  • terminals may be distributed throughout the wireless network, and each terminal may be static or mobile.
  • a terminal may be referred to as a user equipment (UE), a server, a mobile station, a subscriber unit, a station, and the like.
  • the UE can be a cellular phone, a personal digital assistant (PDA), a wireless modem, a wireless communication device, a handheld, a laptop (lapTOS computer), a cordless phone. (cordless phone), wireless local loop (WLL) station.
  • PDA personal digital assistant
  • WLL wireless local loop
  • the UE When the UE is applied to the M2M mode communication, the UE may be referred to as an M2M terminal, and may specifically be a smart meter, a smart home appliance, or the like that supports M2M communication.
  • FIG. 1a is a structural diagram of a data transmission system to which a data transmission method is provided according to an embodiment of the present invention.
  • the data transmission system includes a first terminal 10, A base station 20, a core network 30, a core network 40, a second base station 50, and a second terminal 60.
  • the first base station 20 provides services for the first terminal 10
  • the second base station 50 provides services for the second terminal 60.
  • the first terminal 10 needs to send the to-be-transmitted service to the second terminal 20, the first terminal 10 sets each of the to-be-transmitted services according to the configuration parameters corresponding to each data packet.
  • the data packets are transmitted to the first base station 20.
  • the first base station 20 transmits the to-be-transmitted service to the core network 40 where the second base station 50 is located through the core network 30 where the first base station 20 is located, according to the configuration parameter corresponding to each data packet in the received to-be-transmitted service.
  • the second base station 50 obtains the to-be-transmitted service from the core network 40, and transmits the to-be-transmitted service to the second terminal 60, so that the first terminal 10 transmits the to-be-transmitted service to the second terminal 60, when the first terminal When the second terminal 60 and the second terminal 60 correspond to different base stations, the first terminal 10 and the second terminal 60 may correspond to the same packet data network gateway (PGW), or may correspond to different PGWs.
  • PGW packet data network gateway
  • the embodiment of the present invention uses the core network 30 as an example to describe the specific structure of the core network.
  • the core network 30 may include a mobility management entity (MME) 301 and a serving gateway. S-GW) 302, PGW) 303, policy and charging rules function (PCRF) 304, home subscriber server (HSS) 305, and mobile switching center (MSC) 306.
  • MME 301 is the core of the system and is mainly responsible for signaling grooming, encryption and integrity protection, and terminating user signaling of the non-access stratum.
  • the mobility of the user in the network is managed, including the processing of control signaling such as user access control, authentication, data encryption, service bearer control, paging, and handover control.
  • the S-GW 302 is used as an anchor point for handover between local base stations, and is mainly responsible for transmitting, forwarding, and routing data information between the base station and the PGW 303, providing buffering for downlink data packets, and implementing user-based charging.
  • PGW 303 is the anchor point of data bearer, and is mainly responsible for data packet forwarding, parsing, lawful interception, service-based charging, and quality of service (QoS) control.
  • the PCRF 304 is mainly used for making a decision according to the service information used by the user and the policy information subscribed by the user, and determining the policy of the user service usage and charging, and sending the policy to the policy execution entity in the gateway.
  • the HSS 305 is configured to store user subscription information, and the stored information includes user identification information, user security control information, user location information, user policy control information, and the like.
  • the MSC 306 is a device for providing call forwarding service and call control, and the MSC 306 can perform functions such as call connection, handover control, and wireless channel management.
  • FIG. 1b shows another architecture diagram of a data transmission system applied by a data transmission method according to an embodiment of the present invention.
  • the difference between FIG. 1b and FIG. 1a is that the first terminal and the second terminal are The terminal belongs to the same base station, for example, the base station 20.
  • the first terminal 10 and the second terminal 60 are located within the coverage of the same base station, the first terminal 10 and the second terminal 60 correspond to the same P-GW.
  • the communication device in the embodiment of the present invention may be a base station or a terminal.
  • the following is a description of a structure of a communication device by using a communication device as a terminal, as shown in FIG. 2a.
  • FIG. 2a is a schematic structural diagram of a terminal according to an embodiment of the present invention.
  • the terminal provided by the embodiment of the present invention includes an application (APP) layer, an encoding layer, a real-time transport protocol (RTP) layer, and a user datagram protocol (UDP).
  • APP application
  • RTP real-time transport protocol
  • UDP user datagram protocol
  • IP layer IP layer
  • filter filter
  • DRB data radio bearer
  • PHY physical (physical, PHY) layer.
  • DRB is used to transmit user plane data.
  • the DRB includes: a packet data convergence protocol (PDCP) entity, a radio link control (RLC) entity, and a media access control (MAC) entity.
  • PDCP packet data convergence protocol
  • RLC radio link control
  • MAC media access control
  • the PDCP entity and the RLC entity are connected by a logical channel
  • the RLC entity and the MAC entity are connected by a logical channel.
  • the PDCP entity corresponding to the same to-be-transmitted service has at least two buffers for storing data packets of different attributes.
  • the PDCP entity includes a first buffer and a second buffer.
  • the first buffer is used to store a data packet whose attribute is an important attribute (also referred to as an important data packet)
  • the second buffer is used to store a data packet whose attribute is a non-critical attribute (also referred to as: non-critical data). package).
  • a video compression standard is run in the coding layer, for example, the H.264 standard.
  • the physical layer is used to send out data packets scheduled by the PDCP entity or the MAC entity.
  • the H.264 standard is a highly compressed digital video codec jointly proposed by the international telecommunication union telecommunication standardization sector (ITU-T) and the international standardization organization (ISO)/IEC. standard.
  • the H.264 standard adopts a layered mode.
  • the H.264 standard is divided into two layers, namely a video coding layer (VCL) and a network abstraction layer ( Network abstraction layer, NAL).
  • VCL is the compression of video content.
  • NAL is responsible for packaging compressed data to accommodate transmission requirements in different network environments.
  • NALU network abstraction layer unit
  • SPS sequence parameter set
  • PPS image parameter set
  • the structure of the NALU Header field is as shown in Table 1:
  • the NALU header occupies 1 byte, wherein the nal_unit_type field in the NALU header is used to indicate the type of the NALU:
  • nal_unit_type a packet indicating that the attribute of the NAL data carried by the NALU is a non-essential attribute (for example, a B frame or a P frame).
  • nal_unit_type 5
  • a packet for example, an I frame
  • the attribute of the NAL data carried by the NALU is an important attribute.
  • the terminal may identify that the NAL data carried by the NALU is an I frame or a B/P frame according to parameters carried in the nal_unit_type field in the NALU header.
  • an RTP data packet may contain only one complete NALU, and may also include Multiple NALUs; if the NALU data length is greater than 1400 bytes, an RTP packet contains only a part of one NALU, or a NALU can be split into multiple RTP packets. That is to say, the data carried in an RTP data packet is either an important data packet (for example, an I frame) or a non-critical data packet (for example, a P frame or a B frame), and it is impossible for two different attributes of the data packet to occur. Mixing, that is, it is not possible to have a mixture of multiple types of frames at the same time.
  • the RTP data packet formed after the data passes through the RTP layer carries an RTP header, a NALU header, and NAL data, as shown in FIG. 2c.
  • the indication information carried in an RTP header is used to indicate the type of NAL data (data packet) carried in the RTP data packet.
  • the RTP data packet formed by the RTP layer is transmitted to a user datagram protocol (UDP) layer or an IP layer.
  • the RTP data packet is encapsulated in the UDP packet and then encapsulated in the IP packet.
  • the formed IP data packet carries an IP header, an RTP header, a NALU header, and NAL data, as shown in Figure 2d.
  • the TOS field of the IP header may carry 1 bit of indication information, and the terminal may use the 1 bit indication information carried in the IP header to indicate the attribute of the data packet carried by the IP data packet.
  • the terminal transmits the to-be-transmitted data packet (the IP data packet carrying the IP packet header) obtained from the IP layer to the PDCP entity, and the PDCP entity of the terminal maps the important data packet to the first according to the 1-bit indication information in the IP packet header of the IP data packet.
  • the non-significant data packet is mapped to the second buffer.
  • the PDCP entity adds the PDCP header information to the received data packet and sends it to the RLC entity, and the RLC entity reassembles, splits, and reorders the data frames processed by the PDCP entity according to the indication of the MAC entity, and uses the physical layer to transmit the data frame. Send it out.
  • FIG. 2e is a schematic structural diagram of another terminal according to an embodiment of the present invention. 2e differs from FIG. 2a in that one DRB corresponds to one RLC entity in FIG. 2a, and one DRB corresponds to at least two RLC entities in FIG. 2e, the at least two RLC entities are used to store data packets of different attributes.
  • Each of the at least two RLC entities is connected to the MAC entity through a logical channel, and the different RLC entities correspond to different logical channels, and the logical channel corresponding to one RLC entity is used to indicate the attributes of the data packet mapped in the RLC entity. .
  • the PDCP entity determines, according to the 1-bit indication information carried in the TOS field of the IP packet header, the attribute of the to-be-transmitted data packet acquired from the IP layer, and maps the to-be-transmitted data packet to the corresponding according to the attribute of the to-be-transmitted data packet.
  • the RLC entity On the RLC entity.
  • the embodiment of the present invention uses the at least two RLC entities as the first RLC entity and the second RLC entity as an example.
  • the first RLC entity is used to map data packets whose attributes are important attributes
  • the second RLC entity is used to map attributes.
  • the PDCP entity identifies that the transport packet is an important data packet by using the 1-bit indication information carried in the TOS field of the IP packet header, the PDCP entity maps the transport data packet to the first RLC entity, and the PDCP entity identifies that the transport data packet is not important.
  • the data packet is mapped to the second RLC entity, so that the data packets of different importance are respectively mapped to different RLC entities, wherein the first RLC entity is connected to the MAC entity by using the first logical channel, The second RLC entity is connected to the MAC entity through the second logical channel.
  • Important and non-critical packets can enable the receiving end to adopt synchronization/reordering processing on the important data packet and the non-critical data packet in the PDCP entity.
  • Important and non-critical packets can be configured with different reordering timers (T-reordering) corresponding to different RLC entities.
  • FIG. 2f is a schematic structural diagram of another terminal according to an embodiment of the present invention. 2f differs from FIG. 2a in that one DRB corresponds to one PDCP entity in FIG. 2a, and one DRB corresponds to at least two PDCP entities in FIG. 2f, and each of the at least two PDCP entities is used to store one attribute.
  • the data packet has the same attribute as the data packet stored in the same PDCP entity, and the attributes of the data packets stored in different PDCP entities are different.
  • the embodiment of the present invention is described by taking at least two PDCP entities as the first PDCP entity and the second PDCP entity.
  • the first PDCP entity is configured to store a data packet whose attribute is an important attribute
  • the second PDCP entity is used to store a data packet whose attribute is a non-critical attribute.
  • the terminal identifies, according to the 1-bit indication of the TOS field in the IP header of the IP packet, that the attribute of the IP data packet is an important attribute or a non-critical attribute.
  • the terminal determines that the attribute of the IP data packet is an important attribute, and then maps the IP data packet to the first PDCP entity. If the terminal determines that the attribute of the IP data packet is a non-critical attribute, the terminal maps the IP data packet to the second PDCP.
  • the first PDCP entity and the second PDCP entity respectively have one buffer. The buffer in the first PDCP entity is used to store important data packets, and the buffer in the second PDCP entity is used to store non-critical data packets.
  • the base station includes a baseband subsystem, a middle radio frequency subsystem, an antenna feeder subsystem, and some supporting structures (for example, a whole subsystem). ).
  • the baseband subsystem is used to implement operation and maintenance of the entire base station, implement signaling processing, radio resource principle, and transmission interface to the packet core network, and implement physical layer, medium access control layer, L3 signaling, and operation and maintenance main control functions.
  • the middle RF subsystem realizes conversion between the baseband signal, the intermediate frequency signal and the radio frequency signal, and realizes demodulation of the wireless receiving signal and modulation and power amplification of the transmitted signal.
  • the antenna feeder subsystem includes an antenna and a feeder connected to the base station radio frequency module and an antenna and a feeder of the GRS receiving card for receiving and transmitting the wireless air interface signal.
  • the whole subsystem is the supporting part of the baseband subsystem and the intermediate frequency subsystem, providing structure, power supply and environmental monitoring functions.
  • the baseband subsystem may be as shown in FIG. 2h: for example, the mobile phone Internet access needs to access the core network through the base station, and accesses the Internet through the core network, wherein the data of the Internet is transmitted to the baseband part through the interface between the core network and the base station.
  • the baseband part performs PDCP, RLC, MAC layer, coding, and modulation processing, and delivers to the radio frequency part for transmission to the user equipment.
  • the baseband and the radio frequency can be connected through the CPRI interface; in addition, the radio frequency part can be pulled far by the optical fiber, for example, the remote RRU.
  • the baseband of each step of the data transmission method in the embodiment of the present invention is implemented by radio frequency, and the receiving and transmitting step is implemented by an antenna (for example, an air interface).
  • the interface between the user equipment and the base station involved in the implementation of the present invention may be understood as an air interface for communication between the user equipment and the base station, or may also be referred to as a Uu interface.
  • FIG. 3 is a schematic flowchart of a data transmission method according to an embodiment of the present invention, where the method includes:
  • the terminal determines an attribute of the data packet to be transmitted, where the attribute of the data packet is used to indicate the importance of the data packet.
  • the data packet to be transmitted in the embodiment of the present invention may be any one of the data to be transmitted (for example, a video transmission service or another to-be-transmitted service).
  • the embodiment of the present invention uses the data packet to be transmitted as an example of any data packet in the video transmission service.
  • the video transmission service can be encoded into an I frame, a P frame, and a B frame by using the H.264 standard.
  • I frames, P frames, and B frames are respectively packets of different attributes.
  • attribute of a data packet is an important attribute, it indicates that the data packet needs to be preferentially scheduled during transmission (it can also be understood that the priority level of the data packet is higher), or the data packet cannot be lost during transmission. If the data packet of this important attribute is lost during the transmission, the service to be transmitted will be incomplete.
  • the attribute of a data packet is a non-critical attribute, it indicates that the data packet may be lost or has a lower priority in the transmission process, or the data packet of the non-critical attribute is lost, and the service to be transmitted is not affected.
  • the I frame since the I frame is decoded in the video transmission service, it is not necessary to refer to other frame data to be independently decoded.
  • the P frame and the B frame need to rely on the I frame to complete the decoding. Without the I frame, the P frame and the B frame cannot be decoded. Therefore, the I frame can be determined as a data packet whose attribute is an important attribute, and the P frame and the B frame are determined as data packets whose attributes are non-essential attributes.
  • the terminal transmits the data packet by using a configuration parameter corresponding to the attribute of the data packet.
  • the base station determines an attribute of the received data packet to be transmitted.
  • the base station transmits the data packet by using a configuration parameter corresponding to the attribute of the data packet.
  • the embodiment of the invention provides a data transmission method, which determines the attribute of the data packet to be transmitted, and then transmits the data packet by using the configuration parameter corresponding to the attribute of the data packet.
  • the configuration parameters used for the data packet transmission are also different.
  • each data packet of the same to-be-transmitted service is transmitted by using the same configuration parameter.
  • the data packets included in the transmission service according to the attribute are transmitted by using the configuration parameters corresponding to each data packet, so that the data packets of different attributes correspond to different configuration parameters, and the data packets with different attributes can be treated differently to improve the importance.
  • the high reliability of the transmitted data packet reduces the impact of the quality of the transmission service to be transmitted due to the occurrence of network congestion.
  • the embodiment of the present invention further includes: before step S102:
  • the base station sends the first configuration indication information to the terminal, where the first configuration indication information is used to indicate that the terminal configures different configuration parameters for the data packets of different attributes, where the configuration parameters include different HARQ parameter values or different discarding timing lengths.
  • the terminal receives the first configuration indication information sent by the base station.
  • the terminal may determine the configuration parameter corresponding to each data packet according to the first configuration indication information sent by the base station, or may actively configure a configuration parameter for each data packet according to the attribute of each data packet, when the terminal When actively configuring a configuration parameter for each data packet according to the attributes of each data packet, steps S105 and S106 may be omitted.
  • the base station may send the first configuration indication information to the terminal by using a Radio Resource Control (RRC) message.
  • RRC Radio Resource Control
  • the first configuration indication information may carry configuration parameters corresponding to each of the multiple attributes (for example, taking important data packets and non-critical data packets as an example)
  • the message carries a maxHARQ-Tx field and a minHARQ-Tx field, respectively, for indicating that the terminal limits the maximum number of uplink retransmissions of data packets of different importance.
  • the maxHARQ-Tx field is used to indicate that the terminal limits the maximum number of uplink retransmissions of important data packets
  • the minHARQ-Tx field is used to indicate that the terminal limits the maximum number of uplink retransmissions of non-critical data packets.
  • the terminal After receiving the first configuration indication information, the terminal configures the maximum number of uplink retransmissions corresponding to the important data packet according to the parameters carried in the maxHARQ-Tx field, and configures the non-essential data packet according to the parameters carried in the minHARQ-Tx field. The maximum number of retransmissions in the uplink.
  • the first configuration indication information does not carry the configuration parameter corresponding to each attribute, and after receiving the first configuration indication information, the terminal obtains the preset mapping table.
  • Table 2 lists only the first attribute, the second attribute, and the third attribute.
  • the attribute may include the first attribute, the second attribute, and the third attribute. a plurality of attributes, wherein the first attribute, the second attribute, and the third attribute are different in importance, for example, the importance of the first attribute is lower than the importance of the second attribute, and the importance of the second attribute is lower than the third The importance of the attribute; or the importance of the first attribute is higher than the importance of the second attribute, and the importance of the second attribute is higher than the importance of the third attribute.
  • the terminal may determine, according to the configuration parameter corresponding to each attribute, the configuration parameter corresponding to each attribute, for example, after receiving the first configuration indication information, the terminal may configure the first configuration parameter according to the second attribute of the data packet of the first attribute according to Table 2. Configure a second configuration parameter for the packet whose attribute is the second attribute.
  • the terminal may directly determine the configuration parameter of each data packet according to Table 2.
  • step S107 the embodiment of the present invention further includes step S107:
  • the terminal determines a configuration parameter of the data packet according to an attribute of the data packet.
  • the embodiment of the present invention can configure a large configuration parameter for the attribute with higher importance and a smaller configuration parameter for the attribute with lower importance.
  • the network is congested, it can ensure that the data packets with higher importance are transmitted reliably.
  • different data packets of different attributes in the same to-be-transmitted service may be sorted according to the order of importance from highest to lowest, and then corresponding data is configured for each data packet according to the configuration parameter corresponding to the attribute to which each data packet belongs. Configuration parameters.
  • the attribute is an important attribute or a non-important attribute.
  • the attribute may further include an important attribute or a non-important attribute.
  • the embodiment of the present invention does not limit this:
  • the configuration parameter is a hybrid automatic repeat request (HARQ parameter)
  • HARQ parameter a hybrid automatic repeat request
  • the terminal determines that the configuration parameter of the data packet is the first HARQ parameter or the second HARQ parameter, where the first HARQ parameter is a configuration parameter corresponding to the important attribute, and the second HARQ parameter is a configuration parameter corresponding to the non-important attribute, the first HARQ The value of the parameter is greater than the value of the second HARQ parameter.
  • the terminal when the attribute of the data packet is an important attribute, the terminal configures the first HARQ parameter for the data packet, and when the attribute of the data packet is a non-critical attribute, the terminal configures the second HARQ parameter for the data packet.
  • the transmission reliability of the data packet whose attribute is an important attribute can be guaranteed, and when the terminal determines that the uplink transmission reaches the HARQ parameter of the data packet whose attribute is a non-critical attribute (for example, In the case of the second HARQ parameter, if the data packet whose attribute is a non-critical attribute has not been correctly received, the terminal discards the data packet whose attribute is a non-critical attribute and does not retransmit. It can ensure that when the network is congested, the data packets whose attributes are non-essential attributes are avoided.
  • the to-be-transmitted service includes the first data packet and the second data packet, where the first data packet is a video I frame, and the second data packet is a video P-frame or a B-frame, for example, the terminal is an I-frame.
  • the first HARQ parameter is configured, for example, the first HARQ parameter is 5; the terminal configures the second HARQ parameter for the P frame or the B frame. For example, if the second HARQ parameter is 1, the terminal will be the I after the initial transmission of the I frame fails. The frame is retransmitted and retransmitted at most 5 times.
  • the terminal does not retransmit the I frame; the P frame or B frame transmits. After the failure, the terminal retransmits the P frame or the B frame, and retransmits at most one time. If the number of retransmissions of the P frame or the B frame reaches the second HARQ parameter, the P frame or the B frame still fails to retransmit. Then the terminal does not retransmit the P frame or the B frame.
  • the first HARQ parameter and the second HARQ parameter in the embodiment of the present invention may be set as needed.
  • the value of the first HARQ parameter should be set to be larger.
  • the value of the second HARQ parameter should be set as small as possible.
  • the second HARQ parameter can also be set to 0, that is, if the non-critical data packet fails to be transmitted, no retransmission is performed.
  • a discard timer (DT) is configured for each PDCP entity, and each discard timer corresponds to each of the discarding timers.
  • DT discard timer
  • the discarding timing length of the timer is configured by the eNodeB.
  • the configuration parameter is the discarding timing length.
  • Step S107 provided by the embodiment of the present invention may be implemented in the following manner:
  • the terminal determines that the configuration parameter of the data packet is the first discarding timing length or the second discarding timing length, where the first discarding timing length is a configuration parameter corresponding to the important attribute, and the second discarding timing length is a configuration parameter corresponding to the non-essential attribute.
  • the first discarding timing length is greater than the second discarding timing length.
  • the base station may configure, by using an RRC message, at least two discarding timers for the PDCP entity corresponding to the to-be-transmitted service of the terminal, and each discarding timer corresponds to a discarding timing length.
  • the embodiment of the present invention configures two discarding timers, that is, the first discarding timer corresponds to the first discarding timing length, and the second discarding timer corresponds to the second discarding timer length.
  • data packets with different attributes in the same to-be-transmitted service may be sorted in descending order of importance, and then a discard timer configured with a high-priority packet is configured to correspond to a longer discarding timing length, which is important.
  • a low packet configures a lower drop timer, corresponding to a shorter discard timing length.
  • the discarding timing length of the important attribute may be configured to be greater than the discarding timing length of the non-essential attribute, so as to ensure that the data corresponding to the non-essential attribute is used when the network is congested and the discarding timing length of the non-essential attribute is reached. Packets are discarded to ensure normal transmission of data packets corresponding to important attributes without loss of network transmission resources, thereby reducing the impact on transmission quality.
  • the terminal configures the first discarding timing length for the I frame, for example, the first discard.
  • the timing length is 50 seconds (S)
  • the terminal configures a second discarding timing length for the P frame or the B frame.
  • the second discarding timing length is 10 seconds.
  • the PDCP entity After receiving a PDCP Service Data Unit (SDU), the PDCP entity starts a timer corresponding to the attribute of the PDCP SDU according to the attributes of the PDCP SDU. For example, if the attribute of the PDCP SDU is an important attribute, the PDCP entity starts a timer corresponding to the important attribute.
  • the discarding timing length configured by the timer expires, the PDCP SDU and the corresponding PDCP PDU are discarded.
  • step S101 can be implemented in the following manner:
  • the media access control MAC entity of the terminal at the terminal the first indication information that is sent by the packet data aggregation protocol PDCP entity of the terminal to the MAC entity, where the first indication information is used to indicate the data packet received by the terminal Attributes.
  • the media access control MAC entity of the terminal receives the first indication information sent by the packet data aggregation protocol PDCP entity of the terminal, where the first indication information is used to indicate an attribute of the data packet received by the MAC entity at the current moment.
  • the terminal divides the to-be-transmitted service into a first data packet and a second data packet by using a protocol layer, and sends the first data packet and the second data packet to form an RTP packet through an RTP layer.
  • the terminal adds an IP header to the first data packet and the second data packet at the IP layer to distinguish the attributes of the first data packet and the second data packet by the TOS field in the IP header, for example,
  • the IP header of a data packet carries the first identifier information, where the first identifier information is used to indicate that the attribute of the first data packet is an important attribute, and the IP packet header of the second data packet carries the second identifier information, and the second The identification information is used to indicate that the attribute of the second data packet is a non-critical attribute.
  • the terminal transmits the first data packet and the second data packet carrying the IP packet header from the IP layer to the PDCP entity, and after receiving the first data packet and the second data packet carrying the IP packet header, the PDCP entity passes the first data packet and The first identifier information and the second identifier information in the IP packet header carried by the second data packet respectively determine the attribute of the first data packet and the attribute of the second data packet. After determining that the attribute of the first data packet is an important attribute, the terminal will The first data packet is buffered into the first buffer as shown in FIG. 2a, and the second data packet is buffered into the second buffer as shown in FIG. 2a, and the first data packet and the second data packet are not sent to RLC entity.
  • the PDCP entity After receiving the indication of the attribute of the data packet to be scheduled and the uplink grant (UL Grant), the PDCP entity sends the data in the corresponding buffer to the RLC.
  • the entity for example, the current time sent by the MAC entity needs to schedule a data packet whose attribute is an important attribute, and the PDCP entity sends the first data packet from the first buffer to the RLC entity, and then the RLC entity sends the first data packet to the MAC entity.
  • the PDCP entity sends the first indication information to the MAC entity to indicate that the attribute of the first data packet received by the MAC entity is an important attribute, so that the terminal can use the first HARQ parameter transmission for the first data packet.
  • step S101 can be implemented in the following manner:
  • S1011b The terminal determines an attribute of the data packet according to the RLC header of the data packet, where the RLC packet header carries an identifier that uniquely identifies the data packet attribute.
  • the multiple data packets are transmitted through the IP layer, and then the data packet carrying the IP packet header is generated and sent to the PDCP layer, where the IP packet header carries an indication.
  • the attribute of the data packet is the identification information of the important attribute or the non-important attribute; after receiving the IP packet, the PDCP layer obtains the attribute of the data packet according to the identification information of the IP packet header, and generates a data packet carrying the PDCP packet header, and sends the data packet to the RLC.
  • the PDCP packet header carries identifier information indicating that the attribute of the data packet is an important attribute or a non-essential attribute
  • the RLC entity after receiving the data packet sent by the PDCP entity, the RLC entity sends the data carrying the PDCP header according to the PDCP entity.
  • the identifier information in the packet is used to learn the attribute of the data packet carrying the PDCP packet header, and the data packet carrying the RLC packet header is generated and sent to the MAC entity, where the RLC packet header carries an attribute indicating that the data packet is an important attribute or Identification information for non-critical attributes.
  • the terminal MAC entity can determine the attributes of the data packet through the RLC header of the data packet.
  • step S101 can also be implemented in the following manner:
  • the terminal determines, by the terminal, an attribute of the data packet acquired by using the first logical channel as an important attribute.
  • S1012c The terminal determines, by the terminal, an attribute of the data packet acquired through the second logical channel as a non-critical attribute.
  • the method further includes the step S101: the terminal receives the second indication information that is sent by the base station, where the second indication information is used to indicate the data packet of the different attributes of the terminal and the logical channel used for transmitting the data packet. Correspondence relationship.
  • the second indication information carries an identifier of each logical channel, and a correspondence between an identifier and an attribute of each logical channel.
  • the second indication information is used to indicate that the first logical channel corresponds to the important attribute, and the second logical channel corresponds to the non-important attribute, and is used to indicate the attributes of the data packet transmitted by the UE on different logical channels.
  • the base station further includes: sending, to the terminal, second indication information, where the second indication information is used to indicate a correspondence between a data packet of different attributes of the terminal and a logical channel used for transmitting the data packet.
  • the method provided by the embodiment of the present invention further includes:
  • the terminal determines, according to the data volume of the data packet corresponding to the first attribute, the amount of uplink data to be sent, where the first attribute is any one of different attributes included in the service to be transmitted.
  • the terminal reports the amount of uplink data to be sent to the base station.
  • the terminal reports the amount of uplink data to be sent to the base station in the form of a buffer status report (BSR).
  • BSR buffer status report
  • the base station can know how many important data packets or non-essential data packets are to be sent at the current moment of the terminal.
  • step S108 can be implemented in the following manner:
  • the PDCP entity decides to schedule:
  • the PDCP entity After receiving the data packet included in the service to be transmitted, if the PDCP entity determines that the current scheduling attribute is the data packet of the first attribute, the data packet whose attribute is the first attribute is sent to the RLC entity, and the different attributes are excluded. Packets of the remaining attributes other than an attribute are cached in the PDCP entity for next transmission. Therefore, in the scenario in which the PDCP entity determines the scheduling, the amount of uplink data to be sent sent by the terminal to the base station is only the data amount of the data packet whose attribute is the first attribute obtained by the MAC entity from the RLC entity.
  • the MAC entity decides to schedule:
  • the PDCP entity After receiving a plurality of data packets included in the service to be transmitted, the PDCP entity caches the data packets whose attributes are important attributes and non-important attributes (for example, cached in the first buffer and the second buffer), and the PDCP entity passes through the layer. And sending, to the MAC entity, third indication information, where the third indication information is used to indicate the data volume of the data packet corresponding to each attribute in the different attributes.
  • the MAC entity determines to schedule the data packet of the first attribute, the data quantity of the data packet corresponding to the first attribute is obtained from the third indication information, and the data quantity of the data packet corresponding to the first attribute is reported to the base station in a BSR format. Waiting for resources allocated by the base station. After the terminal receives the resource allocated by the base station for the data packet corresponding to the first attribute, the MAC entity of the terminal sends the fourth indication information to the PDCP entity, where the fourth indication information is used to instruct the PDCP layer to send the data packet corresponding to the first attribute. To the RLC entity.
  • the terminal may further send, to the base station, fifth indication information, where the fifth indication information is used to indicate whether the uplink data volume to be sent is an uplink data volume of an important attribute or The amount of upstream data for non-critical attributes.
  • the terminal may use the 1-bit reserved field in the MAC header to indicate whether the BSR reports the uplink data volume of the important attribute or the non-critical attribute.
  • the MAC entity determines the scheduling of the current time.
  • the PDCP entity after receiving the data packet from the IP layer, the PDCP entity separately buffers the received different attribute data packets. In different buffers. For example, the data packet whose attribute is an important attribute is cached in the first buffer, and the data packet whose attribute is a non-critical attribute is cached in the second buffer, and the MAC entity sends an indication information to the PDCP entity through the cross layer to request the information. The amount of data to be sent upstream.
  • the PDCP entity After receiving the indication information, the PDCP entity sends an indication information (ie, third indication information) to the MAC entity by using the cross-layer, where the third indication information carries the data volume of the data packet corresponding to the important attribute and the non-critical attribute. The amount of data in the packet.
  • the MAC entity determines the data packet corresponding to the important attribute in the third indication information, and reports the data volume of the data packet corresponding to the important attribute in the third indication information through the buffer status report (BSR) reporting manner.
  • BSR buffer status report
  • the base station may send a UL grant to the terminal.
  • the terminal MAC entity After receiving the UL grant of the base station, the terminal MAC entity sends a sixth indication information carrying the UL grant information and the requested data packet attribute to the PDCP entity. If the request attribute is an important attribute in the sixth indication information, in the terminal structure shown in FIG. 2a, the PDCP entity sends the data packet buffered in the first buffer to the data packet as shown in FIG. 2a according to the sixth indication information.
  • the PDCP entity determines, according to the sixth indication information, that the non-essential data packet buffered in the second buffer is sent to the device as shown in FIG. 2a.
  • the PDCP entity sends the buffered important data packet in the first buffer according to the sixth indication information.
  • the PDCP entity determines, according to the sixth indication information, the non-cache buffered in the second buffer. The important data packet is sent to the second RLC entity as shown in Figure 2e.
  • the PDCP entity determines, according to the sixth indication information, the first buffer in the first PDCP entity.
  • the data packet is sent to the RLC entity as shown in FIG. 2f.
  • the terminal determines, according to the sixth indication information, that the second buffer of the second PDCP entity is The data packet is sent to the RLC entity as shown in Figure 2e.
  • the PDCP entity determines the scheduling at the current time.
  • the PDCP entity schedules an important data packet
  • the important data packet is pushed from the first buffer to the RLC entity, otherwise the non-critical data packet is pushed to the RLC entity.
  • the terminal structure shown in FIG. 2e if the PDCP entity decides to schedule an important data packet, the important data packet is pushed from the first buffer to the first RLC entity, otherwise the non-critical data packet is pushed to the second RLC entity.
  • the important data packet is pushed from the first buffer of the first PDCP entity to the RLC entity, otherwise the non-critical data packet is sent from the second PDCP.
  • the second buffer in the entity is pushed to the second RLC entity.
  • the MAC entity of the terminal may obtain, from the first RLC entity, the uplink data amount of the data packet corresponding to the important attribute of the first RLC entity, and The second RLC entity sends a request to determine the amount of uplink data mapped to the data packet corresponding to the non-critical attribute in the second RLC entity.
  • step S102 in the embodiment of the present invention may be implemented in the following manner:
  • the MAC entity of the terminal determines that the attribute of the first data packet is an important attribute, when the first data packet transmission fails, the first data packet is retransmitted with the first HARQ parameter.
  • the terminal may determine that the first data packet transmission fails by:
  • the terminal sends the first data packet to the base station
  • the terminal receives the first response message sent by the base station (for example, the NACK response sent by the base station to the terminal through the PUCCH).
  • the terminal determines that the first data packet transmission fails. For example, if the terminal determines that the received first response message carries a NACK, it indicates that the first data packet transmission is unsuccessful and needs to be retransmitted.
  • the terminal determines that the first response message sent by the base station is not received within the preset time, the terminal determines that the first data packet transmission fails.
  • the preset time can be set as needed, which is not limited in this embodiment of the present invention.
  • the MAC entity of the terminal determines that the attribute of the second data packet is a non-critical attribute, when the second data packet transmission fails, the second data packet is retransmitted with the second HARQ parameter.
  • the terminal identifies, according to the data packet carrying the RLC packet header, the attribute of the received data packet as an important attribute or a non-essential attribute, and if it is an important attribute, transmits the data packet by using a configuration parameter corresponding to the important attribute (ie, the first HARQ parameter). If it is a non-essential attribute, the data packet is transmitted by using the configuration parameter corresponding to the non-important attribute (ie, the second HARQ parameter).
  • step S102 in the embodiment of the present invention may be implemented in the following manner:
  • S1021b If the PDCP entity of the terminal determines that the attribute of the first data packet is an important attribute, the first data packet is discarded when the length of the discard timer corresponding to the first data packet reaches the discarding timing length.
  • the method provided by the embodiment of the present invention further includes:
  • S110 The terminal processes the transmission service to obtain multiple data packets with different attributes.
  • step S103 in the embodiment of the present invention is similar to the step S101.
  • step S104 is similar to the step S102, and details are not described herein again.
  • FIG. 7 is a structural diagram of another data transmission method according to an embodiment of the present invention.
  • the first terminal uses a source base station to perform multiple different attributes.
  • the data packet is sent to the second terminal.
  • the second terminal may receive, by the packet data network gateway, the serving gateway, and the target base station, a plurality of data packets of different attributes sent by the source base station.
  • the data transmission method includes:
  • the first terminal processes the service to obtain a plurality of data packets with different attributes, and an attribute of the data packet is used to indicate the importance of the data packet.
  • the first terminal processes the to-be-transmitted service through the H.264 standard in the coding layer to obtain multiple data packets with different attributes. Then, the data packets with different attributes are respectively passed through the RTP layer to form an RTP data packet, and then sent to the IP layer, and the terminal adds an IP packet header to the data packets with different attributes at the IP layer to utilize the 1 bit information in the IP packet header.
  • the terminal can indicate the attributes of each data packet according to the 1-bit information in the TOS field by extending the TOS field in the IP header.
  • the first terminal sends, by the source base station, a plurality of data packets with different attributes to the PGW, where the PGW is a gateway accessed by the second terminal.
  • the gateway accessed by the second terminal and the gateway accessed by the first terminal may be the same gateway. Even the base stations to which the first terminal and the second terminal are connected are also the same base station.
  • S903 The PGW maps each of the data packets with different attributes to an EPS bearer, where the data packets of different attributes correspond to different EPS bearers.
  • the bearer refers to a bearer channel that carries packet data between the second terminal and the core network serving the second terminal during the communication session. Specifically, it can be carried as an EPS.
  • the PGW maps the data packets of the important attributes to the first bearer, and transmits the non-critical attributes. Packet mapping to the second bearer for transmission
  • the PGW transmits the data packets that are mapped to different bearers on different bearers to the target base station by using the SGW.
  • the target base station is a base station serving the second terminal.
  • the target base station sends, by the target base station, multiple data packets with different attributes received on different bearers to the second terminal.
  • the second terminal receives multiple data packets with different attributes on different EPS bearers, and synchronizes (reorders) data packets with different attributes according to a timestamp field on each data packet.
  • the solution provided by the embodiment of the present invention is mainly introduced from the perspective of a terminal and a base station.
  • the terminal and the base station and the like include hardware structures and/or software modules corresponding to the execution of the respective functions.
  • the embodiments of the present invention can be implemented in a combination of hardware or hardware and computer software in combination with the elements and algorithm steps of the various examples described in the embodiments disclosed herein. Whether a function is implemented in hardware or computer software to drive hardware depends on the specific application and design constraints of the solution. A person skilled in the art can use different methods for implementing the described functions for each particular application, but such implementation should not be considered to be beyond the scope of the present invention.
  • the embodiments of the present invention may divide the function modules of the terminal, the base station, and the like according to the foregoing method.
  • each function module may be divided according to each function, or two or more functions may be integrated into one processing module.
  • the above integrated modules can be implemented in the form of hardware or in the form of software functional modules. It should be noted that the division of the module in the embodiment of the present invention is schematic, and is only a logical function division, and the actual implementation may have another division manner.
  • FIG. 9a shows a possible structural diagram of the terminal involved in the foregoing embodiment, and the terminal 1 includes a determining unit 10 and a transmitting unit 11 in the case of dividing the respective functional modules by corresponding functions.
  • the determining unit 10 is configured to support the terminal 1 to perform the process S101 (specifically, steps S1011b, S1011c, S1012c), S107 (specifically, may be steps S1071a and S1071b), S108 described in the foregoing embodiment;
  • the support terminal 1 executes the step S102 described in the above embodiment (specifically, it may be steps S1021a, S1022a, S1021b, S1022b).
  • the terminal 1 provided by the embodiment of the present invention may further include a sending unit 12 for supporting the terminal 1 to perform the step S109 in the foregoing embodiment, where the first receiving unit 13 is configured to support the terminal to perform the steps S1011a and the second in the foregoing embodiment.
  • the receiving unit 14 is configured to support the terminal 1 to perform steps S106 and S101a in the above embodiment, and the terminal 1 may further include a processing unit 15 for supporting the terminal 1 to perform step S110 in the above embodiment. All the related content of the steps involved in the foregoing method embodiments may be referred to the functional descriptions of the corresponding functional modules, and details are not described herein again.
  • the above determining unit 10, transmission unit 11, transmitting unit 12 and first receiving unit 13 can be integrated in the MAC of the terminal as shown in Figures 2a, 2d, 2e, and 2f.
  • the first receiving unit 13 and the second receiving unit 14 may be receivers, and the transmitting unit 12 may be a transmitter, which may be integrated with the receiver to form a transceiver.
  • the determining unit 10 and the transmitting unit 11 may be embedded in hardware or in a memory independent of the terminal, so that the processor of the terminal invokes the operations corresponding to the above respective units.
  • FIG. 9b shows a possible structural diagram of the terminal involved in the above embodiment.
  • the terminal 1 includes a processing module 102 and a communication module 103.
  • the processing module 102 is configured to control and control the action of the terminal 1.
  • the processing module 102 is configured to support the terminal 1 to perform the step S101 described in the embodiment (specifically, steps S1011a, S1011b, S1011c, S1012c), S101a, S107 (specifically, may be steps S1071a and S1071b), S108, S102 (specifically, may be steps S1021a, S1022a, S1021b, S1022b), S106, S109, and S110, and/or other techniques for the techniques described herein process.
  • the communication module 103 is configured to support the communication between the terminal 1 and other network entities, for example, the support terminal 1 communicates with the base station, and the terminal 1 may further include a storage module 101 for storing the program code and data of the terminal 1.
  • the processing module 102 can be a processor or a controller, for example, a central processing unit (CPU), a general-purpose processor, a digital signal processor (DSP), and an application-specific integrated circuit (Application-Specific Integrated Circuit (ASIC), Field Programmable Gate Array (FPGA) or other programmable logic device, transistor logic device, hardware component, or any combination thereof. It is possible to implement or carry out the various illustrative logical blocks, modules and circuits described in connection with the present disclosure.
  • the processor may also be a combination of computing functions, for example, including one or more microprocessor combinations, a combination of a DSP and a microprocessor, and the like.
  • the communication module 103 can be a transceiver, a transceiver circuit or a communication interface 1013, and the like.
  • the storage module 101 can be a memory.
  • the terminal 1 When the processing module 102 is the processor 1012, the communication module 103 is the communication interface 1013, and the storage module 101 is the memory, the terminal 1 according to the embodiment of the present invention may be the terminal shown in FIG. 9c.
  • the terminal 1 includes a processor 1012, a communication interface 1013, a memory 1011, and a bus 1014.
  • the communication interface 1013, the processor 1012, and the memory 1011 are connected to each other through a bus 1014.
  • the bus 1014 may be a Peripheral Component Interconnect (PCI) bus or an Extended Industry Standard Architecture (EISA) bus. Wait.
  • PCI Peripheral Component Interconnect
  • EISA Extended Industry Standard Architecture
  • Wait The bus can be divided into an address bus, a data bus, a control bus, and the like. For ease of representation, only one thick line is shown in Figure 9c, but it does not mean that there is only one bus or one type of bus.
  • FIG. 10a shows a possible structural diagram of a base station involved in the foregoing embodiment
  • the base station 2 includes a determining unit 20 and a transmitting unit 21 in the case of dividing the respective functional modules by corresponding functions.
  • the determining unit 20 is configured to support the base station 2 to perform the process S103 described in the foregoing embodiment
  • the transmitting unit 21 is configured to support the base station 2 to perform the step S104 described in the foregoing embodiment.
  • the base station 2 provided by the embodiment of the present invention may further include a sending unit 22 for supporting the base station 2 to perform step S105 in the foregoing embodiment. All the related content of the steps involved in the foregoing method embodiments may be referred to the functional descriptions of the corresponding functional modules, and details are not described herein again.
  • the above determining unit 20, the transmitting unit 21, and the transmitting unit 22 may be integrated on the MAC entity of the base station, and on the other hand, the determining unit 20 and the transmitting unit 21 may be in hardware form. Embedded in or independent of the memory of the base station, so that the processor of the base station invokes the operations corresponding to the above units.
  • Fig. 10b shows a possible structural diagram of the base station involved in the above embodiment.
  • the base station 2 includes a processing module 202 and a communication module 203.
  • the processing module 202 is configured to control and manage the actions of the base station 2, for example, the processing module 202 is configured to support the base station 2 to perform steps S103, S104, and S105 described in the embodiments, and/or other techniques for the techniques described herein. process.
  • the communication module 203 is configured to support the communication between the base station 2 and other network entities, for example, to support the base station 2 to communicate with the terminal, and the base station 2 may further include a storage module 201 for storing the program code and data of the base station 2.
  • the processing module 202 can be a processor or a controller, for example, a central processing unit (CPU), a general-purpose processor, a digital signal processor (DSP), and an application-specific integrated circuit (Application-Specific). Integrated Circuit (ASIC), Field Programmable Gate Array (FPGA) or other programmable logic device, transistor logic device, hardware component, or any combination thereof. It is possible to implement or carry out the various illustrative logical blocks, modules and circuits described in connection with the present disclosure.
  • the processor may also be a combination of computing functions, for example, including one or more microprocessor combinations, a combination of a DSP and a microprocessor, and the like.
  • the communication module 203 can be a transceiver, a transceiver circuit or a communication interface 2013, and the like.
  • the storage module 201 can be a memory.
  • the base station 2 involved in the embodiment of the present invention may be the base station shown in FIG. 10c.
  • the base station 2 includes a processor 2012, a communication interface 2013, a memory 2011, and a bus 2014.
  • the communication interface 2013, the processor 2012, and the memory 2011 are connected to each other through a bus 2014;
  • the bus 2014 may be a Peripheral Component Interconnect (PCI) bus or an Extended Industry Standard Architecture (EISA) bus. Wait.
  • PCI Peripheral Component Interconnect
  • EISA Extended Industry Standard Architecture
  • the bus can be divided into an address bus, a data bus, a control bus, and the like. For ease of representation, only one thick line is shown in Figure 10c, but it does not mean that there is only one bus or one type of bus.
  • an embodiment of the present invention provides a computer readable storage medium.
  • the computer readable storage medium stores instructions.
  • the base station is configured to perform steps S103 and S104 in the foregoing embodiment. And S105.
  • an embodiment of the present invention provides a computer readable storage medium, where the computer readable storage medium stores instructions, and when the computer readable storage medium is run on a computer, causes the terminal to perform step S101 in the foregoing embodiment.
  • a computer program product includes one or more computer instructions.
  • the computer can be a general purpose computer, a special purpose computer, a computer network, or other programmable device.
  • the computer instructions can be stored in a computer readable storage medium or transferred from one computer readable storage medium to another computer readable storage medium, for example, computer instructions can be wired from a website site, computer, server or data center (eg, , coaxial cable, fiber optic, digital subscriber line (DSL) or wireless (eg, infrared, wireless, microwave, etc.) to another website site, computer, server or data center.
  • the computer readable storage medium can be any available media that can be read by a computer or a data storage device such as a server, data center, or the like that includes one or more available media.
  • the usable medium may be a magnetic medium (for example, a floppy disk, a hard disk, a magnetic tape), an optical medium (for example, a DVD), or a semiconductor medium (for example, a solid state hard disk (SSD)) or the like.
  • a magnetic medium for example, a floppy disk, a hard disk, a magnetic tape
  • an optical medium for example, a DVD
  • a semiconductor medium for example, a solid state hard disk (SSD)
  • the disclosed system, apparatus, and method may be implemented in other manners.
  • the device embodiments described above are merely illustrative.
  • the division of the modules or units is only a logical function division.
  • there may be another division manner for example, multiple units or components may be used. Combinations can be integrated into another system, or some features can be ignored or not executed.
  • the mutual coupling or direct coupling or communication connection shown or discussed may be an indirect coupling or communication connection through some interface, device or unit, and may be in an electrical, mechanical or other form.
  • the units described as separate components may or may not be physically separated, and the components displayed as units may or may not be physical units, that is, may be located in one place, or may be distributed to multiple network units. Some or all of the units may be selected according to actual needs to achieve the purpose of the solution of the embodiment.
  • each functional unit in each embodiment of the present application may be integrated into one processing unit, or each unit may exist physically separately, or two or more units may be integrated into one unit.
  • the above integrated unit can be implemented in the form of hardware or in the form of a software functional unit.
  • the integrated unit if implemented in the form of a software functional unit and sold or used as a standalone product, may be stored in a computer readable storage medium.
  • a computer readable storage medium A number of instructions are included to cause a computer device (which may be a personal computer, server, or network device, etc.) or processor to perform all or part of the steps of the methods described in various embodiments of the present application.
  • the foregoing storage medium includes: a flash memory, a mobile hard disk, a read only memory, a random access memory, a magnetic disk, or an optical disk, and the like, which can store program codes.

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Quality & Reliability (AREA)
  • Computer Security & Cryptography (AREA)
  • Databases & Information Systems (AREA)
  • Mobile Radio Communication Systems (AREA)
  • Detection And Prevention Of Errors In Transmission (AREA)

Abstract

本发明实施例提供一种数据传输方法、通信设备、终端和基站，涉及数据传输领域，用以通过对重要性不同的数据包配置不同的配置参数，以实现对重要数据包的优先保障，包括：通信设备确定待传输数据包的属性，数据包的属性用于指示数据包的重要性；通信设备采用数据包的属性对应的配置参数传输数据包。本发明实施例应用于数据传输场景中。

Description

一种数据传输方法、通信设备、终端和基站
本申请要求于2017年02月10日提交中国专利局、申请号为201710074932.4、申请名称为“一种数据传输方法、通信设备、终端和基站”的中国专利申请的优先权，其全部内容通过引用结合在本申请中。
技术领域
本发明实施例涉及通信领域，尤其涉及一种数据传输方法、通信设备、终端和基站。
背景技术
视频编码标准中的可解码数据帧类型可分为帧内编码帧(I-Frame，intra coded frames，I帧)、单向预测编码帧(P-Frame，predicted frames，P帧)和双向预测编码帧(B-Frame，Bi-directional predicted frames，B帧)。
其中，I帧是一个完整的画面，而P帧和B帧记录的是P帧和B帧相对于I帧的变化。I帧具有截断误差传播的作用，P帧往往会作为其他帧间编码帧的参考帧，其作用次于I帧。由于B帧通常不作为参考帧，因此其丢失对视频解码质量影响较小。如果在传输过程中I帧出错，则P帧和B帧就无法解码。因此，在视频传输应用中区分数据流的不同帧类型有非常重要的意义。
但是，目前的传输调度策略中对所有视频帧(例如，I帧、P帧和B帧)均采用同一个配置参数传输。这样，在网络拥塞情况下，在作为解码基础的I帧一旦丢失下，便会导致P帧和B帧无法完成解码，形成无效传输，严重影响视频质量。
发明内容
本发明实施例提供一种数据传输方法、通信设备、终端和基站，用以提高重要性较高的传输数据包的可靠性，从而减少了由于网络拥塞能情况的发生导致的对待传输业务传输质量的影响。
为达到上述目的，本发明的实施例采用如下技术方案：
第一方面，本发明实施例提供一种数据传输方法，包括：通信设备确定待传输数据包的属性，该数据包的属性用于指示数据包的重要性，通信设备采用数据包的属性对应的配置参数传输数据包。
本发明实施例提供一种数据传输方法，通过确定待传输数据包的属性，然后采用数据包的属性对应的配置参数对数据包传输。这样，若数据包的属性不同，则对数据包传输时所采用的配置参数也不同，与现有技术中将同一待传输业务的每个数据包采用相同的配置参数传输相比，本发明实施例通过按照属性对待传输业务包括的数据包采用与每个数据包对应的配置参数传输，这样不同属性的数据包对应不同的配置参数，能够将属性不同的数据包区分对待，以提高重要性较高的传输数据包的可靠性，从而减少了由于网络拥塞能情况的发生导致的对待传输业务传输质量的影响。
结合第一方面，在第一方面的第一种可能的实现方式中，通信设备采用数据包的 属性对应的配置参数传输数据包之前，本发明实施例提供的方法还包括：通信设备根据数据包的属性，确定数据包的配置参数。
结合第一方面或第一方面的第一种可能的实现方式，在第一方面的第二种可能的实现方式中，属性为重要属性或非重要属性，配置参数为混合自动重传请求HARQ参数，则通信设备根据数据包的属性，确定数据包的配置参数，包括：通信设备确定数据包的配置参数为第一HARQ参数或者第二HARQ参数，其中，第一HARQ参数为重要属性对应的配置参数，第二HARQ参数与非重要属性对应的配置参数，第一HARQ参数的值大于第二HARQ参数的值；配置参数为丢弃定时长度，则通信设备根据数据包的属性，确定数据包的配置参数，包括：通信设备确定数据包的配置参数为第一丢弃定时长度或第二丢弃定时长度，其中，第一丢弃定时长度为重要属性对应的配置参数，第二丢弃定时长度为非重要属性对应的配置参数，第一丢弃定时长度大于第二丢弃定时长度。通过对属性不同的数据包配置不同的HARQ参数(如，第一HARQ参数和第二HARQ参数)，这样在不同属性的数据包传输失败后，可以对重要属性的数据包多传输几次，以保证重要属性的数据包尽可能的成功传输。另一方面，对属性不同的数据包配置不同的丢弃定时长度(如，第一丢弃定时长度和第二丢弃定时长度)，这样在不同属性的数据包达到各自的丢弃定时长度时，由于重要属性对应的第二丢弃定时长度大于非重要属性对应的第一丢弃定时长度，这样能够在网络资源不变的情况下，将非重要属性的数据包即使丢弃，以避免非重要属性的数据包占据太多网络资源，从而保障了重要属性的数据包的可靠传输。
结合第一方面至第一方面的第二种可能的实现方式中任意一项，在第一方面的第三种可能的实现方式中，通信设备确定待传输数据包的属性，包括：通信设备通过媒体访问控制MAC实体，接收通信设备的分组数据聚合协议PDCP实体向MAC实体发送的用于指示终端接收到的数据包的属性的第一指示信息；通信设备根据第一指示信息，确定数据包的属性；或者，通信设备根据数据包的无线链路控制RLC包头，确定数据包的属性，其中，RLC包头中携带有唯一标识数据包属性的标识。
结合第一方面至第一方面的第三种可能的实现方式中任意一项，在第一方面的第四种可能的实现方式中，通信设备确定待传输数据包的属性，包括：通信设备将通过第一逻辑信道获取的数据包的属性确定为重要属性，以及将通过第二逻辑信道获取的数据包的属性确定为非重要属性。
结合第一方面至第一方面的第四种可能的实现方式中任意一项，在第一方面的第五种可能的实现方式中，通信设备为终端，通信设备确定待传输数据包的属性之前，本发明实施例提供的方法还包括：终端接收基站发送的用于指示不同属性的数据包和用于传输该数据包的逻辑信道之间的对应关系的第二指示信息。这样终端在通过第一逻辑信道接收到数据包时，便可以确定该数据包的属性为重要属性，通过第二逻辑信道接收到数据包时，便可以确定该数据包的属性为非重要属性。
结合第一方面至第一方面的第五种可能的实现方式中任意一项，在第一方面的第六种可能的实现方式中，通信设备根据数据包的属性，确定数据包的配置参数之前，本发明实施例提供的方法还包括：终端接收基站发送的用于指示终端为不同属性的数据包配置不同的配置参数的第一配置指示信息。
结合第一方面至第一方面的第六种可能的实现方式中任意一项，在第一方面的第七种可能的实现方式中，通信设备为基站，本发明实施例提供的方法还包括：基站向终端发送用于指示所述终端为不同属性的数据包配置不同的配置参数的第一配置指示信息。
第二方面，本发明实施例提供一种通信设备，包括：确定单元，用于确定待传输数据包的属性，数据包的属性用于指示该数据包的重要性；传输单元，用于采用该数据包的属性对应的配置参数传输数据包。
结合第二方面，在第二方面的第一种可能的实现方式中，确定单元还用于：根据数据包的属性，确定数据包的配置参数。
结合第二方面或第二方面的第一种可能的实现方式，在第二方面的第二种可能的实现方式中，属性为重要属性或非重要属性，配置参数为混合自动重传请求HARQ参数，则确定单元具体用于：确定数据包的配置参数为第一HARQ参数或者第二HARQ参数，其中，第一HARQ参数为重要属性对应的配置参数，第二HARQ参数与非重要属性对应的配置参数，第一HARQ参数的值大于第二HARQ参数的值；配置参数为丢弃定时长度，则确定单元还具体用于：确定数据包的配置参数为第一丢弃定时长度或第二丢弃定时长度，其中，第一丢弃定时长度为重要属性对应的配置参数，第二丢弃定时长度为非重要属性对应的配置参数，第一丢弃定时长度大于第二丢弃定时长度。
结合第二方面至第二方面的第二种可能的实现方式中任意一项，在第二方面的第三种可能的实现方式中，通信设备包括：第一接收单元，用于通过通信设备的MAC实体，接收通信设备的PDCP实体向MAC实体发送的指示终端接收到的数据包的属性的第一指示信息；确定单元还具体用于：根据第一指示信息，确定数据包的属性；或者，确定单元还具体用于：根据数据包的RLC包头，确定数据包的属性，其中，RLC包头中携带有唯一标识述数据包属性的标识。
结合第二方面至第二方面的第三种可能的实现方式中任意一项，在第二方面的第四种可能的实现方式中，确定单元，具体用于将通过第一逻辑信道获取的数据包的属性确定为重要属性；以及用于将通过第二逻辑信道获取的数据包的属性确定为非重要属性。
结合第二方面至第二方面的第四种可能的实现方式中任意一项，在第二方面的第五种可能的实现方式中，通信设备还包括：第二接收单元，用于接收基站发送的用于指示不同属性的数据包和用于传输该数据包的逻辑信道之间的对应关系的第二指示信息。
结合第二方面至第二方面的第五种可能的实现方式中任意一项，在第二方面的第六种可能的实现方式中，通信设备还包括：第二接收单元，用于接收基站发送的用于指示终端为不同属性的数据包配置不同的配置参数的第一配置指示信息。
结合第二方面至第二方面的第六种可能的实现方式中任意一项，在第二方面的第七种可能的实现方式中，基站还包括：发送单元，用于向终端发送用于指示终端为不同属性的数据包配置不同的配置参数的第一配置指示信息。
第三方面，本发明实施例提供一种终端，该终端包括处理器、存储器、***总线和通信接口；其中，存储器用于存储计算机执行指令，处理器与存储器通过所述*** 总线连接，当终端运行时，处理器执行存储器存储的计算机执行指令，以使终端执行如第一方面至第一方面的第一方面的第六种可能的实现方式中任意一种可能的实现方式所描述的数据传输方法。
第四方面，本发明实施例提供一种基站，该基站包括处理器、存储器、***总线和通信接口；其中，存储器用于存储计算机执行指令，处理器与存储器通过***总线连接，当基站运行时，处理器执行存储器存储的计算机执行指令，以使基站执行如第一方面至第一方面的第四种可能的实现方式中任意一项以及第一方面的第七种可能的实现方式所描述的数据传输方法。
第五方面，本发明实施例提供一种计算机可读存储介质，计算机可读存储介质中存储有指令，当计算机可读存储介质在计算机上运行时，使得终端执行如第一方面至第一方面的第一方面的第六种可能的实现方式中任意一种可能的实现方式所描述的数据传输方法的指令。
第六方面，本发明实施例提供一种计算机可读存储介质，计算机可读存储介质中存储有指令，当计算机可读存储介质在计算机上运行时，使得基站执行如第一方面至第一方面的第四种可能的实现方式中任意一项以及第一方面的第七种可能的实现方式所描述的数据传输方法的指令。
第七方面，本发明实施例提供一种包括指令的计算机程序产品，当其在基站上运行时，使得基站执行如第一方面至第一方面的第四种可能的实现方式中任意一项以及第一方面的第七种可能的实现方式所描述的数据传输方法的方法。
第八方面，本发明实施例提供一种包括指令的计算机程序产品，当其在终端上运行时，使得终端执行如第一方面至第一方面的第一方面的第六种可能的实现方式中任意一种可能的实现方式所描述的数据传输方法的方法。
第九方面，本发明实施例提供一种芯片***，应用于基站中，芯片***包括至少一个处理器和接口电路，所述接口电路和所述至少一个处理器通过线路互联，所述处理器用于运行指令，以执行如第一方面至第一方面的第四种可能的实现方式中任意一项以及第一方面的第七种可能的实现方式所描述的数据传输方法的方法。
第十方面，本发明实施例提供一种芯片***，应用于终端中，芯片***包括至少一个处理器和接口电路，所述接口电路和所述至少一个处理器通过线路互联，所述处理器用于运行指令，以执行如第一方面至第一方面的第一方面的第六种可能的实现方式中任意一种可能的实现方式所描述的数据传输方法的方法。
本发明实施例还提供一种通信***，该通信***包括第三方面至第三方面任意一种可能的实现方式所描述的终端，以及第四方面或第四方面任意一种可能的实现方式所描述的基站。
可以理解地，上述提供的任一种终端、基站或计算机存储介质均用于执行上文所提供的对应的数据传输方法，因此，其所能达到的有益效果可参考上文所提供的对应的方法中的有益效果，此处不再赘述。
附图说明
图1a为本发明实施例提供的一种通信***架构图；
图1b为本发明实施例提供的另一种通信***架构图；
图2a为本发明实施例提供的一种终端的结构示意图一；
图2b为本发明实施例提供的一种NALU结构示意图一；
图2c为本发明实施例提供的一种NALU结构示意图二；
图2d为本发明实施例提供的一种NALU结构示意图三；
图2e为本发明实施例提供的一种终端的结构示意图二；
图2f为本发明实施例提供的一种终端的结构示意图三；
图2g为本发明实施例提供的一种基站的结构示意图二；
图2h为本发明实施例提供的一种基站的结构示意图三；
图3为本发明实施例提供的一种数据传输方法的流程示意图一；
图4为本发明实施例提供的一种数据传输方法的流程示意图二；
图5为本发明实施例提供的一种数据传输方法的流程示意图三；
图6为本发明实施例提供的一种数据传输方法的流程示意图四；
图7为本发明实施例提供的另一种传输架构示意图；
图8为本发明实施例提供的一种数据传输方法的流程示意图五；
图9a为本发明实施例提供的一种终端的又一种结构示意图；
图9b为本发明实施例提供的一种终端的另一种结构示意图；
图9c为本发明实施例提供的一种终端的再一种结构示意图；
图10a为本发明实施例提供的一种终端的又一种结构示意图；
图10b为本发明实施例提供的一种终端的另一种结构示意图；
图10c为本发明实施例提供的一种终端的再一种结构示意图。
具体实施方式
下面结合附图，对本发明实施例进行描述。
为了便于清楚描述本发明实施例的技术方案，在本发明的实施例中，采用了“第一”、“第二”等字样对功能和作用基本相同的相同项或相似项进行区分，本领域技术人员可以理解“第一”、“第二”等字样并不对数量和执行次序构成限定。
本发明实施例中的最大混合自动重传请求(Hybrid Automatic Repeat reQuest，HARQ)参数为上行最大重传次数，用于限定终端上行数据重传的最大次数。
本发明实施例中的丢弃时长度为PDCP SDU对应的丢弃定时器的长度，PDCP实体每收到一个PDCP SDU后，将启动一个该PDCP SDU对应的定时器，当该定时器超时，则PDCP实体将该PDCP SDU以及对应的PDCP PDU丢弃。
终端向基站发送的待传输业务中可能包括多个属性不同的数据包(以视频传输业务为例说明)，终端一般会将视频传输业务中连续若干幅图像编码为I帧、P帧和B帧三种帧类型。
其中，I帧采用帧内预测编码，自身可以通过视频解压算法解压成一张单独的完整图像，即解码I帧时不需要参考其他帧数据即可独立解码。I帧是通过尽可能去除图像空间冗余信息来压缩的。
P帧通过充分降低与图像序列中前面已编码帧的时间冗余信息来压缩传输数据量的编码图像，也叫预测帧。P帧由在它前面的P帧或者I帧预测得到，P帧根据本帧与邻近的前一帧或者几帧的不同点来压缩本帧数据。P帧属于前向预测的帧间编码。P 帧只参考位于P帧之前且与P帧靠近的I帧或P帧。
B帧也可以称为双向预测帧，当把一帧图像压缩成B帧时，B帧根据该B帧邻近的前几帧、本帧以及后几帧数据的不同点来压缩该B帧。也即仅记录该B帧和与该B帧相邻的前后几帧的差值。
综上所述，采用B帧压缩图像，才能达到超高的压缩比。一般地，I帧压缩效率最低，P帧较高，B帧最高。简单的讲，I帧是一个完整的画面，而P帧和B帧记录的是相对于I帧的变化，没有I帧，P帧和B帧可能就无法解码。因此，通信设备在传输视频传输业务时，可以将I帧作为视频传输业务中的属性为重要属性的数据包(可称之为：重要数据包)，将P帧和B帧作为视频传输业务中属性为非重要属性的数据包(可称之为：非重要数据包)。
而现有技术中，终端在向基站进行上行传输时，采用非自适应重传，即通常为同一个待传输业务中的不同属性的数据包采用同一个配置参数。
一方面，终端通过无线资源控制(radio resource control，RRC)消息接收基站为终端配置的HARQ参数，即：最大上行重传参数。这样，终端将对待传输业务按照配置的最大混合自动重传请求向基站传输。终端在该待传输业务传输失败时，则终端以该待传输业务对应的最大混合自动重传请求对该待传输业务传输。终端在该待传输业务达到最大混合自动重传请求时，且该待传输业务依旧传输失败时，则终端将丢弃该待传输业务。
另一方面，基站为终端的每个待传输业务对应的丢弃定时器(Discard timer，DT)配置一个丢弃定时时长。这样，终端每收到一个PDCP SDU后，终端将启动该待传输业务对应的丢弃定时器。终端在确定该待传输业务对应的丢弃定时器超过该丢弃定时器所配置的丢弃定时时长时，则终端将该PDCP SDU以及对应的PDCP PDU丢弃。
综上所述，上述方法对终端上传的同一待传输业务的所有数据包均采用相同的配置参数。因此，同一待传输业务中包括的多个重要性不同的数据包也是采用相同的配置参数，即重要数据包和非重要数据包对应相同的上行最大重传次数或者对应相同的丢弃定时器。这样，在网络拥塞时，由于重要数据包和非重要数据包没有区分对待，一旦重要数据包传输失败，(例如，若在传输过程中I帧传输失败，则导致P帧和B帧就无法解码)从而影响整个待传输业务的传输质量。
本发明实施例通过对待传输业务包括的多个数据包按照重要性区分，并为不同属性的数据包配置不同的配置参数，这样，能够使得当同一待传输业务包括多个属性不同的数据包时，使得不同属性对应的数据包以不同的配置参数传输，从而尽可能避免重要数据包传输失败的情况发生，从而减少了对待传输业务传输质量的影响。
应理解，本发明实施例的技术方案可以应用于各种通信***，例如：全球移动通讯(global system of mobile communication，GSM)***、码分多址(code division multiple access，CDMA)***、宽带码分多址(wideband code division multiple access，WCDMA)***、通用分组无线业务(general packet radio service，GPRS)、长期演进(long term evolution，LTE)***、LTE频分双工(frequency division duplex，FDD)***、LTE时分双工(time division duplex，TDD)、通用移动通信***(universal mobile telecommunication system，UMTS)、全球互联微波接入(worldwide interoperability for  microwave access，WiMAX)通信***、微波通信***等。
其中，在本发明实施例中，基站(base station，简称为BS)可以是与终端(terminal)或其它通信站点如中继站点，进行通信的设备，基站可以提供特定物理区域的通信覆盖。例如，基站具体可以是GSM或CDMA中的基站收发台(base transceiver station，BTS)或基站控制器(base station controller，BSC)；也可以是UMTS中的节点B(node B，NB)或者UMTS中的无线网络控制器(radio network controller，RNC)；还可以是LTE中的演进型基站(envoled Node B，eNB或eNodeB)；或者，也可以是无线通信网络中的提供接入服务的其他接入网设备，本发明实施例并不限定。
在本发明实施例中，终端可以分布于整个无线网络中，每个终端可以是静态的或移动的。
终端可以称为用户设备(user equipment，UE)，服务器，移动台(mobile station)，用户单元(subscriber unit)，站台(station)等。UE可以为蜂窝电话(cellular phone)，个人数字助理(personal digital assistant，简称为PDA)，无线调制解调器(modem)，无线通信设备，手持设备(handheld)，膝上型电脑(lapTOS computer)，无绳电话(cordless phone)，无线本地环路(wireless local loop，简称为WLL)台等。当UE应用于M2M方式通信时，UE可以称为M2M终端，具体可以是支持M2M通信的智能电表、智能家电等。
如图1a所示，图1a示出了，本发明实施例提供的一种数据传输方法所应用的数据传输***的架构图，如图1a所示，该数据传输***包括第一终端10、第一基站20、核心网30、核心网40、第二基站50以及第二终端60。其中，第一基站20为第一终端10提供服务，第二基站50为第二终端60提供服务。在第一终端10需要向第二终端20发送待传输业务时，第一终端10将待传输业务包括的多个数据包，按照每个数据包对应的配置参数，将该待传输业务中的每个数据包传输至第一基站20。然后，第一基站20根据接收到的待传输业务中每个数据包对应的配置参数，将待传输业务通过第一基站20所在的核心网30传输至第二基站50所在的核心网40。然后，第二基站50从核心网40处获得待传输业务，并将该待传输业务传输至第二终端60，以实现第一终端10将待传输业务传输至第二终端60，当第一终端10和第二终端60对应不同的基站时，第一终端10和第二终端60之间可以对应同一个分组数据网络网关(packet data network gateway，PGW)，也可以对应不同的PGW。
具体的，本发明实施例以核心网30为例说明核心网的具体结构，如图1a所示，核心网30可以包括移动性管理实体(mobility management entity，MME)301和服务网关(serving gateway，S-GW)302、PGW)303、策略和计费规则功能(policy and charging rules function，PCRF)304、归属签约用户服务器(home subscriber server，HSS)305和移动交换中心(mobile switching center，MSC)306。其中，MME 301是***的核心，主要负责非接入层的信令疏导、加密和完整性保护、终结用户信令。对用户在网络中的移动性进行管理，具体包括用户接入控制，鉴权，数据加密，业务承载控制，寻呼、切换控制等控制信令的处理。S-GW 302作为本地基站间切换时的锚定点，主要负责在基站和PGW 303之间数据信息的传输、转发和路由，为下行数据包提供缓存，实现基于用户的计费。PGW 303是数据承载的锚定点，主要负责数据包的转发、解析、 合法监听、基于业务的计费、业务服务质量(quality of service，QoS)控制。PCRF 304主要用于根据用户使用的业务信息和用户签约的策略信息进行决策，确定用户业务使用和计费的策略，并下发给网关中的策略执行实体。HSS 305用于存储用户签约信息，存储的信息包括用户标识信息、用户安全控制信息、用户位置信息、用户策略控制信息等。MSC306是用于提供呼叫转换服务和呼叫控制的设备，MSC306可以完成呼叫连接、过区切换控制、无线信道管理等功能。
如图1b所示，图1b示出了本发明实施例提供的一种数据传输方法所应用的数据传输***的又一种架构图，图1b与图1a的区别在于，第一终端和第二终端属于同一个基站，例如，基站20，当第一终端10和第二终端60位于同一个基站的覆盖范围内时，第一终端10和第二终端60对应同一个P-GW。
可以理解的是，本发明实施例中的通信设备可以为基站，也可以为终端。下述将以通信设备为终端为例介绍通信设备的结构，如图2a所示，图2a示出了本发明实施例提供的一种终端的结构示意图。如图2a所示，本发明实施例提供的终端包括应用(Application，APP)层、编码层、实时传输协议(real-time transport protocol，RTP)层、用户数据报协议层(user datagram protocol，UDP)/IP层、滤波器(filter)、一个数据无线承载(data radio bearer，DRB)，以及物理(physical，PHY)层。
其中，DRB用于传输用户面数据。DRB包括：分组数据聚合协议(packet data convergence protocol，PDCP)实体、无线链路控制(radio link control，RLC)实体、媒体访问控制(media access control，MAC)实体。其中，PDCP实体和RLC实体之间通过逻辑信道相连，RLC实体和MAC实体之间通过一个逻辑信道连接。在图2a所示的终端结构示意图中，同一待传输业务对应的PDCP实体具有至少两个缓冲器(buffer)，该至少两个缓冲器分别用于存储不同属性的数据包。
示例性的，如图2a所示，PDCP实体包括第一buffer和第二buffer。具体的，第一buffer用于存储属性为重要属性的数据包(也可以称为：重要数据包)，第二buffer用于存储属性为非重要属性的数据包(也可以称为：非重要数据包)。
其中，编码层中运行有视频压缩标准，例如，H.264标准。物理层用于将PDCP实体或者MAC实体调度的数据包发送出去。
其中，H.264标准是由国际电信联盟标准部(international telecommunication union telecommunication standardization sector，ITU-T)和国际标准化组织(international standardization organization，ISO)/IEC联合提出的一种高度压缩数字视频编解码器标准。
下面简单介绍H.264标准的消息构成及发送机制：H.264标准采用分层模式，例如，H.264标准分为2层，即视频编码层(video coding layer，VCL)和网络抽象层(network abstraction layer，NAL)。其中，VCL是进行视频内容的压缩。NAL负责对压缩数据进行打包以适应在不同的网络环境下的传输要求。
H.264标准的所有待传送业务，包括图像数据及其他消息均封装为统一格式的包传送，即网络抽象层单元(NAL unit，NALU)。NALU可以承载各种H.264处理的各种属性的数据包，NALU可以是原始编码流数据、序列参数集(SPS)、图像参数集(PPS)。NALU结构如图2b所示。
在如图2b所示的NALU结构中，NALU包头(Header)字段的结构如表1所示：
表1
Figure PCTCN2017117540-appb-000001
如表1所示，NALU包头占1个字节，其中，NALU包头中的nal_unit_type字段用来指示NALU的类型：
例如，nal_unit_type＝1时，用于指示该NALU携带的NAL数据的属性为非重要属性的数据包(例如，B帧或者P帧)。
nal_unit_type＝5时，用于指示该NALU携带的NAL数据的属性为重要属性的数据包(例如，I帧)。
也即终端可以根据NALU包头中的nal_unit_type字段所携带的参数来识别出NALU所携带的NAL数据为I帧或者B/P帧。
当前，H.264标准是承载在RTP层之上，编码后的NALU被送入RTP层进行封装，若NALU数据长度小于1400byte，则一个RTP数据包中可以只包含一个完整的NALU，也可以包含多个NALU；若NALU数据长度大于1400byte，则一个RTP数据包中只包含一个NALU的一部分，或者说，一个NALU可以拆分成多个RTP数据包。也就是说，一个RTP数据包中承载的数据要么是重要数据包(例如，I帧)，要么是非重要数据包(例如，P帧或者B帧)，不可能出现两种不同属性的数据包的混合，即不可能同时出现多个类型帧的混合。
数据经过RTP层之后形成的RTP数据包携带一个RTP包头、NALU包头和NAL数据，如图2c所示。一个RTP包头中携带的指示信息用于指示该RTP数据包中携带的即NAL数据(数据包)的类型。
RTP层形成的RTP数据包传送至用户数据包协议(user datagram protocol，UDP)层或者IP层。RTP数据包被封装在UDP包后，再封装在IP包中，形成的IP数据包 携带一个IP包头，一个RTP包头、NALU包头和NAL数据，如图2d所示。
其中，IP包头的TOS字段中可以携带1bit的指示信息，终端可以利用IP包头中所携带的1bit的指示信息来指示IP数据包所携带的数据包的属性。
终端将从IP层获取的待传输数据包(携带IP包头的IP数据包)传输至PDCP实体，终端的PDCP实体根据IP数据包的IP包头中携带1bit的指示信息将重要数据包映射到第一buffer中，将非重要数据包映射到第二buffer中。PDCP实体为接收到的数据包加上PDCP头信息并发送至RLC实体，RLC实体再根据MAC实体的指示对PDCP实体处理过的数据帧进行重组、分割和重排序，以及通过物理层将数据帧发送出去。
如图2e所示，图2e示出了本发明实施例提供的另一种终端的结构示意图。图2e与图2a的区别在于，在图2a中一个DRB对应一个RLC实体，而在图2e中一个DRB对应至少两个RLC实体，该至少两个RLC实体用于存储不同属性的数据包。该至少两个RLC实体中每个RLC实体通过一个逻辑信道与MAC实体连接，不同的RLC实体对应不同的逻辑信道，一个RLC实体对应的逻辑信道用于指示该RLC实体内映射的数据包的属性。
具体的，PDCP实体根据IP包头的TOS字段中携带的1bit指示信息来确定从IP层获取的待传输数据包的属性，并根据该待传输数据包的属性将该待传输数据包映射到相应的RLC实体上。
例如，本发明实施例以至少两个RLC实体为第一RLC实体和第二RLC实体为例进行说明：第一RLC实体用于映射属性为重要属性的数据包，第二RLC实体用于映射属性为非重要属性的数据包。PDCP实体通过IP包头的TOS字段中携带的1bit指示信息识别出该传输数据包为重要数据包时，将该传输数据包映射到第一RLC实体上，PDCP实体识别出该传输数据包为非重要数据包时，将该传输数据包映射到第二RLC实体上，以使得不同重要性的数据包分别映射到不同的RLC实体上，其中，第一RLC实体通过第一逻辑信道与MAC实体相连，第二RLC实体通过第二逻辑信道与MAC实体相连。
可以理解的是，重要数据包和非重要数据包对应相同PDCP实体可以使得接收端在PDCP实体对重要数据包和非重要数据包采用同步/重排序的处理。重要数据包和非重要数据包对应于不同RLC实体可以配置不同的重排序定时器(T-reordering)。
如图2f所示，图2f示出了本发明实施例提供的另一种终端的结构示意图。图2f与图2a的区别在于，在图2a中一个DRB对应一个PDCP实体，而在图2f中一个DRB对应至少两个PDCP实体，该至少两个PDCP实体中每个PDCP实体用于存储一个属性的数据包，同一个PDCP实体内存储的数据包的属性相同，不同PDCP实体内存储的数据包的属性不同。
示例性的，本发明实施例以至少两个PDCP实体为第一PDCP实体和第二PDCP实体为例说明。其中，第一PDCP实体用于存储属性为重要属性的数据包，第二PDCP实体用于存储属性为非重要属性的数据包。
具体的，终端根据IP数据包的IP包头中TOS字段的1bit指示来识别该IP数据包的属性为重要属性或者非重要属性。终端确定IP数据包的属性为重要属性，则将该 IP数据包映射到第一PDCP实体上；终端确定该IP数据包的属性为为非重要属性，则将该IP数据包映射到第二PDCP实体上。具体的，本发明实施例中第一PDCP实体和第二PDCP实体中分别具有一个缓冲器。其中，第一PDCP实体中的缓冲器用于存储重要数据包，第二PDCP实体中的缓冲器用于存储非重要数据包。
图2g为本发明实施例提供的一种基站的硬件结构图，如图2g所示，该基站包括基带子***、中射频子***、天馈子***和一些支撑结构(例如，整机子***)。其中，基带子***用于实现整个基站的操作维护，实现信令处理、无线资源原理、到分组核心网的传输接口，实现物理层、介质访问控制层、L3信令、操作维护主控功能。中射频子***实现基带信号、中频信号和射频信号之间的转换，实现无线接收信号的解调和发送信号的调制和功率放大。天馈子***包括连接到基站射频模块的天线和馈线以及GRS接收卡的天线和馈线，用于实现无线空口信号的接收和发送。整机子***，是基带子***和中频子***的支撑部分，提供结构、供电和环境监控功能。
其中，基带子***可以如图2h所示：例如，手机上网需要通过基站接入核心网，在通过核心网接入因特网，其中因特网的数据通过核心网与基站之间的接口，传递到基带部分，基带部分进行PDCP，RLC，MAC层、编码和调制等处理，交给射频部分发射给用户设备。基带与射频之间可以通过CPRI接口连接；另外，射频部分目前可以通过光纤拉远，例如拉远的RRU。本发明实施例中的数据传输方法的各个步骤基带通过射频来实现，同时接收发送步骤是通过天线(例如，空中接口)来实现的。
本发明实施中涉及的用户设备与基站之间的接口可以理解为用户设备与基站之间进行通信的空中接口，或者也可以称为Uu接口。
如图3所示，图3示出了本发明实施例提供一种数据传输方法的示意性流程图，该方法包括：
S101、终端确定待传输数据包的属性，数据包的属性用于指示该数据包的重要性。
本发明实施例中的待传输数据包可以为待传输业务(例如，视频传输业务或者其他待传输业务)中任意一个数据包。
示例性的，本发明实施例以待传输数据包为视频传输业务中的任意一个数据包为例进行说明，该视频传输业务可以通过H.264标准编码为I帧、P帧和B帧，则I帧、P帧和B帧分别为不同属性的数据包。
其中，一个数据包的属性为重要属性，则表示该数据包在传输过程中需要被优先调度(也可以理解为该数据包的优先等级较高)，或者该数据包在传输过程中不能丢，若在传输过程中该重要属性的数据包丢失，则待传输业务将不完整。
一个数据包的属性为非重要属性，则表示该数据包在传输过程中可以丢失或者优先等级比较低，或者该非重要属性的数据包丢失后，对待传输业务不构成影响。例如，
具体的，由于视频传输业务中解码I帧时不需要参考其他帧数据即可独立解码，P帧和B帧需要依赖I帧才能完成解码，没有I帧，P帧和B帧就无法解码。因此，可以将I帧确定为属性是重要属性的数据包，将P帧和B帧确定为属性是非重要属性的数据包。
S102、终端采用数据包的属性对应的配置参数传输数据包。
S103、基站确定接收的待传输数据包的属性。
S104、基站采用数据包的属性对应的配置参数传输数据包。
本发明实施例提供一种数据传输方法，通过确定待传输数据包的属性，然后采用数据包的属性对应的配置参数对数据包传输。这样，若数据包的属性不同，则对数据包传输时所采用的配置参数也不同，与现有技术中将同一待传输业务的每个数据包采用相同的配置参数传输相比，本发明实施例通过按照属性对待传输业务包括的数据包采用与每个数据包对应的配置参数传输，这样不同属性的数据包对应不同的配置参数，能够将属性不同的数据包区分对待，以提高重要性较高的传输数据包的可靠性，从而减少了由于网络拥塞能情况的发生导致的对待传输业务传输质量的影响。
结合图3，如图4所示，本发明实施例在步骤S102之前还包括：
S105、基站向终端发送第一配置指示信息，该第一配置指示信息用于指示终端为不同属性的数据包配置不同的配置参数，配置参数包括不同的HARQ参数值或者不同的丢弃定时长度。
S106、终端接收基站发送的第一配置指示信息。
本发明实施例中终端可以根据基站发送的第一配置指示信息来确定每个数据包对应的配置参数，也可以主动根据每个数据包的属性，为每个数据包配置一个配置参数，当终端主动根据每个数据包的属性，为每个数据包配置一个配置参数时，步骤S105和S106可以省略。
具体的，基站可以通过无线资源控制(Radio Resource Control，RRC)消息向终端发送第一配置指示信息。
可选的，作为一种可能的实现方式，该第一配置指示信息中可以携带多个属性中每个属性对应的配置参数(例如，以重要数据包和非重要数据包为例说明)该RRC消息中携带有一个maxHARQ-Tx字段和一个minHARQ-Tx字段，分别用于指示终端限制重要性不同的数据包的上行最大重传次数。例如，maxHARQ-Tx字段用于指示终端限制重要数据包的上行最大重传次数，而minHARQ-Tx字段用于指示终端限制非重要数据包的上行最大重传次数。终端在接收到第一配置指示信息后，根据maxHARQ-Tx字段中携带的参数来配置重要数据包对应的上行最大重传次数，根据minHARQ-Tx字段中携带的参数来配置非重要数据包对应的上行最大重传次数。
可选的，作为另一种可能的实现方式，该第一配置指示信息中未携带每个属性对应的配置参数，则终端在接收到第一配置指示信息之后，终端从预设映射表，获取每个属性对应的配置参数，其中，预设映射表中存储有每个属性与配置参数之间的映射关系。示例性的，如表2所示：
表2预设映射表
属性 配置参数
第一属性 第一配置参数
第二属性 第二配置参数
第三属性 第三配置参数
仅是示例性的，表2仅列出了第一属性、第二属性和第三属性，可以理解的是，在实际过程中，属性可以包括第一属性、第二属性和第三属性之外的多个属性，其中，第一属性、第二属性和第三属性的重要性不同，例如，第一属性的重要性低于第二属 性的重要性，第二属性的重要性低于第三属性的重要性；或者第一属性的重要性高于第二属性的重要性，第二属性的重要性高于第三属性的重要性。
可选的，终端可以从表2中确定每个属性对应的配置参数，例如，终端在接收到第一配置指示信息后，可以根据表2为属性为第一属性的数据包配置第一配置参数，为属性为第二属性的数据包配置第二配置参数。当终端主动根据数据包的属性为每个数据包配置与该数据包的属性对应的配置参数时，终端可以直接根据表2确定每个数据包的配置参数。
可选的，结合图3和图4，本发明实施例在步骤S102之前，如图5所示，本发明实施例还包括步骤S107：
S107、终端根据数据包的属性，确定数据包的配置参数。
为了保证重要性较高的数据包的传输可靠性，本发明实施例可以为重要性较高的属性配置一个较大的配置参数，为重要性较低的属性配置一个较小的配置参数，这样在网络拥塞时，能够保证重要性较高的数据包可靠地传输。例如，本发明实施例可以将同一待传输业务中属性不同数据包按照重要性由高至低的顺序排序，然后按照每个数据包所属的属性对应的配置参数，为每个数据包配置相应的配置参数。
以下将以属性为重要属性或非重要属性为例进行说明，在实际使用中属性还可以包括重要属性或非重要属性之外的其余属性本发明实施例对此不进行限定：
第一方面，配置参数为混合自动重传请求HARQ参数，本发明实施例提供的步骤S107可以通过以下方式实现：
S1071a、终端确定数据包的配置参数为第一HARQ参数或者第二HARQ参数，其中，第一HARQ参数为重要属性对应的配置参数，第二HARQ参数为非重要属性对应的配置参数，第一HARQ参数的值大于第二HARQ参数的值。
本发明实施例在数据包的属性为重要属性时，终端为数据包配置第一HARQ参数，在数据包的属性为非重要属性时，终端为数据包配置第二HARQ参数。由于第一HARQ参数大于第二HARQ参数，这样，能够保证属性为重要属性的数据包的传输可靠性，并且，当终端确定上行传输达到属性为非重要属性的数据包配置的HARQ参数(例如，第二HARQ参数)时，若该属性为非重要属性的数据包还没有正确接收，则终端将该属性为非重要属性的数据包丢弃不再重传。能够保证在网络拥塞时，避免属性为非重要属性的数据包占用传输资源。
具体的，以待传输业务包括第一数据包和第二数据包为例，其中，第一数据包为视频I帧，第二数据包为视频P帧或者B帧为例，则终端为I帧配置第一HARQ参数，例如，第一HARQ参数为5；终端为P帧或者B帧配置第二HARQ参数，例如，第二HARQ参数为1，则在I帧初传失败后，终端将对I帧重传，并且最多重传5次，若终端对I帧的重传次数达到第一HARQ参数之后，I帧依旧重传失败，则终端不再重传I帧；在P帧或者B帧传输失败后，终端将对P帧或者B帧重传，并且最多重传1次，若终端对P帧或者B帧的重传次数达到第二HARQ参数之后，P帧或者B帧依旧重传失败，则终端不再重传P帧或者B帧。
具体的，本发明实施例中的第一HARQ参数和第二HARQ参数可以根据需要进行设置，为了保证重要数据包尽可能传输成功，应尽可能将第一HARQ参数的值设置的 较大一些，并且可以在网络传输资源不变的情况下，为了减少网络拥塞时，非重要数据包占用传输资源造成对网络质量的影响，则应尽可能将第二HARQ参数的值设置的较小一些。当然，第二HARQ参数也可以设置为0，也即在非重要数据包一旦传输失败，则不进行重传。
为了避免数据在eNodeB或终端中缓存时间过长，在长期演进(long term evolution，LTE)的***中，为每个PDCP实体配置一个丢弃定时器(discard timer，DT)，每个丢弃定时器对应一个丢弃定时长度。对于终端而言，该定时器的丢弃定时长度由eNodeB配置。当该PDCP实体每收到一个PDCP SDU后，将启动一个该定时器，当该定时器超时，则将该PDCP SDU以及对应的PDCP PDU丢弃。
第二方面，配置参数为丢弃定时长度，本发明实施例提供的步骤S107可以通过以下方式实现：
S1071b、终端确定数据包的配置参数为第一丢弃定时长度或第二丢弃定时长度，其中，第一丢弃定时长度为重要属性对应的配置参数，第二丢弃定时长度为非重要属性对应的配置参数，所述第一丢弃定时长度大于所述第二丢弃定时长度。
具体的，基站可以通过RRC消息为终端某一待传输业务对应的PDCP实体配置至少两个丢弃定时器，每个丢弃定时器对应一个丢弃定时长度。示例性的，本发明实施例配置两个丢弃定时器，即第一丢弃定时器对应第一丢弃定时长度，第二丢弃定时器对应第二丢弃定时长度。
例如，可以将同一待传输业务中属性不同的数据包按照重要性由高至低的顺序排序，然后将重要性高的数据包配置的丢弃定时器对应一个较长的丢弃定时长度，将重要性低的数据包配置较低的丢弃定时器，对应一个较短的丢弃定时长度。
例如，本发明实施例中可以配置重要属性的丢弃定时长度大于非重要属性的丢弃定时长度，这样能够保证在网络拥塞时，且达到非重要属性的丢弃定时长度时，将非重要属性对应的数据包丢弃，以在网络传输资源不变的情况下，保障重要属性对应的数据包正常传输，而不丢失，从而减少了对传输质量的影响。
示例性的，以重要属性对应的数据包为I帧为例，非重要属性对应的数据包为P帧或者B帧为例，则终端为I帧配置第一丢弃定时长度，例如，第一丢弃定时长度为50秒(S)，终端为P帧或者B帧配置第二丢弃定时长度，例如，第二丢弃定时长度为10秒。当PDCP实体每收到一个PDCP服务数据单元(Service Data Unit，SDU)后，则根据该PDCP SDU的属性，启动该PDCP SDU的属性对应的定时器。例如，若该PDCP SDU的属性为重要属性，则PDCP实体启动重要属性对应的定时器，当该定时器配置的丢弃定时长度超时，则将该PDCP SDU以及对应的PDCP PDU丢弃。
可选的，结合图3，一方面，步骤S101可以通过以下方式实现：
S1011a、终端在终端的媒体访问控制MAC实体，接收终端的分组数据聚合协议PDCP实体向MAC实体发送的第一指示信息，所述第一指示信息用于指示所述终端接收到的所述数据包的属性。
具体的，终端的媒体访问控制MAC实体接收终端的分组数据聚合协议PDCP实体发送的第一指示信息，该第一指示信息用于指示MAC实体当前时刻接收到的数据包的属性。
示例性的，结合图2a所示，终端通过协议层将待传输业务分为第一数据包和第二数据包，并将该第一数据包和第二数据包通过RTP层组成RTP包后发送到IP层，终端在IP层对为第一数据包和第二数据包分别加上IP包头，以通过IP包头中的TOS字段对第一数据包和第二数据包的属性区分，例如，第一数据包的IP包头中携带有第一标识信息，该第一标识信息用于指示该第一数据包的属性为重要属性，第二数据包的IP包头中携带有第二标识信息，第二标识信息用于指示第二数据包的属性为非重要属性。然后，终端将携带IP包头的第一数据包和第二数据包从IP层传递到PDCP实体，PDCP实体接收到携带IP包头的第一数据包和第二数据包后，通过第一数据包和第二数据包分别携带的IP包头中的第一标识信息和第二标识信息确定第一数据包的属性和第二数据包的属性，在确定第一数据包的属性为重要属性之后，终端将第一数据包缓存到如图2a所示的第一buffer中，将第二数据包缓存到如图2a所示的第二buffer中，且该第一数据包和第二数据包并不发送给RLC实体。PDCP实体在接收到MAC实体发送的当前时刻需要调度的数据包的属性的和上行链路授权(uplink grant，简称为UL Grant)的指示信息后，PDCP实体将对应的buffer中的数据发送到RLC实体，例如，MAC实体发送的当前时刻需要调度属性为重要属性的数据包，则PDCP实体从第一buffer中将第一数据包发送给RLC实体，然后RLC实体将第一数据包发送给MAC实体，此时PDCP实体向MAC实体发送第一指示信息，用于指示MAC实体接收到的第一数据包的属性为重要属性，这样终端就可以对第一数据包采用第一HARQ参数传输。
另一方面，步骤S101可以通过以下方式实现：
S1011b、终端根据数据包的RLC包头，确定数据包的属性，其中，RLC包头中携带有唯一标识数据包属性的标识。
可以理解的是，终端将待传输业务分为多个数据包之后，该多个数据包经过IP层传输后，生成携带IP包头的数据包，并发送到PDCP层，其中IP包头中携带有指示该数据包的属性为重要属性或者非重要属性的标识信息；PDCP层收到IP包后，根据IP包头的标识信息，获知该数据包的属性，并生成携带PDCP包头的数据包，发送到RLC实体，其中，该PDCP包头中携带有指示该数据包的属性为重要属性或者非重要属性的标识信息，RLC实体收到PDCP实体发送的数据包后，根据PDCP实体发送的携带有PDCP包头的数据包中的标识信息，获知该携带有PDCP包头的数据包的属性，并生成携带RLC包头的数据包，发送到MAC实体，其中，该RLC包头中携带有指示该数据包的属性为重要属性或者非重要属性的标识信息。这样，终端MAC实体即可通过数据包的RLC包头确定数据包的属性。
又一方面，终端采用如图2e所示的结构，则步骤S101还可以通过以下方式实现：
S1011c、终端将通过第一逻辑信道获取的数据包的属性确定为重要属性；
S1012c、终端将通过第二逻辑信道获取的数据包的属性确定为非重要属性。
可以理解的是，在步骤S101之前，还包括步骤S101a：终端接收基站下发的第二指示信息，该第二指示信息用于指示终端不同属性的数据包和传输该数据包使用的逻辑信道的对应关系。
具体的，该第二指示信息中携带有每个逻辑信道的标识，以及每个逻辑信道的标 识与属性的对应关系。示例性的，第二指示信息用于指示第一逻辑信道与重要属性对应，第二逻辑信道与非重要属性对应，用来指示UE不同逻辑信道上传输的数据包的属性。
相应的，若通信设备为基站，则基站还包括：向终端发送第二指示信息，该第二指示信息用于指示终端不同属性的数据包和传输该数据包使用的逻辑信道的对应关系。
可选的，结合图3，如图6所示，一方面，在步骤S102之前，本发明实施例提供的方法还包括：
S108、终端将第一属性对应的数据包的数据量，确定为待发送的上行数据量，其中，第一属性为待传输业务包括的不同属性中的任意一个属性。
S109、终端向基站上报待发送的上行数据量。
具体的，本发明实施例中终端以缓存状态报告(buffer status report，BSR)的形式向基站上报待发送的上行数据量。利用该BSR，基站可以获知终端当前时刻有多少重要数据包或者非重要数据包待发送。
具体的，步骤S108可以通过以下方式实现：
一方面，PDCP实体决定调度：
PDCP实体收到待传输业务包括的多个数据包后，若确定当前调度属性为第一属性的数据包，则将属性为第一属性的数据包发送到RLC实体，而将不同属性中除第一属性之外的其余属性的数据包缓存在PDCP实体中以供下次发送。因此，在PDCP实体决定调度的场景下，终端向基站上报的待发送的上行数据量就只有MAC实体从RLC实体处获得的属性为第一属性的数据包的数据量。
另一方面，MAC实体决定调度：
PDCP实体收到待传输业务包括的多个数据包后，将属性为重要属性和非重要属性的数据包分别缓存(例如，缓存在第一buffer和第二buffer中)，PDCP实体并通过跨层给MAC实体发送第三指示信息，该第三指示信息用来指示不同属性中每个属性对应的数据包的数据量。
MAC实体若确定调度第一属性的数据包，则从第三指示信息中获取第一属性对应的数据包的数据量，并将第一属性对应的数据包的数据量以BSR形式上报给基站，等待基站分配的资源。一旦终端收到基站为第一属性对应的数据包分配的资源，则终端的MAC实体向PDCP实体发送第四指示信息，该第四指示信息用于指示PDCP层将第一属性对应的数据包发送到RLC实体。
可选的，终端在向基站上报待发送的上行数据量时，还可以向基站发送第五指示信息，该第五指示信息用于指示所待发送的上行数据量是重要属性的上行数据量还是非重要属性的上行数据量。
具体的，终端可以利用MAC包头中的1bit预留字段来指示该BSR上报的是重要属性还是非重要属性的上行数据量。
示例性的，一方面，MAC实体决定当前时刻的调度，在如图2a和图2e所示的终端结构中，PDCP实体从IP层收到数据包后，将收到的不同属性数据包分别缓存在不同的buffer中。例如，将属性为重要属性的数据包缓存在第一buffer中，将属性为非重要属性的数据包缓存在第二buffer中，MAC实体通过跨层向PDCP实体发送一个 指示信息，用于请求获知上行待发送的数据量。PDCP实体收到该指示信息后，通过跨层向MAC实体发送一个指示信息(即第三指示信息)，该第三指示信息中携带有重要属性对应的数据包的数据量和非重要属性对应的数据包的数据量。MAC实体在接收到该第三指示信息后，若决定当前时刻调度重要属性对应的数据包，则将第三指示信息中重要属性对应的数据包的数据量通过缓存状态报告(BSR)上报方式上报给基站(并且，终端可以向基站发送指示信息，用于指示所所上报的待发送的上行数据量为重要属性还是非重要属性)。否则，将非重要数据包的数据量以及该数据包对应的属性上报给基站。此后基站可以向终端发送一个UL grant，终端收到基站的UL grant后，终端的MAC实体向PDCP实体发送一个携带UL grant信息以及所请求数据包属性的第六指示信息。若该第六指示信息中请求属性为重要属性，则在如图2a所示的终端结构中，PDCP实体根据该第六指示信息，将第一buffer中缓存的数据包发送到如图2a所示的RLC实体中，若该第六指示信息中请求的数据包的属性为非重要属性，则PDCP实体根据该第六指示信息，决定将第二buffer中缓存的非重要数据包发送到如图2a所示的RLC实体。
在如图2e所示的终端结构中，若该第六指示信息中请求的数据包的属性为重要属性，则PDCP实体根据该第六指示信息，将第一buffer中的缓存的重要数据包发送到如图2e所示的第一RLC实体中，若该第六指示信息中请求的数据包的属性为非重要属性，则PDCP实体根据该第六指示信息，决定将第二buffer中缓存的非重要数据包发送到如图2e所示的第二RLC实体中。
在如图2f所示的终端结构中，若该第六指示信息中请求数据的属性为重要属性，则PDCP实体根据该第六指示信息，则终端决定将第一PDCP实体的第一buffer中的数据包发送到如图2f所示的RLC实体中，若该第六指示信息中请求数据的属性为非重要属性，则终端根据该第六指示信息，决定将第二PDCP实体的第二buffer中的数据包发送到如图2e所示的RLC实体中。
另一方面，PDCP实体决定当前时刻的调度。在如图2a所示的结构中，若PDCP实体调度重要数据包，则将重要数据包从第一buffer中推送到RLC实体，否则将非重要数据包推送到RLC实体。在如图2e所示的终端结构中，若PDCP实体决定调度重要数据包，则将重要数据包从第一buffer中推送到第一RLC实体，否则将非重要数据包推送到第二RLC实体。在如图2f所示的终端结构中，若PDCP实体决定调度重要数据包，则将重要数据包从第一PDCP实体的第一buffer中推送到RLC实体，否则将非重要数据包从第二PDCP实体中的第二buffer推送到第二RLC实体。
另一方面，当终端采用如图2f所示的结构时，终端的MAC实体可以从第一RLC实体中获取映射到该第一RLC实体的重要属性对应的数据包的上行数据量，以及向第二RLC实体发送请求，以确定映射到第二RLC实体中非重要属性对应的数据包的上行数据量。
可选的，一方面，本发明实施例中的步骤S102可以通过以下方式实现：
S1021a、终端的MAC实体若确定第一数据包的属性为重要属性，则在第一数据包传输失败时，以第一HARQ参数，将第一数据包重传。
具体的，终端可以通过以下方式确定第一数据包传输失败：
一方面，终端在向基站发送第一数据包之后，若终端接收到基站发送的第一响应消息(例如基站通过PUCCH向终端发送的NACK响应)。则终端确定第一数据包传输失败。例如，终端若确定接收到的第一响应消息中携带的是NACK就说明第一数据包传输不成功，需要进行重传。
另一方面，终端若确定在预设时间内，未接收到基站发送的第一响应消息，则终端确定第一数据包传输失败。
具体的，该预设时间可以根据需要进行设置，本发明实施例对此不进行限定。
S1022a、终端的MAC实体若确定第二数据包的属性为非重要属性，则在第二数据包传输失败时，以第二HARQ参数，将第二数据包重传。
具体的，终端根据携带RLC包头的数据包来识别收到的数据包的属性为重要属性或者非重要属性，若为重要属性则采用重要属性对应的配置参数(即第一HARQ参数)传输数据包；若为非重要属性则采用非重要属性对应的配置参数(即第二HARQ参数)传输数据包。
可选的，另一方面，本发明实施例中的步骤S102可以通过以下方式实现：
S1021b、终端的PDCP实体若确定第一数据包的属性为重要属性，则在第一数据包对应的丢弃定时器的时长达到丢弃定时长度时，将该第一数据包丢弃。
可选的，结合图3，在本发明实施例的步骤S101之前，本发明实施例提供的方法还包括：
S110、终端对待传输业务做处理，以获取多个属性不同的数据包。
需要说明的是，本发明实施例中步骤S103的具体实现方式和步骤S101类似，具体可以参见步骤S101的具体实现方式，本发明实施例在此不再赘述。步骤S104的具体实现方式和步骤S102类似，本发明实施例在此不再赘述。
如图7所示，图7示出了本发明实施例提供的另一种数据传输方法所使用的架构图，在图7所示的架构中，第一终端通过源基站将多个不同属性的数据包发送给第二终端。例如，第二终端可通过分组数据网络网关、服务网关以及目标基站接收源基站发送的多个不同属性的数据包。具体的，如图8所示，该数据传输方法包括：
S901、第一终端对待传输业务处理，以获取多个属性不同的数据包，一个数据包的属性用于指示该数据包的重要性。
具体的，第一终端将待传输业务通过编码层中的H.264标准处理后，以获取多个属性不同的数据包。然后，将多个属性不同的数据包通过RTP层后分别组成RTP数据包后发送到IP层，终端在IP层对多个属性不同的数据包分别加上IP包头，以利用IP包头中1bit信息来指示每个数据包的属性，例如：终端可以通过扩展IP包头中的TOS字段，根据TOS字段中的1bit信息来指示每个数据包的属性。
S902、第一终端通过源基站将多个属性不同的数据包发送给PGW，其中，该PGW为第二终端所接入的网关。
可以理解的是，在实际传输过程中，当第一终端和第二终端之间的距离比较近时，该第二终端所接入的网关和第一终端所接入的网关可以为同一个网关，甚至第一终端和第二终端所接入的基站也为同一个基站。
S903、PGW将多个属性不同的数据包中每个数据包分别映射到一个EPS承载上， 其中，不同属性的数据包对应不同的EPS承载。
其中，承载是指在通信会话期间在第二终端与为第二终端服务的核心网络之间载送分组数据的承载信道。具体的，可以为EPS承载。
如图7所示，在第二终端和PGW之间存在两个承载即第一承载和第二承载，具体的，PGW将重要属性的数据包映射到第一承载上传输，将非重要属性的数据包映射到第二承载上传输
S904、PGW将映射到不同承载上的多个属性不同的数据包通过SGW传输给目标基站。
其中，目标基站为第二终端服务的基站。
S905、目标基站将在不同承载上接收到的多个属性不同的数据包发送给第二终端。
S906、第二终端在不同EPS承载上接收多个属性不同的数据包，以及根据每个数据包上的时间标识(timestamp)字段对多个属性不同的数据包同步(重排序)处理。
上述主要从终端和基站的角度对本发明实施例提供的方案进行了介绍。可以理解的是，终端和基站等为了实现上述功能，其包含了执行各个功能相应的硬件结构和/或软件模块。本领域技术人员应该很容易意识到，结合本文中所公开的实施例描述的各示例的单元及算法步骤，本发明实施例能够以硬件或硬件和计算机软件的结合形式来实现。某个功能究竟以硬件还是计算机软件驱动硬件的方式来执行，取决于技术方案的特定应用和设计约束条件。专业技术人员可以对每个特定的应用来使用不同方法来实现所描述的功能，但是这种实现不应认为超出本发明的范围。
本发明实施例可以根据上述方法示例对终端和基站等进行功能模块的划分，例如，可以对应各个功能划分各个功能模块，也可以将两个或两个以上的功能集成在一个处理模块中。上述集成的模块既可以采用硬件的形式实现，也可以采用软件功能模块的形式实现。需要说明的是，本发明实施例中对模块的划分是示意性的，仅仅为一种逻辑功能划分，实际实现时可以有另外的划分方式。
在采用对应各个功能划分各个功能模块的情况下，图9a示出了上述实施例中所涉及的终端的一种可能的结构示意图，终端1包括：确定单元10以及传输单元11。其中，确定单元10用于支持终端1执行上述实施例描述的过程S101(具体的可以为步骤S1011b、S1011c、S1012c)、S107(具体的，可以为步骤S1071a以及S1071b)、S108；传输单元11用于支持终端1执行上述实施例中所描述的步骤S102(具体的，可以为步骤S1021a、S1022a、S1021b、S1022b)。当然，本发明实施例提供的终端1还可以包括发送单元12用于支持终端1执行上述实施例中的步骤S109，第一接收单元13用于支持终端执行上述实施例中的步骤S1011a、第二接收单元14用于支持终端1执行上述实施例中的步骤S106以及S101a，终端1还可以包括处理单元15，用于支持终端1执行上述实施例中的步骤S110。其中，上述方法实施例涉及的各步骤的所有相关内容均可以援引到对应功能模块的功能描述，在此不再赘述。
可以理解的是，在硬件实现上，一方面，上述确定单元10、传输单元11、发送单元12以及第一接收单元13可以集成在如图2a、2d、2e、以及2f所示的终端的MAC实体上，另一方面，第一接收单元13和第二接收单元14可以为接收器，发送单元12可以为发送器，其可以与接收器集成在一起构成收发器。确定单元10和传输单元11 可以以硬件形式内嵌于或独立于终端的存储器中，以便于终端的处理器调用执行以上各个单元对应的操作。
在采用集成的单元的情况下，图9b示出了上述实施例中所涉及的终端的一种可能的结构示意图。终端1包括：处理模块102和通信模块103。处理模块102用于对终端1的动作进行控制管理，例如，处理模块102用于支持终端1执行实施例中所描述的步骤S101(具体的可以为步骤S1011a、S1011b、S1011c、S1012c)、S101a、S107(具体的，可以为步骤S1071a以及S1071b)、S108、S102(具体的，可以为步骤S1021a、S1022a、S1021b、S1022b)、S106、S109以及S110，和/或用于本文所描述的技术的其它过程。通信模块103用于支持终端1与其他网络实体的通信，例如支持终端1与基站进行通信，终端1还可以包括存储模块101，用于存储终端1的程序代码和数据。
其中，处理模块102可以是处理器或控制器，例如可以是中央处理器(Central Processing Unit，CPU)，通用处理器，数字信号处理器(Digital Signal Processor，DSP)，专用集成电路(Application-Specific Integrated Circuit，ASIC)，现场可编程门阵列(Field Programmable Gate Array，FPGA)或者其他可编程逻辑器件、晶体管逻辑器件、硬件部件或者其任意组合。其可以实现或执行结合本发明公开内容所描述的各种示例性的逻辑方框，模块和电路。所述处理器也可以是实现计算功能的组合，例如包含一个或多个微处理器组合，DSP和微处理器的组合等等。通信模块103可以是收发器、收发电路或通信接口1013等。存储模块101可以是存储器。
当处理模块102为处理器1012，通信模块103为通信接口1013，存储模块101为存储器时，本发明实施例所涉及的终端1可以为图9c所示的终端。
参阅图9c所示，该终端1包括：处理器1012、通信接口1013、存储器1011以及总线1014。其中，通信接口1013、处理器1012以及存储器1011通过总线1014相互连接；总线1014可以是外设部件互连标准(Peripheral Component Interconnect，PCI)总线或扩展工业标准结构(Extended Industry Standard Architecture，EISA)总线等。所述总线可以分为地址总线、数据总线、控制总线等。为便于表示，图9c中仅用一条粗线表示，但并不表示仅有一根总线或一种类型的总线。
在采用对应各个功能划分各个功能模块的情况下，图10a示出了上述实施例中所涉及的基站的一种可能的结构示意图，基站2包括：确定单元20以及传输单元21。其中，确定单元20用于支持基站2执行上述实施例描述的过程S103；传输单元21用于支持基站2执行上述实施例中所描述的步骤S104。当然，本发明实施例提供的基站2还可以包括发送单元22用于支持基站2执行上述实施例中的步骤S105。其中，上述方法实施例涉及的各步骤的所有相关内容均可以援引到对应功能模块的功能描述，在此不再赘述。
可以理解的是，在硬件实现上，一方面，上述确定单元20、传输单元21、发送单元22可以集成在基站的MAC实体上，另一方面，确定单元20和传输单元21可以以硬件形式内嵌于或独立于基站的存储器中，以便于基站的处理器调用执行以上各个单元对应的操作。
在采用集成的单元的情况下，图10b示出了上述实施例中所涉及的基站的一种可 能的结构示意图。基站2包括：处理模块202和通信模块203。处理模块202用于对基站2的动作进行控制管理，例如，处理模块202用于支持基站2执行实施例中所描述的步骤S103、S104以及S105，和/或用于本文所描述的技术的其它过程。通信模块203用于支持基站2与其他网络实体的通信，例如支持基站2与终端通信，基站2还可以包括存储模块201，用于存储基站2的程序代码和数据。
其中，处理模块202可以是处理器或控制器，例如可以是中央处理器(Central Processing Unit，CPU)，通用处理器，数字信号处理器(Digital Signal Processor，DSP)，专用集成电路(Application-Specific Integrated Circuit，ASIC)，现场可编程门阵列(Field Programmable Gate Array，FPGA)或者其他可编程逻辑器件、晶体管逻辑器件、硬件部件或者其任意组合。其可以实现或执行结合本发明公开内容所描述的各种示例性的逻辑方框，模块和电路。所述处理器也可以是实现计算功能的组合，例如包含一个或多个微处理器组合，DSP和微处理器的组合等等。通信模块203可以是收发器、收发电路或通信接口2013等。存储模块201可以是存储器。
当处理模块202为处理器2012，通信模块203为通信接口2013，存储模块201为存储器时，本发明实施例所涉及的基站2可以为图10c所示的基站。
参阅图10c所示，该基站2包括：处理器2012、通信接口2013、存储器2011以及总线2014。其中，通信接口2013、处理器2012以及存储器2011通过总线2014相互连接；总线2014可以是外设部件互连标准(Peripheral Component Interconnect，PCI)总线或扩展工业标准结构(Extended Industry Standard Architecture，EISA)总线等。所述总线可以分为地址总线、数据总线、控制总线等。为便于表示，图10c中仅用一条粗线表示，但并不表示仅有一根总线或一种类型的总线。
一方面，本发明实施例提供一种计算机可读存储介质，计算机可读存储介质中存储有指令，当计算机可读存储介质在计算机上运行时，使得基站执行上述实施例中的步骤S103、S104以及S105。
另一方面，本发明实施例提供一种计算机可读存储介质，计算机可读存储介质中存储有指令，当计算机可读存储介质在计算机上运行时，使得终端执行上述实施例中的步骤S101(S1011a、S1011b、S1011c、S1012c)、S102(具体的，可以为步骤S1021a、S1022a、S1021b、S1022b)、S106、S107(具体的，可以为步骤S1071a以及S1071b)、S108(S1081a、S1082a、S1081b)、S109以及S110。
在上述实施例中，可以全部或部分的通过软件、硬件、固件或者其任意组合来实现。当使用软件程序实现时，可以全部或部分地以计算机程序产品的形式实现。计算机程序产品包括一个或多个计算机指令。在计算机上加载和执行所述计算机程序指令时，全部或部分地产生按照本发明实施例多描述的流程或功能。所述计算机可以使通用计算机、专用计算机、计算机网络、或者其他可编程装置。计算机指令可以存储在计算机可读存储介质中，或者从一个计算机可读存储介质向另一个计算机可读存储介质传输，例如，计算机指令可以从一个网站站点，计算机、服务器或数据中心通过有线(例如，同轴电缆、光纤、数字用户线DSL)或无线(例如，红外、无线、微波等)方式向另一个网站站点、计算机、服务器或数据中心传输。计算机可读存储介质可以是计算机能够读取的任何可用介质或者是包含一个或多个可用介质集成的服务器、数 据中心等数据存储设备。所述可用介质可以使磁性介质，(例如，软盘，硬盘、磁带)、光介质(例如，DVD)、或者半导体介质(例如，固态硬盘(Solid Stste Disk,SSD))等。
通过以上的实施方式的描述，所属领域的技术人员可以清楚地了解到，为描述的方便和简洁，仅以上述各功能模块的划分进行举例说明，实际应用中，可以根据需要而将上述功能分配由不同的功能模块完成，即将装置的内部结构划分成不同的功能模块，以完成以上描述的全部或者部分功能。上述描述的***，装置和单元的具体工作过程，可以参考前述方法实施例中的对应过程，在此不再赘述。
在本申请所提供的几个实施例中，应该理解到，所揭露的***，装置和方法，可以通过其它的方式实现。例如，以上所描述的装置实施例仅仅是示意性的，例如，所述模块或单元的划分，仅仅为一种逻辑功能划分，实际实现时可以有另外的划分方式，例如多个单元或组件可以结合或者可以集成到另一个***，或一些特征可以忽略，或不执行。另一点，所显示或讨论的相互之间的耦合或直接耦合或通信连接可以是通过一些接口，装置或单元的间接耦合或通信连接，可以是电性，机械或其它的形式。
所述作为分离部件说明的单元可以是或者也可以不是物理上分开的，作为单元显示的部件可以是或者也可以不是物理单元，即可以位于一个地方，或者也可以分布到多个网络单元上。可以根据实际的需要选择其中的部分或者全部单元来实现本实施例方案的目的。
另外，在本申请各个实施例中的各功能单元可以集成在一个处理单元中，也可以是各个单元单独物理存在，也可以两个或两个以上单元集成在一个单元中。上述集成的单元既可以采用硬件的形式实现，也可以采用软件功能单元的形式实现。
所述集成的单元如果以软件功能单元的形式实现并作为独立的产品销售或使用时，可以存储在一个计算机可读取存储介质中。基于这样的理解，本申请的技术方案本质上或者说对现有技术做出贡献的部分或者该技术方案的全部或部分可以以软件产品的形式体现出来，该计算机软件产品存储在一个存储介质中，包括若干指令用以使得一台计算机设备(可以是个人计算机，服务器，或者网络设备等)或处理器执行本申请各个实施例所述方法的全部或部分步骤。而前述的存储介质包括：快闪存储器、移动硬盘、只读存储器、随机存取存储器、磁碟或者光盘等各种可以存储程序代码的介质。
以上所述，仅为本申请的具体实施方式，但本申请的保护范围并不局限于此，任何在本申请揭露的技术范围内的变化或替换，都应涵盖在本申请的保护范围之内。因此，本申请的保护范围应以所述权利要求的保护范围为准。

Claims (20)

  1. 一种数据传输方法，其特征在于，包括：
    通信设备确定待传输数据包的属性，所述数据包的属性用于指示所述数据包的重要性；
    所述通信设备采用所述数据包的属性对应的配置参数传输所述数据包。
  2. 根据权利要求1所述的方法，其特征在于，所述通信设备采用所述数据包的属性对应的配置参数传输所述数据包之前，所述方法还包括：
    所述通信设备根据所述数据包的属性，确定所述数据包的配置参数。
  3. 根据权利要求2所述的方法，其特征在于，所述属性为重要属性或非重要属性，所述配置参数为混合自动重传请求HARQ参数，则所述通信设备根据所述数据包的属性，确定所述数据包的配置参数，包括：
    所述通信设备确定所述数据包的配置参数为第一HARQ参数或者第二HARQ参数，其中，所述第一HARQ参数为所述重要属性对应的配置参数，所述第二HARQ参数为所述非重要属性对应的配置参数，所述第一HARQ参数的值大于所述第二HARQ参数的值；
    或者，所述配置参数为丢弃定时长度，则所述通信设备根据所述数据包的属性，确定所述数据包的配置参数，包括：
    所述通信设备确定所述数据包的配置参数为第一丢弃定时长度或第二丢弃定时长度，其中，所述第一丢弃定时长度为所述重要属性对应的配置参数，所述第二丢弃定时长度为所述非重要属性对应的配置参数，所述第一丢弃定时长度大于所述第二丢弃定时长度。
  4. 根据权利要求1-3任意一项所述的方法，其特征在于，所述通信设备确定待传输数据包的属性，包括：
    所述通信设备通过媒体访问控制MAC实体接收所述通信设备的分组数据聚合协议PDCP实体发送的第一指示信息，所述第一指示信息用于指示所述通信设备接收到的所述数据包的属性；
    所述通信设备根据所述第一指示信息，确定所述数据包的属性；
    或者，
    所述通信设备根据所述数据包的无线链路控制RLC包头，确定所述数据包的属性，其中，所述RLC包头中携带有唯一标识所述数据包属性的标识。
  5. 根据权利要求1-3任意一项所述的方法，其特征在于，所述确定待传输数据包的属性，包括：
    所述通信设备将通过所述第一逻辑信道获取的数据包的属性确定为重要属性；
    所述通信设备将通过所述第二逻辑信道获取的数据包的属性确定为非重要属性。
  6. 根据权利要求5所述的方法，其特征在于，所述通信设备为终端，所述确定待传输数据包的属性之前，所述方法还包括：
    所述终端接收基站发送的第二指示信息，所述第二指示信息用于指示不同属性的数据包和用于传输该数据包的逻辑信道之间的对应关系。
  7. 根据权利要求1-6任意一项所述的方法，其特征在于，所述通信设备为终端， 所述通信设备根据所述数据包的属性，确定所述数据包的配置参数之前，所述方法还包括：
    所述终端接收基站发送的第一配置指示信息，所述第一配置指示信息用于指示所述终端为不同属性的数据包配置不同的配置参数。
  8. 根据权利要求1-5任意一项所述的方法，其特征在于，所述通信设备为基站，所述方法还包括：
    所述基站向终端发送第一配置指示信息，所述第一配置指示信息用于指示所述终端为不同属性的数据包配置不同的配置参数。
  9. 一种通信设备，其特征在于，包括：
    确定单元，用于确定待传输数据包的属性，所述数据包的属性用于指示所述数据包的重要性；
    传输单元，用于采用所述数据包的属性对应的配置参数传输所述数据包。
  10. 根据权利要求9所述的通信设备，其特征在于，所述确定单元还用于：根据所述数据包的属性，确定所述数据包的配置参数。
  11. 根据权利要求10所述的通信设备，其特征在于，所述属性为重要属性或非重要属性，所述配置参数为混合自动重传请求HARQ参数，则所述确定单元具体用于：确定所述数据包的配置参数为第一HARQ参数或者第二HARQ参数，其中，所述第一HARQ参数为所述重要属性对应的配置参数，所述第二HARQ参数与所述非重要属性对应的配置参数，所述第一HARQ参数的值大于所述第二HARQ参数的值；
    所述配置参数为丢弃定时长度，则所述确定单元还具体用于：确定所述数据包的配置参数为第一丢弃定时长度或第二丢弃定时长度，其中，所述第一丢弃定时长度为所述重要属性对应的配置参数，所述第二丢弃定时长度为所述非重要属性对应的配置参数，所述第一丢弃定时长度大于所述第二丢弃定时长度。
  12. 根据权利要求9-11任意一项所述的通信设备，其特征在于，所述通信设备包括：
    第一接收单元，用于通过所述通信设备的MAC实体接收所述通信设备的PDCP实体向所述MAC实体发送的第一指示信息，所述第一指示信息用于指示所述终端接收到的所述数据包的属性；
    所述确定单元还具体用于：根据所述第一指示信息，确定所述数据包的属性；
    或者，
    所述确定单元还具体用于：根据所述数据包的RLC包头，确定所述数据包的属性，其中，所述RLC包头中携带有唯一标识所述数据包属性的标识。
  13. 根据权利要求9-11任意一项所述的通信设备，其特征在于，所述确定单元，具体用于将通过所述第一逻辑信道获取的数据包的属性确定为重要属性；以及用于将通过所述第二逻辑信道获取的数据包的属性确定为非重要属性。
  14. 根据权利要求13所述的通信设备，其特征在于，所述通信设备还包括：第二接收单元，用于接收基站发送的第二指示信息，所述第二指示信息用于指示不同属性的数据包和用于传输该数据包的逻辑信道之间的对应关系。
  15. 根据权利要求9-14任意一项所述的通信设备，其特征在于，所述通信设备还 包括：第二接收单元，用于接收基站发送的第一配置指示信息，所述第一配置指示信息用于指示所述终端为不同属性的数据包配置不同的配置参数。
  16. 根据权利要求9-13任意一项所述的通信设备，其特征在于，所述通信设备为基站，所述基站还包括：发送单元，用于向终端发送第一配置指示信息，所述第一配置指示信息用于指示所述终端为不同属性的数据包配置不同的配置参数。
  17. 一种终端，其特征在于，所述终端包括处理器、存储器、***总线和通信接口；其中，所述存储器用于存储计算机执行指令，所述处理器与所述存储器通过所述***总线连接，当所述终端运行时，所述处理器执行所述存储器存储的所述计算机执行指令，以使所述终端执行如权利要求1-7任意一项所述的数据传输方法。
  18. 一种基站，其特征在于，所述基站包括处理器、存储器、***总线和通信接口；其中，所述存储器用于存储计算机执行指令，所述处理器与所述存储器通过所述***总线连接，当所述基站运行时，所述处理器执行所述存储器存储的所述计算机执行指令，以使所述基站执行如权利要求1-5以及权利要求8中任意一项所述的数据传输方法。
  19. 一种计算机可读存储介质，包括指令，当指令在计算机上运行时，使得计算机执行如权利要求1-7任意一项所述的数据传输方法，或者如权利要求1-5以及权利要求8中任意一项所述的数据传输方法。
  20. 一种包含指令的计算机程序产品，当指令在计算机上运行时，使得计算机执行如权利要求1-7任意一项所述的数据传输方法，或者如权利要求1-5以及权利要求8中任意一项所述的数据传输方法。
PCT/CN2017/117540 2017-02-10 2017-12-20 一种数据传输方法、通信设备、终端和基站 WO2018145521A1 (zh)

Priority Applications (4)

Application Number Priority Date Filing Date Title
JP2019542550A JP6907444B2 (ja) 2017-02-10 2017-12-20 データ伝送方法、通信デバイス、端末、および基地局
RU2019128270A RU2753372C2 (ru) 2017-02-10 2017-12-20 Способ передачи данных, устройство связи, оконечное устройство и базовая станция
EP17895664.5A EP3570590B1 (en) 2017-02-10 2017-12-20 Data transmission method, communication device, terminal and base station
US16/535,772 US11190626B2 (en) 2017-02-10 2019-08-08 Data transmission method, communications device, terminal, and base station

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN201710074932.4 2017-02-10
CN201710074932.4A CN108419275B (zh) 2017-02-10 2017-02-10 一种数据传输方法、通信设备、终端和基站

Related Child Applications (1)

Application Number Title Priority Date Filing Date
US16/535,772 Continuation US11190626B2 (en) 2017-02-10 2019-08-08 Data transmission method, communications device, terminal, and base station

Publications (1)

Publication Number Publication Date
WO2018145521A1 true WO2018145521A1 (zh) 2018-08-16

Family

ID=63107162

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2017/117540 WO2018145521A1 (zh) 2017-02-10 2017-12-20 一种数据传输方法、通信设备、终端和基站

Country Status (6)

Country Link
US (1) US11190626B2 (zh)
EP (1) EP3570590B1 (zh)
JP (1) JP6907444B2 (zh)
CN (1) CN108419275B (zh)
RU (1) RU2753372C2 (zh)
WO (1) WO2018145521A1 (zh)

Families Citing this family (18)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN111066272B (zh) * 2017-09-12 2022-09-09 诺基亚通信公司 移动无线电接入网络中的分组延迟减少
KR102500134B1 (ko) * 2017-11-01 2023-02-15 삼성전자주식회사 무선 통신 시스템에서 패킷 데이터 정보를 송수신하기 위한 장치 및 방법
CN111082899A (zh) 2018-10-19 2020-04-28 中兴通讯股份有限公司 一种传输方法、装置和***
CN111818005A (zh) * 2019-12-26 2020-10-23 厦门雅基软件有限公司 数据包处理方法、装置、电子设备及可读存储介质
CN111277319B (zh) * 2020-01-20 2022-08-16 中国电子科技集团公司电子科学研究院 星地间数据传输方法及装置
CN113950041A (zh) * 2020-07-17 2022-01-18 华为技术有限公司 一种数据传输方法、用户设备及基站
CN114363919A (zh) * 2020-10-13 2022-04-15 大唐移动通信设备有限公司 一种数据传输方法、终端及网络设备
CN112804711B (zh) 2021-01-04 2024-05-07 腾讯科技（深圳）有限公司 数据传输方法、装置、计算机可读介质及电子设备
CN115834742A (zh) * 2021-09-16 2023-03-21 大唐移动通信设备有限公司 定时器处理方法、装置及存储介质
CN115996425A (zh) * 2021-10-19 2023-04-21 维沃移动通信有限公司 数据传输方法、装置及终端
CN116156549A (zh) * 2021-11-15 2023-05-23 ***通信有限公司研究院 信息处理方法、装置、设备及可读存储介质
CN116847405A (zh) * 2022-03-24 2023-10-03 维沃移动通信有限公司 数据包处理方法、装置、通信设备及存储介质
CN117062142A (zh) * 2022-05-05 2023-11-14 华为技术有限公司 通信方法和装置
CN117412285A (zh) * 2022-07-06 2024-01-16 华为技术有限公司 数据量指示方法、数据递交方法及装置
CN115276916A (zh) * 2022-07-22 2022-11-01 上海百家云科技有限公司 一种丢弃数据的确定方法、装置、电子设备及存储介质
CN115242355B (zh) * 2022-09-15 2023-05-26 合肥移瑞通信技术有限公司 无线通信的方法及装置
WO2024065207A1 (zh) * 2022-09-27 2024-04-04 北京小米移动软件有限公司 一种数据发送方法、装置以及可读存储介质
CN117998459A (zh) * 2022-11-03 2024-05-07 华为技术有限公司 通信方法及装置

Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN1780255A (zh) * 2004-11-24 2006-05-31 大唐移动通信设备有限公司 非均等保护的无线数据传输方法
CN102013962A (zh) * 2009-09-04 2011-04-13 华为技术有限公司 数据传输方法及设备
US20120057560A1 (en) * 2009-05-11 2012-03-08 Sung Jun Park Method and apparatus for transmitting and receiving duplicate data in a multicarrier wireless communication system
CN103814582A (zh) * 2013-11-05 2014-05-21 华为技术有限公司 视频业务数据传输方法、数据接收装置和数据发送装置
CN103874140A (zh) * 2012-12-12 2014-06-18 华为技术有限公司 信息处理方法、接入点及站点

Family Cites Families (15)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
JP4673972B2 (ja) * 2000-12-26 2011-04-20 富士通東芝モバイルコミュニケーションズ株式会社 移動通信システム及び通信装置
BRPI0509447A (pt) * 2004-05-05 2007-09-04 Qualcomm Inc método e equipamento para gerenciamento de retardo adaptativo em um sistema de comunicação sem fio
US20070097205A1 (en) * 2005-10-31 2007-05-03 Intel Corporation Video transmission over wireless networks
WO2008021182A2 (en) * 2006-08-09 2008-02-21 Interdigital Technology Corporation Method and apparatus for providing differentiated quality of service for packets in a particular flow
JP5084362B2 (ja) * 2007-06-18 2012-11-28 キヤノン株式会社 データ送信装置、及びデータ送受信システム
KR101513033B1 (ko) * 2007-09-18 2015-04-17 엘지전자 주식회사 다중 계층 구조에서 ＱｏＳ를 보장하기 위한 방법
US9113042B2 (en) * 2009-08-28 2015-08-18 Broadcom Corporation Multi-wireless device channel communications
US20120069927A1 (en) * 2010-09-17 2012-03-22 Intel Corporation CQI feedback mechanisms for distortion-aware link adaptation toward enhanced multimedia communications
JP6085617B2 (ja) * 2012-02-11 2017-02-22 ヴィド スケール インコーポレイテッド ビデオアウェアの（ｖｉｄｅｏａｗａｒｅ）ハイブリッド自動再送要求のための方法および装置
CN104137554A (zh) * 2012-02-24 2014-11-05 Vid拓展公司 使用分组损耗检测的视频编码
CN103312441B (zh) * 2012-03-15 2017-11-17 华为技术有限公司 数据包传输方法及***、发送端设备与接收端设备
EP2826208B1 (en) * 2012-10-29 2018-02-21 Huawei Technologies Co., Ltd. A bandwidth management device, central management device and method of bandwidth management
CN103944681B (zh) * 2014-04-30 2017-08-01 西安交通大学 Hsdpa网络中视频感知的链路自适应方法
JP6717193B2 (ja) * 2014-06-30 2020-07-01 ソニー株式会社 無線通信装置、無線通信方法及びプログラム
US9696935B2 (en) * 2015-04-24 2017-07-04 Kabushiki Kaisha Toshiba Storage device that secures a block for a stream or namespace and system having the storage device

Patent Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN1780255A (zh) * 2004-11-24 2006-05-31 大唐移动通信设备有限公司 非均等保护的无线数据传输方法
US20120057560A1 (en) * 2009-05-11 2012-03-08 Sung Jun Park Method and apparatus for transmitting and receiving duplicate data in a multicarrier wireless communication system
CN102013962A (zh) * 2009-09-04 2011-04-13 华为技术有限公司 数据传输方法及设备
CN103874140A (zh) * 2012-12-12 2014-06-18 华为技术有限公司 信息处理方法、接入点及站点
CN103814582A (zh) * 2013-11-05 2014-05-21 华为技术有限公司 视频业务数据传输方法、数据接收装置和数据发送装置

Non-Patent Citations (1)

* Cited by examiner, † Cited by third party
Title
See also references of EP3570590A4

Also Published As

Publication number Publication date
US20190364137A1 (en) 2019-11-28
EP3570590B1 (en) 2023-07-05
CN108419275B (zh) 2022-01-14
EP3570590A4 (en) 2020-01-22
US11190626B2 (en) 2021-11-30
RU2019128270A3 (zh) 2021-03-10
RU2019128270A (ru) 2021-03-10
JP6907444B2 (ja) 2021-07-21
RU2753372C2 (ru) 2021-08-13
EP3570590A1 (en) 2019-11-20
JP2020509663A (ja) 2020-03-26
CN108419275A (zh) 2018-08-17

Similar Documents

Publication Publication Date Title
WO2018145521A1 (zh) 一种数据传输方法、通信设备、终端和基站
CN108809542B (zh) 一种数据传输的处理方法和装置
KR101098592B1 (ko) 무선 통신 시스템상에서 점대다 서비스를 수신하는 방법
US8386671B2 (en) Communication system, communication device and communication method
WO2021238676A1 (zh) 数据传输方法及装置
WO2022088833A1 (zh) 用于传输媒体流的数据包的方法和通信装置
US20180124355A1 (en) Method and system for improving video quality during call handover
TW201840236A (zh) 傳輸數據的方法和通信設備
EP3446448B1 (en) Methods and apparatus for discarding packets in a wireless communication network
WO2022052102A1 (zh) 一种通信方法及装置
WO2023184479A1 (en) Method and apparatus of supporting mobility
WO2023197312A1 (zh) 无线通信的方法及装置
WO2023087145A1 (en) Methods and apparatuses for pdcp reordering management
CN117014954A (zh) 通信方法和装置
WO2024067374A1 (zh) 一种通信方法及装置
WO2023108413A1 (en) Method and apparatus of reporting buffer status
CN114928554B (zh) 视频传输方法、装置和存储介质
US11917206B2 (en) Video codec aware radio access network configuration and unequal error protection coding
WO2023184545A1 (zh) 一种数据传输方法及装置、通信设备
WO2023201607A1 (zh) 一种数据传输方法及装置、通信设备
WO2024017135A1 (zh) 处理图像的方法和装置
US20240187650A1 (en) Video codec aware radio access network configuration and unequal error protection coding
WO2023115473A1 (en) Methods and apparatuses for supporting a packet discarding operation in a pdcp layer due to a packet loss
TW202329735A (zh) 擴展現實訊務的傳遞優化的方法及其使用者設備
WO2018146771A1 (ja) 通信システム、基地局装置、通信端末装置および管理装置

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 17895664

Country of ref document: EP

Kind code of ref document: A1

ENP Entry into the national phase

Ref document number: 2019542550

Country of ref document: JP

Kind code of ref document: A

NENP Non-entry into the national phase

Ref country code: DE

ENP Entry into the national phase

Ref document number: 2017895664

Country of ref document: EP

Effective date: 20190813