Methods for determining transport block size, base stations, and user equipment

Abstract

This application discloses a method, base station, and user equipment for determining transport block size, belonging to the field of communications. The method includes: 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. The RRC reconfiguration message includes first overhead information and second overhead information. The first overhead information describes the resource allocation strategy between the base station and the user equipment, and the second overhead information indicates a set of candidate overheads for a target resource element, where the target resource element is a resource element that cannot be used for data transmission. The base station receives an RRC reconfiguration completion message transmitted by the user equipment. During data scheduling, the base station sends downlink control information (DCI) to the user equipment. The DCI includes a target overhead field, which indicates the number of resource element overheads scheduled in this instance. The target overhead field is used by the user equipment to determine the transport block size. This application is used to determine the transport block size.

Description

Technical Field

[0001] This application belongs to the field of communications, specifically relating to a method for determining the transport block size, a base station, and user equipment. Background Technology

[0002] Many digital communication systems, including 5G, require a series of processes before data transmission, including 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, and resource mapping. The main reasons for rate matching are as follows: 1) Channel coding generates an excessive amount of check bits that could be used for HARQ retransmission; 2) The receiving end, based on scheduling information, confirms the code rate and other information of the upcoming physical layer transport block (TB), thereby determining the transport block size (TB size) for this transmission.

[0003] During the process of determining the transport block size, due to rate matching, the actual number of available resource elements (REs) for transmission may be less than the theoretically calculated REs. This can lead to an inaccurate determined transport block size, which may cause errors in parsing downlink data by the user equipment (UE), reduce transmission reliability, and affect the user's downlink rate and experience. Summary of the Invention

[0004] This application provides a method, base station, and user equipment for determining the transport block size, which can solve the problem of inaccurate transport block size determination in related technologies.

[0005] In a first aspect, embodiments of this application provide a method for determining the transport block size, including:

[0006] When a Radio Resource Control (RRC) connection has been established between a base station and a user equipment (UE), the base station sends an RRC reconfiguration message to the UE. The RRC reconfiguration message contains serving cell configuration information elements for the physical shared channel. The serving cell configuration information elements include 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 the resource allocation strategy between the base station and the UE. The second overhead information indicates a set of candidate overheads for a target resource element, which is a resource element that cannot be used for data transmission.

[0007] The base station receives the RRC reconfiguration complete message transmitted by the user equipment;

[0008] During the data scheduling process, the base station sends downlink control information (DCI) to the user equipment. The DCI includes a target cost field, which indicates the number of resource element costs scheduled in this operation.

[0009] The target overhead field is used to determine the transport block size.

[0010] Secondly, embodiments of this application provide another method for determining the transport block size, including:

[0011] When an RRC connection has been established between a base station and a user equipment (UE), the UE receives an RRC reconfiguration message sent by the base station. The RRC reconfiguration message contains serving cell configuration information elements for the physical shared channel. The serving cell configuration information elements include 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 the resource allocation strategy between the base station and the UE. The second overhead information indicates a set of candidate overheads for a target resource element, where the target resource element is a resource element that cannot be used for data transmission.

[0012] The user equipment transmits an RRC reconfiguration complete message to the base station;

[0013] The user equipment receives a DCI sent by the base station during the data scheduling process. The DCI includes a target cost field, which indicates the number of resource element costs in this scheduling.

[0014] The user equipment determines the transport block size based on the target overhead field.

[0015] Thirdly, a base station is provided, including:

[0016] The sending module is configured to send an RRC reconfiguration message to the user equipment when an RRC connection has been established between the base station and the user equipment. The RRC reconfiguration message contains serving cell configuration information elements of the physical shared channel. The serving cell configuration information elements include 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 the resource allocation strategy between the base station and the user equipment. The second overhead information indicates a set of candidate overheads for a target resource element, where the target resource element is a resource element that cannot be used for data transmission.

[0017] The receiving module is used to receive the RRC reconfiguration complete message transmitted by the user equipment;

[0018] The sending module is also used to send a DCI to the user equipment during the data scheduling process. The DCI includes a target cost field, which indicates the number of resource element costs in this scheduling.

[0019] The target overhead field is used to determine the transport block size.

[0020] Fourthly, a user equipment is provided, comprising:

[0021] The receiving module 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 contains serving cell configuration information elements of the physical shared channel. The serving cell configuration information elements include 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 the resource allocation strategy between the base station and the user equipment. The second overhead information indicates a set of candidate overheads for a target resource element, where the target resource element is a resource element that cannot be used for data transmission.

[0022] The sending module is used to transmit an RRC reconfiguration complete message to the base station;

[0023] The receiving module is further configured to receive the DCI sent by the base station during the data scheduling process, wherein the DCI includes a target overhead field and the target overhead field indicates the number of resource element overheads in this scheduling.

[0024] The processing module is used to determine the transport block size based on the target overhead field.

[0025] The at least one technical solution provided in the embodiments of this application can achieve the following technical effects:

[0026] In this embodiment, the base station sends an RRC reconfiguration message to the user equipment. The RRC reconfiguration message includes second overhead information, which indicates a set of candidate overheads 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, during data scheduling, the base station sends a DCI to the user equipment. The DCI includes a target overhead field, which indicates the number of resource element overheads scheduled this time. The target overhead field is used to determine the transport block size. Thus, 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 (i.e., the accurate number of resource element overheads), and thereby determine the accurate transport block size, solving the problem of inaccurate transport block size determination in related technologies. Attached Figure Description

[0027] To more clearly illustrate the technical solutions of the embodiments of the present invention, the accompanying drawings used in the embodiments will be briefly introduced below. It should be understood that the following drawings only show some embodiments of the present invention and should not be regarded as a limitation on the scope. For those skilled in the art, other related drawings can be obtained based on these drawings without creative effort.

[0028] Figure 1 This is a flowchart illustrating a method for determining the transport block size provided in an embodiment of this application;

[0029] Figure 2 This is a schematic diagram illustrating the process of a UE accessing a base station in an embodiment of this application;

[0030] Figure 3 This is a flowchart of another method for determining the transport block size provided in an embodiment of this application;

[0031] Figure 4 This is a structural block diagram of a base station provided in an embodiment of this application;

[0032] Figure 5 This is a structural block diagram of a user equipment provided in an embodiment of this application. Detailed Implementation

[0033] The technical solutions of the embodiments of this application will be clearly described below with reference to the accompanying drawings. Obviously, the described embodiments are only some, not all, of the embodiments of this application. Based on the embodiments of this application, all other embodiments obtained by those skilled in the art without creative effort are within the scope of protection of this application.

[0034] The terms "first," "second," etc., used in the specification and claims of this application are used to distinguish similar objects and not to describe a specific order or sequence. It should be understood that such use of data can be interchanged where appropriate so that embodiments of this application can be implemented in orders other than those illustrated or described herein, and the objects distinguished by "first," "second," etc., are generally of the same class and the number of objects is not limited; for example, a first object can be one or more. Furthermore, in the specification and claims, "and / or" indicates at least one of the connected objects, and the character " / " generally indicates that the preceding and following objects are in an "or" relationship.

[0035] Therefore, the following detailed description of the embodiments of the invention provided in the accompanying drawings is not intended to limit the scope of the claimed invention, but merely to illustrate selected embodiments of the invention. All other embodiments obtained by those skilled in the art based on the embodiments of the invention without inventive effort are within the scope of protection of the invention.

[0036] In this embodiment, the receiving end can determine the code rate, modulation and coding scheme (MCS), transmission layer number, and physical resource allocation of the upcoming physical layer transport block (TB) based on scheduling information, thereby determining the transport block size (TB Size) for this transmission. Before confirming the transport block size, the sending end first determines the number of available resource elements (REs) for each physical resource block (PRB) in the scheduled slot. The specific calculation formula is as follows:

[0037] Formula (1)

[0038] Formula (2)

[0039] in, The number of subcarriers per physical resource block (PRB) It refers to the number of Orthogonal Frequency Division Multiplexing (OFDM) symbols allocated in each time slot for transmitting service data. It is the number of demodulation reference signals (DM-RS) that are not used for data transmission in each PRB within a scheduling period (e.g., a time slot). It is an additional overhead parameter (xOverhead) configured by higher layers in the serving cell configuration cell (PDSCH-ServingCellConfig / PUSCH-ServingCellConfig cell) of the Physical Shared Channel. This is the number of PRBs allocated to the receiving end.

[0040] In actual transmission, there may be more REs that cannot be used to transmit service data within the scheduled time slots. These REs include Phase Track Reference Signal (PT-RS), Non-Zero-Power / Zero-Power Channel Status Information Reference Signal (NZP / ZP CSI-RS), and other resources configured by higher layers that are not used for service data transmission.

[0041] The above situation may result in the number of available bits for each transmission being less than the number of encoded bits, which is determined by the actual number of resources. Therefore, it is necessary to remove untransmittable bits before transmission to match the actual resources. This is what rate matching does.

[0042] In this embodiment, the size of the physical layer transport block to be received is determined by formulas (1) and (2) in conjunction with the following formula (3) based on the scheduling information at the receiving UE side:

[0043] Formula (3)

[0044] in, It is the transport block size, that is, the number of information bits transmitted. For bitrate, The modulation order (MCS) is used. This refers to the number of transmission layers, such as the number of Multiple-Input Multiple-Output (MIMO) layers.

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

[0046] The embodiments of this application can accurately calculate the transport block size, ensuring that the current transport block size and the code rate corresponding to the scheduling resources can match the channel conditions, without increasing additional system overhead, thereby improving transmission reliability and enhancing user speed and experience. The following is in conjunction with... Figure 1 To elaborate.

[0047] Figure 1 This is a flowchart illustrating a method for determining the transport block size provided in an embodiment of this application. (Refer to...) Figure 1 The method for determining the transport block size provided in this application embodiment may include:

[0048] Step 110: If 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. The RRC reconfiguration message contains serving cell configuration information elements for the physical shared channel. The serving cell configuration information elements include 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 the resource allocation strategy between the base station and the user equipment. The second overhead information indicates a set of candidate overheads for a target resource element, where the target resource element is a resource element that cannot be used for data transmission.

[0049] In this embodiment of the application, the process of UE accessing the base station can be referred to Figure 2 .like Figure 2 As shown, firstly, the UE establishes an RRC connection with the base station. The specific process of establishing an RRC connection includes: the UE sending an RRC connection establishment request to the base station; the base station establishing an RRC connection with the UE based on the request; and then, the UE sending an RRC connection establishment completion message to the base station. After the RRC connection is established, the base station can perform the UE capability information query and security activation process. Specifically, the base station queries the UE's capability information by sending a UECapabilityEnquiry command. Upon receiving the command, the UE reports its own capability information (UECapabilityInformation) according to the command. UE capability information includes network capabilities and radio capabilities. Network capabilities involve interaction with the core network, while radio capabilities involve querying radio capabilities. The Security Mode Command (SMC) is part of 5G authentication and security, and can ensure the correct configuration of the security mode through the SMC. Through these steps, the base station can accurately understand the UE's capabilities and perform correct scheduling and configuration based on those capabilities, while ensuring security during communication.

[0050] After the RRC connection is established and the UE capability information query and security activation process is completed, the base station can send an RRC reconfiguration message to the user equipment.

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

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

[0053] Among these configuration items, xOverhead is an important parameter, typically used to specify information about the "additional overhead" or "additional 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 uplink and downlink scheduling latency. xOverhead is primarily related to the overhead of PDSCH (Physical Downlink Shared Channel) and PUSCH (Physical Uplink Shared Channel) signal transmission.

[0054] xOverhead is typically an integer value that specifies the level 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 adjustments to uplink and downlink resources based on load and scheduling requests.

[0055] xOverhead can contain the following:

[0056] Uplink and downlink scheduling overhead: The xOverhead configuration item dynamically adjusts based on system load and scheduling needs, affecting uplink (PUSCH) and downlink (PDSCH) scheduling.

[0057] 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.

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

[0059] In this embodiment, the second overhead information can be newly added information in the ServingCellConfig information element. When the second overhead information is an overhead list field (xOver-headList), the overhead list field (xOver-headList) can be a newly added field in the ServingCellConfig information element. The overhead list field can be an enumeration value or a data set containing specific numerical values. This will be explained in detail below.

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

[0061] In the second cost information (e.g., xOver-headList), each candidate cost element contains a cost (overhead) value. For example, the second cost information (e.g., xOver-headList) contains the maximum number of candidate cost elements (e.g., 16 elements), each containing a specific data value. Taking 16 elements as an example, the second overhead information (e.g., xOver-headList) contains the following 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 { overhead 15}, element 16 { overhead 16}.

[0062] 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 send an RRC reconfiguration completion message back to the base station, informing the base station that it has correctly received the RRC reconfiguration message.

[0063] Step 120: The base station receives the RRC reconfiguration complete message transmitted by the user equipment;

[0064] Step 130: During the data scheduling process, the base station sends a DCI to the user equipment. The DCI includes a target cost field, which indicates the number of resource element costs in this scheduling.

[0065] The target overhead field can 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 for determining the transport block size can be referred to formula (3) mentioned above.

[0066] During data scheduling, 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 for the target overhead field is as follows;

[0067]

[0068] In this embodiment, the target overhead field in the DCI is a field occupying n bits, and the number of candidate overhead elements is 2. n Where n is an integer. The table above uses 4 bits as an example, and 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 (or the last) of the candidate overhead set, i.e., element 1 { overhead 1} (or element 16 { overhead 16}).

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

[0070] As can be seen from the above, when a UE accesses the network, the base station configures the second overhead information (e.g., xOver-headList) to the UE via signaling. During dynamic scheduling, when there are REs in the scheduled time slot that are occupied by other channels, the base station notifies the UE of the exact number of RE overheads through the target overhead field of the DCI (e.g., the xOverHead field). Then, the UE can use the formula for available REs of the data channel and the formula for the transport block size to accurately calculate the transport block size scheduled for this time slot.

[0071] In this embodiment, the base station sends an RRC reconfiguration message to the user equipment. The RRC reconfiguration message includes second overhead information, which indicates a set of candidate overheads 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, during data scheduling, the base station sends a DCI to the user equipment. The DCI includes a target overhead field, which indicates the number of resource element overheads scheduled this time. The target overhead field is used to determine the transport block size. Thus, 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 (i.e., the accurate number of resource element overheads), and thereby determine the accurate transport block size, solving the problem of inaccurate transport block size determination in related technologies.

[0072] In another embodiment of this application, the number of resource element overheads indicated by the target overhead field is the number of resource element overheads for a single time slot. Thus, the method for determining the transport block size provided in this application can achieve accurate time slot-level transport block calculation.

[0073] In this embodiment, the number of resource element overheads indicated by the target overhead field can change with the time slot. This allows for real-time dynamic adjustment of the number of resource element overheads, ensuring the accuracy of transport blocks at the time slot level.

[0074] Moreover, by notifying the UE of the exact number of RE overheads via DCI, real-time dynamic adjustments can be made without additional system overhead. This solves the problems of inaccuracy caused by using general values ​​configured with higher-level signaling and excessive system overhead caused by using MCS adjustments.

[0075] In this embodiment, on the one hand, a second overhead information (e.g., xOver-HeadList) is added to the RRC signaling configuration, which can notify the terminal of the candidate RE overhead set; on the other hand, a target overhead field (e.g., xOverHead) is added to the DCI scheduling indicator, indicating the number of RE overheads, which can indicate that the RE overhead scheduled this time corresponds to a specific value in the candidate overhead set configured by the RRC signaling. Thus, the UE can identify the target overhead field in the DCI through the second overhead information, and can accurately determine the transport block size based on the target overhead field.

[0076] Figure 3 This is a flowchart illustrating a method for determining the transport block size provided in an embodiment of this application. (Refer to...) Figure 3 The method for determining the transport block size provided in this application embodiment may include:

[0077] Step 310: If an RRC connection has been established between the base station and the user equipment, the user equipment receives an RRC reconfiguration message sent by the base station. The RRC reconfiguration message contains serving cell configuration information elements for the physical shared channel. The serving cell configuration information elements include 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 the resource allocation strategy between the base station and the user equipment. The second overhead information indicates a set of candidate overheads for a target resource element, where the target resource element is a resource element that cannot be used for data transmission.

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

[0079] Step 320: The user equipment transmits an RRC reconfiguration complete message to the base station;

[0080] Step 330: The user equipment receives the DCI sent by the base station during the data scheduling process. The DCI includes a target cost field, which indicates the number of resource element costs in this scheduling.

[0081] Step 340: The user equipment determines the transport block size based on the target overhead field.

[0082] The specific process by which the user equipment determines the transport block size based on the target overhead field in step 340 can be referred to formulas (1) to (3) above.

[0083] In this embodiment, the user equipment receives an RRC reconfiguration message sent by the base station. The RRC reconfiguration message includes second overhead information, which 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, which indicates the number of resource element overheads scheduled this time. The target overhead field is used to determine the transport block size. Thus, 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 (i.e., the accurate number of resource element overheads), and thereby determine the accurate transport block size, solving the problem of inaccurate transport block size determination in related technologies.

[0084] In another embodiment of this application, the number of resource element overheads indicated by the target overhead field is the number of resource element overheads for a single time slot. Thus, the method for determining transport block size provided in this application can achieve accurate time slot-level transport block calculation. In this embodiment, the number of resource element overheads indicated by the target overhead field can change with the time slot. This allows for real-time dynamic adjustment of the number of resource element overheads, ensuring the accuracy of transport blocks at the time slot level.

[0085] Moreover, by notifying the UE of the exact number of RE overheads via DCI, real-time dynamic adjustments can be made without additional system overhead. This solves the problems of inaccuracy caused by using general values ​​configured with higher-level signaling and excessive system overhead caused by using MCS adjustments.

[0086] In this embodiment, on the one hand, a second overhead information (e.g., xOver-HeadList) is added to the RRC signaling configuration, which can notify the terminal of the candidate RE overhead set; on the other hand, a target overhead field (e.g., xOverHead) is added to the DCI scheduling indicator, indicating the number of RE overheads, which can indicate that the RE overhead scheduled this time corresponds to a specific value in the candidate overhead set configured by the RRC signaling. Thus, the UE can identify the target overhead field in the DCI through the second overhead information, and can accurately determine the transport block size based on the target overhead field.

[0087] It is important to understand that Figure 3 The relevant details of each step in the illustrated embodiment can be found in the preceding discussion, for example, referring to the preceding discussion of... Figure 1 and Figure 2 The discussion continues. In other words, the relevant content of the various embodiments of this application can be referred to in turn, and will not be repeated here.

[0088] Figure 4 This is a structural block diagram of a base station provided in an embodiment of this application. (Refer to...) Figure 4 The base station 400 provided in this application embodiment includes: a transmitting module 410 and a receiving module 420. Wherein:

[0089] The sending module 410 is configured to send an RRC reconfiguration message to the user equipment when an RRC connection has been established between the base station and the user equipment. The RRC reconfiguration message includes a serving cell configuration information element for the physical shared channel. 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 the resource allocation strategy between the base station and the user equipment. The second overhead information indicates a set of candidate overheads for a target resource element, where the target resource element is a resource element that cannot be used for data transmission.

[0090] The receiving module 420 is used to receive the RRC reconfiguration complete message transmitted by the user equipment;

[0091] The sending module 410 is also used to send a DCI to the user equipment during the data scheduling process. The DCI includes a target cost field, which indicates the number of resource element costs in this scheduling.

[0092] The target overhead field is used by the user equipment to determine the transport block size.

[0093] In the base station provided in this application embodiment, the base station sends an RRC reconfiguration message to the user equipment. The RRC reconfiguration message includes second overhead information, which 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 base station sends a DCI to the user equipment during data scheduling. The DCI includes a target overhead field, which indicates the number of resource element overheads scheduled this time. The target overhead field is used to determine the transport block size. Thus, 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 (i.e., the accurate number of resource element overheads), and thereby determine the accurate transport block size, solving the problem of inaccurate transport block size determination in related technologies.

[0094] In this embodiment of the application, the candidate cost set includes multiple candidate cost elements, each of which contains a cost value; the number of resource element costs indicated by the target cost field corresponds to the cost value of one of the multiple candidate cost elements.

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

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

[0097] Furthermore, in this embodiment, the target overhead field is a field occupying n bits, and the number of candidate overhead elements is 2. n , where n is an integer.

[0098] The base station provided in this application embodiment can achieve... Figure 1 The various processes in the method embodiments shown are described in the method embodiments. For related content, please refer to the method embodiments. To avoid repetition, they will not be described again here.

[0099] Figure 5 This is a structural block diagram of a user equipment provided in an embodiment of this application. (Refer to...) Figure 5 The user equipment 500 provided in this application embodiment includes: a receiving module 510, a transmitting module 520, and a processing module 530. Wherein:

[0100] 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 includes a serving cell configuration information element for the physical shared channel. 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 the 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, where the target resource element is a resource element that cannot be used for data transmission.

[0101] The sending module 520 is used to transmit an RRC reconfiguration complete message to the base station;

[0102] The receiving module 510 is further configured to receive the DCI sent by the base station during the data scheduling process, wherein the DCI includes a target overhead field and the target overhead field indicates the number of resource element overheads in this scheduling.

[0103] Processing module 530 is used to determine the transport block size based on the target overhead field.

[0104] In the user equipment provided in this application embodiment, an RRC reconfiguration message sent by the base station is received. This RRC reconfiguration message includes second overhead information, which 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, a DCI sent by the base station during data scheduling is received. The DCI includes a target overhead field, which indicates the number of resource element overheads scheduled this time. The target overhead field is used to determine the transport block size. Thus, 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 (i.e., the accurate number of resource element overheads), and thereby determine the accurate transport block size, solving the problem of inaccurate transport block size determination in related technologies.

[0105] In this embodiment of the application, the candidate cost set includes multiple candidate cost elements, and each candidate cost element contains a cost value;

[0106] The number of resource element overheads indicated by the target overhead field corresponds to the overhead value of one of the plurality of candidate overhead elements.

[0107] In this embodiment of the 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 time slot.

[0108] The user equipment provided in this application embodiment can achieve... Figure 3 The various processes in the method embodiments shown are described in the method embodiments. For related content, please refer to the method embodiments. To avoid repetition, they will not be described again here.

[0109] This application also provides a readable storage medium storing a program or instructions that, when executed by a processor, implement the steps of various embodiments of the method for determining the transport block size and achieve the same technical effect. To avoid repetition, these steps will not be repeated here.

[0110] The readable storage medium includes computer-readable storage media, such as computer read-only memory (ROM), random access memory (RAM), magnetic disk, or optical disk.

[0111] This application embodiment also provides a chip, which includes a processor and a communication interface. The communication interface is coupled to the processor. The processor is used to run programs or instructions to implement the various processes of the above method embodiments and achieve the same technical effect. To avoid repetition, it will not be described again here.

[0112] This application provides a computer program product, which is stored in a storage medium and executed by at least one processor to implement the various processes of the above method embodiments and achieve the same technical effects. To avoid repetition, it will not be described again here.

[0113] It should be noted that, in this document, the terms "comprising," "including," or any other variations thereof are intended to cover non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements includes not only those elements but also other elements not expressly listed, or elements inherent to such a process, method, article, or apparatus. Without further limitations, an element defined by the phrase "comprising one..." does not exclude the presence of other identical elements in the process, method, article, or apparatus that includes that element. Furthermore, it should be noted that the scope of the methods and apparatuses in the embodiments of this application is not limited to performing functions in the order shown or discussed, but may also include performing functions substantially simultaneously or in the reverse order, depending on the functions involved. For example, the described methods may be performed in a different order than described, and various steps may be added, omitted, or combined. Additionally, features described with reference to certain examples may be combined in other examples.

[0114] Through the above description of the embodiments, those skilled in the art can clearly understand that the methods of the above embodiments can be implemented by means of software plus necessary general-purpose hardware platforms. Of course, they can also be implemented by hardware, but in many cases the former is a better implementation method. Based on this understanding, the technical solution of this application, in essence, or the part that contributes to the prior art, can be embodied in the form of a computer software product. This computer software product is stored in a storage medium (such as ROM / RAM, magnetic disk, optical disk) and includes several instructions to cause a terminal (which may be a mobile phone, computer, server, or network device, etc.) to execute the methods described in the various embodiments of this application.

[0115] The embodiments of this application have been described above with reference to the accompanying drawings. However, this application is not limited to the specific embodiments described above. The specific embodiments described above are merely illustrative and not restrictive. Those skilled in the art can make many other forms under the guidance of this application without departing from the spirit and scope of the claims, and all of these forms are within the protection scope of this application.

Claims

1. A method for determining the transport block size, characterized in that, include: When a Radio Resource Control (RRC) connection has been established between a base station and a user equipment (UE), the base station sends an RRC reconfiguration message to the UE. The RRC reconfiguration message contains serving cell configuration information elements for the Physical Shared Channel (PSC). The serving cell configuration information elements include first overhead information and second overhead information. The first overhead information is related to the signal overhead transmitted on the PSC and is used to describe the resource allocation strategy between the base station and the UE. The second overhead information indicates a set of candidate overheads for a target resource element, which is a resource element that cannot be used for data transmission. The base station receives the RRC reconfiguration complete message transmitted by the user equipment; During the data scheduling process, the base station sends downlink control information (DCI) to the user equipment. The DCI includes a target cost field, which indicates the number of resource element costs scheduled in this operation. The target overhead field is used to determine the transport block size.

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

3. The method according to claim 1 or 2, characterized in that, The target overhead field indicates the number of resource element overheads for a single 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 time slot.

5. The method according to claim 2, characterized in that, The target cost field is an n-bit field, and the number of candidate cost elements is 2. n , where n is an integer.

6. A method for determining the transport block size, characterized in that, include: When a Radio Resource Control (RRC) connection has been established between a base station and a user equipment (UE), the UE receives an RRC reconfiguration message sent by the base station. The RRC reconfiguration message contains serving cell configuration information elements for the Physical Shared Channel (PSC). The serving cell configuration information elements include first overhead information and second overhead information. The first overhead information is related to the signal overhead transmitted on the PSC and is used to describe the resource allocation strategy between the base station and the UE. The second overhead information indicates a set of candidate overheads for a target resource element, where 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. The DCI includes a target cost field, which indicates the number of resource element costs scheduled in this operation. The user equipment determines the transport block size based on the target overhead field.

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

8. The method according to claim 6 or 7, characterized in that, The target cost field indicates the number of resource element costs for a single time slot; the number of resource element costs indicated by the target cost field changes as the time slot changes.

9. A base station, characterized in that, include: The transmitting module is configured to send an RRC reconfiguration message to the user equipment when a Radio Resource Control (RRC) connection has been established between the base station and the user equipment. The RRC reconfiguration message includes a serving cell configuration element for a physical shared channel. The serving cell configuration 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 the resource allocation strategy between the base station and the user equipment. The second overhead information indicates a set of candidate overheads for a target resource element, where the target resource element is a resource element that cannot be used for data transmission. The receiving module is used to receive the RRC reconfiguration complete message transmitted by the user equipment; The sending module is also used to send downlink control information (DCI) to the user equipment during the data scheduling process. The DCI includes a target cost field, which indicates the number of resource element costs in this scheduling. The target overhead field is used to determine the transport block size.

10. A user equipment, characterized in that, include: The receiving module is 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 contains serving cell configuration information elements for a physical shared channel. The serving cell configuration information elements include 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 the resource allocation strategy between the base station and the user equipment. The second overhead information indicates a set of candidate overheads for a target resource element, where the target resource element is a resource element that cannot be used for data transmission. The sending module is used to transmit an RRC reconfiguration complete 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 cost field and the target cost field indicates the number of resource element costs in this scheduling. The processing module is used to determine the transport block size based on the target overhead field.

Images