Communication method and application device

CN122553952APending Publication Date: 2026-08-11HUAWEI TECH CO LTD
View PDF 0 Cites 0 Cited by

Patent Information

Authority / Receiving Office
CN · China
Patent Type
Applications(China)
Current Assignee / Owner
Filing Date
2025-02-08
Publication Date
2026-08-11

AI Technical Summary

Technical Problem

[0004]在物理上行共享信道(physical uplink shared channel,PUSCH)上使用OCC做上行传输时,如果该PUSCH占用的时频资源与物理上行控制信道(physical uplink controlchannel,PUCCH)占用的时域资源有重叠,且PUCCH上承载的信息占用的资源较大,极有可能导致网络侧无法正确接收上行数据,进而导致网络侧无法正确接收上行数据,进而导致解码失败

Benefits of technology

[0087]第十三方面,本申请提供了一种芯片系统,包括至少一个处理器和通信接口,通信接口和至少一个处理器通过线路互联,至少一个处理器用于运行计算机程序或指令,以执行上述任一方面或可能的示例中的方法。

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN122553952A_ABST
    Figure CN122553952A_ABST
Patent Text Reader

Abstract

The embodiment of the application provides a communication method and an application device, which can be applied to the field of satellite communication, such as NTN. The method comprises the following steps: CSI reports can be multiplexed on a PUSCH for transmission, and the multiplexed PUSCH is expanded through an OCC sequence, so that the CSI reports to be sent on the terminal side can be avoided to be discarded. Moreover, the resource size occupied by the CSI reports is scaled through a first parameter and then multiplexed on the PUSCH, and in the case that the first parameter of the CSI report is less than 1, the resource size occupied by the CSI reports on the PUSCH can be reduced, the influence of the data transmission to be sent originally borne on the PUSCH occupied by the CSI reports can be reduced, and the network side is facilitated to correctly receive information and data.
Need to check novelty before this filing date? Find Prior Art

Description

Technical Field

[0001] This application relates to the field of communication technology, and in particular to a communication method and application device. Background Technology

[0002] Network equipment (such as satellites) in non-terrestrial networks (NTNs) operates at much higher altitudes than network equipment (such as base stations) in terrestrial networks. Therefore, network equipment in NTNs needs to cover a much larger land area and serve a large number of terminal devices, requiring the use of coverage enhancement technologies in uplink communication scenarios.

[0003] However, the essence of coverage enhancement technology is to reuse time-frequency resources to transmit information from terminal devices, resulting in the consumption of more resources, increased information transmission time, and reduced system capacity and throughput of each terminal device. To reduce resource consumption, those skilled in the art can use orthogonal cover codes (OCC) to enhance system capacity and improve the transmission rate of terminal devices.

[0004] When using OCC for uplink transmission on the physical uplink shared channel (PUSCH), if the time-frequency resources occupied by the PUSCH overlap with the time-domain resources occupied by the physical uplink control channel (PUCCH), and the information carried on the PUCCH occupies a large amount of resources, it is highly likely that the network side will not be able to receive the uplink data correctly, which will lead to decoding failure. Summary of the Invention

[0005] This application discloses a communication method and application apparatus that can reduce the amount of resources occupied by UCI on the PUSCH. By transmitting information extended with an OCC sequence, system capacity can be improved, which is beneficial for the network side to receive data correctly.

[0006] Firstly, this application discloses a communication method. This method can be applied to a first communication device, which can be a terminal as a finished product, a component or module with terminal functions, a circuit or chip (such as a modem chip, also known as a baseband chip, or a system-on-a-chip (SoC) chip containing a modem core, or a system-in-package (SIP) chip), chip system, or processor) capable of performing communication functions within the terminal. Alternatively, it can be a logical node, logical module, or software capable of implementing all or part of the terminal functions. The method includes:

[0007] The first parameter of the Channel State Information (CSI) report is determined; this first parameter is used to scale the resource size occupied by the CSI report. After scaling the resource size occupied by the CSI report using the first parameter, it is multiplexed onto the first Physical Uplink Shared Channel (PUSCH). The multiplexed first PUSCH is then extended with an Orthogonal Cover Code (OCC) sequence, which is associated with the first PUSCH. This prevents the CSI reports to be transmitted by the terminal from being discarded. Furthermore, by scaling the resource size occupied by the CSI report and multiplexing it onto the PUSCH, when the first parameter of the CSI report is less than 1, the resource size occupied by the CSI report can be reduced, thus minimizing the impact on the data transmission originally carried on the PUSCH occupied by the CSI report. By transmitting information and data extended with the OCC sequence, system capacity can be improved, facilitating the network side's correct reception of information and data.

[0008] Secondly, this application discloses a communication method that can be applied to a second communication device. The second communication device can be a network device as a final product, a component or module with network device functions, or a communication chip (e.g., a processor, baseband chip, or chip system) that can be used in a network device. The method includes:

[0009] The first parameter of the Channel State Information (CSI) report is determined; wherein the first parameter is less than or equal to 1, and the first parameter of the CSI report is used to scale the resource size occupied by the CSI report; a first Physical Uplink Shared Channel (PUSCH) is transmitted, and the first PUSCH is multiplexed by the CSI report whose resource size has been scaled by the first parameter, and the multiplexed first PUSCH is extended by an Orthogonal Cover Code (OCC) sequence, which is associated with the first PUSCH. This avoids the discarding of CSI reports to be sent by the terminal. Furthermore, the resource size occupied by the CSI report, after being scaled by the first parameter and multiplexed onto the PUSCH, reduces the resource size occupied by the CSI report on the PUSCH when the first parameter of the CSI report is less than 1, thus reducing the impact on the data transmission originally carried on the PUSCH occupied by the CSI report, and facilitating the network side's correct reception of information and data.

[0010] In this application, the CSI report can be any CSI. The CSI report can be a CSI part 1 report, a CSI part 2 report, etc., and is not limited thereto. From the perspective of scheduling methods, the CSI report can be a periodic CSI report, a semi-persistent CSI report (or a semi-static CSI report), or an aperiodic CSI report. Parameters in the CSI report can include channel quality indicator (CQI), precoding matrix indicator (PMI), CSI reference signal resource indicator (CRI), layer indicator (LI), rank indicator (RI), etc., and are not limited thereto.

[0011] This application does not limit the type of OCC sequence; it can be a Walsh sequence, a Discrete Fourier Transform (DFT) sequence, or other sequences, such as sequence A, sequence B, ZC sequence, etc. In this application, the code length L of the OCC sequence refers to the number of values ​​in the OCC sequence. The values ​​in the OCC sequence can be called OCC elements, and the code length can be called the spreading factor or spreading frequency factor, or simply the OCC sequence length. Spreading is also called block spreading (or block-like spreading), and when spread in the frequency domain, it can also be called spread spectrum. This application does not limit the size of the code length; for example, 2, 4, 8, etc.

[0012] In this application, the use of OCC can be described as using an OCC sequence, or as performing OCC extension, or as performing code division extension or code division multiplexing, or even as performing OCC extension and repetition. The information to be transmitted by different terminal devices is multiplied by different OCC elements in their configured OCC sequences. That is, multiplying the information to be transmitted by each terminal device by different OCC elements in its configured OCC sequence can achieve code division multiplexing or OCC extension. PUSCH undergoing OCC sequence extension can actually be the information carried on the PUSCH undergoing OCC sequence extension, for example, multiplying the information carried on the PUSCH by the OCC element corresponding to the time unit occupied by that information in the OCC sequence.

[0013] In this paper, it is sometimes described as code division multiplexing or OCC extension of resources based on OCC sequences, or it can be described as code division multiplexing or OCC extension of resources based on OCC sequences. In reality, it refers to code division multiplexing or OCC extension of information transmitted on resources based on OCC sequences. Code division multiplexing or OCC extension of information based on OCC sequences means multiplying the information by different elements in the OCC sequence. Specifically, the OCC elements corresponding to resource units in the OCC sequence can be determined first, and the information carried on each resource unit can be multiplied by the corresponding OCC element. These resource units can be resource units obtained by extending the resource units occupied by the information according to the OCC code length, where the extended resource units are integer multiples of the OCC code length, or multiple resource units occupied by the information can be used as the resource units required for extension.

[0014] In this application, information may include data and / or signaling. A resource unit, also known as a time-frequency unit, can be a resource element (RE) or a time unit corresponding to a time-domain resource unit, such as a time slot, a symbol, or a group of symbols.

[0015] OCCs can be categorized by resource unit into inter-slot OCCs, inter-symbol OCCs, inter-symbol OCCs, and intra-symbol OCCs. OCCs can also be categorized by repetition type into inter-repetition OCCs of PUSCH repetition type A and inter-repetition OCCs of PUSCH repetition type B, etc. The resource unit (or time-domain resource unit or time unit) of inter-slot OCCs, inter-repetition OCCs of PUSCH repetition type A, and inter-repetition OCCs of PUSCH repetition type B can be a time slot. The resource unit of inter-symbol OCCs can be a symbol, the resource unit of inter-symbol OCCs can be a symbol group (multiple symbols), and the resource unit of intra-symbol OCCs can be a RE. In this application, the OCC element corresponding to a resource unit refers to the OCC element multiplied when the information carried on that resource unit is used for OCC extension. That is, inter-slot OCC extension multiplies the information carried on each of the multiple time slots by the OCC element corresponding to that time slot. Inter-symbol OCC extension multiplies the information carried by each symbol in a set of symbols by the corresponding OCC element. Inter-symbol group OCC extension multiplies the information carried by each symbol group in a set of symbols by the corresponding OCC element. Intra-symbol OCC extension multiplies the information carried by each RE in a set of REs by the corresponding OCC element.

[0016] In this application, the resource size can be the number of resource units occupied by the CSI report, the number of bits occupied by the CSI report, or the sequence length output after rate matching of the CSI report. Alternatively, the resource size can be the resource size occupied by PUCCH or uplink control information (UCI), such as the total number of resource units occupied by PUCCH or UCI, the total number of bits occupied by UCI, or the sequence length output after rate matching of UCI. Alternatively, the resource size can be the resource size occupied by information in UCI other than the CSI report, such as the number of resource units occupied by hybrid automatic repeat request acknowledgment (HARQ-ACK) information, the number of bits occupied by HARQ-ACK information, or the sequence length output after rate matching of HARQ-ACK information. Alternatively, it can be the sum of the resource sizes occupied by the above information and cyclic redundancy check (CRC), etc., where resource units can be symbols or REs, etc., and are not limited here.

[0017] In this application, the first PUSCH can be a PUSCH to be transmitted on time-domain resources that overlap with the time-domain resources occupied by the PUCCH, or it can be the PUSCH currently to be transmitted, etc., without limitation. The PUCCH is used to carry UCI, which may include CSI reports and / or HARQ-ACK information, etc.

[0018] In conjunction with the first or second aspect, in some possible implementations, the method further includes: determining a second parameter of the HARQ-ACK information, the second parameter of the HARQ-ACK information being used to scale the resource size occupied by the HARQ-ACK information. This can reduce the resource size occupied by the HARQ-ACK information.

[0019] The second parameter of the HARQ-ACK information may be equal to or different from the first parameter of the CSI report. When the second parameter of the HARQ-ACK information is equal to the first parameter of the CSI report, the network side can send only one configuration message to indicate the corresponding values ​​of the first and second parameters, which can save signaling overhead.

[0020] In conjunction with the first aspect or the second aspect, in some possible implementations, the first parameter and / or the second parameter includes a bias value and / or a scaling factor.

[0021] The bias value can be beta_offset, for example, as reported in CSI Part 1. CSI Part 2 report Compared to the bias values ​​greater than 1 in the prior art, the bias value of the CSI report involved in this application can be understood as a newly introduced bias value. In this application, the UCI reused on the PUSCH may include HARQ-ACK information and / or CSI reports, and may not include scheduling requests (SRs). In some possible implementations, the bias value of the newly introduced HARQ-ACK information may also introduce a new value, for example, a value less than or equal to 1.

[0022] In some possible implementations, the bias values ​​of CSI reports and / or HARQ-ACK information can be determined using indexes in the CSI reports and / or HARQ-ACK information. It is understood that indicating bias values ​​through indexes can save signaling overhead. The bias values ​​can be improved values ​​based on tables provided in existing protocols such as Table 9.3-3 or Table 9.3-3A of TS38.213, for example, by setting reserved fields in those tables to bias values ​​less than or equal to 1. Alternatively, the bias values ​​can be determined using a new table, where bias values ​​less than or equal to 1 can be understood as the bias values ​​that take effect when using OCC sequences for extension. That is, when using OCC sequences for extension, if UCI is to be reused on the PUSCH performing the OCC extension, using bias values ​​less than 1 can reduce the resource size occupied by UCI. Otherwise, bias values ​​greater than 1 can be used.

[0023] This application does not limit the magnitude of the bias value. In other possible implementations, the bias value may be between 0.1 and 1, or between 0 and 1, or between 0.05 and 1, etc. It is understood that when the UCI bias value is less than 1, the resource size occupied by the UCI can be reduced, thereby reducing the impact on the data carried on the PUSCH of the UCI multiplexing, which is beneficial for the second communication device to receive the correct data.

[0024] In some possible implementations, the bias value of the HARQ-ACK information can be changed to a new value, which can be less than or equal to 1. This reduces the resource consumption of the HARQ-ACK information.

[0025] The second parameter of the HARQ-ACK information can be described with reference to the first parameter, and is the bias value and / or scaling factor of the HARQ-ACK information. The bias value of the HARQ-ACK information can be a value added based on Table 9.3-1 in protocol TS38.213, such as a value less than or equal to 1, such as 0.05, 0.5, etc.

[0026] In some possible implementations, the bias values ​​of the newly introduced HARQ-ACK information and / or CSI reports, after mapping and coding, will not cause an increase in the original modulation order of the UCI when the first communication device transmits uplink information. Alternatively, the bias values ​​of the newly introduced HARQ-ACK information and / or CSI reports, after mapping and coding, will not cause the modulation order of the UCI to exceed a first threshold when the first communication device transmits uplink information, or will not cause the transformed or increased value of the modulation order of the UCI to exceed the first threshold when the first communication device transmits uplink data. Alternatively, the bias values ​​of the newly introduced HARQ-ACK information and / or CSI reports, after mapping and coding, will not cause the increase in the code rate of the UCI when the first communication device transmits uplink information to exceed the first threshold.

[0027] The first threshold can be predetermined by the protocol or configured by the network side. For example, it can be determined through at least one configuration information from downlink control information (DCI), radio resource control (RRC) signaling, and medium access control (MAC) control element (CE) signaling. Any two of the first thresholds—compared to the increase in code rate, the increase in modulation order, and the change in modulation order—can be equal or unequal, and this is not limited here. It is understood that after the HARQ-ACK information and / or CSI report are mapped according to the newly introduced bias value, if the modulation order remains unchanged, or the increase in code rate and / or the increase in modulation order does not exceed the first threshold, it facilitates the second communication device in decoding the corresponding information.

[0028] In other feasible implementations, if the bias value of the HARQ-ACK information and / or CSI report is greater than 1, and other first parameters, such as the scaling factor, are less than or equal to 1, then the HARQ-ACK information and / or CSI report with OCC sequence extension can be sent on the PUSCH, and the HARQ-ACK information with OCC sequence extension can also be sent. If the bias value of the HARQ-ACK information and / or CSI report is greater than 1, and other first parameters are greater than 1, then UCI can be omitted, preventing the HARQ-ACK information and / or CSI report from being sent. Alternatively, other limiting conditions can be determined, such as the resource size occupied by UCI being less than or equal to a second threshold, and the CSI report with OCC sequence extension can also be sent on the PUSCH, and the HARQ-ACK information with OCC sequence extension can also be sent, etc., without further limitation.

[0029] The resource size occupied by UCI can be the total number of resource units occupied by UCI, the total number of bits occupied by UCI, or the length of the sequence output after rate matching by UCI. Alternatively, the resource size occupied by UCI can be the resource size occupied by CSI reports in UCI, and / or the resource size occupied by HARQ-ACK information, etc. The resource size occupied by UCI may exclude the resource size occupied by SR. Specifically, the resource size can be the number of resource units occupied by HARQ-ACK information and / or CSI reports, or the number of bits occupied by HARQ-ACK information and / or CSI reports, or the length of the sequence output after rate matching by HARQ-ACK information and / or CSI reports. Alternatively, it can be the sum of the resource sizes occupied by the above information and CRC, etc. Resource units can be symbols or REs, etc., and symbols can be modulation symbols or OFDM symbols, etc., without limitation. CRC can be the CRC of all information in UCI, or the CRC can be the CRC of one or more information in UCI, such as the CRC of HARQ-ACK information, or the CRC of CSI reports. The CRC reported by CSI can include the CRC reported by CSI part1, or the CRC reported by CSI part2, or the CRC reported by both CSI part1 and CSI part2. It can be understood that if the resource size occupied by UCI is less than or equal to the second threshold, it indicates that the resource occupied by UCI is relatively small, and its impact on the data carried on the PUSCH after UCI multiplexing is minimal, which is beneficial for the second communication device to receive correct data.

[0030] This application does not limit the second threshold; the second threshold compared with the size of each type of resource may be equal to or different from the second threshold. The second threshold may be predetermined by the protocol or configured by the network side. For example, the second threshold may be determined by at least one of the configuration information of DCI, RRC signaling, and MACCE signaling.

[0031] It should be noted that this application uses a first parameter less than or equal to 1 as an example. In practice, if the first parameter is equal to 1, UCI may not be reused on PUSCH. Equal to the first threshold and / or the second threshold can also be achieved using different steps. For example, if the resource size is greater than or equal to the second threshold, UCI may not be reused on PUSCH.

[0032] In this application, the scaling factor may include a resource scaling factor α, or it may be a new parameter, such as ε. ε may be a scaling factor for CSI reports, or it may be a scaling factor for other information. In some possible implementations, the scaling factor may be a scaling factor for each type in UCI, such as a commonscaling factor. That is, the scaling factor may scale the resource size occupied by each type in UCI, or scale the resource size occupied by one type. For example, CSI reports and HARQ-ACK information may correspond to the same or different scaling factors.

[0033] This application does not limit the size of the scaling factor. The scaling factor can be less than 0.5, or it can be less than or equal to 0.5, and at least one of 0.65, 0.8, and 1, or it can be less than or equal to 1. Among these, 0.5, 0.65, 0.8, and 1 can be values ​​of α defined in existing technologies (such as protocol TS38.331). When the scaling factor of UCI is less than 0.5, the resource size occupied by each piece of information in UCI can be further reduced, such as the resource size occupied by HARQ-ACK information and CSI reports. This application also does not limit the size of the bias value less than 0.5, for example, 0.1, 0.05, etc.

[0034] It is understandable that when the scaling factor for each piece of information in UCI is less than 1, the resource size occupied by UCI can be reduced. For example, when the scaling factor for CSI reports and / or HARQ-ACK information is less than 1, the resource size occupied by CSI reports and / or HARQ-ACK information can be reduced, thereby reducing the impact on the OCC-extended data on the PUSCH after multiplexing CSI and / or HARQ-ACK information, which is beneficial for the second communication device to receive correct data. When the scaling factor of CSI reports is equal to the scaling factor of other information (such as HARQ-ACK information), that is, when the scaling factor is common information applicable to multiple pieces of information, the network side can configure only one scaling factor, thereby reducing signaling overhead. When the scaling factor of CSI reports is different from the scaling factors of other information, the scaling factor can be understood as dedicated information, and the network side needs to configure the scaling factor for each piece of information to ensure the flexibility of scaling factor settings.

[0035] In this application, the first parameter and / or the second parameter can be a bias value and / or a scaling factor. The first parameter and / or the second parameter may also include other information or other forms of representation, i.e., not through... α, ε, etc., represent the first parameter and / or the second parameter. For example, the first parameter of the CSI report can be indicated by the index of the CSI report, and the second parameter of the HARQ-ACK information can be indicated by the index of the HARQ-ACK information.

[0036] In conjunction with the first aspect or the second aspect, in some possible implementations, the first parameter and / or the second parameter are activated when using OCC sequence extension. That is, the first parameter and / or the second parameter can be used when UCI (CSI report and / or HARQ-ACK information, etc.) is multiplexed to the PUSCH that performs OCC extension.

[0037] In conjunction with the first aspect or the second aspect, in some possible implementations, the first parameter and / or the second parameter are related to one of the following: configuration parameters of the OCC sequence, or parameters in the DCI. Thus, the first parameter and / or the second parameter can be determined through the configuration parameters of the OCC sequence and / or parameters in the DCI, saving signaling overhead.

[0038] In conjunction with the first aspect or the second aspect, in some possible implementations, the configuration parameters of the OCC sequence include at least one of the following: the code length of the OCC sequence and / or the index of the OCC sequence.

[0039] In conjunction with the first or second aspect, in some possible implementations, the configuration parameters of the OCC sequence further include an OCC sequence enable indicator; wherein, the OCC sequence enable indicator is used to indicate the use of the OCC sequence for extension, and the information carried on the extended first PUSCH is multiplied by the information and the OCC element corresponding to the resource unit occupied by the first PUSCH in the OCC sequence. This information may include data carried on the PUSCH and / or information multiplexed by UCI, etc., and is not limited thereto.

[0040] In some possible implementations, if no OCC sequence enable indication is provided, the OCC sequence is used for extension by default if the OCC sequence configuration parameters include the code length and / or index of the OCC sequence. If an OCC sequence enable indication is provided, the first and / or second parameters can be activated, thereby reducing the resource size occupied by UCI.

[0041] In some possible implementations, the configuration parameters of the OCC sequence may also include other configuration parameters not described herein, and are not limited thereto. These configuration parameters of the OCC sequence may be used to indicate the first parameter and / or the second parameter, such as a scaling factor and / or an offset value.

[0042] In some possible implementations, the first and / or second parameter corresponding to an OCC sequence code length of 2 can be greater than the first and / or second parameter corresponding to an OCC sequence code length of 4. For example, when the OCC sequence code length is 2, the UCI is usually repeated twice, which is a smaller number of repetitions, and the scaling factor can be a larger value, such as 0.6; when the OCC sequence code length is 4, the UCI is usually repeated four times, which is a larger number of repetitions and has higher reliability, and the scaling factor can be a smaller value, such as 0.2.

[0043] In some possible implementations, the scaling factor can be configured in the information element of the bias value.

[0044] In conjunction with the first aspect or the second aspect, in some possible implementations, the parameters in the DCI include at least one of the following: an indicator value of the offset value (such as a beta_offset indicator), an antenna port, a redundancy version (RV), and a modulation and coding scheme (MCS).

[0045] In this application, the mapping relationship between the parameters in the DCI and the first parameter / or the second parameter can be obtained by improving upon tables provided by existing protocols, or by using tables that take effect when using OCC sequence extensions, etc., and is not limited here. The first parameter / or the second parameter may also be related to n. SCIDThe following parameters are related to the code division multiplexing (CDM) group value, CDM group value λ, parameter Δ, DMRS extra position, DMRS type, PUSCH DMRS time index l′, sounding reference signal (SRS) request message, SRS resource setting indication, SRS offset indication, phase tracking reference signal (PT-RS)-DMRS association, precoding information and layer number, channel state information (CSI) request, PUSCH scheduling transmission power control (TPC) command, code block group (CBG) transmission information, etc., and are not limited here. These indication values ​​can be used alone to indicate the first parameter / or the second parameter, or they can be used in combination to indicate the first parameter / or the second parameter, and are not limited here. Alternatively, the scaling factor can be bound to a value, which can be the aforementioned antenna port, redundancy version, MCS, etc., without limitation here.

[0046] In conjunction with the first or second aspect, in some possible implementations, the first PUSCH is also multiplexed with HARQ-ACK information. This prevents the HARQ-ACK information to be sent by the terminal from being discarded. The resource size occupied by HARQ-ACK information on the first PUSCH can be scaled using the second parameter, or it can be scaled without the second parameter, etc., without limitation here. The information multiplexed onto the PUSCH in UCI may include other information besides CSI reports and HARQ-ACK information, without limitation here. After HARQ-ACK information is multiplexed onto the first PUSCH, the first PUSCH undergoes OCC sequence expansion, so that the HARQ-ACK information also undergoes OCC sequence expansion, consistent with the CSI report.

[0047] This application does not limit the method of using the first parameter and / or the second parameter; improvements can be made by referring to the formulas provided in existing protocols. Alternatively, new formulas can be introduced. For example, the bias value can be substituted into the formulas provided in existing protocols. Another example is that the scaling factor can be multiplied by the resource size of the HARQ-ACK information or CSI report calculated by the existing formula; the scaling factor can also be multiplied by partial information in the existing formula, which can be used to determine the minimum resources occupied by the HARQ-ACK information or CSI report, etc.

[0048] In conjunction with the first or second aspect, in some possible implementations, HARQ-ACK information and CSI reports are carried on the Physical Uplink Shared Channel (PUCCH). The time-domain resources occupied by the PUCCH overlap with K time units, which are contained within M time units. Each of the M time units is used to carry the PUSCH for uplink data, where M and K are integer multiples of L, and L is the code length of the OCC sequence. The method includes: when M = L, transmitting a first PUSCH on each of the K time units. That is, the first communication device transmits the first PUSCH on each of the K time units. Correspondingly, the second communication device receives the first PUSCH on each of the K time units.

[0049] In this application, the M time units include K time units. The uplink data transmitted in each of the M time units can be the same or belong to the same transport block. The K time units can be time-domain resources that actually overlap with the time-domain resources occupied by the PUCCH in the M time units, and these time-domain resources correspond to a complete OCC sequence, meaning the number of corresponding time units is an integer multiple of L.

[0050] It's understandable that when M equals L, M = K = L. Discarding the uplink data carried on the PUSCH would prevent the network from receiving the uplink data, potentially leading to retransmissions and wasting resources. Therefore, UCIs such as CSI reports and HARQ-ACK information can be multiplexed onto the PUSCH. This multiplexed PUSCH can then be extended using OCC to obtain a first PUSCH. This first PUSCH, in addition to the OCC-extended CSI reports and HARQ-ACK information, can also include some uplink data. This reduces the impact of the multiplexed PUSCH on data transmission, making it easier for the second communication device to receive the correct data.

[0051] In conjunction with the first or second aspect, in some possible implementations, the method includes: when M > K, not transmitting the PUSCH for K time units, and transmitting a second PUSCH for the remaining M time units (excluding the K time units), the second PUSCH carrying uplink data extended by the OCC sequence. That is, when the number of repetitions of the PUSCH is greater than K, the first communication device can discard the PUSCH for K time units, thus not transmitting the uplink data carried on that PUSCH. Instead, uplink data extended by the OCC sequence can be transmitted in the remaining M time units (excluding the K time units), facilitating the second communication device to receive the correct data.

[0052] If no PUSCH is sent in the K time units, CSI reports and / or HARQ-ACK information can be sent via PUCCH on the time domain resources occupied by PUCCH, or CSI reports and / or HARQ-ACK information can be sent via PUCCH in each of the K time units, etc., without limitation. Sending CSI reports and / or HARQ-ACK information via PUCCH can be done without OCC sequence extension.

[0053] In some possible implementations, the method may further include: transmitting the PUCCH when the frequency domain resources occupied by the PUCCH do not overlap with the frequency domain resources occupied by the PUCCH in a time unit that overlaps with the time domain resources occupied by the PUCCH. Not transmitting the PUCCH when the frequency domain resources occupied by the PUCCH overlap with the frequency domain resources occupied by the PUCCH in a time unit that overlaps with the time domain resources occupied by the PUCCH. That is, when there is overlap in the time domain resources between the PUCCH and PUSCH but no overlap in the frequency domain resources, a UCI can be transmitted via the PUCCH, and this UCI may not undergo OCC sequence extension. When there is overlap in both the time domain resources and the frequency domain resources between the PUCCH and PUSCH, neither the PUCCH nor the UCI carried on the PUCCH may be transmitted.

[0054] The above example illustrates OCC extension by multiplying information from a time unit with an OCC element. In other possible implementations, OCC extension can be performed on frequency domain units (such as REs). For example, a first PUSCH or PUCCH is transmitted in each of K frequency domain units. Optionally, the K frequency domain units are frequency domain resources that actually overlap between the frequency domain resources occupied by the PUCCH and the frequency domain resources occupied by the PUSCH, and correspond to a complete OCC sequence. In some possible implementations, if the time domain resources occupied by the PUCCH do not overlap with the time domain resources occupied by the PUSCH in the K frequency domain units where the time domain resources occupied by the PUCCH overlap with the frequency domain resources occupied by the PUCCH, then the PUCCH is transmitted. If the time domain resources occupied by the PUSCH overlap with the time domain resources occupied by the PUCCH in the K frequency domain units where the time domain resources occupied by the PUCCH overlap with the frequency domain resources occupied by the PUCCH, then the PUCCH is not transmitted, thus neither the UCI nor the PUCCH is transmitted.

[0055] In some possible implementations, the code length of the OCC sequence can be a frequency hopping value, such as X. That is, the PUSCH extended by the OCC sequence can be transmitted via inter-slot frequency hopping, with frequency hopping occurring in each time slot. Thus, when the code length of the OCC sequence is 4, the second communication device can simultaneously schedule the first communication device with an OCC sequence code length of 2 and the first communication device with an OCC sequence code length of 4 on the same resource.

[0056] In some possible implementations, the first PUSCH can transmit information extended by the OCC sequence over a fixed-length resource unit. This application does not limit the fixed-length time unit; it can be an integer multiple of the code length of the OCC sequence, such as 4. Thus, regardless of whether the code length of the OCC sequence is 2 or 4, both a first communication device with a code length of 2 and a first communication device with a code length of 4 of the OCC sequence can be simultaneously scheduled on the same resource unit.

[0057] It should be understood that the second aspect is implemented by the second communication device. The specific content of the second aspect corresponds to that of the first aspect, and the corresponding features and beneficial effects of the second aspect can be referred to the description of the first aspect. To avoid repetition, detailed descriptions are appropriately omitted here.

[0058] Thirdly, this application discloses a communication method that can be applied to a first communication device. The first communication device can be a terminal as a finished product, a component or module with terminal functions, a circuit or chip (such as a modem chip, also known as a baseband chip, or a system-on-a-chip (SoC) chip containing a modem core, or a system-in-package (SIP) chip), chip system, or processor) that can be applied to the terminal to perform communication functions. Alternatively, it can be a logical node, logical module, or software capable of implementing all or part of the terminal functions. The method includes: transmitting an SRS extended by an OCC sequence in each of P time units.

[0059] Where P is an integer multiple of L, and each of the P time units is used to carry the PUSCH for uplink data to be transmitted. This uplink data may be different from or the same as the uplink data to be transmitted in the aforementioned M time units. The P time units are the time units corresponding to the OCC sequence associated with the time domain resources occupied by the SRS, or can be described as the time units corresponding to the OCC sequence in which the SRS is located. Thus, transmitting the SRS in each of the P time units, and the SRS can be extended by the OCC sequence, does not affect other first communication devices from transmitting data after OCC sequence extension through the PUSCH on the time domain resources for transmitting the SRS, and can ensure the orthogonality between data. In the P time units, the uplink data carried on the PUSCH after OCC sequence extension can also be transmitted on the time domain resources not occupied by the SRS.

[0060] In conjunction with the third aspect, in some possible implementations, the SRS with OCC sequence extension is transmitted on the time domain resources occupied by the SRS in P time units. That is, the SRS with OCC sequence extension can be transmitted on the time domain resources occupied by the SRS in P time units, and the data with OCC sequence extension can be transmitted on the time domain resources other than those occupied by the SRS in P time units.

[0061] In conjunction with the third aspect, in some possible implementations, when P is greater than L, the SRS with OCC sequence extension is transmitted in each of the L time units, and the uplink data carried on the P USCH with OCC sequence extension is transmitted in the time units other than the L time units. Thus, the SRS with OCC sequence extension can be transmitted on the time domain resources corresponding to the SRS in each of the L time units, and the data with OCC sequence extension can be transmitted on the time domain resources other than those occupied by the SRS in the P time units. This application does not limit the number of L time units.

[0062] In conjunction with the third aspect, in some possible implementations, the first SRS symbol in the first time unit out of P time units satisfies the timeline condition. The first SRS symbol is determined by the first symbol configured on the network side to begin transmission of the SRS. This timeline condition can be either the timeline condition required for scheduling PUSCH or the timeline condition required for transmitting the SRS.

[0063] In conjunction with the third aspect, in some possible implementations, the timeline condition is that the interval between the last symbol of the PDCCH and the start time of the first slot in the OCC sequence is not less than the processing duration. This processing duration can be the PUSCH preparation time of the terminal device as described in protocol TS38.214 6.2.1. This avoids SRS dropping.

[0064] In conjunction with the third aspect, in some possible implementations, the method may further include: if the first SRS symbol in the first time unit of P time units does not meet the timeline conditions, the SRS may not be transmitted, or the SRS may be transmitted in a subsequent time unit that meets the timeline conditions.

[0065] The above implementation methods for sending SRS can be executed if the timeline conditions are met, or they can be executed if the timeline conditions are not met.

[0066] Fourthly, this application discloses a communication method that can be applied to a second communication device. The second communication device can be a network device as a final product, a component or module with network device functions, or a communication chip (e.g., a processor, baseband chip, or chip system) applicable to a network device. The method includes: receiving, in each of the P time units, an SRS extended by an OCC sequence, provided that the first time unit in the P time units meets the timeline conditions. Here, P is an integer multiple of L, and L is the code length of the OCC sequence. Each of the P time units is used to carry the PUSCH of the uplink data to be transmitted, and the P time units are the time units corresponding to the OCC sequence associated with the time domain resources occupied by the SRS.

[0067] In conjunction with the fourth aspect, in some possible implementations, the SRS after OCC sequence extension is received on the time domain resources occupied by the SRS in P time units.

[0068] In conjunction with the fourth aspect, in some possible implementations, when P is greater than L, the SRS after OCC sequence expansion is received in each of the L time units, and the uplink data carried on PUSCH after OCC sequence expansion is received in the time units other than the L time units in the P time units.

[0069] In conjunction with the fourth aspect, in some possible implementations, the first SRS symbol in the first time unit of the P time units satisfies the timeline condition, and the first SRS symbol is determined by the first symbol that the SRS transmission begins.

[0070] In conjunction with the fourth aspect, in some possible implementations, the method may further include: if the first SRS symbol in the first time unit of P time units does not meet the timeline condition, the SRS may not be received, or the SRS may be received in a subsequent time unit that meets the timeline condition.

[0071] It should be understood that the second communication device is the implementing entity of the fourth aspect. The specific content of the fourth aspect corresponds to that of the third aspect, and the corresponding features and beneficial effects of the fourth aspect can be referred to the description of the third aspect. To avoid repetition, detailed descriptions are appropriately omitted here.

[0072] Fifthly, this application discloses a communication device, including units, modules, or means for performing the steps of the methods described in the first or fourth aspects or any of them. The modules, units, or means can be implemented by software, hardware, or a combination of software and hardware.

[0073] Sixthly, this application discloses another communication device, which includes a processor for executing computer programs or instructions, such that when the processor executes the computer programs or instructions, the methods of any one of the first to fourth aspects or any possible implementations described above are implemented. Optionally, the communication device further includes a memory.

[0074] Optionally, the communication device may also include interface circuitry, wherein the processor is used to communicate with other devices or components via the interface circuitry.

[0075] Optionally, the communication device may also include a memory.

[0076] In conjunction with the fifth or sixth aspect, in some feasible examples, the communication device may be a first communication device or a second communication device. The first communication device may be a terminal as a finished product, a component or module with terminal functions, or a circuit or chip (such as a modem chip, also known as a baseband chip, or a system-on-chip (SoC) chip or system-in-package (SIP) chip containing a modem core), a chip system, or a processor that can be applied to the terminal to perform communication functions. Alternatively, it may be a logical node, logical module, or software that can implement all or part of the terminal functions.

[0077] In conjunction with the fifth or sixth aspect, in some feasible examples, the communication device may be a second communication device, which may be a network device as a final product, a component or module with network device functions, or a communication chip (such as a processor, baseband chip, or chip system) that can be applied in a network device.

[0078] In one implementation, the second communication device can be a non-terrestrial network device, such as a satellite.

[0079] In a seventh aspect, this application provides a communication system comprising a first communication device and a second communication device. When the first communication device operates in the communication system, it is used to perform the methods described in the first or third aspect or feasible examples thereof. When the second communication device operates in the communication system, it is used to perform the methods described in the second or fourth aspect or feasible examples thereof.

[0080] Eighthly, this application provides another communication system, which includes communication devices as described in the fifth aspect or any possible implementation thereof.

[0081] Ninthly, this application provides a computer-readable storage medium storing a computer program or instructions that, when executed, cause the method of any one of the first to fourth aspects or any possible implementation thereof to be implemented.

[0082] In a tenth aspect, this application provides a computer program product comprising a computer program or instructions that, when executed, cause the method of any one of the first to fourth aspects or any possible implementation thereof to be implemented.

[0083] In one aspect, this application provides a chip or chip system, including at least one processor for calling and executing instructions stored in a memory, causing a communication device on which the chip or chip system is mounted to perform the method of any one of the first to fourth aspects or any possible implementation thereof.

[0084] Optionally, the chip also includes a communication interface for receiving or sending signals.

[0085] Optionally, the chip or chip system may also include memory.

[0086] In a twelfth aspect, this application provides another chip, including: an input interface, an output interface, and a processing circuit. The input interface, the output interface, and the processing circuit are connected to the circuit via internal connection paths. The processing circuit is used to execute the method of any of the above aspects or possible examples. Optionally, the chip also includes a memory. The input interface, the output interface, the processor, and the memory are connected via internal connection paths. The processor is used to execute code in the memory. When the code is executed, the processor is used to execute the method of any of the above aspects or possible examples.

[0087] In a thirteenth aspect, this application provides a chip system including at least one processor and a communication interface, the communication interface and at least one processor being interconnected via a line, the at least one processor being used to run a computer program or instructions to perform the methods in any of the above aspects or possible examples.

[0088] It should be understood that the implementation and beneficial effects of the above-mentioned aspects can be mutually referenced.

[0089] Furthermore, in the process of executing any of the first to second aspects and any possible implementations of the method described above, the processes related to sending and / or receiving information in the above methods can be understood as the process of the processor outputting information, and / or the process of the processor receiving input information. When outputting information, the processor can output the information to a transceiver (or communication interface or transmitting module) so that the transceiver can transmit it. After the information is output by the processor, it may need to undergo other processing before reaching the transceiver. Similarly, when the processor receives input information, the transceiver (or communication interface or transmitting module) receives the information and inputs it into the processor. Furthermore, after the transceiver receives the information, the information may need to undergo other processing before being input into the processor.

[0090] Based on the above principles, for example, the information sent mentioned in the aforementioned method can be understood as information output by the processor. Similarly, the information received can be understood as information received by the processor from input.

[0091] Optionally, unless otherwise specified, or unless they contradict their actual function or internal logic in the relevant description, the operations of the processor, such as transmitting, sending, and receiving, can be more generally understood as processor output and receiving, input, and other operations.

[0092] Optionally, in the process of executing the method of any of the first to second aspects and any possible implementations described above, the processor may be a processor specifically designed to execute these methods, or it may be a processor that executes these methods by executing computer instructions stored in memory, such as a general-purpose processor. The memory may be a non-transitory memory, such as read-only memory (ROM), which may be integrated with the processor on the same chip or disposed on separate chips. This application does not limit the type of memory or the arrangement of the memory and processor. Attached Figure Description

[0093] The accompanying drawings used in the embodiments of this application are described below.

[0094] Figure 1A This is a schematic diagram of the architecture of a communication system provided in an embodiment of this application;

[0095] Figure 1B This is a schematic diagram of the architecture of an NTN communication system provided in an embodiment of this application;

[0096] Figure 2 This is a schematic diagram of uplink information carried on a PUSCH according to an embodiment of this application;

[0097] Figure 3A This is a schematic diagram illustrating the principle of inter-slot OCC extension provided in an embodiment of this application;

[0098] Figure 3B This is a schematic diagram illustrating the principle of inter-symbol OCC extension provided in an embodiment of this application;

[0099] Figure 4 This is a flowchart illustrating a communication method provided in an embodiment of this application;

[0100] Figures 5A to 5D These are schematic flowcharts of a communication method provided in an embodiment of this application;

[0101] Figure 6 This is a schematic diagram of information transmission provided in an embodiment of this application;

[0102] Figure 7A and Figure 7B These are schematic diagrams illustrating an information transmission method provided in the embodiments of this application;

[0103] Figure 8 This is a schematic diagram of the structure of a communication device provided in an embodiment of this application;

[0104] Figure 9 This is a schematic diagram of another communication device provided in an embodiment of this application;

[0105] Figure 10 This is a schematic diagram of the structure of a terminal device provided in an embodiment of this application. Detailed Implementation

[0106] The technical solutions in the embodiments of this application will be clearly and completely described below with reference to the accompanying drawings.

[0107] The technical solutions of this application embodiment can be applied to various communication systems, such as long term evolution (LTE) communication systems, new radio (NR) communication systems, LTE-Advanced (LTE-A) communication systems, device-to-device (D2D) communication systems, vehicle-to-everything (V2X) communication systems, machine-to-machine (M2M) communication systems, internet of things (IoT) communication systems, narrowband internet of things (NB-IoT) communication systems, integrated sensing and communication systems, frequency division duplex (FDD) communication systems, time division duplex (TDD) communication systems, wireless projection communication systems, integrated access and backhaul (IAB) communication systems, public land mobile network (PLMN) communication systems, non-public network (NPN) communication systems, and future communication systems, or can be used for non-3rd generation partnerships. The application does not limit the scope of the method provided in this embodiment to non-terrestrial network (NTN) communication systems (also known as non-terrestrial network communication) or scenarios where NTN and terrestrial network (TN) are integrated. NTN can be a communication system integrated with other communication systems such as 4G, 5G mobile communication systems, or future communication systems, such as NR NTN, IoT NTN, etc. NTN communication systems can be, for example, satellite communication systems, and can also include unmanned aerial vehicles (UAVs), high altitude platform stations (HAPS), and other aerial access network equipment; this application does not limit the scope of the application.

[0108] For example, please refer to Figure 1A , Figure 1A This is a schematic diagram of the architecture of a communication system provided in an embodiment of this application. Figure 1AAs shown, the communication system may include at least one terminal device and at least one network device. The terminal device can be connected to the network device wirelessly or via a wired connection, enabling uplink (UL) or downlink (DL) communication. Terminal devices can also connect to each other wirelessly or via a wired connection, enabling sidelink (SL) communication.

[0109] Terminal devices and network devices, network devices and network devices, and terminal devices and terminal devices can communicate using licensed spectrum, unlicensed spectrum, or both simultaneously. This application does not limit the spectrum resources used by terminal devices and network devices.

[0110] The terminal equipment involved in this application is an entity on the user side used to receive or transmit signals, providing voice and / or data to the user. Terminal equipment can be a terminal, user equipment (UE), access terminal, UE unit, UE station, mobile device, mobile station, mobile station, mobile terminal, mobile client, mobile unit, remote station, remote terminal, remote unit, wireless unit, wireless communication equipment, user agent, or user device, etc. Among them, the access terminal can be a cellular phone, cordless phone, session initiation protocol (SIP) phone, wireless local loop (WLL) station, personal digital assistant (PDA), handheld device with wireless communication capabilities, computing device or other processing device connected to a wireless modem, vehicle-mounted device, wearable device, terminal in a future communication system, terminal in a future evolved PLMN, or terminal in a future NPN, etc. Terminal equipment can also be a communication module with satellite communication capabilities, a satellite phone or its components, or a satellite communication terminal, such as a very small aperture terminal (VSAT) (commonly referred to as a VSAT terminal), a portable station, a fixed station, or a vehicle-mounted or airborne satellite communication terminal. It should be understood that a satellite communication terminal can serve as a micro base station to further provide data interfaces to accessed user equipment. Hereinafter, it will sometimes be simply referred to as a terminal.

[0111] exist Figure 1AIn this example, network devices are represented by access network (AN) nodes. Access network nodes can also be called radio access network (RAN) nodes, or simply access networks. Access network nodes are used to connect terminal devices to the wireless network. In other words, the access network provides access services to terminal devices, enabling them to access (or connect to) the network. Access networks can support both wired and wireless access.

[0112] Optionally, the access network consists of multiple AN / RAN nodes. AN / RAN nodes can include, but are not limited to: access points (APs), enhanced node Bs (eNBs), home evolved node Bs (HNBs), baseband units (BBUs), next-generation node Bs (gNBs), transmission reception points (TRPs), transmission points (TPs), or other access nodes, such as wireless relay nodes or wireless backhaul nodes. AN / RAN nodes can be one or more antenna panels, or network nodes constituting gNBs or transmission points, such as BBUs or distributed units (DUs), or devices performing RAN functions in communication systems such as D2D, V2X, M2M, and U2U. AN / RAN nodes can be radio controllers in cloud radio access network (CRAN) scenarios, open RAN (O-RAN or ORAN), or access networks in future communication systems, etc., without any limitations.

[0113] In some deployments, a gNB may include a centralized unit (CU) and a dedicated unit (DU). The gNB may also include an active antenna unit (AAU). The CU implements some of the gNB's functions, and the DU implements others. For example, the CU handles non-real-time protocols and services, implementing radio resource control (RRC) and packet data convergence protocol (PDCP) layer functions. The DU handles physical layer protocols and real-time services, implementing radio link control (RLC), media access control (MAC), and physical (PHY) layer functions. The AAU implements some physical layer processing functions, radio frequency processing, and active antenna-related functions. RRC layer information is generated by the CU and is ultimately encapsulated by the DU's PHY layer to become PHY layer information, or it may be derived from PHY layer information. Therefore, in this architecture, higher-layer signaling, such as RRC layer signaling, can be considered as being sent by the DU, or by the DU+AAU. It is understood that network devices can be one or more of the following: CU nodes, DU nodes, and AAU nodes. Furthermore, a CU can be classified as a network device in the radio access network (RAN) or a network device in the core network (CN); this application does not limit this classification.

[0114] Furthermore, the solution provided in this application can be applied to satellite communication systems, such as 5G systems or NTN integrated into future evolved communication systems. In this case, the network equipment can be a satellite with access network equipment functionality, or an access network device deployed on a satellite. In some satellite communication scenarios, the network equipment can also be a satellite communication terminal, such as a portable station, a fixed station, a vehicle-mounted or airborne satellite communication terminal. It should be understood that in these scenarios, the satellite communication terminal communicates with the satellite and can act as a micro base station or satellite data station to further provide data interfaces to user equipment accessing the satellite communication terminal.

[0115] In some satellite communication scenarios, network equipment can also be satellite communication terminals, such as portable stations, fixed stations, vehicle-mounted or airborne satellite communication terminals. It should be understood that in these scenarios, the satellite communication terminal communicates with the satellite and can act as a micro base station to further provide data interfaces to user equipment accessing the satellite communication terminal. Network equipment can also be a satellite (or satellite base station) or a high altitude platform station (HAPS), or base station equipment mounted on a satellite / HAPS. The satellite can include at least one of the following: geostationary earth orbit (GEO) satellites or non-geostationary earth orbit (NGEO) satellites. Non-geostationary earth orbit satellites can include at least one of the following: medium earth orbit (MEO) satellites or low earth orbit (LEO) satellites. There are no restrictions here. Network equipment can also be a gateway station (or ground station, earth station, signal gateway, gateway, or gateway station).

[0116] In such Figure 1A The network architecture shown illustrates network devices using access network nodes as an example. Furthermore, Figure 1A The number and types of network devices and terminal devices included in the network architecture shown are merely examples, and the embodiments of this application are not limited thereto. For example, it may also include more or fewer terminal devices communicating with the network devices. Similarly, it may include more or fewer network devices communicating with the terminal devices. For the sake of brevity, they are not described one by one in the accompanying drawings.

[0117] Optionally, the communication system may also include Figure 1A Network devices not shown, such as core network devices, data network devices, etc.

[0118] In different communication systems, core network equipment (hereinafter referred to as core network) can correspond to different devices. For example, in a 3G communication system, it can correspond to the Serving GPRS Support Node (SGSN) and / or the Gateway GPRS Support Node (GGSN); in a 4G communication system, it can correspond to the Mobility Management Entity (MME) and / or the Serving Gateway (S-GW); and in a 5G communication system, it can correspond to policy control function (PCF) network elements, unified data management (UDM) network elements, application function (AF) network elements, access and mobility management function (AMF) network elements, session management function (SMF) network elements, location management function (LMF) network elements, user plane function (UPF) network elements, etc.

[0119] Among them, the UPF network element is responsible for managing the transmission of user plane data and quality of service (QoS) control, traffic statistics and other functions. It can perform user data packet forwarding according to the routing rules of the session management network element, such as sending uplink data to the data network or other user plane network elements, and forwarding downlink data to other user plane network elements or (R)AN network elements.

[0120] The AMF (Access Default Mode) network element is responsible for user access management, security authentication, and mobility management. The LMF (Local Mode Default Mode) network element manages and controls location service requests from target terminals and processes location-related information. The SMF (Supply, Service Default Mode) network element manages sessions, allocating and releasing resources for terminal device sessions. The UDM (User Default Mode) network element manages the context of user subscriptions, such as storing terminal device subscription information. The PCF (Policy and Charging Rules Function) network element is responsible for user policy management. Similar to the Policy and Charging Rules Function (PCRF) network element in LTE, it is primarily responsible for policy authorization, quality of service (QoS), and generating charging rules, and distributing these rules to the UPF (User Default Mode) network element via the SMF network element to complete the installation of the corresponding policies and rules. The AF (Application Default Mode) network element can be a third-party application control platform or the operator's own equipment. The AF network element is responsible for application management and can provide services to multiple application servers.

[0121] In this embodiment, the data network device is hereinafter referred to as the data network. The data network is used to provide business services to users. Generally, the client is a terminal, and the server is the data network. The data network provided by the data network can be a private network, such as a local area network (LAN). The data network can also be an external network not managed by an operator, such as the Internet. The data network can also be a proprietary network jointly deployed by operators, such as a network providing Internet Protocol Multimedia Subsystem (IMS) services.

[0122] In some embodiments, network devices and terminal devices may also be referred to as communication devices, which may be general-purpose devices or special-purpose devices. This application does not specifically limit this.

[0123] This application does not limit the location of terminal devices and network devices; they can be in a fixed state or in a mobile state. Terminal devices and network devices can be deployed on land, water, air, etc. In the embodiments of this application, network devices deployed in the air can be referred to as non-terrestrial network devices, and network devices deployed on the ground can be referred to as terrestrial network devices. An NTN communication system includes at least one non-terrestrial network device and one terrestrial network device; all network devices in a terrestrial communication system are terrestrial network devices. Terrestrial network devices, relative to non-terrestrial network devices, are stationary or move at a relatively slow speed. That is, non-terrestrial network devices, relative to terrestrial network devices, can be high-speed mobile network devices.

[0124] Non-terrestrial network equipment may include satellites, high-altitude platforms (HAPs), drones, hot air balloons, low-Earth orbit satellites, medium-Earth orbit satellites, high-Earth orbit satellites, etc., without limitation. The term "satellite" in this application can refer to a collection of satellites and other network equipment related to satellite communication; therefore, in this application, the descriptions "satellite" and "satellite network equipment" are equivalent.

[0125] Please see Figure 1B , Figure 1B This is a schematic diagram of the architecture of an NTN communication system provided in an embodiment of this application. Figure 1B Taking an NTN communication system integrating 5G communication systems as an example, it should be understood that the solutions provided in this application embodiment can be applied to NTN systems integrating future evolved communication systems. The access network can be a next-generation radio access network (NG-RAN), and the core network can be a 5G core network (5G CN). The 5G core network equipment consists of multiple functional units, which can be divided into control plane and data plane functional entities, such as... Figure 1B The diagram shows a 5G control plane processing unit and a 5G user plane processing unit. The 5G control plane processing unit may include... Figure 1B The network elements include Access and Mobility Management Function (AMF) and Location Management Function (LMF) elements, and may also include PCF, UDM, AF, SMF, etc. (not shown in the figure). Figure 1B The architecture shown can be understood as an NTN-based NG-RAN architecture.

[0126] The interface between terminal equipment and network equipment in a wireless link can be called an air interface, such as the NR Uu interface. The NG interface serves as the interface between the access network and the core network, such as... Figure 1B The interfaces between 5G base stations and ground stations, between ground stations and 5G user plane processing units, and between ground stations and AMF network elements are mainly used for exchanging non-access stratum (NAS) signaling in the core network, as well as user service data. The Xn interface is the interface between access networks, such as... Figure 1B The interface between 5G base stations is mainly used for signaling interactions such as handover. The N6 interface can serve as the interface between the core network and the data network.

[0127] The above interfaces are illustrated using a 5G communication system. Different communication systems may use different names. For example, in a 4G communication system, the interface between access networks can be an X2 interface, and the interface between the access network and the core network can be an S1 interface, etc. Of course, in future communications, the names of these interfaces may remain unchanged or can be replaced with other names; this application does not limit this.

[0128] like Figure 1B As shown, an NTN system may include at least one terminal device, at least one non-terrestrial network device, and at least one terrestrial network device. The non-terrestrial network device is a satellite, such as a 5G base station. The terrestrial network device may include a ground station, a 5G base station, a 5G user plane processing unit, a 5G control plane processing unit, and data network equipment. The ground station is responsible for forwarding signaling and service data between the satellite (access network equipment) and the core network equipment. The functions of the terminal device and various network devices are as described above and will not be repeated here. The terminal device in NTN can be called an NTN terminal, such as an NTN-UE.

[0129] Satellites can communicate with each other as follows: Figure 1B The satellites shown have inter-satellite links (ISLs). These satellites can be referred to as regenerative sanitaries with inter-satellite links. The ISL between two satellites is connected via the Xn interface. Signaling exchange and user data transmission between access network devices can be completed between satellites. Alternatively, satellites may not have inter-satellite links.

[0130] Figure 1B The system architecture shown is a typical architecture in an NTN communication system. In reality, other system architectures can exist, such as transparent satellite access architectures (e.g., RAN architecture with transparent satellite), etc., which are not limited here.

[0131] In a transparent satellite access architecture, terminal devices access the network via an air interface, while 5G base stations are deployed on the ground and connected to ground stations that communicate with the satellite. This means that non-terrestrial network devices and ground stations within terrestrial network devices can act as radio frequency units (RF units), and access networks (such as base stations) within terrestrial network devices can perform RAN (Access Node B) functions (or access service functions). In the scenario corresponding to the transparent satellite access architecture, the satellite's role is: radio frequency filtering, frequency conversion, and amplification. In other words, the satellite can achieve transparent forwarding, acting as a layer 1 relay to regenerate physical layer signals, without involving any higher protocol layers.

[0132] Figure 1A and Figure 1B The number and types of communication devices included in the network architecture shown are merely examples, and the embodiments of this application are not limited thereto. The network architecture and business scenarios described in the embodiments of this application are for the purpose of more clearly illustrating the technical solutions of the embodiments of this application, and do not constitute a limitation on the technical solutions provided by the embodiments of this application. As those skilled in the art will know, with the evolution of network architecture and the emergence of new business scenarios, the technical solutions provided by the embodiments of this application are also applicable to similar technical problems.

[0133] To facilitate understanding of the embodiments of this application, definitions of technical terms that may appear in the embodiments of this application are given below. The terminology used in the implementation section of this application is only used to explain specific embodiments of this application and is not intended to limit this application.

[0134] (1) Time-frequency resources, including time-domain resources and frequency-domain resources.

[0135] Frequency domain resources refer to one or more consecutive resource elements (REs) distributed in the frequency domain. Consecutive REs in the frequency domain can be called a resource block (RB). An RE is defined as the resource bounded by one symbol in the time domain and one subcarrier in the frequency domain. A subcarrier can be understood as the smallest granularity of frequency domain resources; one RE can be called one subcarrier. For example, an RB in an LTE communication system includes 12 subcarriers, and an RB in an NR communication system also includes 12 subcarriers. As communication systems evolve, the number of subcarriers included in an RB can be other values. An RB is called a physical resource block (PRB) at the physical layer. Frequency domain resource units can include subcarriers, subcarrier spacing (SCS), bandwidth, RBs, RBgroups (RBGs), bandwidth parts (BWPs), component carriers, etc.

[0136] Temporal resources refer to one or more contiguous temporal resource units distributed in the time domain. Temporal resource units may include superframes, radio frames (simply called frames), subframes, slots, sub-slots, mini-slots, symbols, etc., without limitation here. A subframe includes at least one slot, and each slot contains several symbols.

[0137] In this application embodiment, the resource unit can be called a time-frequency unit, which may include REs and time units corresponding to time-domain resource units, such as time slots, symbols, and symbol groups composed of multiple symbols. This application does not limit the number of symbols in a symbol group; it can be a positive integer greater than 1. Symbols can be modulation symbols or orthogonal frequency division multiplexing (OFDM) symbols.

[0138] (2) Reference signal (RS), also known as pilot signal, is a known signal provided by the transmitter to the receiver for channel estimation or channel detection.

[0139] Optionally, the reference signal may include, but is not limited to, at least one of the following: channel state information reference signal (CSI-RS), demodulation reference signal (DMRS), phase tracking reference signal (PT-RS), and sounding reference signal (SRS).

[0140] DMRS can be used for channel estimation to demodulate the corresponding physical channels, such as the Physical Downlink Shared Channel (PDSCH), Physical Uplink Shared Channel (PUSCH), Physical Downlink Control Channel (PDCCH), and Physical Uplink Control Channel (PUCCH). DMRS is a signal known to the receiver. Based on the received data signal and the known DMRS signal, the receiver can obtain the fading characteristics of the wireless channel, i.e., the channel coefficients, which are used to recover the received data signal.

[0141] SRS (Streaming Resource Switch) can be used to evaluate uplink and downlink channel parameters, as well as for uplink beam management and beam switching. SRS resources can be indicated by the number of antenna ports, the number of OFDM symbols, time-domain location, and frequency-domain location. The number of antenna ports for the SRS can be configured to 1, 2, or 4. The number of OFDM symbols for the SRS can be configured to 1, 2, 4, 8, or 12. The time-domain location of the SRS can be the last 6 symbols in a slot, specifically {1, 2, 4} consecutive symbols. The frequency-domain location of the SRS can be related to the BWP (Bandwidth, Window, and Window).

[0142] CSI-RS is used for downlink channel measurement, acquiring downlink channel state information, beam management, radio resource management (RRM) measurement / radio link monitoring (RLM) measurement and fine-grained time-frequency tracking, mobility management, rate matching, etc. PT-RS is used for phase noise tracking and compensation.

[0143] It is understood that PDSCH and PDCCH in the embodiments of this application are merely examples of downlink data channels and downlink control channels. PUSCH and PUCCH in the embodiments of this application are examples of uplink data channels and uplink control channels. In different systems and different scenarios, data channels and control channels may have different names, and the embodiments of this application do not limit this.

[0144] (3) PUCCH is a channel used to carry control signaling from terminal equipment to network equipment. It contains control-related information, such as uplink control information (UCI). PUCCH is divided into two types: long-duration PUCCH, which occupies 4 to 14 OFDM symbols and is transmitted using frequency hopping. DMRS and UCI are carried by different symbols, and OCC spreading can be used in each frequency hopping part to increase capacity; and short-duration PUCCH, which occupies 1 to 2 OFDM symbols. In the frequency domain PRB, information can be carried by sequence, or DMRS and UCI can be transmitted by frequency division using different subcarriers. In a time slot, PUCCH can be transmitted from any location.

[0145] (4) PUSCH is a channel for transmitting data and some control information on terminal equipment. Information carried on the PUSCH is transmitted in units of subframes. In the time domain, DMRS and PUSCH are transmitted on different symbols. The data transmitted on the PUSCH can be uplink shared channel (UL-SCH) data or other data. In the following text, UL-SCH data is sometimes simply referred to as data or uplink data.

[0146] Optionally, the network device sends the time-domain resource configuration (TDRA) of the PUSCH to the terminal device. Correspondingly, the terminal device receives the PUSCH TDRA from the network device. The time-domain resource configuration of the PUSCH may include the time-domain resource parameters of the PUSCH.

[0147] Optionally, the time-domain resource parameters of PUSCH may include at least one of the following: PUSCH repetition type, PUSCH mapping type, PUSCH start symbol S and length L, PUSCH repetition number K, number of slots N for TBoMS (TB processing over multiple slots), and PUSCH slot offset K2.

[0148] The PUSCH repetition types include PUSCH repetition type A and PUSCH repetition type B. PUSCH repetition type A is a slot-level repetition type, where each slot uses the same symbol-level configuration, meaning the start symbol and length of the PUSCH within each slot are consistent. PUSCH repetition type B is a mini-slot-level or symbol-level repetition type, primarily suitable for low-latency URLLC scenarios. For PUSCH repetition type A, the start symbol and length are indicated by a start and length indicator (SLIV). For PUSCH repetition type B, the start symbol and length can be directly indicated.

[0149] The PUSCH mapping type defines the combination of the start symbol and length of the PUSCH resource. There are two PUSCH mapping types: PUSCH Mapping Type A and PUSCH Mapping Type B. PUSCH Mapping Type A defines that the start symbol of the PUSCH resource in the time slot begins from the first OFDM symbol (OFDM symbol 0). PUSCH Mapping Type B defines that the start symbol of the PUSCH resource in the time slot can begin from any symbol position.

[0150] The PUSCH repetition count can be transmitted using either DCI format 0_1 ​​or DCI format 0_2. When using TBoMS to transmit PUSCH, the PUSCH repetition count refers to the repetition count of a single TBoMS. The number of time slots in a TBoMS can also be called multi-slot processing (TB processing over multi-slot), and can be transmitted using either DCI format 0_1 ​​or DCI format 0_2. The PUSCH time slot offset defines the time slot offset of the PUSCH transmission relative to the time slot of the PDCCH that schedules the DCI.

[0151] (5) UCI ​​can include three types of information: Scheduling Request (SR), Hybrid Automatic Repeat Request Acknowledgment (HARQ-ACK) information, and Channel State Information (CSI). The priority of each UCI type can be HARQ-ACK > SR > high-priority CSI > low-priority CSI. In some embodiments, SR can be disregarded, and the priority of the UCI type can be HARQ-ACK > high-priority CSI > low-priority CSI. In this application, CSI can be a CSI report, and HARQ-ACK can be called HARQ-ACK information or HARQ-ACK message. In some embodiments, HARQ-ACK can have different priorities, for example, high-priority HARQ-ACK and low-priority HARQ-ACK.

[0152] SR (Schedule Request) is used to request resources for newly transmitted uplink data (such as UL-SCH data). SR can be a scheduling request for PUCCH, and typically cannot be multiplexed onto PUSCH. HARQ-ACK information can employ HARQ technology. HARQ technology is a technique that combines forward error correction (FEC) and automatic repeat request (ARQ). Its main principle is that redundant information is added at the sending end using FEC, allowing the receiving end to correct some errors. Errors that the receiving end cannot correct are retransmitted.

[0153] CSI reports can be any type of CSI. CSI reports can include CSI part1 reports and CSI part2 reports, etc., without limitation. The payload size of the CSI part1 report is fixed and is used to confirm the information bits of the CSI part2 report; therefore, the CSI part1 report is always transmitted before the CSI part2 report. From a scheduling perspective, CSI reports can include periodic CSI (P-CSI) reports, semi-persistent CSI (SP-CSI) reports (or semi-static CSI reports), and aperiodic CSI (AP-CSI) reports.

[0154] PUCCH supports the reporting of P-CSI and SP-CSI reports, while PUSCH supports the reporting of SP-CSI and AP-CSI reports. HARQ-ACK information can be feedback based on semi-persistent scheduling (SPS), or feedback from PDSCH or PDCCH based on DCI scheduling. For P-CSI reports, network devices can configure time-frequency resources for terminal devices via RRC signaling. The terminal device will send a P-CSI report to the network device through this time-frequency resource every fixed transmission cycle. For SP-CSI reports, network devices can activate them via MAC-CE signaling or DCI. After activation, the terminal device will send an SP-CSI report to the network device through the pre-configured time-frequency resource every fixed transmission cycle. For AP-CSI reports, the network device sends a DCI to the terminal device to trigger the terminal device to send an AP-CSI report to the network device on the specified PUCCH resource. AP-CSI reports can be transmitted via PUCCH, P-CSI reports can be transmitted via PUCCH, and SP-CSI reports can be transmitted via PUSCH or PUCCH.

[0155] The parameters in the CSI report may include the channel quality indicator (CQI), precoding matrix indicator (PMI), CSI reference signal resource indicator (CRI), layer indicator (LI), rank indicator (RI), etc., and are not limited here.

[0156] HARQ-ACK information and CSI reports can be transmitted on PUCCH or PUSCH, meaning that HARQ-ACK information and CSI reports can be multiplexed on PUSCH. If the uplink channels of UCI transmission (such as PUCCH and PUSCH) overlap in the time domain, and UCI needs to be multiplexed onto a certain uplink channel for transmission, the terminal equipment needs to meet the processing delay requirements corresponding to each channel. As stated in Section 9.2.5 of the protocol TS38.213, the conditions for multiplexing HARQ-ACK information and / or CSI require that the earliest symbol S0 of the earliest PUCCH or PUSCH in the group of overlapping PUCCHs and PUSCHs must meet certain timing constraints or timeline conditions before the terminal equipment has time to process the multiplexing of HARQ-ACK information and / or CSI reports in the PUSCH transmission in one or more time slots.

[0157] Different UCI types can correspond to different timeline conditions. Meeting the timeline conditions, as described in protocol TS38.213, means that the time interval between the last symbol of the channel used to schedule PUCCH and / or PUSCH and S0 is greater than or equal to the processing duration corresponding to that type of UCI. For example, the processing duration may include T. proc,1 T proc,2 , wait.

[0158] Among them, T proc,1 This can be defined as the processing time for the PDSCH after the terminal device receives the PUCCH scheduling PUCCH, such as the time required to determine the start position of the PUCCH. pr0c,2 This can be the processing time of the PDCCH after the terminal device receives the PUSCH for scheduled transmission, such as the time required to determine the starting position of the PUSCH. This can be the processing time between S0 and the last symbol of any PDSCH, in the case of HARQ-ACK information corresponding to PDSCH or PDCCH. This can be the processing time between S0 and the last symbol of any PDCCHs that has no PDSCH reception schedule but has corresponding HARQ-ACK feedback, provided that there is HARQ-ACK information corresponding to PDSCH or PDCCH. In the case that there is no AP-CSI report multiplexing in the PUSCH of an overlapping PUCCHs and PUSCHs group, the processing time between S0 and the last symbol of the channel scheduling PUCCHs and / or PUSCHs can be specified. In the case of AP-CSI report multiplexing on PUSCH in a group of overlapping PUCCHs and PUSCHs, the processing time between S0 and the last symbol of the last symbol of the channel scheduling PUCCH and / or PUSCH can be specified.

[0159] The timeline conditions must be met, or as described in protocol TS38.214.5.4, the uplink must begin on the next uplink symbol Z following the nth triggered AP-CSI report. ref The time interval between the end of the last symbol of the CP and the PDCCH that triggered the AP-CSI report is greater than the processing time T. proc,CSI And it requires that the next uplink symbol Z' of the nth triggered AP-CSI report be used. ref The processing time for the CP of (n) ending with the last symbol of the measurement signal is greater than the processing time T′. proc,CSI Among them, the measurement signals can be signals for aperiodic CSI-RS resources used for channel measurement, signals for aperiodic CSI-IM used for interference measurement (IM), and signals for aperiodic NZP CSI-RS used for IM, etc.

[0160] Meeting the timeline conditions, or as described in protocol TS38.214.5.4, when periodic or semi-static CSI-RS, CSI-IM, or SSB are used for channel or interference measurements, the terminal equipment does not expect to send an AP-CSI report based on the measurement of the channel or interference on the CSI-RS, CSI-IM, or SSB received within Z' symbols prior to the transmission time of the first OFDM symbol. In other words, the processing time interval between the starting symbol of the AP-CSI report and the last OFDM symbol of the CSI-RS, CSI-IM, or SSB used for channel or interference measurements must be greater than the duration corresponding to Z' symbols. Here, Z' corresponds to the delay requirement defined in 5.4.

[0161] If the timeline conditions are met, or as described in section 6.1.3.x of protocol TS38.321, when the terminal device transmits a PUCCH containing HARQ-ACK information in time slot n, the indicated SP-CSI report setting should be from time slot n. The first time slot after the PUCCH begins application. Here, μ is the subcarrier configuration of the PUCCH. It is the number of subframes included in a time slot.

[0162] If the timeline conditions are met, or as described in protocol TS38.214, the CSI trigger state mapping is from... It begins in the first time slot after, where μ is the subcarrier configuration of PUCCH. k is the number of subframes included in a time slot. In the frequency offset range of 1 and FR2-NTN, k mac =0,k mac K-MAC is provided; if K-MAC is not available, then k mac =0.

[0163] The above are some of the existing timeline conditions for different CSI report transmission requirements. It should be understood that timeline conditions not described in this application may also be included, which will not be elaborated here.

[0164] The UCI mapping process has two cases. The first case is when the HARQ-ACK bits are less than or equal to 2, which is suitable for the puncturing method. The second case is when the HARQ-ACK bits are greater than 2, which is suitable for the rate matching method.

[0165] (6) Rate matching is performed individually for each code block. First, a fixed number of systematic bits are punctured. Depending on the code block size, the proportion of punctured systematic bits can be relatively high, up to 1 / 3 of the systematic bits. The remaining coded bits are written into a circular buffer, starting with the unpunctured systematic bits and then continuing with the parity bits. The selection of bits to be transmitted is based on the required number of bits read from the circular buffer, and the specific set of bits to be transmitted depends on the redundancy version (RV) – corresponding to different starting positions in the circular buffer. Therefore, by selecting different redundancy versions, different sets of coded bits representing the same set of information bits can be generated, which is used when implementing HARQ with incremental redundancy.

[0166] A PUSCH can carry UL-SCH without carrying UCI, or it can carry UCI without carrying UL-SCH, or it can carry both UL-SCH and UCI. When a PUSCH carries both UCI and UL-SCH, the terminal device can multiplex the encoded UCI with the UL-SCH using rate matching and then map it onto the PUSCH. Alternatively, it can map the encoded UCI onto the PUSCH using a UL-SCH that has already been mapped onto the PUSCH via puncturing, thus achieving multiplexing with the UL-SCH. When a PUSCH carries UCI but not UL-SCH, the terminal device maps the encoded UCI onto the PUSCH.

[0167] This application does not limit the resource size occupied by UCI and UL-SCH. This resource size can be calculated from the occupied resource size (such as the number of REs, the number of symbols, etc.), the number of bits occupied, MCS, etc. When UCI is HARQ-ACK information, the resource size occupied by UCI can satisfy the following formula (1):

[0168]

[0169] Among them, Q′ ACK The number of physical resources occupied by HARQ-ACK messages, O ACK L represents the number of bits (or number of bits, i.e., the size of the HARQ-ACK payload) occupied by the HARQ-ACK information. ACK This represents the number of bits in the cyclic redundancy check (CRC) of the HARQ-ACK message. The PUSCH bias value can be viewed as the ratio of the bit rate of other information on the PUSCH (such as UL-SCH) to the bit rate of the UCI. It is notified by the network device and is a number greater than 0. This is used in calculating Q′. ACK hour, This is the bias value for the HARQ-ACK information.

[0170] C represents the transport block size (TBS) corresponding to the UL-SCH on the PUSCH. UL-SCH K is the number of code blocks included in the UL-SCH on the PUSCH. r Let r be the number of bits in the r-th code block in the UL-SCH on the PUSCH. This refers to the number of physical resources available on the PUSCH to support UCI. The number of physical resources available for carrying UCI on the l-th time-domain symbol of the PUSCH. This represents the total number of time-domain symbols on the PUSCH (including the number of symbols carrying DMRS). When l represents the number of time-domain symbols carrying DMRS, When l is a time-domain symbol that does not carry DMRS, The total number of physical resources (i.e., the number of subcarriers) included in symbol l for PUSCH. l0 represents the number of physical resources occupied by the phase tracking reference signal (PT-RS) on symbol l of the PUSCH. α is the scalling factor for the resources, with possible values ​​of 0.5, 0.65, 0.8, and 1. l0 is the first time-domain symbol on the PUSCH that does not carry a DMRS after the first DMRS symbol.

[0171] The input bit sequence used for rate matching is d r0 ,dr1 ,d r2 ,d r3 ,..., Where r is the number of code blocks, and N r This refers to the number of encoded bits in code block number r. Rate matching is performed according to clause 5.4.1 by setting I. BIL =1 and rate matching are used for execution. Rate matching is performed on the HARQ-ACK information, and the resulting output sequence length is: Among them, C UCI This is the number of UCI code blocks determined according to section 5.2.1. E UCI =N L ·Q′ ACK ·Q m , where N L This is the transport layer number of PUSCH. Q m It is the modulation order of PUSCH.

[0172] When UCI reports as CSI part 1, the physical resources occupied by UCI can satisfy the following formula (2):

[0173]

[0174] Among them, Q′ CSI-1 For the amount of physical resources occupied by the CSI Part 1 report, O CSI-1 For the number of bits reported in CSI part 1 (i.e., the payload size of CSI part 1), L CSI-1 This is the number of CRC bits reported in CSI Part 1, Q′ ACK This refers to the amount of physical resources used for or potentially used for transmitting HARQ-ACK information. Physical resources used for transmitting HARQ-ACK information refer to the reserved resources allocated for HARQ-ACK information transmission under certain conditions (such as when the number of bits occupied by HARQ-ACK information does not exceed 2 bits). The terminal device may actually use these reserved resources to transmit HARQ-ACK information, or it may not use these reserved resources to transmit HARQ-ACK information (for example, mapping UL-SCH on these reserved resources).

[0175] Rate matching of the CSI part 1 report yields an output sequence of length . Among them, E UCI =N L ·Q′ CSI-1 ·Q m C UCI NL Q′ CSI-1 and Q m Refer to the foregoing; further details will not be repeated here. In calculating Q′... CSI-1 hour, This is the bias value reported in CSI Part 1.

[0176] When UCI reports as CSI part 2, the physical resources occupied by UCI can satisfy the following formula (3):

[0177]

[0178] Among them, Q′ CSI-2 O represents the amount of physical resources occupied by the UCI. CSI-2 L is the number of bits reported in CSI Part 2 (i.e., the payload size reported in CSI Part 2). CSI-2 This refers to the CRC bit count reported in CSI Part 2. Other references are as described above and will not be repeated here. In calculating Q′... CSI-1 hour,

[0179] Rate matching of the CSI part 1 report yields an output sequence of length . Among them, C UCI This is the number of UCI code blocks determined according to section 5.2.1. E UCI =N L ·Q′ CsI-2 ·Q m , where C UCI N L Q m Q′ CSI-2 and Q m Refer to the foregoing; further details will not be repeated here. In calculating Q′... CSI-2 hour, This is the bias value reported in CSI Part 2.

[0180] The formulas for the physical resources occupied by UCI mentioned above are merely examples. They can also be determined using formulas not shown in this document, such as the relevant formulas in TS38.212. For example, when UCI is a CSI part 1 report, the physical resources occupied by UCI can satisfy formula (4), etc., which will not be described in detail here.

[0181]

[0182] Where R is the code rate of PUSCH. Other parameters are as described above and will not be repeated here.

[0183] The value can be found in the second column of Table 9.3-1 in protocol TS38.213. and Refer to the second column of Table 9.3-2 in protocol TS38.213. It can be seen that the offset value needs to be accurate to three decimal places. Transmitting these offset values ​​directly in RRC signaling or DCI would consume a significant amount of resources. Therefore, TS38.213 creates a series of indexes and provides the relationship between index values ​​and offset values. The offset value selection process is as follows: The index value is determined using the RRC signaling configuration in TS38.331, such as PUSCH-Config, ConfiguredGrantConfig, and BetaOffsets signaling; then, the corresponding offset value is found by querying the table in TS38.213.

[0184] Please see Figure 2 , Figure 2 This is a schematic diagram illustrating uplink information carried on a PUSCH according to an embodiment of this application. Figure 2 As shown, the uplink information includes UCI and UL-SCH data. UCI includes HARQ-ACK information, CSI part 1 reports, and CSI part 2 reports. PUSCH occupies one time slot (including 14 OFDM symbols) and 12 REs. DMRS is configured on the OFDM symbols corresponding to OS#2 and OS#11 in this time slot. HARQ-ACK information is mapped to the two REs corresponding to SC#0 and SC#6 of the OFDM symbol corresponding to OS#3. CSI part 1 reports are mapped to the REs corresponding to SC#0 to SC#11 of each symbol in OS#0 and OS#1, respectively. CSI part 2 reports are mapped to the REs (excluding the REs occupied by HARQ-ACK information) in SC#0 to SC#11 of OS#3 (a total of 10), and the REs corresponding to SC#0 and SC#6 of the OFDM symbol corresponding to OS#4 (a total of 2). The remaining unused time domain resources are used to transmit UL-SCH data.

[0185] (7) Orthogonal Cover Code (OCC), represented in sequence form, can also be called OCC sequence, coded sequence, or orthogonal sequence. This application does not limit the type of OCC sequence, which can be a Walsh sequence, a DFT sequence, or other sequences, such as sequence A, sequence B, ZC sequence, etc.

[0186] In this embodiment, the code length L of the OCC sequence refers to the number of values ​​in the OCC sequence. The values ​​in the OCC sequence may be called OCC elements, and the code length may be called the spreading factor or spreading frequency factor, or simply the OCC sequence length. Spreading is also called block spreading (or block-like spreading), and when spread in the frequency domain, it can also be called spread spectrum. This application does not limit the size of the code length; for example, 2, 4, 8, etc.

[0187] The basic principle of OCC is to multiply the information to be transmitted by the terminal device with the OCC elements in the terminal device's OCC sequence, ensuring that the multiplied information is orthogonal in the code domain, thus achieving non-interference in information transmission between terminal devices. In this way, different terminal devices can reuse the same time-frequency resources, and there is almost no code rate loss for a given number of terminal devices. Therefore, it is commonly used in scenarios that enhance system capacity and increase the transmission rate of terminal devices.

[0188] Network devices can configure different OCC sequences in the same orthogonal matrix for multiple terminal devices using the same time-frequency resources. An orthogonal matrix includes multiple mutually orthogonal OCC sequences. For example, the orthogonal matrix of OCCs includes matrices A, B, and C as shown below. In matrix A, the OCC sequences include W1 assigned to terminal A and W2 assigned to terminal B. In matrix B, the OCC sequences are assigned to W3 for terminal C, W4 for terminal D, W5 for terminal E, and W6 for terminal F. In matrix C, the OCC sequences are assigned to W3 for terminal C, W4 for terminal D, W7 for terminal G, and W8 for terminal H. Where W1 = [1 1], W2 = [1 -1]. W3 = [1 1 1 1], W4 = [1 -1 1 -1], W5 = [1 1 -1 -1], W6 = [1 -1 -1 1]. W7 = [1 -j -1 j], W8 = [1 j -1 -j].

[0189]

[0190] Optionally, when the code length is 2, the DFT sequence can be the same as the Walsh sequence, as shown in matrix A.

[0191] Optionally, when the code length is 4, the DFT sequence can be different from the Walsh sequence. For example, the DFT sequence can be as shown in matrix B, and the Walsh sequence can be as shown in matrix C.

[0192] Taking matrix A as an example, if terminal A transmits information X and terminal B transmits information Y, then multiplying X by the OCC elements in W1 yields X and X, and multiplying Y by the OCC elements in W2 yields Y and -Y. Therefore, terminals A and B transmit the information obtained by multiplying by the OCC elements on the same time-frequency resources, so the information received by the receiving side can be X+Y and XY, respectively. The receiving side can multiply the received information by the OCC elements in W1 and then add them together to obtain 2X, thus obtaining the data transmitted by terminal A. The receiving side can also multiply the received information by the OCC elements in W2 and then add them together to obtain 2Y, thus obtaining the data transmitted by terminal B.

[0193] In the embodiments of this application, the use of OCC can be described as using an OCC sequence, or as performing OCC extension, or as performing code division extension or code division multiplexing, or even as performing OCC extension and repetition. The information to be transmitted by different terminal devices is multiplied by different OCC elements in their configured OCC sequences. That is, multiplying the information to be transmitted by each terminal device by different OCC elements in its configured OCC sequence can achieve code division multiplexing or OCC extension. PUSCH undergoing OCC sequence extension can actually be the information carried on the PUSCH undergoing OCC sequence extension, for example, multiplying the information carried on the PUSCH by the OCC element corresponding to the time unit occupied by that information in the OCC sequence.

[0194] In this document, it is sometimes described as code division multiplexing or OCC extension of resources based on OCC sequences, or it can be described as code division multiplexing or OCC extension of resources based on OCC sequences. In reality, it refers to code division multiplexing or OCC extension of information transmitted on resources based on OCC sequences. Code division multiplexing or OCC extension of information based on OCC sequences means multiplying the information by different elements in the OCC sequence. Specifically, the OCC elements corresponding to resource units in the OCC sequence can be determined first, and the information carried on each resource unit can be multiplied by the corresponding OCC element. These resource units can be resource units obtained by extending the resource units occupied by the information according to the OCC code length, where the extended resource units are integer multiples of the OCC code length, or multiple resource units occupied by the information can be used as the resource units required for extension. In the embodiments of this application, the information may include data and / or signaling.

[0195] Currently, OCCs can be categorized by resource unit into inter-slot OCCs (OCC across slots), inter-symbol OCCs (OCC across OFDM symbols), inter-symbol group OCCs (OCC across OFDM symbols), and intra-symbol OCCs (OCC within an OFDM symbol). Inter-symbol OCCs and inter-symbol group OCCs can be collectively referred to as multiple inter-symbol(s) OCCs.

[0196] OCCs can be categorized by repetition type into inter-repetition OCCs for PUSCH repetition type A and inter-repetition OCCs for PUSCH repetition type B. The inter-repetition OCC for PUSCH repetition type A is an OCC extension of the slot-level PUSCH, with the extended information being slot-level information. Therefore, the inter-repetition OCC for PUSCH repetition type A can be referred to as an inter-slot OCC, or simply an inter-slot OCC for PUSCH repetition type A. The inter-repetition OCC of PUSCH repetition type B is at the min-slot level or symbol level. The information extended by the inter-symbol OCC is at the min-slot level, and the information extended by the inter-symbol OCC is at the symbol level. That is, the inter-repetition OCC of PUSCH repetition type B can be called inter-symbol OCC or inter-symbol OCC, or it can be called inter-symbol OCC with PUSCH repetition type B.

[0197] The resource units (or time-domain resource units or time units) of inter-slot OCC, inter-repetition OCC of PUSCH repetition type A, and inter-repetition OCC of PUSCH repetition type B can be time slots. The resource units of inter-symbol OCC can be symbols, the resource units of inter-symbol OCC can be symbol groups (multiple symbols), and the resource units of intra-symbol OCC can be REs. In the embodiments of this application, the OCC element corresponding to the resource unit refers to the OCC element multiplied when the information carried on the resource unit is performed during OCC extension. That is, inter-slot OCC extension is multiplying the information carried on each time slot in multiple time slots with the OCC element corresponding to that time slot. Inter-symbol OCC extension is multiplying the information carried on each symbol in multiple symbols with the OCC element corresponding to that symbol. Inter-symbol OCC extension is multiplying the information carried on each symbol group in multiple symbol groups with the OCC element corresponding to that symbol group. Intra-symbol OCC extension is multiplying the information carried on each RE in multiple REs with the OCC element corresponding to that RE.

[0198] For example, please refer to Figure 3A or Figure 3B , Figure 3A This is a schematic diagram illustrating the principle of inter-slot OCC extension provided in an embodiment of this application. Figure 3B This is a schematic diagram illustrating the principle of inter-symbol OCC extension provided in an embodiment of this application. For example... Figure 3A As shown, the OCC sequence includes two values, w(1) and w(2). If the OCC sequence is W1 as in the example above, then both w(1) and w(2) can be 1. If the OCC sequence is W2 as in the example above, then w(1) can be [1 1], and w(2) can be [1-1]. Figure 3A In the diagram, the horizontal axis represents the time domain, and there are two time slots, slot #0 and slot #1. Slot #0 can be used as the time slot before expansion, and slot #1 can be used as the time slot obtained by slot #0 to achieve inter-slot OCC expansion. Alternatively, both slot #0 and slot #1 can be used as the time slots required for expansion. Each time slot in slot #0 and slot #1 includes two OFDM symbols occupied by DMRS. OFDM symbols with the same sequence number indicate that the information carried on these OFDM symbols is the same. The information carried on the OFDM symbols in slot #0 other than the OFDM symbols occupied by DMRS can be multiplied by w(1), and the information carried on the OFDM symbols in slot #1 other than the OFDM symbols occupied by DMRS can be multiplied by w(2). Thus, inter-slot OCC expansion can be achieved by multiplying different OCC elements in the OCC sequence with the information carried on the OFDM symbols in different time slots other than the OFDM symbols occupied by DMRS.

[0199] exist Figure 3B In the diagram, the horizontal axis represents the time domain, and the vertical axis represents the frequency domain. Figure 3B Using an OFDM symbol, such as OS#1, M symb =6, with an OCC length of 2 for example. The OCC sequence includes two values, w(1) and w(2). Figure 3B As shown, the frequency domain resources configured on this OFDM symbol are 6 subcarriers. After expansion, the OFDM symbol includes 12 subcarriers, which can be divided into 2 RE groups. Alternatively, the 12 subcarriers configured on the OFDM symbol can be used as the subcarriers required for expansion, and these 12 subcarriers can be divided into 2 RE groups. For example, SC#0-SC#5 can be used as the first RE group, and SC#0-SC#5 can be used as the second RE group. The information carried on the subcarriers with the same sequence number in each RE group is multiplied by the same OCC element. The information carried on each subcarrier can be multiplied by the OCC element corresponding to the RE group. For example, the information carried on each subcarrier in the first RE group can be multiplied by w(2), and the information carried on each subcarrier in the second RE group can be multiplied by w(1). In this way, by multiplying the information carried on the subcarriers by different OCC elements in the OCC sequence, intra-symbol OCC expansion can be achieved.

[0200] Inter-symbol OCC spreading and inter-symbol group OCC spreading, as well as inter-repetition OCC for PUSCH repetition type A and inter-repetition OCC for PUSCH repetition type B, can be described in the same way as inter-slot OCC spreading, and will not be repeated here. The signal processing flow for inter-slot OCC spreading, inter-symbol OCC spreading, and inter-symbol group OCC spreading can be executed after DFT, while the signal processing flow for intra-symbol OCC spreading can be executed before DFT. That is to say, after DFT processing, OCC spreading can be performed through at least one of inter-slot OCC spreading, inter-symbol OCC spreading, and inter-symbol group OCC spreading, enabling repeated transmission and spreading of data on different time slots or symbols. Alternatively, intra-symbol OCC spreading can be performed on the modulated data, followed by DFT on the intra-symbol OCC-spread data, enabling repeated transmission and spreading of data on different REs of the same symbol.

[0201] The information obtained after the DFT-enhanced intrasymmetric OCC expansion (the fourth complex numerical symbol block) typically exhibits a comb-like structure. Please refer to [link / reference]. Figure 3B , Figure 3B The orthogonal sequence in the code has a code length of 2, which can be used to implement intra-symbol OCC extension for two terminal devices (such as UE#1 and UE#2). After intra-symbol OCC extension is performed on UE#1 and UE#2, and after DFT, the information of UE#1 can be as follows: Figure 3BThe information transmitted by UE#2 can be transmitted on the subcarriers corresponding to the vertical squares shown (such as SC#1, SC#3, SC#5, SC#7, SC#9, and SC#11). Figure 3B Transmissions are carried out on the subcarriers corresponding to the cross squares shown (such as SC#0, SC#2, SC#4, SC#6, SC#8 and SC#10).

[0202] An OCC sequence with L resource units can be called an OCC group. Each resource unit in an OCC group corresponds to an OCC element in its OCC sequence. For example, an OCC group for inter-slot OCC extension corresponds to L time slots, and each of the L time slots has a different OCC element in its corresponding OCC sequence. As another example, an OCC group for intra-symbol OCC extension corresponds to L REs, and each of the L REs has a different OCC element in its corresponding OCC sequence.

[0203] When using OCC for uplink transmission on a PUSCH, if the time-frequency resources occupied by the PUSCH overlap with the time-domain resources occupied by the PUCCH, and the information carried on the PUCCH occupies a large amount of resources, it is highly likely that the network side will be unable to correctly receive the uplink data, leading to decoding failure. Furthermore, referring to Table 9.3-2 in protocol TS38.213, it can be found that... and If the corresponding values ​​are all greater than 1, it may not be possible to reduce the resource usage of the CSI report.

[0204] This application proposes a communication method that can reduce the resource consumption of UCI carried on the PUSCH. By transmitting information extended with an OCC sequence, system capacity can be improved, which is beneficial for the network side to correctly receive data.

[0205] The communication method provided in the embodiments of this application will be described in detail below. The communication devices involved in this communication method may include a first communication device and a second communication device. The first communication device may be a terminal as a final product, such as the various terminal devices mentioned above, or a component or part with terminal functions, or a circuit or chip (such as a modem chip, also known as a baseband chip, or a system-on-a-chip (SoC) chip or system-in-package (SIP) chip containing a modem core), a chip system, or a processor that can be applied to the terminal to perform communication functions, or a logic node, logic module, or software that can implement all or part of the terminal functions. The second communication device may be a network device as a final product, such as the various network devices mentioned above, or a component or part with network device functions, or a communication chip (such as a processor, baseband chip, or chip system) that can be applied to the network device. The system architecture of the terminal device and the network device can be referred to Figure 1A or Figure 1B The description will not be repeated here.

[0206] Optionally, the communication method is applicable to NTN communication scenarios, meaning that the second communication device in the method can be a non-terrestrial network device.

[0207] Optionally, the communication method is suitable for coverage enhancement scenarios, in which coverage enhancement technologies such as retransmission, TBoMS, and DMRS bundling can be used.

[0208] Please refer to Figure 4 , Figure 4 This is a flowchart illustrating a communication method provided in an embodiment of this application. For example... Figure 4 As shown, the method includes, but is not limited to, the following steps:

[0209] S401, The first communication device determines a first parameter of the CSI report, the first parameter being less than or equal to 1, and the first parameter of the CSI report is used to scale the resource size occupied by the CSI report.

[0210] Accordingly, the second communication device determines the first parameter of the CSI report.

[0211] In the embodiments of this application, the CSI report can be a CSI part1 report or a CSI part2 report, or it can be other reports, such as an AP-CSI report, an SPS-CSI report, a P-CSI report, etc., which are not limited here. The content of the CSI report can refer to the foregoing, and will not be repeated here. The CSI report can also be a CSI.

[0212] The form of the first parameter in this application is not limited. In some possible implementations, the first parameter may include a bias value.

[0213] The bias value can be referenced as beta_offset, for example, in the CSI part 1 report. CSIpart2 report The bias value of the CSI report involved in this application can be understood as a newly introduced bias value compared to the bias values ​​greater than 1 in the prior art. In some possible implementations, the bias value of the CSI report can be determined by the index of the CSI report. It is understood that indicating the bias value by index can save signaling overhead.

[0214] For example, please refer to Table 1 or Table 2. Table 1 can be an improvement on existing technology; for instance, the bias values ​​corresponding to indices 21 to 26 in Table 9.3-2 can be modified to values ​​less than or equal to 1. The bias values ​​corresponding to indices 21 to 26 can be the same as some of the bias values ​​in the HARQ-ACK information. Thus, the bias values ​​of the CSI report can be configured based on the bias values ​​less than or equal to 1 in the HARQ-ACK information without introducing new values. Table 2 can be understood as a new table where the bias values ​​are less than or equal to 1. These bias values ​​can also come from the bias values ​​in the HARQ-ACK information, or they can be other values. Tables 1 and 2... for index, for The index.

[0215] Table 1

[0216]

[0217]

[0218] Table 2

[0219]

[0220] In this embodiment, the bias value of the CSI report can be as shown in Table 1 or Table 2, or it may not be as shown in Table 1 and Table 2. That is, the bias value of the CSI report can be the value shown in Table 1 or Table 2, or it may not be the value shown in Table 1 and Table 2. Alternatively, it can be understood that the index of the newly introduced CSI report may not correspond to the bias value in Table 1 or Table 2. For example, the bias value of the CSI report can be 0.3, etc. Another example is that the bias value corresponding to index 0 can be 1, or it can be 0.5, etc. The reserved fields in Table 1 and Table 2 can correspond to bias values ​​greater than, less than, or equal to 1, without limitation. Table 2 can be understood as a table expanded using OCC sequences, and the bias values ​​in this table can be less than or equal to 1. That is, when expanding using OCC sequences, Table 2 takes effect, or the bias values ​​less than or equal to 1 in Table 1 take effect, thereby reducing the resource size occupied by the CSI report when using a bias value less than 1. Otherwise, a bias value greater than 1 can be used.

[0221] In this application, an index or index value is used as an example. In practice, the first parameter and / or the second parameter, which will be described later, can also be indicated by other forms of information (serial number, etc.).

[0222] This application does not limit the magnitude of the bias value. In other possible implementations, the bias value of the CSI report may be between 0.1 and 1, or between 0 and 1, or between 0.05 and 1, etc. It is understood that when the bias value of the CSI report is less than 1, the resource size occupied by the CSI report can be reduced, thereby reducing the impact on the data carried on the PUSCH multiplexed by the CSI report, which is beneficial for the second communication device to receive correct data.

[0223] In this embodiment, the UCI multiplexed onto the PUSCH may include HARQ-ACK information and / or CSI reports, but may not include SR. In some possible implementations, the bias value of the newly introduced HARQ-ACK information may also be a new numerical value, for example, a value less than or equal to 1. For example, the bias value of the HARQ-ACK information may be greater than or equal to 0.1 and less than or equal to 1; or the bias value of the HARQ-ACK information may be greater than or equal to 0.05 and less than or equal to 1; or the HARQ-ACK information may be a positive number less than or equal to 1, etc. The "equal to" in the above examples is only an example and may not be equal to.

[0224] In some possible implementations, the bias values ​​of the newly introduced HARQ-ACK information and / or CSI reports, after mapping and coding, will not cause an increase in the original modulation order of the UCI when the first communication device transmits uplink information. Alternatively, the bias values ​​of the newly introduced HARQ-ACK information and / or CSI reports, after mapping and coding, will not cause the modulation order of the UCI to exceed a first threshold when the first communication device transmits uplink information, or will not cause the transformed or increased value of the modulation order of the UCI to exceed the first threshold when the first communication device transmits uplink data. Alternatively, the bias values ​​of the newly introduced HARQ-ACK information and / or CSI reports, after mapping and coding, will not cause the increase in the code rate of the UCI when the first communication device transmits uplink information to exceed the first threshold.

[0225] The first threshold can be predetermined by the protocol or configured by the network side. For example, the first threshold can be determined by at least one configuration information from DCI, RRC signaling, and MAC CE signaling. Any two of the first thresholds—the first threshold compared with the increase in code rate, the first threshold compared with the increase in modulation order, and the first threshold compared with the change in modulation order—can be equal or unequal, and this is not limited here.

[0226] It is understood that after the HARQ-ACK information and / or CSI report are mapped according to the newly introduced bias value, the modulation order remains unchanged, or the increase in code rate and / or modulation order does not exceed the first threshold, which is beneficial for the second communication device to decode and obtain the corresponding information. In some other feasible implementations, the bias value of the HARQ-ACK information and / or CSI report can be greater than 1. If the bias value of the HARQ-ACK information and / or CSI report is greater than 1, and other first parameters, such as the scaling factor described later, are less than or equal to 1, then the subsequent step S402 can be executed. If the bias value of the HARQ-ACK information and / or CSI report is greater than 1, and other first parameters are also greater than 1, then step S402 can be omitted, or other limiting conditions can be determined, such as the resource size occupied by PUCCH or UCI being less than or equal to the second threshold, and step S402 can also be executed, which is not limited here.

[0227] The resource size occupied by UCI can be the total number of resource units occupied by UCI, the total number of bits occupied by UCI, or the length of the sequence output after rate matching by UCI. Alternatively, the resource size occupied by UCI can be the resource size occupied by CSI reports in UCI, and / or the resource size occupied by HARQ-ACK information, etc. The resource size occupied by UCI may exclude the resource size occupied by SR. Specifically, the resource size can be the number of resource units occupied by HARQ-ACK information and / or CSI reports, or the number of bits occupied by HARQ-ACK information and / or CSI reports, or the length of the sequence output after rate matching by HARQ-ACK information and / or CSI reports. Alternatively, it can be the sum of the resource sizes occupied by the above information and cyclic redundancy check (CRC), etc. Resource units can be symbols or REs, etc., and symbols can be modulation symbols or OFDM symbols, etc., without limitation. CRC can be the CRC of all information in UCI, or the CRC of one or more information in UCI, such as the CRC of HARQ-ACK information, or the CRC of CSI reports. The CRC reported by CSI can include the CRC reported by CSI part 1, or the CRC reported by CSI part 2, or the CRC reported by both CSI part 1 and CSI part 2. It can be understood that if the resource size occupied by UCI is less than or equal to the second threshold, it indicates that the resource occupied by UCI is relatively small, and its impact on the data carried on the PUSCH after UCI multiplexing is minimal, which is beneficial for the second communication device to receive correct data.

[0228] This application does not limit the second threshold; the second threshold compared with the resource size of each type of information in the UCI may be equal to or different from the second threshold. The second threshold may be predetermined by the protocol or configured by the network side. For example, the second threshold may be determined by at least one of the configuration information of DCI, RRC signaling, and MAC CE signaling.

[0229] It should be noted that this application uses a first parameter less than or equal to 1 as an example. In practice, if the first parameter is equal to 1, step S402 may not be executed. Similarly, if the parameter is equal to a second threshold, step S402 may not be executed.

[0230] In some possible implementations, the method may further include: a first communication device determining a second parameter of the HARQ-ACK information. Correspondingly, a second communication device determines the second parameter of the HARQ-ACK information. The second parameter is used to scale the resource size occupied by the HARQ-ACK information. The second parameter of the HARQ-ACK information can refer to the description of the first parameter and is a bias value and / or scaling factor for the HARQ-ACK information. The bias value of the HARQ-ACK information can be a value added based on Table 9.3-1 in protocol TS38.213, for example, a value less than or equal to 1, such as 0.05, 0.5, etc. In this way, the resource size occupied by the HARQ-ACK information can be reduced.

[0231] The second parameter of the HARQ-ACK information may be equal to or different from the first parameter of the CSI report. When the second parameter of the HARQ-ACK information is equal to the first parameter of the CSI report, the network side can send only one configuration message to indicate the corresponding values ​​of the first and second parameters, which can save signaling overhead.

[0232] In some possible implementations, the first parameter and / or the second parameter may include a scaling factor.

[0233] The scaling factor can include the aforementioned α, or it can be a new parameter, such as ε. ε can be a scaling factor for CSI reports, or it can be a scaling factor for other information. In some possible implementations, the scaling factor can be a scaling factor for each type in UCI, such as a common scaling factor. That is, the scaling factor can scale the resource size occupied by each type in UCI, or scale the resource size occupied by one type. For example, CSI reports and HARQ-ACK information may correspond to the same or different scaling factors.

[0234] This application does not limit the size of the scaling factor. The scaling factor can be less than 0.5, or it can be less than or equal to 0.5, and at least one of 0.65, 0.8, and 1, or it can be less than or equal to 1. Among these, 0.5, 0.65, 0.8, and 1 can be values ​​of α defined in existing technologies (such as protocol TS38.331). When the scaling factor of UCI is less than 0.5, the resource size occupied by each piece of information in UCI can be further reduced, such as the resource size occupied by HARQ-ACK information and CSI reports. This application also does not limit the size of the bias value less than 0.5, for example, 0.1, 0.05, etc.

[0235] It is understandable that when the scaling factor for each piece of information in UCI is less than 1, the resource size occupied by UCI can be reduced. For example, when the scaling factor for CSI reports and / or HARQ-ACK information is less than 1, the resource size occupied by CSI reports and / or HARQ-ACK information can be reduced, thereby reducing the impact on the OCC-extended data on the PUSCH after multiplexing CSI and / or HARQ-ACK information, which is beneficial for the second communication device to receive correct data. When the scaling factor of CSI reports is equal to the scaling factor of other information (such as HARQ-ACK information), that is, when the scaling factor is common information applicable to multiple pieces of information, the network side can configure only one scaling factor, thereby reducing signaling overhead. When the scaling factor of CSI reports is different from the scaling factors of other information, the scaling factor can be understood as dedicated information, and the network side needs to configure the scaling factor for each piece of information to ensure the flexibility of scaling factor settings.

[0236] In the embodiments of this application, the first parameter and / or the second parameter can be a bias value and / or a scaling factor. That is, the first parameter and / or the second parameter can be a bias value and a scaling factor, or it can be a bias value instead of a scaling factor, or it can be a scaling factor instead of a bias value. The first parameter and / or the second parameter may also include other information or other forms of representation, i.e., not through... α, ε, etc., represent the first parameter and / or the second parameter. For example, the first parameter of the CSI report can be indicated by the index of the CSI report, and the second parameter of the HARQ-ACK information can be indicated by the index of the HARQ-ACK information.

[0237] It is understandable that when both the UCI bias value and scaling factor are less than 1, the resource size occupied by UCI can be reduced. For example, the resource size occupied by CSI reports and / or HARQ-ACK information can be reduced, thereby reducing the impact on the OCC-extended data on the PUSCH after CSI multiplexing, which is beneficial for the second communication device to receive correct data.

[0238] In some possible implementations, the first parameter and / or the second parameter are activated when using OCC sequence extension. That is, when using OCC sequence extension for the CSI report, the first parameter of the CSI report, or the aforementioned Table 1 or Table 2, or subsequent tables, may be effective. When not using OCC sequence extension for the CSI report, the first parameter of the CSI report may be less than or equal to 1, or greater than 1, and may refer to Table 9.3-2 in protocol TS38.213, or to the aforementioned Tables 1 and 2, and subsequent tables, etc., without limitation. Similarly, the second parameter may also be activated when using OCC sequence extension. That is, when using OCC sequence extension for HARQ-ACK information, the second parameter of the HARQ-ACK information may be effective. When not using OCC sequence extension for HARQ-ACK information, the HARQ-ACK information may be less than or equal to 1, or greater than 1, and may refer to Table 9.3-3 or Table 9.3-3A in protocol TS38.213, or not refer to subsequent tables, etc., without limitation.

[0239] In this embodiment, the first parameter and / or the second parameter can be numerical values ​​agreed upon in the protocol, or they can be data configured on the network side. The first parameter and / or the second parameter configured on the network side can be determined by at least one of DCI, RRC signaling, and MAC CE signaling. For example, the network side can indicate Table 1 or Table 2 and indicate the index value of the CSI report through configuration information, and the bias value of the CSI report can be determined through this index value. In this embodiment, the bias value of the HARQ-ACK information can also be indicated by the index value of the HARQ-ACK information.

[0240] In some possible implementations, the first parameter and / or the second parameter are related to the parameters in the DCI.

[0241] The parameters in the DCI may include an indicator value for the bias value (such as a beta_offset indicator). The indicator value for the bias value can be information from DCI format 0_1, DCI format 0_2, DCI format 0_3, etc., used to determine the index or numerical value of the bias value. Please refer to Table 3 or Table 4 for a mapping relationship between the indicator value for the bias value and the scaling factor provided in an embodiment of this application.

[0242] Table 3

[0243]

[0244] Table 4

[0245]

[0246] Among them, 1 st The offset index provided by higher layers can represent the first set of indices configured on the network side. nd The offset index provided by higher layers can represent the second set of indexes configured on the network side, and so on. Each set of indexes can include at least one of the following: the index of HARQ-ACK information, the index of CSI part1 report, the index of CSI part2 report, etc. This application does not limit the number of sets of indexes for the offset values ​​configured on the network side; it can be 2 sets or 4 sets, as shown in Table 3 or Table 4.

[0247] Table 3 can be an improvement on table 9.3-3 in protocol TS38.213, and Table 4 can be an improvement on table 9.3-3A in protocol TS38.213. That is, a scaling factor can be added to the existing mapping relationship between the bias value indicator and the bias value index, so that the bias value indicator can be used to determine the scaling factor. This scaling factor can be the scaling factor activated when using OCC sequence extension, for example, scale factor under OCC. In other words, when using OCC sequence extension for CSI reports and / or HARQ-ACK information, the scaling factor shown in Table 3 or Table 4 can be used to determine the resource size occupied by CSI reports and / or HARQ-ACK information.

[0248] In this embodiment of the application, the scaling factors corresponding to the CSI report and / or HARQ-ACK information are taken as an example to be equal. In fact, the scaling factors corresponding to the CSI report and / or HARQ-ACK information may be unequal.

[0249] Tables 3 and 4 are merely examples. The scaling factor corresponding to the bias value indication can be determined by referring to Table 3 or 4, or by referring to other tables. In some other possible implementations, the bias values ​​indicated in Table 3 or 4 may correspond to scaling factors of other values. For example, a bias value indication of 1 may correspond to ε1, a bias value indication of 0 may correspond to ε2, and so on. These will not be elaborated upon here.

[0250] Please refer to Table 5 for the mapping relationship between the indicator value of another bias value and the scaling factor provided in the embodiments of this application.

[0251] Table 5

[0252]

[0253] Table 5 can be applied to PUSCH transmissions scheduled by DCI format 0_0, where the bias value provided to the terminal device is dynamic; or it can be applied to PUSCH transmissions with configured grant type 2, where the grant type provided to the terminal device is dynamic; or it can be applied to other types of cases, without limitation. It can be understood that in the above cases, the information in the first row is used by default, so that the scaling factor can be determined based on ε indicated in the first row. Table 4 can also refer to Table 5, indicating the scaling factor only through the information in the first row, and not indicating the scaling factor in the second row.

[0254] Tables 3, 4, and 5 above indicate the scaling factor using the bias value indicator. In some possible implementations, the bias value can be indirectly indicated by the index value of the bias value indicated by the bias value indicator. For example, please refer to Tables 6, 7, or 8, which respectively show the mapping relationship between the bias value indicator and the bias value index provided in the embodiments of this application.

[0255] Table 6

[0256]

[0257] Table 7

[0258]

[0259] Table 8

[0260]

[0261] Tables 6 and 8 each have a separate column for the indexes active when using OCC sequence expansion. That is, when using OCC sequence expansion, the scaling factor and / or bias value determined by the index on the right can be used; when not using OCC sequence expansion, the scaling factor and / or bias value determined by the index in the middle can be used. Table 7 does not have a separate column for the indexes active when using OCC sequence expansion; instead, it adds indicators for new bias values, such as '100', '101', '110', and '111'. Each indicator value indicates an index for a set of bias values ​​primarily used when using OCC expansion. Table 8 can be referenced from the description in Table 5, and in some cases, only the index in the first row is indicated.

[0262] Each set of indexes in Tables 6, 7, and 8 can be referenced as described above. It should be understood that Tables 6, 7, and 8 are merely examples. The scaling factor and / or bias value can be determined by referring to the indexes corresponding to the indicator values ​​of the bias values ​​in Tables 6, 7, and 8, or by referring to other tables. Furthermore, this application does not limit the indexes for each set of bias values.

[0263] In the embodiments of this application, the first parameter / or the second parameter may be related to the indication value of the bias value, or may be related to the antenna port, redundancy version (RV), modulation and coding scheme (MCS), etc.

[0264] In some other possible implementations, the scaling factor and / or bias value can be related to n. SCID The values ​​of the code division multiplexing (CDM) group, CDM group value λ, parameter Δ, DMRS extra position, DMRS type, PUSCH DMRS time index l′, sounding reference signal (SRS) request message, SRS resource setting indication, SRS offset indication, phase tracking reference signal (PT-RS)-DMRS association, precoding information and layer number, channel state information (CSI) request, PUSCH scheduling transmission power control (TPC) command, code block group (CBG) transmission information, etc., are not limited here. These indication values ​​can be used alone to indicate the first parameter / or the second parameter, or they can be used in combination to indicate the first parameter / or the second parameter, which is also not limited here.

[0265] The following example uses scaling factors related to antenna ports; please refer to Table 9.

[0266] Table 9

[0267] value Antenna port Scaling factor 0 1000 ε1 1 1001 ε2 2 1002 ε3 3 1003 ε4 4 …

[0268] As can be seen, the scaling factor corresponding to the antenna port can be determined according to Table 9. For example, when receiving first information, which includes the value corresponding to the antenna port, the scaling factor can be determined based on that value. This application does not limit the value of the scaling factor corresponding to the antenna port in Table 9.

[0269] Alternatively, the scaling factor can be determined by a value that can be obtained by redefining the fields in the aforementioned DCI (e.g., antenna port, redundancy version, MCS, etc.), without limitation here. When the number of scaling factors is 4, refer to Table 10.

[0270] Table 10

[0271] Value or bit value Scaling factor 0(00) ε1 1(01) ε2 2(10) ε3 3(11) ε4

[0272] In some other possible implementations, the first parameter and / or the second parameter are related to the configuration parameters of the OCC sequence. These configuration parameters may include: the code length of the OCC sequence and / or the index of the OCC sequence.

[0273] The code length of the OCC sequence can be referred to above and will not be repeated here. It can be understood that, based on the mapping relationship between the index and the OCC sequence, the OCC sequence corresponding to the index and its code length can be determined. When there is a mapping relationship between the code length and the OCC sequence, for example, with a code length of 2, the OCC sequence is [1 1] or [1-1]; with a code length of 4, the OCC sequences are [1 1 1 1], [1 -1 1 -1], [1 1 -1 -1], [1 -1 -1 1], etc., and the OCC sequence can be determined based on its code length. In this embodiment, the code length and / or index of the OCC sequence can also be used to indicate the first parameter and / or the second parameter, such as a scaling factor. This can save signaling overhead.

[0274] In some possible implementations, the configuration parameters of the OCC sequence may also include an enable indication for the OCC sequence.

[0275] In this embodiment, the OCC sequence enable indicator is extended, for example, OCC-enabled, to indicate whether the first communication device uses the OCC sequence for OCC extension or performs OCC extension. For example, the OCC sequence enable indicator may use 0 to indicate that the first communication device uses the OCC sequence for OCC extension, and use 1 to indicate that the first communication device does not use the OCC sequence for OCC extension. Alternatively, the OCC sequence enable indicator may use 1 to indicate that the first communication device uses the OCC sequence for OCC extension, and use 0 to indicate that the first communication device does not use the OCC sequence for OCC extension. As another example, the OCC sequence enable indicator may use yes or enabled to indicate that the first communication device uses the OCC sequence for OCC extension, and use no or disabled to indicate that the first communication device does not use the OCC sequence for OCC extension.

[0276] In this embodiment, extending the information carried on the PUSCH involves multiplying the information by the OCC element corresponding to the resource unit occupied by the PUSCH in the OCC sequence. This information may include data carried on the PUSCH and / or information multiplexed by UCI. The first communication device using the OCC sequence for extension can extend the information to be transmitted using the OCC sequence; that is, the first communication device will transmit the information multiplied by the OCC element corresponding to the resource unit occupied by the information. In other words, the OCC sequence enable indicator can be used to indicate whether the first terminal device uses the OCC sequence to extend the information carried on the PUSCH. If yes, then the subsequent step S402 can be executed. If no, then step S402 is not executed, and the information carried on the PUSCH can be transmitted on the resource unit occupied by the PUSCH without extension based on the OCC sequence.

[0277] The resource units occupied by PUSCH in this application can be determined through the aforementioned time-domain resource configuration, which will not be described in detail here.

[0278] It should be understood that the above values ​​or characters are just some examples of OCC sequence enable indicators. In fact, OCC sequence enable indicators can be represented by other characters, which are not limited here. For example, OCC sequence enable indicators can be represented by "NOOCC" or "N" and are used to indicate that OCC sequence extensions are not used.

[0279] In some possible implementations, if no OCC sequence enable indication is provided, the OCC sequence will be used for extension by default if the configuration parameters of the OCC sequence include the code length and / or index of the OCC sequence. If an OCC sequence enable indication is provided, the first parameter and / or the second parameter can be activated, thereby reducing the resource size occupied by UCI.

[0280] The above examples illustrate the configuration parameters of the OCC sequence as the code length, index, and enable indication of the OCC sequence. In other possible implementations, the configuration parameters of the OCC sequence may also include other configuration parameters not described herein, and are not limited thereto. These configuration parameters of the OCC sequence may be used to indicate the first parameter and / or the second parameter, such as the scaling factor and / or the bias value.

[0281] This application does not limit the mapping relationship between the configuration parameters of the OCC sequence and its corresponding first parameter / or second parameter. For example, please refer to Table 11 or Table 12.

[0282] Table 11

[0283] Code length (or OCC-length) of the OCC sequence Scaling factor 2 ε1 4 ε2

[0284] Table 12

[0285]

[0286] Table 11 illustrates the mapping relationship between the code length and scaling factor of the OCC sequence, while Table 12 illustrates the mapping relationship between the code length, index, and enable indicator of the OCC sequence, and the scaling factor. Table 12 may exclude the enable indicator of the OCC sequence, such as excluding rows with a value of 0. When there is no mapping relationship between the configuration values ​​and the configuration parameters of the OCC sequence on the network side, the enable indicator for the OCC sequence corresponding to an unindicated value can be assumed to be that the OCC sequence is not used for extension. The values ​​in Table 12 can correspond to antenna ports, such as antenna port 1001 corresponding to a value of 1, antenna port 1002 corresponding to a value of 2, etc. Thus, the enable indicator and scaling factor of the OCC sequence can be determined based on the antenna port indicated on the network side.

[0287] In practical use, the corresponding scaling factor can be determined by referring to Table 11 or Table 12, or by referring to other tables. Table 11 or Table 12 are merely examples, and this application does not limit the scaling factor determined by the values ​​therein. That is to say, the scaling factor corresponding to the configuration parameters of the OCC sequence can be as shown in Table 11 or Table 12, or it cannot be different from Table 11 and Table 12.

[0288] In some possible implementations, the first and / or second parameter corresponding to an OCC sequence code length of 2 can be greater than the first and / or second parameter corresponding to an OCC sequence code length of 4. For example, when the OCC sequence code length is 2, the UCI is usually repeated twice, which is a smaller number of repetitions, and the scaling factor can be a larger value, such as 0.6; when the OCC sequence code length is 4, the UCI is usually repeated four times, which is a larger number of repetitions and has higher reliability, and the scaling factor can be a smaller value, such as 0.2.

[0289] In some possible implementations, the scaling factor can be configured in the information element (IE) of the bias value. For example,

[0290]

[0291] The scaling factor in the BetaOffsets information element is a common scaling factor, such as CommonScalingFactor, and this application does not limit the size of this scaling factor. The BetaOffsets information element may include some optional offset values, such as indices indicating the offset values ​​for HARQ-ACK information, such as betaOffsetACK-Index1, betaOffsetACK-Index2, and betaOffsetACK-Index3. The BetaOffsets information element may also include indices for CSI reports, such as betaOffsetCSI-Part1-Index1, betaOffsetCSI-Part1-Index2, betaOffsetCSI-Part2-Index1, and betaOffsetCSI-Part2-Index2. These indices can be integers between 0 and 31, and are not limited here. The above example adds a scaling factor to the BetaOffsets information element; in practice, the scaling factor can be indicated through newer IE browsers or other IE browsers.

[0292] This application does not limit the method of using the first parameter and / or the second parameter, and the aforementioned formula can be referred to. For example, the bias value can be substituted into the formula provided in the existing protocol. Alternatively, a new formula can be introduced, for example, when the scaling factor is ε, it can include at least one of the following methods for determining the resource size occupied by HARQ-ACK information and / or CSI reports.

[0293] Method 1: The scaling factor can be multiplied by the resource size of the HARQ-ACK information or CSI report calculated using existing formulas. For example,

[0294] Q′ ACK,new =ε*Q′ ACK (5)

[0295] Q′ CSI-1,new =ε*Q′ CSI-1 (6)

[0296] Q′ CSI-2,new =ε*Q′ CSI-2 (7)

[0297] Among them, Q′ ACK Q′ CSI-1 and Q′ CSI-2 This can be referred to above, and will not be repeated here. Q′ ACK,new Q′ CSI-1,new and Q′ CSI-2,newThis can be understood as the resource size adjusted by ε. It can be understood that multiplying the scaling factor ε by the resource size occupied by the HARQ-ACK information or CSI report calculated by the existing formula can reduce the occupied resource size when ε is less than 1. The ε in the above example is the same; in other possible implementations, ε can be different for different UCI types. That is, the ε of the HARQ-ACK information can be the same as or different from the ε of the CSI report, and the ε of the CSI part1 report can be the same as or different from the ε of the CSI part2 report.

[0298] Method 2: The scaling factor can be multiplied by a portion of the information in the existing formula. This portion of information can be used to determine the minimum resources required for HARQ-ACK information and / or CSI reporting. For example,

[0299]

[0300] For example,

[0301]

[0302] Formulas (8) and (11) are used to scale the resource size occupied by HARQ-ACK information, respectively. Formulas (9) and (12) are used to scale the resource size occupied by CSI part1 report, respectively. Formulas (10) and (13) are used to scale the remaining resource size occupied by CSI part2 report, respectively. Formulas (5) to (11) are merely examples. This application does not limit the use of scaling factors and / or bias values. They can be applied in existing formulas as described in this application, or they can be used in formulas not described in this application, so that the resources occupied by UCI or HARQ-ACK information or CSI report are scaled.

[0303] S402, the first communication device sends a first PUSCH, the first PUSCH is multiplexed by a CSI report whose resource size is scaled by a first parameter, and the multiplexed first PUSCH is extended by an OCC sequence, the OCC sequence being associated with the first PUSCH.

[0304] Correspondingly, the second communication device receives the first PUSCH. The method for despreading uplink data by the second communication device can be referred to the description of OCC, and will not be repeated here. The PUSCH is extended by the OCC sequence; in practice, this can be the information carried on the PUSCH being extended by the OCC sequence, for example, by multiplying the information carried on the PUSCH by the OCC element corresponding to the time unit occupied by that information in the OCC sequence. Thus, the CSI report in step S402 can be extended by the OCC sequence. In some possible implementations, the first PUSCH is also multiplexed by HARQ-ACK information. This allows HARQ-ACK information to be multiplexed onto the first PUSCH for transmission, thus avoiding data loss. The resource size occupied by HARQ-ACK information on the first PUSCH can be scaled by the second parameter, or it can be scaled without the second parameter, etc., and is not limited here. In addition to CSI reports and HARQ-ACK information, the information multiplexed onto the PUSCH in the UCI can also include other information, and is not limited here. After the HARQ-ACK information is multiplexed into the first PUSCH, the first PUSCH undergoes OCC sequence expansion, so that the HARQ-ACK information also undergoes OCC sequence expansion in accordance with the CSI report.

[0305] In this embodiment, the first PUSCH can be a PUSCH to be transmitted on time-domain resources that overlap with the time-domain resources occupied by the PUCCH, or it can be the currently transmitted PUSCH, etc., without limitation. The PUCCH can carry UCI, and in some possible implementations, the time-domain resources occupied by the PUCCH overlap with K time units.

[0306] In this implementation, K time units are contained within M time units, and each of the M time units is used to carry the PUSCH for uplink data. M and K are integer multiples of L, where L is the code length of the OCC sequence. That is, the M time units include K time units. Furthermore, the uplink data transmitted in each of the M time units can be the same or belong to the same transport block. The K time units can be time-domain resources within the M time units that actually overlap with the time-domain resources occupied by the PUSCH, and these time-domain resources correspond to complete OCC sequences; that is, the number of corresponding time units is an integer multiple of L. In some possible implementations, M = K, or M > K. In some possible implementations, K = L, or K > L. Or in some possible implementations, M = K = L.

[0307] For an example using time-slot OCC, please refer to [link / reference]. Figures 5A to 5D ,exist Figures 5A to 5D The code length of the OCC sequence is 2, i.e., L = 2. In Figure 5A and Figure 5B In this context, M = 8. Figure 5CIn this case, M = 4. Figure 5D In this case, M = 2. For example... Figure 5A As shown, the PUCCH used to carry UCI is located in slots #1 and #2. Slot #1 corresponds to W(2) in the first OCC sequence, and slot #2 corresponds to W(1) in the second OCC sequence. It can be seen that the K time units that actually overlap with the time domain resources occupied by the PUCCH are the time units corresponding to the first and second OCC sequences, i.e., slots #0 to #3, where K = 4, M > K, and K > L. The first PUSCH can be M PUSCHs, such as... Figure 5A As shown in Method 1, the UCI information, after OCC sequence expansion, is transmitted on the PUSCH of each time slot from slot #0 to slot #7. Alternatively, the first PUSCH can be K PUSCHs, such as... Figure 5A As shown in Method 2, the UCI information after OCC sequence expansion is transmitted on the PUSCH of each time slot from slot #0 to slot #3. Alternatively, the first PUSCH can be L PUSCHs, such as... Figure 5A As shown in Method 3, the UCI information, after OCC sequence expansion, is transmitted on the PUSCH of each time slot in slots #0 and #1. Figure 5A In methods one, two, and three, uplink data extended by the OCC sequence can still be transmitted on the time domain resources in the PUSCH that are not occupied by information after UCI extension. Figure 5A In Method 2, within the M time units excluding the K time units, such as the PUSCH of each time slot from slot #4 to slot #7, uplink data extended via the OCC sequence can be transmitted. Figure 5A In Method 3, in the time units other than L time units in M ​​time units, such as the PUSCH of each time slot from slot #2 to slot #7, the uplink data after OCC sequence expansion can be sent.

[0308] like Figure 5B As shown, the PUCCH used to carry UCI is located in slot #2. Therefore, the K time units that actually overlap with the time domain resources occupied by the PUCCH are the time units corresponding to the second OCC sequence, namely slot #2 and slot #3, where K = 2. Thus, M > K, M > L, and K = L. The first PUSCH can have M PUSCHs, such as... Figure 5B As shown in Method 1, the UCI information, after OCC sequence expansion, is transmitted on the PUSCH of each time slot from slot #0 to slot #7. Alternatively, the first PUSCH can be K PUSCHs, such as... Figure 5BAs shown in Method 2, UCI information extended with an OCC sequence is transmitted on the PUSCH of each time slot in slots #2 and #3. Furthermore, uplink data extended with an OCC sequence can still be transmitted on the time domain resources of the PUSCH that are not occupied by UCI-extended information. Figure 5B In Method 2, in the time units other than the K time units in the M time units, such as the PUSCH of each time slot from slot #0, slot #1, slot #4 to slot #7, the uplink data after OCC sequence expansion can be sent.

[0309] like Figure 5C As shown, the PUCCH used to carry UCI is located in slots #1 and #2. Therefore, the K time units that actually overlap with the time domain resources occupied by the PUCCH are the time units corresponding to the first and second OCC sequences, i.e., slots #0 to #3, where K = 4. Thus, M = K, M > L, and K > L. The first PUSCH can be either M PUSCHs or K PUSCHs, such as... Figure 5C As shown in Method 1, UCI information extended by the OCC sequence is transmitted on the PUSCH of each time slot from slot #0 to slot #3. Furthermore, uplink data extended by the OCC sequence can also be transmitted on the time domain resources of the PUSCH that are not occupied by UCI-extended information.

[0310] like Figure 5D As shown, the PUCCH used to carry UCI is located in slot #1. Therefore, the K time units that actually overlap with the time domain resources occupied by the PUCCH are the time units corresponding to the first OCC sequence, i.e., slot #0 and slot #1, where K = 2. Thus, M = K = L = 2. The first PUSCH can be two PUSCHs, such as... Figure 5D As shown, information after UCI sequence expansion is transmitted on the PUSCH of each time slot in slots #0 and #1. Furthermore, uplink data after OCC sequence expansion can still be transmitted on the time domain resources of the PUSCH that are not occupied by information after UCI expansion.

[0311] The above method of transmitting information on M PUSCHs is merely an example; in reality, other methods can also be used. For example, as described later... Figure 5A Method Four and Figure 5B Method 3, and Figure 5C Method two, UCI can be transmitted via PUCCH.

[0312] For example, when M is greater than L, UCI can be sent via PUSCH over L time units, and uplink data extended with OCC sequence can be sent via PUSCH over the remaining M time units (excluding the L time units). The UCI may or may not undergo OCC sequence extension. The L time units may or may not include the time domain resources occupied by PUCCH. Figure 5A As shown in Method 3, the UCI information after OCC sequence extension is transmitted on the PUSCH of slot #1, which overlaps with the time domain resources occupied by the PUCCH. Furthermore, the UCI information after OCC sequence extension can also be transmitted on the PUSCH of slot #0, which does not overlap with the time domain resources occupied by the PUCCH. In some possible implementations, the L time units can be the earliest L time units among the M time units, i.e., the first OCC group among the M time units.

[0313] For example, when M is greater than K, UCI can be sent via PUSCH over K or L time units, and the uplink data after OCC sequence extension can be sent via PUSCH over the remaining M time units (excluding K or L time units). The UCI may or may not undergo OCC sequence extension.

[0314] For example, such as Figure 5C As shown in Method 2, UCI information extended by OCC sequence can be sent on the PUSCH of each time slot in slot #1 and slot #2. Uplink data extended by OCC sequence can also be sent on the time domain resources of the PUSCH that are not occupied by UCI information. Uplink data extended by OCC sequence can also be sent on the PUSCH of each time slot in slot #0 and slot #3.

[0315] In some possible implementations, step S402 may include: when M=L, the first communication device transmits a first PUSCH in each of the K time units. Correspondingly, the second communication device receives the first PUSCH in each of the K time units.

[0316] In this embodiment, the CSI report and / or HARQ-ACK information in UCI can be reused on the PUSCH, and the PUSCH obtained after OCC sequence expansion can be called the first PUSCH. The first PUSCH carries the CSI report and / or HARQ-ACK information after OCC sequence expansion.

[0317] It's understandable that when M equals L, M = K = L. Discarding the uplink data carried on the PUSCH would prevent the network from receiving the uplink data, potentially leading to retransmissions and wasting resources. Therefore, it can be done as follows: Figure 5C or Figure 5D As shown, UCIs such as CSI reports and HARQ-ACK information are multiplexed onto the PUSCH, allowing the multiplexed PUSCH to be extended via OCC to obtain a first PUSCH. This first PUSCH, in addition to the UCIs such as CSI reports and HARQ-ACK information extended via OCC, may also include some uplink data after OCC sequence extension. Furthermore, the information multiplexed onto the PUSCH in the UCIs can include other information besides CSI reports and HARQ-ACK information, which is not limited here. This reduces the impact of UCI multiplexing onto the PUSCH on data transmission, facilitating the second communication device to receive correct data.

[0318] In some other possible implementations, step S402 may include: when M>K, the first communication device does not transmit PUSCH for K time units, and transmits a second PUSCH for the remaining time units out of the M time units. Correspondingly, the second communication device does not receive PUSCH for K time units, and receives the second PUSCH for the remaining time units out of the M time units.

[0319] The second PUSCH carries the uplink data after OCC sequence expansion. In other words, when M is greater than L (i.e., when the number of PUSCH repetitions is greater than K), the first communication device can discard PUSCHs on K time units, thus not transmitting the uplink data carried on those PUSCHs. Instead, it can send the uplink data after OCC sequence expansion on the remaining M time units (excluding K time units), ensuring the second communication device receives the correct data.

[0320] If no PUSCH is sent in the K time units, CSI reports and / or HARQ-ACK information can be sent via PUCCH on the time domain resources occupied by PUCCH, or CSI reports and / or HARQ-ACK information can be sent via PUCCH in each of the K time units; there is no limitation on this. If the resource size occupied by CSI reports and / or HARQ-ACK information is less than the resource size of the time unit, partial CSI reports and / or HARQ-ACK information after OCC sequence expansion can be transmitted via PUCCH in each of the K time units. If the resource size occupied by CSI reports and / or HARQ-ACK information is greater than or equal to the resource size of the time unit, all or part of the CSI reports and / or HARQ-ACK information after OCC sequence expansion can be transmitted via PUCCH in each of the K time units.

[0321] For example, please continue to refer to Figure 5A or Figure 5B .exist Figure 5A In Method 4, where M > K, PUSCH can be omitted for K time units (slots #0 to #3), and UCI can be sent via PUCCH instead. A second PUSCH can be sent for the remaining M time units (slots #4 to #7), carrying the uplink data after OCC sequence expansion. For example... Figure 5B As shown in Method 3, where M > K, PUSCH can be omitted for K time units (slots #2 and #3), and UCI can be sent via PUCCH instead. A second PUSCH can be sent in the remaining M time units (slots #0, #1, #4 to #7), carrying the uplink data after OCC sequence expansion. The UCI sent in the K time units can be as follows: Figure 5A Method 4 or Figure 5B Method 3, which does not involve OCC sequence expansion, can also be less... Figure 5A or Figure 5B The result is an OCC sequence extension, which is not limited here.

[0322] Figures 5A to 5DThe data transmission methods shown for UCI and / or PUSCH are merely examples; in practice, other methods can be used. For instance, if M > L, no PUSCH is transmitted over K time units, and a second PUSCH is transmitted over M time units excluding the K time units. Alternatively, if M > L, no PUSCH is transmitted over either K or L time units, and a second PUSCH is transmitted over M time units excluding the L time units.

[0323] The second PUSCH, as described above, carries the uplink data after OCC sequence expansion. The L time units can be L time units out of K time units, or L time units out of M time units. Each L time unit can correspond to one or more OCC sequences, which is not limited here. The OCC elements in the corresponding OCC sequences for each of the L time units must be different. UCI can be sent via the PUSCH in the L time units, or it can be sent on the time domain resources occupied by the PUCCH. This application does not limit the number of time units occupied when transmitting UCI via PUCCH. For example, when the PUCCH occupies 2 time slots, it can be less than... Figure 5C As shown, UCI is sent via PUCCH in any L time units out of M time units (such as slot#0 and slot#1, or slot#2 and slot#3, or slot#0 and slot#3, or slot#1 and slot#2). In the time units other than those occupied by PUCCH, the uplink data after OCC sequence expansion is sent via the second PUSCH.

[0324] In some possible implementations, the method may further include: If the frequency domain resources occupied by the PUCCH do not overlap with the frequency domain resources occupied by the PUCCH in a time unit where the frequency domain resources occupied by the PUCCH overlap with the time domain resources occupied by the PUCCH, then the PUCCH may not be transmitted. That is, if the time domain resources between the PUCCH and PUSCH overlap, but the frequency domain resources do not overlap, a UCI can be transmitted via the PUCCH, and this UCI may not undergo OCC sequence extension. If the time domain resources between the PUCCH and PUSCH overlap, and the frequency domain resources also overlap, then neither the PUCCH nor the UCI carried on the PUCCH may be transmitted.

[0325] The above example illustrates OCC extension by multiplying information from a time unit with the OCC element. In other possible implementations, OCC extension can be performed on frequency domain units (such as REs). For example, a first PUSCH or PUCCH is transmitted in each of the K frequency domain units. Optionally, the K frequency domain units are frequency domain resources that actually overlap between the frequency domain resources occupied by the PUCCH and the frequency domain resources occupied by the PUSCH, and correspond to a complete OCC sequence. In some possible implementations, if the time domain resources occupied by the PUCCH do not overlap with the time domain resources occupied by the PUSCH in the K frequency domain units where the time domain resources occupied by the PUCCH overlap with the frequency domain resources occupied by the PUCCH, then the PUCCH is transmitted in each of the K frequency domain units. If the time domain resources occupied by the PUCCH overlap with the time domain resources occupied by the PUSCH in the K frequency domain units where the time domain resources occupied by the PUCCH overlap with the frequency domain resources occupied by the PUCCH, then the PUCCH is not transmitted, thus UCI is not transmitted via PUSCH or PUCCH.

[0326] In some possible implementations, the code length of the OCC sequence can be a frequency hopping value, such as X. That is, the PUSCH extended by the OCC sequence can be transmitted and frequency hopping can be performed through inter-slot frequency hopping.

[0327] For example, please refer to Figure 6 When the OCC sequence has a code length of 4, the first communication device can perform frequency hopping in units of 4 time slots. When the OCC sequence has a code length of 2, the first communication device can also perform frequency hopping in units of 4 time slots. Thus, the second communication device can simultaneously schedule the first communication device with an OCC sequence code length of 2 and the first communication device with an OCC sequence code length of 4 on the same time-frequency resources.

[0328] In some possible implementations, the first PUSCH can transmit information extended by the OCC sequence over a fixed-length resource unit. This application does not limit the fixed-length time unit; it can be an integer multiple of the code length of the OCC sequence, such as 4.

[0329] For example, when the OCC sequence has a code length of 4, the first communication device can perform OCC extension over 4 time units. When the OCC sequence has a code length of 2, the first communication device can also perform OCC extension over 4 time units. Thus, the second communication device can simultaneously schedule the first communication device with an OCC sequence code length of 2 and the first communication device with an OCC sequence code length of 4 on the same resource.

[0330] Understandable, Figure 4In the method shown, CSI reports can be multiplexed onto the PUSCH for transmission. The multiplexed PUSCH undergoes OCC sequence extension, which prevents the CSI reports to be sent on the terminal side from being discarded. Furthermore, the resource size occupied by the CSI report is scaled by a first parameter before being multiplexed onto the PUSCH. When the first parameter of the CSI report is less than 1, the resource size occupied by the CSI report on the PUSCH can be reduced, minimizing the impact on the data transmission originally carried on the PUSCH occupied by the CSI report, thus facilitating the network side's correct reception of information and data.

[0331] The examples above illustrate whether the UCI in the PUCCH is multiplexed onto the PUSCH, which requires OCC extension. Other information can be transmitted on the PUSCH, or the resources occupied by the PUSCH can be used for the transmission of other information, such as SRS, etc. Other information can also be extended based on the OCC sequence.

[0332] In other possible implementations, the method may include: a first communication device transmitting an OCC-extended SRS to a second communication device at each of P time units. Correspondingly, the second communication device receives the OCC-extended SRS received by the first communication device at each of the P time units.

[0333] Where P is an integer multiple of L, and each of the P time units is used to carry the PUSCH for uplink data to be transmitted. This uplink data may be different from or the same as the uplink data to be transmitted in the aforementioned M time units. The P time units are the time units corresponding to the OCC sequence associated with the time domain resources occupied by the SRS, or can be described as the time units corresponding to the OCC sequence in which the SRS is located. Thus, transmitting the SRS in each of the P time units, and the SRS can be extended by the OCC sequence, does not affect other first communication devices from transmitting data after OCC sequence extension through the PUSCH on the time domain resources for transmitting the SRS, and can ensure the orthogonality between data. In the P time units, the uplink data carried on the PUSCH after OCC sequence extension can also be transmitted on the time domain resources not occupied by the SRS.

[0334] For example, please refer to Figure 7A , Figure 7AThe code length of the OCC sequence in the sequence is 2. The SRS is located in OS#12 and OS#13 in slot#1. The time units corresponding to the OCC sequence of the OCC element corresponding to slot#0 are slot#0 and slot#1, P=2. The SRS can be extended on OS#12 and OS#13 in slot#0 and slot#1 respectively by the OCC element corresponding to PUSCH. For example, the SRS can be multiplied on OS#12 and OS#13 in slot#0 by W(1) corresponding to slot#0 respectively, and the SRS can be multiplied on OS#12 and OS#13 in slot#1 by W(2) corresponding to slot#1 respectively.

[0335] In some possible implementations, the first communication device transmits the SRS (Extended SRS) with OCC sequence extension to the second communication device on the time-domain resources occupied by the SRS. Correspondingly, the second communication device receives the SRS with OCC sequence extension from the first communication device on the time-domain resources occupied by the SRS. That is, the SRS with OCC sequence extension can be transmitted on the time-domain resources occupied by the SRS within P time units, and data with OCC sequence extension can be transmitted on the time-domain resources other than those occupied by the SRS within the P time units.

[0336] In some possible implementations, when P is greater than L, the first communication device transmits the SRS (Extended Sentence Representation) with OCC sequence extension to the second communication device in each of the L time units, and transmits the uplink data carried on the PUSCH with OCC sequence extension in the time units other than the L time units in the P time units. Correspondingly, the second communication device receives the SRS with OCC sequence extension from the first communication device in each of the L time units, and receives the uplink data carried on the PUSCH with OCC sequence extension in the time units other than the L time units in the P time units. Thus, the SRS with OCC sequence extension can be transmitted on the time domain resources corresponding to the SRS in each of the L time units, and the data with OCC sequence extension can be transmitted on the time domain resources other than those occupied by the SRS in the P time units. This application does not limit the number of L time units.

[0337] The above implementations of SRS transmission can be executed with or without meeting the timeline conditions. In some possible implementations, the first SRS symbol in the first time unit of P time units meets the timeline conditions.

[0338] The first SRS symbol is determined by the first symbol of the SRS configured on the network side to begin transmission. That is, the position of the first SRS symbol is the same as the starting symbol of the SRS. This first SRS symbol may or may not be located within the time unit corresponding to the time domain resources occupied by the SRS configured on the network side. Figure 7A or Figure 7B As shown, the time unit corresponding to the time domain resources occupied by the SRS configured on the network side is slot#1. The first SRS symbol in the first time unit of the P time units is not located in the time unit corresponding to the time domain resources occupied by the SRS configured on the network side, but is located in OS#12 in slot#0.

[0339] The timeline conditions can refer to the aforementioned timeline conditions required for scheduling PUSCH, or they can be the timeline conditions required for transmitting SRS. In some possible implementations, the timeline condition is that the interval between the last symbol of the PDCCH and the start time of the first SRS symbol in the first time slot of P time units is not less than the processing duration. This processing duration can be the preparation procedure time of the PUSCH of the terminal device as described in protocol TS38.214 6.2.1, such as N2+T. switch or N2+14+T switch N2 is selected based on the PUSCH processing capability of the terminal device for the i-th PUSCH and the SCS configuration μ. μ corresponds to the smallest SCS configuration among the PDCCH used for scheduling the i-th PUSCH, the PDCCH used for scheduling PDSCH, or the SCS configuration that provides a DCI format that does not schedule PDSCH. T switch As defined in Section 6.4 of Protocol TS38.214, and the Z1 value in Table 5.4-1 of Protocol TS38.214 is used. Z = max(Z(m)), where m is the number of updated CSI reports.

[0340] It is understandable that if the first SRS symbol in the first time unit of P time units meets the timeline conditions, SRS can be transmitted starting from the first SRS symbol in the first time unit of P time units, thus avoiding SRS dropping. Furthermore, the time domain resources (or symbols) not occupied by SRS in this time unit can still be used to transmit the uplink data carried on PUSCH after OCC sequence expansion.

[0341] In some possible implementations, if the first SRS symbol in the first time unit of P time units does not meet the timeline condition, the SRS may not be transmitted, or it may be transmitted in a subsequent time unit that meets the timeline condition. Optionally, the SRS may or may not be multiplied with the OCC element, etc., and this is not limited here.

[0342] For example, please refer to Figure 7A or Figure 7B , Figure 7A If the interval T1 between the last symbol of the PDCCH and the start time of the first SRS symbol (OS#12 in slot #0) in the first slot of P time units is greater than the processing time T0, then the SRS after OCC sequence expansion can be sent in each of the P time units. Figure 7B If the interval T2 between the last symbol of the PDCCH and the start time of the first SRS symbol (OS#12 in slot#0) in the first slot of P time units is less than the processing time T0, then the SRS does not need to be sent, and the uplink data after OCC sequence expansion can be sent in each of the P time units.

[0343] The methods of the embodiments of this application have been described in detail above, and the apparatus of the embodiments of this application is provided below.

[0344] Please see Figure 8 , Figure 8 This is a schematic diagram of a communication device provided in an embodiment of this application. The communication device may include a transceiver unit 801 and a processing unit 802. The transceiver unit 801 may be a device with signal input (receiving) or output (transmitting) capabilities, used for signal transmission with other devices or other components within a device. The processing unit 802 may be a device with processing capabilities, including one or more processors, used for executing instructions (or code or programs), for example, processing communication protocols and communication data. This communication device may be a first communication device or a second communication device.

[0345] In one embodiment, when the communication device can be a first communication device, wherein:

[0346] The processing unit 802 is used to determine the first parameter of the Channel State Information (CSI) report; wherein the first parameter is less than or equal to 1, and the first parameter of the CSI report is used to scale the resource size occupied by the CSI report;

[0347] The transceiver unit 801 is used to transmit the first physical uplink shared channel (PUSCH). The first PUSCH is multiplexed by the CSI report after the resource size has been scaled by the first parameter. The multiplexed first PUSCH is extended by an orthogonal overlay code (OCC) sequence, and the OCC sequence is associated with the first PUSCH.

[0348] In some possible implementations, the processing unit 802 is further configured to determine a second parameter of the HARQ-ACK information, which is used to scale the resource size occupied by the HARQ-ACK information.

[0349] In some possible implementations, the first parameter and / or the second parameter may include a bias value and / or a scaling factor.

[0350] In some possible implementations, the first parameter and / or the second parameter are related to one of the following: configuration parameters of the OCC sequence, or parameters in the downlink control information (DCI).

[0351] In some possible implementations, the configuration parameters of the OCC sequence include at least one of the following: the code length of the OCC sequence, the index of the OCC sequence, and the enable indicator of the OCC sequence; wherein, the enable indicator of the OCC sequence is used to indicate that the OCC sequence is used for extension, and the information carried on the extended first PUSCH is multiplied by the information and the OCC element corresponding to the resource unit occupied by the first PUSCH in the OCC sequence.

[0352] In some possible implementations, the parameters in the DCI include at least one of the following: an indication value for the bias value, an antenna port, a redundancy version, and a modulation and coding scheme (MCS).

[0353] In some possible implementations, the scaling factor is less than 0.5.

[0354] In some possible implementations, the first parameter and / or the second parameter are activated when using OCC sequence expansion.

[0355] In some possible implementations, the first PUSCH is also reused by the HARQ-ACK message.

[0356] In some possible implementations, HARQ-ACK information and CSI reports are carried on the Physical Uplink Shared Channel (PUCCH). The time domain resources occupied by PUCCH overlap with K time units, which are contained in M ​​time units. Each of the M time units is used to carry uplink data via PUSCH, where M and K are integer multiples of L, and L is the code length of the OCC sequence.

[0357] The transceiver unit 801 is used to transmit the first PUSCH in each of the K time units when M=L.

[0358] In some possible implementations, the transceiver unit 801 is configured to not transmit PUSCH on K resource units when M>K, and to transmit a second PUSCH on time units other than K time units out of M time units, the second PUSCH carrying the uplink data after OCC sequence extension.

[0359] Alternatively, in one embodiment, when the communication device can be a second communication device, wherein:

[0360] The processing unit 802 is used to determine the first parameter of the Channel State Information (CSI) report; wherein the first parameter is less than or equal to 1, and the first parameter of the CSI report is used to scale the resource size occupied by the CSI report;

[0361] The transceiver unit 801 is used to receive the first physical uplink shared channel (PUSCH). The first PUSCH is multiplexed by the CSI report after the resource size has been scaled by the first parameter. The multiplexed first PUSCH is then processed by an orthogonal coverage code (OCC), and the OCC sequence is associated with the first PUSCH.

[0362] In some possible implementations, the processing unit 802 is further configured to determine a second parameter of the HARQ-ACK information, which is used to scale the resource size occupied by the HARQ-ACK information.

[0363] In some possible implementations, the first parameter and / or the second parameter may include a bias value and / or a scaling factor.

[0364] In some possible implementations, the first parameter and / or the second parameter are related to one of the following: configuration parameters of the OCC sequence, or parameters in the downlink control information (DCI).

[0365] In some possible implementations, the configuration parameters of the OCC sequence include at least one of the following: the code length of the OCC sequence, the index of the OCC sequence, and the enable indicator of the OCC sequence; wherein, the enable indicator of the OCC sequence is used to indicate that the OCC sequence is used for extension, and the information carried on the extended first PUSCH is multiplied by the information and the OCC element corresponding to the resource unit occupied by the first PUSCH in the OCC sequence.

[0366] In some possible implementations, the parameters in the DCI include at least one of the following: an indication value for the bias value, an antenna port, a redundancy version, and a modulation and coding scheme (MCS).

[0367] In some possible implementations, the scaling factor is less than 0.5.

[0368] In some possible implementations, the first parameter and / or the second parameter are activated when using OCC sequence expansion.

[0369] In some possible implementations, the first PUSCH is also reused by the HARQ-ACK message.

[0370] In some possible implementations, HARQ-ACK information and CSI reports are carried on the Physical Uplink Shared Channel (PUCCH). The time domain resources occupied by PUCCH overlap with K time units, which are contained in M ​​time units. Each of the M time units is used to carry uplink data via PUSCH, where M and K are integer multiples of L, and L is the code length of the OCC sequence.

[0371] The transceiver unit 801 is used to transmit the first PUSCH in each of the K time units when M=L.

[0372] In some possible implementations, the transceiver unit 801 is configured to not transmit PUSCH on K resource units when M>K, and to transmit a second PUSCH on time units other than K time units out of M time units, the second PUSCH carrying the uplink data after OCC sequence extension.

[0373] Alternatively, in one embodiment, the communication device may be a first communication device, wherein:

[0374] The transceiver unit 801 is used to transmit the SRS extended by the OCC sequence in each of the P time units. Here, P is an integer multiple of L, and L is the code length of the OCC sequence. Each of the P time units is used to carry the PUSCH of the uplink data to be transmitted, and the P time units are the time units corresponding to the OCC sequence associated with the time domain resources occupied by the SRS.

[0375] In some possible implementations, the first SRS symbol in the first time unit of P time units satisfies the timeline condition, and the first SRS symbol is determined by the first symbol that SRS transmission begins.

[0376] In some possible implementations, the transceiver unit 801 is also used to transmit the SRS after OCC sequence extension on the time domain resources occupied by the SRS in P time units.

[0377] In some possible implementations, the transceiver unit 801 is also configured to transmit the SRS after OCC sequence expansion in each of the L time units when P is greater than L, and transmit the uplink data carried on PUSCH after OCC sequence expansion in the time units other than the L time units in the P time units.

[0378] In some possible implementations, the transceiver unit 801 is also configured to either not transmit SRS if the first SRS symbol in the first time unit of the P time units does not meet the timeline conditions, or transmit SRS in a subsequent time unit that meets the timeline conditions.

[0379] Alternatively, in one embodiment, the communication device may be a second communication device, wherein:

[0380] The transceiver unit 801 is used to receive the SRS after OCC sequence expansion in each of the P time units, where P is an integer multiple of L, and L is the code length of the OCC sequence. Each of the P time units is used to carry the PUSCH of the uplink data to be transmitted, and the P time units are the time units corresponding to the OCC sequence associated with the time domain resources occupied by the SRS.

[0381] In some possible implementations, the transceiver unit 801 is also configured to receive the SRS after OCC sequence extension on the time domain resources occupied by the SRS in P time units.

[0382] In some possible implementations, the transceiver unit 801 is further configured to receive the SRS after OCC sequence expansion in each of the L time units when P is greater than L, and to receive the uplink data carried on the PUSCH after OCC sequence expansion in the time units other than the L time units in the P time units.

[0383] In some possible implementations, the first SRS symbol in the first time unit of P time units satisfies the timeline condition, and the first SRS symbol is determined by the first symbol that starts transmitting SRS.

[0384] In some possible implementations, the transceiver unit 801 is also configured to either not receive SRS if the first time unit in the P time units does not meet the timeline conditions, or to receive SRS in subsequent time units that meet the timeline conditions.

[0385] The implementation of the above-mentioned transceiver unit 801 and processing unit 802 can be referred to Figure 4 The relevant descriptions of the method embodiments shown are not repeated here.

[0386] Please see Figure 9 , Figure 9 This is a schematic diagram of another communication device provided in an embodiment of this application. For example... Figure 9 As shown, the communication device may include a processor 111. The processor 111, also referred to as a processing unit, can implement certain control functions. When the processor 111 runs, it causes the communication device to execute the functions described in this embodiment. Figure 4 Any method described.

[0387] like Figure 9 The communication device shown may further include a storage medium 112, which may also be referred to as a storage unit or a memory. Instructions 114 are stored on the storage medium 112. These instructions 114 can be executed on the processor 111, causing the communication device to perform the functions described in this embodiment. Figure 4 Any method described.

[0388] Optionally, the processor 111 may include instructions 113, which can be executed on the processor 111 to cause the communication device to perform the actions described in this embodiment. Figure 4 Any method described.

[0389] The communication device can be a first communication device or a second communication device, used to implement the method described in the method embodiments. However, the scope of the device described in this application is not limited thereto; the communication device can be a standalone device or part of a larger device. For example, the communication device can be:

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

[0391] (2) A collection of one or more ICs, optionally, the collection of ICs may include a storage component for storing data and / or instructions;

[0392] (3) ASIC, such as modems;

[0393] (4) Modules that can be embedded in other devices.

[0394] Please see Figure 10 , Figure 10 This is a schematic diagram of the structure of a terminal device provided in an embodiment of this application. For ease of explanation, Figure 10 Only the main components of the terminal device are shown. For example... Figure 10As shown, the terminal device includes a processor, memory, control circuitry, antenna, and input / output devices. The processor is primarily used to process communication protocols and data, control the entire terminal device, execute software programs, and process the data generated by those programs. The memory is mainly used to store software programs and data. The radio frequency (RF) circuitry is primarily used for converting baseband signals to RF signals and processing RF signals. The antenna is primarily used for transmitting and receiving RF signals in the form of electromagnetic waves. Input / output devices, such as touchscreens, displays, and keyboards, are primarily used to receive user input data and output data to the user.

[0395] When the terminal device is powered on, the processor can read the software program from the storage unit, parse and execute the instructions of the software program, and process the data of the software program. When data needs to be transmitted wirelessly, the processor performs baseband processing on the data to be transmitted and outputs the baseband signal to the radio frequency (RF) circuit. The RF circuit processes the baseband signal to obtain the RF signal and transmits the RF signal outward in the form of electromagnetic waves through the antenna. When data is sent to the terminal device, the RF circuit receives the RF signal through the antenna. This RF signal is further converted into a baseband signal and output to the processor. The processor converts the baseband signal back into data and processes the data.

[0396] For ease of explanation, Figure 10 Only one memory and processor are shown. In actual terminal devices, multiple processors and memories may exist. Memory can also be called storage medium or storage device, etc., and this application embodiment does not limit this.

[0397] In one embodiment, the antenna is used to perform the operations performed by the transceiver unit 801 in the above embodiments. The processor can be used to perform the operations performed by the processing unit 802 in the above embodiments.

[0398] This application also provides a computer-readable storage medium storing instructions that, when executed by a computer or processor, can implement the relevant steps in the communication method provided in the above-described method embodiments.

[0399] This application also provides a computer program product including instructions that, when executed by a computer or processor, cause one or more steps of any of the above-described communication methods to be performed. If the constituent modules of the aforementioned devices are implemented as software functional units and sold or used as independent products, they can be stored in a computer-readable storage medium.

[0400] This application provides a chip or chip system including at least one processor for calling and executing instructions stored in a memory, causing a communication device with the chip installed to perform any of the methods described above.

[0401] This application also provides another chip, including a processor and a memory, wherein the processor is used to call and execute instructions stored in the memory, causing a communication device with the chip installed to perform any of the methods described above.

[0402] This application embodiment also provides another chip, including: an input interface, an output interface, and a processing circuit. The input interface, the output interface, and the processing circuit are connected via internal connection paths. The processing circuit is used to execute any of the methods described above. Optionally, the chip also includes a memory. The input interface, the output interface, the processor, and the memory are connected via internal connection paths. The processor is used to execute code in the memory. When the code is executed, the processor is used to execute any of the methods described above.

[0403] This application also provides another chip system, including at least one processor and a communication interface, wherein the communication interface and at least one processor are interconnected via a line, and the at least one processor is used to run computer programs or instructions to perform any of the methods described above. This chip system may be composed of chips, or may include chips and other discrete devices.

[0404] This application also provides a communication system, which includes a first communication device and a second communication device, as detailed in the following description. Figure 4 The method shown.

[0405] It should be understood that the memory mentioned in the embodiments of this application can be volatile memory or non-volatile memory, or may include both volatile and non-volatile memory. Non-volatile memory can be a hard disk drive (HDD), a solid-state drive (SSD), ROM, programmable read-only memory (PROM), erasable programmable read-only memory (EPROM), electrically erasable programmable read-only memory (EEPROM), or flash memory. Volatile memory can be RAM, which is used as an external cache. Memory is any other medium capable of carrying or storing desired program code having an instruction or data structure form and accessible by a computer, but is not limited thereto. The memory in the embodiments of this application can also be a circuit or any other device capable of implementing a storage function for storing program instructions and / or data.

[0406] It should also be understood that the processor mentioned in the embodiments of this application can be a central processing unit (CPU), or other general-purpose processors, digital signal processors (DSPs), application-specific integrated circuits (ASICs), field-programmable gate arrays (FPGAs), or other programmable logic devices, discrete gate or transistor logic devices, discrete hardware components, etc. A general-purpose processor can be a microprocessor, or any conventional processor, etc.

[0407] It should be noted that when the processor is a general-purpose processor, DSP, ASIC, FPGA, or other programmable logic device, discrete gate or transistor logic device, or discrete hardware component, the memory (storage module) is integrated into the processor.

[0408] It should be noted that the memories described herein are intended to include, but are not limited to, these and any other suitable types of memories.

[0409] Those skilled in the art will recognize that the units and algorithm steps of the various examples described in conjunction with the embodiments provided herein can be implemented in electronic hardware, or a combination of computer software and electronic hardware. Whether these functions are implemented in hardware or software depends on the specific application and design constraints of the technical solution. Those skilled in the art can use different methods to implement the described functions for each specific application, but such implementation should not be considered beyond the scope of this application.

[0410] In the several embodiments provided in this application, it should be understood that the disclosed systems, apparatuses, and methods can be implemented in other ways. For example, the apparatus embodiments described above are merely illustrative; for instance, the division of units is only a logical functional division, and in actual implementation, there may be other division methods. For example, multiple units or components may be combined or integrated into another system, or some features may be ignored or not executed. Furthermore, the coupling or direct coupling or communication connection shown or discussed may be through some interfaces; the indirect coupling or communication connection between apparatuses or units may be electrical, mechanical, or other forms.

[0411] The units described as separate components may or may not be physically separate. The components shown as units may or may not be physical units; that is, they may be located in one place or distributed across multiple network units. Some or all of the units can be selected to achieve the purpose of this embodiment, depending on actual needs.

[0412] In addition, the functional units in the various embodiments of this application can be integrated into one processing unit, or each unit can exist physically separately, or two or more units can be integrated into one unit.

[0413] The steps in the methods of this application can be adjusted, combined, or deleted according to actual needs. Each step in each embodiment can be partially performed (for example, the communication device may not perform the steps performed by the communication device in the above embodiments). The execution order of different steps can be changed. The embodiments described herein can be combined with other embodiments, different embodiments can be combined with each other, and different steps of different embodiments herein can be combined.

[0414] The modules / units in the device of this application embodiment can be merged, divided, and deleted according to actual needs.

[0415] In this document, the term "embodiment" means that a particular feature, structure, or characteristic described in connection with an embodiment may be included in at least one embodiment of this application. The appearance of this phrase in various places in the specification does not necessarily refer to the same embodiment, nor is it a separate or alternative embodiment mutually exclusive with other embodiments.

[0416] In this application, it may refer to a communication protocol or specification, such as the 3GPP communication protocol.

[0417] In this application, unless otherwise specified, "at least one" means "one or more".

[0418] The terms “first,” “second,” “third,” “fourth,” etc. (if present) in the embodiments of this application are used to distinguish similar objects and are not necessarily used to describe a specific order or sequence.

[0419] In the embodiments of this application, "including" can refer to a relationship of inclusion or an equality relationship. For example, A includes B, which could mean that A includes B and may also include other content, or that A and B are the same content.

[0420] In the description of this application, unless otherwise stated, " / " indicates that the objects before and after it are in an "or" relationship. For example, A / B can mean A or B. "And / or" in this application is merely a description of the relationship between the related objects, indicating that three relationships can exist. For example, A and / or B can represent: A alone, A and B simultaneously, and B alone, where A and B can be singular or plural. Furthermore, in the description of this application, unless otherwise stated, "multiple" means two or more. "At least one of the following" or similar expressions refer to any combination of these items, including any combination of singular or plural items. For example, at least one of a, b, or c can represent: a, b, c, ab, ac, bc, or abc, where a, b, and c can be single or multiple.

[0421] In this application, the words "exemplarily" or "for example" are used to indicate that they are examples, illustrations, or descriptions. Any embodiment or design that is described as "exemplarily" or "for example" in this application should not be construed as being more preferred or advantageous than other embodiments or design options. Rather, the use of the words "exemplarily" or "for example" is intended to present the relevant concepts in a specific manner.

[0422] In the description of this application, "instruction" can include direct and indirect instructions, as well as explicit and implicit instructions. The information indicated by a certain piece of information is called the information to be instructed. In the specific implementation process, there are many ways to instruct the information to be instructed. For example, the information to be instructed can be directly instructed, such as by instructing the information itself or its index. Alternatively, the information to be instructed can be indirectly indicated by instructing other information, where there is a relationship between the indicated other information and the information to be instructed. Another example is that only a part of the information to be instructed can be indicated, while the other parts are known or pre-agreed upon. Furthermore, the instruction of specific information can be achieved by using a pre-agreed (such as an agreement) arrangement of various pieces of information, thereby reducing the instruction overhead to some extent.

[0423] It is understood that in the description of this application, "when," "if," and "if" all refer to the device making a corresponding action under certain objective circumstances, and are not time-limited, nor do they require the device to make a judgment action when it is implemented, nor do they mean that there are other limitations.

[0424] It should be understood that in the various embodiments of this application, the order of the above-mentioned processes does not imply the order of execution. The execution order of each process should be determined by its function and internal logic, and should not constitute any limitation on the implementation process of the embodiments of this application.

Claims

1. A communication method characterized by comprising: include: Determine the first parameter of the Channel State Information (CSI) report; wherein the first parameter is less than or equal to 1, and the first parameter of the CSI report is used to scale the resource size occupied by the CSI report; A first physical uplink shared channel (PUSCH) is transmitted. The first PUSCH is multiplexed by the CSI report after the resource size has been scaled by the first parameter. The multiplexed first PUSCH is extended by an orthogonal overlay code (OCC) sequence, which is associated with the first PUSCH.

2. A communication method characterized by comprising: include: Determine the first parameter of the Channel State Information (CSI) report; wherein the first parameter is less than or equal to 1, and the first parameter of the CSI report is used to scale the resource size occupied by the CSI report; The first physical uplink shared channel (PUSCH) is received. The first PUSCH is multiplexed by the CSI report after the resource size has been scaled by the first parameter. The multiplexed first PUSCH is extended by an orthogonal coverage code (OCC) sequence, which is associated with the first PUSCH.

3. The method according to claim 1 or 2, characterized in that, The first parameter includes a bias value and / or a scaling factor.

4. The method according to any one of claims 1 to 3, characterized in that, The first parameter is related to one of the following: the configuration parameters of the OCC sequence, and the parameters in the downlink control information (DCI).

5. The method of claim 4, wherein, The configuration parameters of the OCC sequence include at least one of the following: the code length of the OCC sequence, the index of the OCC sequence, and the enable indicator of the OCC sequence; The enable indicator of the OCC sequence is used to indicate that the OCC sequence is used for extension, and the information carried on the first PUSCH is extended by multiplying the information by the OCC element corresponding to the resource unit occupied by the first PUSCH in the OCC sequence.

6. The method of claim 4, wherein, The parameters in the DCI include at least one of the following: the indicator value of the bias value, the antenna port, the redundancy version, and the modulation and coding scheme (MCS).

7. The method according to any one of claims 1 to 6, characterized in that, The scaling factor is less than 0.

5.

8. The method according to any one of claims 1 to 7, characterized in that, The first parameter is activated when the OCC sequence is extended.

9. The method according to any one of claims 1 to 8, characterized in that, Also includes: A second parameter is determined for the HARQ-ACK information, which is used to scale the resource size occupied by the HARQ-ACK information.

10. The method according to any one of claims 1 to 9, characterized in that, The first PUSCH is also reused by HARQ-ACK information.

11. The method of claim 10, wherein, The HARQ-ACK information and the CSI report are carried on the Physical Uplink Shared Channel (PUCCH). The resources occupied by the PUCCH overlap with K resource units. The K resource units are contained in M ​​resource units. Each of the M resource units is used to carry uplink data via PUSCH. M and K are integer multiples of L, where L is the code length of the OCC sequence. The method includes: When M=L, the first PUSCH is transmitted on each of the K resource units.

12. The method of claim 11, wherein, The method includes: When M>K, the PUSCH is not transmitted on the K resource units, and a second PUSCH is transmitted on the time units other than the K time units in the M resource units. The second PUSCH carries the data after the uplink data has been extended by the OCC sequence.

13. A communication device, characterized in that, include: A processing unit is configured to determine a first parameter of a Channel State Information (CSI) report; wherein the first parameter is less than or equal to 1, and the first parameter of the CSI report is used to scale the resource size occupied by the CSI report; The transceiver unit is used to transmit a first physical uplink shared channel (PUSCH), which is multiplexed by the CSI report after the resource size has been scaled by the first parameter, and the multiplexed first PUSCH is extended by an orthogonal overlay code (OCC) sequence, which is associated with the first PUSCH.

14. A communications device, characterized by include: A processing unit is configured to determine a first parameter of a Channel State Information (CSI) report; wherein the first parameter is less than or equal to 1, and the first parameter of the CSI report is used to scale the resource size occupied by the CSI report; The transceiver unit is used to receive a first physical uplink shared channel (PUSCH), which is multiplexed by the CSI report after the resource size has been scaled by the first parameter, and the multiplexed first PUSCH is extended by an orthogonal coverage code (OCC) sequence, which is associated with the first PUSCH.

15. The apparatus of claim 13 or 14, wherein, The first parameter includes a bias value and / or a scaling factor.

16. The apparatus of any one of claims 13-15, wherein, The first parameter is related to one of the following: the configuration parameters of the OCC sequence, and the parameters in the downlink control information (DCI).

17. The apparatus of claim 16, wherein, The configuration parameters of the OCC sequence include at least one of the following: the code length of the OCC sequence, the index of the OCC sequence, and the enable indicator of the OCC sequence; The enable indicator of the OCC sequence is used to indicate that the OCC sequence is used for extension, and the information carried on the first PUSCH is extended by multiplying the information by the OCC element corresponding to the resource unit occupied by the first PUSCH in the OCC sequence.

18. The apparatus of claim 16, wherein, The parameters in the DCI include at least one of the following: the indicator value of the bias value, the antenna port, the redundancy version, and the modulation and coding scheme (MCS).

19. The apparatus according to any one of claims 13 to 18, characterized in that, The scaling factor is less than 0.

5.

20. The apparatus of any one of claims 13-19, wherein, The first parameter is activated when the OCC sequence is extended.

21. The apparatus of any one of claims 13-20, wherein, The processing unit is further configured to determine a second parameter of the HARQ-ACK information, wherein the second parameter of the HARQ-ACK information is used to scale the resource size occupied by the HARQ-ACK information.

22. The apparatus of any one of claims 13-21, wherein, The first PUSCH is also reused by HARQ-ACK information.

23. The apparatus of claim 22, wherein, The HARQ-ACK information and the CSI report are carried on the Physical Uplink Shared Channel (PUCCH). The time domain resources occupied by the PUCCH overlap with K time units. The K time units are contained in M ​​time units. Each of the M time units is used to carry uplink data via PUSCH. M and K are integer multiples of L, where L is the code length of the OCC sequence. The transceiver unit is used to transmit the first PUSCH in each of the K time units when M=L.

24. The apparatus of claim 23, wherein, The transceiver unit is configured to, when M>K, not transmit the PUSCH on the K resource units, and transmit a second PUSCH on the time units other than the K time units in the M time units, the second PUSCH carrying the uplink data after being extended by the OCC sequence.

25. A communications device, characterized by It includes at least one processor, which, when running, causes the method according to any one of claims 1 to 12 to be performed.

26. A computer readable storage medium or computer program product, characterized in that, It includes a computer program or instructions that, when run, cause the method according to any one of claims 1 to 12 to be performed.

27. A chip or chip system, characterized by It includes at least one processor for retrieving and executing instructions stored in a memory, causing a communication device equipped with a chip or chip system to perform the method as described in any one of claims 1 to 12.

28. A communication system, characterized by It includes a first communication device and a second communication device, wherein the first communication device is used to perform the method according to any one of claims 1, 3 to 12, and the second communication device is used to perform the method according to any one of claims 2 to 12.