WO2023184552A1 - Data transmission method and apparatus, and communication device - Google Patents

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 receiving one or more PDU sets sent by a second protocol layer, a packet header corresponding to each PDU in the PDU sets carrying first information and/or a first flag being transmitted after the PDU sets, wherein the first information comprises at least one of the following: a GOP identifier, a PDU set identifier, a PDU identifier, a frame type, the last frame indicator in a GOP, the number of frames included in the GOP, a GOP list associated with the GOP, and a Qos flow identifier; and the first label comprises at least one of the following: a GOP identifier, a PDU set identifier, a frame type, a Qos flow identifier, the last frame indicator in a GOP, the number of frames included in the GOP, a GOP list associated with the GOP, and a Qos flow identifier.

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, so each PDU in a PDU set is related to each other. However, in the current mobile communication system, the wireless air interface can only identify one data packet (i.e., PDU) when processing the data to be transmitted, and cannot identify the association between PDUs, let alone PDU sets or frames. As a result, these correlations cannot be taken into account during the data transmission process, and the data transmission efficiency cannot be guaranteed.

Contents of the invention

Embodiments of the present application provide a data transmission method and device, communication 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 receives one or more PDU sets sent by the second protocol layer. The header corresponding to each PDU in the PDU set carries the first information and/or the PDU set is transmitted with a first flag, where ,

The first information includes at least one of the following: a Group of Pictures (GOP) identifier, a PDU set identifier, a PDU identifier, a frame type, an indication of the last frame in the GOP, the number of frames included in the GOP, and a GOP association GOP list, Quality of Service (Qos) flow identification;

The first flag includes at least one of the following: GOP identifier, PDU set identifier, frame type, Qos flow identifier, last frame indication in the GOP, number of frames included in the GOP, GOP list associated with the GOP, and Qos flow identifier.

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

The first node sends a first PDCP control PDU to the second node, where the first PDCP control PDU carries feedback information, where the feedback information is used to indicate at least one of the following:

Positive acknowledgment (ACK)/negative acknowledgment (NACK) information for one or more PDUs;

ACK/NACK information of one or more PDU sets;

ACK/NACK information for one or more GOPs.

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

The second node receives the first PDCP control PDU sent by the first node, and the first PDCP control PDU carries feedback information, where the feedback information is used to indicate at least one of the following:

ACK/NACK information for one or more PDUs;

ACK/NACK information of one or more PDU sets;

ACK/NACK information for one or more GOPs.

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

The first protocol layer is used to receive one or more PDU sets sent by the second protocol layer;

The second protocol layer is used to send one or more PDU sets to the first protocol layer;

The header corresponding to each PDU in the PDU set carries the first information and/or the first flag is transmitted after the PDU set, where,

The first information includes at least one of the following: GOP identifier, PDU set identifier, PDU identifier, frame type, last frame indication in the GOP, number of frames included in the GOP, GOP list associated with the GOP, Qos flow identifier;

The first flag includes at least one of the following: GOP identifier, PDU set identifier, frame type, Qos flow identifier, last frame indication in the GOP, number of frames included in the GOP, GOP list associated with the GOP, and Qos flow identifier.

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 PDCP control PDU to the second node, where the first PDCP control PDU carries feedback information, wherein the feedback information is used to indicate at least one of the following:

ACK/NACK information for one or more PDUs;

ACK/NACK information of one or more PDU sets;

ACK/NACK information for one or more GOPs.

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 PDCP control PDU sent by the first node, where the first PDCP control PDU carries feedback information, wherein the feedback information is used to indicate at least one of the following:

ACK/NACK information for one or more PDUs;

ACK/NACK information of one or more PDU sets;

ACK/NACK information for one or more GOPs.

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, by carrying the first information in the header corresponding to each PDU and/or by inserting and transmitting the first flag after the PDU set, the first information includes at least one of the following: image group GOP identification, PDU set Identification, PDU identification, frame type, last frame indication in the GOP, number of frames included in the GOP, GOP list associated with the GOP, quality of service Qos flow identification, the first identification includes at least one of the following: GOP identification, PDU set identifier, frame type, Qos flow identifier, last frame indication in the GOP, number of frames included in the GOP, GOP list associated with the GOP, Qos flow identifier, so that the PDU can be identified according to the first information and/or the first flag. Association between PDU sets or frames, so that different mechanisms can be used for different data according to the association to ensure reliable transmission of important data, 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 according to the embodiment of the present application;

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 principle of application example 1 provided by the embodiment of the present application;

Figure 8-1 is a schematic diagram 1 of the format of the PDCP control PDU provided by the embodiment of this application;

Figure 8-2 is a schematic diagram 2 of the format of the PDCP control PDU provided by the embodiment of this application;

Figure 8-3 is a schematic diagram 3 of the format of the PDCP control PDU provided by the embodiment of this application;

Figure 8-4 is a schematic diagram 4 of the format of the PDCP control PDU provided by the embodiment of this application;

Figure 8-5 is a schematic diagram 5 of the format of the PDCP control PDU provided by the embodiment of this application;

Figure 9-1 is a schematic diagram 6 of the format of the PDCP control PDU provided by the embodiment of this application;

Figure 9-2 is a schematic diagram 7 of the format of the PDCP control PDU provided by the embodiment of this application;

Figure 9-3 is a schematic diagram 8 of the format of the PDCP control PDU provided by the embodiment of this application;

Figure 9-4 is a schematic diagram 9 of the format of the PDCP control PDU provided by the embodiment of this application;

Figure 9-5 is a schematic diagram 10 of the format of the PDCP control PDU provided by the embodiment of this application;

Figure 10 is a schematic diagram of the principle of application example two 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 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. A GOP includes 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. In a GOP, if the I frame is lost, it means that the P and B frames in the GOP are correctly transmitted to each other, and the picture cannot be solved.

At present, in the mobile communication system, the wireless air interface can only identify the data packets one by one when processing the data to be transmitted, that is, the above-mentioned PDU. It cannot identify the relationship between PDUs, that is, the affiliation of PDUs belonging to a PDU set or frame. , and cannot identify the relationship between PDU sets or frames, such as an I frame belonging to a GOP and its associated B frames and P frames. Therefore, during the data transmission process, these data packets cannot be treated differently, and these associations will not be considered in the effective transmission process of data. 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 contents.

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 receives one or more PDU sets sent by the second protocol layer. The header corresponding to each PDU in the PDU set carries the first information and/or the PDU set is transmitted with the first flag, wherein the first information includes at least one of the following: GOP identifier, PDU set identifier, PDU identifier, frame type, last frame indication in the GOP, number of frames included in the GOP, GOP list associated with the GOP, service Quality Qos flow identification; the first identification includes at least one of the following: GOP identification, PDU set identification, frame type, Qos flow identification, last frame indication in the GOP, number of frames included in the GOP, and GOP list associated with the GOP , Qos flow identification.

In this embodiment of the present application, the first protocol layer and the second protocol layer are protocol layers of a communication device, and the communication device may be a network device or a terminal device. 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.

In this embodiment of the present application, the first protocol layer and the second protocol layer belong to the protocol layer of the sending end, that is, the communication device belongs to the sending end. Relative to the sending end, the receiving end can receive the PDU set sent by the sending end. Here, the second protocol layer is an upper protocol layer of the first protocol layer.

In some optional implementations, the header corresponding to each PDU in the PDU set carries first information, and the first information includes at least one of the following: GOP identifier, PDU set identifier, PDU identifier, frame type, The last frame indication in the GOP, the number of frames contained in the GOP, the GOP list associated with the GOP, and the Qos flow identifier.

Here, the GOP identifier refers to the GOP identifier associated with the PDU, that is, the PDU set in which the PDU is located or the identifier of the GOP to which the frame belongs, such as GOP id or GOP SN or GOP index, etc.

Here, the PDU set identifier refers to the PDU set identifier associated with the PDU, that is, the identifier of the PDU set where the PDU is located, such as PDU set id or PDU set SN or PDU set index, etc. Optionally, the PDU set identifier is unique within a GOP.

Here, the PDU identifier refers to the identifier of the PDU, such as PDU id or PDU SN or PDU index, etc. Optionally, the PDU identifier is unique within the PDU set.

Here, the frame type refers to the frame type corresponding to the PDU set in which the PDU is located. The frame type may be, for example, an I frame, a P frame, a B frame, or other frame types.

Here, the last frame indication in the GOP refers to the indication information of the last frame in the GOP to which the PDU set in which the PDU is located belongs. The indication information may be, for example, a PDU set identifier.

Here, the number of frames contained in the GOP refers to the number of frames contained in the GOP to which the PDU set in which the PDU is located belongs.

Here, the GOP list associated with the GOP refers to the GOP list associated with the GOP to which the PDU set in which the PDU is located belongs.

Here, the Qos flow identifier refers to the identifier of the Qos flow where the PDU is located, and the identifier may be QFI, for example.

In some optional implementations, a first flag is transmitted after the PDU set, and the first flag includes at least one of the following: GOP identification, PDU set identification, frame type, Qos flow identification, and last frame indication in the GOP , the number of frames contained in the GOP, the GOP list associated with the GOP, and the Qos flow identifier.

Here, the GOP identifier refers to the identifier of the GOP to which the PDU set or frame belongs before and/or after the first identifier, such as GOP id or GOP SN or GOP index, etc.

Here, the PDU set identifier refers to the PDU set before and/or after the first mark or the PDU set identifier of the frame, such as PDU set id or PDU set SN or PDU set index, etc. Optionally, the PDU set identifier is unique within a GOP.

Here, the frame type refers to the frame type corresponding to the PDU set or frame before and/or after the first mark. The frame type may be, for example, I frame, or P frame, or B frame, or other frame types.

Here, the last frame indication in the GOP refers to the PDU set before and/or after the first mark or the indication information of the last frame in the GOP to which the frame belongs. The indication information may be, for example, a PDU set identifier.

Here, the number of frames included in the GOP refers to the number of frames included in the PDU set before and/or after the first flag or the GOP to which the frame belongs.

Here, the GOP list associated with the GOP refers to the GOP list associated with the PDU set before and/or after the first flag or the GOP to which the frame belongs.

Here, the Qos flow identifier refers to the identifier of the PDU set or the Qos stream in which the frame is located before and/or after the first flag. The identifier may be QFI, for example.

The technical solution of the embodiment of the present application will be described below in conjunction with the specific implementation of the first protocol layer and the second protocol layer.

Case 1

In some optional implementations, the second protocol layer is a GTP layer, the first protocol layer is a Service Data Adaptation Protocol (SDAP) layer, the header is a GTP header, and the third protocol layer is a GTP header. A flag is carried in GTP packets.

Based on this, the SDAP layer receives one or more PDU sets sent by the GTP layer. The GTP header corresponding to each PDU in the PDU set carries the first information and/or the PDU set is transmitted with a first flag. GTP packet, here, optionally, the first flag carried in the GTP packet can also be called the GTP end marker (GTP end marker).

The SDAP layer identifies the PDU set based on the information carried in the GTP packet header and/or the first flag carried in the GTP packet, and passes the PDU set to the Packet Data Convergence Protocol (Packet Data Convergence Protocol) , PDCP) layer.

In some optional implementations, in order for the SDAP layer to allow the PDCP layer to identify the PDU set, the SDAP layer carries the first information and/or the first information in the SDAP header corresponding to each PDU in the PDU set. A transmission SDAP control PDU is inserted after the PDU set, and the SDAP control PDU carries the first flag.

In some optional implementations, the SDAP layer can pass the PDU set to the PDCP layer according to the PDU granularity, that is, the SDAP layer encapsulates the SDAP service data unit (Service Data Unit, SDU) corresponding to each PDU in the PDU set into the corresponding The SDAP PDU is then passed to the PDCP layer, and each SDAP PDU carries one SDAP SDU.

In some optional implementations, the SDAP layer can pass the PDU set to the PDCP layer according to the PDU set granularity, that is, the SDAP layer concatenates the SDAP SDUs corresponding to all the PDUs in the PDU set into one SDAP PDU, and then SDAP PDU is passed to the PDCP layer, and each SDAP PDU carries multiple SDAP SDUs.

It should be noted that after receiving the first GTP packet, the SDAP layer recognizes the first flag from the first GTP packet and then discards the first GTP packet.

Case 2

In some optional implementations, the second protocol layer is an SDAP layer, the first protocol layer is a PDCP layer, the packet header is an SDAP packet header, and the first flag is carried in an SDAP control PDU.

Based on this, the PDCP layer receives one or more PDU sets sent by the SDAP layer. The SDAP header corresponding to each PDU in the PDU set carries the first information and/or the PDU set is transmitted with a packet carrying the first flag. SDAP control PDU. Here, optionally, the first flag carried in the SDAP control PDU may also be called the SDAP end marker.

The PDCP layer identifies the PDU set based on the first information carried in the SDAP packet header and/or the first flag carried in the SDAP control PDU, and passes the PDU set to the wireless link layer control ( Radio Link Control (RLC) layer.

In some optional implementations, in order to enable the RLC layer to identify the PDU set, the PDCP layer carries the first information and/or the first information in the PDCP header corresponding to each PDU in the PDU set. A transmission PDCP control PDU is inserted after the PDU set, and the PDCP control PDU carries the first flag.

In some optional implementations, the PDCP layer can pass the PDU set to the RLC layer according to the PDU granularity, that is, the PDCP layer encapsulates the PDCP SDU corresponding to each PDU in the PDU set into the corresponding PDCP PDU and passes it to the RLC layer. One PDCP SDU is carried in each PDCP PDU.

In some optional implementations, the PDCP layer can pass the PDU set to the RLC layer according to the PDU set granularity, that is, the PDCP layer concatenates the PDCP SDUs corresponding to all the PDUs in the PDU set into one PDCP PDU, and then PDCP PDU is passed to the RLC layer, and each PDCP PDU carries multiple PDCP SDUs.

It should be noted that after receiving the SDAP control PDU, the PDCP layer recognizes the first flag from the SDAP control PDU and then discards the SDAP control PDU.

In the embodiment of this application, after receiving one or more PDU sets sent by the SDAP layer, the PDCP layer determines the frame type of each PDU, so that corresponding mechanisms can be used according to the frame type to ensure reliable transmission of data, thereby improving multimedia Business performance and user experience. Here, the ways in which the PDCP layer determines the frame type include but are not limited to the following ways:

Method 1: The PDCP layer determines the frame type of the PDU based on the frame type carried in the SDAP header corresponding to the PDU and/or the frame type in the first flag.

Method 2: The PDCP layer determines the frame type of the PDU based on the Qos flow identifier carried in the SDAP header corresponding to the PDU and/or the Qos flow identifier in the first flag, and the first corresponding relationship, where: The first corresponding relationship is the corresponding relationship between the Qos flow identifier and the frame type.

In some optional implementations, the first correspondence is configured to the receiving end through RRC signaling, and the first correspondence is used by the PDCP layer of the receiving end to determine the frame of the PDU based on the Qos flow identifier corresponding to the PDU. type. For example: the base station (i.e., the sending end) configures the first corresponding relationship to the terminal device (i.e., the receiving end) through RRC signaling. After the PDCP layer of the terminal device receives the PDU set sent by the base station, the Qos flow corresponding to the PDU in the PDU set is The identification and the first correspondence determine the frame type of the PDU.

In some optional implementations, the lower protocol layer of the PDCP layer is associated with at least two RLC entities, and the logical channel identifiers of different RLC entities correspond to different frame types (that is, there is a corresponding relationship between the logical channel identifiers of the RLC entities and the frame types). ), after the PDCP layer determines the frame type of the PDU through the above method one or method two, the PDCP layer determines the logical channel identifier corresponding to the PDU based on the frame type of the PDU and the second correspondence relationship, and based on the determined logical The channel identifier delivers the PDU to the corresponding RLC entity; wherein the second correspondence is the correspondence between the frame type and the logical channel identifier.

In some optional implementations, the second correspondence relationship is configured to the receiving end through RRC signaling, and the second correspondence relationship is used by the PDCP layer of the receiving end to determine the source from the RLC based on the logical channel identifier corresponding to the RLC entity. The frame type of the entity's PDU. For example: the base station (i.e., the sending end) configures the second corresponding relationship to the terminal device (i.e., the receiving end) through RRC signaling. After the PDCP layer of the terminal device receives the PDU submitted by the RLC entity, it determines the second corresponding relationship based on the logical channel identifier of the RLC entity and the second The correspondence determines the frame type of the PDU from this RLC entity.

In some optional implementations, the PDCP layer carries at least part of the first information in the PDCP header corresponding to each PDU in the PDU set. Here, after the receiving end receives the PDU set sent by the sending end, since the PDCP layer of the sending end carries at least part of the information of the first information in the header corresponding to each PDU in the PDU set, the PDCP layer of the receiving end can be based on the PDU corresponding The information carried in the packet header identifies the frame type of the PDU, the association between PDUs (such as which PDUs belong to a PDU set), the association between PDU sets or frames (such as which PDU sets or frames belong to a GOP), etc.

The above solution of the embodiment of the present application can be, but is not limited to, applied to the following scenarios:

Scenario 1: For the situation where the PDU set or frames in a GOP come from the same Qos flow, the data in the Qos flow is transmitted through one of the following types of bearers:

A first type bearer, the first type bearer corresponds to a PDCP entity and an RLC entity, and the mode of the RLC entity is the UM mode;

A second type bearer, the second type bearer corresponds to one PDCP entity and one RLC entity, and the mode of the RLC entity is AM mode;

A third type bearer, the third type bearer corresponds to one PDCP entity and two RLC entities, one of the two RLC entities is in AM mode and the other RLC entity is in UM mode, or the two RLC entities are all in UM mode.

Scenario 2: For the situation where the PDU set or frame within a GOP comes from at least two Qos flows, the data in the at least two Qos flows is transmitted through one of the following types of bearers:

A first type bearer, the first type bearer corresponds to a PDCP entity and an RLC entity, and the mode of the RLC entity is the UM mode;

A third type bearer, the third type bearer corresponds to one PDCP entity and two RLC entities, one of the two RLC entities is in AM mode and the other RLC entity is in UM mode, or the two RLC entities are all in UM mode;

The fourth type of bearer includes two bearers, one of the two bearers corresponds to a PDCP entity and an AM mode RLC entity, and the other bearer corresponds to a PDCP entity and an UM mode RLC entity.

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 PDCP control PDU to the second node, and the second node receives the first PDCP control PDU sent by the first node. The first PDCP control PDU carries feedback information, where the feedback information is expressed in Indicates at least one of the following: ACK/NACK information of one or more PDUs; ACK/NACK information of one or more PDU sets; ACK/NACK information of one or more GOPs.

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 PDCP control PDU to the second node, the first node receives one or more data packets sent by the second node, and then, the first node sends the first PDCP control PDU to the second node. Control PDU, perform ACK/NACK feedback on the received data packet through the first PDCP control PDU. Here, the first PDCP control PDU carries feedback information, wherein the feedback information is used to indicate at least one of the following: ACK/NACK information of one or more PDUs; ACK/NACK information of one or more PDU sets; ACK/NACK information for one or more GOPs.

Here, when the feedback information is used to indicate ACK/NACK information of one or more PDUs, it can be understood that the first node performs PDU-level ACK/NACK feedback through the first PDCP control PDU. When the feedback information is used to indicate ACK/NACK information of one or more PDU sets, it can be understood that the first node performs ACK/NACK feedback at the PDU set level through the first PDCP control PDU. When the feedback information is used to indicate ACK/NACK information of one or more GOPs, it can be understood that the first node performs GOP-level ACK/NACK feedback through the first PDCP control PDU.

It should be noted that PDU level can also be called PDU granularity (per PDU). PDU set level (PDU set level) can also be called PDU set granularity (per PDU set). GOP level (GOP level) can also be called or GOP granularity (per GOP).

It should be noted that the first PDCP control PDU may also be called ACK/NACK feedback response PDU (ACK/NACK feedback response PDU). This application does not limit the name of the first PDCP control PDU.

In this embodiment of the present application, before the first node sends the first PDCP control PDU to the second node, the method further includes:

The first node receives the PDCP PDU sent by the second node;

If the PDCP PDU carries multiple PDUs in the PDU set, the first node performs ACK/NACK feedback at the PDU set level and/or ACK/NACK feedback at the GOP level through the first PDCP control PDU;

If the PDCP PDU carries a PDU in the PDU set, the first node uses the first PDCP control PDU to perform PDU level ACK/NACK feedback and/or PDU set level ACK/NACK feedback and/or GOP level ACK/NACK feedback.

Here, it should be noted that if the PDCP layer of the second node cascades multiple PDUs (which can be all PDUs) in the PDU set, that is, assembles the PDCP SDUs corresponding to multiple PDUs into one PDCP PDU, then the After receiving a PDCP PDU, a node can perform PDU set level ACK/NACK feedback and/or GOP level ACK/NACK feedback. If the PDCP layer of the second node does not cascade multiple PDUs (which can be all PDUs) in the PDU set, that is, each PDCP PDU is assembled according to the PDCP SDU corresponding to the multiple PDUs (each PDCP PDU carries one PDCP SDU ), then the first node can perform PDU level ACK/NACK feedback and/or PDU set level ACK/NACK feedback and/or GOP level ACK/NACK feedback after receiving the PDCP PDU.

The format of the first PDCP control PDU is described below.

The format of the first PDCP control PDU

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

First information, the first information is used to indicate the GOP identification associated with the feedback information;

Second information, the second information is used to indicate the number of PDU sets contained in the GOP;

Third information, the third information is used to indicate the number of PDUs contained in each PDU set;

A first bitmap, each bit in the first bitmap corresponds to a PDU, and the value of the bit is used to indicate the ACK/NACK information of the PDU corresponding to the bit.

Here, optionally, the corresponding relationship between the bits in the first bitmap and the PDU is: according to the order of PDU set identifiers from small to large, and then according to the order of PDU identifiers in each PDU set from small to large, One-to-one correspondence with the first bitmap in order from low bit to high bit.

For example: there are 2 PDU sets, namely PDU set1 and PDU set2. Among them, PDU set1 includes PDU1, PDU2 and PDU3, and PDU set2 includes PDU1, PDU2 and PDU3. PDU1 in PDU set1 corresponds to the lowest bit of the first bitmap. PDU2 in PDU set1 corresponds to the second low bit of the first bitmap (called the second low bit), PDU1 in PDU set2 corresponds to the third low bit of the first bitmap, and PDU2 in PDU set2 corresponds to the fourth low bit of the first bitmap .

Of course, the technical solutions of the embodiments of the present application are not limited to the above-mentioned correspondence relationships, and the correspondence between PDUs and bits can also be achieved according to other correspondence relationships.

In the above solution, optionally, a bit value of 1 is used to indicate that the PDU corresponding to the bit is ACK, and a bit value of 0 is used to indicate that the PDU corresponding to the bit is NACK.

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

Seventh information, the seventh information is used to indicate whether the first PDCP control PDU is a data PDU or a control PDU;

Eighth information, the eighth information is used to indicate the PDU type to which the first PDCP control PDU belongs.

Here, the PDU type is one of the following:

A first PDU type, the first PDU type is used for PDU level ACK/NACK feedback;

A second PDU type, the second PDU type is used for ACK/NACK feedback at the PDU set level;

A third PDU type, the third PDU type is used for ACK/NACK feedback at the GOP level.

The above-mentioned first PDCP control PDU with format 1) may be used for PDU level ACK/NACK feedback.

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

First information, the first information is used to indicate the GOP identification associated with the feedback information;

At least one set of information, each set of information corresponding to a PDU set in the GOP, each set of information includes fourth information, fifth information and a second bitmap, the fourth information is used to indicate the PDU set identification, the third Five information is used to indicate the number of PDUs contained in the PDU set. Each bit in the second bitmap corresponds to one PDU. The value of the bit is used to indicate the ACK/NACK of the PDU corresponding to the bit. information.

Here, optionally, the corresponding relationship between the bits in the second bitmap and the PDU is: in the order of PDU identifiers from small to large, and in the second bitmap in the order from low to high. correspond.

For example: There are 2 PDU sets, namely PDU set1 and PDU set2. Among them, PDU set1 includes PDU1, PDU2 and PDU3, and PDU set2 includes PDU1, PDU2 and PDU3. Each PDU set corresponds to a set of information. Take PDU set1 as an example. , PDU1 in PDU set1 corresponds to the lowest bit of the second bitmap, and PDU2 in PDU set1 corresponds to the second lowest bit of the second bitmap (called the second lowest bit).

Of course, the technical solutions of the embodiments of the present application are not limited to the above-mentioned correspondence relationships, and the correspondence between PDUs and bits can also be achieved according to other correspondence relationships.

In the above solution, optionally, a bit value of 1 is used to indicate that the PDU corresponding to the bit is ACK, and a bit value of 0 is used to indicate that the PDU corresponding to the bit is NACK.

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

Seventh information, the seventh information is used to indicate whether the first PDCP control PDU is a data PDU or a control PDU;

Eighth information, the eighth information is used to indicate the PDU type to which the first PDCP control PDU belongs.

Here, the PDU type is one of the following:

A first PDU type, the first PDU type is used for PDU level ACK/NACK feedback;

A second PDU type, the second PDU type is used for ACK/NACK feedback at the PDU set level;

A third PDU type, the third PDU type is used for ACK/NACK feedback at the GOP level.

The above-mentioned first PDCP control PDU with format 2) may be used for PDU level ACK/NACK feedback.

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

First information, the first information is used to indicate the GOP identifier associated with the feedback information;

Second information, the second information is used to indicate the number of PDU sets contained in the GOP;

The third bitmap, each bit in the third bitmap corresponds to a PDU set, and the value of the bit is used to indicate the ACK/NACK information of the PDU set corresponding to the bit.

Here, the corresponding relationship between the bits in the third bitmap and the PDU set is: in order from small to large PDU set identifiers, they correspond one-to-one with the third bitmap in the order from low to high.

For example: there are 2 PDU sets, namely PDU set1 and PDU set2. PDU set1 corresponds to the lowest bit of the third bitmap, and PDU set2 corresponds to the second lowest bit of the third bitmap (called the second lowest bit).

Of course, the technical solution of the embodiment of the present application is not limited to the above-mentioned correspondence relationship, and the correspondence between the PDU set and the bits can also be realized according to other correspondence relationships.

In the above solution, optionally, a bit value of 1 is used to indicate that the PDU set corresponding to this bit is ACK, and a bit value of 0 is used to indicate that the PDU set corresponding to this bit is NACK.

Here, if at least one PDU in a PDU set is not received correctly, the ACK/NACK information corresponding to the PDU set is NACK; if all PDUs in a PDU set are received correctly, the ACK/NACK information corresponding to the PDU set is NACK information is ACK.

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

Seventh information, the seventh information is used to indicate whether the first PDCP control PDU is a data PDU or a control PDU;

Eighth information, the eighth information is used to indicate the PDU type to which the first PDCP control PDU belongs.

Here, the PDU type is one of the following:

A first PDU type, the first PDU type is used for PDU level ACK/NACK feedback;

A second PDU type, the second PDU type is used for ACK/NACK feedback at the PDU set level;

A third PDU type, the third PDU type is used for ACK/NACK feedback at the GOP level.

The above-mentioned first PDCP control PDU with format 3) can be used for ACK/NACK feedback at the PDU set level.

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

First information, the first information is used to indicate the GOP identification associated with the feedback information;

Sixth information, the sixth information is ACK/NACK information corresponding to the GOP.

Here, if at least one PDU in the GOP is not received correctly, the ACK/NACK information corresponding to the GOP is NACK; if all PDUs in the GOP are received correctly, the ACK/NACK information corresponding to the GOP is ACK; or , if the specific PDU Set or specific frame in the GOP is not received correctly, the ACK/NACK information corresponding to the GOP is NACK; if the specific PDU Set or specific frame in the GOP is received correctly, the ACK/NACK information corresponding to the GOP The message is ACK.

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

Seventh information, the seventh information is used to indicate whether the first PDCP control PDU is a data PDU or a control PDU;

Eighth information, the eighth information is used to indicate the PDU type to which the first PDCP control PDU belongs.

Here, the PDU type is one of the following:

A first PDU type, the first PDU type is used for PDU level ACK/NACK feedback;

A second PDU type, the second PDU type is used for ACK/NACK feedback at the PDU set level;

A third PDU type, the third PDU type is used for ACK/NACK feedback at the GOP level.

The above-mentioned first PDCP control PDU with format 4) may be used for GOP level ACK/NACK feedback.

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

First information, the first information is used to indicate the GOP identification associated with the feedback information;

Second information, the second information is used to indicate the number of PDU sets contained in the GOP;

Third information, the third information is used to indicate the number of PDUs contained in each PDU set;

A first bitmap, each bit in the first bitmap corresponds to a PDU, and the value of the bit is used to indicate the ACK/NACK information of the PDU corresponding to the bit;

A third bitmap, each bit in the third bitmap corresponds to a PDU set, and the value of the bit is used to indicate the ACK/NACK information of the PDU set corresponding to the bit;

Sixth information, the sixth information is ACK/NACK information corresponding to the GOP.

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

Seventh information, the seventh information is used to indicate whether the first PDCP control PDU is a data PDU or a control PDU;

Eighth information, the eighth information is used to indicate the PDU type to which the first PDCP control PDU belongs;

Ninth information, the ninth information is used to indicate the feedback type corresponding to the first PDCP control PDU.

As an implementation manner, when the feedback type is PDU-level ACK/NACK feedback, the first PDCP control PDU includes the first information, the second information, the third information and the At least one of the first bitmaps. Here, the related meanings of the first information, the second information, the third information and the first bitmap may refer to the description of the foregoing related solutions.

As an implementation manner, when the feedback type is PDU set level ACK/NACK feedback, the first PDCP control PDU includes the first information, the second information and the second bitmap. at least one of. Here, the relevant meanings of the first information, the second information and the second bitmap may refer to the description of the foregoing related solutions.

As an implementation manner, when the feedback type is GOP-level ACK/NACK feedback, the first PDCP control PDU includes at least one of the first information and the sixth information. Here, the relevant meanings of the first information and the sixth information may refer to the description of the foregoing related solutions.

The above-mentioned first PDCP control PDU with format 5) can be used for any of the following levels of ACK/NACK feedback: PDU level ACK/NACK feedback, PDU set level ACK/NACK feedback, and GOP level ACK/NACK feedback.

In some optional implementations, the first node sends the first PDCP control PDU to the second node based on its own implementation. For example: the first node sends a first PDCP control PDU to the second node based on the PDCP layer's reordering timer for PDCP PDUs of one or several GOPs that expires. For example: the first node sends the first PDCP control PDU to the second node according to the request condition configured on the network side when the request condition is met.

In some optional implementations, the first node sends a first PDCP control PDU to the second node based on a request from the second node. Here, the second node's request may be implemented through a second PDCP control PDU. Specifically, the second node sends a second PDCP control PDU to the first node, and the first node receives the second PDCP control PDU. The second PDCP control PDU sent by the node, the second PDCP control PDU is used to request feedback information, wherein the feedback type of the feedback information is PDU level ACK/NACK feedback or PDU set level ACK/NACK feedback or GOP level of ACK/NACK feedback.

It should be noted that the second PDCP control PDU may also be called ACK/NACK feedback request PDU (ACK/NACK feedback request PDU). This application does not limit the name of the second PDCP control PDU.

The format of the second PDCP control PDU is described below.

The format of the second PDCP control PDU

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

First information, the first information is used to indicate the GOP identification associated with the feedback information;

Tenth information, the tenth information is used to indicate the feedback type requested by the second PDCP control PDU.

Further, optionally, the second PDCP control PDU is also used to indicate the PDU set that requires feedback; the second PDCP control PDU also includes at least one of the following information:

PDU set identification list;

The number of PDU set identifiers;

The starting value of the PDU set identifier;

The end value of the PDU set identifier.

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

Eleventh information, the eleventh information is used to indicate whether the second PDCP control PDU is a data PDU or a control PDU;

Twelfth information, the twelfth information is used to indicate the PDU type to which the second PDCP control PDU belongs.

In the above solution, if the feedback type requested by the second PDCP control PDU is PDU-level ACK/NACK feedback, the first node carries ACK/NACK of one or more PDUs in the first PDCP control PDU. Information; if the feedback type requested by the second PDCP control PDU is ACK/NACK feedback at the PDU set level, the first node carries ACK/NACK of one or more PDU sets in the first PDCP control PDU. Information; if the feedback type requested by the second PDCP control PDU is GOP-level ACK/NACK feedback, the first node carries ACK/NACK information of one or more GOPs in the first PDCP control PDU.

In some optional implementations, when the first node determines that a specific frame or a specific PDU set or a specific PDU in the GOP has been lost, the PDCP layer of the first node deletes the undelivered PDUs in the GOP. and/or notify the RLC layer to delete the PDU to be delivered in the GOP. Here, the characteristic frame is, for example, an I frame or a frame with high importance or a frame with high priority. The specific PDU set is, for example, the PDU set corresponding to the I frame or the PDU set with high importance or the PDU set with high priority. The specific PDU set is, for example, It is a PDU belonging to an I frame or a PDU of high importance or a PDU of high priority. It should be noted that when a specific frame or a specific PDU set or a specific PDU in the GOP is lost, since the processing of other data needs to be based on these lost data, the transmission of other data is meaningless, so the PDCP layer can be deleted The relevant data that has been submitted to this layer can also notify the RLC layer to delete the relevant data to be submitted.

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

Application example one

Referring to Figure 7, when all frames (I frames, P frames, B frames) in a GOP come from the same Qos flow, the network side can configure the following types of bearers to transmit the video data in this Qos flow:

Option 1: One PDCP entity and one UM RLC entity (ie, UM mode RLC entity).

Option 2: One PDCP entity and one AM RLC entity (ie, AM mode RLC entity).

Option 3: One PDCP entity and 2 RLC entities. One RLC entity is used to transmit I frames and can be an AM RLC entity or UM RLC entity. The other RLC entity is used to transmit P/B frames and can be a UM RLC entity.

Regardless of the type of bearer, for downlink data, GTP end markers are defined to split PDU sets or frames in a Qos flow. The SDAP layer identifies the PDU set or frame through the GTP end marker. Furthermore, the SDAP layer inserts the SDAP end marker after each PDU set or frame to split the PDU set or frame in a Qos flow. The PDCP layer identifies the PDU set or frame through the SDAP end marker. For upstream data, it depends on the implementation of the terminal device to distinguish PDU sets or frames. Here, GTP end marker and SDAP end marker include at least one of the following information: GOP identifier, PDU set identifier, frame type, Qos flow identifier, last frame indication in the GOP, number of frames included in the GOP, and GOP associated with the GOP List, Qos flow identification. Generally, GTP end marker and SDAP end marker are transmitted behind a PDU set.

Regardless of the type of bearer, for downlink data, the first information can be carried in the GTP header and/or SDAP header corresponding to each PDU. The first information includes at least one of the following: GOP identifier, PDU set identifier, PDU identifier, frame type, last frame indication in the GOP, number of frames contained in the GOP, GOP list associated with the GOP, Qos flow identifier, used to assist the PDCP layer in identifying the PDU, frame type, and the distance between PDUs in a PDU set Association relationship, association relationship between frames in a GOP, and association relationship between GOPs.

Referring to Figure 7, for the bearer types described in option 1, option 2, or option 3 above, the PDCP layer at the sender can implement the cascading function, that is, all PDUs in a PDU set are assembled into one PDCP PDU for unification. of sending. The receiving end can disassemble the cascaded PDCP PDU into SDAP PDU corresponding to each PDU. Here, the sender performs the cascading function after encryption and integrity protection. The receiving end performs disassembly after removing the packet header, and processes the disassembled data safely.

For the bearer types described in option 1, option 2, or option 3 above, the PDCP layer at the sender can identify the SDAP PDU corresponding to the frame type information carried in the SDAP header or the frame type information carried in the SDAP end marker. Frame type of PDU. Alternatively, the PDCP layer at the sender identifies the frame type of the PDU corresponding to the SDAP PDU based on the Qos flow identifier (QFI) carried in the SDAP header and the correspondence between QFI and frame type.

For the bearer types described in option 1, option 2, or option 3 above, in order to let the PDCP layer on the receiving end know the frame type of the received data and which data belongs to the same PDU set or GOP, the PDCP layer on the sending end The layer carries at least the GOP identifier and frame type in the PDCP header. It can also carry information such as the PDU set identifier, the last frame indication in a GOP, and the number of frames contained in the GOP.

For the bearer type described in option 3 above, the receiving end can identify the frame type corresponding to the data from the RLC entity based on the correspondence between the logical channel identifier configured in the RRC signaling and the frame type, such as whether it belongs to an I frame or an I frame. Belongs to P/B frame. Here, there is a corresponding relationship between the logical channel identifier corresponding to the RLC entity and the frame type, and the corresponding relationship can be configured to the receiving end through RRC signaling. For example: Configure the frame type corresponding to the transmission data of two RLC entities through RRC dedicated signaling. For example, one RLC entity is configured with an indication information. The indication information is used to indicate that the logical channel corresponding to the RLC entity is used to transmit I frame data, and the other RLC entity is configured with an indication information. The RLC entity is configured with an indication information, and the indication information is used to indicate that the logical channel corresponding to the RLC entity is used to transmit P/B frame data.

The PDCP layer on the receiving end performs ACK/NACK feedback for the received data. There are three feedback schemes as follows:

Solution A) The receiving end performs ACK/NACK feedback according to the PDU level.

Solution B) The receiving end performs ACK/NACK feedback according to the PDU set level.

Solution C) The receiving end performs ACK/NACK feedback according to the GOP level.

If the PDCP layer at the sender does not concatenate the PDUs in a PDU set, the receiver side can perform ACK/NACK feedback at the PDU level, or ACK/NACK feedback at the PDU set level, or ACK/NACK feedback at the GOP level. If the PDCP layer at the sender performs cascading for PDUs in a PDU set, the receiver side can only perform ACK/NACK feedback at the PDU set level or ACK/NACK feedback at the GOP level.

In order to support the above feedback scheme, a new PDCP control PDU (ie, the first PDCP control PDU or ACK/NACK feedback response PDU) is introduced, and the receiving end performs ACK/NACK feedback through this PDCP control PDU. The format of the PDCP control PDU (hereinafter referred to as PDCP PDU) is implemented as follows:

Format 1: Figure 8-1 shows the format of the PDCP control PDU. Refer to Figure 8-1. The PDCP control PDU contains the following information: D/C information, PDU type (PDU Type), GOP identification, and the number of PDU set identifications. , The number of PDUs and bitmap contained in each PDU set. 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 bit value	meaning
0	Control PDU
1	Data 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 101, which is used to indicate that PDCP PDU is used for PDU level ACK/NACK feedback.

3 bit value	meaning
000	PDCP status report
001	Decentralized ROHC feedback
010	EHC feedback
011	GOP level ACK/NACK feedback
100	PDU set level ACK/NACK feedback
101	PDU level ACK/NACK feedback
110-111	reserve

Table 2

GOP identifier: The GOP identifier used to indicate the association of feedback information.

Number of PDU set identifiers: used to indicate the number of PDU sets contained in the GOP.

The number of PDUs contained in each PDU set: used to indicate the number of PDUs contained in each PDU set associated with the following bitmap.

Bitmap: Each bit in the bitmap corresponds to a PDU, and the value of the bit is used to indicate the ACK/NACK information of the PDU corresponding to the bit. Here, the corresponding relationship between the bits in the bitmap and the PDU is: in the order of PDU set identifiers from small to large, and in the order of PDU identifiers in each PDU set from small to large, and in the bitmap in order from low to large. The order to the highest position corresponds one to one.

The PDCP control PDU of the above format 1 is used for PDU-level ACK/NACK feedback, that is, feedback based on PDCP PDU. The PDCP control PDU gives the GOP identifier to which the feedback data belongs, the number of PDU sets in the GOP, and the number of PDUs contained in each PDU set. Then the PDU set identifier is from small to large, and then the PDU identifier in each PDU set is from small to large. The large sequence is mapped to a bitmap. Each bit in the bitmap corresponds to a PDU. A bit value of 0 indicates that the corresponding PDU is NACK, and a bit value of 1 indicates that the corresponding PDU is ACK.

Format 1: Figure 8-2 shows the format of the PDCP control PDU. Refer to Figure 8-2. The PDCP control PDU contains the following information: D/C information, PDU type (PDU Type), GOP identification, and multiple sets of information. Here , each set of information also includes the PDU set identifier, the number of PDUs included in the PDU set, and the bitmap. For the meaning of D/C information, PDU type (PDU Type), GOP identification, PDU set identification, and the number of PDUs contained in the PDU set, you can refer to the above-mentioned related solutions. For the bitmap, each bit in the bitmap corresponds to a PDU, and the value of the bit is used to indicate the ACK/NACK information of the PDU corresponding to the bit. Here, the corresponding relationship between the bits in the bitmap and the PDU is: the PDU identifiers in the PDU set are in ascending order, and correspond to the bitmap in the order from low to high.

The PDCP control PDU in format 2 above is used for PDU-level ACK/NACK feedback, that is, feedback based on PDCP PDU. The PDCP control PDU gives the GOP identifier to which the feedback data belongs, followed by the PDU set identifier in the GOP, the number of PDUs contained in the PDU set, and then the bitmap corresponding to the PDU set. Each PDU in the PDU set is small according to the PDU identifier. The large order is mapped to the bitmap. Each bit in the bitmap corresponds to a PDU. A bit value of 0 indicates that the corresponding PDU is NACK, and a bit value of 1 indicates that the corresponding PDU is ACK; Then there is the next PDU set identifier, the number of PDUs contained in the PDU set, and then the bitmap corresponding to the PDU set.

Format 3: Figure 8-3 shows the format of the PDCP control PDU. Refer to Figure 8-3. The PDCP control PDU contains the following information: D/C information, PDU type (PDU Type), GOP identification, and PDU contained in the GOP. Set number, bitmap. For the meaning of D/C information, PDU Type (PDU Type), and GOP identification, please refer to the above-mentioned related solutions. For the bitmap, each bit in the bitmap corresponds to a PDU set, and the value of the bit is used to indicate the ACK/NACK information of the PDU set corresponding to the bit. Here, the correspondence relationship between the bits in the bitmap and the PDU set is: in order from small to large PDU set identifiers, they correspond one-to-one with the bitmap in order from low to high.

The PDCP control PDU of the above format 3 is used for ACK/NACK feedback at the PDU set level. Here, if the PDCP layer at the sender performs the cascading operation for PDUs in a PDU set, ACK/NACK feedback based on the PDU set level can also be regarded as feedback based on PDCP PDUs. If the PDCP layer at the sender does not perform cascading operations, the PDU set corresponds to multiple PDCP PDUs. The PDCP control PDU gives the GOP identifier to which the feedback data belongs, the number of PDU sets in the GOP, and then the bitmap. Each PDU set in the GOP is mapped to the bitmap in order from small to large according to the PDU set identifier. The bitmap in the bitmap Each bit corresponds to a PDU set. A bit value of 0 indicates that the corresponding PDU set is NACK, and a bit value of 1 indicates that the corresponding PDU set is ACK. If at least one PDU in a PDU set is not received correctly, NACK will be fed back to the PDU set. If all PDUs in a PDU set are received correctly, ACK will be fed back to the PDU set.

Format 4: Figure 8-4 shows the format of the PDCP control PDU. Referring to Figure 8-4, the PDCP control PDU contains the following information: D/C information, PDU type (PDU Type), GOP identification, and A/N information. For the meaning of D/C information, PDU Type (PDU Type), and GOP identification, please refer to the above-mentioned related solutions. For A/N information, it refers to the ACK/NACK information corresponding to the GOP.

The PDCP control PDU of the above format 4 is used for ACK/NACK feedback at the GOP level. The PDCP control PDU gives the GOP identifier to which the feedback data belongs and the ACK/NACK information corresponding to the GOP. If all PDUs in the GOP are received correctly, ACK will be fed back, otherwise NACK will be fed back. Or, as long as the I frame in the GOP is received correctly, ACK will be fed back, otherwise NACK will be fed back.

Format 5: Figure 8-5 shows the format of the PDCP control PDU. This format can be regarded as the unified format of the above formats 1 to 4. As shown in Figure 8-5, the PDCP control PDU contains the following information: D/C information , PDU type (PDU Type), feedback type (FB type), GOP identification, number of PDU sets included in the GOP, number of PDUs included in each PDU set, bitmap. For D/C information, GOP identification, the number of PDU sets included in the GOP, the number of PDUs included in each PDU set, and the meaning of the bitmap, you can refer to the above-mentioned related solutions. For PDU type and feedback type, their meanings are explained as follows:

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

3 bit value	meaning
000	PDCP status report
001	Decentralized ROHC feedback
010	EHC feedback
011	ACK/NACK feedback response
100-111	reserve

table 3

Feedback type: used to indicate the feedback type corresponding to the PDCP control PDU. Optionally, the feedback type occupies 2 bits. As an example, the corresponding meanings of the 2-bit values are as shown in Table 4 below.

2 bit value	meaning
00	GOP level
01	PDU set level
10	PDU level
11	reserve

Table 4

The above PDCP control PDU of format five can be used for any of the following types of ACK/NACK feedback: GOP level ACK/NACK feedback, PDU set level, and PDU level. The feedback type field in the PDCP control PDU indicates whether the PDCP control PDU performs GOP-level ACK/NACK feedback, PDU set-level ACK/NACK feedback, or PDU-level ACK/NACK feedback.

If the feedback type in the PDCP control PDU indicates the GOP level, the PDCP control PDU provides the GOP identifier to which the feedback data belongs and the ACK/NACK information corresponding to the GOP. If all PDUs in the GOP are received correctly, the ACK/NACK information is ACK, otherwise it is NACK. Or, as long as the I frame in the GOP is received correctly, the ACK/NACK information is ACK, otherwise it is NACK.

If the feedback type in the PDCP control PDU indicates the PDU set level, the PDCP control PDU gives the GOP identifier to which the feedback data belongs and the number of PDU sets in the GOP, and then each PDU set feedback bitmap according to the PDU set identifier from small to large Corresponding ACK or NACK of data. For example, a bit set to 0 indicates that the corresponding PDU set feeds back NACK, and a bit set to 1 indicates that the corresponding PDU set feeds back ACK. If at least one PDU in a PDU set is not received correctly, NACK will be fed back. If all PDUs in a PDU set are received correctly, ACK will be fed back.

If the feedback type in the PDCP control PDU indicates the PDU level, the PDCP control PDU gives the GO identifier to which the feedback data belongs, the number of PDU sets in the GOP and the number of PDUs in each PDU set, and then according to the PDU set identifier from small to large , and then the bitmap of the PDU identifier in each PDU set from small to large corresponds to the ACK or NACK of the data. For example, setting the bit to 0 indicates that the corresponding PDU feeds back NACK, and setting the bit to 1 indicates that the corresponding PDU feeds back ACK.

The receiving end can send an ACK/NACK feedback response PDU based on the request of the sending end or at its own decision. For example, the receiving end sends an ACK/NACK feedback response PDU based on the timeout of the reordering timer of the PDCP PDU of one or several GOPs at the PDCP layer; for example, the receiving end sends an ACK/NACK feedback response PDU when the feedback conditions of the network configuration are met or the network side configuration enables feedback. In this case, send ACK/NACK feedback response PDU.

If the receiving end sends an ACK/NACK feedback response PDU based on the sending end's request, the ACK/NACK feedback requested by the sending end can be at the GOP level, or at the PDU set level, or at the PDU level. During specific implementation, a new PDCP control PDU (ie, the second PDCP control PDU or ACK/NACK feedback request PDU) is introduced, and the sending end performs an ACK/NACK feedback request through the PDCP control PDU. The format of the PDCP control PDU (hereinafter referred to as PDCP PDU) is implemented as follows:

Format I: Figure 9-1 shows the format of the PDCP control PDU. Referring to Figure 9-1, the PDCP control PDU contains the following information: D/C information, PDU type (PDU Type), feedback type (FB type), GOP logo. For the explanation of the meaning of D/C information, GOP logo, and feedback type, please refer to the above-mentioned related solutions. For PDU type, it is used to indicate the PDU type to which the PDCP control PDU belongs. Optionally, the PDU type occupies 3 bits. As an example, the corresponding meanings of the 3-bit values are as shown in Table 5 below. Here, the value of 3 bits is 011, which is used to indicate that PDCP PDU is used for ACK/NACK feedback request.

3 bit value	meaning
000	PDCP status report
001	Decentralized ROHC feedback
010	EHC feedback
011	ACK/NACK feedback request
100-111	reserve

table 5

If the feedback type given in the PDCP control PDU is GOP level, the receiving end performs ACK/NACK feedback according to the GOP level; if the feedback type given in the PDCP control PDU is PDU set level, the receiving end performs ACK/NACK according to the PDU set level. Feedback; if the feedback type given in the PDCP control PDU is PDU level, the receiving end performs ACK/NACK feedback according to the PDU level.

Further, optionally, the sending end can also indicate the PDU set for feedback in the PDCP control PDU. As an implementation method, the PDCP control PDU can contain the PDU set identifier set that needs feedback, as shown in Figure 9-2. As an implementation method, the PDCP control PDU can contain the starting value of the PDU set identifier that needs to be fed back and the end value of the PDU set identifier, as shown in Figure 9-3. As an implementation method, the PDCP control PDU can include the number of PDU sets that need feedback and the starting value of the PDU set identifier, as shown in Figure 9-4. As an implementation method, the PDCP control PDU can include the number of PDU sets that need to be fed back and the termination value of the PDU set identifier, as shown in Figure 9-5.

When a specific frame (such as an I frame) or a specific PDU set (such as the PDU set corresponding to an I frame) or a specific PDU (such as a PDU within an I frame) in the GOP is lost, the PDCP layer at the receiving end will delete the The untransmitted data (such as PDCP PDU, PDCP SDU) will also be notified to the underlying RLC entity to delete the data in the GOP.

Application example two

Referring to Figure 10, when all frames (I frames, P frames, B frames) in a GOP come from the same Qos flow, the network side can configure the following types of bearers to transmit the video data in this Qos flow:

Option 1: One PDCP entity and 2 RLC entities. One RLC entity is used to transmit I frames and can be an AM RLC entity or UM RLC entity. The other RLC entity is used to transmit P/B frames and can be a UM RLC entity.

Option 2: One PDCP entity and one AM RLC entity are used to transmit I frames, and one PDCP entity and one UM RLC entity are used to transmit P/B frames.

Option 3: One PDCP entity and one UM RLC entity for transmitting I/P/B frames.

No matter what type of bearer it is, for downlink data, GTP end marker is defined to split the PDU set or frame in a Qos flow. The SDAP layer identifies the PDU set or frame through the GTP end marker. Furthermore, the SDAP layer inserts the SDAP end marker after each PDU set or frame to split the PDU set or frame in a Qos flow. The PDCP layer identifies the PDU set or frame through the SDAP end marker. For upstream data, it depends on the implementation of the terminal device to distinguish PDU sets or frames. Here, GTP end marker and SDAP end marker include at least one of the following information: GOP identifier, PDU set identifier, frame type, Qos flow identifier, last frame indication in the GOP, number of frames included in the GOP, and GOP associated with the GOP List, Qos flow identification. Generally, GTP end marker and SDAP end marker are transmitted behind a PDU set.

Regardless of the type of bearer, for downlink data, the first information can be carried in the GTP header and/or SDAP header corresponding to each PDU. The first information includes at least one of the following: GOP identifier, PDU set identifier, PDU identifier, frame type, last frame indication in the GOP, number of frames contained in the GOP, GOP list associated with the GOP, Qos flow identifier, used to assist the PDCP layer in identifying the PDU, frame type, and the distance between PDUs in a PDU set Association relationship, association relationship between frames in a GOP, and association relationship between GOPs.

Referring to Figure 7, for the bearer types described in option 1, option 2, or option 3 above, the PDCP layer at the sender can implement the cascading function, that is, all PDUs in a PDU set are assembled into one PDCP PDU for unification. of sending. The receiving end can disassemble the cascaded PDCP PDU into SDAP PDU corresponding to each PDU. Here, the sender performs the cascading function after encryption and integrity protection. The receiving end performs disassembly after removing the packet header, and processes the disassembled data safely.

For the bearer types described in option 1, option 2, or option 3 above, the PDCP layer at the sender can identify the SDAP PDU corresponding to the frame type information carried in the SDAP header or the frame type information carried in the SDAP end marker. Frame type of PDU. Alternatively, the PDCP layer at the sender identifies the frame type of the PDU corresponding to the SDAP PDU based on the Qos flow identifier (QFI) carried in the SDAP header and the correspondence between QFI and frame type. Correspondingly, the sending end can configure the corresponding relationship between QFI and frame type for the receiving end through RRC signaling, and the receiving end identifies the frame type of the data based on the QFI of the Qos flow where the data is located and the corresponding relationship.

For the bearer types described in option 1, option 2, or option 3 above, in order to let the PDCP layer on the receiving end know the frame type of the received data and which data belongs to the same PDU set or GOP, the PDCP layer on the sending end The layer carries at least the GOP identifier and frame type in the PDCP header. It can also carry information such as the PDU set identifier, the last frame indication in a GOP, and the number of frames contained in the GOP.

For the bearer type described in option 1 above, the receiving end can identify the frame type corresponding to the data from the RLC entity based on the correspondence between the logical channel identifier configured in the RRC signaling and the frame type, such as whether it belongs to an I frame or an I frame. Belongs to P/B frame. Here, there is a corresponding relationship between the logical channel identifier corresponding to the RLC entity and the frame type, and the corresponding relationship can be configured to the receiving end through RRC signaling. For example: Configure the frame type corresponding to the transmission data of two RLC entities through RRC dedicated signaling. For example, one RLC entity is configured with an indication information. The indication information is used to indicate that the logical channel corresponding to the RLC entity is used to transmit I frame data, and the other RLC entity is configured with an indication information. The RLC entity is configured with an indication information, and the indication information is used to indicate that the logical channel corresponding to the RLC entity is used to transmit P/B frame data.

The PDCP layer on the receiving end performs ACK/NACK feedback for the received data. There are three feedback schemes as follows:

Solution A) The receiving end performs ACK/NACK feedback according to the PDU level.

Solution B) The receiving end performs ACK/NACK feedback according to the PDU set level.

Solution C) The receiving end performs ACK/NACK feedback according to the GOP level.

If the PDCP layer at the sender does not concatenate the PDUs in a PDU set, the receiver side can perform ACK/NACK feedback at the PDU level, or ACK/NACK feedback at the PDU set level, or ACK/NACK feedback at the GOP level. If the PDCP layer at the sender performs cascading for PDUs in a PDU set, the receiver side can only perform ACK/NACK feedback at the PDU set level or ACK/NACK feedback at the GOP level.

In order to support the above feedback scheme, a new PDCP control PDU (ie, the first PDCP control PDU or ACK/NACK feedback response PDU) is introduced, and the receiving end performs ACK/NACK feedback through this PDCP control PDU. The format of the PDCP control PDU (hereinafter referred to as PDCP PDU) can refer to the solution of the aforementioned application example 1, and will not be described again.

The receiving end can send an ACK/NACK feedback response PDU based on the request of the sending end or at its own decision. For example, the receiving end sends an ACK/NACK feedback response PDU based on the timeout of the reordering timer of the PDCP PDU of one or several GOPs at the PDCP layer; for example, the receiving end sends an ACK/NACK feedback response PDU when the feedback conditions of the network configuration are met or the network side configuration enables feedback. In this case, send ACK/NACK feedback response PDU.

If the receiving end sends an ACK/NACK feedback response PDU based on the sending end's request, the ACK/NACK feedback requested by the sending end can be at the GOP level, or at the PDU set level, or at the PDU level. During specific implementation, a new PDCP control PDU (i.e., the second PDCP control PDU or ACK/NACK feedback request PDU) is introduced, and the sending end performs an ACK/NACK feedback request through this PDCP control PDU. The format of the PDCP control PDU (hereinafter referred to as PDCP PDU) can refer to the solution of the aforementioned application example 1, and will not be described again.

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. As shown in Figure 11, the data transmission device has a first protocol layer 1101 and a second protocol layer 1102;

The first protocol layer 1101 is used to receive one or more PDU sets sent by the second protocol layer;

The second protocol layer 1102 is used to send one or more PDU sets to the first protocol layer;

The header corresponding to each PDU in the PDU set carries the first information and/or the first flag is transmitted after the PDU set, where,

The first information includes at least one of the following: GOP identifier, PDU set identifier, PDU identifier, frame type, last frame indication in the GOP, number of frames included in the GOP, GOP list associated with the GOP, Qos flow identifier;

The first flag includes at least one of the following: GOP identifier, PDU set identifier, frame type, Qos flow identifier, last frame indication in the GOP, number of frames included in the GOP, GOP list associated with the GOP, and Qos flow identifier.

In some optional implementations, when the PDU set or frames within a GOP come from the same Qos flow, the data in one Qos flow is transmitted through one of the following types of bearers:

A first type bearer, the first type bearer corresponds to a PDCP entity and an RLC entity, and the mode of the RLC entity is the UM mode;

A second type bearer, the second type bearer corresponds to one PDCP entity and one RLC entity, and the mode of the RLC entity is AM mode;

A third type bearer, the third type bearer corresponds to one PDCP entity and two RLC entities, one of the two RLC entities is in AM mode and the other RLC entity is in UM mode, or the two RLC entities are all in UM mode.

In some optional implementations, when a PDU set or frame within a GOP comes from at least two Qos flows, the data in the at least two Qos flows is transmitted through one of the following types of bearers:

A first type bearer, the first type bearer corresponds to a PDCP entity and an RLC entity, and the mode of the RLC entity is the UM mode;

A third type bearer, the third type bearer corresponds to one PDCP entity and two RLC entities, one of the two RLC entities is in AM mode and the other RLC entity is in UM mode, or the two RLC entities are all in UM mode;

The fourth type of bearer includes two bearers, one of the two bearers corresponds to a PDCP entity and an AM mode RLC entity, and the other bearer corresponds to a PDCP entity and an UM mode RLC entity.

In some optional implementations, the second protocol layer is a GTP layer, the first protocol layer is an SDAP layer, the header is a GTP header, and the first flag is carried in a GTP packet.

In some optional implementations, the second protocol layer is the SDAP layer, the first protocol layer is the PDCP layer, the header is an SDAP header, and the first flag is carried in the SDAP control PDU.

In some optional implementations, the PDCP layer determines the frame type of the PDU based on the frame type carried in the SDAP header corresponding to the PDU and/or the frame type in the first flag; or, the PDCP layer Determine the frame type of the PDU based on the Qos flow identifier carried in the SDAP header corresponding to the PDU and/or the Qos flow identifier in the first flag, and a first correspondence relationship, wherein the first correspondence relationship is Qos Correspondence between stream identifiers and frame types.

In some optional implementations, the PDCP layer determines the logical channel identifier corresponding to the PDU based on the frame type of the PDU and the second corresponding relationship, and delivers the PDU to the corresponding RLC based on the determined logical channel identifier. Entity; wherein the second correspondence is a correspondence between frame type and logical channel identifier.

In some optional implementations, the second correspondence relationship is configured to the receiving end through RRC signaling, and the second correspondence relationship is used by the PDCP layer of the receiving end to determine the source from the RLC based on the logical channel identifier corresponding to the RLC entity. The frame type of the entity's PDU.

In some optional implementations, the first correspondence is configured to the receiving end through RRC signaling, and the first correspondence is used by the PDCP layer of the receiving end to determine the frame of the PDU based on the Qos flow identifier corresponding to the PDU. type.

In some optional implementations, the PDCP layer carries at least part of the first information in the PDCP header corresponding to each PDU in the PDU set.

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. As shown in Figure 12, the device includes:

The sending unit 1201 is configured to send a first PDCP control PDU to the second node, where the first PDCP control PDU carries feedback information, where the feedback information is used to indicate at least one of the following:

ACK/NACK information for one or more PDUs;

ACK/NACK information of one or more PDU sets;

ACK/NACK information for one or more GOPs.

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

First information, the first information is used to indicate the GOP identification associated with the feedback information;

Second information, the second information is used to indicate the number of PDU sets contained in the GOP;

Third information, the third information is used to indicate the number of PDUs contained in each PDU set;

A first bitmap, each bit in the first bitmap corresponds to a PDU, and the value of the bit is used to indicate the ACK/NACK information of the PDU corresponding to the bit.

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

First information, the first information is used to indicate the GOP identification associated with the feedback information;

At least one set of information, each set of information corresponding to a PDU set in the GOP, each set of information includes fourth information, fifth information and a second bitmap, the fourth information is used to indicate the PDU set identification, the third Five information is used to indicate the number of PDUs contained in the PDU set. Each bit in the second bitmap corresponds to one PDU. The value of the bit is used to indicate the ACK/NACK of the PDU corresponding to the bit. information.

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

First information, the first information is used to indicate the GOP identification associated with the feedback information;

Second information, the second information is used to indicate the number of PDU sets contained in the GOP;

The third bitmap, each bit in the third bitmap corresponds to a PDU set, and the value of the bit is used to indicate the ACK/NACK information of the PDU set corresponding to the bit.

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

First information, the first information is used to indicate the GOP identification associated with the feedback information;

Sixth information, the sixth information is ACK/NACK information corresponding to the GOP.

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

Seventh information, the seventh information is used to indicate whether the first PDCP control PDU is a data PDU or a control PDU;

Eighth information, the eighth information is used to indicate the PDU type to which the first PDCP control PDU belongs.

In some optional implementations, the PDU type is one of the following:

A first PDU type, the first PDU type is used for PDU level ACK/NACK feedback;

A second PDU type, the second PDU type is used for ACK/NACK feedback at the PDU set level;

A third PDU type, the third PDU type is used for ACK/NACK feedback at the GOP level.

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

First information, the first information is used to indicate the GOP identification associated with the feedback information;

Second information, the second information is used to indicate the number of PDU sets contained in the GOP;

Third information, the third information is used to indicate the number of PDUs contained in each PDU set;

A first bitmap, each bit in the first bitmap corresponds to a PDU, and the value of the bit is used to indicate the ACK/NACK information of the PDU corresponding to the bit;

A third bitmap, each bit in the third bitmap corresponds to a PDU set, and the value of the bit is used to indicate the ACK/NACK information of the PDU set corresponding to the bit;

Sixth information, the sixth information is ACK/NACK information corresponding to the GOP.

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

Seventh information, the seventh information is used to indicate whether the first PDCP control PDU is a data PDU or a control PDU;

Eighth information, the eighth information is used to indicate the PDU type to which the first PDCP control PDU belongs;

Ninth information, the ninth information is used to indicate the feedback type corresponding to the first PDCP control PDU.

In some optional implementations, when the feedback type is PDU-level ACK/NACK feedback, the first PDCP control PDU includes the first information, the second information, the third information and At least one of the first bitmaps.

In some optional implementations, when the feedback type is PDU set level ACK/NACK feedback, the first PDCP control PDU includes the first information, the second information and the second bit At least one of the pictures.

In some optional implementations, when the feedback type is GOP-level ACK/NACK feedback, the first PDCP control PDU includes at least one of the first information and the sixth information.

In some optional implementations, the correspondence between the bits in the first bitmap and the PDU is:

According to the order of PDU set identifiers from small to large, and then according to the order of PDU identifiers in each PDU set from small to large, they correspond to the first bitmap in order from low to high.

In some optional implementations, the correspondence between the bits in the second bitmap and the PDU is:

According to the order of PDU identifiers from small to large, they correspond to the second bitmap in order from low to high.

In some optional implementations, the correspondence between the bits in the third bitmap and the PDU set is:

According to the order of PDU set identifiers from small to large, they correspond to the third bitmap in order from low to high.

In some optional implementations, if at least one PDU in a PDU set is not received correctly, the ACK/NACK information corresponding to the PDU set is NACK; if all PDUs in a PDU set are received correctly, then the The ACK/NACK information corresponding to the PDU set is ACK.

In some optional implementations, if at least one PDU in the GOP is not received correctly, the ACK/NACK information corresponding to the GOP is NACK; if all PDUs in the GOP are received correctly, the ACK/NACK information corresponding to the GOP is The NACK information is ACK; or, if the specific PDU Set or specific frame in the GOP is not received correctly, the ACK/NACK information corresponding to the GOP is NACK; if the specific PDU Set or specific frame in the GOP is received correctly, then the The ACK/NACK information corresponding to the GOP is ACK.

In some optional implementations, the device further includes: a receiving unit 1202, configured to receive the PDCP PDU sent by the second node; if the PDCP PDU carries multiple PDUs in the PDU set, the first A node performs PDU set level ACK/NACK feedback and/or GOP level ACK/NACK feedback through the first PDCP control PDU; if the PDCP PDU carries a PDU in the PDU set, then the first node The first PDCP controls the PDU to perform PDU level ACK/NACK feedback and/or PDU set level ACK/NACK feedback and/or GOP level ACK/NACK feedback.

In some optional implementations, the sending unit 1201 is configured to send the first PDCP control PDU to the second node based on the request of the second node; or, based on its own implementation, send the first PDCP control PDU to the second node. Send the first PDCP control PDU.

In some optional implementations, the device further includes: a receiving unit 1202, configured to receive a second PDCP control PDU sent by the second node, where the second PDCP control PDU is used to request feedback information, wherein The feedback type of the feedback information is PDU level ACK/NACK feedback or PDU set level ACK/NACK feedback or GOP level ACK/NACK feedback.

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

First information, the first information is used to indicate the GOP identification associated with the feedback information;

Tenth information, the tenth information is used to indicate the feedback type requested by the second PDCP control PDU.

In some optional implementations, the second PDCP control PDU is also used to indicate the PDU set that requires feedback; the second PDCP control PDU also includes at least one of the following information:

PDU set identification list;

The number of PDU set identifiers;

The starting value of the PDU set identifier;

The end value of the PDU set identifier.

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

Eleventh information, the eleventh information is used to indicate whether the second PDCP control PDU is a data PDU or a control PDU;

Twelfth information, the twelfth information is used to indicate the PDU type to which the second PDCP control PDU belongs.

In some optional implementations, if the feedback type requested by the second PDCP control PDU is PDU-level ACK/NACK feedback, the first node carries one or more PDUs in the first PDCP control PDU. ACK/NACK information; if the feedback type requested by the second PDCP control PDU is PDU set level ACK/NACK feedback, the first node carries one or more PDU sets in the first PDCP control PDU ACK/NACK information; if the feedback type requested by the second PDCP control PDU is GOP-level ACK/NACK feedback, the first node carries one or more GOP ACKs in the first PDCP control PDU. /NACK message.

In some optional implementations, the device further includes: a processing unit 1203, configured to delete undelivered frames in the GOP through the PDCP layer when it is determined that a specific frame or a specific PDU set or a specific PDU has been lost. PDU and/or notify the RLC layer to delete the PDU to be delivered in the GOP.

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 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. As shown in Figure 13, the device includes:

The receiving unit 1301 is configured to receive the first PDCP control PDU sent by the first node, where the first PDCP control PDU carries feedback information, where the feedback information is used to indicate at least one of the following:

ACK/NACK information for one or more PDUs;

ACK/NACK information of one or more PDU sets;

ACK/NACK information for one or more GOPs.

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

First information, the first information is used to indicate the GOP identifier associated with the feedback information;

Second information, the second information is used to indicate the number of PDU sets contained in the GOP;

Third information, the third information is used to indicate the number of PDUs contained in each PDU set;

A first bitmap, each bit in the first bitmap corresponds to a PDU, and the value of the bit is used to indicate the ACK/NACK information of the PDU corresponding to the bit.

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

First information, the first information is used to indicate the GOP identifier associated with the feedback information;

At least one set of information, each set of information corresponding to a PDU set in the GOP, each set of information includes fourth information, fifth information and a second bitmap, the fourth information is used to indicate the PDU set identification, the third Five information is used to indicate the number of PDUs contained in the PDU set. Each bit in the second bitmap corresponds to one PDU. The value of the bit is used to indicate the ACK/NACK of the PDU corresponding to the bit. information.

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

First information, the first information is used to indicate the GOP identification associated with the feedback information;

Second information, the second information is used to indicate the number of PDU sets contained in the GOP;

The third bitmap, each bit in the third bitmap corresponds to a PDU set, and the value of the bit is used to indicate the ACK/NACK information of the PDU set corresponding to the bit.

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

First information, the first information is used to indicate the GOP identification associated with the feedback information;

Sixth information, the sixth information is ACK/NACK information corresponding to the GOP.

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

Seventh information, the seventh information is used to indicate whether the first PDCP control PDU is a data PDU or a control PDU;

Eighth information, the eighth information is used to indicate the PDU type to which the first PDCP control PDU belongs.

In some optional implementations, the PDU type is one of the following:

A first PDU type, the first PDU type is used for PDU level ACK/NACK feedback;

A second PDU type, the second PDU type is used for ACK/NACK feedback at the PDU set level;

A third PDU type, the third PDU type is used for ACK/NACK feedback at the GOP level.

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

First information, the first information is used to indicate the GOP identifier associated with the feedback information;

Second information, the second information is used to indicate the number of PDU sets contained in the GOP;

Third information, the third information is used to indicate the number of PDUs contained in each PDU set;

A first bitmap, each bit in the first bitmap corresponds to a PDU, and the value of the bit is used to indicate the ACK/NACK information of the PDU corresponding to the bit;

A third bitmap, each bit in the third bitmap corresponds to a PDU set, and the value of the bit is used to indicate the ACK/NACK information of the PDU set corresponding to the bit;

Sixth information, the sixth information is ACK/NACK information corresponding to the GOP.

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

Seventh information, the seventh information is used to indicate whether the first PDCP control PDU is a data PDU or a control PDU;

Eighth information, the eighth information is used to indicate the PDU type to which the first PDCP control PDU belongs;

Ninth information, the ninth information is used to indicate the feedback type corresponding to the first PDCP control PDU.

In some optional implementations, when the feedback type is PDU-level ACK/NACK feedback, the first PDCP control PDU includes the first information, the second information, the third information and At least one of the first bitmaps.

In some optional implementations, when the feedback type is PDU set level ACK/NACK feedback, the first PDCP control PDU includes the first information, the second information and the second bit At least one of the pictures.

In some optional implementations, when the feedback type is GOP-level ACK/NACK feedback, the first PDCP control PDU includes at least one of the first information and the sixth information.

In some optional implementations, the correspondence between the bits in the first bitmap and the PDU is:

According to the order of PDU set identifiers from small to large, and then according to the order of PDU identifiers in each PDU set from small to large, they correspond to the first bitmap in order from low to high.

In some optional implementations, the correspondence between the bits in the second bitmap and the PDU is:

According to the order of PDU identifiers from small to large, they correspond to the second bitmap in order from low to high.

In some optional implementations, the correspondence between the bits in the third bitmap and the PDU set is:

According to the order of PDU set identifiers from small to large, they correspond to the third bitmap in order from low to high.

In some optional implementations, if at least one PDU in a PDU set is not received correctly, the ACK/NACK information corresponding to the PDU set is NACK; if all PDUs in a PDU set are received correctly, then the The ACK/NACK information corresponding to the PDU set is ACK.

In some optional implementations, if at least one PDU in the GOP is not received correctly, the ACK/NACK information corresponding to the GOP is NACK; if all PDUs in the GOP are received correctly, the ACK/NACK information corresponding to the GOP is The NACK information is ACK; or, if the specific PDU Set or specific frame in the GOP is not received correctly, the ACK/NACK information corresponding to the GOP is NACK; if the specific PDU Set or specific frame in the GOP is received correctly, then the The ACK/NACK information corresponding to the GOP is ACK.

In some optional implementations, the device further includes a sending unit 1302, configured to send a second PDCP control PDU to the first node, where the second PDCP control PDU is used to request feedback information, wherein the feedback The feedback type of information is PDU level ACK/NACK feedback or PDU set level ACK/NACK feedback or GOP level ACK/NACK feedback.

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

First information, the first information is used to indicate the GOP identification associated with the feedback information;

Tenth information, the tenth information is used to indicate the feedback type requested by the second PDCP control PDU.

In some optional implementations, the second PDCP control PDU is also used to indicate the PDU set that requires feedback; the second PDCP control PDU also includes at least one of the following information:

PDU set identification list;

The number of PDU set identifiers;

The starting value of the PDU set identifier;

The end value of the PDU set identifier.

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

Eleventh information, the eleventh information is used to indicate whether the second PDCP control PDU is a data PDU or a control PDU;

Twelfth information, the twelfth information is used to indicate the PDU type to which the second PDCP control PDU belongs.

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 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, and the indirect coupling or communication connection of the devices or units 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 (64)

1. A data transmission method, the method includes:

   The first protocol layer receives one or more packet data unit sets PDU set sent by the second protocol layer. The header corresponding to each packet data unit PDU in the PDU set carries the first information and/or after the PDU set The transmission has the first flag, where,

   The first information includes at least one of the following: image group GOP identification, PDU set identification, PDU identification, frame type, last frame indication in the GOP, number of frames included in the GOP, GOP list associated with the GOP, quality of service Qos stream identifier;

   The first flag includes at least one of the following: GOP identifier, PDU set identifier, frame type, Qos flow identifier, last frame indication in the GOP, number of frames included in the GOP, GOP list associated with the GOP, and Qos flow identifier.
2. The method according to claim 1, wherein, for the situation that the PDU set or frame within a GOP comes from the same Qos flow, the data in the one Qos flow is transmitted through one of the following types of bearers:

   A first type bearer, the first type bearer corresponds to a Packet Data Convergence Protocol PDCP entity and a Radio Link Layer Control RLC entity, and the mode of the RLC entity is the unacknowledged mode UM mode;

   A second type bearer, the second type bearer corresponds to a PDCP entity and an RLC entity, and the mode of the RLC entity is the acknowledgment mode AM mode;

   A third type bearer, the third type bearer corresponds to one PDCP entity and two RLC entities, one of the two RLC entities is in AM mode and the other RLC entity is in UM mode, or the two RLC entities are all in UM mode.
3. The method according to claim 1, wherein, for a PDU set or frame within a GOP from at least two Qos flows, the data in the at least two Qos flows is transmitted through one of the following types of bearers:

   A first type bearer, the first type bearer corresponds to a PDCP entity and an RLC entity, and the mode of the RLC entity is the UM mode;

   A third type bearer, the third type bearer corresponds to one PDCP entity and two RLC entities, one of the two RLC entities is in AM mode and the other RLC entity is in UM mode, or the two RLC entities are all in UM mode;

   The fourth type of bearer includes two bearers, one of the two bearers corresponds to a PDCP entity and an AM mode RLC entity, and the other bearer corresponds to a PDCP entity and an UM mode RLC entity.
4. The method according to any one of claims 1 to 3, wherein the second protocol layer is a GPRS tunnel protocol GTP layer, the first protocol layer is a service data adaptation protocol SDAP layer, and the packet header is GTP Packet header, the first flag is carried in the GTP packet.
5. The method according to any one of claims 1 to 3, wherein the second protocol layer is an SDAP layer, the first protocol layer is a PDCP layer, the packet header is an SDAP packet header, and the first flag carries in the SDAP control PDU.
6. The method of claim 5, further comprising:

   The PDCP layer determines the frame type of the PDU based on the frame type carried in the SDAP header corresponding to the PDU and/or the frame type in the first flag; or,

   The PDCP layer determines the frame type of the PDU based on the Qos flow identifier carried in the SDAP header corresponding to the PDU and/or the Qos flow identifier in the first flag, and a first correspondence relationship, wherein the first The corresponding relationship is the corresponding relationship between the Qos flow identifier and the frame type.
7. The method of claim 6, further comprising:

   The PDCP layer determines the logical channel identifier corresponding to the PDU based on the frame type of the PDU and the second corresponding relationship, and delivers the PDU to the corresponding RLC entity based on the determined logical channel identifier; wherein, the second The corresponding relationship is the corresponding relationship between the frame type and the logical channel identifier.
8. The method according to claim 7, wherein the second correspondence relationship is configured to the receiving end through Radio Resource Control (RRC) signaling, and the second correspondence relationship is used for the logical channel corresponding to the PDCP layer of the receiving end based on the RLC entity. The identification determines the frame type of the PDU from the RLC entity.
9. The method according to claim 6, wherein the first correspondence is configured to the receiving end through RRC signaling, and the first correspondence is used by the PDCP layer of the receiving end to determine the Qos flow identifier corresponding to the PDU. Frame type of PDU.
10. The method according to any one of claims 5 to 9, wherein the method further comprises:

    The PDCP layer carries at least part of the first information in the PDCP header corresponding to each PDU in the PDU set.
11. A data transmission method, the method includes:

    The first node sends a first PDCP control PDU to the second node, where the first PDCP control PDU carries feedback information, where the feedback information is used to indicate at least one of the following:

    Positive acknowledgment ACK/negative acknowledgment NACK information for one or more PDUs;

    ACK/NACK information of one or more PDU sets;

    ACK/NACK information for one or more GOPs.
12. The method according to claim 11, wherein the first PDCP control PDU includes at least one of the following information:

    First information, the first information is used to indicate the GOP identifier associated with the feedback information;

    Second information, the second information is used to indicate the number of PDU sets contained in the GOP;

    Third information, the third information is used to indicate the number of PDUs contained in each PDU set;

    A first bitmap, each bit in the first bitmap corresponds to a PDU, and the value of the bit is used to indicate the ACK/NACK information of the PDU corresponding to the bit.
13. The method according to claim 11, wherein the first PDCP control PDU includes at least one of the following information:

    First information, the first information is used to indicate the GOP identifier associated with the feedback information;

    At least one set of information, each set of information corresponding to a PDU set in the GOP, each set of information includes fourth information, fifth information and a second bitmap, the fourth information is used to indicate the PDU set identification, the third Five information is used to indicate the number of PDUs contained in the PDU set. Each bit in the second bitmap corresponds to one PDU. The value of the bit is used to indicate the ACK/NACK of the PDU corresponding to the bit. information.
14. The method according to claim 11, wherein the first PDCP control PDU includes at least one of the following information:

    First information, the first information is used to indicate the GOP identification associated with the feedback information;

    Second information, the second information is used to indicate the number of PDU sets contained in the GOP;

    The third bitmap, each bit in the third bitmap corresponds to a PDU set, and the value of the bit is used to indicate the ACK/NACK information of the PDU set corresponding to the bit.
15. The method according to claim 11, wherein the first PDCP control PDU includes at least one of the following information:

    First information, the first information is used to indicate the GOP identifier associated with the feedback information;

    Sixth information, the sixth information is ACK/NACK information corresponding to the GOP.
16. The method according to any one of claims 12 to 15, wherein the first PDCP control PDU further includes at least one of the following information:

    Seventh information, the seventh information is used to indicate whether the first PDCP control PDU is a data PDU or a control PDU;

    Eighth information, the eighth information is used to indicate the PDU type to which the first PDCP control PDU belongs.
17. The method according to claim 16, wherein the PDU type is one of the following:

    A first PDU type, the first PDU type is used for PDU level ACK/NACK feedback;

    A second PDU type, the second PDU type is used for ACK/NACK feedback at the PDU set level;

    A third PDU type, the third PDU type is used for ACK/NACK feedback at the GOP level.
18. The method according to claim 11, wherein the first PDCP control PDU includes at least one of the following information:

    First information, the first information is used to indicate the GOP identification associated with the feedback information;

    Second information, the second information is used to indicate the number of PDU sets contained in the GOP;

    Third information, the third information is used to indicate the number of PDUs contained in each PDU set;

    A first bitmap, each bit in the first bitmap corresponds to a PDU, and the value of the bit is used to indicate the ACK/NACK information of the PDU corresponding to the bit;

    A third bitmap, each bit in the third bitmap corresponds to a PDU set, and the value of the bit is used to indicate the ACK/NACK information of the PDU set corresponding to the bit;

    Sixth information, the sixth information is ACK/NACK information corresponding to the GOP.
19. The method according to claim 18, wherein the first PDCP control PDU further includes at least one of the following information:

    Seventh information, the seventh information is used to indicate whether the first PDCP control PDU is a data PDU or a control PDU;

    Eighth information, the eighth information is used to indicate the PDU type to which the first PDCP control PDU belongs;

    Ninth information, the ninth information is used to indicate the feedback type corresponding to the first PDCP control PDU.
20. The method according to claim 19, wherein when the feedback type is PDU-level ACK/NACK feedback, the first PDCP control PDU includes the first information, the second information, the third at least one of three pieces of information and the first bitmap.
21. The method according to claim 19, wherein when the feedback type is PDU set level ACK/NACK feedback, the first PDCP control PDU includes the first information, the second information and the At least one of the second bitmaps.
22. The method according to claim 19, wherein when the feedback type is GOP-level ACK/NACK feedback, the first PDCP control PDU includes at least one of the first information and the sixth information. one.
23. The method according to claim 12 or 18, wherein the corresponding relationship between the bits in the first bitmap and the PDU is:

    According to the order of PDU set identifiers from small to large, and then according to the order of PDU identifiers in each PDU set from small to large, they correspond to the first bitmap in order from low to high.
24. The method according to claim 13, wherein the corresponding relationship between the bits in the second bitmap and the PDU is:

    According to the order of PDU identifiers from small to large, they correspond to the second bitmap in order from low to high.
25. The method according to claim 14 or 18, wherein the corresponding relationship between the bits in the third bitmap and the PDU set is:

    According to the order of PDU set identifiers from small to large, they correspond to the third bitmap in order from low to high.
26. The method according to any one of claims 14, 18, and 21, wherein,

    If at least one PDU in a PDU set is not received correctly, the ACK/NACK information corresponding to the PDU set is NACK;

    If all PDUs in a PDU set are received correctly, the ACK/NACK information corresponding to the PDU set is ACK.
27. The method according to any one of claims 15, 18, and 22, wherein,

    If at least one PDU in the GOP is not received correctly, the ACK/NACK information corresponding to the GOP is NACK; if all PDUs in the GOP are received correctly, the ACK/NACK information corresponding to the GOP is ACK; or,

    If the specific PDU Set or specific frame in the GOP is not received correctly, the ACK/NACK information corresponding to the GOP is NACK; if the specific PDU Set or specific frame in the GOP is received correctly, the ACK/NACK information corresponding to the GOP for ACK.
28. The method according to any one of claims 11 to 27, wherein before the first node sends the first PDCP control PDU to the second node, the method further includes:

    The first node receives the PDCP PDU sent by the second node;

    If the PDCP PDU carries multiple PDUs in the PDU set, the first node performs ACK/NACK feedback at the PDU set level and/or ACK/NACK feedback at the GOP level through the first PDCP control PDU;

    If the PDCP PDU carries a PDU in the PDU set, the first node uses the first PDCP control PDU to perform PDU level ACK/NACK feedback and/or PDU set level ACK/NACK feedback and/or GOP level ACK/NACK feedback.
29. The method according to any one of claims 11 to 28, wherein the first node sends a first PDCP control PDU to the second node, including:

    The first node sends a first PDCP control PDU to the second node based on the request of the second node; or,

    The first node sends a first PDCP control PDU to the second node based on its own implementation.
30. The method according to claim 29, wherein when the first node sends a first PDCP control PDU to the second node based on the request of the second node, the method further includes:

    The first node receives a second PDCP control PDU sent by the second node, and the second PDCP control PDU is used to request feedback information, wherein the feedback type of the feedback information is PDU-level ACK/NACK feedback or PDU set level ACK/NACK feedback or GOP level ACK/NACK feedback.
31. The method according to claim 30, wherein the second PDCP control PDU includes at least one of the following information:

    First information, the first information is used to indicate the GOP identification associated with the feedback information;

    Tenth information, the tenth information is used to indicate the feedback type requested by the second PDCP control PDU.
32. The method according to claim 31, wherein the second PDCP control PDU is also used to indicate a PDU set that requires feedback; the second PDCP control PDU further includes at least one of the following information:

    PDU set identification list;

    The number of PDU set identifiers;

    The starting value of the PDU set identifier;

    The end value of the PDU set identifier.
33. The method according to claim 31 or 32, wherein the second PDCP control PDU further includes at least one of the following information:

    Eleventh information, the eleventh information is used to indicate whether the second PDCP control PDU is a data PDU or a control PDU;

    Twelfth information, the twelfth information is used to indicate the PDU type to which the second PDCP control PDU belongs.
34. The method according to any one of claims 30 to 33, wherein,

    If the feedback type requested by the second PDCP control PDU is PDU-level ACK/NACK feedback, the first node carries ACK/NACK information of one or more PDUs in the first PDCP control PDU;

    If the feedback type requested by the second PDCP control PDU is ACK/NACK feedback at the PDU set level, the first node carries ACK/NACK information of one or more PDU sets in the first PDCP control PDU;

    If the feedback type requested by the second PDCP control PDU is GOP-level ACK/NACK feedback, the first node carries ACK/NACK information of one or more GOPs in the first PDCP control PDU.
35. The method according to any one of claims 11 to 34, wherein the method further comprises:

    When the first node determines that a specific frame or a specific PDU set or a specific PDU in the GOP has been lost, the PDCP layer of the first node deletes the undelivered PDUs in the GOP and/or notifies the RLC layer to delete all Describes the PDU to be submitted in the GOP.
36. A data transmission method, the method includes:

    The second node receives the first PDCP control PDU sent by the first node, and the first PDCP control PDU carries feedback information, where the feedback information is used to indicate at least one of the following:

    ACK/NACK information for one or more PDUs;

    ACK/NACK information of one or more PDU sets;

    ACK/NACK information for one or more GOPs.
37. The method of claim 36, wherein the first PDCP control PDU includes at least one of the following information:

    First information, the first information is used to indicate the GOP identification associated with the feedback information;

    Second information, the second information is used to indicate the number of PDU sets contained in the GOP;

    Third information, the third information is used to indicate the number of PDUs contained in each PDU set;

    A first bitmap, each bit in the first bitmap corresponds to a PDU, and the value of the bit is used to indicate the ACK/NACK information of the PDU corresponding to the bit.
38. The method of claim 36, wherein the first PDCP control PDU includes at least one of the following information:

    First information, the first information is used to indicate the GOP identifier associated with the feedback information;

    At least one set of information, each set of information corresponding to a PDU set in the GOP, each set of information includes fourth information, fifth information and a second bitmap, the fourth information is used to indicate the PDU set identification, the third Five information is used to indicate the number of PDUs contained in the PDU set. Each bit in the second bitmap corresponds to one PDU. The value of the bit is used to indicate the ACK/NACK of the PDU corresponding to the bit. information.
39. The method of claim 36, wherein the first PDCP control PDU includes at least one of the following information:

    First information, the first information is used to indicate the GOP identification associated with the feedback information;

    Second information, the second information is used to indicate the number of PDU sets contained in the GOP;

    The third bitmap, each bit in the third bitmap corresponds to a PDU set, and the value of the bit is used to indicate the ACK/NACK information of the PDU set corresponding to the bit.
40. The method of claim 36, wherein the first PDCP control PDU includes at least one of the following information:

    First information, the first information is used to indicate the GOP identification associated with the feedback information;

    Sixth information, the sixth information is ACK/NACK information corresponding to the GOP.
41. The method according to any one of claims 37 to 40, wherein the first PDCP control PDU further includes at least one of the following information:

    Seventh information, the seventh information is used to indicate whether the first PDCP control PDU is a data PDU or a control PDU;

    Eighth information, the eighth information is used to indicate the PDU type to which the first PDCP control PDU belongs.
42. The method according to claim 41, wherein the PDU type is one of the following:

    A first PDU type, the first PDU type is used for PDU level ACK/NACK feedback;

    A second PDU type, the second PDU type is used for ACK/NACK feedback at the PDU set level;

    A third PDU type, the third PDU type is used for ACK/NACK feedback at the GOP level.
43. The method of claim 36, wherein the first PDCP control PDU includes at least one of the following information:

    First information, the first information is used to indicate the GOP identifier associated with the feedback information;

    Second information, the second information is used to indicate the number of PDU sets contained in the GOP;

    Third information, the third information is used to indicate the number of PDUs contained in each PDU set;

    A first bitmap, each bit in the first bitmap corresponds to a PDU, and the value of the bit is used to indicate the ACK/NACK information of the PDU corresponding to the bit;

    A third bitmap, each bit in the third bitmap corresponds to a PDU set, and the value of the bit is used to indicate the ACK/NACK information of the PDU set corresponding to the bit;

    Sixth information, the sixth information is ACK/NACK information corresponding to the GOP.
44. The method according to claim 43, wherein the first PDCP control PDU further includes at least one of the following information:

    Seventh information, the seventh information is used to indicate whether the first PDCP control PDU is a data PDU or a control PDU;

    Eighth information, the eighth information is used to indicate the PDU type to which the first PDCP control PDU belongs;

    Ninth information, the ninth information is used to indicate the feedback type corresponding to the first PDCP control PDU.
45. The method according to claim 44, wherein when the feedback type is PDU-level ACK/NACK feedback, the first PDCP control PDU includes the first information, the second information, the third at least one of three pieces of information and the first bitmap.
46. The method according to claim 44, wherein when the feedback type is PDU set level ACK/NACK feedback, the first PDCP control PDU includes the first information, the second information and the At least one of the second bitmaps.
47. The method according to claim 44, wherein when the feedback type is GOP-level ACK/NACK feedback, the first PDCP control PDU includes at least one of the first information and the sixth information. one.
48. The method according to claim 37 or 43, wherein the corresponding relationship between the bits in the first bitmap and the PDU is:

    According to the order of PDU set identifiers from small to large, and then according to the order of PDU identifiers in each PDU set from small to large, they correspond to the first bitmap in order from low to high.
49. The method according to claim 38, wherein the corresponding relationship between the bits in the second bitmap and the PDU is:

    According to the order of PDU identifiers from small to large, they correspond to the second bitmap in order from low to high.
50. The method according to claim 39 or 43, wherein the corresponding relationship between the bits in the third bitmap and the PDU set is:

    According to the order of PDU set identifiers from small to large, they correspond to the third bitmap in order from low to high.
51. The method according to any one of claims 39, 43, and 46, wherein,

    If at least one PDU in a PDU set is not received correctly, the ACK/NACK information corresponding to the PDU set is NACK;

    If all PDUs in a PDU set are received correctly, the ACK/NACK information corresponding to the PDU set is ACK.
52. The method according to any one of claims 40, 43, and 47, wherein,

    If at least one PDU in the GOP is not received correctly, the ACK/NACK information corresponding to the GOP is NACK; if all PDUs in the GOP are received correctly, the ACK/NACK information corresponding to the GOP is ACK; or,

    If the specific PDU Set or specific frame in the GOP is not received correctly, the ACK/NACK information corresponding to the GOP is NACK; if the specific PDU Set or specific frame in the GOP is received correctly, the ACK/NACK information corresponding to the GOP for ACK.
53. The method according to any one of claims 36 to 52, wherein the method further comprises:

    The second node sends a second PDCP control PDU to the first node, and the second PDCP control PDU is used to request feedback information, wherein the feedback type of the feedback information is PDU-level ACK/NACK feedback or PDU Set-level ACK/NACK feedback or GOP-level ACK/NACK feedback.
54. The method of claim 53, wherein the second PDCP control PDU includes at least one of the following information:

    First information, the first information is used to indicate the GOP identifier associated with the feedback information;

    Tenth information, the tenth information is used to indicate the feedback type requested by the second PDCP control PDU.
55. The method according to claim 54, wherein the second PDCP control PDU is also used to indicate a PDU set that requires feedback; the second PDCP control PDU further includes at least one of the following information:

    PDU set identification list;

    The number of PDU set identifiers;

    The starting value of the PDU set identifier;

    The end value of the PDU set identifier.
56. The method according to claim 54 or 55, wherein the second PDCP control PDU further includes at least one of the following information:

    Eleventh information, the eleventh information is used to indicate whether the second PDCP control PDU is a data PDU or a control PDU;

    Twelfth information, the twelfth information is used to indicate the PDU type to which the second PDCP control PDU belongs.
57. A data transmission device, the device has a first protocol layer and a second protocol layer;

    The first protocol layer is used to receive one or more PDU sets sent by the second protocol layer;

    The second protocol layer is used to send one or more PDU sets to the first protocol layer;

    The header corresponding to each PDU in the PDU set carries the first information and/or the first flag is transmitted after the PDU set, where,

    The first information includes at least one of the following: GOP identifier, PDU set identifier, PDU identifier, frame type, last frame indication in the GOP, number of frames included in the GOP, GOP list associated with the GOP, Qos flow identifier;

    The first flag includes at least one of the following: GOP identifier, PDU set identifier, frame type, Qos flow identifier, last frame indication in the GOP, number of frames included in the GOP, GOP list associated with the GOP, and Qos flow identifier.
58. A data transmission device, applied to the first node, the device includes:

    A sending unit configured to send a first PDCP control PDU to the second node, where the first PDCP control PDU carries feedback information, where the feedback information is used to indicate at least one of the following:

    ACK/NACK information for one or more PDUs;

    ACK/NACK information of one or more PDU sets;

    ACK/NACK information for one or more GOPs.
59. A data transmission device, applied to the second node, the device includes:

    A receiving unit configured to receive a first PDCP control PDU sent by the first node, where the first PDCP control PDU carries feedback information, wherein the feedback information is used to indicate at least one of the following:

    ACK/NACK information for one or more PDUs;

    ACK/NACK information of one or more PDU sets;

    ACK/NACK information for one or more GOPs.
60. 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 10 The method, or the method described in any one of claims 11 to 35, or the method described in any one of claims 36 to 56.
61. 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 10, or claims 11 to 35 The method according to any one of claims 36 to 56.
62. 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 10, or the method according to any one of claims 11 to 35 , or the method of any one of claims 36 to 56.
63. 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 10, or the method as claimed in any one of claims 11 to 35, or the method as claimed in any one of claims 11 to 35, or The method of any one of claims 36 to 56.
64. A computer program that causes a computer to perform the method according to any one of claims 1 to 10, or the method according to any one of claims 11 to 35, or any one of claims 36 to 56. method described in one item.

Images