Configuration method and apparatus, communication device, and readable storage medium

Abstract

The application discloses a configuration method and device, communication equipment and a readable storage medium, and belongs to the wireless technical field. The configuration method in the embodiment of the application comprises the following steps: a terminal receives first configuration information; the first configuration information is used for configuring a plurality of physical uplink shared channels (PUSCHs), the payload size of each PUSCH is different, and each PUSCH is used for reporting information. Therefore, the terminal can adaptively select a suitable PUSCH to report beam information according to the specific situation of an information reporting event, so that resources can be saved to the maximum extent.

Description

Technical Field

[0001] This application belongs to the field of wireless technology, specifically relating to a configuration method, apparatus, communication device, and readable storage medium. Background Technology

[0002] In related technologies, it has been proposed that beam reporting be initiated by the terminal. However, for component carriers (CCs) operating in different frequency bands, high-frequency CCs may frequently trigger beam reporting events, while low-frequency CCs are relatively stable, and usually not many CCs trigger beam reporting events simultaneously. In this situation, since the network cannot know exactly how many CCs are triggering beam reporting events simultaneously, it will adopt a conservative strategy, allocating resources to the Physical Uplink Shared Channel (PUSCH) according to the maximum payload capacity to ensure that even if all CCs trigger beam reporting events simultaneously, the terminal can successfully report the required information. While this configuration ensures communication reliability, it may lead to unnecessary waste of resources. Summary of the Invention

[0003] The purpose of this application is to provide a configuration method, apparatus, communication device, and readable storage medium to solve the problem of resource waste caused by resource configuration methods in related technologies.

[0004] To solve the above-mentioned technical problems, this application is implemented as follows:

[0005] Firstly, a configuration method is provided for use on a terminal, including:

[0006] The terminal receives first configuration information; wherein the first configuration information is used to configure multiple PUSCHs, each PUSCH having a different payload capacity, and each PUSCH is used to report information.

[0007] Secondly, a configuration method is provided for network-side devices, including:

[0008] The network-side device sends first configuration information to the terminal; wherein, the first configuration information is used to configure multiple PUSCHs, each of which can carry a different payload size, and each of which is used to report information.

[0009] Thirdly, a configuration device is provided for use in a terminal, including:

[0010] A first receiving module is used to receive first configuration information; wherein the first configuration information is used to configure multiple PUSCHs, each PUSCH having a different payload capacity, and each PUSCH is used to report information.

[0011] Fourthly, a configuration device is provided for use in network-side equipment, comprising:

[0012] The fourth sending module is used to send first configuration information to the terminal; wherein, the first configuration information is used to configure multiple PUSCHs, each PUSCH having a different payload capacity, and each PUSCH is used to report information.

[0013] Fifthly, a communication device is provided, including a processor, a memory, and a program or instructions stored in the memory and executable on the processor, wherein the program or instructions, when executed by the processor, implement the steps of the method described in the first aspect, or the steps of the method described in the second aspect.

[0014] In a sixth aspect, a readable storage medium is provided, on which a program or instructions are stored, which, when executed by a processor, implement the steps of the method described in the first aspect, or the steps of the method described in the second aspect.

[0015] In a seventh aspect, a computer program product is provided, including computer instructions that, when executed by a processor, implement the steps of the method described in the first aspect, or the steps of the method described in the second aspect.

[0016] In this embodiment, the terminal can receive first configuration information, which is used to configure multiple PUSCHs. Each PUSCH has a different payload capacity and is used to report information. Therefore, by using the first configuration information, the terminal can adaptively select an appropriate PUSCH to report information based on the specific circumstances of the information reporting event, thus avoiding wasted PUSCH resources due to the network's inability to assess the actual payload size, thereby maximizing resource conservation. Attached Figure Description

[0017] Figure 1 This is a flowchart of a configuration method provided in an embodiment of this application;

[0018] Figure 2 This is a schematic diagram illustrating the division of CC groups in an embodiment of this application;

[0019] Figure 3 This is a schematic diagram of the beam report transmission process in Example 1 of this application;

[0020] Figure 4 This is a schematic diagram of the beam report transmission process in Example 2 of this application;

[0021] Figure 5 This is a schematic diagram of the beam report transmission process in Example 3 of this application;

[0022] Figure 6 This is a schematic diagram of the beam report transmission process in Example 4 of this application;

[0023] Figure 7 This is a schematic diagram of the beam report transmission process in Example 5 of this application;

[0024] Figure 8 This is a schematic diagram of the beam report transmission process in Example 6 of this application;

[0025] Figure 9 This is a flowchart of another configuration method provided in an embodiment of this application;

[0026] Figure 10 This is a schematic diagram of the structure of a configuration device provided in an embodiment of this application;

[0027] Figure 11 This is a schematic diagram of another configuration device provided in an embodiment of this application;

[0028] Figure 12 This is a schematic diagram of the structure of a communication device provided in an embodiment of this application. Detailed Implementation

[0029] The technical solutions of the embodiments of this application will be clearly and completely described below with reference to the accompanying drawings. Obviously, the described embodiments are only some embodiments of this application, not all embodiments. 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.

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

[0031] To facilitate understanding of the embodiments of this application, the following will be described first.

[0032] Channel State Information (CSI) Reporting: The CSI feedback reporting framework is an important component of a communication system. It allows terminals such as User Equipment (UE) to report CSI to the base station gNB for effective beam management and channel-dependent scheduling. The CSI feedback process mainly consists of two steps: First, CSI resource configuration, where the gNB sends a Channel State Information Reference Signal (CSI-RS) and / or a Synchronization Signal Block (SSB) to the UE according to the configuration; second, CSI reporting configuration, where the UE measures the CSI-RS and / or SSB and then reports the CSI to the gNB according to the configuration.

[0033] Beam management: Beamforming technology concentrates signal energy into a narrow beam in a specific direction by adjusting the amplitude and phase of the antenna, thereby enhancing coverage and reducing interference. The beam management process mainly includes: First, scanning. The gNB transmits multiple beams in different spatial directions. The UE listens for / scans these beams in different receiving spaces and evaluates the received signal quality of each beam, including metrics such as Reference Signal Received Power (RSRP) and Signal to Interference plus Noise Ratio (SINR). Next, the UE reports this beam quality and decision information to the gNB. The gNB can then adjust the current beam based on the beam measurement results reported by the UE.

[0034] Cross-carrier (CC) Transmission Configuration Indicator (TCI) Update: All CCs within a band have a corresponding Physical Downlink Shared Channel (PDSCH), and each CC indicates one TCI State. If the TCI State needs to be updated on multiple CCs, the Downlink Control Information (DCI) must be called separately to update the TCI State of the corresponding CCs. Alternatively, a Medium Access Control Element (MAC CE) can be used to update the PDSCH TCI State across CCs, or to update the TCI State of a Control Resource Set (CORESET) together. This requires that the CORESETs being updated across CCs have the same ID. Furthermore, different CC IDs can be bound to the same list; if a PDSCH TCI State MAC CE indication is received on a CC in a CC list, the TCI State of all CCs in that CC list will be updated.

[0035] To address the resource waste caused by resource allocation methods in related technologies, this application proposes configuring multiple PUSCHs for reporting information, with each PUSCH capable of carrying a different payload size. This allows the terminal to adaptively select the appropriate PUSCH to report information (such as sending a beam report) based on the specific circumstances of the information reporting event, thus avoiding PUSCH resource waste caused by the network's inability to assess the actual payload size and maximizing resource savings.

[0036] The configuration method, apparatus, communication device, and readable storage medium provided in this application will be described in detail below with reference to the accompanying drawings and through specific embodiments and application scenarios.

[0037] Please see Figure 1 , Figure 1 This is a flowchart of a configuration method provided in an embodiment of this application. This method is applied to a terminal, such as... Figure 1 As shown, the method includes the following steps:

[0038] Step 11: The terminal receives the first configuration information; the first configuration information is used to configure multiple PUSCHs, each PUSCH can carry a different payload size, and each PUSCH is used to report information.

[0039] In this embodiment of the application, the first configuration information can be sent via Radio Resource Control (RRC signaling) or MAC CE, etc.

[0040] The reported information may be beam-related information or beam report information, etc. The reported information may include, but is not limited to, sending a beam report, reporting a beam report, sending measurement results, reporting measurement results, sending a measurement report, and reporting a measurement report.

[0041] For example, the reported information may be at least one of the following: Transmission Configuration Indicator State ID (TCIstate ID), Reference Signal Resource Indicator (CSI-RS Resource Indicator, CRI), Synchronization Signal Block ID (SSB ID), Layer 1 Reference Signal Received Power (L1-RSRP), and Layer 1 Reference Signal to Interference plus Noise Ratio (L1-SINR), etc.

[0042] The payload size that each PUSCH can carry can vary, which could be: the payload size of uplink control information (UCI) that each PUSCH can carry can vary.

[0043] Optionally, the plurality of PUSCHs may include at least two PUSCHs. The plurality of PUSCHs may include a first PUSCH and a second PUSCH, wherein the payload that the first PUSCH can carry is smaller than the payload that the second PUSCH can carry; that is, the first PUSCH can be understood as a PUSCH with a small payload size, and the second PUSCH can be understood as a PUSCH with a large payload size.

[0044] Therefore, by using the first configuration information, the terminal can adaptively select the appropriate PUSCH to report information based on the specific circumstances of the information reporting event, so as to avoid the waste of PUSCH resources due to the network's inability to assess the actual effective payload size, thereby maximizing resource savings.

[0045] For example, in this embodiment, a beam reporting event may include at least one of the following: 1) the quality of the current serving beam (e.g., Layer 1 reference signal received power (L1-RSRP)) is lower than a certain threshold; 2) the quality of at least one new beam is higher than the quality of the current serving beam by a certain threshold; 3) the quality of at least one new beam is higher than the best quality of the Mth (M≥1)th beam in the active TCI state by a certain threshold.

[0046] Optionally, the scenarios applicable to the embodiments of this application include, but are not limited to, scenarios where the terminal initiates (UE-initiated) beam reporting in cross-CC scenarios.

[0047] Optionally, after receiving the first configuration information, the configuration method in this embodiment may further include:

[0048] The terminal selects a target PUSCH from the plurality of PUSCHs based on whether its CC (CC) satisfies the first condition, and then reports information using the target PUSCH. This reported information may be beam-related information or beam report information, etc. The condition that the terminal's CC satisfies the first condition can be any CC of the terminal. This allows for the selection of a suitable PUSCH to send the beam report, maximizing resource conservation.

[0049] The CC satisfying the first condition can be understood as a CC trigger event (such as triggering a beam report event). If the CC satisfies the first condition, the transmission of a beam report can be triggered; at this time, the process for transmitting the beam report can be an existing process, and there are no restrictions on it.

[0050] The CC satisfying the first condition may include, but is not limited to, at least one of the following: 1) the quality of the current serving beam of the CC (e.g., L1-RSRP) is lower than a first threshold; 2) the quality of at least one new beam of the CC is higher than the quality of the current serving beam by a second threshold; 3) the quality of at least one new beam of the CC is higher than the best quality of the first beam by a third threshold, where the first beam is a beam that activates the TCI state, such as the Mth (M≥1)th beam among the beams activating the TCI state. The first threshold, second threshold, and third threshold can be pre-configured or agreed upon by the protocol, and can be set based on actual needs, without limitation.

[0051] For example, assuming the first PUSCH and second PUSCH are configured as described above: If a CC operating at low frequency triggers an event, since the amount of beam content to be reported is small, the first PUSCH (i.e., the PUSCH with a small payload size) can be selected to send the beam report; or, if multiple CCs operating at low or high frequency trigger the same event, since the reporting content of different CCs is the same, only the beam report of any one of the multiple CCs needs to be reported, and the first PUSCH (i.e., the PUSCH with a small payload size) can be selected to send the beam report; or, if multiple CCs operating at low or high frequency trigger different events, since a beam report needs to be reported for each CC, the second PUSCH (i.e., the PUSCH with a large payload size) can be selected to send the beam report.

[0052] Optionally, the beam report may include, but is not limited to: a CC index, and its corresponding CSI-RS Resource Indicator (CRI) / SSB Resource Indicator (SSBRI), and its corresponding L1-RSRP / L1-SINR; wherein the CC index may be indicated in the form of a bitmap.

[0053] In this embodiment, since different CCs trigger events under different circumstances—for example, high-frequency CCs may frequently trigger events, while low-frequency CCs are more stable and usually do not trigger events frequently—multiple CCs of the terminal can be grouped to select the appropriate PUSCH for reporting information based on the event triggering behavior of CCs in different groups. This reported information can be beam-related information or beam report information, etc.

[0054] Optionally, the configuration method in this embodiment may further include:

[0055] The terminal receives second configuration information; wherein the second configuration information is used to divide the terminal's multiple CCs into multiple groups, that is, to group the multiple CCs.

[0056] The terminal selects a target PUSCH from the plurality of PUSCHs based on the condition that each CC in each group meets the first condition, and reports information using the target PUSCH. This reported information may be beam-related information or beam report information, etc. The CC meeting the first condition can be any CC, which can be understood as triggering a beam report event. The CC meeting the first condition may include, but is not limited to, at least one of the following: 1) the quality of the current serving beam of the CC (e.g., L1-RSRP) is lower than a first threshold; 2) the quality of at least one new beam of the CC (e.g., L1-RSRP) is higher than the quality of the current serving beam than a second threshold; 3) the quality of at least one new beam of the CC is higher than the best quality of the Mth (M≥1)th beam in the activated TCI state than a third threshold. The first, second, and third thresholds can be pre-configured or agreed upon by the protocol, and can be set based on actual needs, without limitation.

[0057] By grouping CCs in this way, different PUSCHs can be configured to carry different payload sizes for different groups, which is beneficial for selecting the appropriate PUSCH to report information.

[0058] Optionally, after selecting a target PUSCH, the terminal can send indication information to the network-side device. This indication information instructs the terminal to use the target PUSCH for reporting information, so that the network side knows the PUSCH selected by the terminal for reporting information. For example, if X PUSCHs are configured, the indication information can be selected as follows: bit, that is, through The bit indicates the PUSCH of the information to be reported selected by the terminal.

[0059] For example, the indication information is carried through a first PUCCH, and the first PUCCH is bound to multiple PUSCHs configured for reporting information, so that after the terminal selects a target PUSCH from the multiple PUSCHs, it indicates the selected target PUSCH to the network through the first PUCCH.

[0060] Optionally, the plurality of groups includes at least two groups. The plurality of groups may include a first group and a second group, wherein the first group and the second group can satisfy any of the following:

[0061] (1) The CCs in the first group are low-frequency CCs, and the CCs in the second group are high-frequency CCs;

[0062] (2) The CCs in the first group are CCs in the same CC list, the CCs in the second group are CCs in the same CC list, and the CCs in the first group and the CCs in the second group belong to different CC lists.

[0063] It should be noted that for UE-initiated beam management in cross-CC scenarios, the sensitivity of CCs operating in different frequency bands to events triggered by the terminal varies. For example, CCs operating at high frequencies (i.e., high-frequency CCs) may frequently meet the event triggering requirements, while CCs operating at low frequencies (i.e., low-frequency CCs) are more stable, and usually not many CCs will simultaneously meet the event triggering requirements. Therefore, it is advisable to configure high-frequency and low-frequency CCs into different groups to select and allocate subsequent PUSCHs based on different group types to carry UE-initiated beam reports. By dividing CCs operating in different frequency bands into different groups, the selection of appropriate PUSCHs can be made more flexible.

[0064] For example, such as Figure 2 As shown, for different CCs in the combined frequency band, {CC#0,CC#1,CC#2} are low-frequency CCs, and {CC#3,CC#4,CC#5} are high-frequency CCs. Therefore, {CC#0,CC#1,CC#2} can be configured as low-frequency CC group 1, and {CC#3,CC#4,CC#5} can be configured as high-frequency CC group 2.

[0065] Considering that a maximum of two CC lists can currently be configured, and the CCs included in these two CC lists cannot be duplicated, each CC list represents a list of CCs that can update the TCI state together. The current beam is determined by indicating the TCI state, therefore the current beams in the CC lists are identical. Furthermore, all CCs in a CC list that satisfy the first condition are also very likely to produce the same new beam. Therefore, CC groups can be formed based on the CC lists, for example, placing CCs from one CC list in one group and CCs from another CC list in another group. In this way, CCs in a group are very likely to trigger events simultaneously, thereby triggering the terminal to spontaneously report beams, and CCs in a group may trigger the same event, meaning the reported content is the same, thus reducing reporting resource overhead.

[0066] Optionally, if the plurality of PUSCHs includes a first PUSCH and a second PUSCH, the effective load that the first PUSCH can carry is smaller than the effective load that the second PUSCH can carry, and the plurality of groups includes a first group and a second group, wherein the CCs in the first group are low-frequency CCs and the CCs in the second group are high-frequency CCs, then the selection of a target PUSCH from the plurality of PUSCHs based on the condition that the CCs in each group satisfy the first condition may include at least one of the following:

[0067] (a) When one or more CCs in the first group meet the first condition, the terminal selects the first PUSCH (i.e., the PUSCH with the small payload size) as the target PUSCH.

[0068] (b) When multiple CCs in the first group meet the first condition and the multiple CCs trigger the same event, the terminal selects the first PUSCH (i.e., the PUSCH with the small payload size) as the target PUSCH.

[0069] (c) When multiple CCs in the first group meet the first condition and the multiple CCs trigger different events, the terminal selects the second PUSCH (i.e., the PUSCH with the large payload size) as the target PUSCH.

[0070] (d) When multiple CCs in the second group meet the first condition and the multiple CCs trigger different events, the terminal selects the second PUSCH (i.e., the PUSCH with the large payload size) as the target PUSCH.

[0071] (e) When multiple CCs in the second group meet the first condition and the multiple CCs trigger the same event, the terminal selects the first PUSCH (i.e., the PUSCH with a small payload size) as the target PUSCH.

[0072] (f) When one or more CCs in the first group meet the first condition and one or more CCs in the second group meet the first condition, the terminal selects the second PUSCH (i.e., the PUSCH with the large payload size) as the target PUSCH.

[0073] In (a) to (f) above, the events are specifically information reporting events, such as beam reporting events, i.e., when a beam reporting event is triggered, the terminal initiates a beam report. Thus, by using (a) to (f) above, an appropriate PUSCH can be adaptively selected to report beam-related information, avoiding wasted PUSCH resources due to the network's inability to assess the actual payload size, thereby maximizing resource savings.

[0074] It should be noted that the above embodiment is based on configuring two PUSCHs and dividing CCs into two groups, but this application is not limited to this. For example, three PUSCHs can also be configured, and each of the three PUSCHs can carry a different payload size, and / or CCs can be divided into three groups, four groups, etc. As long as PUSCHs are configured and / or CCs are grouped in a similar manner as described above, they all fall within the protection scope of this application.

[0075] The following examples illustrate the method for selecting the target PUSCH in this application.

[0076] Assuming a UE-initiated beam reporting scenario across CCs, the network configures CC#0, CC#1, and CC#2 (operating at low frequencies) as group 1, and CC#3, CC#4, and CC#5 (operating at high frequencies) as group 2. Each group is bound to the first PUCCH (e.g., PUCCH#0), and two PUSCHs are configured for transmitting beam reports: PUSCH#0 with a smaller payload size and PUSCH#1 with a larger payload size. That is, these two PUSCHs can carry different payload sizes. Then, the following situation exists:

[0077] Example 1: Figure 3 As shown, if CC#0 and / or CC#1 in low-frequency group 1 meet the first condition, and any event is triggered, the terminal can send a 1-bit PUCCH#0 to notify the network to select the PUSCH#0 with the smaller payload size to send the UE-initiated Beam Reporting (UEIBR). In this PUSCH#0, one CSI report is reported for each different CC. The reported content can at least include the CC Index, its corresponding CRI / SSBRI, and its corresponding L1-RSRP / L1-SINR. The CC index can be indicated in the form of a bitmap. For example, when CC#0 meets the condition to trigger UEI, the CC index indicates 100000.

[0078] Example 2: Figure 4As shown, if all CCs in low-frequency group 1 meet the first condition and trigger the same event, the terminal can send a 1-bit PUCCH#0 to notify the network to select the PUSCH#0 with the smaller payload size to send the UEIBR. Since all CCs in a group trigger the same event, that is, the reporting content of different CCs is the same, the terminal can select the PUSCH#0 with the smaller payload size to send the beam report. At this time, the network can select the UEIBR of the event triggered by one of the CCs to report. In this PUSCH#0, only one CSI report is reported. The reported content can at least include the CC Index, its corresponding CRI / SSBRI, and its corresponding L1-RSRP / L1-SINR. The CC index can be indicated in the form of a bitmap. For example, when CC#0, CC#1, and CC#2 simultaneously meet the same condition to trigger UEI, the beam report of CC#2 can be selected to be reported, and the CC index is indicated as 111000.

[0079] Example 3: such as Figure 5 As shown, if all CCs in low-frequency group 1 meet the first condition and trigger different events, the terminal can send a 1-bit PUCCH#0 to notify the network to select a PUSCH#1 with a larger payload size to send the UEIBR corresponding to different events. In this PUSCH#1, a CSI report is reported for each different CC. The reported content can include at least the CC Index, its corresponding CRI / SSBRI, and its corresponding L1-RSRP / L1-SINR. The CC index can be indicated in the form of a bitmap. For example, when CC#1 meets the condition to trigger UEI, the CC index indicates 110000.

[0080] It is worth noting that Examples 1 to 3 above represent cases where the CCs in the low-frequency group meet the first condition. Typically, low-frequency CCs are more stable and less likely to trigger events. Therefore, except for cases where all CCs in the group meet the first condition and trigger different events, a smaller payload-size PUSCH can be configured to send beam reports in the remaining cases.

[0081] Example 4: Figure 6As shown, if at least two of CC#3, CC#4, and CC#5 in high-frequency group 2 meet the first condition and trigger different events, the terminal can send a 1-bit PUCCH#0 to notify the network to select a PUSCH#1 with a larger payload size to send the UEIBR corresponding to the different events. In this PUSCH#1, a CSI report is reported for each different CC. The reported content can include at least the CC Index, its corresponding CRI / SSBRI, and its corresponding L1-RSRP / L1-SINR. The CC index can be indicated in the form of a bitmap. For example, when CC#3 and CC#4 meet the condition to trigger UEI, the CC index indicates 001100.

[0082] Example 5: Figure 7 As shown, if CC#3, CC#4, and CC#5 in high-frequency group 2 all meet the first condition and trigger the same event, the terminal can send a 1-bit PUCCH#0 to notify the network to select the PUSCH#0 with the smaller payload size to send the UEIBR. Since all CCs in a group trigger the same event, that is, the reporting content of different CCs is the same, the terminal can choose the PUSCH#0 with the smaller payload size to send the beam report. At this time, the network can select the UEIBR of the event triggered by one of the CCs for reporting. In this PUSCH#0, only one CSI report is reported. The reported content can at least include the CC Index, its corresponding CRI / SSBRI, and its corresponding L1-RSRP / L1-SINR. The CC index can be indicated in the form of a bitmap. For example, when CC#3, CC#4, and CC#5 simultaneously meet the same condition to trigger UEI, the CC index indicates 000111.

[0083] It is worth noting that Examples 4 and 5 above represent cases where the high-frequency group's CC (Current Compatibility) meets the first condition. Typically, high-frequency CCs are more likely to trigger events, therefore a larger payload size PUSCH can be configured to send beam reports.

[0084] Example 6: Figure 8As shown, if CC#2 in the low-frequency group and CC#3 and CC#5 in the high-frequency group 2 all meet the first condition and trigger any different event, the terminal can send a 1-bit PUCCH#0 to notify the network to select a PUSCH#1 with a larger payload size to send the UEIBR corresponding to the different events. In this PUSCH#1, a CSI report is reported for each different CC. The reported content can at least include the CC Index, its corresponding CRI / SSBRI, and its corresponding L1-RSRP / L1-SINR. The CC index can be indicated in the form of a bitmap. For example, when CC#2, CC#3, CC#4, and CC#5 meet the condition to trigger UEI, the CC index indicates 001111.

[0085] It should be noted that for Examples 1 to 6 above, if the N optimal beams and their corresponding L1 RSRP and CRI / SSBRI are reported when sending beam reports, the corresponding format can be shown in Table 1 below:

[0086] Table 1

[0087]

[0088] Please see Figure 9 , Figure 9 This is a flowchart illustrating a configuration method provided in an embodiment of this application. This method is applied to network-side devices, such as... Figure 9 As shown, the method includes the following steps:

[0089] Step 91: The network-side device sends first configuration information to the terminal; the first configuration information is used to configure multiple PUSCHs, each PUSCH having a different payload capacity, and the PUSCHs are used for reporting information. This reported information may be beam-related information or beam report information, etc.

[0090] Optionally, the first configuration information can be sent via RRC signaling or MAC CE, etc.

[0091] The payload size that each PUSCH can carry can vary, which could be: the payload size that each PUSCH can carry for UCI can vary.

[0092] Optionally, the plurality of PUSCHs may include at least two PUSCHs. The plurality of PUSCHs may include a first PUSCH and a second PUSCH, wherein the payload that the first PUSCH can carry is smaller than the payload that the second PUSCH can carry; that is, the first PUSCH can be understood as a PUSCH with a small payload size, and the second PUSCH can be understood as a PUSCH with a large payload size.

[0093] Therefore, by using the first configuration information, the terminal can adaptively select the appropriate PUSCH to report information based on the specific circumstances of the information reporting event, so as to avoid the waste of PUSCH resources due to the network's inability to assess the actual effective payload size, thereby maximizing resource savings.

[0094] Optionally, after sending the first configuration information, the network-side device can receive indication information sent by the terminal. This indication information instructs the terminal to use the target PUSCH to report information, so that the network side knows the PUSCH selected by the terminal for reporting information. This reporting information can be beam-related information or beam report information, etc. For example, if X PUSCHs are configured, the indication information can be selected as... bit, that is, through The bit indicates the PUSCH of the information to be reported selected by the terminal.

[0095] For example, the indication information is carried through a first PUCCH, and the first PUCCH is bound to multiple PUSCHs configured for reporting information, so that after the terminal selects a target PUSCH from the multiple PUSCHs, it indicates the selected target PUSCH to the network through the first PUCCH.

[0096] Optionally, after sending the first configuration information as described above, the configuration method in this embodiment may further include:

[0097] The network-side device sends second configuration information to the terminal; wherein, the second configuration information is used to divide the terminal's multiple CCs into multiple groups, and the terminal selects a target PUSCH from the multiple PUSCHs according to the condition that the CCs in each group meet a first condition, and sends a beam report using the target PUSCH. The CC meeting the first condition can be selected as triggering a beam report event, such as including but not limited to at least one of the following: 1) the quality of the current serving beam of the CC (e.g., L1-RSRP) is lower than a certain threshold; 2) the quality of at least one new beam of the CC is higher than the quality of the current serving beam than a certain threshold; 3) the quality of at least one new beam of the CC is higher than the best quality of the Mth (M≥1)th beam in the activated TCI state than a certain threshold.

[0098] By grouping CCs in this way, the payload capacity of different PUSCHs can be configured for different groups, which is beneficial for selecting the appropriate PUSCH to send beam reports.

[0099] Optionally, the plurality of groups includes at least two groups. The plurality of groups may include a first group and a second group, wherein the first group and the second group can satisfy any of the following:

[0100] (1) The CCs in the first group are low-frequency CCs, and the CCs in the second group are high-frequency CCs;

[0101] (2) The CCs in the first group are CCs in the same CC list, the CCs in the second group are CCs in the same CC list, and the CCs in the first group and the CCs in the second group belong to different CC lists.

[0102] It should be noted that the configuration method provided in this application embodiment can be executed by a configuration device or a control module within that configuration device for executing the configuration method. This application embodiment uses the execution of the configuration method by a configuration device as an example to illustrate the configuration device provided in this application embodiment.

[0103] Please see Figure 10 , Figure 10 This is a schematic diagram of a configuration device provided in an embodiment of this application. The device is applied to a terminal, such as... Figure 10 As shown, the configuration device 100 includes:

[0104] The first receiving module 101 is used to receive first configuration information; wherein, the first configuration information is used to configure multiple PUSCHs, each PUSCH having a different payload capacity, and each PUSCH is used to report information. This reported information may be beam-related information or beam report information, etc.

[0105] Optionally, the plurality of PUSCHs includes a first PUSCH and a second PUSCH, wherein the first PUSCH can carry a smaller effective load than the second PUSCH.

[0106] Optionally, the configuration device 100 further includes:

[0107] The second receiving module is used to receive second configuration information; wherein the second configuration information is used to divide the multiple component carriers (CCs) of the terminal into multiple groups;

[0108] The first selection module is used to select a target PUSCH from the plurality of PUSCHs based on the condition that the CC in each group satisfies a first condition.

[0109] The first reporting module is used to report information using the target PUSCH.

[0110] Optionally, the CC satisfying the first condition includes at least one of the following:

[0111] The quality of the current serving beam of the CC is lower than or equal to a first threshold.

[0112] The quality of at least one new beam of the CC is higher than the quality of the current serving beam of the CC by a second threshold.

[0113] The quality of at least one new beam of the CC is higher than the optimal quality of the first beam, which is the beam that indicates the TCI state of the active transmission configuration of the CC.

[0114] Optionally, the plurality of groups includes a first group and a second group, wherein the first group and the second group satisfy any one of the following:

[0115] The CCs in the first group are low-frequency CCs, and the CCs in the second group are high-frequency CCs;

[0116] The CCs in the first group are all from the same CC list, and the CCs in the second group are all from the same CC list, but the CCs in the first group and the CCs in the second group belong to different CC lists.

[0117] Optionally, if the plurality of PUSCHs includes a first PUSCH and a second PUSCH, the effective load that the first PUSCH can carry is smaller than the effective load that the second PUSCH can carry, and the plurality of groups includes a first group and a second group, wherein the CC in the first group is a low-frequency CC and the CC in the second group is a high-frequency CC, the selection module is specifically used to perform at least one of the following:

[0118] When one or more CCs in the first group meet the first condition, the first PUSCH is selected as the target PUSCH.

[0119] When multiple CCs in the first group meet the first condition and the multiple CCs trigger the same event, the first PUSCH is selected as the target PUSCH.

[0120] When multiple CCs in the first group meet the first condition and the multiple CCs trigger different events, the second PUSCH is selected as the target PUSCH.

[0121] When multiple CCs in the second group meet the first condition and the multiple CCs trigger different events, the second PUSCH is selected as the target PUSCH;

[0122] When multiple CCs in the second group meet the first condition and the multiple CCs trigger the same event, the first PUSCH is selected as the target PUSCH;

[0123] When one or more CCs in the first group satisfy the first condition, and one or more CCs in the second group satisfy the first condition, the second PUSCH is selected as the target PUSCH.

[0124] Optionally, the configuration device 100 further includes:

[0125] The first sending module is used to send indication information to the network-side device, the indication information being used to instruct the terminal to report information using the target PUSCH.

[0126] Optionally, the configuration device 100 further includes:

[0127] The second selection module is used to select a target PUSCH from the plurality of PUSCHs based on the condition that the CC of the terminal satisfies the first condition.

[0128] The second reporting module is used to report information using the target PUSCH.

[0129] The configuration device 100 of this application embodiment can achieve the above. Figure 1 The various processes of the method embodiments shown can achieve the same technical effect, and will not be described again here to avoid repetition.

[0130] Please see Figure 11 , Figure 11 This is a schematic diagram of a configuration device provided in an embodiment of this application. This device is applied to network-side equipment, such as... Figure 11 As shown, the configuration device 110 includes:

[0131] The second sending module 111 is used to send first configuration information to the terminal; wherein, the first configuration information is used to configure multiple PUSCHs, each PUSCH having a different payload size, and each PUSCH is used to report information.

[0132] Optionally, the plurality of PUSCHs includes a first PUSCH and a second PUSCH, wherein the first PUSCH can carry a smaller effective load than the second PUSCH.

[0133] Optionally, the configuration device 110 further includes:

[0134] The third sending module is used to send second configuration information to the terminal; wherein the second configuration information is used to divide the terminal's multiple CCs into multiple groups, and the terminal selects a target PUSCH from the multiple PUSCHs according to the condition that the CCs in each group meet the first condition, and uses the target PUSCH to report information.

[0135] Optionally, the plurality of groups includes a first group and a second group, wherein the first group and the second group satisfy any one of the following:

[0136] The CCs in the first group are low-frequency CCs, and the CCs in the second group are high-frequency CCs;

[0137] The CCs in the first group are all from the same CC list, and the CCs in the second group are all from the same CC list, but the CCs in the first group and the CCs in the second group belong to different CC lists.

[0138] The configuration device 110 of this application embodiment can achieve the above. Figure 9 The various processes of the method embodiments shown can achieve the same technical effect, and will not be described again here to avoid repetition.

[0139] Optionally, such as Figure 12 As shown, this application embodiment also provides a communication device 120, including a processor 121, a memory 122, and a program or instructions stored in the memory 122 and executable on the processor 121. For example, when the communication device 120 is a terminal, the program or instructions executed by the processor 121 implement the above-mentioned... Figure 1 The various processes of the configuration method embodiments shown can achieve the same technical effect. When the communication device 120 is a network-side device, the program or instructions executed by the processor 121 implement the above-described... Figure 9 The various processes of the configuration method embodiments shown can achieve the same technical effect, and will not be described again here to avoid repetition.

[0140] This application also provides a computer program product, including computer instructions, which, when executed by a processor, can perform the above-described functions. Figure 1 or Figure 9 The various processes of the method embodiments shown can achieve the same technical effect, and will not be described again here to avoid repetition.

[0141] This application also provides a readable storage medium storing a program or instructions. When the program or instructions are executed by a processor, they can implement the various processes of the above configuration method embodiments and achieve the same technical effect. To avoid repetition, they will not be described again here.

[0142] Computer-readable media include both permanent and non-permanent, removable and non-removable media, which can store information using any method or technology. Information can be computer-readable instructions, data structures, modules of programs, or other data. Examples of computer storage media include, but are not limited to, phase-change memory (PRAM), static random access memory (SRAM), dynamic random access memory (DRAM), other types of random access memory (RAM), read-only memory (ROM), electrically erasable programmable read-only memory (EEPROM), flash memory or other memory technologies, CD-ROM, digital versatile optical disc (DVD) or other optical storage, magnetic tape, magnetic disk storage or other magnetic storage devices, or any other non-transferable medium that can be used to store information accessible by a computing device. As defined herein, computer-readable media does not include transient computer-readable media, such as modulated data signals and carrier waves.

[0143] 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. Unless otherwise specified, 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.

[0144] The sequence numbers of the embodiments in this application are for descriptive purposes only and do not represent the superiority or inferiority of the embodiments.

[0145] 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 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 service classification device (which may be a mobile phone, computer, server, air conditioner, or network device, etc.) to execute the methods described in the various embodiments of this application.

[0146] The above description is only a preferred embodiment of this application. It should be noted that for those skilled in the art, several improvements and modifications can be made without departing from the principle of this application, and these improvements and modifications should also be considered within the scope of protection of this application.

Claims

1. A configuration method, characterized in that, include: The terminal receives first configuration information; wherein the first configuration information is used to configure multiple Physical Uplink Shared Channels (PUSCHs), each PUSCH having a different payload capacity, and each PUSCH being used for reporting information.

2. The method according to claim 1, characterized in that, The plurality of PUSCHs includes a first PUSCH and a second PUSCH, wherein the effective load that the first PUSCH can carry is smaller than that that that the second PUSCH can carry.

3. The method according to claim 1 or 2, characterized in that, The method further includes: The terminal receives second configuration information; wherein, the second configuration information is used to divide the terminal's multiple component carriers (CCs) into multiple groups; The terminal selects a target PUSCH from the plurality of PUSCHs based on the condition that the CC in each group meets the first condition, and uses the target PUSCH to report information.

4. The method according to claim 3, characterized in that, The CC satisfies at least one of the following conditions: The quality of the current serving beam of the CC is lower than or equal to a first threshold. The quality of at least one new beam of the CC is higher than the quality of the current serving beam of the CC by a second threshold. The quality of at least one new beam of the CC is higher than the optimal quality of the first beam, which is the beam that indicates the TCI state of the active transmission configuration of the CC.

5. The method according to claim 3, characterized in that, The plurality of groups includes a first group and a second group, wherein the first group and the second group satisfy any one of the following: The CCs in the first group are low-frequency CCs, and the CCs in the second group are high-frequency CCs; The CCs in the first group are all from the same CC list, and the CCs in the second group are all from the same CC list, but the CCs in the first group and the CCs in the second group belong to different CC lists.

6. The method according to claim 3, characterized in that, If the plurality of PUSCHs includes a first PUSCH and a second PUSCH, the effective load that the first PUSCH can carry is smaller than the effective load that the second PUSCH can carry, and the plurality of groups includes a first group and a second group, wherein the CCs in the first group are low-frequency CCs, and the CCs in the second group are high-frequency CCs. The terminal selects a target PUSCH from the plurality of PUSCHs based on the condition that the CC in each group satisfies a first condition, including at least one of the following: When one or more CCs in the first group meet the first condition, the terminal selects the first PUSCH as the target PUSCH. When multiple CCs in the first group meet the first condition and the multiple CCs trigger the same event, the terminal selects the first PUSCH as the target PUSCH. When multiple CCs in the first group meet the first condition and the multiple CCs trigger different events, the terminal selects the second PUSCH as the target PUSCH. When multiple CCs in the second group meet the first condition and the multiple CCs trigger different events, the terminal selects the second PUSCH as the target PUSCH. When multiple CCs in the second group meet the first condition and the multiple CCs trigger the same event, the terminal selects the first PUSCH as the target PUSCH. When one or more CCs in the first group meet the first condition, and one or more CCs in the second group meet the first condition, the terminal selects the second PUSCH as the target PUSCH.

7. The method according to claim 3, characterized in that, The method further includes: The terminal sends an instruction message to the network-side device, the instruction message being used to instruct the terminal to report information using the target PUSCH.

8. The method according to claim 1, characterized in that, The method further includes: The terminal selects a target PUSCH from the plurality of PUSCHs based on the condition that the terminal's CC meets the first condition, and uses the target PUSCH to report information.

9. A configuration method, characterized in that, include: The network-side device sends first configuration information to the terminal; wherein, the first configuration information is used to configure multiple PUSCHs, each of which can carry a different payload size, and each of which is used to report information.

10. The method according to claim 9, characterized in that, The plurality of PUSCHs includes a first PUSCH and a second PUSCH, wherein the effective load that the first PUSCH can carry is smaller than that that that the second PUSCH can carry.

11. The method according to claim 9 or 10, characterized in that, The method further includes: The network-side device sends second configuration information to the terminal; wherein, the second configuration information is used to divide the terminal's multiple CCs into multiple groups, and the terminal selects a target PUSCH from the multiple PUSCHs according to the condition that the CCs in each group meet a first condition, and uses the target PUSCH to report information.

12. The method according to claim 11, characterized in that, The plurality of groups includes a first group and a second group, wherein the first group and the second group satisfy any one of the following: The CCs in the first group are low-frequency CCs, and the CCs in the second group are high-frequency CCs; The CCs in the first group are all from the same CC list, and the CCs in the second group are all from the same CC list, but the CCs in the first group and the CCs in the second group belong to different CC lists.

13. A configuration device, characterized in that, include: A first receiving module is used to receive first configuration information; wherein the first configuration information is used to configure multiple PUSCHs, each PUSCH having a different payload capacity, and each PUSCH is used to report information.

14. A configuration device, characterized in that, include: The fourth sending module is used to send first configuration information to the terminal; wherein, the first configuration information is used to configure multiple PUSCHs, each PUSCH having a different payload capacity, and each PUSCH is used to report information.

15. A communication device, characterized in that, It includes a processor, a memory, and a program or instructions stored in the memory and executable on the processor, wherein the program or instructions, when executed by the processor, implement the steps of the method as claimed in any one of claims 1 to 8, or the steps of the method as claimed in any one of claims 9 to 12.

16. A readable storage medium, characterized in that, The readable storage medium stores a program or instructions that, when executed by a processor, implement the steps of the method as described in any one of claims 1 to 8, or the steps of the method as described in any one of claims 9 to 12.

17. A computer program product, characterized in that, Includes computer instructions that, when executed by a processor, implement the steps of the method as claimed in any one of claims 1 to 8, or the steps of the method as claimed in any one of claims 9 to 12.

Images