WO2019126963A1 - Uplink grant method, network device, and terminal device - Google Patents

Abstract

Disclosed are an uplink grant method, a network device, and a terminal device. the method comprises: a first network device receives, from data volumes to be transmitted sent by a terminal device, a first data volume buffered by a Packet Data Convergence Protocol (PDCP) layer of the terminal device, the data volumes to be transmitted being the sum of the first data volume and a second data volume buffered by a radio link control (RLC) layer of the terminal device, the second data volume comprising a data volume buffered by the RLC layer and waiting for primary transmission; the terminal device interacts with the first network device by means of the first RLC layer, and interacts with a second network device by means of a second RLC layer. The method, the network device, and the terminal device of embodiments of the present application help improving the uplink grant performance.

Description

Uplink authorization method, network device and terminal device Technical field

The embodiments of the present application relate to the field of communications, and in particular, to a method, a network device, and a terminal device for uplink authorization.

Background technique

When the data bearer adopts a split bearer protocol architecture, two Packet Radio Convergence Protocols (PDCPs) are respectively connected to two or more Radio Link Controls (RLCs). The network devices in the cell group interact with the terminal devices through different RLCs.

In the new radio (NR), the terminal is allowed to send the uplink data from the PDCP to the RLC before the uplink grant arrives, and then wait until the uplink grant arrives, and then send it to the media access control (Media Access Control, MAC). Therefore, in order to alleviate the transient processing capability requirements of the terminal, how to perform uplink authorization is a problem to be solved in a scenario where a certain splitting bearer of the terminal has a pre-processing.

Summary of the invention

In view of this, the embodiment of the present application provides a method for uplink authorization, a network device, and a terminal device, which are beneficial to improving performance of uplink authorization.

In a first aspect, a method for uplink authorization is provided, where the method includes: receiving, by a first network device, a first data amount buffered by a PDCP layer of a packet data convergence protocol of the terminal device in a data volume to be transmitted sent by the terminal device, where the The amount of transmission data is equal to the sum of the first data amount and the second data amount buffered by the radio link control RLC layer of the terminal device, where the second data amount includes the amount of data waiting for the initial transmission of the RLC layer buffer, and the terminal device The first RLC layer interacts with the first network device, and the terminal device interacts with the second network device through the second RLC layer.

The first data amount of the PDCP layer cache is reported by the terminal device to the first network device and/or the second network device, which is convenient for avoiding resources for all data volumes of the PDCP layer cached by the first network device and the second network device. The waste of resources caused by the allocation increases the performance of the uplink authorization.

The amount of data buffered by the RLC layer includes the amount of data waiting to be newly transmitted and/or the amount of data waiting to be retransmitted.

In a possible implementation, the amount of data waiting for the initial transmission buffered by the RLC layer includes, before the terminal device receives the uplink authorization information sent by the first network device, from the PDCP layer to the first RLC layer. The amount of data to be preprocessed, and/or the amount of data to be preprocessed from the PDCP layer into the second RLC layer before the terminal device receives the uplink grant information sent by the second network device.

In a possible implementation, the second data volume includes a third data volume of the first RLC layer cache and a fourth data volume of the second RLC layer cache.

In a possible implementation manner, the method further includes: the first network device sending, to the terminal device, uplink authorization information, where the uplink authorization information is used to schedule data corresponding to the fifth data amount in the first data amount. And the data corresponding to the sixth data amount in the first data amount is scheduled by the second network device, and the sum of the fifth data amount and the sixth data amount is equal to the first data amount.

In a possible implementation, the uplink authorization information is further used to schedule data corresponding to the third data volume, and the method further includes: receiving, by the first network device, the third data volume sent by the terminal device.

In a possible implementation, before the first network device sends the uplink authorization information to the terminal device, the method further includes: the first network device negotiates with the second network device to determine the fifth data amount.

In a possible implementation manner, before the first network device sends the uplink authorization information to the terminal device, the method further includes: determining, by the first network device, the fifth data amount; The second network device sends the sixth amount of data.

In a possible implementation manner, the amount of data to be transmitted is greater than a threshold.

In a possible implementation manner, the first network device is a network device of a primary cell group MCG, and the second network device is a network device of a secondary cell group SCG.

A second aspect provides a method for uplink authorization, where the method includes: the terminal device sends, to the first network device, a first data amount of a packet data convergence protocol PDCP layer cache of the terminal device in the data volume to be transmitted, where the terminal data is to be transmitted. The amount of data is equal to the sum of the first data amount and the second data amount buffered by the radio link control RLC layer of the terminal device, where the second data amount includes the amount of data waiting for the initial transmission in the RLC layer buffer, and the terminal device passes The first RLC layer interacts with the first network device, and the terminal device interacts with the second network device through the second RLC layer.

In a possible implementation, the amount of data waiting for the initial transmission buffered by the RLC layer includes, before the terminal device receives the uplink authorization information sent by the first network device, from the PDCP layer to the first RLC layer. And the amount of data to be preprocessed from the PDCP layer to the second RLC layer for preprocessing.

In a possible implementation, the second data volume includes a third data volume of the first RLC layer cache and a fourth data volume of the second RLC layer cache.

In a possible implementation, the method further includes: receiving, by the terminal device, uplink authorization information sent by the first network device, where the uplink authorization information is used to schedule a fifth data amount corresponding to the first data amount. Data, the data corresponding to the sixth data amount of the first data amount is scheduled by the second network device, and the sum of the fifth data amount and the sixth data amount is equal to the first data amount.

In a possible implementation, the method further includes: the terminal device sending the third amount of data to the first network device.

In a possible implementation manner, the terminal device receives uplink authorization information sent by the first network device, where the uplink authorization information is used to schedule data corresponding to the third data volume.

In a possible implementation, the method further includes: the terminal device transmitting the first data amount and the fourth data amount to the second network device.

In a possible implementation manner, the terminal device sends the first data amount to the first network device, where the terminal device sends the first data to the first network device, where the amount of data to be transmitted is greater than a threshold. The amount of data.

In a possible implementation manner, the first network device is a network device of a primary cell group MCG, and the second network device is a network device of a secondary cell group SCG.

In a third aspect, a network device is provided for performing the method of any of the first aspect or the first aspect of the first aspect. In particular, the network device comprises means for performing the method of any of the above-described first aspect or any of the possible implementations of the first aspect.

In a fourth aspect, a terminal device is provided for performing the method in any of the above-mentioned second aspect or any possible implementation of the second aspect. In particular, the terminal device comprises means for performing the method of any of the above-described second or second aspects of the second aspect.

In a fifth aspect, a network device is provided, the network device comprising: a memory, a processor, an input interface, and an output interface. The memory, the processor, the input interface, and the output interface are connected by a bus system. The memory is for storing instructions for executing the memory stored instructions for performing the method of any of the first aspect or the first aspect of the first aspect.

In a sixth aspect, a terminal device is provided, the terminal device comprising: a memory, a processor, an input interface, and an output interface. The memory, the processor, the input interface, and the output interface are connected by a bus system. The memory is for storing instructions for executing the memory stored instructions for performing the method of any of the above-described second aspect or any of the possible implementations of the second aspect.

In a seventh aspect, a computer storage medium is provided for storing the method in any of the above possible implementations of the first aspect or the first aspect, or any possible implementation of the second or second aspect Computer software instructions for use in the method of the present invention, including programs designed to perform the various aspects described above.

In an eighth aspect, a computer program product comprising instructions, when executed on a computer, causes the computer to perform the method of any of the first aspect or the optional implementation of the first aspect, or the second Aspect or method of any alternative implementation of the second aspect.

These and other aspects of the present application will be more readily apparent from the following description of the embodiments.

DRAWINGS

FIG. 1 is a schematic diagram of an application scenario of an embodiment of the present application.

FIG. 2 shows a protocol architecture diagram of a split bearer in a dual connectivity scenario.

FIG. 3 is a schematic block diagram of a method for uplink authorization according to an embodiment of the present application.

FIG. 4 is another schematic block diagram of a method for uplink authorization according to an embodiment of the present application.

FIG. 5 shows a schematic block diagram of a network device of an embodiment of the present application.

FIG. 6 shows a schematic block diagram of a terminal device of an embodiment of the present application.

FIG. 7 shows another schematic block diagram of a network device of an embodiment of the present application.

FIG. 8 is another schematic block diagram of a terminal device according to an embodiment of the present application.

Detailed ways

The technical solutions in the embodiments of the present application will be clearly and completely described in the following with reference to the accompanying drawings in the embodiments.

It should be understood that the technical solutions of the embodiments of the present application can be applied to various communication systems, such as a Global System of Mobile communication (GSM) system, a Code Division Multiple Access (CDMA) system, and a wideband code. Wideband Code Division Multiple Access (WCDMA) system, General Packet Radio Service (GPRS), Long Term Evolution (LTE) system, LTE Frequency Division Duplex (FDD) system, LTE time division duplex (Time Division Duplex, TDD), Universal Mobile Telecommunication System (UMTS), Worldwide Interoperability for Microwave Access (WiMAX) communication system, New Radio (NR) or future 5G System, etc.

In particular, the technical solutions of the embodiments of the present application can be applied to various communication systems based on non-orthogonal multiple access technologies, such as a sparse code multiple access (SCMA) system, and a low-density signature (Low). Density Signature (LDS) system, etc., of course, the SCMA system and the LDS system may also be referred to as other names in the communication field; further, the technical solution of the embodiment of the present application can be applied to multi-carrier using non-orthogonal multiple access technology. Transmission system, for example, Orthogonal Frequency Division Multiplexing (OFDM), Filter Bank Multi-Carrier (FBMC), General Frequency Division Multiplexing (Generalized Frequency Division Multiplexing (OFDM)) Frequency Division Multiplexing (GFDM), Filtered Orthogonal Frequency Division Multiplexing (Filtered-OFDM, F-OFDM) system, and the like.

The terminal device in the embodiment of the present application may refer to a user equipment (User Equipment, UE), an access terminal, a subscriber unit, a subscriber station, a mobile station, a mobile station, a remote station, a remote terminal, a mobile device, a user terminal, a terminal, and a wireless device. Communication device, user agent or user device. The access terminal may be a cellular phone, a cordless phone, a Session Initiation Protocol (SIP) phone, a Wireless Local Loop (WLL) station, a Personal Digital Assistant (PDA), with wireless communication. Functional handheld devices, computing devices or other processing devices connected to wireless modems, in-vehicle devices, wearable devices, terminal devices in future 5G networks, or in the future evolution of the Public Land Mobile Network (PLMN) The terminal device and the like are not limited in the embodiment of the present application.

The network device in the embodiment of the present application may be a device for communicating with a terminal device, where the network device may be a Base Transceiver Station (BTS) in GSM or CDMA, or may be a base station (NodeB, NB) in a WCDMA system. And may be an evolved base station (eNB or eNodeB) in the LTE system, or may be a wireless controller in a cloud radio access network (CRAN) scenario, or the network device may be The embodiments of the present application are not limited to the relay station, the access point, the in-vehicle device, the wearable device, and the network device in the future 5G network or the network device in the future evolved PLMN network.

FIG. 1 is a schematic diagram of an application scenario of an embodiment of the present application. The communication system in FIG. 1 may include a terminal device 10 and a network device 20. The network device 20 is configured to provide communication services for the terminal device 10 and access the core network. The terminal device 10 accesses the network by searching for synchronization signals, broadcast signals, and the like transmitted by the network device 20, thereby performing communication with the network. The arrows shown in FIG. 1 may represent uplink/downlink transmissions by a cellular link between the terminal device 10 and the network device 20.

Those skilled in the art understand that two or more RLCs can be respectively connected under one PDCP, and such a bearer can be referred to as a split bearer. The protocol architecture of the split bearer in the dual connectivity scenario will be briefly described below with reference to FIG. 2 . For uplink and downlink, the PDCP is located in a cell group (Cell Group, CG), which is an anchor cell group (anchor CG), where the CG includes a primary cell group (MCG) and a secondary cell group (Secondary). Cell Group, SCG), PDCP can send PDCP Protocol Data Unit (PDU) to RLC in MCG and SCG, so that data can be transmitted by using two connections, data passing through RLC of different cell groups, media access Control (Media Access Control, MAC), then go through the air interface to the terminal (downlink) or the base station (uplink) corresponding MAC, RLC layer, and finally aggregate to PDCP, and finally submit the data to the upper layer.

In LTE, when the upper layer data arrives, it stays at the PDCP layer. When the MCG or the SCG has the uplink resource grant to reach the terminal device, the terminal device sends the data down to the RLC layer of the primary cell group or the secondary cell group, and finally sends the data to the RLC layer. Network side. The disadvantage of this type of processing is that the terminal device sends the data from the PDCP to the RLC, generates the RLC PDU, and then generates the MAC PDU, which is too high for the instantaneous processing capability of the terminal device.

In the NR, a pre-processing is proposed for the problem, that is, the terminal device is allowed to send data from the PDCP to the RLC to generate an RLC PDU before the uplink resource authorization reaches the terminal device, and wait until the uplink resource authorization is reached. In turn, a MAC PDU is generated, thereby alleviating the transient processing capability requirements for the UE. How to perform uplink authorization in the scenario where the terminal device preprocesses the data of a split bearer is a problem that needs to be solved.

It should be understood that the terms "system" and "network" are used interchangeably herein. The term "and/or" in this context is merely an association describing the associated object, indicating that there may be three relationships, for example, A and / or B, which may indicate that A exists separately, and both A and B exist, respectively. B these three situations. In addition, the character "/" in this article generally indicates that the contextual object is an "or" relationship.

It should be understood that, in this application, a splitting bearer is used as an example of a PDCP connecting two RLCs. A split bearer may also be a PDCP connection of three or four RLCs, and the embodiment of the present application is not limited thereto.

FIG. 3 is a schematic block diagram of a method 100 of uplink authorization in an embodiment of the present application. As shown in FIG. 3, the method 100 includes the following parts or all of the contents:

S110. The first network device receives, by the terminal device, the first data volume buffered by the PDCP layer of the packet data convergence protocol of the terminal device, where the amount of data to be transmitted is equal to the first data amount and the wireless device of the terminal device. The link controls the sum of the second data volume buffered by the RLC layer, the second data volume includes the amount of data waiting to be initially transmitted by the RLC layer buffer, and the terminal device interacts with the first network device by using the first RLC layer, where The terminal device interacts with the second network device through the second RLC layer.

Optionally, the second amount of data includes a third amount of data cached by the first RLC layer and/or a fourth amount of data cached by the second RLC layer.

Specifically, the embodiment of the present application is directed to a split bearer of the terminal device, and the respective network devices in the two cell groups interact with the terminal device through the link as shown in FIG. 2, where the split bearer The network side PDCP is located in the cell group CG1. In the embodiment of the present application, the amount of data to be transmitted includes both the data volume buffered by the PDCP layer and the data volume buffered by the RLC layer, and the data volume buffered by the RLC layer may be the data volume of the RLC layer cache on the CG1 link. / or the amount of data buffered by the RLC layer on the CG2 link. The amount of data buffered by the RLC layer may further include the amount of data waiting to be newly transmitted in the RLC layer buffer and the amount of data waiting to be retransmitted in the RLC layer buffer. The amount of data buffered by the RLC layer may include the amount of data entering the RLC layer on the CG1 link and/or the amount of data entering the RLC layer on the CG2 link from the PDCP layer before the UE receives the uplink grant. It should be understood that the data volume of the RLC layer cache described in the multiple embodiments of the present application includes the amount of data waiting for initial transmission, that is, the amount of data that has been pre-processed, and the amount of data buffered by the RLC layer may also be only waiting for weight. The amount of data to be transmitted is not limited as long as the data is cached by the RLC layer.

It is understood by those skilled in the art that the UE needs to report the amount of data to be scheduled to the network, that is, the Buffer State Report (BSR). After receiving the BSR, the network allocates resources to the amount of data reported by the UE. The amount of data to be transmitted at this time may be divided into two parts, one part is the amount of data buffered by the RLC layer, for example, may include entering the CG1 and/or CG2 link from the PDCP layer before the UE receives the uplink grant. The data of the RLC layer. The other part is the amount of data buffered by the PDCP layer. This part of data buffered by the PDCP layer can be shared by the respective network devices of CG1 and CG2, that is, a part of data buffered in the PDCP layer can be scheduled by the network device of CG1, and the PDCP layer is scheduled by the network device of CG2. Another part of the data cached. In this way, it is possible to avoid waste of resources caused by resource allocation of all data of the CG1 and CG2 network devices that are buffered by the PDCP layer, and improve the performance of the uplink authorization.

It should be understood that, in the embodiment of the present application, the following scenarios may be included:

First, before the terminal device receives the uplink grant, only the RLC layer on the CG1 link buffers the data, and the terminal device can separately report the data volume of the PDCP layer cache and the RLC cache on the CG1 link to the network device of the CG1. The amount of data, and the terminal device does not report the amount of data to the network device of the CG2; before the terminal device receives the uplink grant, only the RLC layer on the CG2 link buffers the data, and the terminal device can report the PDCP layer only to the network device of the CG2. The amount of data buffered and the amount of data of the RLC cache on the CG2 link, and the terminal device does not report the amount of data to the network device of the CG1.

Second, before the terminal device receives the uplink grant, only the RLC layer on the CG1 link caches data, and the terminal device can report the data volume of the RLC cache only to the network device of the CG1, and the terminal device can send the network device to the CG2. Reporting the amount of data buffered by the PDCP layer; before the terminal device receives the uplink grant, only the RLC layer on the CG2 link buffers the data, the terminal device can report the data volume of the PDCP cache only to the network device of the CG1, and the terminal device can The amount of data cached by the RLC layer on the CG2 link is reported only to the network device of the CG2.

Third, before the terminal device receives the uplink grant, only the RLC layer on the CG1 link caches data, and the terminal device can report the data volume buffered by the PDCP layer to the network devices of the CG1 and the CG2; the terminal device receives the uplink. Before the authorization, only the RLC layer on the CG2 link buffers the data, and the terminal device can report the data volume of the PDCP layer cache to the network devices of the CG1 and the CG2.

Fourth, before the terminal device receives the uplink grant, the RLC layer on the CG1 link and the RLC layer on the CG2 link both cache data, and the terminal device can report the data volume of the PDCP layer cache to the network device of the CG1 or CG2. .

Fifth, before the terminal device receives the uplink grant, the RLC layer on the CG1 link and the RLC layer on the CG2 link both have data, and the terminal device can report the data buffered by the PDCP layer to the network devices of the CG1 and the CG2. the amount.

Optionally, in the embodiment of the present application, the method further includes: the first network device sends, to the terminal device, uplink authorization information, where the uplink authorization information is used to schedule, corresponding to a fifth data amount in the first data volume. The data corresponding to the sixth data amount in the first data amount is scheduled by the second network device, and the sum of the fifth data amount and the sixth data amount is equal to the first data amount.

A person skilled in the art understands that the terminal device reports the amount of data to the network device, and the network device can allocate resources according to the received data amount, and indicate the allocated resources by sending uplink authorization information to the terminal device. In the embodiment of the present application, the uplink authorization information sent by the first network device to the terminal device may be used to schedule part of the data buffered by the PDCP layer. The other part of the data buffered by the PDCP layer can be scheduled by the second network device, that is, the second network device also sends uplink grant information to the terminal device, and the uplink grant information can be used to schedule the remaining PDCP layer cache. data.

Optionally, in the embodiment of the present application, the uplink authorization information is further used to schedule data corresponding to the third data volume, where the method further includes: receiving, by the first network device, the third data volume sent by the terminal device .

Optionally, in the embodiment of the present application, the terminal device may report the fourth data volume to the second network device, where the uplink authorization information sent by the second network device to the terminal device may be scheduled corresponding to the sixth data amount. In addition to the data, data corresponding to the fourth amount of data may also be scheduled.

It should be understood that the data buffered in the RLC layer on a certain link must be scheduled by the network device on the corresponding link. For example, the amount of data buffered by the RLC layer on the CG1 link must be scheduled by the network device of CG1.

Optionally, in the embodiment of the present application, before the first network device sends the first uplink authorization information to the terminal device, the method further includes: the first network device negotiates with the second network device to determine the fifth data. the amount.

Optionally, in the embodiment of the present application, before the first network device sends the uplink authorization information to the terminal device, the method further includes: determining, by the first network device, the fifth data amount and the sixth data amount; The first network device sends the sixth data amount to the second network device. The second network device receives the sixth amount of data sent by the first network device.

The terminal device can separately send the data volume of the PDCP layer buffer to one of the CG1 and the CG2, and the network device that receives the data amount can allocate the data volume of the PDCP layer buffer that is assumed by the other network device, and inform the other The amount of data buffered by the PDCP layer that a network device should bear, for example, can be directly sent to another network device or can report the amount of data of the PDCP layer buffer that it should bear to the other network device through the terminal device. The network device that receives the amount of data can also negotiate with another network device for the amount of data that is buffered by the PDCP layer. The terminal device can also send the data amount to the respective network devices of the CG1 and the CG2, so that the network devices of the CG1 and the CG2 can negotiate or allocate the data amount of the PDCP layer buffered by each of the network devices. This example is not limiting.

In the embodiment of the present application, the amount of data to be transmitted is mainly divided into two parts: the data volume buffered by the PDCP layer and the data volume buffered by the RLC layer. For example, the amount of data cached by the RLC layer of the CG1 link is set to A, the amount of data buffered by the RLC layer of the CG2 link is set to B, and the amount of data buffered by the PDCP layer is set to C, and the terminal device can separately The network device of each of CG1 and CG2 reports the data amount C, then the network device of CG1 can negotiate with the network device of CG2 to bear the amount of data in each data amount C, for example, the network device of CG1 bears the data amount of 0.5 C, the network of CG2 The device also bears a data volume of 0.5C. The terminal device can also report the data amount C to only one of the CG1 or CG2 network devices. For example, only the data amount C is reported to the network device of the CG1, and the network device of the CG1 can decide to bear the data amount of 0.5C by itself, by the CG2. The network device bears the remaining 0.5C data amount, and the network device of the CG1 can directly send the remaining 0.5C data amount to the network device of the CG2, or the terminal device can forward the remaining 0.5C data amount to the network device of the CG2. . It should be understood that the amount of data each of the network device of CG1 and the network device of CG2 is intended to be illustrative, and is not intended to limit the scope of the application.

Optionally, in the embodiment of the present application, the amount of data to be transmitted is greater than a threshold. A threshold may be set for the amount of data to be transmitted. If the amount of data to be transmitted is less than the threshold, the terminal device may report the amount of data buffered by the PDCP layer and the amount of data cached by the RLC layer on the MSG link to the MSG network. If the amount of data to be transmitted is greater than the threshold, the solution of the embodiment of the present application may be used, and the data volume of the PDCP layer buffered by the two network devices in the CG1 and the CG2 may further improve the performance of the uplink authorization.

Optionally, in the embodiment of the present application, the first network device is a network device of a primary cell group MCG, and the second network device is a network device of a secondary cell group SCG. That is, the above CG1 and CG2 may be MCG and SCG, respectively. If the PDCP is located in the MSG, the splitting bearer is the splitting bearer of the primary cell group. If the PDCP is located in the SCG, the splitting bearer is the splitting bearer of the secondary cell group.

FIG. 4 shows a schematic block diagram of a method 200 of uplink authorization in an embodiment of the present application. As shown in FIG. 4, the method 200 includes the following parts or all of the contents:

S210, the terminal device sends, to the first network device, a first data amount buffered by the packet data convergence protocol PDCP layer of the terminal device in the data volume to be transmitted, where the data volume to be transmitted is equal to the first data amount and the terminal The radio link of the device controls the sum of the second data amounts buffered by the RLC layer, the second data amount includes the amount of data waiting to be initially transmitted in the RLC layer buffer, and the terminal device passes the first RLC layer and the first A network device interacts, and the terminal device interacts with the second network device through the second RLC layer.

Therefore, the method for the uplink authorization in the embodiment of the present application is beneficial to avoid waste of resources caused by resource allocation of all data sources of the CG1 and CG2, and the uplink authorization performance is improved.

Optionally, in the embodiment of the present application, the amount of data waiting for the initial transmission of the RLC layer buffer is included in the PDCP layer before the terminal device receives the uplink authorization information sent by the first network device. And an amount of data to be preprocessed in the first RLC layer, and/or from the PDCP layer to the second RLC layer before the terminal device receives the uplink grant sent by the second network device The amount of data to be preprocessed.

Optionally, in the embodiment of the present application, the second data volume includes a third data volume of the first RLC layer cache and a fourth data volume of the second RLC layer cache.

Optionally, in the embodiment of the present application, the method further includes: receiving, by the terminal device, uplink authorization information sent by the first network device, where the uplink authorization information is used for scheduling and the first data volume. Data corresponding to the fifth data amount, data corresponding to the sixth data amount of the first data amount is scheduled by the second network device, and a sum of the fifth data amount and the sixth data amount is equal to The first amount of data.

Optionally, in the embodiment of the present application, the method further includes: the terminal device sending the third data amount to the first network device.

Optionally, in the embodiment of the present application, the terminal device receives uplink authorization information sent by the first network device, where the uplink authorization information is used to schedule data corresponding to the third data volume.

Optionally, in the embodiment of the present application, the method further includes: the terminal device sending the first data amount and the fourth data amount to the second network device.

Optionally, in the embodiment of the present application, the sending, by the terminal device, the first data volume to the first network device, includes: when the amount of data to be transmitted is greater than a threshold, the terminal device is to the first The network device transmits the first amount of data.

Optionally, in the embodiment of the present application, the first network device is a network device of a primary cell group MCG, and the second network device is a network device of a secondary cell group SCG.

It should be understood that the interaction between the terminal device and the network device described by the terminal device and related features, functions, and the like correspond to related features and functions of the network device. The related content has been described in detail in the above method 100. For brevity, no further details are provided herein.

It should also be understood that, in various embodiments of the present application, the size of the sequence numbers of the above processes does not mean the order of execution, and the order of execution of each process should be determined by its function and internal logic, and should not be implemented in the present application. The implementation of the examples constitutes any limitation.

The method for uplink authorization according to the embodiment of the present application is described in detail above. The device for uplink authorization according to the embodiment of the present application will be described below with reference to FIG. 5 to FIG. 8. The technical features described in the method embodiment are applicable to the following device implementation. example.

FIG. 5 shows a schematic block diagram of a network device 300 of an embodiment of the present application. As shown in FIG. 5, the network device 300 includes:

The receiving unit 310 is configured to receive, by the terminal device, a first data amount buffered by the packet data convergence protocol PDCP layer of the terminal device, where the amount of data to be transmitted is equal to the first data amount and the The radio link of the terminal device controls the sum of the second data amounts buffered by the RLC layer, the second data amount includes the amount of data waiting to be initially transmitted by the RLC layer buffer, and the terminal device passes the first RLC layer and the The first network device interacts, and the terminal device interacts with the second network device through the second RLC layer.

Therefore, the network device in the embodiment of the present application is advantageous in avoiding waste of resources caused by resource allocation of all data sources of the CG1 and CG2, which are all buffered by the PDCP layer, and improves the performance of the uplink authorization.

Optionally, in the embodiment of the present application, the amount of data waiting for the initial transmission of the RLC layer buffer is included in the PDCP layer before the terminal device receives the uplink authorization information sent by the first network device. And an amount of data to be preprocessed in the first RLC layer, and/or from the PDCP layer to the second RLC before the terminal device receives the uplink grant information sent by the second network device The amount of data to be preprocessed in the layer.

Optionally, in the embodiment of the present application, the second data volume includes a third data volume of the first RLC layer cache and a fourth data volume of the second RLC layer cache.

Optionally, in the embodiment of the present application, the network device further includes: a sending unit, configured to send, to the terminal device, uplink authorization information, where the uplink authorization information is used for scheduling and the first data amount. Data corresponding to the fifth data amount, data corresponding to the sixth data amount of the first data amount is scheduled by the second network device, and a sum of the fifth data amount and the sixth data amount is equal to The first amount of data is described.

Optionally, in the embodiment of the present application, the uplink authorization information is further used to schedule data corresponding to the third data volume, and the receiving unit is further configured to: receive the third sent by the terminal device The amount of data.

Optionally, in the embodiment of the present application, the network device further includes: a determining unit, configured to negotiate with the second network device to determine the fifth data amount.

Optionally, in the embodiment of the present application, the network device further includes: a determining unit, configured to determine the fifth data amount; the sending unit is further configured to: send the first to the second network device Six data volumes.

Optionally, in the embodiment of the present application, the amount of data to be transmitted is greater than a threshold.

Optionally, in the embodiment of the present application, the first network device is a network device of a primary cell group MCG, and the second network device is a network device of a secondary cell group SCG.

It should be understood that the network device 300 according to the embodiment of the present application may correspond to the network device in the method embodiment of the present application, and the foregoing and other operations and/or functions of the respective units in the network device 300 respectively implement the network in the method of FIG. The corresponding process of the device is not described here for brevity.

FIG. 6 shows a schematic block diagram of a terminal device 400 of an embodiment of the present application. As shown in FIG. 6, the terminal device 400 includes:

The sending unit 410 is configured to send, to the first network device, a first data amount of the packet data convergence protocol PDCP layer buffer of the terminal device in the data volume to be transmitted, where the data volume to be transmitted is equal to the first data volume and The radio link of the terminal device controls the sum of the second data amounts buffered by the RLC layer, the second data amount includes the amount of data waiting for the initial transmission in the RLC layer buffer, and the terminal device passes the first RLC layer and the The first network device interacts, and the terminal device interacts with the second network device through the second RLC layer.

Therefore, the terminal device in the embodiment of the present application is advantageous in avoiding waste of resources caused by resource allocation of all data sources of the CG1 and CG2, which are buffered by the PDCP layer, and improves the performance of the uplink authorization.

Optionally, in the embodiment of the present application, the amount of data waiting for the initial transmission of the RLC layer buffer is included in the PDCP layer before the terminal device receives the uplink authorization information sent by the first network device. And an amount of data to be preprocessed in the first RLC layer, and/or from the PDCP layer to the second RLC layer before the terminal device receives the uplink grant sent by the second network device The amount of data to be preprocessed.

Optionally, in the embodiment of the present application, the second data volume includes a third data volume of the first RLC layer cache and a fourth data volume of the second RLC layer cache.

Optionally, in the embodiment of the present application, the terminal device further includes: a receiving unit, configured to receive uplink authorization information sent by the first network device, where the uplink authorization information is used to schedule and the first data Data corresponding to the fifth data amount in the quantity, data corresponding to the sixth data quantity in the first data quantity is scheduled by the second network device, and the fifth data quantity and the sixth data quantity And equal to the first amount of data.

Optionally, in the embodiment of the present application, the sending unit is further configured to: send the third data volume to the first network device.

Optionally, in the embodiment of the present application, the terminal device further includes: a receiving unit, configured to receive uplink authorization information sent by the first network device, where the uplink authorization information is used to schedule and the third data The amount of data corresponding.

Optionally, in the embodiment of the present application, the sending unit is further configured to: send the first data amount and the fourth data amount to the second network device.

Optionally, in the embodiment of the present application, the sending unit is specifically configured to: when the amount of data to be transmitted is greater than a threshold, send the first data amount to the first network device.

Optionally, in the embodiment of the present application, the first network device is a network device of a primary cell group MCG, and the second network device is a network device of a secondary cell group SCG.

It should be understood that the terminal device 400 according to the embodiment of the present application may correspond to the terminal device in the method embodiment of the present application, and the foregoing and other operations and/or functions of the respective units in the terminal device 400 respectively implement the terminal in the method of FIG. 4 The corresponding process of the device is not described here for brevity.

As shown in FIG. 7, the embodiment of the present application further provides a network device 500, which may be the network device 300 in FIG. 5, which can be used to execute the content of the network device corresponding to the method 100 in FIG. . The network device 500 includes an input interface 510, an output interface 520, a processor 530, and a memory 540. The input interface 510, the output interface 520, the processor 530, and the memory 540 can be connected by a bus system. The memory 540 is for storing programs, instructions or code. The processor 530 is configured to execute a program, an instruction or a code in the memory 540 to control the input interface 510 to receive a signal, control the output interface 520 to send a signal, and complete the operations in the foregoing method embodiments.

Therefore, the network device in the embodiment of the present application is advantageous in avoiding waste of resources caused by resource allocation of all data sources of the CG1 and CG2, which are all buffered by the PDCP layer, and improves the performance of the uplink authorization.

It should be understood that, in the embodiment of the present application, the processor 530 may be a central processing unit (CPU), and the processor 530 may also be other general-purpose processors, digital signal processors, application specific integrated circuits, and ready-made Program gate arrays or other programmable logic devices, discrete gates or transistor logic devices, discrete hardware components, and more. The general purpose processor may be a microprocessor or the processor or any conventional processor or the like.

The memory 540 can include read only memory and random access memory and provides instructions and data to the processor 530. A portion of the memory 540 may also include a non-volatile random access memory. For example, the memory 540 can also store information of the device type.

In the implementation process, each content of the foregoing method may be completed by an integrated logic circuit of hardware in the processor 530 or an instruction in a form of software. The content of the method disclosed in the embodiments of the present application may be directly implemented as a hardware processor, or may be performed by a combination of hardware and software modules in the processor. The software module can be located in a conventional storage medium such as random access memory, flash memory, read only memory, programmable read only memory or electrically erasable programmable memory, registers, and the like. The storage medium is located in the memory 540, and the processor 530 reads the information in the memory 540 and combines the hardware to complete the contents of the above method. To avoid repetition, it will not be described in detail here.

In a specific implementation, the receiving unit in the network device 300 can be implemented by the input interface 510 in FIG. 7, and the determining unit in the network device 300 can be implemented by the processor 530 in FIG. The transmitting unit in network device 300 can be implemented by output interface 520 in FIG.

As shown in FIG. 8, the embodiment of the present application further provides a terminal device 600, which may be the terminal device 400 in FIG. 6, which can be used to execute the content of the terminal device corresponding to the method 200 in FIG. . The terminal device 600 includes an input interface 610, an output interface 620, a processor 630, and a memory 640. The input interface 610, the output interface 620, the processor 630, and the memory 640 can be connected through a bus system. The memory 640 is used to store programs, instructions or code. The processor 630 is configured to execute a program, an instruction or a code in the memory 640 to control the input interface 610 to receive a signal, control the output interface 620 to send a signal, and complete the operations in the foregoing method embodiments.

Therefore, the terminal device in the embodiment of the present application is advantageous in avoiding waste of resources caused by resource allocation of all data sources of the CG1 and CG2, which are buffered by the PDCP layer, and improves the performance of the uplink authorization.

It should be understood that, in the embodiment of the present application, the processor 630 may be a central processing unit (CPU), and the processor 630 may also be other general-purpose processors, digital signal processors, application specific integrated circuits, and ready-made Program gate arrays or other programmable logic devices, discrete gates or transistor logic devices, discrete hardware components, and more. The general purpose processor may be a microprocessor or the processor or any conventional processor or the like.

The memory 640 can include read only memory and random access memory and provides instructions and data to the processor 630. A portion of the memory 640 can also include a non-volatile random access memory. For example, the memory 640 can also store information of the device type.

In the implementation process, each content of the foregoing method may be completed by an integrated logic circuit of hardware in the processor 630 or an instruction in a form of software. The content of the method disclosed in the embodiments of the present application may be directly implemented as a hardware processor, or may be performed by a combination of hardware and software modules in the processor. The software module can be located in a conventional storage medium such as random access memory, flash memory, read only memory, programmable read only memory or electrically erasable programmable memory, registers, and the like. The storage medium is located in the memory 640, and the processor 630 reads the information in the memory 640 and combines the hardware to complete the contents of the above method. To avoid repetition, it will not be described in detail here.

In a specific embodiment, the transmitting unit in the terminal device 400 can be implemented by the output interface 620 in FIG. The determining unit in the terminal device 400 can be implemented by the processor 630 in FIG. The receiving unit in the terminal device 400 can be implemented by the input interface 610 in FIG.

Those of ordinary skill in the art will appreciate that the elements and algorithm steps of the various examples described in connection with the embodiments disclosed herein can be implemented in electronic hardware or a combination of computer software and electronic hardware. Whether these functions are performed in hardware or software depends on the specific application and design constraints of the solution. A person skilled in the art can use different methods to implement the described functions for each particular application, but such implementation should not be considered to be beyond the scope of the present application.

A person skilled in the art can clearly understand that for the convenience and brevity of the description, the specific working process of the system, the device and the unit described above can refer to the corresponding process in the foregoing method embodiment, and details are not described herein again.

In the several embodiments provided by the present application, it should be understood that the disclosed systems, devices, and methods may be implemented in other manners. For example, the device embodiments described above are merely illustrative. For example, the division of the unit is only a logical function division. In actual implementation, there may be another division manner, for example, multiple units or components may be combined or may be Integrate into another system, or some features can be ignored or not executed. In addition, the mutual coupling or direct coupling or communication connection shown or discussed may be an indirect coupling or communication connection through some interface, device or unit, and may be in an electrical, mechanical or other form.

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

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

This functionality, if implemented as a software functional unit and sold or used as a standalone product, can be stored on a computer readable storage medium. Based on such understanding, the technical solution of the present application, which is essential or contributes to the prior art, or a part of the technical solution, may be embodied in the form of a software product, which is stored in a storage medium, including The instructions are used to cause a computer device (which may be a personal computer, server, or network device, etc.) to perform all or part of the steps of various embodiments of the present application. The foregoing storage medium includes: a U disk, a mobile hard disk, a read-only memory (ROM), a random access memory (RAM), a magnetic disk, or an optical disk, and the like, which can store program codes. .

The foregoing is only a specific embodiment of the present application, but the scope of protection of the present application is not limited thereto, and any person skilled in the art can easily think of changes or substitutions within the technical scope disclosed in the present application. It should be covered by the scope of protection of this application. Therefore, the scope of protection of the present application should be determined by the scope of protection of the claims.

Claims (32)

A method for uplink authorization, which is characterized by comprising: Receiving, by the first network device, a first data amount buffered by the PDCP layer of the packet data convergence protocol of the terminal device in the data volume to be transmitted sent by the terminal device, where the data volume to be transmitted is equal to the first data amount and the terminal device The wireless link controls a sum of a second amount of data buffered by the RLC layer, the second amount of data includes an amount of data waiting to be initially transmitted by the RLC layer buffer, and the terminal device passes the first RLC layer and the first The network device interacts, and the terminal device interacts with the second network device through the second RLC layer. The method according to claim 1, wherein the amount of data waiting for the initial transmission buffered by the RLC layer comprises, before the terminal device receives the uplink grant information sent by the first network device, from the PDCP. Entering, by the layer, the amount of data to be preprocessed in the first RLC layer, and/or entering from the PDCP layer to the first before the terminal device receives the uplink grant information sent by the second network device The amount of data to be preprocessed in the second RLC layer. The method according to claim 1 or 2, wherein the second amount of data comprises a third amount of data buffered by the first RLC layer and a fourth amount of data of the second RLC layer buffer. The method of claim 3, wherein the method further comprises: The first network device sends uplink authorization information to the terminal device, where the uplink authorization information is used to schedule data corresponding to a fifth data amount in the first data amount, and the first data amount The data corresponding to the sixth data amount is scheduled by the second network device, and a sum of the fifth data amount and the sixth data amount is equal to the first data amount. The method according to claim 4, wherein the uplink authorization information is further used to schedule data corresponding to the third amount of data, the method further comprising: The first network device receives the third amount of data sent by the terminal device. The method according to claim 4 or 5, wherein before the first network device sends the uplink authorization information to the terminal device, the method further includes: The first network device negotiates with the second network device to determine the fifth amount of data. The method according to claim 4 or 5, wherein before the first network device sends the uplink authorization information to the terminal device, the method further includes: Determining, by the first network device, the fifth amount of data; The first network device sends the sixth data amount to the second network device. The method according to any one of claims 1 to 7, wherein the amount of data to be transmitted is greater than a threshold. A method for uplink authorization, which is characterized by comprising: The terminal device sends, to the first network device, a first data amount buffered by the packet data convergence protocol PDCP layer of the terminal device in the data volume to be transmitted, where the data volume to be transmitted is equal to the first data amount and the terminal device The wireless link controls a sum of a second amount of data buffered by the RLC layer, the second amount of data includes an amount of data waiting to be initially transmitted in the RLC layer buffer, and the terminal device passes the first RLC layer and the first network The device interacts, and the terminal device interacts with the second network device through the second RLC layer. The method according to claim 9, wherein the amount of data waiting for the initial transmission buffered by the RLC layer comprises, before the terminal device receives the uplink grant information sent by the first network device, from the PDCP. The amount of data that the layer enters into the first RLC layer for pre-processing, and/or from the PDCP layer to the second before the terminal device receives the uplink grant sent by the second network device The amount of data to be preprocessed in the RLC layer. The method according to claim 9 or 10, wherein the second amount of data comprises a third amount of data buffered by the first RLC layer and a fourth amount of data of the second RLC layer buffer. The method of claim 11 wherein the method further comprises: The terminal device receives uplink authorization information sent by the first network device, where the uplink authorization information is used to schedule data corresponding to a fifth data amount in the first data volume, and the first data volume The data corresponding to the sixth data amount is scheduled by the second network device, and the sum of the fifth data amount and the sixth data amount is equal to the first data amount. The method according to claim 11 or 12, wherein the method further comprises: The terminal device sends the third data amount to the first network device. The method of claim 13 wherein the method further comprises: The terminal device receives uplink authorization information sent by the first network device, where the uplink authorization information is used to schedule data corresponding to the third data volume. The method according to any one of claims 11 to 14, wherein the method further comprises: The terminal device sends the first data amount and the fourth data amount to the second network device. The method according to any one of claims 9 to 15, wherein the transmitting, by the terminal device, the first data amount to the first network device comprises: And the terminal device sends the first data amount to the first network device, where the amount of data to be transmitted is greater than a threshold. A network device, where the network device is a first network device, and the network device includes: a receiving unit, configured to receive a first data amount buffered by a packet data convergence protocol PDCP layer of the terminal device in a data volume to be transmitted sent by the terminal device, where the data volume to be transmitted is equal to the first data amount and the terminal The radio link of the device controls a sum of the second data amounts buffered by the RLC layer, the second data amount includes the amount of data waiting to be initially transmitted by the RLC layer buffer, and the terminal device passes the first RLC layer and the first A network device interacts, and the terminal device interacts with the second network device through the second RLC layer. The network device according to claim 17, wherein the amount of data waiting to be initially transmitted by the RLC layer buffer is included before the terminal device receives the uplink grant information sent by the first network device. The amount of data that the PDCP layer enters into the first RLC layer for pre-processing, and/or enters from the PDCP layer before the terminal device receives the uplink grant information sent by the second network device The amount of data to be preprocessed in the second RLC layer. The network device according to claim 17 or 18, wherein the second amount of data comprises a third amount of data buffered by the first RLC layer and a fourth amount of data of the second RLC layer buffer. The network device according to claim 19, wherein the network device further comprises: a sending unit, configured to send, to the terminal device, uplink authorization information, where the uplink authorization information is used to schedule data corresponding to a fifth data quantity in the first data quantity, and a first one of the first data quantity The data corresponding to the six data amounts is scheduled by the second network device, and the sum of the fifth data amount and the sixth data amount is equal to the first data amount. The network device according to claim 20, wherein the uplink grant information is further used to schedule data corresponding to the third amount of data, and the receiving unit is further configured to: Receiving the third amount of data sent by the terminal device. The network device according to claim 20 or 21, wherein the network device further comprises: a determining unit, configured to negotiate with the second network device to determine the fifth amount of data. The network device according to claim 20 or 21, wherein the network device further comprises: a determining unit, configured to determine the fifth amount of data; The sending unit is further configured to: Sending the sixth amount of data to the second network device. The network device according to any one of claims 17 to 23, wherein the amount of data to be transmitted is greater than a threshold. A terminal device, comprising: a sending unit, configured to send, to the first network device, a first data amount of a packet data convergence protocol PDCP layer cache of the terminal device in the data volume to be transmitted, where the data volume to be transmitted is equal to the first data amount and the The radio link of the terminal device controls a sum of the second data amounts buffered by the RLC layer, the second data amount includes an amount of data waiting to be initially transmitted in the RLC layer buffer, and the terminal device passes the first RLC layer and the The first network device interacts, and the terminal device interacts with the second network device through the second RLC layer. The terminal device according to claim 25, wherein the amount of data waiting for the initial transmission buffered by the RLC layer includes, before the terminal device receives the uplink authorization information sent by the first network device, The amount of data that the PDCP layer enters into the first RLC layer for pre-processing, and/or from the PDCP layer to the first before the terminal device receives the uplink grant sent by the second network device The amount of data to be preprocessed in the second RLC layer. The terminal device according to claim 25 or 26, wherein the second data amount comprises a third data amount buffered by the first RLC layer and a fourth data amount buffered by the second RLC layer. The terminal device according to claim 27, wherein the terminal device further comprises: a receiving unit, configured to receive uplink authorization information sent by the first network device, where the uplink authorization information is used to schedule data corresponding to a fifth data quantity in the first data quantity, and the first data quantity The data corresponding to the sixth data amount is scheduled by the second network device, and the sum of the fifth data amount and the sixth data amount is equal to the first data amount. The terminal device according to claim 27 or 28, wherein the sending unit is further configured to: Transmitting the third amount of data to the first network device. The terminal device according to claim 29, wherein the terminal device further comprises: The receiving unit is configured to receive uplink grant information sent by the first network device, where the uplink grant information is used to schedule data corresponding to the third data volume. The terminal device according to any one of claims 27 to 30, wherein the transmitting unit is further configured to: Transmitting the first amount of data and the fourth amount of data to the second network device. The terminal device according to any one of claims 25 to 31, wherein the transmitting unit is specifically configured to: And sending the first data amount to the first network device if the amount of data to be transmitted is greater than a threshold.

Images