WO2024007875A1 - Data volume indication method, data delivery method, and apparatus - Google Patents

Abstract

A data volume indication method, a data delivery method, and an apparatus, which relate to the technical field of communications and can alleviate the technical problem of how to indicate a data volume to a MAC entity when a PDCP entity of a terminal device is associated with a plurality of RLC entities. The method may comprise: a PDCP entity of a terminal device indicating a first data volume to a MAC entity of the terminal device, and indicating a second data volume to the MAC entity, wherein the PDCP entity is associated with a first RLC entity of the terminal device and a second RLC entity of the terminal device, the first data volume comprises the data volume of a first data set associated with the first RLC entity, and the second data volume comprises the data volume of a second data set associated with the second RLC entity.

Description

Data volume indication method, data submission method and device

This application claims priority to the Chinese patent application submitted to the State Intellectual Property Office on July 6, 2022, with application number 202210790760.1 and the application title "Data volume indication method, data submission method and device", the entire content of which is incorporated by reference. in this application.

Technical field

The present application relates to the field of communication technology, and in particular, to a data amount indication method, data submission method and device.

Background technique

In a communication system, when a terminal device sends data to a network device, the packet data convergence protocol (PDCP) entity of the terminal device can submit the data to the radio link control (radio link control, RLC) entity and send the PDCP The amount of data is indicated to the medium access control (MAC) entity. The MAC entity can send a buffer status report (BSR) to the network device based on the PDCP data volume and RLC data volume to indicate to the network device the amount of data to be sent by the terminal device. The network device can configure corresponding uplink resources for the terminal device based on the received BSR. The terminal device sends data to the network device according to the uplink resources configured by the network device.

Among them, the PDCP entity of the terminal device can be associated with one or more RLC entities. When the PDCP entity is associated with multiple RLC entities, how the PDCP entity indicates the amount of data to the MAC entity has become an urgent technical issue to be solved.

Contents of the invention

Embodiments of the present application provide a data volume indication method, data submission method and device, which can improve the technical problem of how to indicate the data volume to the MAC entity when the PDCP entity of the terminal device is associated with multiple RLC entities.

In a first aspect, embodiments of the present application provide a data volume indication method. The method may include: the packet data convergence protocol PDCP entity of the terminal device indicates the first data volume to the media access control MAC entity of the terminal device, and the MAC entity Indicates the second data amount; wherein, the PDCP entity is associated with the first radio link control RLC entity of the terminal device and the second RLC entity of the terminal device, the first data amount includes the data amount of the first data set, and the first data set is associated with The first RLC entity is associated; the second data amount includes the data amount of the second data set, and the second data set is associated with the second RLC entity.

Based on the first aspect, the way in which the PDCP entity indicates the amount of data to the MAC entity is modified. The PDCP entity may indicate the first amount of data to the MAC entity associated with the first RLC entity and the second amount of data to the MAC entity associated with the second RLC entity. The amount of data. When the PDCP entity indicates the data amount to the MAC entity, the data can be distinguished (or described as differentiating RLC entities), and different data (or described as different RLC entities) can be indicated by different data amounts. The MAC entity can determine the BSR based on the amount of data indicated by the PDCP entity, which is conducive to accurate reporting of the BSR and thus saves resources.

In a possible design, the first data amount also includes the data amount of the control PDU set; and/or the second data amount also includes the data amount of the control PDU set.

Based on this possible design, the PDCP entity can determine through which RLC entity to submit the control PDU set based on preconfiguration or predefinition. If it is determined that the control PDU set is delivered through the first RLC entity, the first data amount also includes the data amount of the control PDU set. If it is determined that the control PDU set is delivered through the second RLC entity, the second data amount also includes the data amount of the control PDU set. If it is determined that the control PDU set is delivered through the first RLC entity and/or the second RLC entity, both the first data amount and the second data amount include the data amount of the control PDU set.

In a possible design, the first data set includes part or all of the second data of one or more data groups; the second data set includes part or all of the first data of one or more data groups; wherein the data group includes first data, and one or more second data.

In the second aspect, embodiments of the present application provide a communication device, which can be applied to the PDCP entity of the terminal equipment in the above-mentioned first aspect or the possible design of the first aspect, so as to realize the functions performed by the PDCP entity of the above-mentioned terminal equipment. , the communication device can be a PDCP entity of the terminal device, or a chip or a system-on-chip used to implement the PDCP entity function of the terminal device. The communication device can execute corresponding software through hardware to realize what is executed by the PDCP entity of the terminal device. Function. The hardware or software includes one or more modules corresponding to the above functions. For example, transceiver module and processing module. The processing module is used to obtain the first data amount, and to obtain the second data amount; the transceiver module is used to indicate the first data amount to the MAC entity of the terminal device, and to indicate the second data amount to the MAC entity; wherein, the PDCP entity and The first radio link control RLC entity of the terminal device is associated with the second RLC entity of the terminal device, the first data amount includes the data amount of the first data set, the first data set is associated with the first RLC entity; the second data amount includes The data amount of the second data set, the second data set is associated with the second RLC entity.

In a possible design, the first data amount also includes the data amount of the control PDU set; and/or the second data amount also includes the data amount of the control PDU set.

In a possible design, the first data set includes part or all of the second data of one or more data groups; the second data set includes part or all of the first data of one or more data groups; wherein the data group includes first data, and one or more second data.

It should be noted that the specific implementation of the communication device in the second aspect may refer to the behavioral function of the PDCP entity of the terminal device in the data amount indication method provided by the first aspect or any possible design of the first aspect.

In the third aspect, embodiments of the present application provide a communication device, which may be a PDCP entity of a terminal device or a chip or a system-on-chip used to implement the PDCP entity function of a terminal device. The communication device can implement the functions performed by the PDCP entity of the terminal device in the above aspects or in each possible design, and the functions can be implemented by hardware. In a possible design, the communication device may include: a transceiver and a processor. The transceiver and the processor may be used to support the communication device to implement the functions involved in the above-mentioned first aspect or any possible design of the first aspect. For example: the processor can be used to obtain the first amount of data, and to obtain the second amount of data; the transceiver can be used to indicate the first amount of data to the MAC entity of the terminal device, and to indicate the second amount of data to the MAC entity; wherein, PDCP The entity is associated with a first radio link control RLC entity of the terminal device and a second RLC entity of the terminal device, the first data amount includes the data amount of the first data set, the first data set is associated with the first RLC entity; the second data The amount includes the amount of data of the second data set associated with the second RLC entity. In yet another possible design, the communication device may further include a memory for storing computer execution instructions and data of the communication device. When the communication device is running, the transceiver and the processor execute the computer execution instructions stored in the memory, so that the communication device executes the amount of data as described in the above-mentioned first aspect or any possible design of the first aspect. Instruction method.

The specific implementation of the communication device in the third aspect may refer to the behavioral function of the PDCP entity of the terminal device in the data amount indication method provided by the first aspect or any possible design of the first aspect.

In the fourth aspect, embodiments of the present application provide a data volume indication method. The method may include: the packet data convergence protocol PDCP entity of the terminal device obtains the third data volume, and indicates the third data volume to the media access control MAC entity of the terminal device. The amount of data; wherein, the PDCP entity is associated with the first radio link control RLC entity of the terminal device and the second RLC entity of the terminal device; the third data amount includes the data amount of the first data set and the data amount of the second data set; The first data set is associated with the first RLC entity; the second data set is associated with the second RLC entity.

Based on the fourth aspect, the way in which the PDCP entity indicates the data amount to the MAC entity is modified. The PDCP entity can indicate a total data amount, such as a third data amount, to the MAC entity. When the PDCP entity indicates the data amount to the MAC entity, the data may not be distinguished (or described as not distinguishing the RLC entity), which is conducive to accurate indication of the data amount. The MAC entity can determine the BSR based on the amount of data indicated by the PDCP entity, which is conducive to accurate reporting of the BSR and thus saves resources.

In a possible design, the third data amount also includes the data amount of the control PDU set.

Based on this possible design, since the PDCP entity does not distinguish between RLC entities when indicating the data amount to the MAC entity, no matter which RLC entity submits the control PDU set, the third data amount includes the data amount of the control PDU set.

In a possible design, the first data set includes part or all of the second data of one or more data groups; the second data set includes part or all of the first data of one or more data groups; wherein the data group includes first data, and one or more second data.

In the fifth aspect, embodiments of the present application provide a communication device, which can be applied to the PDCP entity of the terminal equipment in the above-mentioned fourth aspect or the possible design of the fourth aspect, so as to realize the functions performed by the PDCP entity of the above-mentioned terminal equipment. , the communication device can be a PDCP entity of the terminal device, or a chip or a system-on-chip used to implement the PDCP entity function of the terminal device. The communication device can execute corresponding software through hardware to realize what is executed by the PDCP entity of the terminal device. Function. The hardware or software includes one or more modules corresponding to the above functions. For example, transceiver module and processing module. The processing module is used to obtain the third data amount; the transceiver module is used to indicate the third data amount to the MAC entity of the terminal device; wherein, the PDCP entity and the first wireless link control RLC entity of the terminal device and the second wireless link control RLC entity of the terminal device The RLC entity is associated; the third data amount includes the data amount of the first data set and the data amount of the second data set; the first data set is associated with the first RLC entity; the second data set is associated with the second RLC entity.

In a possible design, the third data amount also includes the data amount of the control PDU set.

In a possible design, the first data set includes part or all of the second data of one or more data groups; the second data set includes part or all of the first data of one or more data groups; wherein the data group includes first data, and one or more second data.

It should be noted that the specific implementation of the communication device in the fifth aspect may refer to the behavioral function of the PDCP entity of the terminal device in the data amount indication method provided by the fourth aspect or any possible design of the fourth aspect.

In the sixth aspect, embodiments of the present application provide a communication device, which may be a PDCP entity of a terminal device or used to implement The chip or system-on-chip of the PDCP entity function of the terminal device. The communication device can implement the functions performed by the PDCP entity of the terminal device in the above aspects or in each possible design, and the functions can be implemented by hardware. In a possible design, the communication device may include: a transceiver and a processor. The transceiver and the processor may be used to support the communication device to implement the functions involved in the above-mentioned fourth aspect or any possible design of the fourth aspect. For example: the processor can be used to obtain the third data amount; the transceiver can be used to indicate the third data amount to the MAC entity of the terminal device; wherein, the PDCP entity and the first wireless link control RLC entity of the terminal device and the terminal device The second RLC entity is associated; the third data amount includes the data amount of the first data set and the data amount of the second data set; the first data set is associated with the first RLC entity; the second data set is associated with the second RLC entity. In yet another possible design, the communication device may further include a memory, which is used to store computer execution instructions and data of the communication device. When the communication device is running, the transceiver and the processor execute the computer execution instructions stored in the memory, so that the communication device executes the amount of data as described in the above-mentioned fourth aspect or any possible design of the fourth aspect. Instruction method.

The specific implementation of the communication device in the sixth aspect may refer to the behavioral function of the PDCP entity of the terminal device in the data amount indication method provided by the fourth aspect or any possible design of the fourth aspect.

In the seventh aspect, embodiments of the present application provide a data volume indication method. The method may include: the packet data convergence protocol PDCP entity of the terminal device indicating the first data volume to the media access control MAC entity of the terminal device, and indicating the first data volume to the MAC entity. Indicates a third data amount; wherein the PDCP entity is associated with a first radio link control RLC entity of the terminal device and a second RLC entity of the terminal device; the first data amount includes the data amount of the first data set, and the first data set is associated with The first RLC entity is associated; the third data amount includes the data amount of the first data set and the data amount of the second data set, and the second data set is associated with the second RLC entity.

Based on the seventh aspect, the way in which the PDCP entity indicates the amount of data to the MAC entity is modified. If the PDCP entity submits the first data set to the first RLC entity, the PDCP entity may indicate the first data to the MAC entity associated with the first RLC entity. quantity. If the PDCP entity submits the second data set to the second RLC entity, the PDCP entity may also submit the first data set to the second RLC entity. The PDCP entity may indicate a total data amount to the MAC entity associated with the second RLC entity, such as Three data volumes. The PDCP entity can distinguish the RLC entities when indicating the data amount to the MAC entity, and different RLC entities are indicated by different data amounts. The MAC entity can determine the BSR based on the amount of data indicated by the PDCP entity, which is conducive to accurate reporting of the BSR and thus saves resources.

In a possible design, the first data amount also includes the data amount of the control PDU set; and/or the third data amount also includes the data amount of the control PDU set.

Based on this possible design, the PDCP entity can determine which RLC entity specifically delivers the control PDU set through preconfiguration or predefinition. If it is determined that the control PDU set is delivered through the first RLC entity, the first data amount also includes the data amount of the control PDU set. If it is determined that the control PDU set is delivered through the second RLC entity, the third data amount also includes the data amount of the control PDU set. If it is determined that the control PDU set is delivered through the first RLC entity and/or the second RLC entity, both the first data amount and the third data amount include the data amount of the control PDU set.

In a possible design, the first data set includes part or all of the second data of one or more data groups; the second data set includes part or all of the first data of one or more data groups; wherein the data group includes first data, and one or more second data.

In an eighth aspect, embodiments of the present application provide a communication device, which can be applied to the PDCP entity of the terminal device in the seventh aspect or the possible design of the seventh aspect, so as to realize the functions performed by the PDCP entity of the terminal device. , the communication device can be a PDCP entity of the terminal device, or a chip or a system-on-chip used to implement the PDCP entity function of the terminal device. The communication device can execute corresponding software through hardware to realize what is executed by the PDCP entity of the terminal device. Function. The hardware or software includes one or more modules corresponding to the above functions. For example, transceiver module and processing module. The processing module is used to obtain the first data amount, and obtain the third data amount; the transceiver module is used to indicate the first data amount to the MAC entity of the terminal device, and to indicate the third data amount to the MAC entity; wherein, the PDCP entity and The first radio link control RLC entity of the terminal device is associated with the second RLC entity of the terminal device; the first data amount includes the data amount of the first data set, and the first data set is associated with the first RLC entity; the third data amount includes The data amount of the first data set and the data amount of the second data set, and the second data set is associated with the second RLC entity.

In a possible design, the first data amount also includes the data amount of the control PDU set; and/or the third data amount also includes the data amount of the control PDU set.

In a possible design, the first data set includes part or all of the second data of one or more data groups; the second data set includes part or all of the first data of one or more data groups; wherein the data group includes first data, and one or more second data.

It should be noted that the specific implementation of the communication device in the eighth aspect may refer to the behavior function of the PDCP entity of the terminal device in the data amount indication method provided by the seventh aspect or any possible design of the seventh aspect.

In a ninth aspect, embodiments of the present application provide a communication device, which may be a PDCP entity of a terminal device or a chip or a system-on-chip used to implement the PDCP entity function of a terminal device. The communication device can implement the functions performed by the PDCP entity of the terminal device in the above aspects or in each possible design, and the functions can be implemented by hardware. In a possible design, the communication device may include: a transceiver and a processor. The transceiver and processor may be used to support the communication device to implement the functions involved in the seventh aspect or any possible design of the seventh aspect. For example: the processor can be used to obtain the first data amount, and obtain the third data amount; the transceiver can be used to indicate the first data amount to the MAC entity of the terminal device, and indicate the third data amount to the MAC entity; wherein, PDCP The entity is associated with a first radio link control RLC entity of the terminal device and a second RLC entity of the terminal device; the first data amount includes the data amount of the first data set, and the first data set is associated with the first RLC entity; the third data The quantity includes the data quantity of the first data set and the data quantity of the second data set, and the second data set is associated with the second RLC entity. In yet another possible design, the communication device may further include a memory for storing computer execution instructions and data of the communication device. When the communication device is running, the transceiver and the processor execute the computer execution instructions stored in the memory, so that the communication device executes the amount of data as described in the seventh aspect or any possible design of the seventh aspect. Instruction method.

The specific implementation of the communication device in the ninth aspect may refer to the behavioral function of the PDCP entity of the terminal device in the data amount indication method provided by the seventh aspect or any possible design of the seventh aspect.

In the tenth aspect, embodiments of the present application provide a data submission method. The method may include: the PDCP entity of the terminal device obtains the first data of the second data group; if the second data submission of the first data group is completed or the submission is terminated, The PDCP entity submits the first data of the second data group to the second RLC entity of the terminal device; wherein, the PDCP entity is associated with the first RLC entity and the second RLC entity of the terminal device; the first data group includes the first data, and a or a plurality of second data; the second data group includes the first data and one or more second data; the first data is associated with the second RLC entity; the second data is associated with the first RLC entity.

Based on the tenth aspect, the limiting conditions for the PDCP entity to submit data to the RLC entity are added. Taking the priority of the first data as higher than the priority of the second data as an example, if the PDCP entity determines that all the second data of the first data group is submitted Upon completion or delivery termination, the PDCP entity may submit the first data of the second data group to the second RLC entity to prevent the PDCP entity from preferentially submitting the first data of the second data group to the second RLC entity, resulting in the first data of the first data group being 2. Data cannot be transferred.

In a possible design, the PDCP entity sends a first request to the first RLC entity and receives a first response from the first RLC entity; wherein the first request is used to request whether the submission of the second data of the first data group is completed or Submission termination information; the first response is used to indicate whether the submission of the second data of the first data group is completed or the submission is terminated.

In a possible design, the PDCP entity receives first indication information from the first RLC entity; wherein the first indication information is used to indicate completion or termination of the second data submission of the first data group.

Based on the above two possible designs, multiple feasible solutions are provided for the PDCP entity to determine whether the submission of the second data of the first data group is completed or the submission is terminated.

In a possible design, the completion or termination of the submission of the second data of the first data group includes: the second data of the first data group is submitted to the MAC entity by the first RLC entity; or, the second data of the first data group is submitted to the MAC entity. The data is submitted at the PDCP entity and/or the first RLC entity.

In an eleventh aspect, embodiments of the present application provide a communication device. The communication device can be applied to the PDCP entity of the terminal device in the tenth aspect or the possible design of the tenth aspect, so as to implement the PDCP entity of the terminal device. Function, the communication device can be a PDCP entity of the terminal device, or a chip or system-on-chip used to implement the PDCP entity function of the terminal device. The communication device can execute the corresponding software through hardware to implement the execution of the PDCP entity of the terminal device. function. The hardware or software includes one or more modules corresponding to the above functions. For example, transceiver module and processing module. The processing module is used to obtain the first data of the second data group; the transceiver module is used to submit the second data of the second data group to the second RLC entity of the terminal device if the submission of the second data of the first data group is completed or the submission is terminated. One data; wherein, the PDCP entity is associated with the first RLC entity and the second RLC entity of the terminal device; the first data group includes first data, and one or more second data; the second data group includes the first data, and One or more second data; the first data is associated with the second RLC entity; the second data is associated with the first RLC entity.

In a possible design, the transceiver module is also used to send a first request to the first RLC entity and receive a first response from the first RLC entity; wherein the first request is used to request the second data of the first data group. Information about whether the submission is completed or the submission is terminated; the first response is used to indicate whether the second data of the first data group is submitted is completed or the submission is terminated.

In a possible design, the transceiver module is further configured to receive first indication information from the first RLC entity; wherein the first indication information is used to indicate completion or termination of the second data submission of the first data group.

In a possible design, the submission of the second data of the first data group is completed or the submission is terminated, including: the second data of the first data group is An RLC entity is submitted to the MAC entity; alternatively, the second data of the first data group is terminated by the PDCP entity and/or the first RLC entity.

It should be noted that the specific implementation of the communication device in the eleventh aspect may refer to the behavioral functions of the PDCP entity of the terminal device in the data submission method provided by the tenth aspect or any possible design of the tenth aspect.

In a twelfth aspect, embodiments of the present application provide a communication device, which may be a PDCP entity of a terminal device or a chip or a system-on-chip used to implement the PDCP entity function of a terminal device. The communication device can implement the functions performed by the PDCP entity of the terminal device in the above aspects or in each possible design, and the functions can be implemented by hardware. In a possible design, the communication device may include: a transceiver and a processor. The transceiver and the processor may be used to support the communication device to implement the functions involved in the tenth aspect or any possible design of the tenth aspect. For example: the processor may be used to obtain the first data of the second data group; the transceiver may be used to submit the second data group to the second RLC entity of the terminal device if the second data submission of the first data group is completed or the delivery is terminated. The first data; wherein, the PDCP entity is associated with the first RLC entity and the second RLC entity of the terminal device; the first data group includes the first data, and one or more second data; the second data group includes the first data , and one or more second data; the first data is associated with the second RLC entity; the second data is associated with the first RLC entity. In yet another possible design, the communication device may further include a memory for storing computer execution instructions and data of the communication device. When the communication device is running, the transceiver and the processor execute the computer execution instructions stored in the memory, so that the communication device performs data submission as described in the tenth aspect or any possible design of the tenth aspect. method.

The specific implementation of the communication device in the twelfth aspect may refer to the behavioral function of the PDCP entity of the terminal device in the data submission method provided by the tenth aspect or any possible design of the tenth aspect.

In a thirteenth aspect, embodiments of the present application provide a data submission method. The method may include: the PDCP entity of the terminal device obtains the second data of the first data group; if the first condition is met, the PDCP entity submits the data to the second data of the terminal device. The RLC entity submits the second data of the first data group; wherein the PDCP entity is associated with the first RLC entity and the second RLC entity of the terminal device; the first condition includes the PDCP entity obtaining the first data of the second data group or the PDCP entity Determine to submit the first data of the second data group to the second RLC entity; the first data group includes the first data and one or more second data; the second data group includes the first data and one or more second data Data; the first data is associated with the second RLC entity; the second data is associated with the first RLC entity.

Based on the thirteenth aspect, the limiting conditions for the PDCP entity to submit data to the RLC entity are added. Taking the priority of the first data as higher than the priority of the second data as an example, if the second data of the first data group has not been submitted yet or When the submission is terminated, the PDCP entity obtains the first data of the second data group or determines to submit the first data of the second data group to the second RLC entity. The PDCP entity can submit the second data of the first data group to the second RLC entity. , if all the second data of the first data group is submitted or the delivery is terminated, the PDCP entity may submit the first data of the second data group to the second RLC entity. This prevents the PDCP entity from preferentially submitting the first data of the second data group to the second RLC entity, causing the second data of the first data group to fail to be transmitted.

In a possible design, if the submission of the second data of the first data group is completed or the delivery is terminated, the PDCP entity submits the first data of the second data group to the second RLC entity.

Based on this possible design, if the delivery of the second data of the first data group is completed or the delivery is terminated, the PDCP entity can submit the first data of the second data group to the second RLC entity to ensure normal delivery of data.

In a possible design, the completion or termination of the submission of the second data of the first data group includes: the second data of the first data group is submitted to the MAC entity; or the second data of the first data group is received by the PDCP entity. and/or the second RLC entity submits termination.

In a possible design, the PDCP entity submits to the second RLC entity the data in the second data of the first data group that has not been submitted by the first RLC entity.

In a possible design, the data in the second data of the first data group that is not submitted by the first RLC entity includes: the data in the second data of the first data group that is not submitted by the PDCP entity to the first RLC entity; and /or, the second data in the first data group is data that has been submitted to the first RLC entity by the PDCP entity but has not been submitted by the first RLC entity.

Based on the above two possible designs, the PDCP entity can submit the data in the second data of the first data group that has not been submitted by the first RLC entity to the second RLC entity to avoid repeated submission of data and reduce overhead.

In a possible design, if the first condition is not met, the PDCP entity submits the second data of the first data group to the first RLC entity.

Based on this possible design, if the first condition is not met, the PDCP entity can submit the second data of the first data group to the first RLC entity to ensure normal delivery of data.

In a possible design, before the PDCP entity submits the second data of the first data group to the second RLC entity, the method further includes one or more of the following: the PDCP entity sends the second indication information to the first RLC entity; wherein , the second indication information is used to indicate the second data group's One data arrives; and/or, the PDCP entity sends third indication information to the first RLC entity; wherein the third indication information is used to instruct the first RLC entity to feed back a delivery status report of the second data of the first data group; and/or Or, the PDCP entity sends fourth indication information to the first RLC entity; wherein the fourth indication information is used to instruct the first RLC entity to delete the second data of the first data group.

Based on this possible design, the PDCP entity may send the above one or more indication information to the first RLC entity, so that the first RLC entity stops data submission.

In a fourteenth aspect, embodiments of the present application provide a communication device. The communication device can be applied to the PDCP entity of the terminal equipment in the above-mentioned thirteenth aspect or the possible design of the thirteenth aspect, so as to realize the PDCP entity of the above-mentioned terminal equipment. The communication device can be the PDCP entity of the terminal device, or a chip or system on a chip used to implement the PDCP entity function of the terminal device. The communication device can execute the corresponding software through hardware to implement the PDCP entity of the terminal device. function performed. The hardware or software includes one or more modules corresponding to the above functions. For example, transceiver module and processing module. The processing module is used to obtain the second data of the first data group; the transceiver module is used to, if the first condition is met, the PDCP entity submits the second data of the first data group to the second RLC entity of the terminal device; wherein, the PDCP entity Associated with the first RLC entity and the second RLC entity of the terminal device; the first condition includes the PDCP entity acquiring the first data of the second data group or the PDCP entity determining to submit the first data of the second data group to the second RLC entity; The first data group includes first data and one or more second data; the second data group includes first data and one or more second data; the first data is associated with the second RLC entity; the second data is associated with The first RLC entity is associated.

In a possible design, the transceiver module is also configured to submit the first data of the second data group to the second RLC entity if the submission of the second data of the first data group is completed or the delivery is terminated.

In a possible design, the completion or termination of the submission of the second data of the first data group includes: the second data of the first data group is submitted to the MAC entity; or the second data of the first data group is received by the PDCP entity. and/or the second RLC entity submits termination.

In a possible design, the transceiver module is also configured to submit to the second RLC entity the data in the second data of the first data group that has not been submitted by the first RLC entity.

In a possible design, the data in the second data of the first data group that is not submitted by the first RLC entity includes: the data in the second data of the first data group that is not submitted by the PDCP entity to the first RLC entity; and /or, the second data in the first data group is data that has been submitted to the first RLC entity by the PDCP entity but has not been submitted by the first RLC entity.

In a possible design, the transceiver module is also used to submit the second data of the first data group to the first RLC entity if the first condition is not met.

In a possible design, before submitting the second data of the first data group to the second RLC entity, the transceiver module further includes one or more of the following: a transceiver module, which is also used to send the second indication to the first RLC entity. information; wherein the second indication information is used to indicate the arrival of the first data of the second data group; and/or the transceiver module is also used to send third indication information to the first RLC entity; wherein the third indication information is used to Instruct the first RLC entity to feed back a delivery status report of the second data of the first data group; and/or the transceiver module is also configured to send fourth indication information to the first RLC entity; wherein the fourth indication information is used to indicate the An RLC entity deletes the second data of the first data group.

It should be noted that the specific implementation of the communication device in the fourteenth aspect may refer to the behavioral functions of the PDCP entity of the terminal device in the data submission method provided by the thirteenth aspect or any possible design of the thirteenth aspect.

In a fifteenth aspect, embodiments of the present application provide a communication device, which may be a PDCP entity of a terminal device or a chip or a system-on-chip used to implement the PDCP entity function of a terminal device. The communication device can implement the functions performed by the PDCP entity of the terminal device in the above aspects or in each possible design, and the functions can be implemented by hardware. In a possible design, the communication device may include: a transceiver and a processor. The transceiver and processor may be used to support the communication device to implement the functions involved in the above-mentioned thirteenth aspect or any possible design of the thirteenth aspect. For example: the processor can be used to obtain the second data of the first data group; the transceiver can be used to, if the first condition is met, the PDCP entity submits the second data of the first data group to the second RLC entity of the terminal device; wherein, The PDCP entity is associated with the first RLC entity and the second RLC entity of the terminal device; the first condition includes that the PDCP entity obtains the first data of the second data group or the PDCP entity determines to submit the first data of the second data group to the second RLC entity. data; the first data group includes first data and one or more second data; the second data group includes first data and one or more second data; the first data is associated with the second RLC entity; the second The data is associated with the first RLC entity. In yet another possible design, the communication device may further include a memory for storing computer execution instructions and data of the communication device. When the communication device is running, the transceiver and the processor execute the computer execution instructions stored in the memory, so that the communication device executes the above-mentioned thirteenth aspect or any of the possible designs of the thirteenth aspect. Data submission method.

Among them, the specific implementation method of the communication device in the fifteenth aspect may refer to the thirteenth aspect or any possible design proposal of the thirteenth aspect. The behavioral functions of the PDCP entity of the terminal device in the data delivery method provided.

In a sixteenth aspect, embodiments of the present application provide a data submission method. The method may include: the Service Data Adaptation Protocol SDAP entity of the terminal device obtains the first data of the second data group; if the second data of the first data group When the submission is completed or the submission is terminated, the SDAP entity submits the first data of the second data group to the second PDCP entity; wherein, the SDAP entity is associated with the first Packet Data Convergence Protocol PDCP entity of the terminal device and the second PDCP entity of the terminal device; A data group includes first data and one or more second data; the second data group includes first data and one or more second data; the first data is associated with the second PDCP entity, and the second data is associated with the second PDCP entity. A PDCP entity association.

Based on the sixteenth aspect, the limiting conditions for the SDAP entity to submit data to the PDCP entity are added. Taking the priority of the first data as higher than the priority of the second data as an example, if the SDAP entity determines that all the second data of the first data group When the submission is completed or the submission is terminated, the SDAP entity can submit the first data of the second data group to the second PDCP entity to prevent the SDAP entity from preferentially submitting the first data of the second data group to the second PDCP entity, resulting in the loss of the first data group. The second data cannot be transferred.

In a possible design, the SDAP entity sends a second request to the first PDCP entity and receives a second response from the first PDCP entity; where the second request is used to request whether the submission of the second data of the first data group is completed or Submission termination information; the second response is used to indicate whether the submission of the second data of the first data group is completed or the submission is terminated.

In a possible design, the SDAP entity sends a third request to the first radio link control RLC entity of the terminal device and receives a third response from the first RLC entity; wherein the third request is used to request the first data group Information about whether the submission of the second data is completed or terminated; the third response is used to indicate whether the submission of the second data of the first data group is completed or terminated.

In a possible design, the SDAP entity receives fifth indication information from the first PDCP entity or the first RLC entity of the terminal device; wherein the fifth indication information is used to indicate the completion or delivery of the second data submission of the first data group. termination.

Based on the above three possible designs, multiple feasible solutions are provided for the SDAP entity to determine whether the submission of the second data of the first data group is completed or the submission is terminated.

In a possible design, the completion or termination of the submission of the second data of the first data group includes: the second data of the first data group is submitted to the MAC entity of the terminal device by the first RLC entity of the terminal device; or, The second data of a data group is submitted and terminated by one or more of the following entities: the SDAP entity, the first PDCP entity, and the first RLC entity of the terminal device.

In a seventeenth aspect, embodiments of the present application provide a communication device. The communication device can be applied to the SDAP entity of the terminal device in the sixteenth aspect or the possible design of the sixteenth aspect, so as to realize the SDAP entity of the terminal device. The communication device can be the SDAP entity of the terminal device, or a chip or system-on-chip used to implement the SDAP entity function of the terminal device. The communication device can execute the corresponding software through hardware to implement the SDAP entity of the terminal device. function performed. The hardware or software includes one or more modules corresponding to the above functions. For example, transceiver module and processing module. The processing module is used to obtain the first data of the second data group; the transceiver module is used to submit the first data of the second data group to the second PDCP entity if the second data submission of the first data group is completed or the submission is terminated; Wherein, the SDAP entity is associated with the first Packet Data Convergence Protocol PDCP entity of the terminal device and the second PDCP entity of the terminal device; the first data group includes the first data and one or more second data; the second data group includes the One data, and one or more second data; the first data is associated with the second PDCP entity, and the second data is associated with the first PDCP entity.

In a possible design, the transceiver module is also configured to send a second request to the first PDCP entity and receive a second response from the first PDCP entity; wherein the second request is used to request second data of the first data group. Information about whether the submission is completed or the submission is terminated; the second response is used to indicate whether the second data of the first data group is submitted is completed or the submission is terminated.

In a possible design, the transceiver module is also configured to send a third request to the first radio link control RLC entity of the terminal device, and receive a third response from the first RLC entity; wherein the third request is used to request the third Information about whether the second data of a data group has been submitted or terminated; the third response is used to indicate whether the second data of the first data group has been submitted or terminated.

In a possible design, the transceiver module is also configured to receive fifth indication information from the first PDCP entity or the first RLC entity of the terminal device; wherein the fifth indication information is used to indicate the second data of the first data group. The submission is completed or the submission is terminated.

In a possible design, the completion or termination of the submission of the second data of the first data group includes: the second data of the first data group is submitted to the MAC entity of the terminal device by the first RLC entity of the terminal device; or, The second data of a data group is submitted and terminated by one or more of the following entities: the SDAP entity, the first PDCP entity, and the first RLC entity of the terminal device.

It should be noted that the specific implementation of the communication device in the seventeenth aspect may refer to the behavioral functions of the SDAP entity of the terminal device in the data submission method provided by the sixteenth aspect or any possible design of the sixteenth aspect.

In the eighteenth aspect, embodiments of the present application provide a communication device. The communication device may be an SDAP entity of a terminal device or used for implementation. A chip or system on a chip that implements the SDAP entity function of the terminal device. The communication device can realize the functions performed by the SDAP entity of the terminal device in the above aspects or in each possible design, and the functions can be realized by hardware. In a possible design, the communication device may include: a transceiver and a processor. The transceiver and processor may be used to support the communication device to implement the functions involved in the sixteenth aspect or any possible design of the sixteenth aspect. For example: the processor may be configured to obtain the first data of the second data group; the transceiver may be configured to submit the first data of the second data group to the second PDCP entity if the submission of the second data of the first data group is completed or the submission is terminated. Data; wherein, the SDAP entity is associated with the first Packet Data Convergence Protocol PDCP entity of the terminal device and the second PDCP entity of the terminal device; the first data group includes first data, and one or more second data; the second data group It includes first data and one or more second data; the first data is associated with the second PDCP entity, and the second data is associated with the first PDCP entity. In yet another possible design, the communication device may further include a memory for storing computer execution instructions and data of the communication device. When the communication device is running, the transceiver and the processor execute the computer execution instructions stored in the memory, so that the communication device executes the above-mentioned sixteenth aspect or any of the possible designs of the sixteenth aspect. Data submission method.

The specific implementation of the communication device in the eighteenth aspect may refer to the behavioral function of the SDAP entity of the terminal device in the data submission method provided by the sixteenth aspect or any possible design of the sixteenth aspect.

In a nineteenth aspect, embodiments of the present application provide a data submission method. The method may include: the second packet data convergence protocol PDCP entity of the terminal device obtains the first data of the second data group; if the second data of the first data group When the data submission is completed or the submission is terminated, the second PDCP entity submits the first data of the second data group to the second radio link control RLC entity of the terminal equipment; wherein, the service data adaptation protocol SDAP entity of the terminal equipment and the third entity of the terminal equipment A PDCP entity is associated with a second PDCP; the first data group includes first data and one or more second data; the second data group includes first data and one or more second data; the first data and the The second PDCP entity is associated with the second RLC entity; the second data is associated with the first PDCP and the first RLC entity of the terminal device.

Based on the nineteenth aspect, the limiting conditions for the PDCP entity to submit data to the RLC entity are added. Taking the priority of the first data as higher than the priority of the second data as an example, if the second PDCP entity determines the second data of the first data group, When all data submission is completed or the submission is terminated, the second PDCP entity can submit the first data of the second data group to the second RLC entity to prevent the second PDCP entity from preferentially submitting the first data of the second data group to the second RLC entity. As a result, the second data of the first data group cannot be transmitted.

In a possible design, the second PDCP entity sends a fourth request to the SDAP entity and receives a fourth response from the SDAP entity; wherein the fourth request is used to request whether the second data of the first data group is submitted or terminated. information; the fourth response is used to indicate whether the submission of the second data of the first data group is completed or the submission is terminated.

In a possible design, the second PDCP entity sends a fifth request to the first PDCP entity and receives a fifth response from the first PDCP entity; wherein the fifth request is used to request whether the second data of the first data group is submitted. Information on completion or termination of delivery; the fifth response is used to indicate whether the second data of the first data group is completed or terminated.

In a possible design, the second PDCP entity receives sixth indication information from the SDAP entity or the first PDCP entity; wherein the sixth indication information is used to indicate that the second data submission of the first data group is completed or the delivery is terminated.

Based on the above three possible designs, multiple feasible solutions are provided for the second PDCP entity to determine whether the submission of the second data of the first data group is completed or the submission is terminated.

In a possible design, the completion or termination of the submission of the second data of the first data group includes: the second data of the first data group is submitted to the MAC entity of the terminal device by the first RLC entity; or, the first data group The second data is submitted to the first PDCP entity and/or the first RLC entity for termination.

In a twentieth aspect, embodiments of the present application provide a communication device. The communication device can be applied to the second PDCP entity of the terminal device in the nineteenth aspect or the possible design of the nineteenth aspect, so as to realize the third PDCP entity of the terminal device. Functions performed by the second PDCP entity. The communication device can be the second PDCP entity of the terminal device, or it can be a chip or system-on-chip used to implement the functions of the second PDCP entity of the terminal device. The communication device can execute the corresponding functions through hardware. The software implements the functions performed by the second PDCP entity of the above terminal device. The hardware or software includes one or more modules corresponding to the above functions. For example, transceiver module and processing module. The processing module is used to obtain the first data of the second data group; the transceiver module is used to submit the second data to the second radio link control RLC entity of the terminal device if the submission of the second data of the first data group is completed or the submission is terminated. The first data of the data group; wherein the Service Data Adaptation Protocol SDAP entity of the terminal device is associated with the first PDCP and second PDCP entities of the terminal device; the first data group includes the first data and one or more second data ; The second data group includes first data, and one or more second data; the first data is associated with the second PDCP entity and the second RLC entity; the second data is associated with the first PDCP and the first RLC entity of the terminal device .

In one possible design, the transceiver module is also used to send a fourth request to the SDAP entity and receive a fourth response from the SDAP entity; The fourth request is used to request information about whether the second data of the first data group has been submitted or terminated; the fourth response is used to indicate whether the second data of the first data group has been submitted or terminated.

In a possible design, the transceiver module is also configured to send a fifth request to the first PDCP entity and receive a fifth response from the first PDCP entity; wherein the fifth request is used to request the second data of the first data group. Information about whether the submission is completed or the submission is terminated; the fifth response is used to indicate whether the second data of the first data group is submitted is completed or the submission is terminated.

In a possible design, the transceiver module is also configured to receive sixth indication information from the SDAP entity or the first PDCP entity; wherein the sixth indication information is used to indicate that the second data submission of the first data group is completed or the submission is terminated. .

In a possible design, the completion or termination of the submission of the second data of the first data group includes: the second data of the first data group is submitted to the MAC entity of the terminal device by the first RLC entity; or, the first data group The second data is submitted to the first PDCP entity and/or the first RLC entity for termination.

It should be noted that the specific implementation of the communication device in the twentieth aspect may refer to the behavioral function of the second PDCP entity of the terminal device in the data submission method provided by the nineteenth aspect or any possible design of the nineteenth aspect. .

In a twenty-first aspect, embodiments of the present application provide a communication device, which may be a second PDCP entity of a terminal device or a chip or a system-on-chip used to implement the function of the second PDCP entity of a terminal device. The communication device can implement the functions performed by the second PDCP entity of the terminal device in the above aspects or in each possible design, and the functions can be implemented by hardware. In a possible design, the communication device may include: a transceiver and a processor. The transceiver and processor may be used to support the communication device to implement the functions involved in the nineteenth aspect or any possible design of the nineteenth aspect. For example: the processor may be used to obtain the first data of the second data group; the transceiver may be used to submit the second data to the second radio link control RLC entity of the terminal device if the submission of the second data of the first data group is completed or the delivery is terminated. The first data of the second data group; wherein the Service Data Adaptation Protocol SDAP entity of the terminal device is associated with the first PDCP and second PDCP entities of the terminal device; the first data group includes the first data, and one or more third Two data; the second data group includes the first data and one or more second data; the first data is associated with the second PDCP entity and the second RLC entity; the second data is associated with the first PDCP and the first RLC of the terminal device Entity association. In yet another possible design, the communication device may further include a memory, which is used to store computer execution instructions and data of the communication device. When the communication device is running, the transceiver and the processor execute the computer execution instructions stored in the memory, so that the communication device executes the above-mentioned nineteenth aspect or any possible design of the nineteenth aspect. Data submission method.

The specific implementation of the communication device in the twenty-first aspect may refer to the behavioral function of the second PDCP entity of the terminal device in the data submission method provided by the nineteenth aspect or any possible design of the nineteenth aspect.

In a twenty-second aspect, embodiments of the present application provide a communication device. The communication device includes one or more processors; one or more processors for running computer programs or instructions. When the one or more processors execute When the computer instructions or instructions are given, the communication device is caused to perform the data amount indication method as described in the first aspect or any possible design of the first aspect, or to perform the method as described in the fourth aspect or any possible design of the fourth aspect. The data amount indicating method, or perform the data amount indicating method as described in the seventh aspect or any possible design of the seventh aspect; or perform the data amount indicating method as described in the tenth aspect or any possible design of the tenth aspect Submission method; or execute the data submission method as described in the thirteenth aspect or any possible design of the thirteenth aspect; or execute the data as described in the sixteenth aspect or any possible design of the sixteenth aspect Submission method; or perform the data submission method as described in the nineteenth aspect or any possible design of the nineteenth aspect.

In a possible design, the communication device further includes one or more memories, the one or more memories are coupled to one or more processors, and the one or more memories are used to store the above-mentioned computer programs or instructions. In a possible implementation, the memory is located outside the communication device. In another possible implementation, the memory is located within the communication device. In the embodiment of the present application, the processor and the memory may also be integrated into one device, that is, the processor and the memory may also be integrated together. In a possible implementation, the communication device further includes a transceiver, and the transceiver is used to receive information and/or send information.

In a possible design, the communication device further includes one or more communication interfaces, the one or more communication interfaces are coupled to one or more processors, and the one or more communication interfaces are used to communicate with other modules other than the communication device. communicate.

In a twenty-third aspect, embodiments of the present application provide a communication device. The communication device includes an input-output interface and a logic circuit; the input-output interface is used to input and/or output information; and the logic circuit is used to perform the first aspect Or perform the data amount indicating method described in any possible design of the first aspect, or perform the data amount indicating method described in the fourth aspect or any possible design of the fourth aspect, or perform the method described in the seventh aspect or any possible design of the fourth aspect. The data amount indicating method described in any possible design of the seventh aspect; or performing the data submission method described in the tenth aspect or any possible design of the tenth aspect; or performing the thirteenth aspect or the thirteenth aspect aspects of any possible design described in the number or perform the data submission method as described in the sixteenth aspect or any possible design of the sixteenth aspect; or perform the data submission method as described in the nineteenth aspect or any possible design of the nineteenth aspect Data submission method to process and/or generate information based on the information.

In a twenty-fourth aspect, embodiments of the present application provide a computer-readable storage medium that stores computer instructions or programs. When the computer instructions or programs are run on a computer, the results are as described in the first aspect or The data amount indication method described in any possible design of the first aspect is executed, or causes the data amount indication method described in the fourth aspect or any possible design of the fourth aspect to be executed, or causes the data amount indication method described in any possible design of the fourth aspect to be executed, or causes the data amount indication method to be executed as described in the seventh aspect. The data amount indication method described in the aspect or any possible design of the seventh aspect is executed; or the data submission method described in the tenth aspect or any possible design of the tenth aspect is executed; or the method described in the tenth aspect or any possible design of the tenth aspect is executed; or the method described in any possible design of the tenth aspect is executed; The data submission method described in the thirteenth aspect or any possible design of the thirteenth aspect is executed; or the data submission method described in the sixteenth aspect or any possible design of the sixteenth aspect is executed; Or causing the data submission method described in the nineteenth aspect or any possible design of the nineteenth aspect to be executed.

In a twenty-fifth aspect, embodiments of the present application provide a computer program product containing computer instructions. When run on a computer, the amount of data as described in the first aspect or any possible design of the first aspect is The instruction method is executed, or the data amount indication method as described in the fourth aspect or any possible design of the fourth aspect is executed, or the method as described in the seventh aspect or any possible design of the seventh aspect is executed. The data amount indication method is executed; or the data submission method as described in the tenth aspect or any possible design of the tenth aspect is executed; or the data submission method as described in the thirteenth aspect or any possible design of the thirteenth aspect is executed The data submission method is executed; or the data submission method described in the sixteenth aspect or any possible design of the sixteenth aspect is executed; or the data submission method is executed as in the nineteenth aspect or any possible design of the nineteenth aspect. One possible design of the data submission method is implemented.

In a twenty-sixth aspect, embodiments of the present application provide a computer program that, when run on a computer, causes the data amount indication method described in the first aspect or any possible design of the first aspect to be executed, or causing the data amount indicating method described in the fourth aspect or any possible design of the fourth aspect to be executed, or causing the data amount indicating method described in the seventh aspect or any possible design of the seventh aspect to be executed ; Or causing the data submission method described in the tenth aspect or any possible design of the tenth aspect to be executed; or causing the data submission method described in the thirteenth aspect or any possible design of the thirteenth aspect be executed; or cause the data submission method described in the sixteenth aspect or any possible design of the sixteenth aspect to be executed; or cause the data submission method described in the nineteenth aspect or any possible design of the nineteenth aspect to be executed The data submission method is executed.

Among them, the technical effects brought by any one of the design methods in the twenty-second to twenty-sixth aspects can be referred to the technical effects brought by any possible design of the above-mentioned first aspect, or refer to the above-mentioned fourth aspect. The technical effects brought by any possible design in the above aspect, or the technical effects brought by any possible design in the above seventh aspect, or the technical effects brought by any possible design in the tenth aspect above or refer to the technical effects brought by any possible design of the above-mentioned thirteenth aspect, or refer to the technical effects brought by any possible design of the sixteenth aspect above, or refer to the technical effects brought by any possible design of the above-mentioned sixteenth aspect, or refer to the technical effects brought by any possible design of the above-mentioned sixteenth aspect. The technical effects brought about by any possible design of aspect 19.

In a twenty-seventh aspect, a communication system is provided. The communication system may include the communication device as described in any one of the second to third aspects, or include any one of the fifth to sixth aspects. The communication device may include the communication device as described in any one of the eighth to ninth aspects, or the communication device as described in any one of the eleventh to twelfth aspects, or include The communication device as described in any one of the fourteenth to fifteenth aspects, or including the communication device as described in any one of the seventeenth to eighteenth aspects, or including the twentieth aspect to The communication device according to any one of the twenty-first aspects.

Description of the drawings

Figure 1 is a schematic diagram of a communication system provided by an embodiment of the present application;

Figure 2 is a schematic diagram of a 5G communication system provided by an embodiment of the present application;

Figure 3 is a schematic diagram of a user plane protocol stack architecture provided by an embodiment of the present application;

Figure 4 is a schematic diagram of a network architecture provided by an embodiment of the present application;

Figure 5 is a schematic diagram of another network architecture provided by an embodiment of the present application;

Figure 6 is a schematic diagram of another network architecture provided by an embodiment of the present application;

Figure 7 is a schematic diagram of a protocol architecture A provided by an embodiment of the present application;

Figure 8 is a schematic diagram of another protocol architecture A provided by the embodiment of the present application;

Figure 9 is a schematic diagram of a protocol architecture B provided by an embodiment of the present application;

Figure 10 is a schematic diagram of another protocol architecture B provided by the embodiment of the present application;

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

Figure 12 is a flow chart of another data volume indication method provided by an embodiment of the present application;

Figure 13 is a flow chart of yet another data volume indication method provided by an embodiment of the present application;

Figure 14 is a flow chart of yet another data amount indication method provided by an embodiment of the present application;

Figure 15 is a flow chart of a data submission method provided by an embodiment of the present application;

Figure 16 is a flow chart of another data submission method provided by an embodiment of the present application;

Figure 17 is a flow chart of yet another data submission method provided by an embodiment of the present application;

Figure 18 is a flow chart of yet another data submission method provided by an embodiment of the present application;

Figure 19 is a schematic diagram of the composition of a terminal device provided by an embodiment of the present application;

Figure 20 is a schematic diagram of the composition of a communication device provided by an embodiment of the present application.

Detailed ways

The implementation of the embodiments of the present application will be described in detail below with reference to the accompanying drawings.

Among them, the terms "first" and "second" in the description, claims and drawings of this application are used to distinguish different objects, rather than describing a specific sequence. “First” and “second” are only used for descriptive purposes and cannot be understood as indicating or implying relative importance or implicitly indicating the quantity of indicated technical features. Therefore, features defined as "first" and "second" may explicitly or implicitly include one or more of these features. In the description of this embodiment, unless otherwise specified, "plurality" means two or more.

Furthermore, the terms "including" and "having" and any variations thereof are intended to cover non-exclusive inclusion. For example, a process, method, system, product or device that includes a series of steps or units is not limited to the listed steps or units, but optionally also includes steps or units that are not listed, or optionally also includes Other steps or units inherent to such processes, methods, products or devices.

It should be understood that in this application, "at least one (item)" refers to one or more. "Plural" means two or more. "At least two (items)" means two or three or more than three. "And/or" is used to describe the relationship between associated objects, indicating that three relationships can exist. For example, "A and/or B" can mean: only A exists, only B exists, and both A and B exist simultaneously, where A and B can be singular or plural. The character "/" generally indicates that the related objects are in an "or" relationship. “At least one of the following” or similar expressions thereof refers to any combination of these items, including any combination of a single item (items) or a plurality of items (items). For example, at least one of a, b or c can mean: a, b, c, "a and b", "a and c", "b and c", or "a and b and c" ”, where a, b, c can be single or multiple. "...when" and "if" both mean that corresponding processing will be made under certain objective circumstances. They do not limit the time, nor do they require judgment during implementation, nor do they mean that there are other limitations.

In the embodiments of this application, words such as "exemplary" or "for example" are used to represent examples, illustrations or explanations. Any embodiment or design described as "exemplary" or "such as" in the embodiments of the present application is not to be construed as preferred or advantageous over other embodiments or designs. Rather, the use of words such as "exemplary" or "such as" is intended to present related concepts in a concrete manner that is easier to understand.

The data amount indication method provided by the embodiment of the present application can be used in any communication system. The communication system can be a third generation partnership project (3GPP) communication system, for example, long term evolution (LTE) The system can be a fifth generation (5G) mobile communication system, a new radio (NR) communication system, a new radio (vehicle to everything, NR V2X) system, and can also be applied to LTE and 5G In hybrid networking systems, or non-terrestrial network (NTN) systems, device-to-device (D2D) communication systems, machine-to-machine (M2M) communication systems, The Internet of Things (IoT) and other next-generation communication systems, such as 6G and other future communication systems, can also be non-3GPP communication systems without restrictions.

The following uses Figure 1 as an example to describe the communication system provided by the embodiment of the present application.

Figure 1 is a schematic diagram of a communication system provided by an embodiment of the present application. As shown in Figure 1, the communication system may include terminal equipment, network equipment, core network elements and a data network (DN); wherein, the core Network elements may include mobility management network elements, session management network elements, user plane network elements and other network elements.

Among them, the terminal device in Figure 1 may be located within the cell coverage of the network device. Among them, the terminal device can communicate with the network device through the air interface through uplink (UL) or downlink (downlink, DL). For example: the terminal device can send uplink data to the network device through the physical uplink shared channel (PUSCH) in the UL direction; the network device can send uplink data to the network device through the physical downlink shared channel (PDSCH) in the DL direction. The terminal device sends downlink data.

In Figure 1, the terminal device can also communicate with the core network element through a specific interface. For example, the terminal device can communicate with the mobility management network element in the core network element through the N1 interface.

After the terminal device is connected to the network, it can establish a protocol data unit (PDU) session and access it through the PDU session. External data network, which interacts with application servers deployed in the data network.

Among them, the terminal equipment (user equipment, UE) in Figure 1 can be a device with wireless transceiver functions or a chip or chip system that can be installed on the device. It can also be called a terminal or a mobile station (MS). ) or mobile terminal (mobile terminal, MT), etc. Specifically, the terminal device in Figure 1 can be a mobile phone, a tablet computer, or a computer with wireless transceiver functions. Terminal devices can also be virtual reality (VR) terminals, augmented reality (AR) terminals, wireless terminals in industrial control, wireless terminals in driverless driving, wireless terminals in telemedicine, and smart grids. Wireless terminals, wireless terminals in smart cities, wireless terminals in smart homes, vehicle-mounted terminals, vehicles with vehicle-to-vehicle (V2V) communication capabilities, intelligent network connections Vehicles, drones with UAV to UAV (U2U) communication capabilities, etc. are not restricted.

The network device in Figure 1 can be any device deployed in the access network and capable of wireless communication with terminal devices. It is mainly used to implement wireless physical control functions, resource scheduling and wireless resource management, wireless access control and mobility. Management and other functions. Specifically, the network device may be a device that supports wired access or a device that supports wireless access. For example, the network device may be an access network (AN)/radio access network (RAN) device, which is composed of multiple AN/RAN nodes. AN/RAN nodes can be: access point (AP), base station (nodeB, NB), macro base station, micro base station, relay station, enhanced base station (enhance nodeB, eNB), next generation base station (NR nodeB, gNB ), transmission reception point (TRP), transmission point (TP) or some other access node, etc. Network equipment can also be a centralized unit (CU)/distributed unit (DU) architecture. In this case, the network equipment can include two network elements: CU and DU; the network equipment can also be a control plane-user plane. (control plane-user plane, CP-UP) architecture. At this time, the network equipment can include three network elements: CU control plane (CU-CP), CU user plane (CU-UP) and DU, without restrictions. .

The mobility management network element in Figure 1 is mainly responsible for the access authentication of terminal equipment, mobility management, signaling interaction between various functional network elements, etc., such as: user registration status, user connection status, user registration Network access, tracking area update, cell switching user authentication and key security are managed.

The session management network element in Figure 1 can be called a session management function or a multicast/broadcast-service management function (MB-SMF) or a multicast session management network element, etc., without limitation. The session management network element is mainly used to implement user plane transmission logical channels, such as session management functions such as establishment, release and modification of PDU sessions. The session management network element can also send the quality of service flow (QoS flow) configuration and QoS requirements of the PDU session to the network device through the mobility management network element.

The user plane network elements in Figure 1 can be called PDU session anchors and user plane functions. The user plane network element can be used as an anchor point on the user plane transmission logical channel. It is mainly used to complete functions such as routing and forwarding of user plane data, such as establishing a channel with the terminal device (i.e., user plane transmission logical channel). In this channel It forwards data packets between the terminal device and the data network and is responsible for data packet filtering, data forwarding, rate control, and generation of accounting information for the terminal device.

The data network in Figure 1 can be an operator network that provides data transmission services to users. For example, it can be an operator network that provides Internet protocol multi-media services (IMS) to users. An application server (AS) can be deployed in the data network, and the application server can provide data transmission services to users.

It should be noted that the terminal equipment, network equipment and core network elements in the embodiments of this application can all be one or more chips, or they can be a system on chip (SOC), etc. Figure 1 is only an exemplary drawing, and the number of devices included therein is not limited. Furthermore, the communication system may include other devices in addition to the devices shown in Figure 1 . The names of each device and each link in Figure 1 are not restricted. In addition to the names shown in Figure 1, each device and each link can also be named with other names. In addition to the network elements shown in Figure 1, the network shown in Figure 1 can also include policy control network elements, application function network elements, network slice selection network elements, network warehouse network elements, authentication service network elements, network data analysis network elements, network Present network elements, etc., are not restricted.

Taking the communication system shown in Figure 1 as a 5G communication system as an example, as shown in Figure 2, the network elements or entities corresponding to the above network devices can be the network elements or entities corresponding to the RAN and mobility management network elements in the 5G communication system. The network element or entity corresponding to the access and mobility management function (AMF) and session management network element in the 5G communication system can be the session management function (session management function) in the 5G communication system. SMF), the network element or entity corresponding to the user plane network element can be the user plane function (UPF) in the 5G communication system.

Among them, as shown in Figure 2, the UE can communicate with the AMF through the N1 interface, the RAN can communicate with the AMF through the N2 interface, the RAN can also communicate with the UPF through the N3 interface, and the UPF can communicate with the application server in the DN through the N6 interface. The core network elements can They can communicate with each other through service-oriented interfaces. For example, AMF can communicate with other core network elements through the Namf interface, and SMF can communicate with other core network elements through the Nsmf interface.

Before describing the embodiments of the present application, technical terms involved in the embodiments of the present application are described.

User plane protocol stack architecture: the protocol suite used for user data transmission. As shown in Figure 3, it can include the service data adaptation protocol (service data adaptation protocol, SDAP) layer, packet data convergence protocol (packet data convergence protocol, PDCP) layer, wireless link control (radio link control, RLC) layer, Media access control (medium access control, MAC) layer and physical (physical, PHY) layer.

Control plane protocol stack architecture: that is, the protocol suite used for system control signaling transmission. Can include non-access (non-access stratum, NAS) layer, radio resource control (radio resource control, RRC) layer, PDCP layer, RLC layer, MAC layer and PHY layer.

Protocol data unit (PDU): It can be divided into two categories: data PDU (data PDU) and control PDU (control PDU). PDCP data PDU can carry control plane data and/or user plane data. The PDCP control PDU mainly carries any one or more of robust header compression (ROHC) feedback, Ethernet header compression (EHC) feedback and PDCP status report.

Buffer status reporting (BSR): The terminal device can send a BSR to the network device to request resources from the network device. For example, the terminal device needs to send data to the network device. The terminal device can send a BSR to the network device to indicate to the network device the size of the data to be sent by the terminal device. The network device can determine the size of the data to be sent by the terminal device based on the BSR, and then provide the terminal with The device configures uplink resources, and the terminal device sends data to the network device according to the uplink resources configured by the network device.

For example, the PDCP entity of the terminal device may submit the data to the RLC entity of the terminal device, and the PDCP entity of the terminal device indicates the PDCP data amount to the MAC entity of the terminal device and/or the RLC entity of the terminal device indicates the RLC data amount to The MAC entity of the terminal device. The MAC entity generates a BSR based on the data amount indicated by the PDCP entity and/or the data amount indicated by the RLC entity, and sends it to the network device.

By way of example, the PDCP data volume may include one or more of the following:

(1) PDCP service data unit (SDU) that has not yet constructed PDCP data PDU;

(2) PDCP data PDU that has not yet been submitted to the lower layer (for example, RLC layer);

(3) PDCP control PDU;

(4) For acknowledged mode (AM) DRB, PDCP SDU to be retransmitted; or,

(5) For AM DRB, PDCP data PDU to be retransmitted.

The PDCP data volume may be referred to as the data volume indicated by the PDCP entity to the MAC entity.

In a standalone (SA) networking scenario, a PDCP entity can be associated with an RLC entity. For example, the PDCP entity may deliver the data to the RLC entity associated with the PDCP entity, and indicate the PDCP data amount to the MAC entity or the MAC entity associated with the RLC entity.

In carrier aggregation (CA) and/or dual connectivity (DC) scenarios, a PDCP entity can be associated with one or more RLC entities.

For example, if the terminal device is configured with PDCP duplication, the PDCP entity can submit data PDUs to each activated RLC entity and only submit control PDUs to the primary RLC (primary RLC) entity. The RLC entity associated with the PDCP entity may include a primary RLC entity and one or more secondary RLC entities. The activated RLC entity may include the primary RLC entity. Optionally, the activated RLC entity may also include secondary RLC entities associated with the PDCP entity. One or more of the entities. For data volume indication:

The PDCP entity may indicate the amount of PDCP data to the MAC entity associated with the primary RLC entity.

The PDCP entity may indicate the amount of PDCP data other than control PDUs to the MAC entity associated with other activated RLC entities; wherein the other activated RLC entities include RLC entities other than the primary RLC entity among the activated RLC entities.

The PDCP entity may indicate to the MAC entity associated with the deactivated RLC entity that the PDCP data amount is 0.

If the terminal device is configured with split radio bearer (split RB), when the amount of data is large, the PDCP entity can submit data to the primary RLC entity or the split secondary RLC (split secondary RLC) entity. When the amount of data is small, The PDCP entity can submit data to the primary RLC entity. For data volume indication:

When the amount of data is large, the PDCP entity can indicate the amount of PDCP data to the MAC entity associated with the primary RLC entity and the MAC entity associated with the split secondary RLC entity; indicate to other RLC entities that the amount of PDCP data is 0. The MAC entity associated with the primary RLC entity and the MAC entity associated with the split secondary RLC entity may be the same MAC entity or different MAC entities.

When the data amount is small, the PDCP entity can indicate the PDCP data amount to the MAC entity associated with the primary RLC entity and indicate to other RLC entities that the PDCP data amount is 0.

When transmitting data between the terminal device and the application server in the data network, any of the network architectures shown in Figures 4 to 6 below can be used for data transmission.

As shown in Figure 4, the application server can use different data flows to transmit different data to the terminal device. Specifically, the application server can use different data flows to send different data to the user plane network element; the user plane network element can use different data Streams (such as different quality of service (QoS) streams) send different data to network devices; network devices can also use different data streams (such as different data radio bearers (DRB) or different Logical channel (logical channel, LCH)) sends different data to the terminal device.

It should be noted that different data can be data of different priorities, different types of data, or other different data, without limitation. The data flow between the application server and the user plane network element, the data flow between the user plane network element and the network device, and the data flow between the network device and the terminal device can represent different meanings, such as the application server and the user plane network element. The data flow between them can be Internet protocol (IP) flow, the data flow between user plane network elements and network equipment can be QoS flow, and the data flow between network equipment and terminal equipment can be DRB or LCH, etc. , not restricted.

For example, taking the extended reality (XR) communication scenario as an example, the data can be divided into data of different priorities according to the importance of the data, and the data of different priorities can be transmitted through different data streams. Among them, XR communication scenarios are all real and virtual combined environments and human-computer interactions generated by computer technology and wearable devices. It can include different types of reality, such as the following representative forms and the fields in which they are inserted: AR, VR, mixed reality (MR).

For example, take the application server transmitting a group of continuous pictures (GOP) to the terminal device as an example. The GOP can include an I frame and one or more P frames. The I frame has a higher priority than the P frame. The application server Data stream 1 can be used to send I frames to the terminal device, and data stream 2 can be used to send P frames to the terminal device. The data flow may include any one or more of the data flow between the application server and the user plane network element, the data flow between the user plane network element and the network device, and the data flow between the network device and the terminal device. .

For example, the I frame is an intra-coded frame (which may also be called a key frame), and the P frame is a forward prediction frame (which may also be called a forward reference frame). The I frame is a complete picture, and the P frame records the changes relative to the I frame. If there is no I frame, the P frame will not be decoded, so the transmission priority of the I frame needs to be higher than that of the P frame.

Different from the application server in Figure 4 that uses different data flows to transmit different data to the user plane network element, as shown in Figure 5, the application server can also use the same data flow to transmit different data to the user plane network element. After receiving the data sent by the application server, the element can distinguish the data and transmit different data to the network device through different data flows (such as different QoS flows). The network device uses different data flows (such as different DRBs or different LCH) transmits different data to the terminal device.

For example, taking the application server transmitting a GOP including an I frame and one or more P frames to the terminal device as an example, the application server can use the same data flow to send I frames and P frames to the user plane network element; the user plane network element can use the QoS flow 1 sends I frames to the network device, and uses QoS flow 2 to send P frames to the network device; the network device can use DRB1 to send I frames to the terminal device, and DRB2 to send P frames to the terminal device.

What is different from the user plane network element in Figure 5 that uses different data flows to transmit different data to the network device is that, as shown in Figure 6, the user plane network element can also use the same data flow (such as the same QoS flow) to transmit to the network device. For different data, after the network device receives the data sent by the user plane network element, it can distinguish the data and transmit different data to the terminal device through different data streams (such as different DRBs or different LCHs).

For example, taking the application server transmitting a GOP including an I frame and one or more P frames to the terminal device, the application server can use the same data flow to send I frames and P frames to the user plane network element; the user plane network element can use the same QoS The flow sends I frames and P frames to the network device; the network device can use DRB1 to send I frames to the terminal device, and DRB2 to send P frames to the terminal device.

The above Figures 4 to 6 describe the network architecture by taking the application server to send data to the terminal device as an example. When the terminal device sends data to the application server, for example, the terminal device can use the mapping relationship between the QoS flow and the DRB or LCH. , mapping application layer data to the corresponding DRB or LCH for transmission.

For example, taking the use of different QoS streams to transmit different data between user plane network elements and network devices in Figures 4 and 5 above, the SDAP layer of the terminal device can receive data associated with different QoS streams sent by the application layer. , the SDAP entity can submit data associated with different QoS flows to different PDCP entities, and the PDCP entity can submit the received data to the RLC entity associated with itself, and indicate the amount of PDCP data to the MAC entity or the MAC entity associated with the RLC entity.

For example, as shown in Figure 7, taking the SDAP entity receiving data associated with QoS flow 1 and data associated with QoS flow 2 sent by the application layer as an example, the SDAP entity can submit associated QoS flow 1 (or described as associated QoS flow 1) to PDCP entity 1. The data of flow identifier 1 (QoS flow identifier 1, QFI 1)) is submitted to PDCP entity 2 for data associated with QoS flow 2 (or described as associated with QFI 2). PDCP entity 1 submits data associated with QoS flow 1 to RLC entity 1 associated with itself, and indicates the amount of PDCP data to the MAC entity associated with RLC entity 1. The PDCP entity 2 submits the data associated with the QoS flow 2 to the RLC entity 2 associated with itself, and indicates the amount of PDCP data to the MAC entity associated with the RLC entity 2.

In the second example, taking the same QoS stream to transmit different data between the user plane network element and the network device in Figure 6 above, the SDAP layer of the terminal device can receive different data associated with the same QoS stream sent by the application layer. The SDAP entity can distinguish data based on identification information and submit different data to different PDCP entities. The PDCP entity can submit the received data to its associated RLC entity and indicate the amount of data to the MAC entity associated with the RLC entity.

For example, the identification information may be included in the header of the data. For example, identification information is used to distinguish different data.

For example, the identification information may include/be called: extended QoS identifier (extended QoS identifier, eQI). It should be noted that the identification information can also have other names without limitation.

For example, "the SDAP entity can differentiate data based on identification information" may include: the SDAP entity can differentiate data based on identification information and QFI.

For example, as shown in Figure 8, taking the SDAP entity receiving different data associated with the same QoS flow sent by the application layer as an example, the SDAP entity can distinguish the received data according to the eQI into data 1 associated with eQI 1 and data associated with eQI 2 2. Submit data 1 associated with eQI 1 to PDCP entity 1, and submit data 2 associated with eQI 2 to PDCP entity 2. PDCP entity 1 may submit data 1 to its associated RLC entity 1 and indicate the PDCP data amount to the MAC entity associated with RLC entity 1. PDCP entity 2 may submit data 2 to its associated RLC entity 2 and indicate the PDCP data amount to the MAC entity associated with RLC entity 2.

In the above two examples, the SDAP entity of the terminal device is associated with multiple PDCP entities. The SDAP entity can submit different data to different PDCP entities. The PDCP entity can refer to the above description of data submission to submit the received data to its associated RLC entity. Data, refer to the foregoing description of PDCP data amount indication to indicate the PDCP data amount to the MAC entity associated with the RLC entity. It should be noted that the above-mentioned protocol architecture shown in Figures 7 and 8 can be called protocol architecture A.

In the third example, taking the use of different QoS streams to transmit different data between user plane network elements and network devices in Figures 4 and 5 above, the SDAP layer of the terminal device can receive associated different QoS streams sent by the application layer. The SDAP entity can submit data associated with different QoS flows to the same PDCP entity, and the PDCP entity can submit data associated with different QoS flows to different RLC entities associated with itself.

For example, as shown in Figure 9, taking the SDAP entity receiving data associated with QoS flow 1 and data associated with QoS flow 2 sent by the application layer as an example, the SDAP entity can submit associated QoS flow 1 (or described as associated QFI 1) to the PDCP entity ) and data associated with QoS flow 2 (or described as associated QFI 2). The PDCP entity can submit data associated with QoS flow 1 to its associated RLC entity 1, and submit data associated with QoS flow 2 to its associated RLC entity 2.

In the fourth example, taking the same QoS stream to transmit different data between the user plane network element and the network device in Figure 6 above, the SDAP layer of the terminal device can receive different data associated with the same QoS stream sent by the application layer. The SDAP entity can submit different data associated with the same QoS flow to the same PDCP entity. The PDCP entity can distinguish the data based on identification information and submit data associated with different identification information to different RLC entities.

For example, as shown in Figure 10, taking the SDAP entity receiving different data associated with the same QoS flow sent by the application layer as an example, the SDAP entity can submit different data associated with the same QoS flow to the PDCP entity, and the PDCP entity can convert the received data according to the eQI. The data is divided into data 1 associated with eQI 1 and data 2 associated with eQI 2. Data 1 associated with eQI 1 is submitted to RLC entity 1, and data 2 associated with eQI 2 is submitted to RLC entity 2.

In the third and fourth examples above, the SDAP entity of the terminal device is associated with a PDCP entity. The PDCP entity can be associated with multiple RLC entities and submit different data to different RLC entities, as shown in Figures 9 and 10 above. The protocol architecture can be called protocol architecture B.

Based on the above protocol architecture A, the PDCP entity can submit the same data to one or more RLC entities associated with itself, and indicate the data amount to the MAC entity with reference to the foregoing description of data amount indication. However, for protocol architecture B, the PDCP entity delivers different data to different RLC entities associated with itself. How the PDCP entity indicates the amount of data to the MAC entity has become an urgent technical issue to be solved.

In addition, in the above four examples, if the data transmission delay is greater than the business cycle, the previous set of data (or described as the previous set of data) may appear. Data group) has not been transmitted yet, the next group of data (or described as the next data group) has arrived, if the transmission priority of some data in the next group of data is greater than the transmission of the untransmitted data in the previous group of data The priority will cause the terminal device to give priority to the data with a higher transmission priority in the next group of data, which will cause the data with a lower transmission priority in the previous group of data to fail to be transmitted or to be delayed.

Among them, the transmission priority can also be described as priority, logical channel priority, etc., which will not be described again.

Based on this, it is proposed that the transmission priority of the data in the previous group of data can be increased to prevent the terminal device from preferentially transmitting the data with a higher transmission priority in the next group of data. However, if the data in the previous group of data is increased, The transmission priority will affect the transmission of data whose transmission priority is between the adjusted transmission priority of the data in the previous group of data and the transmission priority of the data in the next group of data.

For example, taking the terminal device transmitting a GOP as an example, it may happen that the P frame in the previous GOP has not been transmitted yet and the next GOP has arrived, because the transmission priority of the I frame in the next GOP is greater than the P frame in the previous GOP. The transmission priority of the frame. At this time, the terminal device will give priority to transmitting the I frame in the next GOP, causing the P frame in the previous GOP to be unable to be transmitted or to be delayed. If the transmission priority of the P frame in the previous GOP is adjusted to a transmission priority higher than the transmission priority of the I frame in the next GOP, it will affect the transmission priority between the adjusted transmission priority of the P frame and the I frame. Transmission of data between frame transmission priorities.

In order to solve the above technical problems, embodiments of the present application provide a data amount indication method. The method may include: the PDCP entity of the terminal device indicates the first data amount to the MAC entity of the terminal device, and indicates the second data amount to the MAC entity; Wherein, the PDCP entity is associated with the first RLC entity of the terminal device and the second RLC entity of the terminal device, the first data amount includes the data amount of the first data set, the first data set is associated with the first RLC entity; the second data amount A data amount including a second data set associated with a second RLC entity.

In this embodiment of the present application, if the PDCP entity submits the first data set to the first RLC entity, the PDCP entity may indicate the first data amount to the MAC entity associated with the first RLC entity. If the PDCP entity submits the second data set to the second RLC entity, the PDCP entity may indicate the second data amount to the MAC entity associated with the second RLC entity. The MAC entity can determine the BSR based on the amount of data indicated by the PDCP entity, which is conducive to accurate reporting of the BSR and thus saves resources.

In specific implementation, as shown in Figure 1 or Figure 2, for example, each terminal device, network device, and core network device can adopt the composition structure shown in Figure 11, or include the components shown in Figure 11. Figure 11 is a schematic diagram of the composition of a communication device 1100 provided by an embodiment of the present application. The communication device 1100 can be a terminal device or a chip or a system on a chip in a terminal device; it can also be a network device or a chip or a system on a chip in a network device. ; It can also be a core network device or a chip or system on a chip in the core network device. As shown in FIG. 11 , the communication device 1100 includes a processor 1101 , a transceiver 1102 and a communication line 1103 .

Further, the communication device 1100 may also include a memory 1104. The processor 1101, the memory 1104 and the transceiver 1102 may be connected through a communication line 1103.

Among them, the processor 1101 is a central processing unit (CPU), a general-purpose processor, a network processor (NP), a digital signal processor (DSP), a microprocessor, a microcontroller, Programmable logic device (PLD) or any combination thereof. The processor 1101 can also be other devices with processing functions, such as circuits, devices or software modules, without limitation.

Transceiver 1102, used to communicate with other devices or other communication networks. The other communication network may be Ethernet, wireless access network (radio access network, RAN), wireless local area networks (wireless local area networks, WLAN), etc. Transceiver 1102 may be a module, circuit, transceiver, or any device capable of enabling communications.

The communication line 1103 is used to transmit information between components included in the communication device 1100 .

Memory 1104, used to store instructions. Wherein, the instructions may be computer programs.

Among them, the memory 1104 can be a read-only memory (ROM) or other types of static storage devices that can store static information and/or instructions, or it can be a random access memory (random access memory, RAM) or other types of static storage devices that can store static information and/or instructions. Other types of dynamic storage devices that store information and/or instructions can also be electrically erasable programmable read-only memory (EEPROM), compact disc read-only memory (CD- ROM) or other optical disc storage, optical disc storage (including compressed optical discs, laser discs, optical discs, digital versatile discs, Blu-ray discs, etc.), magnetic disk storage media or other magnetic storage devices, etc., are not restricted.

It should be noted that the memory 1104 may exist independently of the processor 1101 or may be integrated with the processor 1101. The memory 1104 can be used to store instructions or program codes or some data. The memory 1104 may be located within the communication device 1100 or outside the communication device 1100, without limitation. The processor 1101 is configured to execute instructions stored in the memory 1104 to implement the data amount indication method provided in the following embodiments of this application.

In one example, the processor 1101 may include one or more CPUs, such as CPU0 and CPU1 in FIG. 11 .

As an optional implementation manner, the communication device 1100 includes multiple processors. For example, in addition to the processor 1101 in Figure 11, it may also include a processor 1107.

As an optional implementation manner, the communication device 1100 also includes an output device 1105 and an input device 1106. For example, the input device 1106 is a device such as a keyboard, a mouse, a microphone, or a joystick, and the output device 1105 is a device such as a display screen, a speaker, or the like.

It should be noted that the communication device 1100 may be a desktop computer, a portable computer, a network server, a mobile phone, a tablet computer, a wireless terminal, an embedded device, a chip system, or a device with a similar structure as shown in FIG. 11 . In addition, the composition structure shown in FIG. 11 does not constitute a limitation of the communication device. In addition to the components shown in FIG. 11 , the communication device may include more or less components than shown in the figure, or some components may be combined. , or a different component arrangement.

In the embodiments of this application, the chip system may be composed of chips, or may include chips and other discrete devices.

In addition, actions, terms, etc. involved in various embodiments of this application can be referred to each other and are not limited. In the embodiments of this application, the name of the message exchanged between the various devices or the name of the parameters in the message is just an example, and other names may also be used in the specific implementation without limitation.

In conjunction with the communication system shown in Figure 1 or Figure 2, and with reference to Figure 12 below, the data amount indication method provided by the embodiment of the present application will be described, wherein the terminal device can be any terminal device in the communication system shown in Figure 1 or Figure 2 , the network device can be any network device in the communication system shown in Figure 1 or Figure 2. The terminal equipment and network equipment described in the following embodiments may all be equipped with the components shown in Figure 11. The processing performed by a single execution subject (terminal device or network device) shown in the embodiments of this application can also be divided into multiple execution subjects for execution. These execution subjects can be logically and/or physically separated. be restricted.

It should be noted that in the various embodiments shown in Figures 12 to 18 of this application, the data amount indicated by the PDCP entity to the MAC entity is the PDCP data amount.

Figure 12 is a flow chart of a data volume indication method provided by an embodiment of the present application. As shown in Figure 12, the method is applied to a terminal device. The method may include:

Step 1201: The PDCP entity indicates the first data amount to the MAC entity.

Step 1202: The PDCP entity indicates the second data amount to the MAC entity.

For example, the PDCP entity indicating the first data amount to the MAC entity includes: the PDCP entity indicating the first data amount to the MAC entity associated with the first RLC entity.

For example, the PDCP entity indicating the second data amount to the MAC entity includes: the PDCP entity indicating the second data amount to the MAC entity associated with the second RLC entity.

For example, in the terminal device in Figure 12, the PDCP entity can be associated with multiple RLC entities, and the PDCP entity can submit different data to different RLC entities (such as using the protocol architecture B shown in Figure 9 or Figure 10 above) .

It should be noted that when the PDCP entity submits data to the RLC entity, the submission may be executed, or the submission may be terminated due to some reasons. Therefore, the data submitted by the PDCP entity to the RLC entity can also be described as: PDCP entity submits to RLC The data of the entity is either described as data that the PDCP entity is preparing to submit to the RLC entity, or is described as data that the PDCP entity will submit to the RLC entity, or is described as data that the PDCP entity may submit to the RLC entity, or is described as data associated with the RLC entity Data, no restrictions.

Exemplarily, the PDCP entity may also include the data amount (for example, the PDCP data amount) associated with a certain RLC entity (such as the first RLC entity) in a certain data amount (such as the first data amount) and indicate to the The MAC entity associated with this RLC entity.

For example, if the PDCP entity is associated with multiple RLC entities, the PDCP entity may indicate multiple data amounts to the MAC entity. The number of data amounts indicated by the PDCP entity to the MAC entity may be less than or equal to the number of RLC entities associated with the PDCP entity, and is not limited by this application.

For example, taking the PDCP entity associating the first RLC entity and the second RLC entity as an example, the PDCP entity submits the first data set to the first RLC entity and submits the second data set to the second RLC entity. The PDCP entity may indicate the first data amount to the MAC entity associated with the first RLC entity and the second data amount to the MAC entity associated with the second RLC entity. It should be noted that the PDCP entity may also be associated with other RLC entities, which is not limited by this application.

In the embodiment of this application, the description related to "the PDCP entity submits the data set or data to the RLC entity" does not limit whether the PDCP entity performs the submission.

For example, a first data set is associated with a first RLC entity. For example, the first data set may be data that the PDCP entity may submit to the first RLC entity, or may be data that the PDCP entity is preparing to submit to the first RLC entity, or may be described as data that the PDCP entity will submit to the first RLC entity. Data handed over to the first RLC entity, or data described as associated with the first RLC entity, is not restricted. It should be noted that this does not limit that part or all of the first data set must be submitted to the first RLC entity.

For example, the second data set is associated with a second RLC entity. For example, the second data set may be data that the PDCP entity may submit to the second RLC entity, or may be data that the PDCP entity prepares to submit to the second RLC entity, or may be described as data that the PDCP entity will submit to the second RLC entity. Or described as data associated with the second RLC entity, which is not restricted. It should be noted that this does not limit that part or all of the second data set must be submitted to the second RLC entity.

For example, the first data amount may include the data amount of the first data set.

For example, the second amount of data may include the amount of data of the second data set.

It should be noted that the MAC entity associated with the first RLC entity and the MAC entity associated with the second RLC entity may be the same MAC entity or different MAC entities.

Optionally, the first data amount does not include the data amount of the second data set. Optionally, the second data amount does not include the data amount of the first data set.

For another example, taking the PDCP entity associating the first RLC entity, the second RLC entity and the third RLC entity as an example, the PDCP entity may submit the first data set to the first RLC entity, the second data set to the second RLC entity, and the second data set to the second RLC entity. The third RLC entity submits a third data set. The PDCP entity may indicate the first data amount to the MAC entity associated with the first RLC entity, the second data amount to the MAC entity associated with the second RLC entity, and the fourth data amount to the MAC entity associated with the third RLC entity.

For example, a third data set is associated with a third RLC entity. The third data set may be data that the PDCP entity may submit to the third RLC entity, or may be data that the PDCP entity is preparing to submit to the third RLC entity, or may be described as data that the PDCP entity will submit to the third RLC entity, or describe Data associated with the third RLC entity is not restricted. It should be noted that this does not limit that part or all of the third data set must be submitted to the third RLC entity.

For example, the fourth data amount may include the data amount of the third data set.

It should be noted that any two or three of the MAC entity associated with the first RLC entity, the MAC entity associated with the second RLC entity, and the MAC entity associated with the third RLC entity may be the same MAC entity, or they may be Different MAC entities.

Optionally, the first data amount does not include the data amount of the second data set and/or the data amount of the third data set. Optionally, the second data amount does not include the data amount of the first data set and/or the data amount of the third data set. Optionally, the fourth data amount does not include the data amount of the first data set and/or the data amount of the second data set.

Optionally, taking the PDCP entity associating the first RLC entity and the second RLC entity as an example, the PDCP entity receives the data submitted by the SDAP entity and can determine the first data set and the RLC entity based on the QFI or eQI or RLC entity associated with the received data. Second data set.

For example, the data in the first data set is data associated with the first QFI, and the data in the second data set is data associated with the second QFI. Alternatively, the data in the first data set is data associated with the first eQI, and the data in the second data set is data associated with the second eQI.

The data set may include one or more data. Data may include PDUs and/or SDUs.

For example, the PDU may include a PDCP data PDU. For example, the SDU may include PDCP SDU.

For example, the first set of data may include one or more PDUs and/or SDUs. For example, the second set of data may include one or more PDUs and/or SDUs.

Optionally, the priority of the data included in the first data set is different from the priority of the data included in the second data set.

Optionally, the first data set includes part or all of the second data of one or more data groups. Optionally, the second data set includes part or all of the first data of one or more data groups. Optionally, the data group includes first data and one or more second data.

For example, taking the data group as a GOP, depending on the encoding technology, the first data can be an I frame, and the second data can be a P frame; the first data can also be basic layer data, and the second data can also be Enhancement layer data; not limited.

In this embodiment of the present application, the I frame may include: I frame data. In this embodiment of the present application, the P frame may include: P frame data.

For example, assuming that the data group is a GOP, the first data is an I frame, and the second data is a P frame, the first data set may include part or all of the P frames in one or more GOPs, and the second data set may include a or some or all I-frames in multiple GOPs. The PDCP entity may submit the I frame to the second RLC entity, and include the data amount corresponding to the I frame in the second data amount and indicate it to the MAC entity associated with the second RLC entity. The PDCP entity may also submit the P frame to the first RLC entity, and include the data amount corresponding to the P frame in the first data amount and indicate it to the MAC entity associated with the first RLC entity.

It should be noted that in a data group, different second data can be associated with the same or different RLC entities.

Optionally, the priority of the first data is higher than the priority of the second data.

Optionally, the first data amount also includes the data amount of the control PDU set; and/or the second data amount also includes the data amount of the control PDU set.

For example, a set of control PDUs may include one or more PDCP control PDUs.

Among them, the PDCP entity can determine which RLC entity is used to submit the control PDU set according to preconfiguration or predefinition or protocol regulations or base station configuration. If the control PDU set is delivered through the first RLC entity, the first data amount also includes the data amount of the control PDU set. If the control PDU set is delivered through the second RLC entity, the second data amount also includes the data amount of the control PDU set. If the control PDU set can be delivered through the first RLC entity and/or the second RLC entity, both the first data amount and the second data amount include the data amount of the control PDU set.

Optionally, the method may also include step 1203: the PDCP entity obtains the first data amount. For example, step 1203 may precede step 1201.

Optionally, the method may also include step 1204: the PDCP entity obtains the second amount of data. For example, step 1204 may precede step 1202.

It should be noted that step 1201, or step 1203 and step 1201 can be used as independent embodiments and do not depend on step 1202.

Based on the method shown in Figure 12 above, the way in which the PDCP entity indicates the amount of data to the MAC entity is modified. If the PDCP entity submits the first data set to the first RLC entity, the PDCP entity can report the amount of data to the MAC entity associated with the first RLC entity. Indicates the first data amount. If the PDCP entity submits the second data set to the second RLC entity, the PDCP entity may indicate the second data amount to the MAC entity associated with the second RLC entity. The PDCP entity can differentiate the data (or describe it as differentiating RLC entities) when indicating the data amount to the MAC entity. Different data (or describe it as data associated with different RLC entities) can be indicated to the MAC through different data amounts. entity. The MAC entity can determine the BSR based on the amount of data indicated by the PDCP entity, which is conducive to accurate reporting of the BSR and thus saves resources.

Different from the distinction between data when the PDCP entity indicates the data amount to the MAC entity in the above-mentioned Figure 12, referring to the following Figure 13, the PDCP entity indicates the data amount to the MAC entity and does not need to differentiate the data.

Figure 13 is a data volume indication method provided by an embodiment of the present application. This method can be applied to a terminal device. The method can include:

Step 1301: The PDCP entity obtains the third amount of data.

Step 1302: The PDCP entity indicates the third data amount to the MAC entity.

For example, in the terminal device in Figure 13, the PDCP entity can be associated with multiple RLC entities, and the PDCP entity can submit different data to different RLC entities (such as using the protocol architecture B shown in Figure 9 or Figure 10 above) .

Exemplarily, the PDCP entity may also indicate the data amount of data associated with multiple RLC entities (for example, the first RLC entity and the second RLC entity) in a total data amount (such as the third data amount). to the MAC entity. What the PDCP entity indicates to the MAC entity is a total data amount, not multiple data amounts corresponding to multiple RLC entities. When the PDCP entity indicates the amount of data to the MAC entity, it may not differentiate the data, or it may be described as not distinguishing the RLC entity. It should be noted that the number of RLC entities associated with the PDCP entity may be greater than or equal to the RLC entities associated with the data set (for example, the first data set and the second data set) corresponding to the third data amount (for example, the first RLC The number of entities and second RLC entities) is not limited by this application.

For example, taking the PDCP entity associating the first RLC entity and the second RLC entity as an example, the PDCP entity submits the first data set to the first RLC entity and the second data set to the second RLC entity. The PDCP entity may indicate the third amount of data to the MAC entity. It should be noted that the PDCP entity may also be associated with other RLC entities, which is not limited by this application.

For example, the MAC entity is associated with a first RLC entity and/or a second RLC entity.

The third data amount may include the data amount of the first data set and the data amount of the second data set. The description of the first data set and the second data set may refer to the related description of the first data set and the second data set in the above-mentioned FIG. 12 and will not be described again.

In another example, taking the PDCP entity associating the first RLC entity, the second RLC entity and the third RLC entity as an example, the PDCP entity submits the first data set to the first RLC entity and submits the second data set to the second RLC entity. , submit the third data set to the third RLC entity. The PDCP entity may indicate the third amount of data to the MAC entity.

For example, the MAC entity is associated with one or more of a first RLC entity, a second RLC entity, or a third RLC entity.

The third data amount may include the data amount of the first data set, the data amount of the second data set, and the data amount of the third data set. For descriptions of the first data set, the second data set, and the third data set, reference may be made to the related descriptions of the first data set, the second data set, and the third data set in the above-mentioned FIG. 12 and will not be described again.

Optionally, taking the PDCP entity associating the first RLC entity and the second RLC entity as an example, the first data set associated with the first RLC entity Includes part or all of the second data of one or more data groups. Optionally, the second data set associated with the second RLC entity includes part or all of the first data of one or more data groups. Optionally, the data group includes first data and one or more second data.

For example, assuming that the data group is a GOP, the first data is an I frame, and the second data is a P frame, the first data set may include part or all of the P frames in one or more GOPs, and the second data set may include Includes some or all I-frames in one or more GOPs. The PDCP entity delivers an I frame to the second RLC entity and a P frame to the first RLC entity, and includes the data amount of the I frame and the data amount of the P frame in a total data amount (such as a third data amount) and indicates it to the MAC. entity.

Optionally, the priority of the first data is higher than the priority of the second data.

Optionally, the third data amount also includes the data amount of the control PDU set.

For example, since the PDCP entity does not distinguish between RLC entities when indicating the data amount to the MAC entity, the third data amount may include the data amount of the control PDU set no matter which RLC entity submits the control PDU set.

Optionally, if the granularity of the BSR report by the MAC entity includes the third data amount corresponding to the LCH, the PDCP entity of the terminal device uses the method shown in Figure 13 to indicate the third data amount to the MAC entity.

The LCH corresponding to the third data amount may include the LCH corresponding to the first RLC entity and the LCH corresponding to the second RLC entity.

For example, the granularity reported by the BSR is based on the logical channel group (LCG), that is, the cache status of the LCG is reported.

For example, if the granularity of the BSR report by the MAC entity is LCG, and a certain LCG includes the LCH corresponding to the third amount of data (for example, the LCH corresponding to the first RLC entity and the LCH corresponding to the second RLC entity), the PDCP entity of the terminal device uses the figure The method shown in 13 indicates the third data amount to the MAC entity. It should be noted that the method does not limit whether the PDCP entity also indicates other data amounts to the MAC entity.

Based on the method shown in Figure 13 above, the way in which the PDCP entity indicates the amount of data to the MAC entity is modified. If the PDCP entity submits the first data set to the first RLC entity and the second data set to the second RLC entity, the PDCP The entity may indicate a total data amount, such as a third data amount, to the MAC entity. When the PDCP entity indicates the data amount to the MAC entity, the data may not be differentiated (or it may be described as not distinguishing the RLC entity), which is conducive to simplified indication of the data amount. The MAC entity can determine the BSR based on the amount of data indicated by the PDCP entity, which is conducive to accurate reporting of the BSR and thus saves resources.

What is different from the PDCP entity submitting different data to different RLC entities in Figures 12 and 13 above is that the PDCP entity can submit different data to different RLC entities, and can also submit different data to the same RLC entity (as shown in Figure 12). (a data set, a second data set), for data volume indication, the PDCP entity may use the method shown in Figure 14 to indicate the data volume to the MAC entity.

Figure 14 is a data volume indication method provided by an embodiment of the present application. This method can be applied to terminal devices. The method can include:

Step 1401: The PDCP entity indicates the first data amount to the MAC entity.

Step 1402: The PDCP entity indicates the third data amount to the MAC entity.

For example, the PDCP entity indicating the first data amount to the MAC entity includes: the PDCP entity indicating the first data amount to the MAC entity associated with the first RLC entity.

For example, the PDCP entity indicating the third data amount to the MAC entity includes: the PDCP entity indicating the third data amount to the MAC entity associated with the second RLC entity.

For example, in the terminal device in Figure 14, the PDCP entity can be associated with multiple RLC entities, and the PDCP entity can submit different data to different RLC entities (such as using the protocol architecture B shown in Figure 9 or Figure 10 above) , you can also submit different data to the same RLC entity.

Exemplarily, the PDCP entity may also include the amount of data (eg, the first data set and the second data set) associated with a certain RLC entity (eg, the second RLC entity) in a certain amount of data (eg, the second RLC entity). The third data amount) indicates the MAC entity associated with the RLC entity.

For example, if the PDCP entity is associated with multiple RLC entities, the PDCP entity may indicate multiple data amounts to the MAC entity. The number of data amounts indicated by the PDCP entity to the MAC entity may be less than or equal to the number of RLC entities associated with the PDCP entity, and is not limited by this application.

For example, taking the PDCP entity associating the first RLC entity and the second RLC entity as an example, the PDCP entity submits the first data set to the first RLC entity and the second data set to the second RLC entity. The PDCP entity also submits the second data set to the second RLC entity. Submit the first data set. The PDCP entity may indicate the first data amount to the MAC entity associated with the first RLC entity, and indicate the third data amount to the MAC entity associated with the second RLC entity.

Wherein, the first data amount may include the data amount of the first data set. The third data amount may include the data amount of the first data set and the data amount of the second data set.

For example, the MAC entity associated with the first RLC entity and the MAC entity associated with the second RLC entity may be the same MAC entity or different MAC entities.

For descriptions of the first data set and the second data set, reference may be made to the relevant descriptions of the first data set and the second data set in the above-mentioned FIGS. 12 and 13 , and will not be described again.

For example, a first data set is associated with a second RLC entity. For example, the first data set may be data that the PDCP entity may submit to the second RLC entity, or may be data that the PDCP entity is preparing to submit to the second RLC entity, or may be described as data that the PDCP entity will submit to the second RLC entity. Or described as data associated with the second RLC entity, which is not restricted. It should be noted that this does not limit that part or all of the first data set must be submitted to the second RLC entity.

Optionally, the first data set includes part or all of the second data of one or more data groups. Optionally, the second data set includes part or all of the first data of one or more data groups. Optionally, the data group includes first data and one or more second data.

For example, during the data submission process, the PDCP entity may submit the first data of the data group to the second RLC entity and the second data of the data group to the first RLC entity. Taking the data group including the first data group and the second data group as an example, assuming that the priority of the first data is higher than the priority of the second data, the PDCP entity can preferentially submit the first data of the first data group to the second RLC entity. , and then submits the second data of the first data group to the first RLC entity. If the second data submission of the first data group is completed or the delivery is terminated and the second data group arrives, the PDCP entity may submit the first data of the second data group to the second RLC entity, and then submit the second data group to the first RLC entity the second data. However, if the second data of the first data group has not yet been delivered or the delivery has been terminated, and the second data group has arrived, the PDCP entity can first submit the second data of the first data group to the second RLC entity, and then to the second RLC entity. Submit the first data of the second data group to prevent the PDCP entity from submitting the first data of the second data group to the second RLC entity first, causing the second data of the first data group to fail to be transmitted or to be delayed in transmission.

For example, assuming that the data group is a GOP, the first data is an I frame, and the second data is a P frame, the PDCP entity may first submit the I frame of the first GOP to the second RLC entity, and then submit it to the first RLC entity. P frame of the first GOP. If the delivery of the P frame of the first GOP is completed or the delivery is terminated and the second GOP arrives, the PDCP entity can deliver the I frame of the second GOP to the second RLC entity, and then deliver the P frame of the second GOP to the first RLC entity. However, if the delivery of the P frame of the first GOP has not been completed or the delivery is terminated, and the second GOP has arrived, the PDCP entity can first submit the P frame of the first GOP to the second RLC entity, and then submit the P frame of the second GOP to the second RLC entity. I frame.

Based on this, after the PDCP entity submits the first data of the data group to the second RLC entity, the PDCP entity may also submit the second data of the data group to the second RLC entity. Therefore, the PDCP entity submits the second data of the data group to the second RLC entity. When the MAC entity indicates the data amount, it indicates the third data amount including the data amount of the first data set and the data amount of the second data set. Since the PDCP entity submits the second data of the data group to the first RLC entity, when the PDCP entity indicates the data amount to the MAC entity corresponding to the first RLC entity, it indicates the first data amount including the data amount of the first data set. The amount of data.

Optionally, the priority of the first data is higher than the priority of the second data.

Optionally, the first data amount also includes the data amount of the control PDU set; and/or the third data amount also includes the data amount of the control PDU set.

Among them, the PDCP entity can determine which RLC entity is used to submit the control PDU set according to preconfiguration or predefinition or protocol regulations or base station configuration. If the control PDU set is delivered through the first RLC entity, the first data amount also includes the data amount of the control PDU set. If the control PDU set is delivered through the second RLC entity, the third data amount also includes the data amount of the control PDU set. If the control PDU set is submitted through the first RLC entity and/or the second RLC entity, both the first data amount and the third data amount include the data amount of the control PDU set.

Optionally, the method may also include step 1403: the PDCP entity obtains the first data amount. For example, step 1403 may precede step 1401.

Optionally, the method may also include step 1404: the PDCP entity obtains a third amount of data. For example, step 1404 may precede step 1402.

It should be noted that step 1401, or step 1403 and step 1401 can be used as independent embodiments and do not depend on step 1402. Step 1402, or step 1404 and step 1402 can be used as independent embodiments and do not depend on step 1401.

Based on the method shown in Figure 14 above, the way in which the PDCP entity indicates the amount of data to the MAC entity is modified. If the PDCP entity submits the first data set to the first RLC entity, the PDCP entity can send a request to the MAC entity associated with the first RLC entity. indicates first data quantity. If the PDCP entity submits the second data set to the second RLC entity, the PDCP entity may also submit the first data set to the second RLC entity, and the PDCP entity may indicate the third data amount to the MAC entity associated with the second RLC entity. The PDCP entity can differentiate the data (or describe it as differentiating RLC entities) when indicating the data amount to the MAC entity. Different data (or describe it as data associated with different RLC entities) can be indicated to the MAC through different data amounts. entity. The MAC entity can determine the BSR based on the amount of data indicated by the PDCP entity, which is conducive to accurate reporting of the BSR and thus saves resources.

Corresponding to the data amount indication method shown in the above-mentioned Figures 12 to 14, the following Figures 15 to 18 describe the specific process of data submission.

Figure 15 is a data submission method provided by an embodiment of the present application. The method is applied to a terminal device. The method may include:

Step 1501: The PDCP entity obtains the first data of the second data group.

In this embodiment of the present application, the PDCP entity obtaining the first data of the second data group may include the PDCP entity obtaining the second data group.

For example, in the terminal device in Figure 15, the PDCP entity can be associated with multiple RLC entities, and the PDCP entity can submit different data to different RLC entities, such as using the protocol architecture B shown in Figure 9 or Figure 10.

For example, taking the PDCP entity associating the first RLC entity and the second RLC entity as an example, the PDCP entity submits second data to the first RLC entity and submits first data to the second RLC entity.

For example, the first data is associated with the second RLC entity. The first data may be data that the PDCP entity may submit to the second RLC entity, or may be data that the PDCP entity is preparing to submit to the second RLC entity, or may be described as data that the PDCP entity will submit to the second RLC entity, or may be described as The data associated with the second RLC entity is not restricted. It should be noted that this does not limit that part or all of the first data must be submitted to the second RLC entity.

For example, the second data is associated with the first RLC entity. The second data may be data that the PDCP entity may submit to the first RLC entity, or may be data that the PDCP entity is preparing to submit to the first RLC entity, or may be described as data that the PDCP entity will submit to the first RLC entity, or may be described as The data associated with the first RLC entity is not restricted. It should be noted that this does not limit that part or all of the second data must be submitted to the first RLC entity.

For example, the PDCP entity may obtain a first data group from the SDAP entity, and the first data group may include first data and one or more second data.

It should be noted that the first data and the second data may be different types of data. The first data in different data groups may be different data. The second data in different data groups can also be different data. Multiple first data in the same data group may also be different data. Multiple second data in the same data group may also be different data. The first data and the second data are only used to distinguish different data and do not refer to a specific data.

Optionally, after the PDCP entity obtains the first data group, it can distinguish the first data and the second data according to the QFI or eQI associated with the data, submit the first data to the second RLC entity, and submit the second data to the first RLC entity. .

For example, the PDCP entity may also obtain a second data group from the SDAP entity, and the second data group may include the first data and one or more second data.

Optionally, after obtaining the second data group, the PDCP entity can distinguish the first data and the second data according to the QFI or eQI associated with the data, submit the first data to the second RLC entity, and submit the second data to the first RLC entity. .

Optionally, the first data group and the second data group are data groups of the same service.

Optionally, the priority of the first data is higher than the priority of the second data.

For example, if the priority of the first data is higher than the priority of the second data, the PDCP entity may perform the following step 1502 to prevent the PDCP entity from preferentially submitting the first data of the second data group to the second RLC entity, resulting in the first The second data of the data group cannot be transmitted or is delayed.

Step 1502: If the submission of the second data of the first data group is completed or the delivery is terminated, the PDCP entity submits the first data of the second data group to the second RLC entity.

Wherein, if the second data submission of the first data group is completed or the delivery is terminated, the PDCP entity can submit the first data of the second data group to the second RLC entity, but if the second data of the first data group is not submitted or is submitted To terminate, the PDCP entity needs to wait for the second data submission of the first data group to be completed or the delivery to be terminated, and then submit the first data of the second data group to the second RLC entity.

It should be noted that the submission termination may refer to the termination before data submission has started, or it may refer to the data submission having already started and a part of the data has been completed, and the remaining unsubmitted data shall be terminated.

Optionally, if the second data of the first data group is delivered to the MAC entity by the first RLC entity, it may be considered that the delivery of the second data of the first data group is completed. Or it can also be described as if the second data of the first data group is submitted by the first RLC entity, it can be considered that the first The second data submission of the data group is completed.

Optionally, if the delivery of the second data of the first data group is terminated by the PDCP entity and/or the first RLC entity, it is considered that the delivery of the second data of the first data group is terminated.

For example, if the packet loss rate of the first data of the first data group is greater than or equal to a certain threshold, it may be considered that there is no need to continue transmitting the second data of the first data group, and the PDCP entity and/or the first RLC entity may terminate the second data. Submission of second data of a data set.

For example, assuming that the data group is a GOP, the first data is an I frame, and the second data is a P frame, the PDCP entity submits the I frame of the first GOP to the second RLC entity and the first GOP to the first RLC entity. P frame, if the delivery of the P frame of the first GOP is completed or the delivery is terminated, the PDCP entity can continue to submit the I frame of the second GOP to the second RLC entity, and submit the P frame of the second GOP to the first RLC entity.

In a possible design, the PDCP entity sends a first request to the first RLC entity, the first RLC entity sends a first response to the PDCP entity according to the first request, and the PDCP entity determines the second data of the first data group according to the first response. Whether the submission is completed or the submission is terminated.

The first request may be used to request information about whether the second data of the first data group has been submitted or terminated; or it may be used to request information about whether the buffer of the first RLC entity is empty.

In this embodiment of the present application, whether the submission of the second data of the first data group is completed or the submission is terminated may include the submission status of the second data of the first data group.

For example, the buffer of the first RLC entity may include a transmission buffer and/or a retransmission buffer of the first RLC entity.

In this embodiment of the present application, the request may include any one or more of query, polling, and determination.

The first response may be used to indicate whether the delivery of the second data of the first data group is completed or terminated, or to indicate whether the buffer of the first RLC entity is empty.

For example, if the first RLC entity determines that the second data submission of the first data group is completed or the delivery is terminated, the first response is used to indicate that the second data submission of the first data group is completed or the delivery is terminated or is used to indicate that the first RLC entity buffer is empty. If the first RLC entity determines that the delivery of the second data of the first data group is not completed or the delivery is terminated, the first response is used to indicate that the second data of the first data group is not delivered completed or the delivery is terminated or is used to indicate that the first RLC entity buffer is not empty.

Optionally, the PDCP entity sends the first request to the first RLC entity before submitting the first data of the second data group to the second RLC entity, so as to avoid frequently sending the first request and reduce power consumption.

Optionally, the PDCP entity obtains the second data group from the SDAP entity and sends the first request to the first RLC entity to avoid frequently sending the first request and reduce power consumption.

In another possible design, the PDCP entity receives the first indication information from the first RLC entity.

The first indication information may be used to indicate that the second data submission of the first data group is completed or the delivery is terminated or to indicate that the buffer of the first RLC entity is empty.

For example, if the first RLC entity determines that the second data submission of the first data group is completed or terminated or the buffer of the first RLC entity is empty, the first RLC entity may actively report the first indication information to the PDCP entity to facilitate PDCP The entity determines that the second data submission of the first data group is completed or terminated or the buffer of the first RLC entity is empty according to the first indication information, and then submits the first data of the second data group to the second RLC entity.

In the embodiment of this application, reporting can be described as an instruction.

In another possible design, the first RLC entity may also periodically report to the PDCP entity indication information of whether the second data of the first data group has been submitted or terminated, or indication information of whether the buffer of the first RLC entity is empty. It is convenient for the PDCP entity to determine whether the delivery of the second data of the first data group is completed or the delivery is terminated based on the indication information.

The reporting period may be preconfigured or predefined, or specified by the base station configuration or protocol, and is not limited.

Based on the method shown in Figure 15 above, the limiting conditions for the PDCP entity to submit data to the RLC entity are added. Taking the priority of the first data as higher than the priority of the second data as an example, if the PDCP entity determines that the first data group has When the second data submission is completed or the submission is terminated, the PDCP entity can submit the first data of the second data group to the second RLC entity to prevent the PDCP entity from submitting the first data of the second data group to the second RLC entity, causing the first data group to The second data cannot be transmitted or the transmission is delayed.

It should be noted that the method shown in FIG. 15 can be implemented alone or in combination with the method shown in FIG. 12 or 13 without limitation.

Different from the PDCP entity delivering different data to different RLC entities in Figure 15 above, as shown in Figure 16, the PDCP entity can deliver different data to different RLC entities, and can also deliver different data (for example, The first data and the second data) are submitted to the same RLC entity.

Figure 16 is a data submission method provided by an embodiment of the present application. The method is applied to a terminal device. The method may include:

Step 1601: The PDCP entity obtains the second data of the first data group.

For example, in the terminal device in Figure 16, the PDCP entity can be associated with multiple RLC entities, and the PDCP entity can submit different data to different RLC entities, such as using the protocol architecture B shown in Figure 9 or Figure 10 above.

For example, taking the PDCP entity associating the first RLC entity and the second RLC entity as an example, the PDCP entity submits second data to the first RLC entity and submits first data to the second RLC entity.

For the description of the first data and the second data, reference may be made to the description of the first data and the second data in the above-mentioned FIG. 15 , and no further description will be given.

For example, the PDCP entity may obtain a first data group from the SDAP entity, and the first data group may include first data and one or more second data.

Optionally, after the PDCP entity obtains the first data group, it can distinguish the first data and the second data according to the QFI or eQI associated with the data, submit the first data to the second RLC entity, and submit the second data to the first RLC entity. .

For example, the PDCP entity may also obtain a second data group from the SDAP entity, and the second data group may include the first data and one or more second data.

Optionally, after obtaining the second data group, the PDCP entity can distinguish the first data and the second data according to the QFI or eQI associated with the data, submit the first data to the second RLC entity, and submit the second data to the first RLC entity. .

Optionally, the first data group and the second data group are data groups of the same service.

Optionally, the priority of the first data is higher than the priority of the second data.

For example, if the priority of the first data is higher than the priority of the second data, the PDCP entity may perform the following step 1602 to prevent the PDCP entity from preferentially submitting the first data of the second data group to the second RLC entity, resulting in the first The second data of the data group cannot be transmitted or is delayed.

Step 1602: If the first condition is met, the PDCP entity submits the second data of the first data group to the second RLC entity.

For example, the first condition may include that the PDCP entity obtains the first data of the second data group. For example, the PDCP entity obtaining the first data of the second data group may include the PDCP entity obtaining the second data group.

In yet another example, the first condition may include the PDCP entity determining to submit the first data of the second data group to the second RLC entity. For example, the PDCP entity determines or will deliver the first data of the second data group to the second RLC entity, which may include: the PDCP entity will deliver the first data of the second data group to the second RLC entity.

For example, if the PDCP entity obtains lower layer indication information indicating that uplink resources have been obtained, the PDCP entity may determine to submit the first data of the second data group to the second RLC entity.

For example, during the data submission process, the PDCP entity may submit the first data of the first data group to the second RLC entity and the second data of the first data group to the first RLC entity. Alternatively, it can also be described as, if the first condition is not met, the PDCP entity can submit the second data of the first data group to the first RLC entity.

If the second data submission of the first data group is completed or the delivery is terminated, the PDCP entity obtains the first data of the second data group or determines to submit the first data of the second data group to the second RLC entity, the PDCP entity may The RLC entity submits the first data of the second data group and submits the second data of the second data group to the first RLC entity.

However, if the delivery of the second data of the first data group has not been completed or the delivery is terminated, the PDCP entity obtains the first data of the second data group or determines to submit the first data of the second data group to the second RLC entity. The PDCP entity The second data of the first data set may be delivered to the second RLC entity, and then the first data of the second data set may be delivered to the second RLC entity. This prevents the PDCP entity from submitting the first data of the second data group to the second RLC entity first, causing the second data of the first data group to fail to be transmitted or to be transmitted delayed.

For example, assuming that the data group is a GOP, the first data is an I frame, and the second data is a P frame, the PDCP entity may submit the I frame of the first GOP to the second RLC entity and the first RLC entity to the first RLC entity. GOP P frame. If the delivery of the P frame of the first GOP is completed or the delivery is terminated, the PDCP entity obtains the I frame of the second GOP or determines to submit the I frame of the second GOP to the second RLC entity, the PDCP entity can submit the second GOP to the second RLC entity The I frame of the second GOP is submitted to the first RLC entity. However, if the delivery of the P frame of the first GOP has not been completed or the delivery is terminated, the PDCP entity obtains the I frame of the second GOP or determines to submit the I frame of the second GOP to the second RLC entity. The PDCP entity can The P frame of the first GOP is delivered, and then the I frame of the second GOP is delivered to the second RLC entity.

In a possible design, before the PDCP entity obtains the first data of the second data group or determines to submit the first data of the second data group to the second RLC entity, if the second data of the first data group is obtained by the first The RLC entity submits to the MAC entity that the first data group The second data submission is completed. Or it can also be described as if the second data of the first data group is submitted to the first RLC entity or the buffer of the first RLC entity is empty, it is considered that the second data of the first data group is submitted to be completed.

In another possible design, after the PDCP entity obtains the first data of the second data group or determines to submit the first data of the second data group to the second RLC entity, if the second data of the first data group is in the PDCP entity and/or the first RLC entity's submission is terminated, or the buffer of the PDCP entity and/or the first RLC entity is empty, it is considered that the second data submission of the first data group is terminated.

For example, if the packet loss rate of the first data of the first data group is greater than or equal to a certain threshold, it may be considered that there is no need to continue transmitting the second data of the first data group, and the PDCP entity and/or the first RLC entity may terminate the second data. Submission of second data of a data set.

In another possible design, the PDCP entity obtains the first data of the second data group or determines to submit the first data of the second data group to the second RLC entity. If the second data of the first data group has not yet been submitted or When the submission is terminated, the PDCP entity may submit the second data of the first data group to the second RLC entity. If the second data of the first data group is delivered to the MAC entity by the second RLC entity, it is considered that the delivery of the second data of the first data group is completed. Or it can also be described as if the second data of the first data group is submitted to the second RLC entity, or the buffer of the PDCP entity and/or the second RLC entity is empty, it is considered that the second data of the first data group is submitted to be completed.

In another possible design, the PDCP entity obtains the first data of the second data group or determines to submit the first data of the second data group to the second RLC entity. If the second data of the first data group has not yet been submitted or When the submission is terminated, the PDCP entity may submit the second data of the first data group to the second RLC entity. If the delivery of the second data of the first data group is terminated by the PDCP entity and/or the second RLC entity, or the buffer of the PDCP entity and/or the second RLC entity is empty, it is considered that the delivery of the second data of the first data group is terminated.

In the above four possible designs, the PDCP entity may send a request to the first RLC entity to determine whether the second data of the first data group is submitted to the first RLC entity or terminated based on the response sent by the first RLC entity. Or, according to the indication information sent by the first RLC entity when or after the second data of the first data group is completed or terminated by the first RLC entity, it is determined that the second data of the first data group is completed by the first RLC entity. Or submit a termination. Alternatively, determine whether the second data of the first data group is in the first RLC entity based on the indication information periodically reported by the first RLC entity to indicate whether the second data of the first data group is submitted to the first RLC entity or terminated. RLC entity submission is completed or submission is terminated.

Optionally, the second data of the first data group submitted by the PDCP entity to the second RLC entity may include: data in the second data of the first data group that has not been submitted by the first RLC entity.

The data in the second data of the first data group that is not submitted by the first RLC entity may include one or more of the following: the data in the second data of the first data group that is not submitted by the PDCP entity to the first RLC entity , data in the second data of the first data group that has been submitted to the first RLC entity by the PDCP entity but has not been submitted by the first RLC entity.

For example, the data in the second data of the first data group that has not been submitted to the first RLC entity by the PDCP entity includes: the data in the second data of the first data group that has not been submitted to the first RLC entity by the PDCP entity and exists in the PDCP buffer data in.

For example, "data in the second data of the first data group that has been submitted to the first RLC entity by the PDCP entity but has not been submitted by the first RLC entity" includes: data in the second data of the first data group that has been submitted to the first RLC entity by the PDCP entity Data that is not submitted by the first RLC entity and exists in the buffer of the first RLC entity.

Optionally, before the PDCP entity submits the second data of the first data group to the second RLC entity, the PDCP entity may also perform one or more of the following:

①The PDCP entity sends the second indication information to the first RLC entity.

For example, the second indication information may be used to indicate the arrival of the first data of the second data group or to instruct the PDCP entity to determine to deliver the first data of the second data group to the second RLC entity.

For example, if the PDCP entity receives the first data of the second data group submitted by the SDAP entity, the PDCP entity may send second indication information to the first RLC entity to indicate the arrival of the first data of the second data group.

Optionally, the first RLC entity may send response information to the PDCP entity according to the second indication information to indicate whether the delivery of the second data of the first data group is completed or the delivery is terminated. If the delivery of the second data of the first data group is completed, Or the submission is terminated, and the PDCP entity may submit the first data of the second data group to the second RLC entity. If the delivery of the second data of the first data group has not been completed or the delivery has been terminated, the PDCP entity may deliver the second data of the first data group to the second RLC entity, so that the second RLC entity preferentially transmits the second data of the first data group. data, and then transmits the first data of the second data group.

Optionally, the first RLC entity may feedback a delivery status report of the second data of the first data group to the PDCP entity according to the second indication information. The delivery status report of the second data of the first data group may include the PDCP sequence number (SN) of the data that has not been delivered by the first RLC entity in the second data of the first data group. The PDCP entity can determine the first number based on the submission status report According to which data in the second data of the first data group has not been submitted, the undelivered data in the second data of the first data group is submitted to the second RLC entity, so that the second RLC entity preferentially transmits the second data of the first data group. data, and then transmits the first data of the second data group.

Optionally, the delivery status report of the second data of the first data group may also include response information indicating whether the delivery of the second data of the first data group is completed or terminated.

Optionally, the first RLC entity may also delete the second data of the first data group according to the second indication information. Or it may be described as the first RLC entity clearing the buffer of the first RLC entity according to the second indication information.

②The PDCP entity sends the third indication information to the first RLC entity.

The third instruction information is used to instruct the first RLC entity to feed back the delivery status report of the second data of the first data group. The description of the delivery status report of the second data of the first data group may refer to the foregoing relevant descriptions. Repeat.

③The PDCP entity sends fourth indication information to the first RLC entity.

The fourth instruction information is used to instruct the first RLC entity to delete the second data of the first data group, or is described as the fourth instruction information is used to instruct the first RLC entity to clear the buffer of the first RLC entity.

Any two or more items of the second indication information, the third indication information, and the fourth indication information may be the same indication information, or they may be different indication information, without limitation.

Based on the method shown in Figure 16 above, the limiting conditions for the PDCP entity to submit data to the RLC entity are added. Taking the priority of the first data as higher than the priority of the second data as an example, if the second data of the first data group has not yet been When the submission is completed or the submission is terminated, the PDCP entity obtains the first data of the second data group or determines to submit the first data of the second data group to the second RLC entity. The PDCP entity can submit the first data of the first data group to the second RLC entity. the second data, and then submits the first data of the second data group to the second RLC entity. This prevents the PDCP entity from preferentially submitting the first data of the second data group to the second RLC entity, resulting in failure or delayed transmission of the second data of the first data group.

It should be noted that the method shown in FIG. 16 can be implemented alone or in combination with the method shown in FIG. 14 without limitation.

Different from the above-mentioned Figures 15 and 16 where SDAP delivers different data to the same PDCP entity, as shown in Figure 17, the SDAP entity can also deliver different data (for example, first data, second data) to different PDCP entity.

Figure 17 is a data submission method provided by an embodiment of the present application. The method is applied to a terminal device. The method may include:

Step 1701: The SDAP entity obtains the first data of the second data group.

For example, in the terminal device of Figure 17, the SDAP entity can be associated with multiple PDCP entities, and the SDAP entity can submit different data to different PDCP entities, such as using the protocol architecture A shown in Figure 7 or Figure 8 above.

It should be noted that when the SDAP entity submits data to the PDCP entity, the submission may be executed, or the submission may be terminated due to some reasons. Therefore, the data submitted by the SDAP entity to the PDCP entity can also be described as: SDAP entity submits to PDCP The data of the entity is either described as data that the SDAP entity is preparing to submit to the PDCP entity, or is described as data that the SDAP entity will submit to the PDCP entity, or is described as data that SDAP may submit to the PDCP entity, or is described as data associated with the PDCP entity , not restricted.

For example, assuming that the SDAP entity is associated with the first PDCP entity and the second PDCP entity, the first PDCP entity is associated with the first RLC entity, and the second PDCP entity is associated with the second RLC entity, the SDAP entity submits the second data to the first PDCP entity, Submit the first data to the second PDCP entity; the first PDCP entity submits the second data to the first RLC entity, and the second PDCP entity submits the first data to the second RLC entity.

For example, the first data is associated with the second PDCP entity. The first data may be data that the SDAP entity may submit to the second PDCP entity, or may be data that the SDAP entity is preparing to submit to the second PDCP entity, or may be described as data that the SDAP entity will submit to the second PDCP entity, or may be described as The data associated with the second PDCP entity is not restricted. It should be noted that this does not limit that part or all of the first data must be submitted to the second PDCP entity.

For example, the second data is associated with the first PDCP entity. The second data may be data that the SDAP entity may submit to the first PDCP entity, or may be data that the SDAP entity is preparing to submit to the first PDCP entity, or may be described as data that the SDAP entity will submit to the first PDCP entity, or may be described as The data associated with the first PDCP entity is not restricted. It should be noted that this does not limit that part or all of the second data must be submitted to the first PDCP entity.

For example, the SDAP entity may obtain a first data group from the application layer, and the first data group may include first data and one or more second data.

Optionally, after the SDAP entity obtains the first data group, it can distinguish the first data and the second data according to the QFI or eQI associated with the data, submit the first data to the second PDCP entity, and submit the second data to the first PDCP entity. .

For example, the SDAP entity may also obtain a second data group from the application layer, and the second data group may include the first data and one or more second data.

Optionally, after the SDAP entity obtains the second data group, it can distinguish the first data and the second data according to the QFI or eQI associated with the data, submit the first data to the second PDCP entity, and submit the second data to the first PDCP entity. .

Optionally, the first data group and the second data group are data groups of the same service.

Optionally, the priority of the first data is higher than the priority of the second data.

For example, if the priority of the first data is higher than the priority of the second data, the SDAP entity may perform the following step 1702 to prevent the SDAP entity from submitting the first data of the second data group to the second PDCP entity, causing the first data to be The second data of the group cannot be transmitted or is delayed.

Step 1702: If the second data submission of the first data group is completed or the delivery is terminated, the SDAP entity submits the first data of the second data group to the second PDCP entity.

For example, if the delivery of the second data of the first data group is completed or the delivery is terminated, the SDAP entity may deliver the first data of the second data group to the second PDCP entity, but if the second data of the first data group is not delivered completed or delivered To terminate, the SDAP entity needs to wait for the second data submission of the first data group to be completed or the delivery to be terminated, and then submit the first data of the second data group to the second PDCP entity.

Optionally, if the second data of the first data group is delivered to the MAC entity by the first RLC entity, it is considered that the delivery of the second data of the first data group is completed. Or it can also be described as if the delivery of the second data of the first data group is completed at the first RLC entity, it is considered that the delivery of the second data of the first data group is completed.

Wherein, the first RLC entity is an RLC entity associated with the first PDCP entity.

Optionally, if the delivery of the second data of the first data group is terminated by one or more of the following entities, it is considered that the delivery of the second data of the first data group is terminated: the SDAP entity, the first PDCP entity, or the first RLC entity.

Wherein, if the packet loss rate of the first data of the first data group is greater than or equal to a certain threshold, it can be considered that there is no need to continue transmitting the second data of the first data group. The SDAP entity, and/or the first PDCP entity, and /Or the first RLC entity may terminate the submission of the second data of the first data group.

For example, assuming that the data group is a GOP, the first data is an I frame, and the second data is a P frame, the SDAP entity can submit the I frame of the first GOP to the second PDCP entity and the first PDCP entity. For the P frame of the GOP, if the delivery of the P frame of the first GOP is completed or terminated, the SDAP entity can continue to submit the I frame of the second GOP to the second PDCP entity and the P frame of the second GOP to the first PDCP entity.

In a possible design, the SDAP entity sends a second request to the first PDCP entity, the first PDCP entity sends a second response to the SDAP entity according to the second request, and the SDAP entity determines the second data of the first data group according to the second response. Whether the submission is completed or the submission is terminated.

The second request may be used to request information on whether the second data of the first data group has been submitted or terminated; or, it may be used to request whether the buffer of the first PDCP entity and/or the buffer of the first RLC entity is empty. information.

The second response may be used to indicate whether the delivery of the second data of the first data group is completed or terminated; or, to indicate whether the buffer of the first PDCP entity and/or the buffer of the first RLC entity is empty.

For example, if the first PDCP entity determines that the second data delivery of the first data group is completed or the delivery is terminated, the second response may be used to indicate that the second data delivery of the first data group is completed or the delivery is terminated or to indicate to the first PDCP entity The buffer and/or the buffer of the first RLC entity is empty; if the first PDCP entity determines that the delivery of the second data of the first data group is not completed or the delivery is terminated, the second response may be used to indicate the second data of the first data group. No delivery is completed or delivery is terminated or the buffer used to indicate the first PDCP entity and/or the buffer of the first RLC entity is not empty.

For a description of the first PDCP entity determining whether the delivery of the second data of the first data group is completed or the delivery is terminated, reference may be made to the correlation of the PDCP entity determining whether the submission of the second data of the first data group is completed or the delivery is terminated in step 1502. Description without going into details.

Optionally, the SDAP entity sends the second request to the first PDCP entity before submitting the first data of the second data group to the second PDCP entity, so as to avoid frequently sending the second request and reduce power consumption.

Optionally, the SDAP entity obtains the second data group from the application layer and sends the second request to the first PDCP entity to avoid frequently sending the second request and reduce power consumption.

In another possible design, the SDAP entity sends a third request to the first RLC entity, the first RLC entity sends a third response to the SDAP entity according to the third request, and the SDAP entity determines the second element of the first data group according to the third response. Whether the data submission is completed or the submission is terminated.

The third request may be used to request information on whether the submission of the second data of the first data group is completed or terminated; or, used to request Information about whether the buffer of the first RLC entity is empty.

The third response may be used to indicate whether the delivery of the second data of the first data group is completed or terminated, or to indicate whether the buffer of the first RLC entity is empty.

If the first RLC entity determines that the second data submission of the first data group is completed or the delivery is terminated, the third response may be used to indicate that the second data submission of the first data group is completed or the delivery is terminated or used to indicate the buffer of the first RLC entity Is empty. If the first RLC entity determines that the delivery of the second data of the first data group is not completed or the delivery is terminated, the third response may be used to indicate that the second data of the first data group is not delivered or is terminated or is used to indicate to the first RLC entity The buffer is not empty.

Optionally, the SDAP entity sends the third request to the first RLC entity before submitting the first data of the second data group to the second PDCP entity, so as to avoid frequently sending the third request and reduce power consumption.

Optionally, the SDAP entity obtains the second data group from the application layer and sends the third request to the first RLC entity to avoid frequently sending the third request and reduce power consumption.

In another possible design, the SDAP entity receives fifth indication information from the first PDCP entity and/or the first RLC entity.

The fifth indication information may be used to indicate that the second data submission of the first data group is completed or the delivery is terminated or to indicate that the buffer of the first PDCP entity and/or the buffer of the first RLC entity is empty.

Specifically, if the first PDCP entity and/or the first RLC entity determines that the second data submission of the first data group is completed or the delivery is terminated or the buffer of the first PDCP entity and/or the buffer of the first RLC entity is empty, the first The PDCP entity or the first RLC entity may actively report the fifth indication information to the SDAP entity, so that the SDAP entity determines that the second data submission of the first data group is completed or the delivery is terminated based on the fifth indication information, and then submits the second data group to the second PDCP entity. The first data of the second data group.

In another possible design, the first PDCP entity and/or the first RLC entity may also periodically report to the SDAP entity indication information of whether the second data of the first data group is submitted or terminated or the buffer of the first PDCP entity. and/or indication information of whether the buffer of the first RLC entity is empty, so that the SDAP entity can determine whether the submission of the second data of the first data group is completed or terminated based on the indication information.

The reporting period may be preconfigured or predefined, or specified by the base station configuration or protocol, and is not limited.

Based on the method shown in Figure 17 above, the limiting conditions for the SDAP entity to submit data to the PDCP entity are added. Taking the priority of the first data as higher than the priority of the second data as an example, if the SDAP entity determines that the first data group has When the second data submission is completed or the submission is terminated, the SDAP entity can submit the first data of the second data group to the second PDCP entity to avoid the SDAP entity preferentially submitting the first data of the second data group to the second PDCP entity, resulting in the first data The second data of the group cannot be transmitted or is delayed.

Different from the above Figure 17, if the SDAP entity determines that the second data submission of the first data group is completed or the delivery is terminated, the SDAP entity can submit the first data of the second data group to the second PDCP entity, as shown in Figure 18, A restriction condition may be added for the second PDCP entity to submit data to the second RLC entity, instead of restricting the SDAP entity to submit data to the PDCP entity.

Figure 18 is a data indication method provided by an embodiment of the present application. The method is applied to a terminal device. The method may include:

Step 1801: The second PDCP entity obtains the first data of the second data group.

For example, in the terminal device in Figure 18, the SDAP entity can be associated with multiple PDCP entities, and the SDAP entity can submit different data to different PDCP entities, such as using the protocol architecture A shown in Figure 7 or Figure 8 above.

For example, assuming that the SDAP entity is associated with the first PDCP entity and the second PDCP entity, the first PDCP entity is associated with the first RLC entity, and the second PDCP entity is associated with the second RLC entity, the SDAP entity can submit the second data to the first PDCP entity. , submit the first data to the second PDCP entity; the first PDCP entity may submit the second data to the first RLC entity, and the second PDCP entity submits the first data to the second RLC entity.

For example, first data and second PDCP entity.

For example, the second data and the first PDCP entity.

For the description of the first data and the second data, reference may be made to the description of the first data and the second data in the above-mentioned FIG. 17 , and no further description will be given.

For example, the SDAP entity may obtain a first data group from the application layer, and the first data group may include first data and one or more second data.

Optionally, after the SDAP entity obtains the first data group, it can distinguish the first data and the second data according to the QFI or eQI associated with the data, submit the first data to the second PDCP entity, and submit the second data to the first PDCP entity. .

For example, the SDAP entity may also obtain a second data group from the application layer, and the second data group may include the first data and one or more second data.

Optionally, after the SDAP entity obtains the second data group, it can distinguish the first data and the second data according to the QFI or eQI associated with the data, submit the first data to the second PDCP entity, and submit the second data to the first PDCP entity. .

Optionally, the first data group and the second data group are data groups of the same service.

Optionally, the priority of the first data is higher than the priority of the second data.

For example, if the priority of the first data is higher than the priority of the second data, the second PDCP entity may perform the following step 1802 to prevent the second PDCP entity from preferentially submitting the first data of the second data group to the second RLC entity. , resulting in the failure or delayed transmission of the second data of the first data group.

Step 1802: If the second data submission of the first data group is completed or the delivery is terminated, the second PDCP entity submits the first data of the second data group to the second RLC entity.

Wherein, if the second data submission of the first data group is completed or the delivery is terminated, the second PDCP entity may submit the first data of the second data group to the second RLC entity, but if the second data submission of the first data group is not completed Or the delivery is terminated. The second PDCP entity needs to wait for the completion of the delivery of the second data of the first data group or the termination of delivery, and then submits the first data of the second data group to the second RLC entity.

Optionally, if the second data of the first data group is delivered to the MAC entity by the first RLC entity, it is considered that the delivery of the second data of the first data group is completed. Or it can also be described as if the delivery of the second data of the first data group is completed at the first RLC entity, it is considered that the delivery of the second data of the first data group is completed.

Optionally, if the delivery of the second data of the first data group is terminated by the first PDCP entity and/or the first RLC entity, it is considered that the delivery of the second data of the first data group is terminated.

Wherein, if the packet loss rate of the first data of the first data group is greater than or equal to a certain threshold, it may be considered that there is no need to continue transmitting the second data of the first data group, and the first PDCP entity and/or the first RLC entity may Terminate the submission of the second data of the first data group.

For example, assuming that the data group is a GOP, the first data is an I frame, and the second data is a P frame, the second PDCP entity can submit the I frame of the first GOP to the second RLC entity, and the first PDCP entity can submit the I frame of the first GOP to the second RLC entity. The first RLC entity submits the P frame of the first GOP. If the delivery of the P frame of the first GOP is completed or the delivery is terminated, the second PDCP entity can continue to submit the I frame of the second GOP to the second RLC entity. The first PDCP entity can continue Submit the P frame of the second GOP to the first RLC entity.

In a possible design, the second PDCP entity sends a fourth request to the SDAP entity, the SDAP entity sends a fourth response to the second PDCP entity according to the fourth request, and the second PDCP entity determines the first data group based on the fourth response. 2. Whether the data submission is completed or the submission is terminated.

The fourth request may be used to request information on whether the second data of the first data group has been submitted or terminated; or, it may be used to request whether the buffer of the first PDCP entity and/or the buffer of the first RLC entity is empty. information.

The fourth response may be used to indicate whether the delivery of the second data of the first data group is completed or terminated; or, to indicate whether the buffer of the first PDCP entity and/or the buffer of the first RLC entity is empty.

For example, if the SDAP entity determines that the second data submission of the first data group is completed or the delivery is terminated, the fourth response may be used to indicate that the second data submission of the first data group is completed or the delivery is terminated or used to indicate the buffer of the first PDCP entity and/or the buffer of the first RLC entity is empty; if the SDAP entity determines that the delivery of the second data of the first data group is not completed or the delivery is terminated, the fourth response may be used to indicate that the second data of the first data group is not delivered or is completed. The submission is terminated or used to indicate that the buffer of the first PDCP entity and/or the buffer of the first RLC entity is not empty.

For the description of the SDAP entity determining whether the submission of the second data of the first data group is completed or the delivery is terminated, reference may be made to the relevant description of the SDAP entity determining whether the submission of the second data of the first data group is completed or the submission is terminated in the above step 1702. No further details will be given.

Optionally, the second PDCP entity sends the fourth request to the SDAP entity before submitting the first data of the second data group to the second RLC entity, so as to avoid frequently sending the fourth request and reduce power consumption.

Optionally, the second PDCP entity obtains the second data group from the SDAP entity and sends a fourth request to the SDAP entity to avoid frequently sending the fourth request and reduce power consumption.

In another possible design, the second PDCP entity sends a fifth request to the first PDCP entity, the first PDCP entity sends a fifth response to the second PDCP entity according to the fifth request, and the second PDCP entity determines the fifth response based on the fifth response. Whether the submission of the second data of a data group is completed or the submission is terminated.

The fifth request may be used to request information on whether the second data of the first data group has been submitted or terminated; or, it may be used to request whether the buffer of the first PDCP entity and/or the buffer of the first RLC entity is empty. information.

The fifth response may be used to indicate whether the delivery of the second data of the first data group is completed or the delivery is terminated; or, it may be used to indicate whether the first PDCP actual Whether the buffer of the entity and/or the buffer of the first RLC entity is empty.

For example, if the first PDCP entity determines that the second data delivery of the first data group is completed or the delivery is terminated, the fifth response may be used to indicate that the second data delivery of the first data group is completed or the delivery is terminated or to indicate to the first PDCP entity The buffer and/or the buffer of the first RLC entity is empty; if the first PDCP entity determines that the delivery of the second data of the first data group is not completed or the delivery is terminated, the fifth response may be used to indicate the second data of the first data group. No delivery is completed or delivery is terminated or the buffer used to indicate the first PDCP entity and/or the buffer of the first RLC entity is not empty.

For a description of the first PDCP entity determining whether the delivery of the second data of the first data group is completed or the delivery is terminated, reference may be made to the correlation of the PDCP entity determining whether the submission of the second data of the first data group is completed or the delivery is terminated in step 1502. The description or related description of the first PDCP entity determining whether the delivery of the second data of the first data group is completed or the delivery is terminated in step 1702 will not be described again.

Optionally, the second PDCP entity sends the fifth request to the first PDCP entity before submitting the first data of the second data group to the second RLC entity, so as to avoid frequently sending the fifth request and reduce power consumption.

Optionally, the second PDCP entity obtains the second data group from the SDAP entity and sends the fifth request to the first PDCP entity to avoid frequently sending the fifth request and reduce power consumption.

In another possible design, the second PDCP entity receives sixth indication information from the SDAP entity or the first PDCP entity.

The sixth indication information may be used to indicate that the second data submission of the first data group is completed or the delivery is terminated or to indicate that the buffer of the first PDCP entity and/or the buffer of the first RLC entity is empty.

Specifically, if the SDAP entity and/or the first PDCP entity determines that the second data submission of the first data group is completed or the submission is terminated, the SDAP entity or the first PDCP entity may proactively report the sixth indication information to the second PDCP entity to facilitate the The second PDCP entity determines that the second data submission of the first data group is completed or the delivery is terminated according to the sixth instruction information, and then submits the first data of the second data group to the second RLC entity.

In another possible design, the SDAP entity and/or the first PDCP entity may also periodically report to the second PDCP entity the indication information of whether the second data of the first data group is submitted or terminated or the buffer of the first PDCP entity. and/or indication information of whether the buffer of the first RLC entity is empty, so that the second PDCP entity can determine whether the submission of the second data of the first data group is completed or terminated based on the indication information.

The reporting period may be preconfigured or predefined, or specified by the base station configuration or protocol, and is not limited.

Based on the method shown in Figure 18 above, the limiting conditions for the PDCP entity to submit data to the RLC entity are added. Taking the priority of the first data as higher than the priority of the second data as an example, if the second PDCP entity determines that the first data group When the second data submission is completed or the submission is terminated, the second PDCP entity may submit the first data of the second data group to the second RLC entity to prevent the second PDCP entity from preferentially submitting the first data of the second data group to the second RLC entity. data, resulting in the failure or delay in transmission of the second data of the first data group.

It should be noted that the above-mentioned methods shown in Figure 17 and Figure 18 can be implemented individually or in combination without limitation.

It should be understood that the existing technology may change with the evolution of technical solutions, and the technical solutions provided in this application are not limited to the existing technologies provided.

It should be noted that different embodiments or some steps (for example, any one or more steps) in different embodiments in this application can be combined with each other to form new embodiments. It should be noted that some steps in different embodiments are not limited or any one or more steps may include optional steps in a certain embodiment, or may include mandatory steps in a certain embodiment, or may include certain steps. The optional steps and required steps in each embodiment are not limited by this application.

It should be noted that, if there is no special explanation or logical conflict, the terms and/or descriptions between different embodiments are consistent and can be referenced to each other.

It should be noted that the order of the steps in the embodiments of this application is not limited by this application.

It should be noted that the order in which different conditions are judged in the embodiments of this application is not limited by this application.

It should be noted that "after" and "when" in this application do not strictly limit the time point.

The above mainly introduces the solution provided by the embodiments of the present application from the perspective of interaction between devices. It can be understood that, in order to implement the above functions, each device includes a corresponding hardware structure and/or software module to perform each function. Those skilled in the art should readily appreciate that the algorithm steps of each example described in conjunction with the embodiments disclosed herein, the present application can be implemented in the form of hardware or a combination of hardware and computer software. Whether a function is performed by hardware or computer software driving the hardware 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.

Embodiments of the present application can divide each device into functional modules according to the above method examples. For example, each functional module can be divided into corresponding functional modules, or two or more functions can be integrated into one processing module. The above integrated modules can be implemented in the form of hardware or software function modules. It should be noted that the division of modules in the embodiment of the present application is schematic and is only a logical function division. In actual implementation, there may be other division methods.

In the case where each functional module is divided corresponding to each function, FIG. 19 shows a terminal device 190. The terminal device 190 can perform the actions performed by the terminal device in the above-mentioned FIGS. 12 to 18.

Among them, the terminal device 190 may include a transceiver module 1901 and a processing module 1902. For example, the terminal device 190 may be a terminal device, or may be a chip applied in the terminal device or other combined device, component, etc. having the functions of the above terminal device. When the terminal device 190 is a terminal device, the transceiver module 1901 may be a transceiver, and the transceiver may include an antenna, a radio frequency circuit, etc.; the processing module 1902 may be a processor (or, processing circuit), such as a baseband processor, in a baseband processor Can include one or more CPUs. When the terminal device 190 is a component with the above terminal device functions, the transceiver module 1901 may be a radio frequency unit; the processing module 1902 may be a processor (or, processing circuit), such as a baseband processor. When the terminal device 190 is a chip system, the transceiver module 1901 can be the input and output interface of the chip (such as a baseband chip); the processing module 1902 can be the processor (or processing circuit) of the chip system, which can include one or more central processing units. unit. It should be understood that the transceiver module 1901 in the embodiment of the present application can be implemented by a transceiver or a transceiver-related circuit component; the processing module 1902 can be implemented by a processor or a processor-related circuit component (or, referred to as a processing circuit).

For example, the transceiver module 1901 can be used to perform all transceiver operations performed by the terminal device in the embodiments shown in Figures 12 to 18, and/or to support other processes of the technology described herein; the processing module 1902 can use In performing all operations performed by the terminal device in the embodiments shown in FIGS. 12 to 18 , except for the sending and receiving operations, and/or other processes used to support the technology described herein.

As another implementation manner, the transceiver module 1901 in Figure 19 can be replaced by a transceiver, which can integrate the functions of the transceiver module 1901; the processing module 1902 can be replaced by a processor, which can integrate the functions of the processing module 1902. Function. Further, the terminal device 190 shown in Figure 19 may also include a memory.

Alternatively, when the processing module 1902 is replaced by a processor and the transceiver module 1901 is replaced by a transceiver, the terminal device 190 involved in the embodiment of the present application can also be the communication device 200 shown in Figure 20 , where the processor can be Logic circuit 2001, transceiver may be interface circuit 2002. Further, the communication device 200 shown in FIG. 20 may also include a memory 2003.

Embodiments of the present application also provide a computer program product, which, when executed by a computer, can implement the functions of any of the above method embodiments.

An embodiment of the present application also provides a computer program, which when executed by a computer can implement the functions of any of the above method embodiments.

An embodiment of the present application also provides a computer-readable storage medium. All or part of the processes in the above method embodiments can be completed by instructing relevant hardware through a computer program. The program can be stored in the above computer-readable storage medium. When executed, the program can include the processes of the above method embodiments. . The computer-readable storage medium may be an internal storage unit of the terminal (including the data sending end and/or the data receiving end) of any of the foregoing embodiments, such as the hard disk or memory of the terminal. The above-mentioned computer-readable storage medium can also be an external storage device of the above-mentioned terminal, such as a plug-in hard disk, smart media card (SMC), secure digital (SD) card, flash memory card equipped on the above-mentioned terminal. (flash card) etc. Further, the computer-readable storage medium may also include both an internal storage unit of the terminal and an external storage device. The above computer-readable storage medium is used to store the above computer program and other programs and data required by the above terminal. The above-mentioned computer-readable storage media can also be used to temporarily store data that has been output or is to be output.

Through the above description of the embodiments, those skilled in the art can clearly understand that for the convenience and simplicity of description, only the division of the above functional modules is used as an example. In actual applications, the above functions can be allocated as needed. It is completed by different functional modules, that is, the internal structure of the device is divided into different functional modules to complete all or part of the functions described above.

In the several embodiments provided in this application, it should be understood that the disclosed devices and methods can be implemented in other ways. For example, the device embodiments described above are only illustrative. For example, the division of modules or units is only a logical function division. In actual implementation, there may be other division methods, for example, multiple units or components may be The combination can either be integrated into another device, or some features can be omitted, 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. The components shown as units may be one physical unit or multiple physical units, that is, they may be located in one place, or they may be distributed to multiple different places. . 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. The above integrated units can be implemented in the form of hardware or software functional units.

If the integrated unit is implemented in the form of a software functional unit and sold or used as an independent product, it may be stored in a readable storage medium. Based on this understanding, the technical solutions of the embodiments of the present application are essentially or all or part of the technical solutions can be embodied in the form of a software product. The software product is stored in a storage medium and includes a number of instructions to cause a device ( It may be a microcontroller, a chip, etc.) or a processor (processor) that executes 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, ROM, RAM, magnetic disk or optical disk and other media that can store program codes.

Claims (32)

A data volume indication method, characterized by including: The Packet Data Convergence Protocol PDCP entity of the terminal device indicates the first data amount to the Media Access Control MAC entity of the terminal device; wherein the PDCP entity and the first Radio Link Control RLC entity of the terminal device and the The second RLC entity of the terminal device is associated, the first data amount includes the data amount of the first data set, and the first data set is associated with the first RLC entity; The PDCP entity indicates a second data amount to the MAC entity; wherein the second data amount includes a data amount of a second data set, and the second data set is associated with the second RLC entity. The method according to claim 1, characterized in that: The first data amount also includes the data amount of the control protocol data unit PDU set; and/or The second data amount also includes the data amount of the control PDU set. A data volume indication method, characterized by including: The Packet Data Convergence Protocol PDCP entity of the terminal device acquires a third amount of data; wherein the PDCP entity is associated with the first Radio Link Control RLC entity of the terminal device and the second RLC entity of the terminal device; the third The three data amounts include the data amount of the first data set and the data amount of the second data set; the first data set is associated with the first RLC entity; the second data set is associated with the second RLC entity; The PDCP entity indicates the third data amount to the media access control MAC entity of the terminal device. The method according to claim 3, characterized in that: The third data amount also includes the data amount of the control PDU set. The method according to any one of claims 1-4, characterized in that, The first data set includes part or all of the second data of one or more data groups; The second data set includes part or all of the first data of one or more data groups; Wherein, the data group includes first data and one or more second data. The method according to any one of claims 1-5, characterized in that the method further includes: The PDCP entity obtains the first data of the second data group; If the second data submission of the first data group is completed or the delivery is terminated, the PDCP entity submits the first data of the second data group to the second RLC entity; Wherein, the first data group includes first data and one or more second data; the second data group includes first data and one or more second data; the first data and the The second RLC entity is associated; the second data is associated with the first RLC entity. The method of claim 6, further comprising: The PDCP entity sends a first request to the first RLC entity, where the first request is used to request information on whether the second data of the first data group is submitted to completion or to be terminated; The PDCP entity receives a first response from the first RLC entity; wherein the first response is used to indicate whether the delivery of the second data of the first data group is completed or the delivery is terminated. The method of claim 6, further comprising: The PDCP entity receives first indication information from the first RLC entity; wherein the first indication information is used to indicate that the second data submission of the first data group is completed or the submission is terminated. The method according to any one of claims 6-8, characterized in that the completion or termination of the second data submission of the first data group includes: The second data of the first data group is delivered to the MAC entity by the first RLC entity; or The second data of the first data group is submitted and terminated by the PDCP entity and/or the first RLC entity. A data volume indication method, characterized by including: The Packet Data Convergence Protocol PDCP entity of the terminal device indicates the first data amount to the Media Access Control MAC entity of the terminal device; wherein the PDCP entity and the first Radio Link Control RLC entity of the terminal device and the The second RLC entity of the terminal device is associated; the first data amount includes the data amount of a first data set, and the first data set is associated with the first RLC entity; The PDCP entity indicates a third data amount to the MAC entity; wherein the third data amount includes the data amount of the first data set and the data amount of the second data set, and the second data set is different from the data amount. The second RLC entity association. The method of claim 10, further comprising: The first data amount also includes the data amount of the control protocol data unit PDU set; and/or The third data amount also includes the data amount of the control PDU set. The method according to claim 10 or 11, characterized in that, The first data set includes part or all of the second data of one or more data groups; The second data set includes part or all of the first data of one or more data groups; Wherein, the data group includes first data and one or more second data. The method according to any one of claims 10-12, characterized in that the method further includes: The PDCP entity obtains the second data of the first data group; If the first condition is met, the PDCP entity submits the second data of the first data group to the second RLC entity; wherein the first condition includes the PDCP entity obtaining the first data of the second data group or The PDCP entity determines to submit the first data of the second data group to the second RLC entity; The first data group includes first data and one or more second data; the second data group includes first data and one or more second data; the first data and the second data RLC entity association; the second data is associated with the first RLC entity. The method of claim 13, further comprising: If the second data submission of the first data group is completed or the delivery is terminated, the PDCP entity submits the first data of the second data group to the second RLC entity. The method according to claim 14, characterized in that the second data submission of the first data group is completed or the submission is terminated, including: The second data of the first data group is delivered to the MAC entity; or The second data of the first data group is submitted and terminated by the PDCP entity and/or the second RLC entity. The method according to any one of claims 13-15, characterized in that the PDCP entity submits the second data of the first data group to the second RLC entity, including: The PDCP entity submits to the second RLC entity the data in the second data of the first data group that has not been submitted by the first RLC entity. The method according to claim 16, characterized in that: The data in the second data of the first data group that has not been submitted by the first RLC entity includes: the data in the second data of the first data group that has not been submitted to the first RLC entity by the PDCP entity. data; and/or, data in the second data of the first data group that has been submitted to the first RLC entity by the PDCP entity but has not been submitted by the first RLC entity. The method according to any one of claims 13-17, characterized in that the method further includes: If the first condition is not met, the PDCP entity submits second data of the first data group to the first RLC entity. The method according to any one of claims 13 to 18, characterized in that before the PDCP entity submits the second data of the first data group to the second RLC entity, the method further includes the following: One or more items: The PDCP entity sends second indication information to the first RLC entity; wherein the second indication information is used to indicate the arrival of the first data of the second data group; and/or The PDCP entity sends third indication information to the first RLC entity; wherein the third indication information is used to instruct the first RLC entity to feed back a delivery status report of the second data of the first data group; and / or The PDCP entity sends fourth indication information to the first RLC entity; wherein the fourth indication information is used to instruct the first RLC entity to delete the second data of the first data group. A data submission method, characterized by including: The service data adaptation protocol SDAP entity of the terminal device obtains the first data of the second data group; wherein the SDAP entity, the first packet data convergence protocol PDCP entity of the terminal device and the second PDCP entity of the terminal device association; If the second data submission of the first data group is completed or the delivery is terminated, the SDAP entity submits the first data of the second data group to the second PDCP entity; wherein the first data group includes the first data , and one or more second data; the second data group includes first data, and one or more second data; the first data is associated with the second PDCP entity, and the second data is associated with The first PDCP entity association. The method of claim 20, further comprising: The SDAP entity sends a second request to the first PDCP entity; wherein the second request is used to request information on whether the second data of the first data group is submitted or terminated; The SDAP entity receives a second response from the first PDCP entity; wherein the second response is used to indicate whether the delivery of the second data of the first data group is completed or the delivery is terminated. The method of claim 20, further comprising: The SDAP entity sends a third request to the first radio link control RLC entity of the terminal device; wherein the third request is used to request whether the second data of the first data group is submitted or terminated. information; The SDAP entity receives a third response from the first RLC entity; wherein the third response is used to indicate whether the delivery of the second data of the first data group is completed or the delivery is terminated. The method of claim 20, further comprising: The SDAP entity receives fifth indication information from the first PDCP entity or the first RLC entity of the terminal device; wherein the fifth indication information is used to indicate the second data submission of the first data group Completion or submission of termination. The method according to any one of claims 20 to 23, characterized in that the completion or termination of the second data submission of the first data group includes: The second data of the first data group is delivered by the first RLC entity of the terminal device to the MAC entity of the terminal device; or The second data of the first data group is submitted and terminated by one or more of the following entities: the SDAP entity, the first PDCP entity, and the first RLC entity of the terminal device. A data submission method, characterized by including: The second packet data aggregation protocol PDCP entity of the terminal device obtains the first data of the second data group; wherein the service data adaptation protocol SDAP entity of the terminal device and the first PDCP and the second PDCP of the terminal device entity association; If the second data submission of the first data group is completed or the submission is terminated, the second PDCP entity submits the first data of the second data group to the second radio link control RLC entity of the terminal device; wherein, The first data group includes first data and one or more second data; the second data group includes first data and one or more second data; the first data and the second PDCP The entity is associated with the second RLC entity; the second data is associated with the first PDCP and the first RLC entity of the terminal device. The method of claim 25, further comprising: The second PDCP entity sends a fourth request to the SDAP entity; wherein the fourth request is used to request information on whether the second data of the first data group is submitted or terminated; The second PDCP entity receives a fourth response from the SDAP entity; wherein the fourth response is used to indicate whether the delivery of the second data of the first data group is completed or the delivery is terminated. The method of claim 25, further comprising: The second PDCP entity sends a fifth request to the first PDCP entity; wherein the fifth request is used to request information on whether the second data of the first data group has been submitted to completion or has been terminated; The second PDCP entity receives a fifth response from the first PDCP entity; wherein the fifth response is used to indicate whether the delivery of the second data of the first data group is completed or the delivery is terminated. The method of claim 25, further comprising: The second PDCP entity receives sixth indication information from the SDAP entity or the first PDCP entity; wherein the sixth indication information is used to indicate the completion or delivery of the second data submission of the first data group termination. The method according to any one of claims 25 to 28, characterized in that the completion or termination of the second data submission of the first data group includes: The second data of the first data group is delivered by the first RLC entity to the MAC entity of the terminal device; or The second data of the first data group is submitted and terminated by the first PDCP entity and/or the first RLC entity. A communication device, characterized in that the communication device includes a processor; the processor is used to run a computer program or instructions to cause the communication device to execute the data according to any one of claims 1-9 The amount indication method, or the data amount indication method as described in any one of claims 10-19, or the data submission method as described in any one of claims 20-24, or the data amount indication method as described in any one of claims 25-29. The data submission method described in item 1. A computer-readable storage medium, characterized in that the computer-readable storage medium stores computer instructions or programs. When the computer instructions or programs are run on a computer, the amount of data as described in any one of claims 1-9 is achieved. Instructs the method to be executed, or as claimed The method for indicating the amount of data according to any one of claims 10-19 is executed, or the data submission method according to any one of claims 20-24 is executed, or the data amount according to any one of claims 25-29 is executed. The submission method is executed. A computer program product, characterized in that the computer program product includes computer instructions; when part or all of the computer instructions are run on a computer, the data amount indication method as described in any one of claims 1-9 be executed, or the data amount indication method as described in any one of claims 10-19 is executed, or the data submission method as described in any one of claims 20-24 is executed, or as any one of claims 25-29 The data submission method described in item 1 is executed.