Method and apparatus for determining layer 2 cache size

Abstract

The present application proposes a method and apparatus for determining the Layer 2 cache size, which relates to the field of communication technologies. By applying the method of the present application, the peak data rate for eRedCap terminals can be provided, and an effective solution for determining the Layer 2 cache size for eRedCap terminals can be obtained to meet the updated requirements of the peak data rate of eRedCap terminals, thereby saving costs.

Description

Technical Field

[0001] This application relates to the field of communication technologies, and particularly to a method and apparatus for determining the size of a Layer 2 buffer. Background Art

[0002] For a Reduced capability (eRedCap) terminal, a possible solution for reducing complexity is to limit the Transport Block Size (TBS). This solution is beneficial for reducing the buffer size of Hybrid Automatic Repeat request (HARQ), as well as the cost of devices such as Low Density Parity Check Code (LDPC) encoding. If the TBS is further restricted, the peak data rate of the eRedCap needs to be re-determined.

[0003] Currently, the update of the peak data rate of the eRedCap terminal affects the calculation of the Layer 2 total buffer size of the eRedCap terminal. However, there is currently a lack of an effective solution for determining the Layer 2 buffer size for the eRedCap terminal. Summary of the Invention

[0004] This application proposes a method and apparatus for determining the size of a Layer 2 buffer, providing an effective solution for determining the Layer 2 buffer size for the eRedCap terminal to meet the update requirements of the peak data rate of the eRedCap terminal, thereby saving costs.

[0005] In a first aspect embodiment of this application, a method for determining the size of a Layer 2 buffer is provided, which is executed on the eRedCap terminal side. The method includes: determining the size of the Layer 2 buffer of the eRedCap terminal according to the peak data rate of the uplink and the peak data rate of the downlink supported by the eRedCap terminal.

[0006] In some embodiments of the present application, the method further includes: determining the peak data rate of the uplink supported by the eRedCap terminal according to the maximum transport block size (TBS) supported by the eRedCap terminal, the duration of the time slot, and the maximum number of transport blocks (TBs) supported by the eRedCap terminal within the time slot; and determining the peak data rate of the downlink supported by the eRedCap terminal according to 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 within the time slot; determining the layer 2 buffer size of the eRedCap terminal based on the peak data rate of the uplink and the peak data rate of the downlink supported by the eRedCap terminal.

[0007] In some embodiments of the present application, the determining the peak data rate of the uplink supported by the eRedCap terminal according to 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 within the time slot 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 data rate of the uplink supported by the eRedCap terminal.

[0008] In some embodiments of the present application, the determining the peak data rate of the downlink of the eRedCap terminal according to 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 within the time slot 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 data rate of the downlink supported by the eRedCap terminal.

[0009] In some embodiments of the present application, the method further includes: obtaining a first scaling factor for the physical uplink shared channel (PUSCH) and a second scaling factor for the physical downlink shared channel (PDSCH), where both the first scaling factor and the second scaling factor are greater than 0 and less than 1; determining the peak data rate of the uplink supported by the eRedCap terminal according to the peak data rate of the uplink supported by the legacy terminal and the first scaling factor; and determining the peak data rate of the downlink supported by the eRedCap terminal according to the peak data rate of the downlink supported by the legacy terminal and the second scaling factor.

[0010] In some embodiments of the present application, determining 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 includes: multiplying the peak uplink data rate supported by the traditional terminal by the first scaling factor to obtain the peak uplink data rate supported by the eRedCap terminal.

[0011] In some embodiments of the present application, determining the peak downlink data rate supported by the eRedCap terminal according to the peak downlink data rate supported by the traditional terminal and the second scaling factor includes: multiplying the peak downlink data rate supported by the traditional terminal by the second scaling factor to obtain the peak downlink data rate supported by the eRedCap terminal.

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

[0013] In some embodiments of the present application, determining the layer 2 buffer size of the eRedCap terminal according to the peak uplink data rate and the peak downlink data rate supported by the eRedCap terminal includes: adding the result obtained by multiplying the peak uplink data rate by the round-trip time RLC RTT of the radio link control layer to the result obtained by multiplying the peak downlink data rate by RLC RTT to obtain the layer 2 buffer size of the eRedCap terminal.

[0014] An embodiment of the second aspect of the present application provides a method for determining the layer 2 buffer size, which is executed on the base station side. The method includes: determining the layer 2 buffer size of the eRedCap terminal according to the peak uplink data rate and the peak downlink data rate supported by the eRedCap terminal.

[0015] In some embodiments of the present application, the method further includes: determining the peak data rate of the uplink supported by the eRedCap terminal according to the maximum transport block size (TBS) supported by the eRedCap terminal, the duration of the time slot, and the maximum number of transport blocks (TBs) supported by the eRedCap terminal within the time slot; and determining the peak data rate of the downlink supported by the eRedCap terminal according to 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 within the time slot; and determining the layer 2 buffer size of the eRedCap terminal based on the peak data rate of the uplink and the peak data rate of the downlink supported by the eRedCap terminal.

[0016] In some embodiments of the present application, the determining the peak data rate of the uplink supported by the eRedCap terminal according to 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 within the time slot 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 data rate of the uplink supported by the eRedCap terminal.

[0017] In some embodiments of the present application, the determining the peak data rate of the downlink of the eRedCap terminal according to 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 within the time slot 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 data rate of the downlink supported by the eRedCap terminal.

[0018] In some embodiments of the present application, the method further includes: obtaining a first scaling factor of the physical uplink shared channel (PUSCH) and a second scaling factor of the physical downlink shared channel (PDSCH), where both the first scaling factor and the second scaling factor are greater than 0 and less than 1; determining the peak data rate of the uplink supported by the eRedCap terminal according to the peak data rate of the uplink supported by the traditional terminal and the first scaling factor; and determining the peak data rate of the downlink supported by the eRedCap terminal according to the peak data rate of the downlink supported by the traditional terminal and the second scaling factor.

[0019] In some embodiments of the present application, determining 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 includes: multiplying the peak uplink data rate supported by the traditional terminal by the first scaling factor to obtain the peak uplink data rate supported by the eRedCap terminal.

[0020] In some embodiments of the present application, determining the peak downlink data rate supported by the eRedCap terminal according to the peak downlink data rate supported by the traditional terminal and the second scaling factor includes: multiplying the peak downlink data rate supported by the traditional terminal by the second scaling factor to obtain the peak downlink data rate supported by the eRedCap terminal.

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

[0022] In some embodiments of the present application, determining the layer 2 buffer size of the eRedCap terminal according to the peak uplink data rate and the peak downlink data rate supported by the eRedCap terminal includes: adding the result obtained by multiplying the peak uplink data rate by the round-trip time RLC RTT of the radio link control layer to the result obtained by multiplying the peak downlink data rate by RLC RTT to obtain the layer 2 buffer size of the eRedCap terminal.

[0023] An embodiment of the third aspect of the present application provides a device for determining the layer 2 buffer size, which is applied to the eRedCap terminal side. The device includes: a determining unit, configured to determine the layer 2 buffer size of the eRedCap terminal according to the peak uplink data rate and the peak downlink data rate supported by the eRedCap terminal.

[0024] An embodiment of the fourth aspect of the present application provides a device for determining the layer 2 buffer size, which is applied to the base station side. The device includes: a determining unit, configured to determine the layer 2 buffer size of the eRedCap terminal according to the peak uplink data rate and the peak downlink data rate supported by the eRedCap terminal.

[0025] 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; a processor, which is respectively connected to the transceiver and the memory, and is configured to control the wireless signal transceiver of the transceiver by executing computer-executable instructions on the memory, and can implement the method of the first aspect embodiment of the present application.

[0026] 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; a processor, which is respectively connected to the transceiver and the memory, and is configured to control the wireless signal transceiver of the transceiver by executing computer-executable instructions on the memory, and can implement the method of the second aspect embodiment of the present application.

[0027] The seventh aspect embodiment of the present application provides a computer storage medium, which is applied to the eRedCap terminal side. The computer storage medium stores computer-executable instructions; after the computer-executable instructions are executed by a processor, the method of the first aspect embodiment of the present application can be implemented.

[0028] The eighth aspect embodiment of the present application provides a computer storage medium, which is applied to the base station side. The computer storage medium stores computer-executable instructions; after the computer-executable instructions are executed by a processor, the method of the second aspect embodiment of the present application can be implemented.

[0029] The embodiment of the present application provides a method and device for determining the layer 2 cache size, which can provide the peak data rate for the eRedCap terminal, and provide an effective solution for determining the layer 2 cache size for the eRedCap terminal to meet the update requirements of the peak data rate of the eRedCap terminal (to meet the requirements of further restricted TBS), thereby saving costs.

[0030] The additional aspects and advantages of the present application will be partially given in the following description, partially become obvious from the following description, or be understood through the practice of the present application. Description of the Drawings

[0031] The above and / or additional aspects and advantages of the present application will become obvious and easy to understand from the following description of the embodiments in conjunction with the drawings, where:

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

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

[0034] Figure 3Flow chart of a method for determining the size of a Layer 2 cache according to an embodiment of the present application;

[0035] Figure 4 Flow chart of a method for determining the size of a Layer 2 cache according to an embodiment of the present application;

[0036] Figure 5 Flow chart of a method for determining the size of a Layer 2 cache according to an embodiment of the present application;

[0037] Figure 6 Flow chart of a method for determining the size of a Layer 2 cache according to an embodiment of the present application;

[0038] Figure 7 Flow chart of a method for determining the size of a Layer 2 cache according to an embodiment of the present application;

[0039] Figure 8 Flow chart of a method for determining the size of a Layer 2 cache according to an embodiment of the present application;

[0040] Figure 9 Flow chart of a method for determining the size of a Layer 2 cache according to an embodiment of the present application;

[0041] Figure 10 Block diagram of a device for determining the size of a Layer 2 cache according to an embodiment of the present application;

[0042] Figure 11 Block diagram of a device for determining the size of a Layer 2 cache according to an embodiment of the present application;

[0043] Figure 12 Block diagram of a device for determining the size of a Layer 2 cache according to an embodiment of the present application;

[0044] Figure 13 Structural diagram of a communication device according to an embodiment of the present application;

[0045] Figure 14 Structural diagram of a chip provided by an embodiment of the present application. Detailed implementation manners

[0046] The embodiments of the present application will be described in detail below. The examples of the embodiments are shown in the drawings, where the same or similar reference numerals denote the same or similar elements or elements with the same or similar functions from beginning to end. The embodiments described below by referring to the drawings are exemplary and are intended to explain the present application, but should not be construed as a limitation to the present application. It should be noted that, without conflict, the embodiments of the present application and the features in the embodiments may be combined with each other.

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

[0048] It should be understood that although the terms first, second, third, etc. may be used in the embodiments of the present application to describe various information, such 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 referred to as the second information, and similarly, the second information may also be referred to as the first information. Depending on the context, the word "if" as used herein may be interpreted as "when" or "while" or "in response to determining".

[0049] For ease of understanding, the terms involved in this embodiment are introduced first.

[0050] 1. Physical Uplink Shared Channel (PUSCH)

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

[0052] 2. Physical Downlink Shared Channel (PDSCH)

[0053] The PDSCH is used to carry data from the Downlink Shared Channel (DSCH).

[0054] 3. eRedCap terminal

[0055] The 3rd Generation Partnership Project (3GPP) established a dedicated standard project in the communication protocol Release 17 (Rel-17) phase to analyze and optimize the functional characteristics of existing 5G terminals and networks, enabling 5G Internet of Things (IoT) terminals to access the 5G core network through the 5G New Radio (NR). In this standard project, 3GPP proposed NR devices with reduced capabilities, namely RedCap terminals. Compared with traditional enhanced mobile broadband (eMBB) devices and ultra-reliable and low latency communication (URLLC) devices, RedCap terminal devices have the advantages of lower cost, lower complexity, more compact size, and sufficient performance. The eRedCap terminal further reduces the terminal cost based on the RedCap terminal to support 5G IoT terminals with lower rates to use NR technology.

[0056] Currently, for eRedCap terminals, a possible solution to reduce complexity is to limit the Transport Block Size (TBS). This solution is beneficial for the Hybrid Automatic Repeat reQuest (HARQ) buffer size and the reduction of costs for components such as Low-Density Parity-Check (LDPC) coding. However, if the TBS is further restricted, the peak data rate of traditional terminals, which is a constraint condition for the TBS, will no longer be applicable. Therefore, it is necessary to re-determine the peak data rate for eRedCap terminals. The update of the peak data rate of eRedCap terminals will affect the calculation of the Layer 2 (L2) total buffer size of eRedCap terminals. However, there is currently no effective solution for determining the L2 total buffer size for eRedCap terminals.

[0057] Therefore, this embodiment proposes a method and device for determining the L2 buffer size, providing an effective solution for determining the L2 total buffer size for eRedCap terminals to meet the update requirements of the peak data rate of eRedCap terminals.

[0058] The following will introduce in detail the method and device for determining the L2 buffer size provided by this application in conjunction with the accompanying drawings.

[0059] Figure 1 It shows a schematic flowchart of one of the methods for determining the L2 buffer size according to an embodiment of this application. As Figure 1As shown, it can be applied to the eRedCap terminal side or the base station side, and may include the following steps.

[0060] Step 101: Determine the layer 2 cache size of the eRedCap terminal according to the peak data rate of the uplink and the peak data rate of the downlink supported by the eRedCap terminal.

[0061] 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 according to the peak data rate of the uplink and the peak data rate of the downlink supported by the eRedCap terminal. Furthermore, an effective solution for determining the layer 2 cache size for the eRedCap terminal can be provided according to the peak data rate of the eRedCap terminal, so as to meet the update requirements of the peak data rate of the eRedCap terminal (to meet the requirements of further restricted TBS), and thus save costs.

[0062] Figure 2 The flowchart shows one of the methods for determining the layer 2 cache size according to an embodiment of the present application. Based on Figure 1 the embodiment shown, as Figure 2 shown, it can be applied to the eRedCap terminal side or the base station side, and this method may include the following steps.

[0063] Step 201: Determine the peak data rate of the uplink supported by the eRedCap terminal according to the maximum uplink TBS supported by the eRedCap terminal, the duration of one time slot, and the maximum number of uplink TBs supported by the eRedCap terminal within this time slot, and determine the peak data rate of the downlink supported by the eRedCap terminal according to the maximum downlink TBS supported by the eRedCap terminal, the duration of one time slot, and the maximum number of downlink TBs supported by the eRedCap terminal within this time slot.

[0064] The maximum uplink TBS and the maximum downlink TBS supported by the eRedCap terminal can be obtained from the communication protocol. For example, it can be directly stipulated in the communication protocol that the maximum uplink TBS (transport block size) supported by the eRedCap terminal is U bits (number of bits), and it can be directly stipulated in the communication protocol that the maximum downlink TBS supported by the eRedCap terminal is D bits, and these contents can be preset in the communication protocol.

[0065] For example, based on the maximum uplink TBS (U bits) supported by the eRedCap terminal as specified in the communication protocol, the slot duration, and the maximum number of uplink TBs supported by the eRedCap terminal within a slot, the peak data rate of the uplink supported by the eRedCap terminal is calculated; and based on the maximum downlink TBS (D bits) supported by the eRedCap terminal as specified in the communication protocol, the slot duration, and the maximum number of downlink TBs supported by the eRedCap terminal within a slot, the peak data rate of the downlink supported by the eRedCap terminal is calculated.

[0066] Step 202: Determine the layer 2 buffer size of the eRedCap terminal according to the peak data rate of the uplink and the peak data rate of the downlink supported by the eRedCap terminal.

[0067] By applying the method for determining the layer 2 buffer size provided in this embodiment, the peak data rate of the uplink supported by the eRedCap terminal can be determined according to the maximum uplink TBS supported by the eRedCap terminal as specified in the communication protocol, the duration of one time slot, and the maximum number of uplink TBs supported by the eRedCap terminal within this time slot, and the peak data rate of the downlink supported by the eRedCap terminal can be determined according to the maximum downlink TBS supported by the eRedCap terminal as specified in the communication protocol, the duration of one time slot, and the maximum number of downlink TBs supported by the eRedCap terminal within this time slot. Furthermore, based on the peak data rate of the uplink and the peak data rate of the downlink supported by the eRedCap terminal, the L2 total buffer size of the eRedCap terminal is determined. Thus, an effective solution for determining the L2 total buffer size of the eRedCap terminal is provided to meet the update requirements of the peak data rate of the eRedCap terminal and save costs.

[0068] Figure 3 The flowchart shows one method for determining the layer 2 buffer size according to an embodiment of the present application. Based on Figure 2 the embodiment shown, as Figure 3 shown, it can be applied to the eRedCap terminal side or the base station side, and this method may include the following steps.

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

[0070] 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 by the duration of the time slot to obtain the peak data rate of the uplink supported by the eRedCap terminal. Also, multiply the maximum downlink TBS supported by the eRedCap terminal by the maximum number of downlink TBs supported by the eRedCap terminal in one time slot, and then divide by the duration of the time slot to obtain the peak data rate of the downlink supported by the eRedCap terminal.

[0071] For example, to determine the peak data rate of the uplink supported by the eRedCap terminal in TS 38.306 protocol, as shown in Formula 1 below:

[0072] Peak data rate of the uplink supported by the eRedCap terminal = U * M1 / T_slot (Formula 1)

[0073] In Formula 1, U is the maximum uplink TBS supported by the eRedCap terminal, M1 is the maximum number of uplink TBs that can be transmitted or supported by the eRedCap terminal in one slot, and T_slot is the duration of the slot.

[0074] To determine the peak data rate of the downlink supported by the eRedCap terminal in TS 38.306 protocol, as shown in Formula 2 below:

[0075] Peak data rate of the downlink supported by the eRedCap terminal = D * M2 / T_slot (Formula 2)

[0076] In Formula 2, D is the maximum downlink TBS supported by the eRedCap terminal, M2 is the maximum number of downlink TBs that can be transmitted or supported by the eRedCap terminal in one slot, and T_slot is the duration of the slot.

[0077] Step 303: Determine the layer 2 buffer size of the eRedCap terminal according to the peak data rate of the uplink and the peak data rate of the downlink supported by the eRedCap terminal.

[0078] It should be noted that although Figure 3 the embodiments shown are described based on Figure 1 the embodiments shown, similarly, this Figure 3 embodiment shown can also be based on Figure 2 the embodiments shown, and will not be elaborated here.

[0079] By applying the method for determining the layer 2 buffer size 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 within one time slot, and then divided by the duration of the time slot to obtain the peak data rate of the uplink supported by the eRedCap terminal. Also, the maximum downlink TBS supported by the eRedCap terminal can be multiplied by the maximum number of downlink TBs supported by the eRedCap terminal within one time slot, and then divided by the duration of the time slot to obtain the peak data rate of the downlink supported by the eRedCap terminal. Furthermore, based on the peak data rate of the uplink and the peak data rate of the downlink supported by the eRedCap terminal, the L2 total buffer size of the eRedCap terminal can be determined. Thus, an effective solution for determining the L2 total buffer size for the eRedCap terminal is provided to meet the update requirements of the peak data rate of the eRedCap terminal and save costs.

[0080] Figure 4 The flowchart shows one of the methods for determining the layer 2 buffer size according to the embodiments of the present application. Based on Figure 2 the embodiments shown, as Figure 4 shown, it can be applied to the eRedCap terminal side or the base station side, and the method may include the following steps.

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

[0082] Step 402: Determine the peak data rate of the uplink supported by the eRedCap terminal according to the maximum uplink TBS supported by the eRedCap terminal, the duration of one time slot, and the maximum number of uplink TBs supported by the eRedCap terminal within the time slot, and determine the peak data rate of the downlink supported by the eRedCap terminal according to the maximum downlink TBS supported by the eRedCap terminal, the duration of one time slot, and the maximum number of downlink TBs supported by the eRedCap terminal within the time slot.

[0083] Step 403: Multiply the peak data rate of the uplink supported by the eRedCap terminal by the RLC RTT, add the result obtained by multiplying the peak data rate of the downlink supported by the eRedCap terminal by the RLC RTT, and obtain the layer 2 buffer size of the eRedCap terminal.

[0084] Among them, RLC RTT is the round-trip time (RTT) of the Radio Link Control (RLC) layer. For example, the L2 total buffer size of the eRedCap terminal is calculated through Formula 5.

[0085] L2 total buffer size = MaxULdatarate * RLC RTT + MaxDLdatarate * RLC RTT (Formula 3)

[0086] In Formula 3, MaxULdatarate is the peak data rate of the uplink supported by the eRedCap terminal, and MaxDLdatarate is the peak data rate of the downlink supported by the eRedCap terminal.

[0087] It should be noted that although Figure 4 the illustrated embodiment is described based on Figure 2 the illustrated embodiment, similarly, this Figure 4 illustrated embodiment can also be based on Figure 3 the illustrated embodiment, and will not be elaborated here.

[0088] By applying the method provided in this embodiment, the result obtained by multiplying the peak data rate of the uplink supported by the eRedCap terminal by RLC RTT is added to the result obtained by multiplying the peak data rate of the downlink supported by the eRedCap terminal by RLC RTT, to obtain the layer 2 buffer size of the eRedCap terminal. Furthermore, based on the peak data rate of the uplink and the peak data rate of the downlink supported by the eRedCap terminal, the L2 total buffer size of the eRedCap terminal is determined. Thus, an effective solution for determining the L2 total buffer size of the eRedCap terminal is provided to meet the update requirements of the peak data rate of the eRedCap terminal, saving costs.

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

[0090] Step 501, obtain the first scaling factor of the PUSCH channel and the second scaling factor of the PDSCH channel.

[0091] Among them, both the first scaling factor and the second scaling factor can be greater than 0 and less than 1. The first scaling factor and the second scaling factor can be obtained through a communication protocol or determined by the terminal itself 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 TBS supported by the traditional terminal multiplied by the first scaling factor, and the maximum downlink TBS supported by the eRedCap terminal is the maximum downlink TBS supported by the traditional terminal multiplied by the second scaling factor.

[0092] 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 the first scaling factor, and this first scaling factor can be 1 / A1, where A1>1; and it can be specified in the communication protocol that the maximum downlink TBS supported by the eRedCap terminal is the maximum downlink TBS supported by the traditional terminal multiplied by the second scaling factor, and this second scaling factor can be 1 / A2, where A2>1. Through this specified content, the first scaling factor 1 / A1 of the PUSCH and the second scaling factor 1 / A2 of the PDSCH can be obtained. Among them, the PDSCH channel and the PUSCH channel can have different scaling factors, that is, 1 / A1 and 1 / A2 can be different.

[0093] Step 502: Determine the peak data rate of the uplink supported by the eRedCap terminal according to the peak data rate of the uplink supported by the traditional terminal and the first scaling factor of the PUSCH channel, and determine the peak data rate of the downlink supported by the eRedCap terminal according to the peak data rate of the downlink supported by the traditional terminal and the second scaling factor of the PDSCH channel.

[0094] For example, according to the peak data rate of the uplink supported by the traditional terminal (different from the eRedCap terminal) and the first scaling factor 1 / A1 (A1>1) of the PUSCH channel, determine the peak data rate of the uplink supported by the eRedCap terminal, and according to the peak data rate of the downlink supported by the traditional terminal and the second scaling factor 1 / A2 (A2>1) of the PDSCH channel, determine the peak data rate of the downlink supported by the eRedCap terminal.

[0095] Step 503: Determine the layer 2 buffer size of the eRedCap terminal according to the peak data rate of the uplink and the peak data rate of the downlink supported by the eRedCap terminal.

[0096] By applying the method for determining the layer 2 cache size provided in this embodiment, the peak data rate of the uplink supported by the eRedCap terminal can be determined based on the peak data rate of the uplink supported by the traditional terminal and the first scaling factor of the PUSCH channel, and the peak data rate of the downlink supported by the eRedCap terminal can be determined based on the peak data rate of the downlink supported by the traditional terminal and the second scaling factor of the PDSCH channel. Furthermore, based on the peak data rate of the uplink and the peak data rate of the downlink supported by the eRedCap terminal, the L2 total buffer size of the eRedCap terminal can be determined. Thus, an effective solution for determining the L2 total buffer size of the eRedCap terminal is provided to meet the updated requirements of the peak data rate of the eRedCap terminal and save costs.

[0097] Figure 6 FIG. is a schematic flow chart of a method for determining the layer 2 cache size according to one embodiment of the present application. Based on Figure 5 the embodiment shown, as Figure 6 shown, it can be applied to the eRedCap terminal side or the base station side, and may include the following steps.

[0098] Step 601, obtain the first scaling factor of the PUSCH channel and the second scaling factor of the PDSCH channel.

[0099] Wherein, both the first scaling factor and the second scaling factor are greater than 0 and less than 1.

[0100] Step 602, multiply the peak data rate of the uplink supported by the traditional terminal by the first scaling factor of the PUSCH channel to obtain the peak data rate of the uplink supported by the eRedCap terminal, and multiply the peak data rate of the downlink supported by the traditional terminal by the second scaling factor of the PDSCH channel to obtain the peak data rate of the downlink supported by the eRedCap terminal.

[0101] For example, multiply the peak data rate (peak data rate) of the uplink supported by the traditional terminal by the first scaling factor 1 / A1 (A1>1) of the PUSCH channel to obtain the peak data rate of the uplink supported by the eRedCap terminal, and multiply the peak data rate of the downlink supported by the traditional terminal by the second scaling factor 1 / A2 (A2>1) of the PDSCH channel to obtain the peak data rate of the downlink supported by the eRedCap terminal.

[0102] Step 603: Determine the Layer 2 buffer size of the eRedCap terminal according to the peak data rate of the uplink and the peak data rate of the downlink supported by the eRedCap terminal.

[0103] By applying the method provided in this embodiment, the peak data rate determination formula of the uplink supported by the traditional terminal can be multiplied by the first scaling factor of the PUSCH channel to obtain the peak data rate of the uplink supported by the eRedCap terminal, and the peak data rate determination formula of the downlink supported by the traditional terminal can be multiplied by the second scaling factor of the PDSCH channel to obtain the peak data rate of the downlink supported by the eRedCap terminal. Furthermore, based on the peak data rate of the uplink and the peak data rate of the downlink supported by the eRedCap terminal, the L2 total buffer size of the eRedCap terminal is determined. Thus, an effective solution for determining the L2 total buffer size for the eRedCap terminal is provided to meet the updated requirements of the peak data rate of the eRedCap terminal and save costs.

[0104] Figure 7 The flowchart shows one method for determining the Layer 2 buffer size according to an embodiment of the present application. Based on Figure 5 the illustrated embodiment, as Figure 7 shown, it can be applied to the eRedCap terminal side or the base station side. The method may include the following steps.

[0105] Step 701: Obtain the first scaling factor of the PUSCH channel and the second scaling factor of the PDSCH channel.

[0106] Among them, both the first scaling factor and the second scaling factor are greater than 0 and less than 1.

[0107] Step 702: Determine the peak data rate of the uplink supported by the eRedCap terminal according to the peak data rate of the uplink supported by the traditional terminal and the first scaling factor of the PUSCH channel, and determine the peak data rate of the downlink supported by the eRedCap terminal according to the peak data rate of the downlink supported by the traditional terminal and the second scaling factor of the PDSCH channel.

[0108] Step 703: Multiply the peak data rate of the uplink supported by the eRedCap terminal by the RLC RTT, add the result obtained by multiplying the peak data rate of the downlink supported by the eRedCap terminal by the RLC RTT, to obtain the Layer 2 buffer size of the eRedCap terminal.

[0109] Among them, RLC RTT is the round-trip delay of the radio link control layer. For example, the L2 total buffer size of the eRedCap terminal is calculated through Formula 3 (refer to Formula 3 in Step 403).

[0110] It should be noted that although Figure 7 the embodiments shown are described based on Figure 5 the embodiments shown, similarly, the Figure 7 embodiments shown can also be based on Figure 6 the embodiments shown, and will not be elaborated here.

[0111] By applying the method provided in this embodiment, the result obtained by multiplying the peak data rate of the uplink supported by the eRedCap terminal by RLC RTT, plus the result obtained by multiplying the peak data rate of the downlink supported by the eRedCap terminal by RLC RTT, is used to obtain the layer 2 buffer size of the eRedCap terminal. Furthermore, based on the peak data rate of the uplink and the peak data rate of the downlink supported by the eRedCap terminal, the L2 total buffer size of the eRedCap terminal is determined. Thus, an effective solution for determining the L2 total buffer size of the eRedCap terminal is provided to meet the update requirements of the peak data rate of the eRedCap terminal and save costs.

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

[0113] Step 801, obtain the peak data rate of the uplink supported by the eRedCap terminal specified in the communication protocol, and obtain the peak data rate of the downlink supported by the eRedCap terminal specified in the communication protocol.

[0114] For example, the specific value of the peak data rate of the eRedCap terminal can be directly specified in the communication protocol, where different values can be set for the uplink and downlink. Furthermore, the peak data rate of the uplink supported by the eRedCap terminal specified in the communication protocol can be obtained as the peak data rate of the uplink supported by the eRedCap terminal, and the peak data rate of the downlink supported by the eRedCap terminal specified in the communication protocol can be obtained as the peak data rate of the downlink supported by the eRedCap terminal.

[0115] Step 802: Determine the layer 2 buffer size of the eRedCap terminal according to the peak data rate of the uplink and the peak data rate of the downlink supported by the eRedCap terminal.

[0116] By applying the method for determining the layer 2 buffer size provided in this embodiment, the peak data rate of the uplink supported by the eRedCap terminal specified in the communication protocol can be obtained as the peak data rate of the uplink supported by the eRedCap terminal, and the peak data rate of the downlink supported by the eRedCap terminal specified in the communication protocol can be obtained as the peak data rate of the downlink supported by the eRedCap terminal. Furthermore, based on the peak data rate of the uplink and the peak data rate of the downlink supported by the eRedCap terminal, the L2 total buffer size of the eRedCap terminal is determined. Thus, an effective solution for determining the L2 total buffer size for the eRedCap terminal is provided to meet the update requirements of the peak data rate of the eRedCap terminal and save costs.

[0117] Figure 9 The flowchart shows one of the methods for determining the layer 2 buffer size according to an embodiment of the present application. Based on Figure 8 the embodiment shown, as Figure 9 shown, it can be applied to the eRedCap terminal side or the base station side. The method may include the following steps.

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

[0119] Step 902: Multiply the peak data rate of the uplink supported by the eRedCap terminal by the RLC RTT, and add the result obtained by multiplying the peak data rate of the downlink supported by the eRedCap terminal by the RLC RTT to obtain the Layer 2 buffer size of the eRedCap terminal.

[0120] Among them, RLC RTT is the round-trip delay of the Radio Link Control layer. For example, the L2 total buffer size of the eRedCap terminal is calculated through Formula 3 (refer to Formula 3 in Step 403).

[0121] By applying the method for determining the Layer 2 buffer size provided in this embodiment, multiply the peak data rate of the uplink supported by the eRedCap terminal by the RLC RTT, and add the result obtained by multiplying the peak data rate of the downlink supported by the eRedCap terminal by the RLC RTT to obtain the Layer 2 buffer size of the eRedCap terminal. Furthermore, based on the peak data rate of the uplink and the peak data rate of the downlink supported by the eRedCap terminal, determine the L2 total buffer size of the eRedCap terminal. Thus, an effective solution for determining the L2 total buffer size for the eRedCap terminal is provided to meet the update requirements of the peak data rate of the eRedCap terminal and save costs.

[0122] The above-mentioned Figures 2 to 4 The method shown is to determine the peak data rate of the uplink supported by the eRedCap terminal according to 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 within the time slot, and the peak data rate of the downlink supported by the eRedCap terminal can be determined according to 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 within the time slot. Furthermore, the Layer 2 buffer size of the eRedCap terminal is determined through the peak data rate of the uplink and the peak data rate of the downlink. The above-mentioned Figures 5 to 7The method shown is to determine the peak uplink data rate supported by the eRedCap terminal based on the peak uplink data rate supported by the traditional terminal and the first scaling factor 1 / A1 (A1>1) of the PUSCH channel, and to determine the peak downlink data rate supported by the eRedCap terminal based on the peak downlink data rate supported by the traditional terminal and the second scaling factor 1 / A2 (A2>1) of the PDSCH channel, and then to determine the layer 2 buffer size of the eRedCap terminal through the peak uplink data rate and the peak downlink data rate. And the above such as Figures 8 to 9 The method shown is to obtain the peak uplink data rate supported by the eRedCap terminal specified in the communication protocol, and to obtain the peak downlink data rate supported by the eRedCap terminal specified in the communication protocol, and then to determine the layer 2 buffer size of the eRedCap terminal through the peak uplink data rate and the peak downlink data rate.

[0123] It should be noted that the above several methods can also be comprehensively analyzed according to actual needs in actual use, and then the layer 2 buffer size of the eRedCap terminal can be determined. For example, corresponding priorities are pre-configured respectively, and then according to the priorities, the determination method with the highest priority is selected to obtain the layer 2 buffer size of the eRedCap terminal; for another example, the results obtained by these several determination methods can also be calculated by weighted average, and then the layer 2 buffer size of the eRedCap terminal can be determined, etc.

[0124] 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 the network device and the user equipment respectively. In order to implement the various functions in the methods provided by the embodiments of the present application, the network device and the user equipment may include a hardware structure and software modules, and implement the above various functions in the form of a hardware structure, a software module, or a combination of a hardware structure and a software module. A certain function among the above various functions can be executed in the form of a hardware structure, a software module, or a combination of a hardware structure and a software module.

[0125] Corresponding to the methods for determining the layer 2 buffer size provided by the above several embodiments, the present application also provides a device for determining the layer 2 buffer size, which can be applied to the eRedCap terminal or the base station side. The device may include: a determination module, configured to determine the layer 2 buffer size of the eRedCap terminal according to the peak uplink data rate and the peak downlink data rate supported by the eRedCap terminal. Since the device for determining the layer 2 buffer size provided by the embodiments of the present application corresponds to the methods for determining the layer 2 buffer size provided by the above several embodiments, the implementation manners of the methods for determining the layer 2 buffer size are also applicable to the device for determining the layer 2 buffer size provided by the present embodiment, and will not be described in detail in the present embodiment.

[0126] Figure 10 This is a schematic structural diagram of one of the apparatuses for determining the layer 2 cache size provided by an embodiment of the present application. As Figure 9 shown, the apparatus may specifically include: a first acquisition module 1010, configured to determine the peak data rate of the uplink supported by the eRedCap terminal according to the maximum transport block size (TBS) supported by the eRedCap terminal, the duration of the time slot, and the maximum number of transport blocks (TBs) supported by the eRedCap terminal within the time slot; and determine the peak data rate of the downlink supported by the eRedCap terminal according to 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 within the time slot; a first determination module 1020, configured to determine the layer 2 cache size of the eRedCap terminal according to the peak data rate of the uplink and the peak data rate of the downlink supported by the eRedCap terminal.

[0127] 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 the result by the duration of the time slot to obtain the peak data rate of the uplink supported by the eRedCap terminal.

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

[0129] In some embodiments, the first determination module 1020 is specifically configured to add the result obtained by multiplying the peak data rate of the uplink by the round-trip time (RTT) of the radio link control (RLC) layer to the result obtained by multiplying the peak data rate of the downlink by the RLC RTT to obtain the layer 2 cache size of the eRedCap terminal.

[0130] By applying the solution provided in this embodiment, the peak data rate of the uplink supported by the eRedCap terminal can be determined according to the maximum uplink TBS supported by the eRedCap terminal specified in the communication protocol, the duration of the time slot, and the maximum number of uplink TBs supported by the eRedCap terminal within the time slot. And the peak data rate of the downlink supported by the eRedCap terminal can be determined according to 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 within the time slot. Furthermore, based on the peak data rate of the uplink and the peak data rate of the downlink supported by the eRedCap terminal, the L2 total buffer size of the eRedCap terminal can be determined. Thus, an effective solution for determining the L2 total buffer size for the eRedCap terminal is provided to meet the update requirements of the peak data rate of the eRedCap terminal and save costs.

[0131] Figure 11 FIG. is a schematic structural diagram of one of the apparatuses for determining the layer 2 buffer size provided in the embodiments of the present application. As Figure 11 shown, the apparatus may specifically include: a second acquisition module 1110, configured to acquire a first scaling factor of the physical uplink shared channel PUSCH and a second scaling factor of the physical downlink shared channel PDSCH, where both the first scaling factor and the second scaling factor are greater than 0 and less than 1; determine the peak data rate of the uplink supported by the eRedCap terminal according to the peak data rate of the uplink supported by the legacy terminal and the first scaling factor; and determine the peak data rate of the downlink supported by the eRedCap terminal according to the peak data rate of the downlink supported by the legacy terminal and the second scaling factor; a second determination module 1120, configured to determine the layer 2 buffer size of the eRedCap terminal based on the peak data rate of the uplink and the peak data rate of the downlink supported by the eRedCap terminal.

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

[0133] In some embodiments, the second acquisition module 1110 is further specifically configured to multiply the peak data rate of the downlink supported by the legacy terminal by the second scaling factor to obtain the peak data rate of the downlink supported by the eRedCap terminal.

[0134] 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 radio link control layer, and add the result obtained by multiplying the downlink peak data rate by RLC RTT to obtain the layer 2 buffer size of the eRedCap terminal.

[0135] By applying the solution provided in this embodiment, the uplink peak data rate supported by the eRedCap terminal can be determined according to the uplink peak data rate supported by the traditional terminal and the first scaling factor of the PUSCH channel, and the downlink peak data rate supported by the eRedCap terminal can be determined according to the downlink peak data rate supported by the traditional terminal and the second scaling factor of the PDSCH channel. Furthermore, based on the uplink peak data rate and the downlink peak data rate supported by the eRedCap terminal, the L2 total buffer size of the eRedCap terminal is determined. Thus, an effective solution for determining the L2 total buffer size of the eRedCap terminal is provided to meet the update requirements of the peak data rate of the eRedCap terminal and save costs.

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

[0137] 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 radio link control layer, and add the result obtained by multiplying the downlink peak data rate by RLC RTT to obtain the layer 2 buffer size of the eRedCap terminal.

[0138] By applying the solution provided in this embodiment, the uplink peak data rate supported by the eRedCap terminal specified in the communication protocol can be obtained as the uplink 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 downlink peak data rate supported by the eRedCap terminal. Furthermore, based on the uplink peak data rate and the downlink peak data rate supported by the eRedCap terminal, the L2 total buffer size of the eRedCap terminal can be determined. Thus, an effective solution for determining the L2 total buffer size of the eRedCap terminal is provided to meet the update requirements of the peak data rate of the eRedCap terminal and save costs.

[0139] Please refer to Figure 13 , Figure 13 FIG. 1300 is a schematic structural diagram of a communication device 1300 provided in this embodiment. It can be applied to an eRedCap terminal or the base station side. The communication device 1300 can be a network device, a user equipment, a chip, a chip system, or a processor that supports the network device to implement the above method, or a chip, a chip system, or a processor that supports the user equipment to implement the above method. This device can be used to implement the method described in the above method embodiment. Specifically, please refer to the description in the above method embodiment.

[0140] The communication device 1300 may include one or more processors 1301. The processor 1301 can be a general-purpose processor or a dedicated processor, etc. 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, and the central processing unit can be used to control a communication device (such as a base station, a baseband chip, a terminal device, a terminal device chip, a DU or a CU, etc.), execute a computer program, and process the data of the computer program.

[0141] Optionally, the communication device 1300 may further include one or more memories 1302, on which a computer program 1204 may be stored. The processor 1301 executes the computer program 1304 to enable the communication device 1300 to execute the method described in the above method embodiment. Optionally, data may also be stored in the memory 1302. The communication device 1300 and the memory 1302 may be provided separately or integrated together.

[0142] Optionally, the communication device 1300 may further include a transceiver 1305 and an antenna 1306. The transceiver 1305 may be referred to as a transceiver unit, a transceiver, or a transceiver circuit, etc., for implementing a transceiver function. The transceiver 1205 may include a receiver and a transmitter, the receiver may be referred to as a receiver or a receiving circuit, etc., for implementing a receiving function; the transmitter may be referred to as a transmitter or a transmitting circuit, etc., for implementing a transmitting function.

[0143] Optionally, the communication device 1300 may further 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 the code instructions to enable the communication device 1300 to execute the method described in the above method embodiment.

[0144] In one implementation, the processor 1301 may include a transceiver for implementing the receiving and sending functions. For example, the transceiver may be a transceiver circuit, an interface, or an interface circuit. The transceiver circuit, interface, or interface circuit for implementing the receiving and sending functions may be separate or integrated. The above-mentioned transceiver circuit, interface, or interface circuit may be used for reading and writing code / data, or the above-mentioned transceiver circuit, interface, or interface circuit may be used for transmitting or delivering signals.

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

[0146] In one implementation, the communication device 1300 may include circuitry that can implement the functions of transmitting, receiving, or communicating in the foregoing method embodiments. The processor and transceiver described in this application may be implemented on an integrated circuit (IC), analog IC, radio frequency integrated circuit RFIC, mixed-signal IC, application specific integrated circuit (ASIC), printed circuit board (PCB), electronic device, etc. The processor and transceiver may also be fabricated using various IC process technologies, such as complementary metal oxide semiconductor (CMOS), N-type metal-oxide-semiconductor (NMOS), P-type metal-oxide semiconductor (PMOS), bipolar junction transistor (BJT), BiCMOS, silicon germanium (SiGe), gallium arsenide (GaAs), etc.

[0147] The communication device described in the above embodiments may be a network device or a 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 Figure 13 . The communication device may be an independent device or may be a part of a larger device. For example, the communication device may be:

[0148] (1) An independent integrated circuit IC, or chip, or chip system or subsystem;

[0149] (2) A collection of one or more ICs, optionally, the IC collection may also include a storage component for storing data and computer programs;

[0150] (3) ASIC, such as a modem;

[0151] (4) A module that can be embedded in other devices;

[0152] (5) A receiver, terminal device, smart terminal device, cellular phone, wireless device, handset, mobile unit, vehicle-mounted device, network device, cloud device, artificial intelligence device, etc.;

[0153] (6) Others, etc.

[0154] For the case where the communication device can be a chip or a chip system, reference can be made to Figure 14 the structural schematic diagram of the chip shown. Figure 14 The chip shown includes a processor 1401 and an interface 1402. Among them, the number of processors 1401 can be one or more, and the number of interfaces 1402 can be multiple.

[0155] Optionally, the chip further includes a memory 1403, and the memory 1403 is used to store necessary computer programs and data.

[0156] Those skilled in the art can also understand that the various illustrative logical blocks and steps listed in the embodiments of the present application can be implemented by electronic hardware, computer software, or a combination of the two. Whether such a function is implemented by hardware or software depends on the specific application and the design requirements of the entire system. For each specific application, those skilled in the art can use various methods to implement the described function, but such implementation should not be construed as exceeding the scope protected by the embodiments of the present application.

[0157] The present application also provides a computer storage medium, which can be applied to an eRedCap terminal or to the base station side, and instructions are stored thereon. When the instructions are executed by a computer, the functions of any one of the above method embodiments are implemented.

[0158] The present 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, the functions of any one of the above method embodiments are implemented.

[0159] In the above embodiments, it can be implemented in whole or in part by software, hardware, firmware, or any combination thereof. When implemented using software, it can be implemented in whole or in part in the form of a computer program product. The computer program product includes one or more computer programs. When the computer program is loaded and executed on a computer, the processes or functions according to the embodiments of the present application are generated in whole or in part. The computer can be a general-purpose computer, a special-purpose computer, a computer network, or other programmable devices. The computer program can be stored in a computer-readable storage medium, or transmitted from one computer-readable storage medium to another computer-readable storage medium. For example, the computer program can be transmitted from one website, computer, server, or data center to another website, computer, server, or data center by wire (such as coaxial cable, optical fiber, digital subscriber line (DSL)) or wirelessly (such as infrared, wireless, microwave, etc.). The computer-readable storage medium can be any available medium that the computer can access, or a data storage device such as a server or data center that includes one or more integrated available media. The available medium can be a magnetic medium (such as a floppy disk, hard disk, magnetic tape), an optical medium (such as a high-density digital video disc (DVD)), or a semiconductor medium (such as a solid state disk (SSD)), etc.

[0160] Those of ordinary skill in the art can understand that the various digital numbers such as the first and second involved in the present application are only for the convenience of description and are not used to limit the scope of the embodiments of the present application, nor do they represent the order of precedence.

[0161] At least one in the present application can also be described as one or more. The plurality can be two, three, four, or more, and the present application does not make any restrictions. In the embodiments of the present application, for a technical feature, the technical features in this technical feature are distinguished by "first", "second", "third", "A", "B", "C", and "D", etc. There is no order of precedence or size order among the technical features described by the "first", "second", "third", "A", "B", "C", and "D".

[0162] As used herein, the terms "machine-readable medium" and "computer-readable medium" refer to any computer program product, device, and / or apparatus (such as a magnetic disk, optical disk, memory, programmable logic device (PLD)) for providing machine instructions and / or data to a programmable processor, including a machine-readable medium that receives machine instructions as a machine-readable signal. The term "machine-readable signal" refers to any signal for providing machine instructions and / or data to a programmable processor.

[0163] The systems and techniques described herein can be implemented in a computing system including backend components (e.g., as a data server), or a computing system including middleware components (e.g., an application server), or a computing system including frontend components (e.g., a user computer having a graphical user interface or a web browser through which a user can interact with an implementation of the systems and techniques described herein), or a computing system including any combination of such backend components, middleware components, or frontend components. The components of the system can be interconnected to each other by digital data communication in any form or medium (e.g., a communication network). Examples of communication networks include: local area network (LAN), wide area network (WAN), and the Internet.

[0164] A computer system can include a client and a server. The client and the server are generally remote from each other and typically interact through a communication network. The client-server relationship is created by computer programs running on the respective computers and having a client-server relationship with each other.

[0165] It should be understood that various forms of the processes shown above can be used, steps can be reordered, added, or deleted. For example, the steps recited in this application can be executed in parallel, sequentially, or in a different order, as long as the desired results of the technical solutions of this application can be achieved, and no limitation is imposed herein.

[0166] In addition, it should be understood that the various embodiments described in this application can be implemented separately or, where the solution permits, in combination with other embodiments.

[0167] Those of ordinary skill in the art can realize that the units and algorithm steps of the examples described in connection with the embodiments claimed herein can be implemented in electronic hardware, or in a combination of computer software and electronic hardware. Whether these functions are executed in a hardware or software manner depends on the specific application and design constraints of the technical solution. A professional technician can use different methods for each specific application to implement the described functions, but such implementation should not be considered to exceed the scope of this application.

[0168] Those skilled in the art can clearly understand that, for the sake of convenience and brevity of description, the specific working processes of the systems, devices, and units described above can refer to the corresponding processes in the foregoing method embodiments and will not be elaborated herein.

[0169] As described above, it is only the specific implementation manner of this application, but the protection scope of this application is not limited thereto. Any person skilled in the art within the technical scope disclosed by this application can easily think of changes or substitutions, which should all be covered within the protection scope of this application. Therefore, the protection scope of this application shall be subject to the protection scope of the claims described.

Claims

1. A method for determining the size of a Layer 2 cache, characterized in that Execute on the eRedCap terminal side for the application with reduced capabilities, the method includes: Determine the Layer 2 cache size of the eRedCap terminal according to the peak data rate of the uplink and the peak data rate of the downlink supported by the eRedCap terminal; The peak data rate of the uplink supported by the eRedCap terminal is determined comprehensively according to the following items: The maximum uplink transport block size (TBS) supported by the eRedCap terminal, the duration of the time slot, and the maximum number of uplink transport blocks (TBs) supported by the eRedCap terminal within the time slot; The peak data rate of the uplink supported by the traditional terminal and the first scaling factor of the physical uplink shared channel (PUSCH), where the first scaling factor is greater than 0 and less than 1; The peak data rate of the uplink supported by the eRedCap terminal as specified in the communication protocol; The peak data rate of the downlink supported by the eRedCap terminal is determined comprehensively according to the following items: 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 within the time slot; The peak data rate of the downlink supported by the traditional terminal and the second scaling factor of the physical downlink shared channel (PDSCH), where the second scaling factor is greater than 0 and less than 1; The peak data rate of the downlink supported by the eRedCap terminal as specified in the communication protocol.

2. The method according to claim 1, wherein Determine the peak data rate of the uplink supported by the eRedCap terminal according to 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 within the time slot, including: Multiply the maximum uplink TBS by the maximum number of uplink TBs, and then divide by the duration of the time slot to obtain the peak data rate of the uplink supported by the eRedCap terminal.

3. The method according to claim 1, wherein Determine the peak data rate of the downlink supported by the eRedCap terminal according to 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 within the time slot, including: Multiply the maximum downlink TBS by the maximum number of downlink TBs, and then divide by the duration of the time slot to obtain the peak data rate of the downlink supported by the eRedCap terminal.

4. The method according to claim 1, wherein Determine the peak data rate of the uplink supported by the eRedCap terminal according to the peak data rate of the uplink supported by the traditional terminal and the first scaling factor, including: Multiply the peak data rate of the uplink supported by the traditional terminal by the first scaling factor to obtain the peak data rate of the uplink supported by the eRedCap terminal.

5. The method according to claim 1, wherein Determine the peak data rate of the downlink supported by the eRedCap terminal according to the peak data rate of the downlink supported by the traditional terminal and the second scaling factor, including: Multiply the peak data rate of the downlink supported by the traditional terminal by the second scaling factor to obtain the peak data rate of the downlink supported by the eRedCap terminal.

6. The method according to any one of claims 1 to 5, characterized in that, Determining the layer 2 buffer size of the eRedCap terminal according to the peak data rate of the uplink and the peak data rate of the downlink supported by the eRedCap terminal includes: Add the result obtained by multiplying the peak data rate of the uplink by the round-trip delay RLC RTT of the radio link control layer to the result obtained by multiplying the peak data rate of the downlink by RLC RTT to obtain the layer 2 buffer size of the eRedCap terminal.

7. A method for determining the Layer 2 cache size, characterized in that, Applied to be executed on the base station side, the method includes: Determine the layer 2 buffer size of the eRedCap terminal according to the peak data rate of the uplink and the peak data rate of the downlink supported by the eRedCap terminal; The peak data rate of the uplink supported by the eRedCap terminal is determined comprehensively according to the following items: The maximum uplink transport block size TBS supported by the eRedCap terminal, the duration of the time slot, and the maximum number of uplink transport blocks TB supported by the eRedCap terminal within the time slot; The peak data rate of the uplink supported by the traditional terminal and the first scaling factor of the physical uplink shared channel PUSCH, where the first scaling factor is greater than 0 and less than 1; The peak data rate of the uplink supported by the eRedCap terminal specified in the communication protocol; The peak data rate of the downlink supported by the eRedCap terminal is determined comprehensively according to the following items: 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 within the time slot; The peak data rate of the downlink supported by the traditional terminal and the second scaling factor of the physical downlink shared channel PDSCH, where the second scaling factor is greater than 0 and less than 1; The peak data rate of the downlink supported by the eRedCap terminal specified in the communication protocol.

8. The method according to claim 7, wherein Determining the peak data rate of the uplink supported by the eRedCap terminal according to 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 within the time slot includes: Multiply the maximum uplink TBS by the maximum number of uplink TBs, and then divide by the duration of the time slot to obtain the peak data rate of the uplink supported by the eRedCap terminal.

9. The method according to claim 7, wherein Determining the peak data rate of the downlink supported by the eRedCap terminal according to 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 within the time slot includes: Multiply the maximum downlink TBS by the maximum number of downlink TBs, and then divide by the duration of the time slot to obtain the peak data rate of the downlink supported by the eRedCap terminal.

10. The method according to claim 7, wherein Determining 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 includes: Multiplying the peak uplink data rate supported by the traditional terminal by the first scaling factor to obtain the peak uplink data rate supported by the eRedCap terminal.

11. The method according to claim 7, wherein Determining the peak downlink data rate supported by the eRedCap terminal according to the peak downlink data rate supported by the traditional terminal and the second scaling factor includes: Multiplying the peak downlink data rate supported by the traditional terminal by the second scaling factor to obtain the peak downlink data rate supported by the eRedCap terminal.

12. The method according to any one of claims 7 to 11, characterized in that Determining the layer 2 buffer size of the eRedCap terminal according to the peak uplink data rate and the peak downlink data rate supported by the eRedCap terminal includes: Adding the result obtained by multiplying the peak uplink data rate by the round-trip time RLC RTT of the radio link control layer to the result obtained by multiplying the peak downlink data rate by RLC RTT to obtain the layer 2 buffer size of the eRedCap terminal.

13. An apparatus for determining the size of a layer 2 cache, characterized in that, Applied to the side of the eRedCap terminal with reduced capabilities, the device includes: A determination module, configured to determine the layer 2 buffer size of the eRedCap terminal according to the peak uplink data rate and the peak downlink data rate supported by the eRedCap terminal; The peak uplink data rate supported by the eRedCap terminal is determined comprehensively according to the following items: The maximum uplink transport block size TBS supported by the eRedCap terminal, the duration of the time slot, and the maximum number of uplink transport blocks TB supported by the eRedCap terminal within the time slot; The peak uplink data rate supported by the traditional terminal and the first scaling factor of the physical uplink shared channel PUSCH, where the first scaling factor is greater than 0 and less than 1; The peak uplink data rate supported by the eRedCap terminal specified in the communication protocol; The peak downlink data rate supported by the eRedCap terminal is determined comprehensively according to the following items: 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 within the time slot; The peak downlink data rate supported by the traditional terminal and the second scaling factor of the physical downlink shared channel PDSCH, where the second scaling factor is greater than 0 and less than 1; The peak downlink data rate supported by the eRedCap terminal specified in the communication protocol.

14. A device for determining the size of a Layer 2 cache, characterized in that, Applied to the base station side, the device includes: A determination module, configured to determine the layer 2 buffer size of the eRedCap terminal according to the peak uplink data rate and the peak downlink data rate supported by the eRedCap terminal with reduced capabilities; The peak uplink data rate supported by the eRedCap terminal is determined comprehensively according to the following items: The maximum uplink transport block size TBS supported by the eRedCap terminal, the duration of a time slot, and the maximum number of uplink transport blocks TB supported by the eRedCap terminal within the time slot; The peak data rate of the uplink supported by a traditional terminal and a first scaling factor of the physical uplink shared channel PUSCH, where the first scaling factor is greater than 0 and less than 1; The peak data rate of the uplink supported by the eRedCap terminal as specified in the communication protocol; The peak data rate of the downlink supported by the eRedCap terminal is determined comprehensively based on the following items: 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 within the time slot; The peak data rate of the downlink supported by a traditional terminal and a second scaling factor of the physical downlink shared channel PDSCH, where the second scaling factor is greater than 0 and less than 1; The peak data rate of the downlink supported by the eRedCap terminal as specified in the communication protocol.

15. A communication device is applied to the eRedCap terminal side with degraded capabilities, where The communication device includes: a transceiver; a memory; a processor, which is respectively connected to the transceiver and the memory, and is configured to control the wireless signal transceiver of the transceiver by executing computer-executable instructions on the memory, and is capable of implementing the method according to any one of claims 1-6.

16. A communication device, applied to the base station side, wherein, The communication device includes: a transceiver; a memory; a processor, which is respectively connected to the transceiver and the memory, and is configured to control the wireless signal transceiver of the transceiver by executing computer-executable instructions on the memory, and is capable of implementing the method according to any one of claims 7-12.

17. A computer storage medium, applied to the eRedCap terminal side with degraded capabilities, wherein, The computer storage medium stores computer-executable instructions; after the computer-executable instructions are executed by a processor, the method according to any one of claims 1-6 can be implemented.

18. 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 a processor, the method according to any one of claims 7-12 can be implemented.

Images