WO2023184545A1

WO2023184545A1 - Data transmission method and apparatus, and communication device

Info

Publication number: WO2023184545A1
Application number: PCT/CN2022/085119
Authority: WO
Inventors: 王淑坤; 付喆; 石聪
Original assignee: Oppo广东移动通信有限公司
Priority date: 2022-04-02
Filing date: 2022-04-02
Publication date: 2023-10-05

Abstract

Provided in the embodiments of the present application are a data transmission method and apparatus, and a communication device. The method comprises: a first protocol layer acquiring attribute information of a first data packet; the first protocol layer executing specific processing in respect of the first data packet on the basis of the attribute information of the first data packet, the attribute information comprising at least one of the following: specific quality of service (Qos) attribute, data type, the data importance degree, and data priority.

Description

A data transmission method and device, communication equipment

Technical field

The embodiments of the present application relate to the field of mobile communication technology, and specifically relate to a data transmission method and device, and communication equipment.

Background technique

Packet Data Unit set (Packet Data Unit set, PDU set) consists of one or more Packet Data Units (Packet Data Unit set, PDU). For a PDU set, it represents a frame or a video clip, and each PDU in the PDU set represents an application layer data packet. Currently, in air interface data transmission and processing, data packets are processed accordingly according to the Quality of Service (Qos) flow or data bearer in which the data packet is located. Data packets on the same Qos flow or data bearer have the same processing method. However, for PDU sets, PDUs in different PDU sets have different processing requirements, so how to use different processing methods for PDUs (that is, data packets) is a problem that needs to be solved.

Contents of the invention

Embodiments of the present application provide a data transmission method and device, communication equipment, network equipment, chips, computer-readable storage media, computer program products, and computer programs.

The data transmission method provided by the embodiment of this application includes:

The first protocol layer obtains attribute information of the first data packet;

The first protocol layer performs specific processing on the first data packet based on the attribute information of the first data packet;

Wherein, the attribute information includes at least one of the following: specific Qos attributes, data type, data importance, and data priority.

The first node sends a first PDU to the second node, where the first PDU is used to indicate to the second node a list of serial numbers (Serial Number, SN) that need to feedback positive acknowledgment (ACK)/negative acknowledgment (NACK);

The first node receives a second PDU sent by the second node, and the second PDU is used to indicate to the first node the ACK/NACK information corresponding to the SN list.

The second node receives the first PDU sent by the first node, where the first PDU is used to indicate to the second node a list of SNs that need to feed back ACK/NACK;

The second node sends a second PDU to the first node, where the second PDU is used to indicate to the first node the ACK/NACK information corresponding to the SN list.

The data transmission device provided by the embodiment of the present application has a first protocol layer;

The first protocol layer is used to obtain attribute information of the first data packet; based on the attribute information of the first data packet, perform specific processing for the first data packet;

The data transmission device provided by the embodiment of the present application is applied to the first node, and the device includes:

A sending unit, configured to send a first PDU to the second node, where the first PDU is used to indicate to the second node a list of SNs that need to feed back ACK/NACK;

A receiving unit configured to receive a second PDU sent by the second node, where the second PDU is used to indicate ACK/NACK information corresponding to the SN list to the first node.

The data transmission device provided by the embodiment of the present application is applied to the second node, and the device includes:

A receiving unit, configured to receive a first PDU sent by the first node, where the first PDU is used to indicate to the second node a list of SNs that need to feed back ACK/NACK;

A sending unit, configured to send a second PDU to the first node, where the second PDU is used to indicate to the first node the ACK/NACK information corresponding to the SN list.

The communication device provided by the embodiment of the present application includes a processor and a memory. The memory is used to store computer programs, and the processor is used to call and run the computer programs stored in the memory and perform the above-mentioned data transmission method.

The chip provided by the embodiment of the present application is used to implement the above data transmission method.

Specifically, the chip includes: a processor, configured to call and run a computer program from the memory, so that the device installed with the chip executes the above-mentioned data transmission method.

The computer-readable storage medium provided by the embodiment of the present application is used to store a computer program. The computer program causes the computer to execute the above-mentioned data transmission method.

The computer program product provided by the embodiment of the present application includes computer program instructions, which cause the computer to execute the above-mentioned data transmission method.

The computer program provided by the embodiment of the present application, when run on a computer, causes the computer to perform the above data transmission method.

Through the above technical solution, the first protocol layer performs specific processing for the first data packet according to the attribute information of the first data packet. The attribute information includes at least one of the following: specific quality of service Qos attributes, data type, data importance, Data priority, in this way, can implement different processing methods for different data packets, thereby better improving the performance and user experience of multimedia services.

Description of drawings

The drawings described here are used to provide a further understanding of the present application and constitute a part of the present application. The illustrative embodiments of the present application and their descriptions are used to explain the present application and do not constitute an improper limitation of the present application. In the attached picture:

Figure 1 is a schematic diagram of an application scenario;

Figure 2 is a 5G network system architecture diagram;

Figure 3 is a schematic diagram of a Qos mechanism;

Figure 4 is a schematic diagram of PDU set transmission provided by the embodiment of this application;

Figure 5 is a schematic flowchart 1 of the data transmission method provided by the embodiment of the present application;

Figure 6 is a schematic flowchart 2 of the data transmission method provided by the embodiment of the present application;

Figure 7 is a schematic diagram of the protocol layer provided by the embodiment of the present application;

Figure 8 is a schematic diagram of the interaction between the sending end and the receiving end provided by the embodiment of the present application;

Figure 9-1 is a schematic diagram 1 of the format of the ACK/NACK feedback request PDU provided by the embodiment of this application;

Figure 9-2 is a schematic diagram 2 of the format of the ACK/NACK feedback request PDU provided by the embodiment of this application;

Figure 9-3 is a schematic diagram 3 of the format of the ACK/NACK feedback request PDU provided by the embodiment of this application;

Figure 9-4 is a schematic diagram 4 of the format of the ACK/NACK feedback request PDU provided by the embodiment of this application;

Figure 9-5 is a schematic diagram 5 of the format of the ACK/NACK feedback request PDU provided by the embodiment of this application;

Figure 10 is a schematic diagram of the format of the ACK/NACK feedback response PDU provided by the embodiment of the present application;

Figure 11 is a schematic structural diagram of a data transmission device provided by an embodiment of the present application;

Figure 12 is a schematic diagram 2 of the structure of the data transmission device provided by the embodiment of the present application;

Figure 13 is a schematic diagram 3 of the structure of the data transmission device provided by the embodiment of the present application;

Figure 14 is a schematic structural diagram of a communication device provided by an embodiment of the present application;

Figure 15 is a schematic structural diagram of a chip according to an embodiment of the present application;

Figure 16 is a schematic block diagram of a communication system provided by an embodiment of the present application.

Detailed ways

The technical solutions in the embodiments of the present application will be described below with reference to the accompanying drawings in the embodiments of the present application. Obviously, the described embodiments are part of the embodiments of the present application, but not all of the embodiments. Based on the embodiments in this application, all other embodiments obtained by those of ordinary skill in the art without creative efforts fall within the scope of protection of this application.

Figure 1 is a schematic diagram of an application scenario according to the embodiment of the present application.

As shown in FIG. 1 , the communication system 100 may include a terminal device 110 and a network device 120 . The network device 120 may communicate with the terminal device 110 through the air interface. Multi-service transmission is supported between the terminal device 110 and the network device 120.

It should be understood that the embodiment of the present application is only exemplified by using the communication system 100, but the embodiment of the present application is not limited thereto. That is to say, the technical solutions of the embodiments of the present application can be applied to various communication systems, such as: Long Term Evolution (LTE) system, LTE Time Division Duplex (TDD), Universal Mobile Communication System (Universal Mobile Communication System) Mobile Telecommunication System (UMTS), Internet of Things (IoT) system, Narrow Band Internet of Things (NB-IoT) system, enhanced Machine-Type Communications (eMTC) system, 5G communication system (also known as New Radio (NR) communication system), or future communication system, etc.

In the communication system 100 shown in FIG. 1 , the network device 120 may be an access network device that communicates with the terminal device 110 . The access network device may provide communication coverage for a specific geographical area and may communicate with terminal devices 110 (eg, UEs) located within the coverage area.

The network device 120 may be an evolutionary base station (Evolutional Node B, eNB or eNodeB) in a Long Term Evolution (LTE) system, or a next generation radio access network (Next Generation Radio Access Network, NG RAN) equipment, It may be a base station (gNB) in an NR system, or a wireless controller in a Cloud Radio Access Network (CRAN), or the network device 120 may be a relay station, access point, vehicle-mounted device, or wearable device. Equipment, hubs, switches, bridges, routers, or network equipment in the future evolved Public Land Mobile Network (Public Land Mobile Network, PLMN), etc.

The terminal device 110 may be any terminal device, including but not limited to terminal devices that are wired or wirelessly connected to the network device 120 or other terminal devices.

For example, the terminal device 110 may refer to an access terminal, user equipment (UE), user unit, user station, mobile station, mobile station, remote station, remote terminal, mobile device, user terminal, terminal, wireless communication Device, user agent, or user device. Access terminals can be cellular phones, cordless phones, Session Initiation Protocol (SIP) phones, IoT devices, satellite handheld terminals, Wireless Local Loop (WLL) stations, Personal Digital Assistants (Personal Digital Assistant) , PDA), handheld devices with wireless communication functions, computing devices or other processing devices connected to wireless modems, vehicle-mounted devices, wearable devices, terminal devices in 5G networks or terminal devices in future evolution networks, etc.

The terminal device 110 can be used for device to device (Device to Device, D2D) communication.

The wireless communication system 100 may also include a core network device 130 that communicates with the base station. The core network device 130 may be a 5G core network (5G Core, 5GC) device, such as an access and mobility management function (Access and Mobility Management Function). , AMF), for example, Authentication Server Function (AUSF), for example, User Plane Function (UPF), for example, Session Management Function (Session Management Function, SMF). Optionally, the core network device 130 may also be an Evolved Packet Core (EPC) device of the LTE network, for example, a session management function + core network data gateway (Session Management Function + Core Packet Gateway, SMF + PGW- C) Equipment. It should be understood that SMF+PGW-C can simultaneously realize the functions that SMF and PGW-C can realize. In the process of network evolution, the above-mentioned core network equipment may also be called by other names, or a new network entity may be formed by dividing the functions of the core network, which is not limited by the embodiments of this application.

Various functional units in the communication system 100 can also establish connections through next generation network (NG) interfaces to achieve communication.

For example, the terminal device establishes an air interface connection with the access network device through the NR interface for transmitting user plane data and control plane signaling; the terminal device can establish a control plane signaling connection with the AMF through the NG interface 1 (referred to as N1); access Network equipment, such as the next generation wireless access base station (gNB), can establish user plane data connections with UPF through NG interface 3 (referred to as N3); access network equipment can establish control plane signaling with AMF through NG interface 2 (referred to as N2) connection; UPF can establish a control plane signaling connection with SMF through NG interface 4 (referred to as N4); UPF can exchange user plane data with the data network through NG interface 6 (referred to as N6); AMF can communicate with SMF through NG interface 11 (referred to as N11) SMF establishes a control plane signaling connection; SMF can establish a control plane signaling connection with PCF through NG interface 7 (referred to as N7).

Figure 1 exemplarily shows a base station, a core network device and two terminal devices. Optionally, the wireless communication system 100 may include multiple base station devices and other numbers of terminals may be included within the coverage of each base station. Equipment, the embodiments of this application do not limit this.

It should be noted that FIG. 1 only illustrates the system to which the present application is applicable in the form of an example. Of course, the method shown in the embodiment of the present application can also be applied to other systems. Additionally, the terms "system" and "network" are often used interchangeably herein. The term "and/or" in this article is just an association relationship that describes related objects, indicating that three relationships can exist. For example, A and/or B can mean: A exists alone, A and B exist simultaneously, and they exist alone. B these three situations. In addition, the character "/" in this article generally indicates that the related objects are an "or" relationship. It should also be understood that the "instruction" mentioned in the embodiments of this application may be a direct instruction, an indirect instruction, or an association relationship. For example, A indicates B, which can mean that A directly indicates B, for example, B can be obtained through A; it can also mean that A indirectly indicates B, for example, A indicates C, and B can be obtained through C; it can also mean that there is an association between A and B. relation. It should also be understood that the "correspondence" mentioned in the embodiments of this application can mean that there is a direct correspondence or indirect correspondence between the two, it can also mean that there is an associated relationship between the two, or it can mean indicating and being instructed. , configuration and configured relationship. It should also be understood that the "predefined" or "predefined rules" mentioned in the embodiments of this application can be pre-saved in the device (for example, including terminal devices and network devices) by pre-saving corresponding codes, tables or other available The method is implemented by indicating relevant information, and this application does not limit its specific implementation method. For example, predefined can refer to what is defined in the protocol. It should also be understood that in the embodiments of this application, the "protocol" may refer to a standard protocol in the communication field, which may include, for example, LTE protocol, NR protocol, and related protocols applied in future communication systems. This application does not limit this. .

In order to facilitate understanding of the technical solutions of the embodiments of the present application, the relevant technologies of the embodiments of the present application are described below. The following related technologies can be optionally combined with the technical solutions of the embodiments of the present application, and they all belong to the embodiments of the present application. protected range.

5G network architecture

Figure 2 is a 5G network system architecture diagram. As shown in Figure 2, the network elements involved in the 5G network system include: User Equipment (User Equipment, UE), Radio Access Network (Radio Access Network, RAN), and user plane functions (User Plane Function, UPF), Data Network (DN), Access and Mobility Management Function (AMF), Session Management Function (Session Management Function, SMF), Policy Control Function (Policy Control Function (PCF), Application Function (AF), Authentication Server Function (AUSF), Unified Data Management (UDM).

As shown in Figure 2, the UE connects to the access layer (AS) with the RAN through the Uu interface, and exchanges access layer messages and wireless data transmission. The UE performs a non-access stratum (NAS) connection with the AMF through the N1 interface and exchanges NAS messages. AMF is the mobility management function in the core network, and SMF is the session management function in the core network. In addition to mobility management of the UE, the AMF is also responsible for forwarding session management related messages between the UE and the SMF. PCF is the policy management function in the core network and is responsible for formulating policies related to UE mobility management, session management, and charging. UPF is the user plane function in the core network. It transmits data to the DN through the N6 interface and to the RAN through the N3 interface.

QoS mechanism

In a mobile communication network, in order to transmit user plane data, one or more Qos flows (Qos Flow) need to be established. As an important measure of communication quality, Qos parameters are usually used to indicate the characteristics of Qos flows. Different Qos flows correspond to different Qos parameters. Qos parameters may include but are not limited to: 5G Quality of Service Identifier (5QI), Allocation Retension Priority (ARP), Guaranteed Flow Bit Rate (GFBR), Maximum Flow Bit Rate ( Maximum Flow Bit Rate, MFBR), up/downlink maximum packet loss rate (UL/DL Maximum Packet Loss Rate, UL/DL MPLR), end-to-end packet delay budget (Packet Delay Budget, PDB), AN-PDB, Packet Error Rate (PER), priority level (Priority Level), average window (Averaging Window), resource type (Resource Type), maximum data burst volume (Maximum Data Burst Volume), UE aggregate maximum bit rate ( UE Aggregate Maximum Bit Rate, UE-AMBR), session aggregate maximum bit rate (Session Aggregate Maximum Bit Rate, Session-AMBR), etc.

Filter (Filter) contains characteristic parameters that describe data packets (such as some related parameters of IP data packets, some related parameters of Ethernet data packets), and is used to filter out specific data packets to bind to specific Qos flows. Here, the most commonly used Filter is the IP five-tuple, which is the source IP address, destination IP address, source port number, destination port number and protocol type.

Referring to Figure 3, UPF and UE will form a filter based on the combination of characteristic parameters of the data packet (the leftmost trapezoid and the rightmost parallelogram in Figure 3 represent filters), and filter the matching data transmitted on the user plane through the filter. The upstream or downstream data packet of the packet's characteristic parameters and bound to a certain Qos flow. The uplink Qos flow is bound by the UE, and the downlink Qos flow is bound by the UPF. In the Qos mechanism, one or more Qos flows can be mapped to a data radio bearer (Data Resource Bearer, DRB) for transmission. For a Qos flow, corresponding to a set of Qos parameters, the base station will establish a DRB based on the Qos parameters and bind the Qos flow to a specific DRB.

Qos flow is established triggered by SMF. When Qos needs to be adjusted, both the UE and the network side can trigger the PDU session modification process to change Qos. Taking the UE as an example, the UE can modify the Qos parameters of the Qos flow or establish a new Qos flow by sending a PDU Session Modification Request (PDU Session Modification Request) message. In other words, when the UE adjusts Qos, it needs to perform a session modification process and must obtain the consent of the network. Since the PDU session modification process takes a long time, and there is no guarantee that the modification will be successful, it will affect the behavior of the application, that is, the application cannot accurately determine whether and how long it can use the QoS it wants, which is difficult for many real-time services. , such as machine learning, neural network analysis, etc., will have a greater impact. There are many situations that cause Qos changes. As examples, the following situations can cause Qos changes: 1) Base station switching occurs; 2) Network congestion occurs (such as a sudden increase in the number of users); 3) UE moves into or out of a specific range. (Such as the service scope of the edge server).

In order to facilitate understanding of the technical solutions of the embodiments of the present application, the relevant terms of the embodiments of the present application are described below. The meanings of the following relevant terms can be optionally combined with the technical solutions of the embodiments of the present application, and they all belong to the implementation of the present application. Example of protection scope.

Cloud Gaming (CG): refers to a set of use cases in which the vast majority of game-related calculations (single or multiplayer) are offloaded from the UE to edge or remote servers.

Extended Reality (EXtended Reality, XR): It is a large-scale umbrella for multiple heterogeneous use cases and services. Mixed Reality, MR).

Extended Reality and media services (XRM): The combination of XR and media services technology.

Video Slice: A spatially distinct area in a video frame that is encoded separately from other areas in the same frame.

PDU Set: consists of one or more PDUs. These PDUs carry an information unit generated at the application layer (for example, frames or video clips of XRM services). This information has the same importance requirements at the application layer. . The application layer requires all PDUs in the PDU set to use the corresponding information unit. In some cases, when some PDUs are lost, the application layer can still recover some information units.

I-frame: As an intra-frame encoded picture, it is a complete picture that can be independently encoded and decoded like a JPG image file.

P-frame: As a predicted picture, it is not a complete frame and only contains image changes compared with the previous frame. If the reference frame is lost, the P frame cannot be decoded and displayed.

B-frame: As a bidirectional prediction picture, it contains the changes between the previous reference frame and the next reference frame. The more reference frames, the higher the compression ratio. However, B-frames can only be decoded if the previous and next reference frames are available.

A Group of Pictures (GOP): A collection of consecutive video frames. Generally, the first frame of a GOP is an I frame, and subsequent frames can be P frames or B frames.

For media services, I frames, P frames, B frames, etc. will be generated during the video compression encoding and decoding process. The PDU set is a group of PDUs. This group of PDUs represents a frame or a video clip. Each PDU in a PDU set is related to each other. Losing any PDU in a PDU set will cause the PDU set to be unable to be decoded successfully, resulting in the loss of part of the video image. I frames, P frames, and B frames have different degrees of importance. For example, an I frame is associated with multiple P frames. If the I frame is lost, all P frames cannot be decoded. If the P frame is lost, the I frame and other P frames can be decoded. Recovery, so the I frame is very important and cannot be lost. Currently, in air interface data transmission and processing, data packets are processed accordingly according to the Qos flow or data bearer where the data packet is located. Data packets on the same Qos flow or data bearer have the same processing method. Different processing methods are adopted depending on the situation. However, for PDU sets, PDUs in different PDU sets have different processing requirements. Using different processing methods for different PDUs (that is, data packets) can better improve the performance and user experience of multimedia services. To this end, the following technical solutions of the embodiments of the present application are proposed. It should be noted that the technical solutions of the embodiments of this application can be, but are not limited to, applied to 5G NR system architecture, for example, they can also be applied to future enhanced NR system architecture, etc.

In order to facilitate understanding of the technical solutions of the embodiments of the present application, the technical solutions of the present application are described in detail below through specific embodiments. The above related technologies can be arbitrarily combined with the technical solutions of the embodiments of the present application as optional solutions, and they all fall within the protection scope of the embodiments of the present application. The embodiments of this application include at least part of the following content.

For a GOP, it contains a group of frames, which may come from different Qos flows or from the same Qos flow. Each frame in the GOP has its own type, such as I frame, B frame, P frame, etc. As an implementation, the GOP can contain an I frame and at least one P frame and/or at least one B frame associated with it. . In order to be able to identify each frame belonging to a GOP, define a GOP identifier (such as GOP id or GOP SN or GOP index, etc.), and use the GOP identifier to identify a GOP, and each frame in the GOP will be associated with the GOP identifier. Thus, each frame belonging to a GOP is identified through the GOP identifier. It should be noted that the form of the GOP identification is not limited to GOP id or GOP SN or GOP index, etc. It can also be in other forms, such as a certain time interval or a certain period, and each frame within a certain time interval or a certain period belongs to one GOP.

For a frame, it is a PDU set, which is composed of multiple PDUs. In order to facilitate data transmission/retransmission and scheduling on the air interface, a PDU set identifier (such as PDU set id or PDU set SN or PDU set index, etc.) is defined for each PDU set, and a PDU set is identified by the PDU set identifier. The PDU set identifier is unique within a GOP.

For a PDU, in order to identify each PDU in a PDU set, a PDU identifier (such as PDU id or PDU SN or PDU index, etc.) is defined for each PDU, and a PDU identifier is identified by the PDU identifier. The PDU identifier is unique within the PDU set.

To sum up, each PDU can be associated with at least one of the following information: GOP identification, PDU set identification, PDU identification, and frame type.

Figure 4 is a schematic diagram of PDU set transmission provided by the embodiment of this application. As shown in Figure 4, the PDUs in a PDU set belong to a Qos flow, and the order between them is in sequence in the GPRS Tunnelling Protocol (GTP). ) is transmitted in the tunnel, that is, there will be no cross-transmission between PDU sets.

Figure 5 is a schematic flowchart 1 of the data transmission method provided by the embodiment of the present application. As shown in Figure 5, the data transmission method includes the following steps:

Step 501: The first protocol layer obtains attribute information of the first data packet, where the attribute information includes at least one of the following: specific Qos attributes, data type, data importance, and data priority.

Step 502: The first protocol layer performs specific processing on the first data packet based on the attribute information of the first data packet.

The technical solutions of the embodiments of this application are applied to communication equipment, which may be network equipment or terminal equipment. Taking downlink transmission as an example, the communication device is a network device, such as a base station. Taking uplink transmission as an example, the communication device is a terminal device. Each protocol layer in the embodiment of this application is the protocol layer of the communication device.

In the embodiment of this application, the first data packet generally refers to a data packet received by the first protocol layer from the upper protocol layer. The first protocol layer performs specific processing on the first data packet based on the attribute information of the first data packet. How the first protocol layer performs specific processing on the first data packet is described below.

Option One

The first protocol entity delivers the first data packet to the second protocol entity or the third protocol entity based on the attribute information of the first data packet, wherein the first protocol entity is located at the first protocol layer, The second protocol entity and the third protocol entity are located at the second protocol layer.

Specifically, if the attribute information of the first data packet is the first attribute information, the first protocol entity delivers the first data packet to the second protocol entity; if the attribute information of the first data packet is If the attribute information is the second attribute information or is not the first attribute information, the first protocol entity delivers the first data packet to the third protocol entity.

Here, optionally, the attribute information of the first data packet is first attribute information, including at least one of the following:

The specific Qos attribute of the first data packet is the first Qos attribute;

The data type of the first data packet is a first data type;

The data importance of the first data packet is the first importance;

The data priority of the first data packet is the first priority.

Here, the first Qos attribute is, for example, packet loss is not allowed or ACK/NACK feedback is required.

Here, the first data type is, for example, an I frame.

Here, the first importance level is, for example, a high importance level.

Here, the first priority is, for example, high priority.

For example: if the specific Qos attribute of the first data packet is that packet loss is not allowed or ACK/NACK feedback is required, and/or the data type of the first data packet is I frame, and/or the first data packet The data importance level is high, and/or the priority of the first data packet is high priority, then the first protocol entity delivers the first data packet to the second protocol entity.

Here, optionally, the attribute information of the first data packet is not the first attribute information, and includes at least one of the following:

The specific Qos attribute of the first data packet is not the first Qos attribute;

The data type of the first data packet is not the first data type;

The data importance of the first data packet is not the first importance;

The data priority of the first data packet is not the first priority.

Here, optionally, the attribute information of the first data packet is second attribute information, including at least one of the following:

The specific Qos attribute of the first data packet is the second Qos attribute;

The data type of the first data packet is the second data type;

The data importance of the first data packet is the second importance;

The data priority of the first data packet is the second priority.

Here, the second Qos attribute is, for example, allowing packet loss or not requiring ACK/NACK feedback.

Here, the second data type is, for example, a B frame and/or a P frame.

Here, the second importance level is, for example, a low importance level.

Here, the second priority is, for example, low priority.

For example: if the specific Qos attribute of the first data packet is to allow packet loss or does not require ACK/NACK feedback, and/or the data type of the first data packet is not an I frame, and/or the first data packet The data importance level is low, and/or the priority of the first data packet is low priority, then the first protocol entity delivers the first data packet to the third protocol entity.

In some optional implementations, the mode of the second protocol entity is an acknowledged mode (AM) mode, and the mode of the third protocol entity is an unacknowledged mode (UM). In other optional implementations, the mode of the second protocol entity is UM mode, and the mode of the third protocol entity is UM mode.

In some optional implementations, the first protocol entity, the second protocol entity and the third protocol entity belong to a first data bearer, and the first data bearer is configured through RRC signaling.

During specific implementation, as an optional method, the first protocol layer is a Packet Data Convergence Protocol (PDCP) layer, and the second protocol layer is a Radio Link Control (RLC) layer. )layer. Correspondingly, the first protocol entity is a PDCP entity, the second protocol entity is an AM RLC entity or a UM RLC entity, and the third protocol entity is a UM RLC entity.

Option II

The first protocol layer determines, based on the attribute information of the first data packet, whether to perform packet loss behavior for the first data packet after a packet loss timer times out.

Specifically, if the attribute information of the first data packet is the first attribute information, the first protocol layer determines not to perform packet loss behavior for the first data packet after the packet loss timer times out; if If the attribute information of the first data packet is the second attribute information or is not the first attribute information, the first protocol layer determines to perform packet loss behavior for the first data packet after the packet loss timer times out.

The specific Qos attribute of the first data packet is the first Qos attribute;

The data type of the first data packet is a first data type;

The data importance of the first data packet is the first importance;

The data priority of the first data packet is the first priority.

Here, the first data type is, for example, an I frame.

Here, the first importance level is, for example, a high importance level.

Here, the first priority is, for example, high priority.

For example: if the specific Qos attribute of the first data packet is that packet loss is not allowed or ACK/NACK feedback is required, and/or the data type of the first data packet is I frame, and/or the first data packet The data importance is high, and/or the priority of the first data packet is high priority, then the first protocol layer determines not to execute the first data packet after the packet loss timer expires. packet loss behavior.

The data type of the first data packet is not the first data type;

The data importance of the first data packet is not the first importance;

The data priority of the first data packet is not the first priority.

The data type of the first data packet is the second data type;

The data importance of the first data packet is the second importance;

The data priority of the first data packet is the second priority.

Here, the second data type is, for example, a B frame and/or a P frame.

Here, the second importance level is, for example, a low importance level.

Here, the second priority is, for example, low priority.

For example: if the specific Qos attribute of the first data packet is to allow packet loss or does not require ACK/NACK feedback, and/or the data type of the first data packet is not an I frame, and/or the first data packet The data importance level is low, and/or the priority of the first data packet is low priority, then the first protocol layer determines to execute the processing for the first data packet after the packet loss timer expires. Packet dropping behavior.

In specific implementation, as an optional method, the first protocol layer is a PDCP layer.

third solution

The first protocol layer determines whether to start a packet loss timer applicable to the first data packet based on the attribute information of the first data packet.

Specifically, if the attribute information of the first data packet is the first attribute information, the first protocol layer determines not to start the packet loss timer applicable to the first data packet; if the first data packet The attribute information is the second attribute information or is not the first attribute information, then the first protocol layer determines to start the packet loss timer applicable to the first data packet.

The specific Qos attribute of the first data packet is the first Qos attribute;

The data type of the first data packet is a first data type;

The data importance of the first data packet is the first importance;

The data priority of the first data packet is the first priority.

Here, the first data type is, for example, an I frame.

Here, the first importance level is, for example, a high importance level.

Here, the first priority is, for example, high priority.

For example: if the specific Qos attribute of the first data packet is that packet loss is not allowed or ACK/NACK feedback is required, and/or the data type of the first data packet is I frame, and/or the first data packet The data importance is high, and/or the priority of the first data packet is high priority, then the first protocol layer determines not to start the packet loss timer applicable to the first data packet.

The data type of the first data packet is not the first data type;

The data importance of the first data packet is not the first importance;

The data priority of the first data packet is not the first priority.

The data type of the first data packet is the second data type;

The data importance of the first data packet is the second importance;

The data priority of the first data packet is the second priority.

Here, the second data type is, for example, a B frame and/or a P frame.

Here, the second importance level is, for example, a low importance level.

Here, the second priority is, for example, low priority.

For example: if the specific Qos attribute of the first data packet is to allow packet loss or does not require ACK/NACK feedback, and/or the data type of the first data packet is not an I frame, and/or the first data packet The importance of the data is low, and/or the priority of the first data packet is low priority, then the first protocol layer determines to start a packet loss timer applicable to the first data packet.

It should be noted that for the packet discard timer (discard timer) in the above-mentioned scheme 2 and scheme 3, if the packet discard timer needs to be started, the discard timer will be started when the first protocol layer receives the data packet from the upper protocol layer. Packet timer. If the first protocol layer completes passing the data packet to the lower layer protocol while the packet loss timer is running, the packet loss timer will be stopped.

In this embodiment of the present application, the first protocol layer can obtain the attribute information of the first data packet in the following manner:

The first header corresponding to the first data packet carries the attribute information; and/or, a control data packet is transmitted after the PDU set where the PDU corresponding to the first data packet is located, and the control data packet carries the Describe attribute information. Based on this, the first protocol layer obtains the attribute information based on the first packet header and/or the control data packet.

Here, the control data packet is used to indicate the end of a PDU set and/or the start of the next PDU set.

Here, the first packet header is a packet header corresponding to the third protocol layer; and/or the control data packet is a control data packet corresponding to the third protocol layer. Wherein, the third protocol layer is an upper protocol layer of the first protocol layer.

During specific implementation, as an optional method, the first protocol layer is a PDCP layer, and the third protocol layer is a Service Data Adaptation Protocol (SDAP) layer. Correspondingly, the first protocol layer is a Service Data Adaptation Protocol (SDAP) layer. The packet header is an SDAP packet header, and the control data packet is an SDAP control PDU.

Figure 6 is a flow diagram 2 of the data transmission method provided by the embodiment of the present application. As shown in Figure 6, the data transmission method includes the following steps:

Step 601: The first node sends a first PDU to the second node, and the second node receives the first PDU sent by the first node. The first PDU is used to indicate to the second node a list of SNs that need to feed back ACK/NACK. .

Step 602: The second node sends a second PDU to the first node, and the first node receives the second PDU sent by the second node, and the second PDU is used to indicate to the first node ACK/NACK information corresponding to the SN list.

In this embodiment of the present application, both the first node and the second node belong to communication devices. The first node may be a network device (such as a base station), and the second node may be a terminal device, or the first node may be a terminal device, and the second node may be a terminal device. The node may be a network device (such as a base station), or the first node may be a first terminal device and the second node may be a second terminal device.

In this embodiment of the present application, before the first node sends the first PDU to the second node, the first node sends one or more data packets to the second node, and each data packet (that is, PDU) is associated with an SN. Then, the first node A node can indicate to the second node the SN list that needs to feed back ACK/NACK through the first PDU. In this way, the second node can perform corresponding ACK/NACK feedback according to the SN list. That is, the second node can provide the corresponding ACK/NACK feedback to the first node through the second PDU. Indicates the ACK/NACK information corresponding to the SN list.

It should be noted that the first PDU can also be called ACK/NACK feedback request PDU (ACK/NACK feedback request PDU), and the second PDU can also be called ACK/NACK feedback response PDU (ACK/NACK feedback response PDU). The application does not limit the names of the first PDU and the second PDU.

The following describes the formats of the first PDU and the second PDU.

Format of the first PDU

Format 1) In some optional implementations, the first PDU includes at least one of the following information:

First information, the first information is used to indicate the number of SNs that need to feed back ACK/NACK;

Second information, the second information is used to indicate the starting SN that needs to feed back ACK/NACK;

The first bitmap is used to indicate the SN after the starting SN that needs to feed back ACK/NACK.

Here, each bit in the first bitmap corresponds to an SN after the starting SN, and the value of the bit is used to indicate whether the SN corresponding to the bit needs to feed back ACK/NACK.

Further, the first PDU also includes at least one of the following information:

Sixth information, the sixth information is used to indicate whether the first PDU belongs to a data PDU or a control PDU;

Seventh information, the seventh information is used to indicate the type of control PDU to which the first PDU belongs;

Eighth information, the eighth information is used to indicate the identity of a process.

Format 2) In some optional implementations, the first PDU includes at least one of the following information:

Third information, the third information is used to indicate a list of SNs that need to feed back ACK/NACK.

Further, the first PDU also includes at least one of the following information:

Format 3) In some optional implementations, the first PDU includes at least one of the following information:

Fourth information, the fourth information is used to indicate the starting SN that needs to feed back ACK/NACK;

Fifth information, the fifth information is used to indicate the termination SN that needs to feed back ACK/NACK.

Further, the first PDU also includes at least one of the following information:

Format of the second PDU

In some optional implementations, the second PDU includes at least one of the following information:

A second bitmap, the second bitmap is used to indicate ACK/NACK information of multiple SNs after the starting SN.

Here, each bit in the second bitmap corresponds to an SN that needs feedback after the starting SN, and the value of the bit is used to indicate the ACK/NACK information of the SN corresponding to the bit.

Further, the second PDU also includes at least one of the following information:

Ninth information, the ninth information is used to indicate whether the second PDU belongs to a data PDU or a control PDU;

Tenth information, the tenth information is used to indicate the type of control PDU to which the second PDU belongs;

Eleventh information, the eleventh information is used to indicate the identity of a process.

The above solution of the embodiment of the present application can be applied to the PDCP layer, or can also be applied to the RLC layer.

As an application scenario, the above solution is applied to the PDCP layer. The first PDU is a first PDCP control PDU, the second PDU is a second PDCP control PDU, and the SN is carried in the PDCP PDU. For the PDCP layer, the list of SNs that need to feedback ACK/NACK can be determined in the following way:

The PDCP layer of the first node obtains the attribute information of the data packet; the PDCP layer of the first node determines a list of SNs that need to feed back ACK/NACK based on the attribute information; wherein the attribute information includes at least one of the following : Specific Qos attributes, data types, data importance, and data priority. Here, the way in which the PDCP layer of the first node obtains the attribute information of the data packet can refer to the relevant description shown in Figure 5. For example, the PDCP layer of the first node can obtain the attribute information of the data packet from the header of the data packet and/or the data packet. Obtain the attribute information from the control data packet after the PDU set where the corresponding PDU is located.

As an application scenario, the above solution is applied to the RLC layer. The first PDU is a first RLC control PDU, the second PDU is a second RLC control PDU, and the SN is carried in the RLC PDU. For the RLC layer, the SN list that needs to feedback ACK/NACK can be determined in the following way:

The PDCP layer of the first node obtains the attribute information of the data packet; the PDCP layer of the first node determines the data packet that needs to be fed back ACK/NACK based on the attribute information, and sends the data that needs to be fed back ACK/NACK. The packet is indicated to the RLC layer; the RLC layer of the first node determines the SN list that needs to feed back ACK/NACK based on the indication from the PDCP layer; wherein the attribute information includes at least one of the following: specific Qos attributes, data Type, data importance, data priority. Here, the way in which the PDCP layer of the first node obtains the attribute information of the data packet can refer to the relevant description shown in Figure 5. For example, the PDCP layer of the first node can obtain the attribute information of the data packet from the header of the data packet and/or the data packet. Obtain the attribute information from the control data packet after the PDU set where the corresponding PDU is located.

In some optional implementations, the first node determines, based on the second PDU, the PDU corresponding to the SN that the second node did not receive correctly; the first node determines the PDU corresponding to the SN that was not received correctly based on the first node. The attribute information of the PDU is used to determine whether to retransmit the PDU. The attribute information includes at least one of the following: specific Qos attributes, data type, data importance, and data priority.

Specifically, if the attribute information of the PDU is the first attribute information, it is determined to retransmit the PDU; if the attribute information of the PDU is the second attribute information or not the first attribute information, it is determined that the PDU is retransmitted. The above PDU will not be retransmitted.

Here, optionally, the attribute information of the PDU is first attribute information, including at least one of the following:

The specific Qos attribute of the PDU is the first Qos attribute;

The data type of the PDU is the first data type;

The data importance of the PDU is the first importance;

The data priority of the PDU is the first priority.

Here, the first data type is, for example, an I frame.

Here, the first importance level is, for example, a high importance level.

Here, the first priority is, for example, high priority.

For example: if the specific Qos attribute of the PDU does not allow packet loss or requires ACK/NACK feedback, and/or the data type of the PDU is I frame (that is, the PDU set in which the PDU is located is an I frame), and/or the data importance of the PDU is of high importance, and/or the priority of the PDU is high priority, then the first node determines to retransmit the PDU.

Here, optionally, the attribute information of the PDU is not the first attribute information, and includes at least one of the following:

The specific Qos attribute of the PDU is not the first Qos attribute;

The data type of the PDU is not the first data type;

The data importance of the PDU is not the first importance;

The data priority of the PDU is not the first priority.

Here, optionally, the attribute information of the PDU is second attribute information, including at least one of the following:

The specific Qos attribute of the PDU is the second Qos attribute;

The data type of the PDU is the second data type;

The data importance of the PDU is the second importance;

The data priority of the PDU is the second priority.

Here, the second data type is, for example, a B frame and/or a P frame.

Here, the second importance level is, for example, a low importance level.

Here, the second priority is, for example, low priority.

For example: if the specific Qos attribute of the PDU is to allow packet loss or does not require ACK/NACK feedback, and/or the data type of the PDU is not an I frame (that is, the PDU set in which the PDU is located is not an I frame), and/or the data importance of the PDU is of low importance, and/or the priority of the PDU is low priority, then the first node determines not to retransmit the PDU.

In some optional implementations, the first node determines whether to cancel the sending of a specific data packet based on the second PDU. Specifically, the first protocol layer of the first node determines whether to cancel the sending of the data packet based on the second PDU; and/or the first protocol layer of the first node determines whether to cancel the transmission of the data packet that has been submitted to the second protocol layer. data packet, and determine based on the second PDU whether to notify the second protocol layer to cancel the sending of the data packet through the first indication information; wherein the first protocol layer is the PDCP layer or the RLC layer, and the first protocol layer The second protocol layer is a lower protocol layer of the first protocol layer.

Here, the data packet to be canceled is determined based on the incorrectly received SN determined by the second PDU. That is, the first protocol layer of the first node determines the incorrectly received SN based on the second PDU, and determines to cancel the sent data packet based on the incorrectly received SN.

In some optional implementations, the first indication information is used to indicate at least one of the following:

Cancel the sent SN list;

Cancel the PDU set associated with the sent SN, that is, all data in the associated PDU set are canceled;

Cancel the frame associated with the sent SN, that is, all data in the associated frame are cancelled;

Cancel the GOP associated with the sent SN, that is, all data in the associated GOP are cancelled.

It should be noted that the "feedback about the SN" described in the embodiment of this application essentially refers to "the feedback about the data packet corresponding to the SN". For simplicity of description, the "feedback about the data packet corresponding to the SN" is described as " Feedback on SN".

The technical solutions of the embodiments of the present application are illustrated below with reference to specific application examples.

Application example one

1. The network side configures a dedicated data bearer (DRB) through RRC dedicated signaling. The DRB includes one PDCP entity and at least two RLC entities. Figure 7 illustrates one PDCP entity and two RLC entities. As an implementation method, the RLC1 entity is in AM mode, and the RLC2 entity is in UM mode; as another implementation method, both the RLC1 entity and the RLC2 entity are in UM mode.

2. After receiving the data packet from the SDAP layer, the PDCP layer determines the attribute information of the data packet. The attribute information includes at least one of the following: specific Qos attributes, data type, data importance, and data priority.

Here, the attribute information is attribute information at packet granularity (per data). Different data packets in a Qos flow have independent attribute information. That is to say, different data packets in a Qos flow can have different attribute information.

The PDCP layer obtains the attribute information of the data packet, including but not limited to:

Method 1: The SDAP header of the SDAP PDU corresponding to the data packet contains attribute information, and the PDCP layer obtains the attribute information of the data packet from the SDAP header.

Method 2: The SDAP control PDU contains attribute information, and the PDCP layer obtains the attribute information of the data packet from the SDAP header. Here, the SDAP control PDU is used to split different PDU sets, located after one PDU set and before the next PDU set.

Method 3: The SDAP header of the SDAP PDU corresponding to the data packet contains indication information and/or the SDAP control PDU contains indication information. After obtaining the indication information, the PDCP layer determines the attribute information of the data packet based on the indication information. Here, the mapping relationship between indication information and attribute information is configured through RRC signaling.

3. The PDCP layer assembles the data packet into a PDCP PDU based on the attribute information of the data packet, and then submits it to the RLC1 entity or RLC2 entity.

Specifically, if the specific Qos attribute of the data packet is that packet loss is not allowed or ACK/NACK feedback is required, and/or the data type of the data packet is I frame, and/or the data importance of the data packet is high importance, and/ Or the priority of the data packet is high priority, then the data packet is delivered to the RLC1 entity. If the specific Qos attribute of the data packet is to allow packet loss or does not require ACK/NACK feedback, and/or the data type of the data packet is not an I frame, and/or the data importance of the data packet is low importance, and/or the data packet The priority is low priority, then the data packet is delivered to the RLC2 entity.

Application example two

1. The network side configures a dedicated data bearer (DRB) through RRC dedicated signaling. The DRB includes a PDCP entity and at least one RLC entity. In the configuration of the PDCP entity, a packet discard timer (discard timer) is configured.

3. Based on the attribute information of the data packet, the PDCP layer determines whether to perform packet loss behavior for the data packet after the packet loss timer expires or determines whether to start a packet loss timer applicable to the data packet.

Specifically, if the specific Qos attribute of the data packet is that packet loss is not allowed or ACK/NACK feedback is required, and/or the data type of the data packet is I frame, and/or the data importance of the data packet is high importance, and/ Or if the priority of the data packet is high priority, no packet loss behavior will be performed for the data packet or the packet loss timer applicable to the data packet will not be started after the packet loss timer times out. If the specific Qos attribute of the data packet is to allow packet loss or does not require ACK/NACK feedback, and/or the data type of the data packet is not an I frame, and/or the data importance of the data packet is low importance, and/or the data packet The priority is low priority, then after the packet loss timer times out, the packet loss behavior for the data packet will be performed or the packet loss timer applicable to the data packet will be started.

Application example three

The PDCP layer can determine the attribute information of the data packet through the above related solutions. The PDCP layer can determine which data packets need ACK/NACK feedback based on the attribute information of the data packet, that is, determine the SN list that needs ACK/NACK feedback. Each SN is associated with a data packet. Then at the PDCP layer, feedback interaction can be achieved. Figure 8 shows a schematic diagram of the interaction between the sending end (i.e., the first node) and the receiving end (i.e., the second node). The sending end sends an ACK/NACK feedback request PDU (i.e., the first PDU) to the receiving end, and the receiving end sends The sending end sends an ACK/NACK feedback response PDU (ie, the second PDU). Here, the PDCP layer defines two types of PDCP control PDUs, namely PDCP control PDU on the sending end side (ie, ACK/NACK feedback request PDU) and PDCP control PDU on the receiving end side (ie, ACK/NACK feedback response PDU). Among them, the ACK/NACK feedback request PDU is used by the sending end to indicate to the receiving end the SN list that requires ACK/NACK feedback. When the receiving end receives the ACK/NACK feedback request PDU sent by the sending end, it performs ACK/NACK feedback according to the SN list indicated by the sending end, that is, sends an ACK/NACK feedback response PDU to the sending end.

The format of the ACK/NACK feedback request PDU (hereinafter referred to as PDCP PDU) may, but is not limited to, include the following formats:

Format 1: As shown in Figure 9-1, PDCP PDU contains the following information: D/C information, PDU type (PDU Type), process identification (Transaction ID), number of SN (Number of SN), starting SN, bitmap (bitmap). The meaning of this information is explained below:

D/C information: used to indicate whether the PDCP PDU is a data PDU or a control PDU. Optionally, the D/C information occupies 1 bit. As an example, the meaning of the value of this 1 bit is as shown in Table 1 below. Here, the value of 1 bit is 0, which is used to indicate that the PDCP PDU is a control PDU.

1比特取值1 bit value	含义meaning
00	控制PDU Control PDU
11	数据PDUData PDU

Table 1

PDU type: used to indicate the type of control PDU. Optionally, the PDU type occupies 3 bits. As an example, the corresponding meanings of the 3-bit values are as shown in Table 2 below. Here, the value of 3 bits is 011, which is used to indicate that the PDCP PDU is a control PDU for ACK/NACK feedback request.

3比特取值3 bit value	含义meaning
000000	PDCP状态报告PDCP status report
001001	分散ROHC反馈Decentralized ROHC feedback
010010	EHC反馈EHC feedback
011011	ACK/NACK反馈请求ACK/NACK feedback request
100-111100-111	保留reserve

Table 2

Process identifier: used to identify a process, that is, to identify two PDUs in a process (i.e., ACK/NACK feedback request PDU and ACK/NACK feedback response PDU). The process identifiers in the two PDUs in a process are the same.

Number of SNs: Used to indicate the number of PDCP SNs that need to feedback ACK/NACK.

Starting SN: Used to indicate the starting PDCP SN that needs to feedback ACK/NACK.

Bitmap: used to indicate the SN after the starting SN that needs to feedback ACK/NACK. Specifically, if a certain bit in the bitmap is set to 1, it means that the SN corresponding to the bit needs feedback. If a certain bit in the bitmap is set to 0, it means that the SN corresponding to the bit does not need feedback. Here, the SN corresponding to the i-th bit in the bitmap = starting SN+i, and i is a positive integer.

Format 2: As shown in Figure 9-2, PDCP PDU contains the following information: D/C information, PDU Type (PDU Type), process identification (Transaction ID), Number of SN (Number of SN), and SN list. The meaning of the D/C information, PDU Type, Transaction ID, and Number of SN in this information can be explained by referring to the description related to the aforementioned format. The meaning of the SN list in this information is explained as follows:

SNi: Indicates the PDCP SN that requires ACK/NACK feedback, i is a positive integer.

Format 3: As shown in Figure 9-3, PDCP PDU contains the following information: D/C information, PDU type (PDU Type), process identification (Transaction ID), SN number (Number of SN), and starting SN. The meaning of this information can be explained by referring to the description related to Format 1 mentioned above.

Format 4: As shown in Figure 9-4, PDCP PDU contains the following information: D/C information, PDU type (PDU Type), process identification (Transaction ID), SN number (Number of SN), and termination SN. The meaning of the D/C information, PDU Type, Transaction ID, and Number of SN in this information can be explained by referring to the description related to the aforementioned format. The meaning of the termination SN in these messages is explained as follows:

Termination SN: Used to indicate the termination PDCP SN that requires ACK/NACK feedback.

Format 5: As shown in Figure 9-5, PDCP PDU contains the following information: D/C information, PDU type (PDU Type), process identification (Transaction ID), number of SN (Number of SN), starting SN, and ending SN . For the meaning of the D/C information, PDU Type, Transaction ID, Number of SN, and starting SN in this information, please refer to the description related to the aforementioned format. The meaning of the termination SN in these messages can be explained with reference to the description of Format 4.

The format of the ACK/NACK feedback response PDU (hereinafter referred to as PDCP PDU) may, but is not limited to, include the following formats:

Format A: As shown in Figure 10, PDCP PDU contains the following information: D/C information, PDU type (PDU Type), process identification (Transaction ID), number of SN (Number of SN), starting SN, bitmap ). The meaning of this information is explained below:

D/C information: used to indicate whether the PDCP PDU is a data PDU or a control PDU. Optionally, the D/C information occupies 1 bit. As an example, the meaning of the value of this 1 bit is as shown in Table 3 below. Here, the value of 1 bit is 0, which is used to indicate that the PDCP PDU is a control PDU.

table 3

PDU type: used to indicate the type of control PDU. Optionally, the PDU type occupies 3 bits. As an example, the corresponding meanings of the 3-bit values are as shown in Table 4 below. Here, the value of 3 bits is 011, which is used to indicate that the PDCP PDU is a control PDU for ACK/NACK feedback response.

3比特取值3 bit value	含义meaning
000000	PDCP状态报告PDCP status report
001001	分散ROHC反馈Decentralized ROHC feedback
010010	EHC反馈EHC feedback
011011	ACK/NACK反馈响应ACK/NACK feedback response
100-111100-111	保留reserve

Table 4

Bitmap: used to indicate the starting SN and the ACK/NACK information corresponding to several consecutive SNs that need to feedback ACK/NACK. Specifically, if a certain bit in the bitmap is set to 1, it means that the SN corresponding to the bit returns ACK. If a certain bit in the bitmap is set to 0, it means that the SN corresponding to the bit returns NACK. Here, the SN corresponding to the i-th bit in the bitmap = starting SN+i-1, and i is a positive integer.

Application example four

The PDCP layer can determine the attribute information of the data packet through the above related solutions, and the PDCP layer can determine which data packets require ACK/NACK feedback based on the attribute information of the data packet. The PDCP layer indicates "which data packets require ACK/NACK feedback" to the RLC layer, for example, by carrying indication information in the PDCP header. The RLC layer determines which data packets require ACK/NACK feedback according to the instructions of the PDCP layer, that is, determines the SN list that requires ACK/NACK feedback. Each SN is associated with a data packet. Then at the RLC layer, feedback interaction can be achieved. It should be noted that at the RLC layer, for RLC entities in UM mode, feedback for specific RLC PDUs can be implemented. For RLC PDUs that need feedback, the RLC PDU needs to carry SN regardless of whether the segmentation process is performed or not. If there is no segmentation and no feedback requirement, the RLC PDU does not need to carry the SN number.

For the RLC layer, the sending end sends an ACK/NACK feedback request PDU (ie, the first PDU) to the receiving end, and the receiving end sends an ACK/NACK feedback response PDU (ie, the second PDU) to the sending end. Here, the RLC layer defines two RLC control PDUs, namely the RLC control PDU on the sending end side (ie, ACK/NACK feedback request PDU) and the RLC control PDU on the receiving end side (ie, ACK/NACK feedback response PDU). Among them, the ACK/NACK feedback request PDU is used by the sending end to indicate to the receiving end the SN list that requires ACK/NACK feedback. When the receiving end receives the ACK/NACK feedback request PDU sent by the sending end, it performs ACK/NACK feedback according to the SN list indicated by the sending end, that is, sends an ACK/NACK feedback response PDU to the sending end.

Here, the format of the ACK/NACK feedback request PDU and the format of the ACK/NACK feedback response PDU are similar to the relevant solution of the aforementioned application example 3. Just replace the relevant description of "PDCP" with "RLC" and will not be described again.

Application example five

After the sender receives the ACK/NACK feedback response PDU from the receiver, it determines the data packets that the receiver did not receive correctly based on the ACK/NACK feedback response PDU. The RLC layer or PDCP layer of the sender determines based on the attribute information of the incorrectly received data packets. Whether to retransmit it. Here, the attribute information includes at least one of the following: specific Qos attributes, data type, data importance, and data priority.

Specifically, if the specific Qos attribute of the data packet is that packet loss is not allowed or ACK/NACK feedback is required, and/or the data type of the data packet is I frame, and/or the data importance of the data packet is high importance, and/ Or the priority of the data packet is high priority, then it is determined to retransmit the data packet. If the specific Qos attribute of the data packet is to allow packet loss or does not require ACK/NACK feedback, and/or the data type of the data packet is not an I frame, and/or the data importance of the data packet is low importance, and/or the data packet If the priority is low priority, it is determined that the data packet will not be retransmitted.

Application example six

After the sending end receives the ACK/NACK feedback response PDU from the receiving end, it determines the data packets that the receiving end did not receive correctly based on the ACK/NACK feedback response PDU. The RLC layer or PDCP layer of the sending end uses the attribute information of the incorrectly received data packets. Determine whether to cancel the sending of a packet. At the same time, for data packets that have been submitted to the lower protocol layer, the RLC layer or PDCP layer can instruct the lower protocol layer to cancel the sending of certain data packets. The indication information may be used to indicate at least one of the following:

Cancel the sent SN list;

The technical solutions of the embodiments of this application can implement different processing methods for different data packets, thereby better improving the performance and user experience of multimedia services.

The preferred embodiments of the present application have been described in detail above with reference to the accompanying drawings. However, the present application is not limited to the specific details of the above-mentioned embodiments. Within the scope of the technical concept of the present application, various simple modifications can be made to the technical solutions of the present application. These simple modifications all belong to the protection scope of this application. For example, each specific technical feature described in the above-mentioned specific embodiments can be combined in any suitable way without conflict. In order to avoid unnecessary repetition, this application will no longer describe various possible combinations. Specify otherwise. For another example, any combination of various embodiments of the present application can be carried out. As long as they do not violate the idea of the present application, they should also be regarded as the contents disclosed in the present application. For another example, on the premise of no conflict, each embodiment described in this application and/or the technical features in each embodiment can be arbitrarily combined with the existing technology, and the technical solution obtained after the combination shall also fall within the scope of this application. protected range.

It should also be understood that in the various method embodiments of the present application, the size of the sequence numbers of the above-mentioned processes does not mean the order of execution. The execution order of each process should be determined by its functions and internal logic, and should not be used in this application. The implementation of the examples does not constitute any limitations. In addition, in the embodiments of this application, the terms "downlink", "uplink" and "sidelink" are used to indicate the transmission direction of signals or data, where "downlink" is used to indicate that the transmission direction of signals or data is from the station. The first direction to the user equipment of the cell, "uplink" is used to indicate that the transmission direction of the signal or data is the second direction from the user equipment of the cell to the site, and "sidelink" is used to indicate that the transmission direction of the signal or data is A third direction sent from User Device 1 to User Device 2. For example, "downlink signal" indicates that the transmission direction of the signal is the first direction. In addition, in the embodiment of this application, the term "and/or" is only an association relationship describing associated objects, indicating that three relationships can exist. Specifically, A and/or B can represent three situations: A exists alone, A and B exist simultaneously, and B exists alone. In addition, the character "/" in this article generally indicates that the related objects are an "or" relationship.

Figure 11 is a schematic structural diagram of a data transmission device provided by an embodiment of the present application. The device has a first protocol layer 1101;

The first protocol layer 1101 is used to obtain the attribute information of the first data packet; based on the attribute information of the first data packet, perform specific processing for the first data packet;

In some optional implementations, the device also has a second protocol layer 1102;

The first protocol entity delivers the first data packet to the second protocol entity or the third protocol entity based on the attribute information of the first data packet, wherein the first protocol entity is located in the first protocol layer 1101 , the second protocol entity and the third protocol entity are located in the second protocol layer 1102.

In some optional implementations, the mode of the second protocol entity is AM mode or UM mode, and the mode of the third protocol entity is UM mode.

In some optional implementations, if the attribute information of the first data packet is the first attribute information, the first protocol entity delivers the first data packet to the second protocol entity; if the If the attribute information of the first data packet is the second attribute information or is not the first attribute information, then the first protocol entity delivers the first data packet to the third protocol entity.

In some optional implementations, the first protocol layer 1101 is used to determine, based on the attribute information of the first data packet, whether to perform packet loss behavior for the first data packet after the packet loss timer expires. ; Or, based on the attribute information of the first data packet, determine whether to start a packet loss timer applicable to the first data packet.

In some optional implementations, if the attribute information of the first data packet is the first attribute information, the first protocol layer 1101 determines not to perform processing for the first data packet after the packet loss timer times out. Packet loss behavior; if the attribute information of the first data packet is the second attribute information or not the first attribute information, the first protocol layer 1101 determines to execute the packet loss behavior for the first data packet after the packet loss timer expires. packet loss behavior.

In some optional implementations, if the attribute information of the first data packet is the first attribute information, the first protocol layer 1101 determines not to start the packet loss timer applicable to the first data packet; if If the attribute information of the first data packet is the second attribute information or is not the first attribute information, the first protocol layer 1101 determines to start the packet loss timer applicable to the first data packet.

In some optional implementations, the attribute information of the first data packet is first attribute information, including at least one of the following:

The specific Qos attribute of the first data packet is the first Qos attribute;

The data type of the first data packet is a first data type;

The data importance of the first data packet is the first importance;

The data priority of the first data packet is the first priority.

In some optional implementations, the attribute information of the first data packet is not the first attribute information, and includes at least one of the following:

The data type of the first data packet is not the first data type;

The data importance of the first data packet is not the first importance;

The data priority of the first data packet is not the first priority.

In some optional implementations, the attribute information of the first data packet is second attribute information, including at least one of the following:

The data type of the first data packet is the second data type;

The data importance of the first data packet is the second importance;

The data priority of the first data packet is the second priority.

In some optional implementations, the first packet header corresponding to the first data packet carries the attribute information; and/or, a control data packet is transmitted after the PDU set in which the PDU corresponding to the first data packet is located. , the control data packet carries the attribute information.

In some optional implementations, the first protocol layer 1101 obtains the attribute information based on the first packet header and/or the control data packet.

In some optional implementations, the device also has a third protocol layer 1103; the first header is a header corresponding to the third protocol layer 1103; and/or the control data packet is a header corresponding to the third protocol layer 1103. control packet.

In some optional implementations, the third protocol layer 1103 is an SDAP layer, correspondingly, the first packet header is an SDAP packet header, and the control data packet is an SDAP control PDU.

In some optional implementations, the control data packet is used to indicate the end of a PDU set and/or the start of the next PDU set.

In some optional implementations, the second protocol layer is an RLC layer.

In some optional implementations, the first protocol layer is a PDCP layer.

Those skilled in the art should understand that the relevant description of the above-mentioned data transmission device in the embodiment of the present application can be understood with reference to the relevant description of the data transmission method in the embodiment of the present application.

Figure 12 is a schematic diagram 2 of the structure of a data transmission device provided by an embodiment of the present application. It is applied to the first node. The device includes:

The sending unit 1201 is configured to send a first PDU to the second node, where the first PDU is used to indicate to the second node a list of SNs that need to feed back ACK/NACK;

The receiving unit 1202 is configured to receive a second PDU sent by the second node, where the second PDU is used to indicate ACK/NACK information corresponding to the SN list to the first node.

In some optional implementations, the first PDU includes at least one of the following information:

In some optional implementations, each bit in the first bitmap corresponds to an SN after the starting SN, and the value of the bit is used to indicate whether the SN corresponding to the bit needs to feedback ACK/ NACK.

In some optional implementations, the first PDU also includes at least one of the following information:

In some optional implementations, each bit in the second bitmap corresponds to an SN that requires feedback after the starting SN, and the value of the bit is used to indicate the ACK of the SN corresponding to the bit. /NACK message.

In some optional implementations, the second PDU also includes at least one of the following information:

In some optional implementations, the first PDU is a first PDCP control PDU, the second PDU is a second PDCP control PDU, and the SN is carried in the PDCP PDU.

In some optional implementations, the device further includes: a processing unit 1203, configured to obtain attribute information of the data packet through the PDCP layer; and determine a list of SNs that need to feed back ACK/NACK based on the attribute information through the PDCP layer; wherein , the attribute information includes at least one of the following: specific Qos attributes, data type, data importance, and data priority.

In some optional implementations, the first PDU is a first RLC control PDU, the second PDU is a second RLC control PDU, and the SN is carried in the RLC PDU.

In some optional implementations, the device further includes: a processing unit 1203, configured to obtain the attribute information of the data packet through the PDCP layer; determine the data packet that requires ACK/NACK feedback based on the attribute information through the PDCP layer, and Indicate the data packet that needs to feed back ACK/NACK to the RLC layer; the RLC layer determines the list of SNs that need to feed back ACK/NACK based on the indication from the PDCP layer; wherein the attribute information includes at least one of the following: Specific Qos attributes, data types, data importance, and data priority.

In some optional implementations, the device further includes: a processing unit 1203, configured to determine, based on the second PDU, the PDU corresponding to the SN that the second node did not receive correctly; The attribute information of the corresponding PDU determines whether to retransmit the PDU. The attribute information includes at least one of the following: specific Qos attributes, data type, data importance, and data priority.

In some optional implementations, the processing unit 1203 is configured to determine to retransmit the PDU if the attribute information of the PDU is the first attribute information; if the attribute information of the PDU is the second attribute The information is either or is not the first attribute information, then it is determined not to retransmit the PDU.

In some optional implementations, the attribute information of the PDU is first attribute information, including at least one of the following:

The specific Qos attribute of the PDU is the first Qos attribute;

The data type of the PDU is the first data type;

The data importance of the PDU is the first importance;

The data priority of the PDU is the first priority.

In some optional implementations, the attribute information of the PDU is not the first attribute information, and includes at least one of the following:

The specific Qos attribute of the PDU is not the first Qos attribute;

The data type of the PDU is not the first data type;

The data importance of the PDU is not the first importance;

The data priority of the PDU is not the first priority.

In some optional implementations, the attribute information of the PDU is second attribute information, including at least one of the following:

The specific Qos attribute of the PDU is the second Qos attribute;

The data type of the PDU is the second data type;

The data importance of the PDU is the second importance;

The data priority of the PDU is the second priority.

In some optional implementations, the apparatus further includes: a processing unit 1203, configured to determine whether to cancel the sending of a specific data packet based on the second PDU.

In some optional implementations, the processing unit 1203 is configured to determine whether to cancel the sending of the data packet based on the second PDU through the first protocol layer; and/or, through the first protocol layer, determine whether to cancel the transmission of the data packet that has been submitted to the first PDU. For the data packet of the second protocol layer, it is determined based on the second PDU whether to notify the second protocol layer to cancel the sending of the data packet through the first indication information; wherein the first protocol layer is the PDCP layer or the RLC layer, The second protocol layer is a lower protocol layer of the first protocol layer.

In some optional implementations, the data packet sent is canceled based on the incorrectly received SN determination determined by the second PDU.

Cancel the sent SN list;

Cancel the PDU set associated with the sent SN;

Cancel the frame associated with the sent SN;

Cancel the GOP associated with the sent SN.

Figure 13 is a schematic diagram 3 of the structure of a data transmission device provided by an embodiment of the present application. It is applied to the second node. The device includes:

The receiving unit 1301 is configured to receive a first PDU sent by the first node, where the first PDU is used to indicate to the second node a list of SNs that need to feed back ACK/NACK;

The sending unit 1302 is configured to send a second PDU to the first node, where the second PDU is used to indicate to the first node the ACK/NACK information corresponding to the SN list.

Figure 14 is a schematic structural diagram of a communication device 1400 provided by an embodiment of the present application. The communication device can be a terminal device or a network device. The communication device 1400 shown in Figure 14 includes a processor 1410. The processor 1410 can call and run a computer program from the memory to implement the method in the embodiment of the present application.

Optionally, as shown in Figure 14, the communication device 1400 may further include a memory 1420. The processor 1410 can call and run the computer program from the memory 1420 to implement the method in the embodiment of the present application.

The memory 1420 may be a separate device independent of the processor 1410, or may be integrated into the processor 1410.

Optionally, as shown in Figure 14, the communication device 1400 may also include a transceiver 1430, and the processor 1410 may control the transceiver 1430 to communicate with other devices. Specifically, it may send information or data to other devices, or receive other devices. Information or data sent by the device.

Among them, the transceiver 1430 may include a transmitter and a receiver. The transceiver 1430 may further include an antenna, and the number of antennas may be one or more.

The communication device 1400 can implement the corresponding processes implemented by each method in the embodiment of the present application. For the sake of brevity, details will not be described again here.

Figure 15 is a schematic structural diagram of a chip according to an embodiment of the present application. The chip 1500 shown in Figure 15 includes a processor 1510. The processor 1510 can call and run a computer program from the memory to implement the method in the embodiment of the present application.

Optionally, as shown in Figure 15, the chip 1500 may also include a memory 1520. The processor 1510 can call and run the computer program from the memory 1520 to implement the method in the embodiment of the present application.

The memory 1520 may be a separate device independent of the processor 1510, or may be integrated into the processor 1510.

Optionally, the chip 1500 may also include an input interface 1530. The processor 1510 can control the input interface 1530 to communicate with other devices or chips. Specifically, it can obtain information or data sent by other devices or chips.

Optionally, the chip 1500 may also include an output interface 1540. The processor 1510 can control the output interface 1540 to communicate with other devices or chips. Specifically, it can output information or data to other devices or chips.

This chip can be applied to the communication device in the embodiment of the present application, and the chip can implement the corresponding processes implemented by the communication device in each method of the embodiment of the present application. For the sake of brevity, details will not be repeated here.

It should be understood that the chips mentioned in the embodiments of this application may also be called system-on-chip, system-on-a-chip, system-on-chip or system-on-chip, etc.

Figure 16 is a schematic block diagram of a communication system 1600 provided by an embodiment of the present application. As shown in Figure 16, the communication system 1600 includes a terminal device 1610 and a network device 1620.

Among them, the terminal device 1610 can be used to implement the corresponding functions implemented by the terminal device in the above method, and the network device 1620 can be used to implement the corresponding functions implemented by the network device in the above method. For the sake of brevity, no details will be described here. .

It should be understood that the processor in the embodiment of the present application may be an integrated circuit chip and has signal processing capabilities. During the implementation process, each step of the above method embodiment can be completed through an integrated logic circuit of hardware in the processor or instructions in the form of software. The above-mentioned processor can be a general-purpose processor, a digital signal processor (Digital Signal Processor, DSP), an application specific integrated circuit (Application Specific Integrated Circuit, ASIC), an off-the-shelf programmable gate array (Field Programmable Gate Array, FPGA) or other available processors. Programmed logic devices, discrete gate or transistor logic devices, discrete hardware components. Each method, step and logical block diagram disclosed in the embodiment of this application can be implemented or executed. A general-purpose processor may be a microprocessor or the processor may be any conventional processor, etc. The steps of the method disclosed in conjunction with the embodiments of the present application can be directly implemented by a hardware decoding processor, or executed by a combination of hardware and software modules in the decoding processor. The software module can be located in random access memory, flash memory, read-only memory, programmable read-only memory or electrically erasable programmable memory, registers and other mature storage media in this field. The storage medium is located in the memory, and the processor reads the information in the memory and completes the steps of the above method in combination with its hardware.

It can be understood that the memory in the embodiment of the present application may be a volatile memory or a non-volatile memory, or may include both volatile and non-volatile memories. Among them, non-volatile memory can be read-only memory (Read-Only Memory, ROM), programmable read-only memory (Programmable ROM, PROM), erasable programmable read-only memory (Erasable PROM, EPROM), electrically removable memory. Erase programmable read-only memory (Electrically EPROM, EEPROM) or flash memory. Volatile memory may be Random Access Memory (RAM), which is used as an external cache. By way of illustration, but not limitation, many forms of RAM are available, such as static random access memory (Static RAM, SRAM), dynamic random access memory (Dynamic RAM, DRAM), synchronous dynamic random access memory (Synchronous DRAM, SDRAM), double data rate synchronous dynamic random access memory (Double Data Rate SDRAM, DDR SDRAM), enhanced synchronous dynamic random access memory (Enhanced SDRAM, ESDRAM), synchronous link dynamic random access memory (Synchlink DRAM, SLDRAM) ) and direct memory bus random access memory (Direct Rambus RAM, DR RAM). It should be noted that the memory of the systems and methods described herein is intended to include, but is not limited to, these and any other suitable types of memory.

It should be understood that the above memory is an exemplary but not restrictive description. For example, the memory in the embodiment of the present application can also be a static random access memory (static RAM, SRAM), a dynamic random access memory (dynamic RAM, DRAM), Synchronous dynamic random access memory (synchronous DRAM, SDRAM), double data rate synchronous dynamic random access memory (double data rate SDRAM, DDR SDRAM), enhanced synchronous dynamic random access memory (enhanced SDRAM, ESDRAM), synchronous connection Dynamic random access memory (synch link DRAM, SLDRAM) and direct memory bus random access memory (Direct Rambus RAM, DR RAM) and so on. That is, memories in embodiments of the present application are intended to include, but are not limited to, these and any other suitable types of memories.

Embodiments of the present application also provide a computer-readable storage medium for storing computer programs. The computer-readable storage medium can be applied to the communication device in the embodiment of the present application, and the computer program causes the computer to execute the corresponding processes implemented by the communication device in the various methods of the embodiment of the present application. For the sake of brevity, the details are not repeated here.

An embodiment of the present application also provides a computer program product, including computer program instructions. The computer program product can be applied to the communication device in the embodiment of the present application, and the computer program instructions cause the computer to execute the corresponding processes implemented by the communication device in the various methods of the embodiment of the present application. For the sake of brevity, the details will not be described again.

An embodiment of the present application also provides a computer program. This computer program can be applied to the communication device in the embodiment of the present application. When the computer program is run on the computer, it causes the computer to execute the corresponding processes implemented by the communication device in each method of the embodiment of the present application. For the sake of brevity, this is not mentioned here. Again.

Those of ordinary skill in the art will appreciate that the units and algorithm steps of each example described in conjunction with the embodiments disclosed herein can be implemented with electronic hardware, or a combination of computer software and electronic hardware. Whether these functions are performed in hardware or software depends on the specific application and design constraints of the technical solution. Skilled artisans may implement the described functionality using different methods for each specific application, but such implementations should not be considered beyond the scope of this application.

Those skilled in the art can clearly understand that for the convenience and simplicity of description, the specific working processes of the systems, devices and units described above can be referred to the corresponding processes in the foregoing method embodiments, and will not be described again here.

In the several embodiments provided in this application, it should be understood that the disclosed systems, devices and methods can be implemented in other ways. For example, the device embodiments described above are only illustrative. For example, the division of the units is only a logical function division. In actual implementation, there may be other division methods. For example, multiple units or components may be combined or can be integrated into another system, or some features can be ignored, or not implemented. On the other hand, the coupling or direct coupling or communication connection between each other shown or discussed may be through some interfaces, indirect coupling or communication connection of devices or units, which may be in electrical, mechanical or other forms.

The units described as separate components may or may not be physically separated, and the components shown as units may or may not be physical units, that is, they may be located in one place, or they may be distributed to multiple network units. Some or all of the units can be selected according to actual needs to achieve the purpose of the solution of this embodiment.

In addition, each functional unit in each embodiment of the present application can be integrated into one processing unit, each unit can exist physically alone, or two or more units can be integrated into one unit.

If the functions are implemented in the form of software functional units and sold or used as independent products, they can be stored in a computer-readable storage medium. Based on this understanding, the technical solution of the present application is essentially or the part that contributes to the existing technology or the part of the technical solution can be embodied in the form of a software product. The computer software product is stored in a storage medium, including Several instructions are used to cause a computer device (which may be a personal computer, a server, or a network device, etc.) to execute all or part of the steps of the methods described in various embodiments of this application. The aforementioned storage media include: U disk, mobile hard disk, read-only memory (Read-Only Memory,) ROM, random access memory (Random Access Memory, RAM), magnetic disk or optical disk and other media that can store program code. .

The above are only specific embodiments of the present application, but the protection scope of the present application is not limited thereto. Any person familiar with the technical field can easily think of changes or substitutions within the technical scope disclosed in the present application. should be covered by the protection scope of this application. Therefore, the protection scope of this application should be determined by the protection scope of the claims.

Claims

A data transmission method, the method includes:

The first protocol layer obtains attribute information of the first data packet;

The first protocol layer performs specific processing on the first data packet based on the attribute information of the first data packet;

Wherein, the attribute information includes at least one of the following: specific quality of service Qos attributes, data type, data importance, and data priority.
The method according to claim 1, wherein the first protocol layer performs specific processing for the first data packet based on the attribute information of the first data packet, including:

The first protocol entity delivers the first data packet to the second protocol entity or the third protocol entity based on the attribute information of the first data packet, wherein the first protocol entity is located at the first protocol layer, The second protocol entity and the third protocol entity are located at the second protocol layer.
The method according to claim 2, wherein the first protocol entity, the second protocol entity and the third protocol entity belong to a first data bearer, and the first data bearer uses Radio Resource Control (RRC) signaling. configuration.
The method according to claim 2, wherein the mode of the second protocol entity is an acknowledgment mode AM mode or a non-acknowledgment mode UM mode, and the mode of the third protocol entity is a non-acknowledgement mode UM mode.
The method according to any one of claims 2 to 4, wherein the first protocol entity delivers the first data packet to the second protocol entity or a third party based on the attribute information of the first data packet. Agreement entities include:

If the attribute information of the first data packet is the first attribute information, the first protocol entity delivers the first data packet to the second protocol entity;

If the attribute information of the first data packet is the second attribute information or is not the first attribute information, the first protocol entity delivers the first data packet to the third protocol entity.
The method according to claim 1, wherein the first protocol layer performs specific processing for the first data packet based on the attribute information of the first data packet, including:

The first protocol layer determines whether to perform packet loss behavior for the first data packet after a packet loss timer times out based on the attribute information of the first data packet; or,

The first protocol layer determines whether to start a packet loss timer applicable to the first data packet based on the attribute information of the first data packet.
The method according to claim 6, wherein the first protocol layer determines whether to perform a packet loss behavior for the first data packet after a packet loss timer expires based on the attribute information of the first data packet, include:

If the attribute information of the first data packet is the first attribute information, the first protocol layer determines not to perform packet loss behavior for the first data packet after the packet loss timer times out;

If the attribute information of the first data packet is the second attribute information or not the first attribute information, the first protocol layer determines to perform packet loss behavior for the first data packet after the packet loss timer times out.
The method according to claim 6, wherein the first protocol layer determines whether to start a packet loss timer applicable to the first data packet based on the attribute information of the first data packet, including:

If the attribute information of the first data packet is the first attribute information, the first protocol layer determines not to start the packet loss timer applicable to the first data packet;

If the attribute information of the first data packet is the second attribute information or is not the first attribute information, the first protocol layer determines to start a packet loss timer applicable to the first data packet.
The method according to any one of claims 5, 7, and 8, wherein the attribute information of the first data packet is first attribute information, including at least one of the following:

The specific Qos attribute of the first data packet is the first Qos attribute;

The data type of the first data packet is a first data type;

The data importance of the first data packet is the first importance;

The data priority of the first data packet is the first priority.
The method according to any one of claims 5, 7, and 8, wherein the attribute information of the first data packet is not the first attribute information, and includes at least one of the following:

The specific Qos attribute of the first data packet is not the first Qos attribute;

The data type of the first data packet is not the first data type;

The data importance of the first data packet is not the first importance;

The data priority of the first data packet is not the first priority.
The method according to any one of claims 5, 7, and 8, wherein the attribute information of the first data packet is second attribute information, including at least one of the following:

The specific Qos attribute of the first data packet is the second Qos attribute;

The data type of the first data packet is the second data type;

The data importance of the first data packet is the second importance;

The data priority of the first data packet is the second priority.
The method according to any one of claims 1 to 11, wherein,

The first header corresponding to the first data packet carries the attribute information; and/or,

A control data packet is transmitted after the packet data unit set PDU set where the packet data unit PDU corresponding to the first data packet is located, and the control data packet carries the attribute information.
The method according to claim 12, wherein the first protocol layer obtains attribute information of the first data packet, including:

The first protocol layer obtains the attribute information based on the first packet header and/or the control data packet.
The method according to claim 12 or 13, wherein,

The first packet header is a packet header corresponding to the third protocol layer; and/or,

The control data packet is a control data packet corresponding to the third protocol layer.
The method according to claim 14, wherein the third protocol layer is a service data adaptation protocol SDAP layer, correspondingly, the first packet header is an SDAP packet header, and the control data packet is an SDAP control PDU.
The method according to any one of claims 12 to 15, wherein the control data packet is used to indicate the end of a PDU set and/or the start of the next PDU set.
The method according to any one of claims 2 to 5, wherein the second protocol layer is a Radio Link Control (RLC) layer.
The method according to any one of claims 1 to 17, wherein the first protocol layer is a Packet Data Convergence Protocol (PDCP) layer.
A data transmission method, the method includes:

The first node sends a first PDU to the second node, the first PDU is used to indicate to the second node a sequence number SN list that needs to feed back a positive acknowledgment ACK/negative acknowledgment NACK; and/or,

The first node receives a second PDU sent by the second node, and the second PDU is used to indicate to the first node the ACK/NACK information corresponding to the SN list.
The method of claim 19, wherein the first PDU includes at least one of the following information:

First information, the first information is used to indicate the number of SNs that need to feed back ACK/NACK;

Second information, the second information is used to indicate the starting SN that needs to feed back ACK/NACK;

The first bitmap is used to indicate the SN after the starting SN that needs to feed back ACK/NACK.
The method according to claim 20, wherein each bit in the first bitmap corresponds to an SN after the starting SN, and the value of the bit is used to indicate whether the SN corresponding to the bit is required. Feedback ACK/NACK.
The method of claim 19, wherein the first PDU includes at least one of the following information:

First information, the first information is used to indicate the number of SNs that need to feed back ACK/NACK;

Third information, the third information is used to indicate a list of SNs that need to feed back ACK/NACK.
The method of claim 19, wherein the first PDU includes at least one of the following information:

First information, the first information is used to indicate the number of SNs that need to feed back ACK/NACK;

Fourth information, the fourth information is used to indicate the starting SN that needs to feed back ACK/NACK;

Fifth information, the fifth information is used to indicate the termination SN that needs to feed back ACK/NACK.
The method according to any one of claims 20 to 23, wherein the first PDU further includes at least one of the following information:

Sixth information, the sixth information is used to indicate whether the first PDU belongs to a data PDU or a control PDU;

Seventh information, the seventh information is used to indicate the type of control PDU to which the first PDU belongs;

Eighth information, the eighth information is used to indicate the identity of a process.
The method according to any one of claims 19 to 24, wherein the second PDU includes at least one of the following information:

First information, the first information is used to indicate the number of SNs that need to feed back ACK/NACK;

Second information, the second information is used to indicate the starting SN that needs to feed back ACK/NACK;

A second bitmap, the second bitmap is used to indicate ACK/NACK information of multiple SNs after the starting SN.
The method according to claim 25, wherein each bit in the second bitmap corresponds to an SN that needs feedback after the starting SN, and the value of the bit is used to indicate the corresponding SN of the bit. SN's ACK/NACK information.
The method according to claim 25 or 26, wherein the second PDU further includes at least one of the following information:

Ninth information, the ninth information is used to indicate whether the second PDU belongs to a data PDU or a control PDU;

Tenth information, the tenth information is used to indicate the type of control PDU to which the second PDU belongs;

Eleventh information, the eleventh information is used to indicate the identity of a process.
The method according to any one of claims 19 to 27, wherein the first PDU is a first PDCP control PDU, the second PDU is a second PDCP control PDU, and the SN is carried in the PDCP PDU.
The method of claim 28, wherein the method further includes:

The PDCP layer of the first node obtains the attribute information of the data packet;

The PDCP layer of the first node determines a list of SNs that need to feed back ACK/NACK based on the attribute information;

Wherein, the attribute information includes at least one of the following: specific Qos attributes, data type, data importance, and data priority.
The method according to any one of claims 19 to 27, wherein the first PDU is a first RLC control PDU, the second PDU is a second RLC control PDU, and the SN is carried in the RLC PDU.
The method of claim 30, wherein the method further includes:

The PDCP layer of the first node obtains the attribute information of the data packet;

The PDCP layer of the first node determines the data packet that needs to feed back ACK/NACK based on the attribute information, and indicates the data packet that needs to feed back ACK/NACK to the RLC layer;

The RLC layer of the first node determines a list of SNs that need to feed back ACK/NACK based on the indication from the PDCP layer;

Wherein, the attribute information includes at least one of the following: specific Qos attributes, data type, data importance, and data priority.
The method according to any one of claims 19 to 31, wherein the method further comprises:

The first node determines, based on the second PDU, the PDU corresponding to the SN that the second node did not correctly receive;

The first node determines whether to retransmit the PDU based on the attribute information of the PDU corresponding to the incorrectly received SN. The attribute information includes at least one of the following: specific Qos attributes, data type, and data importance. , data priority.
The method according to claim 32, wherein the first node determines whether to retransmit the PDU based on the attribute information of the PDU corresponding to the incorrectly received SN, including:

If the attribute information of the PDU is the first attribute information, determine to retransmit the PDU;

If the attribute information of the PDU is the second attribute information or is not the first attribute information, it is determined not to retransmit the PDU.
The method according to claim 33, wherein the attribute information of the PDU is first attribute information, including at least one of the following:

The specific Qos attribute of the PDU is the first Qos attribute;

The data type of the PDU is the first data type;

The data importance of the PDU is the first importance;

The data priority of the PDU is the first priority.
The method according to claim 33, wherein the attribute information of the PDU is not the first attribute information and includes at least one of the following:

The specific Qos attribute of the PDU is not the first Qos attribute;

The data type of the PDU is not the first data type;

The data importance of the PDU is not the first importance;

The data priority of the PDU is not the first priority.
The method according to claim 33, wherein the attribute information of the PDU is second attribute information, including at least one of the following:

The specific Qos attribute of the PDU is the second Qos attribute;

The data type of the PDU is the second data type;

The data importance of the PDU is the second importance;

The data priority of the PDU is the second priority.
The method according to any one of claims 19 to 36, wherein the method further comprises:

The first node determines whether to cancel the sending of the specific data packet based on the second PDU.
The method of claim 37, wherein the first node determines whether to cancel the sending of a specific data packet based on the second PDU, including:

The first protocol layer of the first node determines whether to cancel the sending of the data packet based on the second PDU; and/or,

For the data packet that has been submitted to the second protocol layer, the first protocol layer of the first node determines whether to notify the second protocol layer to cancel the sending of the data packet through the first indication information based on the second PDU;

Wherein, the first protocol layer is a PDCP layer or an RLC layer, and the second protocol layer is a lower protocol layer of the first protocol layer.
38. The method of claim 38, wherein de-sending the data packet is based on an incorrectly received SN determination of the second PDU determination.
The method according to claim 38 or 39, wherein the first indication information is used to indicate at least one of the following:

Cancel the sent SN list;

Cancel the PDU set associated with the sent SN;

Cancel the frame associated with the sent SN;

Cancel the GOP associated with the sent SN.
A data transmission method, the method includes:

The second node receives the first PDU sent by the first node, the first PDU is used to indicate to the second node a list of SNs that need to feed back ACK/NACK; and/or,

The second node sends a second PDU to the first node, where the second PDU is used to indicate to the first node the ACK/NACK information corresponding to the SN list.
The method of claim 41, wherein the first PDU includes at least one of the following information:

First information, the first information is used to indicate the number of SNs that need to feed back ACK/NACK;

Second information, the second information is used to indicate the starting SN that needs to feed back ACK/NACK;

The first bitmap is used to indicate the SN after the starting SN that needs to feed back ACK/NACK.
The method according to claim 42, wherein each bit in the first bitmap corresponds to an SN after the starting SN, and the value of the bit is used to indicate whether the SN corresponding to the bit is required. Feedback ACK/NACK.
The method of claim 41, wherein the first PDU includes at least one of the following information:

First information, the first information is used to indicate the number of SNs that need to feed back ACK/NACK;

Third information, the third information is used to indicate a list of SNs that need to feed back ACK/NACK.
The method of claim 41, wherein the first PDU includes at least one of the following information:

First information, the first information is used to indicate the number of SNs that need to feed back ACK/NACK;

Fourth information, the fourth information is used to indicate the starting SN that needs to feed back ACK/NACK;

Fifth information, the fifth information is used to indicate the termination SN that needs to feed back ACK/NACK.
The method according to any one of claims 42 to 45, wherein the first PDU further includes at least one of the following information:

Sixth information, the sixth information is used to indicate whether the first PDU belongs to a data PDU or a control PDU;

Seventh information, the seventh information is used to indicate the type of control PDU to which the first PDU belongs;

Eighth information, the eighth information is used to indicate the identity of a process.
The method according to any one of claims 41 to 46, wherein the second PDU includes at least one of the following information:

First information, the first information is used to indicate the number of SNs that need to feed back ACK/NACK;

Second information, the second information is used to indicate the starting SN that needs to feed back ACK/NACK;

A second bitmap, the second bitmap is used to indicate ACK/NACK information of multiple SNs after the starting SN.
The method according to claim 47, wherein each bit in the second bitmap corresponds to an SN that needs feedback after the starting SN, and the value of the bit is used to indicate the corresponding bit. SN's ACK/NACK information.
The method according to claim 47 or 48, wherein the second PDU further includes at least one of the following information:

Ninth information, the ninth information is used to indicate whether the second PDU belongs to a data PDU or a control PDU;

Tenth information, the tenth information is used to indicate the type of control PDU to which the second PDU belongs;

Eleventh information, the eleventh information is used to indicate the identity of a process.
The method according to any one of claims 41 to 49, wherein the first PDU is a first PDCP control PDU, the second PDU is a second PDCP control PDU, and the SN is carried in the PDCP PDU.
The method according to any one of claims 41 to 49, wherein the first PDU is a first RLC control PDU, the second PDU is a second RLC control PDU, and the SN is carried in the RLC PDU.
A data transmission device, the device has a first protocol layer;

The first protocol layer is used to obtain attribute information of the first data packet; based on the attribute information of the first data packet, perform specific processing for the first data packet;

Wherein, the attribute information includes at least one of the following: specific Qos attributes, data type, data importance, and data priority.
A data transmission device, applied to the first node, the device includes:

A sending unit, configured to send a first PDU to the second node, where the first PDU is used to indicate to the second node a list of SNs that need to feed back ACK/NACK;

A receiving unit configured to receive a second PDU sent by the second node, where the second PDU is used to indicate ACK/NACK information corresponding to the SN list to the first node.
A data transmission device, applied to the second node, the device includes:

A receiving unit, configured to receive a first PDU sent by the first node, where the first PDU is used to indicate to the second node a list of SNs that need to feed back ACK/NACK;

A sending unit, configured to send a second PDU to the first node, where the second PDU is used to indicate to the first node the ACK/NACK information corresponding to the SN list.
A communication device, including: a processor and a memory, the memory is used to store a computer program, the processor is used to call and run the computer program stored in the memory, and execute as described in any one of claims 1 to 18 The method, or the method described in any one of claims 19 to 40, or the method described in any one of claims 41 to 51.
A chip, including: a processor for calling and running a computer program from a memory, so that a device equipped with the chip executes the method according to any one of claims 1 to 18, or claims 19 to 40 The method according to any one of claims 41 to 51.
A computer-readable storage medium for storing a computer program, the computer program causing a computer to perform the method according to any one of claims 1 to 18, or the method according to any one of claims 19 to 40 , or the method of any one of claims 41 to 51.
A computer program product comprising computer program instructions that cause a computer to perform the method as claimed in any one of claims 1 to 18, or the method as claimed in any one of claims 19 to 40, or the method as claimed in any one of claims 19 to 40, or The method of any one of claims 41 to 51.
A computer program that causes a computer to perform the method as claimed in any one of claims 1 to 18, or the method as claimed in any one of claims 19 to 40, or any one of claims 41 to 51. method described in one item.