Method for determining size of transmission block, base station and user equipment

Abstract

The invention discloses a method for determining the size of a transmission block, a base station and user equipment, and belongs to the field of communication. The method comprises: when an RRC connection has been established between a base station and a user equipment, the base station sending an RRC reconfiguration message to the user equipment, the RRC reconfiguration message comprising first overhead information and second overhead information; the first overhead information is used for describing a resource allocation strategy between the base station and the user equipment, the second overhead information indicates a candidate overhead set for a target resource element, and the target resource element is a resource element which cannot be used for data transmission; the base station receives an RRC reconfiguration completion message transmitted by the user equipment; in a data scheduling process, a base station sends downlink control information (DCI) to user equipment, the DCI comprises a target overhead field, and the target overhead field indicates the overhead number of resource elements of the scheduling; wherein the target overhead field is used for the user equipment to determine the size of the transmission block. The method is used for determining the size of the transmission block.

Description

Technical Field

[0001] The present application belongs to the field of communications, and in particular relates to a method for determining a transmission block size, a base station, and a user equipment. Background Art

[0002] Many digital communication systems, including 5G, need to go through cyclic redundancy check (CRC) calculation, code block segmentation and CRC addition, channel coding, rate matching, hybrid automatic repeat request (HARQ), scrambling, modulation, layer mapping, precoding, resource mapping and other processes before data transmission. Among them, the main reasons for rate matching are as follows: 1) After channel coding, an excess of check bit data that may be used for HARQ retransmission will be generated; 2) The receiving end confirms the code rate and other information of the physical layer transport block (TB) to be received based on the scheduling information, thereby determining the transport block size (TB Size) of this transmission.

[0003] In the process of determining the transmission block size, due to the existence of rate matching, the resource elements (RE) actually available for transmission may be less than the RE calculated theoretically, which will lead to inaccurate transmission block size, which may cause errors in parsing downlink data by user equipment (UE), reduce transmission reliability, and affect user downlink rate and experience. Summary of the invention

[0004] The embodiments of the present application provide a method for determining a transmission block size, a base station, and a user equipment, which can solve the problem of inaccurate transmission block size determined by related technologies.

[0005] In a first aspect, an embodiment of the present application provides a method for determining a transport block size, including: In a case where a radio resource control (RRC) connection has been established between a base station and a user equipment, the base station sends an RRC reconfiguration message to the user equipment, the RRC reconfiguration message including a serving cell configuration information element of a physical shared channel, the serving cell configuration information element including first overhead information and second overhead information; the first overhead information is related to a signal overhead transmitted on the physical shared channel and is used to describe a resource allocation strategy between the base station and the user equipment, and the second overhead information indicates a candidate overhead set for a target resource element, the target resource element being a resource element that cannot be used for data transmission; The base station receives an RRC reconfiguration complete message transmitted by the user equipment; The base station sends downlink control information (Downlink Control Information, DCI) to the user equipment during data scheduling, the DCI including a target overhead field, the target overhead field indicating the number of resource element overheads for this scheduling; The target overhead field is used to determine the transmission block size.

[0006] In a second aspect, an embodiment of the present application provides another method for determining a transport block size, including: In a case where an RRC connection has been established between a base station and a user equipment, the user equipment receives an RRC reconfiguration message sent by the base station, the RRC reconfiguration message includes a serving cell configuration information element of a physical shared channel, the serving cell configuration information element includes first overhead information and second overhead information; the first overhead information is related to a signal overhead transmitted on the physical shared channel, and is used to describe a resource allocation strategy between the base station and the user equipment, and the second overhead information indicates a candidate overhead set for a target resource element, and the target resource element is a resource element that cannot be used for data transmission; The user equipment transmits an RRC reconfiguration complete message to the base station; The user equipment receives the DCI sent by the base station during data scheduling, where the DCI includes a target overhead field, where the target overhead field indicates the number of resource element overheads for this scheduling; The user equipment determines a transport block size based on the target overhead field.

[0007] In a third aspect, a base station is provided, including: a sending module, configured to send an RRC reconfiguration message to a user equipment when an RRC connection has been established between the base station and the user equipment, the RRC reconfiguration message comprising a serving cell configuration information element of a physical shared channel, the serving cell configuration information element comprising first overhead information and second overhead information; the first overhead information is related to a signal overhead transmitted on the physical shared channel and is used to describe a resource allocation strategy between the base station and the user equipment, the second overhead information indicates a candidate overhead set for a target resource element, the target resource element being a resource element that cannot be used for data transmission; A receiving module, configured to receive an RRC reconfiguration completion message transmitted by the user equipment; The sending module is further used to send DCI to the user equipment during data scheduling, where the DCI includes a target overhead field, and the target overhead field indicates the number of resource element overheads for this scheduling; The target overhead field is used to determine the transmission block size.

[0008] In a fourth aspect, a user equipment is provided, including: A receiving module, configured to receive an RRC reconfiguration message sent by the base station when an RRC connection has been established between the base station and the user equipment, the RRC reconfiguration message comprising a serving cell configuration information element of a physical shared channel, the serving cell configuration information element comprising first overhead information and second overhead information; the first overhead information is related to the signal overhead transmitted on the physical shared channel, and is used to describe a resource allocation strategy between the base station and the user equipment, and the second overhead information indicates a candidate overhead set for a target resource element, and the target resource element is a resource element that cannot be used for data transmission; A sending module, used for transmitting an RRC reconfiguration completion message to the base station; The receiving module is further configured to receive a DCI sent by the base station during data scheduling, wherein the DCI includes a target overhead field, and the target overhead field indicates the number of resource element overheads for this scheduling; A processing module is used to determine a transport block size based on the target overhead field.

[0009] At least one of the above technical solutions provided in the embodiments of the present application can achieve the following technical effects: In an embodiment of the present application, the base station sends an RRC reconfiguration message to the user equipment, the RRC reconfiguration message includes second overhead information, the second overhead information indicates a candidate overhead set for a target resource element, and the target resource element is a resource element that cannot be used for data transmission; after the RRC reconfiguration is completed, the base station sends a DCI to the user equipment during data scheduling, the DCI includes a target overhead field, and the target overhead field indicates the number of resource element overheads for this scheduling; wherein the target overhead field is used to determine the transmission block size. In this way, through the second overhead information and the target overhead field in the DCI, the user equipment can obtain the number of resource element overheads for this scheduling (i.e., the accurate number of resource element overheads), and then determine the accurate transmission block size accordingly, solving the problem of inaccurate transmission block size determined by related technologies. BRIEF DESCRIPTION OF THE DRAWINGS

[0010] In order to more clearly illustrate the technical solutions of the embodiments of the present invention, the drawings required for use in the embodiments are briefly introduced below. It should be understood that the following drawings only show certain embodiments of the present invention and therefore should not be regarded as limiting the scope. For ordinary technicians in this field, other related drawings can be obtained based on these drawings without creative work.

[0011] Figure 1 is a flow chart of a method for determining a transport block size provided by an embodiment of the present application; Figure 2 is a schematic diagram of a process in which a UE accesses a base station in an embodiment of the present application; Figure 3 is a flowchart of another method for determining a transport block size provided by an embodiment of the present application; Figure 4 is a structural block diagram of a base station provided in an embodiment of the present application; Figure 5 It is a structural block diagram of a user equipment provided in an embodiment of the present application. DETAILED DESCRIPTION

[0012] The following will be combined with the drawings in the embodiments of the present application to clearly describe the technical solutions in the embodiments of the present application. Obviously, the described embodiments are part of the embodiments of the present application, not all of the embodiments. Based on the embodiments in the present application, all other embodiments obtained by ordinary technicians in this field without creative work are within the scope of protection of this application.

[0013] The terms "first", "second", etc. in the specification and claims of the present application are used to distinguish similar objects, and are not used to describe a specific order or sequence. It should be understood that the data used in this way can be interchangeable under appropriate circumstances, so that the embodiments of the present application can be implemented in an order other than those illustrated or described here, and the objects distinguished by "first", "second", etc. are generally of one type, and the number of objects is not limited. For example, the first object can be one or more. In addition, "and / or" in the specification and claims represents at least one of the connected objects, and the character " / " generally indicates that the objects associated with each other are in an "or" relationship.

[0014] Therefore, the following detailed description of the embodiments of the present invention provided in the accompanying drawings is not intended to limit the scope of the invention claimed for protection, but merely represents selected embodiments of the present invention. Based on the embodiments of the present invention, all other embodiments obtained by ordinary technicians in this field without creative work are within the scope of protection of the present invention.

[0015] In the embodiment of the present application, the receiving end can confirm the code rate, modulation and coding scheme (MCS), number of transmission layers and physical resource allocation of the physical layer transport block (TB) to be received based on the scheduling information, so as to determine the transport block size (TB Size) of this transmission. Before the sending end confirms the transport block size, it first determines the number of resource elements (RE) available in each physical resource block (PRB) in the scheduled time slot (Slot). The specific calculation formula is as follows: Formula (1) Formula (2) in, is the number of subcarriers per physical resource block (PRB), It is the number of OFDM (Orthogonal Frequency Division Multiplexing) symbols used to allocate transmission service data in each time slot. It is the number of REs of the demodulation reference signal (DM-RS) in each PRB that is not used for data transmission within the scheduling period (e.g., time slot). It is an additional overhead parameter (xOverhead) configured by the higher layer in the serving cell configuration information element (PDSCH-ServingCellConfig / PUSCH-ServingCellConfig information element) of the physical shared channel. is the number of PRBs allocated to the receiving end.

[0016] However, in actual transmission, there may be more REs in the scheduled time slot that cannot be used to transmit service data. These REs include the Phase Track Reference Signal (PT-RS), the Non-Zero-Power / Zero-Power Channel Status Information Reference Signal (NZP / ZP CSI-RS), and other high-level configured resources that are not used for service data transmission.

[0017] The above situation may result in the number of available bits determined by the actual number of resources for each transmission being less than the number of coded bits. Therefore, the bits that cannot be transmitted need to be removed before transmission to match the actual resources. This is what rate matching does.

[0018] In the embodiment of the present application, when the receiving end UE side confirms the size of the physical layer transmission block to be received according to the scheduling information, it is determined by formula (1), formula (2) and the following formula (3): Formula (3) in, is the transport block size, i.e. the number of information bits transmitted, is the bit rate, is the modulation order (MCS), is the number of transmission layers, such as the number of Multiple-Input Multiple-Output (MIMO) layers.

[0019] Due to the existence of rate matching in the related art, the RE available for actual transmission may be less than the RE obtained by formula (2), which leads to inaccurate transmission blocks calculated by formula (3).

[0020] The embodiment of the present application can accurately calculate the transmission block size, ensure that the current transmission block size and the code rate corresponding to the scheduling resource can match the channel conditions, and at the same time do not increase additional system overhead, improve transmission reliability, and improve user rate and experience. Figure 1 Discuss.

[0021] Figure 1 is a flow chart of a method for determining a transmission block size provided by an embodiment of the present application. Figure 1 , the method for determining the transport block size provided in the embodiment of the present application may include: Step 110: When an RRC connection has been established between the base station and the user equipment, the base station sends an RRC reconfiguration message to the user equipment, where the RRC reconfiguration message includes a serving cell configuration information element of a physical shared channel, where the serving cell configuration information element includes first overhead information and second overhead information; the first overhead information is related to a signal overhead transmitted on the physical shared channel and is used to describe a resource allocation strategy between the base station and the user equipment, and the second overhead information indicates a candidate overhead set for a target resource element, where the target resource element is a resource element that cannot be used for data transmission; In the embodiment of the present application, the process of UE accessing the base station can refer to Figure 2 .like Figure 2As shown, first, the UE establishes an RRC connection with the base station. The specific process of establishing an RRC connection includes: the UE sends an RRC connection establishment request to the base station, the base station establishes an RRC connection with the UE based on the RRC connection establishment request, and then the UE sends an RRC connection establishment completion message to the base station. After the RRC connection is established, the base station can perform the process of UE capability information query and security activation. Specifically, the base station queries the UE's capability information by sending a UE capability information query (UECapabilityEnquiry) instruction. After receiving the instruction, the UE reports its own capability information (UECapabilityInformation) according to the instruction. UE capability information includes network capability and wireless capability. The network capability involves interaction with the core network, while the wireless capability involves querying the radio capability. The security mode command (SMC) is part of 5G authentication and security, and the correct configuration of the security mode can be ensured through SMC. Through these steps, the base station can accurately understand the capabilities of the UE, and perform correct scheduling and configuration according to its capabilities, while ensuring security during the communication process.

[0022] After the RRC connection establishment is completed and the UE capability information query and security activation processes are performed, the base station may send an RRC reconfiguration message to the user equipment.

[0023] In step 110, the physical shared channel may include at least one of a physical downlink shared channel (PDSCH) and a physical uplink shared channel (PUSCH). The first overhead information may be an overhead field (xOverhead) in a serving cell configuration (ServingCellConfig) information element, and the second overhead information may be an overhead list field (xOver-headList) in a serving cell configuration (ServingCellConfig) information element. The first overhead information and the second overhead information are two independent specific contents in the serving cell configuration (ServingCellConfig) information element.

[0024] In 5G New Radio (NR), PDSCH-ServingCellConfig and PUSCH-ServingCellConfig are signal and resource configuration items involved in downlink and uplink resource configuration. These configuration items are closely related to the signal exchange between user equipment and base stations, and contain detailed information about physical channels and corresponding configurations.

[0025] Among these configuration items, xOverhead is an important configuration parameter, which is usually used to specify information about the "extra overhead" or "extra resource requirements" of the relevant channels. Specifically, xOverhead can affect the efficiency of scheduling and resource allocation, especially in terms of resource pools, scheduling requests, or scheduling delays for uplink and downlink. xOverhead is mainly related to the overhead of PDSCH (Physical Downlink Shared Channel) and PUSCH (Physical Uplink Shared Channel) signal transmission.

[0026] xOverhead is usually an integer value that specifies the degree of overhead or additional resource allocation. This value can be used to describe the resource allocation strategy between the UE and the base station, including the adjustment of uplink and downlink resources based on load and scheduling requests.

[0027] The contents of xOverhead can be as follows: Uplink and downlink scheduling overhead: The xOverhead configuration item will be dynamically adjusted according to the system load and scheduling requirements, affecting the scheduling of uplink (PUSCH) and downlink (PDSCH).

[0028] PUSCH / PDSCH resource allocation strategy: This configuration may affect the specific transport block size, scheduling period, number of resource blocks, etc. to ensure the stability of uplink and downlink signal transmission.

[0029] Scheduling request and transmission timing: For resource overhead of PUSCH or PDSCH, the xOverhead configuration may affect the allocation of time slots, symbols, etc., as well as the period and frequency of data transmission.

[0030] In an embodiment of the present application, the second overhead information may be new information in the serving cell configuration (ServingCellConfig) information element. When the second overhead information is an overhead list field (xOver-headList), the overhead list field (xOver-headList) may be a new field in the serving cell configuration (ServingCellConfig) information element. The overhead list field may be an enumeration value or a data set containing specific values. The following is a detailed description.

[0031] The second overhead information (eg, xOver-headList) is a sequence including, for example, 16 candidate overhead elements. Each element is in the form of a structure, for example, and the structure includes a field named overhead, which is an integer ranging from 1 to 16.

[0032] Each candidate overhead element in the second overhead information (eg, xOver-headList) includes an overhead value. For example, the second overhead information (eg, xOver-headList) includes a maximum number of candidate overhead elements (eg, 16 elements), each of which includes a specific data value. Taking 16 elements as an example, the second overhead information (for example, xOver-headList) contains 16 elements: element 1 { overhead 1}, element 2 { overhead 2}, element 3 { overhead 3}, element 4 { overhead 4}, element 5 { overhead 5}, element 6 { overhead 6}, element 7 { overhead 7}, element 8 { overhead 8}, element 9 { overhead 9}, element 10 { overhead 10}, element 11 { overhead 11}, element 12 { overhead 12}, element 13 { overhead 13}, element 14 { overhead 14}, element 15 { overhead15}, element 16 { overhead 16}.

[0033] In this step, after the UE receives the RRC reconfiguration message sent by the base station, it can know the scheduling related information in advance. The UE can store the RRC reconfiguration message and feed back an RRC reconfiguration completion message to the base station to inform the base station that it has correctly received the RRC reconfiguration message.

[0034] Step 120, the base station receives an RRC reconfiguration complete message transmitted by the user equipment; Step 130: the base station sends a DCI to the user equipment during data scheduling, where the DCI includes a target overhead field, and the target overhead field indicates the number of resource element overheads for this scheduling; The target overhead field may be located in the part of the DCI related to scheduling resource allocation, and is used to determine the transport block size. The specific process of determining the transport block size may refer to the formula (3) mentioned above.

[0035] When scheduling data, a 4-bit target overhead field (xOverHead) can be added to the DCI of the scheduling (DCI 0_1, DCI 1_1, etc.). The relevant information of the target overhead field can be as follows;

[0036] In the embodiment of the present application, the target overhead field in the DCI is a field occupying n bits, and the number of the candidate overhead elements is 2 n , where n is an integer. In the above table, taking n as 4 bits as an example, the number of candidate overhead elements can be 16. If the target overhead field is 0000, it can represent the value of the first element of the candidate overhead set (or the last one), that is, element 1 { overhead 1} (or element 16 { overhead 16}).

[0037] In the embodiment of the present application, the candidate overhead set includes multiple candidate overhead elements, and each candidate overhead element includes an overhead value. The number of resource element overheads indicated by the target overhead field corresponds to the overhead value of a candidate overhead element among the multiple candidate overhead elements. That is to say, after receiving the DCI sent by the base station, the UE can confirm the specific RE overhead value of this scheduling in the set of the number of REs not used for data transmission carried in the previous base station RRC reconfiguration message based on the information of the DCI. In this way, the user equipment can obtain the number of resource element overheads for this scheduling (that is, the accurate number of resource element overheads) from multiple candidate overhead elements.

[0038] From the above, it can be seen that when the UE accesses, the base station configures the second overhead information (such as xOver-headList) to the UE through signaling. During dynamic scheduling, when there are REs occupied by other channels in the scheduled time slot, the UE is notified of the exact number of RE overheads through the DCI target overhead field (such as the xOverHead field). Then, the UE can use the formula for the available REs of the data channel and the formula for the transmission block size to accurately calculate the transmission block size scheduled in this time slot.

[0039] In an embodiment of the present application, the base station sends an RRC reconfiguration message to the user equipment, the RRC reconfiguration message includes second overhead information, the second overhead information indicates a candidate overhead set for a target resource element, and the target resource element is a resource element that cannot be used for data transmission; after the RRC reconfiguration is completed, the base station sends a DCI to the user equipment during data scheduling, the DCI includes a target overhead field, and the target overhead field indicates the number of resource element overheads for this scheduling; wherein the target overhead field is used to determine the transmission block size. In this way, through the second overhead information and the target overhead field in the DCI, the user equipment can obtain the number of resource element overheads for this scheduling (i.e., the accurate number of resource element overheads), and then determine the accurate transmission block size accordingly, solving the problem of inaccurate transmission block size determined by related technologies.

[0040] In another embodiment of the present application, the number of resource element overheads indicated by the target overhead field is the number of resource element overheads for one time slot. In this way, the method for determining the transport block size provided by the embodiment of the present application can achieve accurate calculation of the transport block at the time slot level.

[0041] In the embodiment of the present application, the number of resource element overheads indicated by the target overhead field may change with the change of the time slot, so that the real-time dynamic adjustment of the number of resource element overheads can be achieved to ensure the accuracy of the transmission block at the time slot level.

[0042] Moreover, by notifying the UE of the accurate number of RE overheads through DCI, real-time dynamic adjustment can be achieved without requiring more system overhead, thereby solving the problems of inaccuracy caused by using high-level signaling to configure universal values ​​and excessive system overhead caused by using MCS adjustment.

[0043] In the embodiment of the present application, on the one hand, the second overhead information (e.g., xOver-HeadList) configured by the newly added RRC signaling can notify the terminal of the candidate RE overhead set; on the other hand, the target overhead field (e.g., xOverHead) for indicating the number of RE overheads in the newly added DCI scheduling can indicate that the RE overhead of this scheduling corresponds to a specific value in the candidate overhead set configured by the RRC signaling. In this way, the UE can identify the target overhead field in the DCI through the second overhead information, and then accurately determine the transport block size according to the target overhead field.

[0044] Figure 3 1 is a flow chart of a method for determining a transmission block size provided by an embodiment of the present application. Figure 3 , the method for determining the transport block size provided in the embodiment of the present application may include: Step 310: When an RRC connection has been established between a base station and a user equipment, the user equipment receives an RRC reconfiguration message sent by the base station, where the RRC reconfiguration message includes a serving cell configuration information element of a physical shared channel, where the serving cell configuration information element includes first overhead information and second overhead information; the first overhead information is related to a signal overhead transmitted on the physical shared channel and is used to describe a resource allocation strategy between the base station and the user equipment, and the second overhead information indicates a candidate overhead set for a target resource element, where the target resource element is a resource element that cannot be used for data transmission; In the embodiment of the present application, the candidate overhead set includes multiple candidate overhead elements, and each candidate overhead element includes an overhead value. The number of resource element overheads indicated by the target overhead field corresponds to the overhead value of a candidate overhead element among the multiple candidate overhead elements. That is to say, after receiving the DCI sent by the base station, the UE can confirm the specific RE overhead value of this scheduling in the set of the number of REs not used for data transmission carried in the previous base station RRC reconfiguration message based on the information of the DCI. In this way, the user equipment can obtain the number of resource element overheads for this scheduling (that is, the accurate number of resource element overheads) from multiple candidate overhead elements.

[0045] Step 320, the user equipment transmits an RRC reconfiguration complete message to the base station; Step 330: The user equipment receives the DCI sent by the base station during data scheduling, where the DCI includes a target overhead field, and the target overhead field indicates the number of resource element overheads for this scheduling; Step 340: The user equipment determines a transport block size based on the target overhead field.

[0046] The specific process of the user equipment determining the transport block size based on the target overhead field in step 340 may refer to the above formulas (1) to (3).

[0047] In an embodiment of the present application, a user equipment receives an RRC reconfiguration message sent by the base station, the RRC reconfiguration message includes second overhead information, the second overhead information indicates a candidate overhead set for a target resource element, the target resource element is a resource element that cannot be used for data transmission; after the RRC reconfiguration is completed, the user equipment receives a DCI sent by the base station during data scheduling, the DCI includes a target overhead field, the target overhead field indicates the number of resource element overheads for this scheduling; wherein the target overhead field is used to determine the transmission block size. In this way, through the second overhead information and the target overhead field in the DCI, the user equipment can obtain the number of resource element overheads for this scheduling (i.e., the accurate number of resource element overheads), and then determine the accurate transmission block size accordingly, solving the problem of inaccurate transmission block size determined by related technologies.

[0048] In another embodiment of the present application, the number of resource element overheads indicated by the target overhead field is the number of resource element overheads for one time slot. In this way, the method for determining the transmission block size provided by the embodiment of the present application can realize accurate calculation of the transmission block at the time slot level. In the embodiment of the present application, the number of resource element overheads indicated by the target overhead field can change with the change of the time slot. In this way, the real-time dynamic adjustment of the number of resource element overheads can be realized to ensure the accuracy of the transmission block at the time slot level.

[0049] Moreover, by notifying the UE of the accurate number of RE overheads through DCI, real-time dynamic adjustment can be achieved without requiring more system overhead, thereby solving the problems of inaccuracy caused by using high-level signaling to configure universal values ​​and excessive system overhead caused by using MCS adjustment.

[0050] In the embodiment of the present application, on the one hand, the second overhead information (e.g., xOver-HeadList) configured by the newly added RRC signaling can notify the terminal of the candidate RE overhead set; on the other hand, the target overhead field (e.g., xOverHead) for indicating the number of RE overheads in the newly added DCI scheduling can indicate that the RE overhead of this scheduling corresponds to a specific value in the candidate overhead set configured by the RRC signaling. In this way, the UE can identify the target overhead field in the DCI through the second overhead information, and then accurately determine the transport block size according to the target overhead field.

[0051] It is important to understand that Figure 3 The relevant contents of each step in the embodiment shown can be referred to the above discussion, for example, Figure 1 and Figure 2 That is to say, the relevant contents of each embodiment of the present application can be referenced to each other and will not be repeated here.

[0052] Figure 4 is a structural block diagram of a base station provided in an embodiment of the present application. Figure 4 The base station 400 provided in the embodiment of the present application includes: a sending module 410 and a receiving module 420. Among them: A sending module 410 is configured to send an RRC reconfiguration message to a user equipment when an RRC connection has been established between the base station and the user equipment, wherein the RRC reconfiguration message includes a serving cell configuration information element of a physical shared channel, and the serving cell configuration information element includes first overhead information and second overhead information; the first overhead information is related to a signal overhead transmitted on the physical shared channel and is used to describe a resource allocation strategy between the base station and the user equipment, and the second overhead information indicates a candidate overhead set for a target resource element, and the target resource element is a resource element that cannot be used for data transmission; The receiving module 420 is configured to receive an RRC reconfiguration completion message transmitted by the user equipment; The sending module 410 is further configured to send DCI to the user equipment during data scheduling, where the DCI includes a target overhead field, where the target overhead field indicates the number of resource element overheads for this scheduling; The target overhead field is used by the user equipment to determine the transport block size.

[0053] In the base station provided in the embodiment of the present application, the base station sends an RRC reconfiguration message to the user equipment, the RRC reconfiguration message includes second overhead information, the second overhead information indicates a candidate overhead set for a target resource element, and the target resource element is a resource element that cannot be used for data transmission; after the RRC reconfiguration is completed, the base station sends a DCI to the user equipment during data scheduling, the DCI includes a target overhead field, and the target overhead field indicates the number of resource element overheads for this scheduling; wherein the target overhead field is used to determine the transmission block size. In this way, through the second overhead information and the target overhead field in the DCI, the user equipment can obtain the number of resource element overheads for this scheduling (i.e., the accurate number of resource element overheads), and then determine the accurate transmission block size accordingly, solving the problem of inaccurate transmission block size determined by related technologies.

[0054] In an embodiment of the present application, the candidate overhead set includes multiple candidate overhead elements, each candidate overhead element contains an overhead value; the number of resource element overheads indicated by the target overhead field corresponds to the overhead value of a candidate overhead element among the multiple candidate overhead elements.

[0055] In one embodiment of the present application, the number of resource element overheads indicated by the target overhead field is the number of resource element overheads for one time slot.

[0056] In another embodiment of the present application, the number of resource element overheads indicated by the target overhead field varies with the time slot.

[0057] In addition, the target overhead field in the embodiment of the present application is a field occupying n bits, and the number of the candidate overhead elements is 2. n , where n is an integer.

[0058] The base station provided in the embodiment of the present application can achieve Figure 1 For the various processes in the illustrated method embodiment, the relevant contents can be referred to the method embodiment, and will not be described again here to avoid repetition.

[0059] Figure 5 is a structural block diagram of a user equipment provided in an embodiment of the present application. Figure 5 The user equipment 500 provided in the embodiment of the present application includes: a receiving module 510, a sending module 520 and a processing module 530. Among them: The receiving module 510 is configured to receive an RRC reconfiguration message sent by the base station when an RRC connection has been established between the base station and the user equipment, the RRC reconfiguration message including a serving cell configuration information element of a physical shared channel, the serving cell configuration information element including first overhead information and second overhead information; the first overhead information is related to the signal overhead transmitted on the physical shared channel, and is used to describe a resource allocation strategy between the base station and the user equipment, and the second overhead information indicates a candidate overhead set for a target resource element, and the target resource element is a resource element that cannot be used for data transmission; A sending module 520, configured to transmit an RRC reconfiguration completion message to the base station; The receiving module 510 is further configured to receive a DCI sent by the base station during data scheduling, wherein the DCI includes a target overhead field, and the target overhead field indicates the number of resource element overheads for this scheduling; The processing module 530 is configured to determine a transport block size based on the target overhead field.

[0060] In the user equipment provided in the embodiment of the present application, the RRC reconfiguration message sent by the base station is received, and the RRC reconfiguration message includes second overhead information, and the second overhead information indicates a candidate overhead set for a target resource element, and the target resource element is a resource element that cannot be used for data transmission; after the RRC reconfiguration is completed, the DCI sent by the base station in the process of data scheduling is received, and the DCI includes a target overhead field, and the target overhead field indicates the number of resource element overheads scheduled this time; wherein the target overhead field is used to determine the transmission block size. In this way, through the second overhead information and the target overhead field in the DCI, the user equipment can obtain the number of resource element overheads scheduled this time (that is, the accurate number of resource element overheads), and then determine the accurate transmission block size accordingly, solving the problem of inaccurate transmission block size determined by related technologies.

[0061] In an embodiment of the present application, the candidate overhead set includes a plurality of candidate overhead elements, each candidate overhead element including an overhead value; The number of resource element overheads indicated by the target overhead field corresponds to an overhead value of a candidate overhead element among the multiple candidate overhead elements.

[0062] In an embodiment of the present application, the number of resource element overheads indicated by the target overhead field is the number of resource element overheads for a time slot; the number of resource element overheads indicated by the target overhead field changes with the change of the time slot.

[0063] The user equipment provided in the embodiment of the present application can achieve Figure 3For the various processes in the illustrated method embodiment, the relevant contents can be referred to the method embodiment, and will not be described again here to avoid repetition.

[0064] An embodiment of the present application also provides a readable storage medium, on which a program or instruction is stored. When the program or instruction is executed by a processor, the steps of each embodiment of the method for determining the size of a transmission block are implemented, and the same technical effect can be achieved. To avoid repetition, it will not be repeated here.

[0065] The readable storage medium includes a computer-readable storage medium, such as a computer read-only memory ROM, a random access memory RAM, a magnetic disk or an optical disk.

[0066] An embodiment of the present application further provides a chip, which includes a processor and a communication interface, wherein the communication interface is coupled to the processor, and the processor is used to run programs or instructions to implement the various processes of the above-mentioned method embodiment, and can achieve the same technical effect. To avoid repetition, it will not be repeated here.

[0067] An embodiment of the present application provides a computer program product, which is stored in a storage medium. The program product is executed by at least one processor to implement the various processes of the above-mentioned method embodiment and can achieve the same technical effect. To avoid repetition, it will not be repeated here.

[0068] It should be noted that, in this article, the terms "comprise", "include" or any other variant thereof are intended to cover non-exclusive inclusion, so that the process, method, article or device including a series of elements includes not only those elements, but also includes other elements not explicitly listed, or also includes elements inherent to such process, method, article or device. In the absence of further restrictions, the elements defined by the sentence "comprise one..." do not exclude the presence of other identical elements in the process, method, article or device including the element. In addition, it should be pointed out that the scope of the methods and devices in the embodiments of the present application is not limited to performing functions in the order shown or discussed, and may also include performing functions in a substantially simultaneous manner or in reverse order according to the functions involved, for example, the described method may be performed in an order different from that described, and various steps may also be added, omitted, or combined. In addition, the features described with reference to certain examples may be combined in other examples.

[0069] Through the description of the above implementation methods, those skilled in the art can clearly understand that the above-mentioned embodiment methods can be implemented by means of software plus a necessary general hardware platform, and of course by hardware, but in many cases the former is a better implementation method. Based on such an understanding, the technical solution of the present application, or the part that contributes to the prior art, can be embodied in the form of a computer software product, which is stored in a storage medium (such as ROM / RAM, a magnetic disk, or an optical disk), and includes a number of instructions for enabling a terminal (which can be a mobile phone, a computer, a server, or a network device, etc.) to execute the methods described in each embodiment of the present application.

[0070] The embodiments of the present application are described above in conjunction with the accompanying drawings, but the present application is not limited to the above-mentioned specific implementation methods. The above-mentioned specific implementation methods are merely illustrative and not restrictive. Under the guidance of the present application, ordinary technicians in this field can also make many forms without departing from the purpose of the present application and the scope of protection of the claims, all of which are within the protection of the present application.

Claims

1. A method for determining a transport block size, characterized in that: include: In a case where a radio resource control RRC connection has been established between a base station and a user equipment, the base station sends an RRC reconfiguration message to the user equipment, the RRC reconfiguration message includes a serving cell configuration information element of a physical shared channel, the serving cell configuration information element includes first overhead information and second overhead information; the first overhead information is related to a signal overhead transmitted on the physical shared channel, and is used to describe a resource allocation strategy between the base station and the user equipment, and the second overhead information indicates a candidate overhead set for a target resource element, and the target resource element is a resource element that cannot be used for data transmission; The base station receives an RRC reconfiguration complete message transmitted by the user equipment; The base station sends downlink control information DCI to the user equipment during data scheduling, where the DCI includes a target overhead field, where the target overhead field indicates the number of resource element overheads for this scheduling; The target overhead field is used to determine the transmission block size.

2. The method according to claim 1, characterized in that: The candidate cost set includes a plurality of candidate cost elements, each candidate cost element includes a cost value; The number of resource element overheads indicated by the target overhead field corresponds to an overhead value of a candidate overhead element among the multiple candidate overhead elements.

3. The method according to claim 1 or 2, characterized in that: The number of resource element overheads indicated by the target overhead field is the number of resource element overheads for one time slot.

4. The method according to claim 3, characterized in that The number of resource element overheads indicated by the target overhead field varies with the change of time slots.

5. The method according to claim 1 or 2, characterized in that: The target overhead field is a field that occupies n bits, and the number of candidate overhead elements is 2 n , where n is an integer.

6. A method for determining a transport block size, characterized in that: include: In a case where a radio resource control RRC connection has been established between a base station and a user equipment, the user equipment receives an RRC reconfiguration message sent by the base station, the RRC reconfiguration message includes a serving cell configuration information element of a physical shared channel, the serving cell configuration information element includes first overhead information and second overhead information; the first overhead information is related to a signal overhead transmitted on the physical shared channel, and is used to describe a resource allocation strategy between the base station and the user equipment, and the second overhead information indicates a candidate overhead set for a target resource element, and the target resource element is a resource element that cannot be used for data transmission; The user equipment transmits an RRC reconfiguration complete message to the base station; The user equipment receives downlink control information DCI sent by the base station during data scheduling, where the DCI includes a target overhead field, where the target overhead field indicates the number of resource element overheads for this scheduling; The user equipment determines a transport block size based on the target overhead field.

7. The method according to claim 6, characterized in that The candidate cost set includes a plurality of candidate cost elements, each candidate cost element includes a cost value; The number of resource element overheads indicated by the target overhead field corresponds to an overhead value of a candidate overhead element among the multiple candidate overhead elements.

8. The method according to claim 6 or 7, characterized in that: The number of resource element overheads indicated by the target overhead field is the number of resource element overheads for one time slot; the number of resource element overheads indicated by the target overhead field changes with the change of the time slot.

9. A base station, characterized in that: include: A sending module, configured to send an RRC reconfiguration message to a user equipment when a radio resource control RRC connection has been established between the base station and the user equipment, wherein the RRC reconfiguration message includes a serving cell configuration information element of a physical shared channel, and the serving cell configuration information element includes first overhead information and second overhead information; the first overhead information is related to the signal overhead transmitted on the physical shared channel and is used to describe a resource allocation strategy between the base station and the user equipment, and the second overhead information indicates a candidate overhead set for a target resource element, and the target resource element is a resource element that cannot be used for data transmission; A receiving module, configured to receive an RRC reconfiguration completion message transmitted by the user equipment; The sending module is further used to send downlink control information DCI to the user equipment during data scheduling, where the DCI includes a target overhead field, and the target overhead field indicates the number of resource element overheads for this scheduling; The target overhead field is used to determine the transmission block size.

10. A user equipment, characterized in that: include: A receiving module, configured to receive an RRC reconfiguration message sent by the base station when a radio resource control RRC connection has been established between the base station and the user equipment, the RRC reconfiguration message comprising a serving cell configuration information element of a physical shared channel, the serving cell configuration information element comprising first overhead information and second overhead information; the first overhead information is related to the signal overhead transmitted on the physical shared channel, and is used to describe a resource allocation strategy between the base station and the user equipment, and the second overhead information indicates a candidate overhead set for a target resource element, and the target resource element is a resource element that cannot be used for data transmission; A sending module, used for transmitting an RRC reconfiguration completion message to the base station; The receiving module is further configured to receive downlink control information DCI sent by the base station during data scheduling, wherein the DCI includes a target overhead field, and the target overhead field indicates the number of resource element overheads for this scheduling; A processing module is used to determine a transport block size based on the target overhead field.

Images