WO2024007270A1

WO2024007270A1 - Method and apparatus for determining l2 total buffer size

Info

Publication number: WO2024007270A1
Application number: PCT/CN2022/104473
Authority: WO
Inventors: 乔雪梅
Original assignee: 北京小米移动软件有限公司
Priority date: 2022-07-07
Filing date: 2022-07-07
Publication date: 2024-01-11
Also published as: CN115349273A

Abstract

A method and apparatus for determining an L2 total buffer size, which method and apparatus relate to the technical field of communications. An effective solution is provided for determining an L2 total buffer size for an eRedCap terminal according to peak data rates of the eRedCap terminal, so as to meet the requirement for updating the peak data rates of the eRedCap terminal, thereby saving on costs.

Description

Method and device for determining layer 2 cache size

Technical field

The present application relates to the field of communication technology, and in particular to a method and device for determining the size of a layer 2 cache.

Background technique

For reduced capability (eRedCap) terminals, a possible complexity reduction solution is to limit the transport block size (TransportBlock Size, TBS). This solution is beneficial to the reduction of the buffer size of Hybrid Automatic Repeat Request (HARQ) and the cost of devices such as Low Density Parity Check Code (LDPC) encoding. If TBS is further restricted, the peak data rate of eRedCap needs to be redetermined.

Currently, updates to the peak data rate of eRedCap terminals will affect the calculation of the L2 total buffer size of eRedCap terminals. However, there is currently a lack of effective solutions for determining the L2 buffer size for eRedCap terminals.

Contents of the invention

This application proposes a method and device for determining the size of the layer 2 cache, providing an effective solution for determining the size of the layer 2 cache for eRedCap terminals to meet the peak data rate update requirements of the eRedCap terminal, thereby saving costs.

The first aspect of the embodiment of the present application provides a method for determining the size of the layer 2 cache, which is applied to eRedCap terminal side execution. The method includes: according to the uplink peak data rate and the downlink peak data rate supported by the eRedCap terminal, Determine the layer 2 cache size of the eRedCap endpoint.

In some embodiments of the present application, the method further includes: based on the maximum uplink transmission block size TBS supported by the eRedCap terminal, the duration of the time slot, and the maximum uplink transmission supported by the eRedCap terminal within the time slot. The number of block TBs determines the uplink peak data rate supported by the eRedCap terminal; and, based on the maximum downlink TBS supported by the eRedCap terminal, the duration of the time slot and the number of times the eRedCap terminal performs in the time slot. The maximum number of supported downlink TBs determines the downlink peak data rate supported by the eRedCap terminal; determines the layer 2 of the eRedCap terminal based on the uplink peak data rate and downlink peak data rate supported by the eRedCap terminal. Cache size.

In some embodiments of the present application, the eRedCap is determined based on the maximum uplink TBS supported by the eRedCap terminal, the duration of the time slot, and the maximum number of uplink TBs supported by the eRedCap terminal in the time slot. The peak uplink data rate supported by the terminal includes: multiplying the maximum uplink TBS by the maximum number of uplink TBs, and then dividing by the duration of the time slot to obtain the peak uplink data rate supported by the eRedCap terminal. data rate.

In some embodiments of the present application, the determination is based on the maximum downlink TBS supported by the eRedCap terminal, the duration of the time slot, and the maximum number of downlink TBs supported by the eRedCap terminal in the time slot. The peak data rate of the downlink data of the eRedCap terminal includes: multiplying the maximum downlink TBS by the maximum number of downlink TBs, and then dividing by the duration of the time slot to obtain the peak downlink rate supported by the eRedCap terminal. data rate.

In some embodiments of the present application, the method further includes: obtaining a first scaling coefficient of the physical uplink shared channel PUSCH and a second scaling coefficient of the physical downlink shared channel PDSCH, wherein the first scaling coefficient and the third scaling coefficient The two scaling coefficients are both greater than 0 and less than 1; determine the uplink peak data rate supported by the eRedCap terminal according to the uplink peak data rate supported by the traditional terminal and the first scaling coefficient; and, according to the The peak downlink data rate supported by the traditional terminal and the second scaling factor determine the peak downlink data rate supported by the eRedCap terminal.

In some embodiments of the present application, determining the uplink peak data rate supported by the eRedCap terminal based on the uplink peak data rate supported by the traditional terminal and the first scaling factor includes: The uplink peak data rate supported by the traditional terminal is multiplied by the first scaling factor to obtain the uplink peak data rate supported by the eRedCap terminal.

In some embodiments of the present application, determining the downlink peak data rate supported by the eRedCap terminal based on the downlink peak data rate supported by the traditional terminal and the second scaling factor includes: The downlink peak data rate supported by the traditional terminal is multiplied by the second scaling factor to obtain the downlink peak data rate supported by the eRedCap terminal.

In some embodiments of the present application, the method further includes: obtaining the uplink peak data rate supported by the eRedCap terminal with reduced capabilities specified in the communication protocol; and obtaining the downlink supported by the eRedCap terminal specified in the communication protocol. the peak data rate of the eRedCap terminal; determine the layer 2 cache size of the eRedCap terminal based on the peak data rate of the upstream and the peak data rate of the downstream data supported by the eRedCap terminal.

In some embodiments of the present application, determining the layer 2 cache size of the eRedCap terminal based on the uplink peak data rate and downlink peak data rate supported by the eRedCap terminal includes: The result obtained by multiplying the data rate by the round-trip delay RLC RTT of the wireless link control layer is added to the result obtained by multiplying the downlink peak data rate by the RLC RTT to obtain the layer 2 cache size of the eRedCap terminal.

The second aspect of the embodiment of the present application provides a method for determining the layer 2 cache size, which is applied to the base station side. The method includes: determining based on the uplink peak data rate and the downlink peak data rate supported by the eRedCap terminal. Layer 2 cache size of the eRedCap endpoint.

The third aspect embodiment of the present application provides a device for determining the size of the layer 2 cache, which is applied to the eRedCap terminal side. The device includes: a determining unit configured to determine the uplink peak data rate and downlink data rate supported by the eRedCap terminal. The peak data rate determines the Layer 2 cache size of the eRedCap endpoint.

The fourth aspect embodiment of the present application provides a device for determining the layer 2 cache size, which is applied to the base station side. The device includes: a determining unit configured to determine the uplink peak data rate and the downlink peak data rate based on the uplink peak data rate supported by the eRedCap terminal. The data rate determines the Layer 2 cache size of the eRedCap endpoint.

The fifth aspect embodiment of the present application provides a communication device, which is applied to the eRedCap terminal side. The communication device includes: a transceiver; a memory; and a processor, which is connected to the transceiver and the memory respectively, and is configured to execute a computer on the memory. The instructions can be executed to control the wireless signal transmission and reception of the transceiver, and can implement the method according to the embodiment of the first aspect of the present application.

The sixth aspect embodiment of the present application provides a communication device, which is applied to the base station side. The communication device includes: a transceiver; a memory; and a processor, which is connected to the transceiver and the memory respectively, and is configured to execute a computer on the memory. The instructions are executed to control the wireless signal transmission and reception of the transceiver, and can implement the method as in the embodiment of the second aspect of the present application.

The seventh embodiment of the present application provides a computer storage medium, which is applied to the eRedCap terminal side, in which the computer storage medium stores computer executable instructions; after the computer executable instructions are executed by the processor, the computer executable instructions can be implemented as described in the first aspect of the present application. Methods of embodiments in one aspect.

The eighth embodiment of the present application provides a computer storage medium, which is applied to the base station side, wherein the computer storage medium stores computer executable instructions; after the computer executable instructions are executed by the processor, the second step of the present application can be implemented. Methods of Aspect Embodiments.

The embodiments of the present application provide a method and device for determining the layer 2 cache size, which can provide an effective solution for determining the layer 2 cache size for the eRedCap terminal in response to the peak data rate of the eRedCap terminal, so as to meet the peak data rate of the eRedCap terminal. Update needs (to meet the needs of TBS being further restricted), thereby saving costs.

Additional aspects and advantages of the application will be set forth in part in the description which follows, and in part will be obvious from the description, or may be learned by practice of the application.

Description of the drawings

The above and/or additional aspects and advantages of the present application will become apparent and readily understood from the following description of the embodiments in conjunction with the accompanying drawings, in which:

Figure 1 is a schematic flowchart of a method for determining the size of a layer 2 cache according to an embodiment of the present application;

Figure 2 is a schematic flowchart of a method for determining the size of a layer 2 cache according to an embodiment of the present application;

Figure 3 is a schematic flowchart of a method for determining the size of a layer 2 cache according to an embodiment of the present application;

Figure 4 is a schematic flowchart of a method for determining the size of a layer 2 cache according to an embodiment of the present application;

Figure 5 is a schematic flowchart of a method for determining the size of a layer 2 cache according to an embodiment of the present application;

Figure 6 is a schematic flowchart of a method for determining the size of a layer 2 cache according to an embodiment of the present application;

Figure 7 is a schematic flowchart of a method for determining the size of a layer 2 cache according to an embodiment of the present application;

Figure 8 is a schematic flowchart of a method for determining the size of the layer 2 cache according to an embodiment of the present application;

Figure 9 is a schematic flowchart of a method for determining the size of a layer 2 cache according to an embodiment of the present application;

Figure 10 is a block diagram of a device for determining layer 2 cache size according to an embodiment of the present application;

Figure 11 is a block diagram of a device for determining the size of a layer 2 cache according to an embodiment of the present application;

Figure 12 is a block diagram of a device for determining the size of a layer 2 cache according to an embodiment of the present application;

Figure 13 is a schematic structural diagram of a communication device according to an embodiment of the present application;

Figure 14 is a schematic structural diagram of a chip provided by an embodiment of the present application.

Detailed ways

The embodiments of the present application are described in detail below. Examples of the embodiments are shown in the accompanying drawings, wherein the same or similar reference numerals throughout represent the same or similar elements or elements with the same or similar functions. The embodiments described below with reference to the drawings are exemplary and are intended to explain the present application, but should not be construed as limiting the present application. It should be noted that, as long as there is no conflict, the embodiments of the present application and the features in the embodiments can be combined with each other.

The terms used in the embodiments of the present application are only for the purpose of describing specific embodiments and are not intended to limit the embodiments of the present application. As used in the embodiments and the appended claims, the singular forms "a", "an" and "the" are intended to include the plural forms as well, unless the context clearly dictates otherwise. It will also be understood that the term "and/or" as used herein refers to and includes any and all possible combinations of one or more of the associated listed items.

It should be understood that although the terms first, second, third, etc. may be used to describe various information in the embodiments of this application, the information should not be limited to these terms. These terms are only used to distinguish information of the same type from each other. For example, without departing from the scope of the embodiments of the present application, the first information may also be called second information, and similarly, the second information may also be called first information. Depending on the context, the word "if" as used herein may be interpreted as "when" or "when" or "in response to determining."

To facilitate understanding, the terminology involved in this embodiment is first introduced.

1. Physical Uplink Shared Channel (PUSCH)

As the main uplink data bearing channel of the physical layer, PUSCH is used for the transmission of uplink data and can carry control information, user service information, broadcast service information, etc.

2. Physical Downlink Shared Channel (PDSCH)

PDSCH is used to carry data from the transmission downlink shared channel (Downlink Shared Channel, DSCH).

3. eRedCap terminal

The 3rd Generation Partnership Project (3GPP) established a special standards project in the communication protocol version 17 (release17, Rel-17) stage to analyze and optimize the functional characteristics of existing 5G terminals and networks to implement 5G IoT terminals access the 5G core network through 5G New Radio (NR). In this standard project, 3GPP proposed NR equipment that supports reduced capability (Reduced Capability), also known as RedCap terminal. Compared with traditional enhanced mobile broadband (eMBB) equipment and ultra-reliable and low latency communication (URLLC) equipment, RedCap terminal equipment has lower cost, lower complexity, and more compact size , performance and other advantages. The eRedCap terminal is based on the RedCap terminal, further reducing terminal costs to support lower-speed 5G IoT terminals using NR technology.

Currently for eRedCap terminals, a possible complexity-reducing solution is to limit TBS. This solution is beneficial to reducing the cost of HARQbuffersize, LDPC encoding and other devices. If TBS is further restricted, the peak data rate of traditional terminals as a constraint for TBS will no longer apply. Therefore, the peak data rate needs to be re-determined for the eRedCap terminal, and the update of the peak data rate of the eRedCap terminal will affect the calculation of the L2 total buffer size (layer 2 cache size) of the eRedCap terminal. However, there is currently a lack of determination of L2 for the eRedCap terminal. Effective solution for total buffer size.

To this end, this embodiment proposes a method and device for determining the size of the layer 2 cache, and provides an effective solution for determining the L2 total buffer size for the eRedCap terminal to meet the update requirements of the peak data rate of the eRedCap terminal.

The method and device for determining the size of the layer 2 cache provided by this application will be introduced in detail below with reference to the accompanying drawings.

Figure 1 shows a schematic flowchart of a method for determining the size of a layer 2 cache according to an embodiment of the present application. As shown in Figure 1, it can be applied to the eRedCap terminal side or the base station side, and may include the following steps.

Step 101: Determine the layer 2 cache size of the eRedCap terminal based on the uplink peak data rate and downlink peak data rate supported by the eRedCap terminal.

By applying the method for determining the layer 2 cache size provided in this embodiment, the layer 2 cache size of the eRedCap terminal can be determined based on the uplink peak data rate and the downlink peak data rate supported by the eRedCap terminal, and thus the eRedCap terminal can be provided with Peak data rate, an effective solution to determine the layer 2 cache size for eRedCap terminals to meet the update needs of the peak data rate of eRedCap terminals (to meet the need for TBS to be further restricted), thereby saving costs.

Figure 2 shows a schematic flowchart of a method for determining the size of a layer 2 cache according to an embodiment of the present application. Based on the embodiment shown in Figure 1, as shown in Figure 2, it can be applied to the eRedCap terminal side or to the base station side, and the method can include the following steps.

Step 201: Determine the uplink peak data rate supported by the eRedCap terminal based on the maximum uplink TBS supported by the eRedCap terminal, the duration of a time slot, and the maximum number of uplink TBs supported by the eRedCap terminal in the time slot, and based on The maximum downlink TBS supported by the eRedCap terminal, the duration of a time slot, and the maximum number of downlink TBs supported by the eRedCap terminal in the time slot determine the peak downlink data rate supported by the eRedCap terminal.

The maximum uplink TBS and maximum downlink TBS supported by the eRedCap terminal can be obtained from the communication protocol. For example, the maximum uplink TBS (transmission block size) supported by the eRedCap terminal can be directly specified in the communication protocol as U bits (number of bits) , and directly stipulate in the communication protocol that the maximum downlink TBS supported by the eRedCap terminal is D bits. These contents can be preset in the communication protocol.

For example, based on the maximum uplink TBS (U bits) supported by the eRedCap terminal, slot duration (duration of the time slot), and the maximum number of uplink TBs supported by the eRedCap terminal in the slot specified in the communication protocol, the eRedCap terminal is calculated. The supported uplink peak data rate (peak data rate); and the maximum downlink TBS (D bits) supported by the eRedCap terminal according to the communication protocol, slot duration (duration of the time slot), and the eRedCap terminal supported within the slot The maximum number of downstream TBs is calculated to obtain the peak data rate of the downstream supported by the eRedCap terminal.

Step 202: Determine the layer 2 cache size of the eRedCap terminal based on the uplink peak data rate and the downlink peak data rate supported by the eRedCap terminal.

By applying the method for determining the layer 2 cache size provided in this embodiment, the maximum uplink TBS supported by the eRedCap terminal specified in the communication protocol, the duration of a time slot, and the maximum uplink supported by the eRedCap terminal in the time slot can be determined. The number of TBs determines the uplink peak data rate supported by the eRedCap terminal, as well as the maximum downlink TBS supported by the eRedCap terminal as specified in the communication protocol, the duration of a time slot, and the eRedCap terminal supports in the time slot. The maximum number of downstream TBs determines the peak data rate of the downstream supported by the eRedCap terminal. Then, determine the L2 total buffer size of the eRedCap terminal based on the upstream peak data rate and downstream peak data rate supported by the eRedCap terminal. Thus, an effective solution for L2 total buffer size is determined for the eRedCap terminal to meet the update requirements of the peak data rate of the eRedCap terminal and save costs.

Figure 3 shows a schematic flowchart of a method for determining the size of a layer 2 cache according to an embodiment of the present application. Based on the embodiment shown in Figure 2, as shown in Figure 3, it can be applied to the eRedCap terminal side or to the base station side, and the method can include the following steps.

Step 301: Obtain the maximum uplink TBS supported by the eRedCap terminal, and obtain the maximum downlink TBS supported by the eRedCap terminal.

Step 302: Multiply the maximum uplink TBS supported by the eRedCap terminal by the maximum number of uplink TBs supported by the eRedCap terminal in one time slot, and then divide it by the duration of the time slot to obtain the uplink peak data supported by the eRedCap terminal. rate, and multiply the maximum downlink TBS supported by the eRedCap terminal by the maximum number of downlink TBs supported by the eRedCap terminal in a time slot, and then divide it by the duration of the time slot to obtain the downlink peak data supported by the eRedCap terminal. rate.

For example, determine the upstream peak data rate (peak data rate) supported by the eRedCap terminal in the TS38.306 protocol, as shown in the following formula 1:

The upstream peak data rate supported by the eRedCap terminal=U*M1/T_slot (Formula 1)

In Formula 1, U is the maximum upstream TBS supported by the eRedCap terminal, M1 is the maximum number of upstream TBs that the eRedCap terminal transmits or can support transmission in one slot, and T_slot is the duration in the slot.

Determine the downlink peak data rate (peak data rate) supported by the eRedCap terminal in the TS38.306 protocol, as shown in the following formula 2:

Downstream peak data rate supported by eRedCap terminal=D*M2/T_slot (Formula 2)

In Formula 2, D is the maximum downlink TBS supported by the eRedCap terminal, M2 is the maximum number of downlink TBs that the eRedCap terminal transmits or can support transmission in one slot, and T_slot is the duration in the slot.

Step 303: Determine the layer 2 cache size of the eRedCap terminal based on the uplink peak data rate and downlink peak data rate supported by the eRedCap terminal.

It should be noted that although the embodiment shown in Fig. 3 is described based on the embodiment shown in Fig. 1, similarly, the embodiment shown in Fig. 3 can also be based on the embodiment shown in Fig. 2, which will not be discussed here. Elaborate.

By applying the method for determining the size of the layer 2 cache provided in this embodiment, the maximum uplink TBS supported by the eRedCap terminal can be multiplied by the maximum number of uplink TBs supported by the eRedCap terminal in a time slot, and then divided by the maximum number of uplink TBs supported by the eRedCap terminal in a time slot. The duration is obtained by obtaining the uplink peak data rate supported by the eRedCap terminal, and multiplying the maximum downlink TBS supported by the eRedCap terminal by the maximum number of downlink TBs supported by the eRedCap terminal in a time slot, and then dividing by the time slot The duration is the downstream peak data rate supported by the eRedCap terminal. Then, determine the L2 total buffer size of the eRedCap terminal based on the upstream peak data rate and downstream peak data rate supported by the eRedCap terminal. Thus, an effective solution for L2 total buffer size is determined for the eRedCap terminal to meet the update requirements of the peak data rate of the eRedCap terminal and save costs.

Figure 4 shows a schematic flowchart of a method for determining the size of a layer 2 cache according to an embodiment of the present application. Based on the embodiment shown in Figure 2, as shown in Figure 4, it can be applied to the eRedCap terminal side or to the base station side, and the method can include the following steps.

Step 401: Obtain the maximum uplink TBS supported by the eRedCap terminal, and obtain the maximum downlink TBS supported by the eRedCap terminal.

Step 402: Determine the uplink peak data rate supported by the eRedCap terminal based on the maximum uplink TBS supported by the eRedCap terminal, the duration of a time slot, and the maximum number of uplink TBs supported by the eRedCap terminal in the time slot, and based on The maximum downlink TBS supported by the eRedCap terminal, the duration of a time slot, and the maximum number of downlink TBs supported by the eRedCap terminal in the time slot determine the peak downlink data rate supported by the eRedCap terminal.

Step 403: Multiply the uplink peak data rate supported by the eRedCap terminal by the RLC RTT, and add the downlink peak data rate supported by the eRedCap terminal multiplied by the RLC RTT to obtain the layer 2 of the eRedCap terminal. Cache size.

Among them, RLC RTT is the round-trip time delay (Round-Trip Time, RTT) of the wireless link control layer (Radio Link Control, RLC). For example, the L2 total buffer size of the eRedCap terminal is calculated through Formula 5.

L2 total buffer size＝MaxULdatarate*RLC RTT+MaxDLdatarate*RLC RTT (Formula 3)

In Formula 3, MaxULdatarate is the upstream peak data rate supported by eRedCap terminals, and MaxDLdatarate is the downstream peak data rate supported by eRedCap terminals.

It should be noted that although the embodiment shown in Fig. 4 is described based on the embodiment shown in Fig. 2, similarly, the embodiment shown in Fig. 4 can also be based on the embodiment shown in Fig. 3, which will not be discussed here. Elaborate.

By applying the method provided in this embodiment, the result obtained by multiplying the uplink peak data rate supported by the eRedCap terminal by the RLC RTT is added to the result obtained by multiplying the downlink peak data rate supported by the eRedCap terminal by the RLC RTT. Gets the layer 2 cache size of the eRedCap terminal. Then, determine the L2 total buffer size of the eRedCap terminal based on the upstream peak data rate and downstream peak data rate supported by the eRedCap terminal. Thus, an effective solution for L2 total buffer size is determined for the eRedCap terminal to meet the update requirements of the peak data rate of the eRedCap terminal and save costs.

Figure 5 is a schematic flowchart of a method for determining the size of a layer 2 cache according to an embodiment of the present application. Based on the embodiment shown in Figure 1, as shown in Figure 5, it can be applied to the eRedCap terminal side or to the base station side, and the method can include the following steps.

Step 501: Obtain the first scaling coefficient of the PUSCH channel and the second scaling coefficient of the PDSCH channel.

Wherein, both the first scaling coefficient and the second scaling coefficient may be greater than 0 and less than 1. The first scaling factor and the second scaling factor can be obtained through the communication protocol or determined by the terminal and reported to the base station. Optionally, the maximum uplink TBS supported by the eRedCap terminal specified in the communication protocol is the maximum uplink supported by the traditional terminal. The TBS is multiplied by the first scaling factor, and the maximum downlink TBS supported by the eRedCap terminal is the maximum downlink TBS supported by the legacy terminal multiplied by the second scaling factor.

For example, it can be specified in the communication protocol that the maximum uplink TBS supported by the eRedCap terminal is the maximum uplink TBS supported by the traditional terminal multiplied by a first scaling factor, and the first scaling factor can be 1/A1, A1>1; and in communication The agreement stipulates that the maximum downlink TBS supported by eRedCap terminals is the maximum downlink TBS supported by traditional terminals multiplied by a second scaling factor. The second scaling factor can be 1/A2, A2>1. Through this specified content, the first scaling coefficient 1/A1 of PUSCH and the second scaling coefficient 1/A2 of PDSCH can be obtained. The PDSCH channel and the PUSCH channel can have different scaling coefficients, that is, 1/A1 and 1/A2 can is different.

Step 502: Determine the uplink peak data rate supported by the eRedCap terminal based on the uplink peak data rate supported by the traditional terminal and the first scaling coefficient of the PUSCH channel, and determine the downlink peak data rate supported by the traditional terminal based on the PDSCH channel The second scaling factor determines the downlink peak data rate supported by the eRedCap terminal.

For example, determine the uplink peak data rate supported by the eRedCap terminal based on the uplink peak data rate (peak data rate) supported by the traditional terminal (different from the eRedCap terminal) and the first scaling coefficient 1/A1 (A1>1) of the PUSCH channel. data rate, and determine the downlink peak data rate supported by the eRedCap terminal based on the downlink peak data rate supported by the traditional terminal and the second scaling coefficient 1/A2 (A2>1) of the PDSCH channel.

Step 503: Determine the layer 2 cache size of the eRedCap terminal based on the uplink peak data rate and downlink peak data rate supported by the eRedCap terminal.

By applying the method for determining the layer 2 cache size provided by this embodiment, the uplink peak data rate supported by the eRedCap terminal can be determined based on the uplink peak data rate supported by the traditional terminal and the first scaling coefficient of the PUSCH channel, and based on The downlink peak data rate supported by the traditional terminal and the second scaling coefficient of the PDSCH channel determine the downlink peak data rate supported by the eRedCap terminal. Then, determine the L2 total buffer size of the eRedCap terminal based on the upstream peak data rate and downstream peak data rate supported by the eRedCap terminal. Thus, an effective solution for L2 total buffer size is determined for the eRedCap terminal to meet the update requirements of the peak data rate of the eRedCap terminal and save costs.

Figure 6 is a schematic flowchart of a method for determining the size of a layer 2 cache according to an embodiment of the present application. Based on the embodiment shown in Figure 5, as shown in Figure 6, it can be applied to the eRedCap terminal side or the base station side, and can include the following steps.

Step 601: Obtain the first scaling coefficient of the PUSCH channel and the second scaling coefficient of the PDSCH channel.

Wherein, the first scaling coefficient and the second scaling coefficient are both greater than 0 and less than 1.

Step 602: Multiply the peak uplink data rate supported by the traditional terminal by the first scaling coefficient of the PUSCH channel to obtain the peak uplink data rate supported by the eRedCap terminal, and multiply the peak downlink data rate supported by the traditional terminal by The second scaling coefficient of the PDSCH channel is used to obtain the downlink peak data rate supported by the eRedCap terminal.

For example, multiply the uplink peak data rate (peak data rate) supported by traditional terminals by the first scaling coefficient 1/A1 (A1>1) of the PUSCH channel to obtain the uplink peak data rate supported by eRedCap terminals, and The downlink peak data rate supported by the traditional terminal is multiplied by the second scaling coefficient of the PDSCH channel 1/A2 (A2>1) to obtain the downlink peak data rate supported by the eRedCap terminal.

Step 603: Determine the layer 2 cache size of the eRedCap terminal based on the uplink peak data rate and the downlink peak data rate supported by the eRedCap terminal.

By applying the method provided by this embodiment, the uplink peak data rate determination formula supported by the traditional terminal can be multiplied by the first scaling coefficient of the PUSCH channel to obtain the uplink peak data rate supported by the eRedCap terminal, and the uplink peak data rate supported by the traditional terminal can be obtained The supported downlink peak data rate determination formula is multiplied by the second scaling factor of the PDSCH channel to obtain the downlink peak data rate supported by the eRedCap terminal. Then, determine the L2 total buffer size of the eRedCap terminal based on the upstream peak data rate and downstream peak data rate supported by the eRedCap terminal. Thus, an effective solution for L2 total buffer size is determined for the eRedCap terminal to meet the update requirements of the peak data rate of the eRedCap terminal and save costs.

Figure 7 shows a schematic flowchart of a method for determining the size of a layer 2 cache according to an embodiment of the present application. Based on the embodiment shown in Figure 5, as shown in Figure 7, it can be applied to the eRedCap terminal side or to the base station side, and the method can include the following steps.

Step 701: Obtain the first scaling coefficient of the PUSCH channel and the second scaling coefficient of the PDSCH channel.

Wherein, both the first scaling coefficient and the second scaling coefficient may be greater than 0 and less than 1.

Step 702: Determine the uplink peak data rate supported by the eRedCap terminal based on the uplink peak data rate supported by the traditional terminal and the first scaling coefficient of the PUSCH channel, and determine the downlink peak data rate supported by the traditional terminal based on the PDSCH channel The second scaling factor determines the downlink peak data rate supported by the eRedCap terminal.

Step 703: Multiply the uplink peak data rate supported by the eRedCap terminal by the RLC RTT, and add the downlink peak data rate supported by the eRedCap terminal multiplied by the RLC RTT to obtain layer 2 of the eRedCap terminal. Cache size.

Among them, RLC RTT is the round-trip delay of the wireless link control layer. For example, the L2 total buffer size of the eRedCap terminal is calculated through Formula 3 (see Formula 3 in step 403).

It should be noted that although the embodiment shown in Fig. 7 is described based on the embodiment shown in Fig. 5, similarly, the embodiment shown in Fig. 7 can also be based on the embodiment shown in Fig. 6, which will not be discussed here. Elaborate.

Figure 8 shows a schematic flowchart of a method for determining the size of a layer 2 cache according to an embodiment of the present application. Based on the embodiment shown in Figure 1, as shown in Figure 8, it can be applied to the eRedCap terminal side or to the base station side, and can include the following steps.

Step 801: Obtain the uplink peak data rate supported by the eRedCap terminal specified in the communication protocol, and obtain the downlink peak data rate supported by the eRedCap terminal specified in the communication protocol.

For example, the specific value of the peak data rate of the eRedCap terminal can be directly specified in the communication protocol, and different values can be set for the upstream and downstream. Then the upstream peak data rate supported by the eRedCap terminal specified in the communication protocol can be obtained as the upstream peak data rate supported by the eRedCap terminal, and the downlink peak data rate supported by the eRedCap terminal specified in the communication protocol can be obtained as The downstream peak data rate supported by eRedCap terminal.

Step 802: Determine the layer 2 cache size of the eRedCap terminal based on the uplink peak data rate and the downlink peak data rate supported by the eRedCap terminal.

By applying the method for determining the size of the layer 2 cache provided by this embodiment, the upstream peak data rate supported by the eRedCap terminal specified in the communication protocol can be obtained, as the upstream peak data rate supported by the eRedCap terminal, and the upstream peak data rate in the communication protocol can be obtained The specified downstream peak data rate supported by the eRedCap terminal is used as the downstream peak data rate supported by the eRedCap terminal. Then, determine the L2 total buffer size of the eRedCap terminal based on the upstream peak data rate and downstream peak data rate supported by the eRedCap terminal. Thus, an effective solution for L2 total buffer size is determined for the eRedCap terminal to meet the update requirements of the peak data rate of the eRedCap terminal and save costs.

Figure 9 shows a schematic flowchart of a method for determining the size of a layer 2 cache according to an embodiment of the present application. Based on the embodiment shown in Figure 8, as shown in Figure 9, it can be applied to the eRedCap terminal side or to the base station side, and the method can include the following steps.

Step 901: Obtain the uplink peak data rate supported by the eRedCap terminal specified in the communication protocol, and obtain the downlink peak data rate supported by the eRedCap terminal specified in the communication protocol.

Step 902: Multiply the uplink peak data rate supported by the eRedCap terminal by the RLC RTT, and add the downlink peak data rate supported by the eRedCap terminal multiplied by the RLC RTT to obtain layer 2 of the eRedCap terminal. Cache size.

By applying the method for determining the size of the layer 2 cache provided by this embodiment, the upstream peak data rate supported by the eRedCap terminal is multiplied by the RLC RTT, plus the downlink peak data rate supported by the eRedCap terminal multiplied by the RLC The result obtained by RTT is the layer 2 cache size of the eRedCap terminal. Then, determine the L2 total buffer size of the eRedCap terminal based on the upstream peak data rate and downstream peak data rate supported by the eRedCap terminal. Thus, an effective solution for L2 total buffer size is determined for the eRedCap terminal to meet the update requirements of the peak data rate of the eRedCap terminal and save costs.

The above methods shown in Figures 2 to 4 are to determine the uplink TBS supported by the eRedCap terminal based on the maximum uplink TBS supported by the eRedCap terminal, the duration of the time slot, and the maximum number of uplink TBs supported by the eRedCap terminal in the time slot. The peak data rate, and the peak downlink data rate supported by the eRedCap terminal can be determined based on the maximum downlink TBS supported by the eRedCap terminal, the duration of the time slot, and the maximum number of downlink TBs supported by the eRedCap terminal in the time slot. The layer 2 cache size of the eRedCap terminal is then determined based on the peak data rate of the upstream and the peak data rate of the downstream. The above methods shown in Figures 5 to 7 are to determine the uplink peak data supported by the eRedCap terminal based on the uplink peak data rate supported by the traditional terminal and the first scaling coefficient 1/A1 (A1>1) of the PUSCH channel. rate, and determine the downlink peak data rate supported by the eRedCap terminal based on the downlink peak data rate supported by the traditional terminal and the second scaling factor 1/A2 (A2>1) of the PDSCH channel, and then determine the uplink peak data rate through and the downstream peak data rate determine the Layer 2 cache size of the eRedCap terminal. The above method shown in Figures 8 to 9 is to obtain the uplink peak data rate supported by the eRedCap terminal specified in the communication protocol, and obtain the downlink peak data rate supported by the eRedCap terminal specified in the communication protocol, and then use the uplink The peak data rate and the peak downstream data rate determine the Layer 2 cache size of the eRedCap terminal.

It should be noted that the above methods can also be comprehensively analyzed according to actual needs in actual use to determine the layer 2 cache size of the eRedCap terminal. For example, the corresponding priorities are pre-configured, and then based on the priorities, the determination method with the highest priority is selected to obtain the layer 2 cache size of the eRedCap terminal; for another example, the weighted average calculation method can be used to calculate these determination methods to obtain The weighted average calculation is performed on the results to determine the layer 2 cache size of the eRedCap terminal, etc.

In the above embodiments provided by the present application, the methods provided by the embodiments of the present application are introduced from the perspectives of network equipment and user equipment respectively. In order to implement each function in the method provided by the above embodiments of the present application, network equipment and user equipment may include hardware structures and software modules to implement the above functions in the form of hardware structures, software modules, or hardware structures plus software modules. A certain function among the above functions can be executed by a hardware structure, a software module, or a hardware structure plus a software module.

Corresponding to the methods for determining the size of the layer 2 cache provided by the above embodiments, this application also provides a device for determining the size of the layer 2 cache, which can be applied to eRedCap terminals or to the base station side. The device can include: a determination module , used to determine the layer 2 cache size of the eRedCap terminal based on the uplink peak data rate and downlink peak data rate supported by the eRedCap terminal. Since the device for determining the size of the layer 2 cache provided by the embodiment of the present application corresponds to the method for determining the size of the layer 2 cache provided by the above-mentioned embodiments, the implementation of the method for determining the size of the layer 2 cache is also applicable to the method provided by this embodiment. The device for determining the layer 2 cache size will not be described in detail in this embodiment.

Figure 10 is a schematic structural diagram of a device for determining the size of a layer 2 cache provided by an embodiment of the present application. As shown in Figure 9, the device may specifically include: a first acquisition module 1010, configured to determine the size of a layer 2 cache according to the maximum size supported by the eRedCap terminal. The uplink transmission block size TBS, the duration of the time slot and the maximum number of uplink transmission blocks TB supported by the eRedCap terminal in the time slot determine the uplink peak data rate supported by the eRedCap terminal; and, based on the maximum number of uplink transmission blocks supported by the eRedCap terminal; and The downlink TBS, the duration of the time slot and the maximum number of downlink TBs supported by the eRedCap terminal in the time slot are used to determine the downlink peak data rate supported by the eRedCap terminal; the first determination module 1020 is used to determine the downlink peak data rate supported by the eRedCap terminal. The peak upstream data rate and the peak downstream data rate determine the layer 2 cache size of the eRedCap terminal.

In some embodiments, the first acquisition module 1010 is specifically configured to multiply the maximum uplink TBS by the maximum number of uplink TBs, and then divide it by the duration of the time slot to obtain the uplink peak data rate supported by the eRedCap terminal.

In some embodiments, the first acquisition module 1010 is specifically configured to multiply the maximum downlink TBS by the maximum number of downlink TBs, and then divide it by the duration of the time slot to obtain the downlink peak data rate supported by the eRedCap terminal.

In some embodiments, the first determination module 1020 is specifically configured to multiply the uplink peak data rate by the round-trip delay RLC RTT of the wireless link control layer, plus the downlink peak data rate multiplied by the RLC RTT. The result obtained is the layer 2 cache size of the eRedCap terminal.

By applying the solution provided by this embodiment, the eRedCap terminal can be determined based on the maximum uplink TBS supported by the eRedCap terminal, the duration of the time slot, and the maximum number of uplink TBs supported by the eRedCap terminal in the time slot specified in the communication protocol. The supported uplink peak data rate, and the maximum downlink TBS supported by the eRedCap terminal specified in the communication protocol, the duration of the time slot, and the maximum number of downlink TBs supported by the eRedCap terminal in the time slot can be determined. Supported downstream peak data rate. Then, determine the L2 total buffer size of the eRedCap terminal based on the upstream peak data rate and downstream peak data rate supported by the eRedCap terminal. Thus, an effective solution for L2 total buffer size is determined for the eRedCap terminal to meet the update requirements of the peak data rate of the eRedCap terminal and save costs.

FIG. 11 is a schematic structural diagram of a device for determining the size of a layer 2 cache provided by an embodiment of the present application. As shown in Figure 11, the device may specifically include: a second acquisition module 1110, configured to acquire the first scaling coefficient of the physical uplink shared channel PUSCH and the second scaling coefficient of the physical downlink shared channel PDSCH, where the first scaling coefficient and The second scaling factors are all greater than 0 and less than 1; determine the uplink peak data rate supported by the eRedCap terminal based on the uplink peak data rate supported by the traditional terminal and the first scaling factor; and based on the downlink peak data rate supported by the traditional terminal The data rate and the second scaling coefficient determine the downlink peak data rate supported by the eRedCap terminal; the second determination module 1120 is used to determine the eRedCap terminal based on the uplink peak data rate and downlink peak data rate supported by the eRedCap terminal. Tier 2 cache size.

In some embodiments, the second acquisition module 1110 is specifically configured to multiply the uplink peak data rate supported by the traditional terminal by the first scaling factor to obtain the uplink peak data rate supported by the eRedCap terminal.

In some embodiments, the second acquisition module 1110 is specifically configured to multiply the downlink peak data rate supported by the traditional terminal by the second scaling factor to obtain the downlink peak data rate supported by the eRedCap terminal.

In some embodiments, the second determination module 1120 is specifically configured to multiply the uplink peak data rate by the round-trip delay RLC RTT of the wireless link control layer, plus the downlink peak data rate multiplied by the RLC RTT. The result obtained is the layer 2 cache size of the eRedCap terminal.

By applying the solution provided by this embodiment, the uplink peak data rate supported by the eRedCap terminal can be determined based on the uplink peak data rate supported by the traditional terminal and the first scaling coefficient of the PUSCH channel, and the uplink peak data rate supported by the traditional terminal can be determined based on the downlink peak data rate supported by the traditional terminal. The peak data rate and the second scaling coefficient of the PDSCH channel determine the downlink peak data rate supported by the eRedCap terminal. Then, determine the L2 total buffer size of the eRedCap terminal based on the upstream peak data rate and downstream peak data rate supported by the eRedCap terminal. Thus, an effective solution for L2 total buffer size is determined for the eRedCap terminal to meet the update requirements of the peak data rate of the eRedCap terminal and save costs.

Figure 12 is a schematic structural diagram of a device for determining the size of a layer 2 cache provided by an embodiment of the present application. As shown in Figure 12, the device may include: a third acquisition module 1210, used to acquire the uplink peak data rate supported by the eRedCap terminal specified in the communication protocol; and, acquire the downlink supported by the eRedCap terminal specified in the communication protocol. The peak data rate; the third determination module 1220 is used to determine the layer 2 cache size of the eRedCap terminal based on the peak data rate of the upstream and the peak data rate of the downstream data supported by the eRedCap terminal.

In some embodiments, the third determination module 1220 is specifically configured to multiply the uplink peak data rate by the round-trip delay RLC RTT of the wireless link control layer, plus the downlink peak data rate multiplied by the RLC RTT. The result obtained is the layer 2 cache size of the eRedCap terminal.

By applying the solution provided by this embodiment, the upstream peak data rate supported by the eRedCap terminal specified in the communication protocol can be obtained as the upstream peak data rate supported by the eRedCap terminal, and the upstream peak data rate supported by the eRedCap terminal specified in the communication protocol can be obtained The downstream peak data rate is the downstream peak data rate supported by the eRedCap terminal. Then, determine the L2 total buffer size of the eRedCap terminal based on the upstream peak data rate and downstream peak data rate supported by the eRedCap terminal. Thus, an effective solution for L2 total buffer size is determined for the eRedCap terminal to meet the update requirements of the peak data rate of the eRedCap terminal and save costs.

Please refer to Figure 13, which is a schematic structural diagram of a communication device 1300 provided in this embodiment. It can be applied to eRedCap terminals or to the base station side. The communication device 1300 can be a network device, a user device, a chip, a chip system, or a processor that supports the network device to implement the above method, or it can also be a user device. A chip, chip system, or processor that implements the above method. The device can be used to implement the method described in the above method embodiment. For details, please refer to the description in the above method embodiment.

Communication device 1300 may include one or more processors 1301. The processor 1301 may be a general-purpose processor or a special-purpose processor, or the like. For example, it can be a baseband processor or a central processing unit. The baseband processor can be used to process communication protocols and communication data. The central processor can be used to control communication devices (such as base stations, baseband chips, terminal equipment, terminal equipment chips, DU or CU, etc.) and execute computer Program, a computer program that processes data.

Optionally, the communication device 1300 may also include one or more memories 1302, on which a computer program 1204 may be stored. The processor 1301 executes the computer program 1304, so that the communication device 1300 executes the method described in the above method embodiment. Optionally, the memory 1302 may also store data. The communication device 1300 and the memory 1302 can be provided separately or integrated together.

Optionally, the communication device 1300 may also include a transceiver 1305 and an antenna 1306. The transceiver 1305 may be called a transceiver unit, a transceiver, a transceiver circuit, etc., and is used to implement transceiver functions. The transceiver 1205 may include a receiver and a transmitter. The receiver may be called a receiver or a receiving circuit, etc., used to implement the receiving function; the transmitter may be called a transmitter, a transmitting circuit, etc., used to implement the transmitting function.

Optionally, the communication device 1300 may also include one or more interface circuits 1307. The interface circuit 1307 is used to receive code instructions and transmit them to the processor 1301 . The processor 1301 executes code instructions to cause the communication device 1300 to perform the method described in the above method embodiment.

In one implementation, the processor 1301 may include a transceiver for implementing receiving and transmitting functions. For example, the transceiver may be a transceiver circuit, an interface, or an interface circuit. The transceiver circuits, interfaces or interface circuits used to implement the receiving and transmitting functions can be separate or integrated together. The above-mentioned transceiver circuit, interface or interface circuit can be used for reading and writing codes/data, or the above-mentioned transceiver circuit, interface or interface circuit can be used for signal transmission or transfer.

In one implementation, the processor 1301 may store a computer program 1303, and the computer program 1303 runs on the processor 1301, causing the communication device 1300 to perform the method described in the above method embodiment. The computer program 1203 may be solidified in the processor 1201, in which case the processor 1301 may be implemented by hardware.

In one implementation, the communication device 1300 may include a circuit, which may implement the functions of sending or receiving or communicating in the foregoing method embodiments. The processor and transceiver described in this application can be implemented in integrated circuits (ICs), analog ICs, radio frequency integrated circuits RFICs, mixed signal ICs, application specific integrated circuits (ASICs), printed circuit boards ( printed circuit board (PCB), electronic equipment, etc. The processor and transceiver can also be manufactured using various IC process technologies, such as complementary metal oxide semiconductor (CMOS), n-type metal oxide-semiconductor (NMOS), P-type Metal oxide semiconductor (positive channel metal oxide semiconductor, PMOS), bipolar junction transistor (BJT), bipolar CMOS (BiCMOS), silicon germanium (SiGe), gallium arsenide (GaAs), etc.

The communication device described in the above embodiments may be a network device or user equipment, but the scope of the communication device described in this application is not limited thereto, and the structure of the communication device may not be limited by FIG. 13 . The communication device may be a stand-alone device or may be part of a larger device. For example, the communication device can be:

(1) Independent integrated circuit IC, or chip, or chip system or subsystem;

(2) A collection of one or more ICs. Optionally, the IC collection may also include storage components for storing data and computer programs;

(3)ASIC, such as modem;

(4) Modules that can be embedded in other devices;

(5) Receivers, terminal equipment, intelligent terminal equipment, cellular phones, wireless equipment, handheld devices, mobile units, vehicle-mounted equipment, network equipment, cloud equipment, artificial intelligence equipment, etc.;

(6) Others, etc.

For the case where the communication device may be a chip or a chip system, refer to the schematic structural diagram of the chip shown in FIG. 14 . The chip shown in Figure 14 includes a processor 1401 and an interface 1402. The number of processors 1401 may be one or more, and the number of interfaces 1402 may be multiple.

Optionally, the chip also includes a memory 1403, which is used to store necessary computer programs and data.

Those skilled in the art can also understand that the various illustrative logical blocks and steps listed in the embodiments of this application can be implemented by electronic hardware, computer software, or a combination of both. Whether such functionality is implemented in hardware or software depends on the specific application and overall system design requirements. Those skilled in the art can use various methods to implement the described functions for each specific application, but such implementation should not be understood as exceeding the protection scope of the embodiments of the present application.

This application also provides a computer storage medium, which can be applied to the eRedCap terminal or to the base station side. Instructions are stored on the medium, and when the instructions are executed by the computer, the functions of any of the above method embodiments are realized.

This application also provides a computer program product, which can be applied to an eRedCap terminal or to the base station side. When the computer program product is executed by a computer, it implements the functions of any of the above method embodiments.

In the above embodiments, it may be implemented in whole or in part by software, hardware, firmware, or any combination thereof. When implemented using software, it may be implemented in whole or in part in the form of a computer program product. A computer program product includes one or more computer programs. When a computer program is loaded and executed on a computer, processes or functions according to embodiments of the present application are generated in whole or in part. The computer may be a general purpose computer, a special purpose computer, a computer network, or other programmable device. The computer program may be stored in or transmitted from one computer-readable storage medium to another computer-readable storage medium, for example, the computer program may be transmitted from a website, computer, server or data center via a wireline (e.g. Coaxial cable, optical fiber, digital subscriber line (DSL)) or wireless (such as infrared, wireless, microwave, etc.) means to transmit to another website, computer, server or data center. Computer-readable storage media can be any available media that can be accessed by a computer or a data storage device such as a server, data center, or other integrated media that contains one or more available media. Available media may be magnetic media (e.g., floppy disks, hard disks, tapes), optical media (e.g., high-density digital video discs (DVD)), or semiconductor media (e.g., solid state disks (SSD)) )wait.

Persons of ordinary skill in the art can understand that the first, second, and other numerical numbers involved in this application are only for convenience of description and are not used to limit the scope of the embodiments of this application and also indicate the order.

At least one in this application can also be described as one or more, and the plurality can be two, three, four or more, which is not limited by this application. In the embodiment of this application, for a technical feature, the technical feature is distinguished by "first", "second", "third", "A", "B", "C" and "D", etc. The technical features described in "first", "second", "third", "A", "B", "C" and "D" are in no particular order or order.

As used herein, the terms "machine-readable medium" and "computer-readable medium" refer to any computer program product, apparatus, and/or means for providing machine instructions and/or data to a programmable processor ( For example, magnetic disks, optical disks, memories, programmable logic devices (PLD)), including machine-readable media that receive machine instructions as machine-readable signals. The term "machine-readable signal" refers to any signal used to provide machine instructions and/or data to a programmable processor.

The systems and techniques described herein may be implemented in a computing system that includes back-end components (e.g., as a data server), or a computing system that includes middleware components (e.g., an application server), or a computing system that includes front-end components (e.g., A user's computer having a graphical user interface or web browser through which the user can interact with implementations of the systems and technologies described herein), or including such backend components, middleware components, or any combination of front-end components in a computing system. The components of the system may be interconnected by any form or medium of digital data communication (eg, a communications network). Examples of communication networks include: local area network (LAN), wide area network (WAN), and the Internet.

Computer systems may include clients and servers. Clients and servers are generally remote from each other and typically interact over a communications network. The relationship of client and server is created by computer programs running on corresponding computers and having a client-server relationship with each other.

It should be understood that various forms of the process shown above may be used, with steps reordered, added or deleted. For example, each step described in this application can be executed in parallel, sequentially, or in a different order. As long as the desired results of the technical solution of this application can be achieved, there is no limitation here.

In addition, it should be understood that the various embodiments described in this application can be implemented alone or in combination with other embodiments if the scheme allows.

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

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

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

Claims

A method for determining the size of the layer 2 cache, which is characterized in that it is applied to eRedCap terminal side execution with reduced capabilities. The method includes:

The layer 2 cache size of the eRedCap terminal is determined according to the uplink peak data rate and the downlink peak data rate supported by the eRedCap terminal.
The method of claim 1, further comprising:

According to the maximum uplink transmission block size TBS supported by the eRedCap terminal, the duration of the time slot and the maximum number of uplink transmission blocks TB supported by the eRedCap terminal in the time slot, the uplink supported by the eRedCap terminal is determined. Peak data rate; and,

Determine the peak downlink data rate supported by the eRedCap terminal based on the maximum downlink TBS supported by the eRedCap terminal, the duration of the time slot, and the maximum number of downlink TBs supported by the eRedCap terminal in the time slot. .
The method according to claim 2, characterized in that, based on the maximum uplink TBS supported by the eRedCap terminal, the duration of the time slot and the maximum number of uplink TBs supported by the eRedCap terminal in the time slot, Determine the peak uplink data rate supported by the eRedCap terminal, including:

Multiply the maximum uplink TBS by the maximum number of uplink TBs, and then divide it by the duration of the time slot to obtain the uplink peak data rate supported by the eRedCap terminal.
The method according to claim 2, characterized in that the method is based on the maximum downlink TBS supported by the eRedCap terminal, the duration of the time slot and the maximum number of downlink TBs supported by the eRedCap terminal in the time slot. Number to determine the peak downlink data rate supported by the eRedCap terminal, including:

Multiply the maximum downlink TBS by the maximum number of downlink TBs, and then divide it by the duration of the time slot to obtain the downlink peak data rate supported by the eRedCap terminal.
The method of claim 1, further comprising:

Obtain the first scaling coefficient of the physical uplink shared channel PUSCH and the second scaling coefficient of the physical downlink shared channel PDSCH, wherein the first scaling coefficient and the second scaling coefficient are both greater than 0 and less than 1;

Determine the peak uplink data rate supported by the eRedCap terminal according to the peak uplink data rate supported by the traditional terminal and the first scaling factor; and,

The downlink peak data rate supported by the eRedCap terminal is determined according to the downlink peak data rate supported by the legacy terminal and the second scaling factor.
The method of claim 5, wherein the uplink peak data rate supported by the eRedCap terminal is determined based on the uplink peak data rate supported by the traditional terminal and the first scaling factor, include:

The peak uplink data rate supported by the traditional terminal is multiplied by the first scaling factor to obtain the peak uplink data rate supported by the eRedCap terminal.
The method of claim 5, wherein the downlink peak data rate supported by the eRedCap terminal is determined based on the downlink peak data rate supported by the traditional terminal and the second scaling factor, include:

The peak downlink data rate supported by the traditional terminal is multiplied by the second scaling factor to obtain the peak downlink data rate supported by the eRedCap terminal.
The method of claim 1, further comprising:

Obtain the upstream peak data rate supported by the eRedCap terminal specified in the communication protocol; and,

Obtain the downlink peak data rate supported by the eRedCap terminal specified in the communication protocol.
The method according to any one of claims 1 to 8, characterized in that the layer 2 cache size of the eRedCap terminal is determined based on the uplink peak data rate and the downlink peak data rate supported by the eRedCap terminal. ,include:

The result obtained by multiplying the uplink peak data rate by the round-trip delay RLC RTT of the wireless link control layer is added to the result obtained by multiplying the downlink peak data rate by the RLC RTT to obtain the result of the eRedCap terminal. Tier 2 cache size.
A method for determining the size of the layer 2 cache, which is characterized in that it is applied to the base station side, and the method includes:

The layer 2 cache size of the eRedCap terminal is determined based on the uplink peak data rate and the downlink peak data rate supported by the eRedCap terminal with reduced capabilities.
The method of claim 10, further comprising:

According to the maximum uplink transmission block size TBS supported by the eRedCap terminal, the duration of the time slot and the maximum number of uplink transmission blocks TB supported by the eRedCap terminal in the time slot, the uplink supported by the eRedCap terminal is determined. Peak data rate; and,

Determine the peak downlink data rate supported by the eRedCap terminal based on the maximum downlink TBS supported by the eRedCap terminal, the duration of the time slot, and the maximum number of downlink TBs supported by the eRedCap terminal in the time slot. .
The method according to claim 11, characterized in that, based on the maximum uplink TBS supported by the eRedCap terminal, the duration of the time slot and the maximum number of uplink TBs supported by the eRedCap terminal in the time slot, Determine the peak uplink data rate supported by the eRedCap terminal, including:

Multiply the maximum uplink TBS by the maximum number of uplink TBs, and then divide it by the duration of the time slot to obtain the uplink peak data rate supported by the eRedCap terminal.
The method according to claim 11, characterized in that the method is based on the maximum downlink TBS supported by the eRedCap terminal, the duration of the time slot and the maximum number of downlink TBs supported by the eRedCap terminal in the time slot. Number to determine the peak downlink data rate supported by the eRedCap terminal, including:

Multiply the maximum downlink TBS by the maximum number of downlink TBs, and then divide it by the duration of the time slot to obtain the downlink peak data rate supported by the eRedCap terminal.
The method of claim 10, further comprising:

Obtain the first scaling coefficient of the physical uplink shared channel PUSCH and the second scaling coefficient of the physical downlink shared channel PDSCH, wherein the first scaling coefficient and the second scaling coefficient are both greater than 0 and less than 1;

Determine the peak uplink data rate supported by the eRedCap terminal according to the peak uplink data rate supported by the traditional terminal and the first scaling factor; and,

The downlink peak data rate supported by the eRedCap terminal is determined according to the downlink peak data rate supported by the legacy terminal and the second scaling factor.
The method of claim 14, wherein the uplink peak data rate supported by the eRedCap terminal is determined based on the uplink peak data rate supported by the traditional terminal and the first scaling factor, include:

The peak uplink data rate supported by the traditional terminal is multiplied by the first scaling factor to obtain the peak uplink data rate supported by the eRedCap terminal.
The method of claim 14, wherein the downlink peak data rate supported by the eRedCap terminal is determined based on the downlink peak data rate supported by the traditional terminal and the second scaling factor, include:

The peak downlink data rate supported by the traditional terminal is multiplied by the second scaling factor to obtain the peak downlink data rate supported by the eRedCap terminal.
The method of claim 10, further comprising:

Obtain the upstream peak data rate supported by the eRedCap terminal specified in the communication protocol; and,

Obtain the downlink peak data rate supported by the eRedCap terminal specified in the communication protocol.
The method according to any one of claims 10 to 17, characterized in that determining the layer 2 cache size of the eRedCap terminal according to the uplink peak data rate and the downlink peak data rate supported by the eRedCap terminal includes: :

The result obtained by multiplying the uplink peak data rate by the round-trip delay RLC RTT of the wireless link control layer is added to the result obtained by multiplying the downlink peak data rate by the RLC RTT to obtain the result of the eRedCap terminal. Tier 2 cache size.
A device for determining the size of the layer 2 cache, characterized in that it is applied to the eRedCap terminal side with reduced capabilities, and the device includes:

A determination module, configured to determine the layer 2 cache size of the eRedCap terminal based on the uplink peak data rate and the downlink peak data rate supported by the eRedCap terminal.
A device for determining the size of a layer 2 buffer, characterized in that it is applied to the base station side, and the device includes:

A determination module configured to determine the layer 2 cache size of the eRedCap terminal based on the uplink peak data rate and the downlink peak data rate supported by the eRedCap terminal with reduced capabilities.
A communication device, applied to the eRedCap terminal side with reduced capabilities, wherein the communication device includes: a transceiver; a memory; a processor, respectively connected to the transceiver and the memory, configured to execute The computer can execute instructions to control the wireless signal transmission and reception of the transceiver, and can implement the method described in any one of claims 1-9.
A communication device, applied to the base station side, wherein the communication device includes: a transceiver; a memory; a processor, respectively connected to the transceiver and the memory, configured to execute a computer executable on the memory Instructions to control the wireless signal transmission and reception of the transceiver, and to implement the method described in any one of claims 10-18.
A computer storage medium, applied to eRedCap terminals with reduced capabilities, wherein the computer storage medium stores computer executable instructions; after the computer executable instructions are executed by a processor, any one of claims 1-9 can be realized method described in the item.
A computer storage medium, applied to the base station side, wherein the computer storage medium stores computer executable instructions; after the computer executable instructions are executed by the processor, the computer executable instructions can realize any one of claims 10-18 Methods.