Communication method and application apparatus

Abstract

Embodiments of the present application provide a communication method and an application apparatus, which can be applied to the field of satellite communications, such as NTN. The method comprises: upon receiving first information, determining a configuration parameter of an OCC sequence on the basis of the first information. In this way, the configuration parameter of the OCC sequence can be clarified. Data to be sent on a PUSCH is processed by means of the OCC sequence, so that data extension and repeated transmission can be realized, and the system capacity and system performance can be improved.

Description

Communication methods and application devices

[0001] This application claims priority to Chinese Patent Application No. 202510127980.X, filed on January 27, 2025, entitled "Communication Method and Application Device", the entire contents of which are incorporated herein by reference. Technical Field

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

[0003] 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, NTN network equipment needs to cover a much larger land area and serve a large number of terminal devices than terrestrial network base stations. In uplink communication scenarios, coverage enhancement technology is required.

[0004] However, the essence of coverage enhancement technology is to reuse time-frequency resources to transmit information from terminal devices, which results in the consumption of more resources, increases the information transmission time, and reduces the system capacity and the throughput of each terminal device. Summary of the Invention

[0005] This application discloses a communication method and application apparatus that can clearly define the configuration parameters of the orthogonal cover code (OCC) sequence used for extending the physical uplink shared channel (PUSCH). By processing the data to be transmitted on the PUSCH through the OCC sequence, data extension and repeated transmission can be achieved, thereby improving system capacity and facilitating correct data reception on the network side.

[0006] Firstly, this application discloses a first communication method, which 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-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:

[0007] The first communication device receives first information; wherein the first information is used to indicate the configuration parameters of the Orthogonal Covering Code (OCC) sequence; the first communication device transmits uplink data on the resource unit occupied by the Physical Uplink Shared Channel (PUSCH), the uplink data being the data to be transmitted on the PUSCH processed by the OCC element corresponding to the resource unit in the OCC sequence. In this way, the configuration parameters of the OCC sequence can be clearly defined. By processing the data to be transmitted on the PUSCH using the OCC sequence, data expansion and repeated transmission can be achieved, thereby improving system capacity and system performance.

[0008] Secondly, this application discloses a second communication method, which 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 second communication device sends first information, which indicates the configuration parameters of the Orthogonal Cover Code (OCC) sequence. The second communication device receives uplink data on a resource unit occupied by the Physical Uplink Shared Channel (PUSCH), the uplink data being the data to be transmitted on the PUSCH processed by the OCC element corresponding to the resource unit in the OCC sequence. This clarifies the configuration parameters of the OCC sequence. Processing the data to be transmitted on the PUSCH using the OCC sequence enables data expansion and repeated transmission, thereby improving system capacity and performance.

[0010] 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 of an OCC sequence refers to the number of bits in an OCC sequence. A bit in an OCC sequence may be called an OCC element, and the code length may be called the spreading factor or spreading 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.

[0011] In this application, information may include data and / or signaling. The information to be transmitted by different terminal devices is processed by the corresponding OCC element in their configured OCC sequence. That is, the information to be transmitted by each terminal device is processed by the corresponding OCC element in its configured OCC sequence. The processing may include extension, code division multiplexing, multiplication, etc., and is not limited here. In some cases, no processing may be performed. For example, if the OCC element is 1, the transmitted information may be sent without processing, i.e., the information itself may be sent. In some cases, the above processing may also be an inversion operation. For example, if the OCC element is -1, the processing of the information to be transmitted may be an inversion operation on each information element of the information to be transmitted. In some cases, in addition to processing by OCC elements, the information to be transmitted may also undergo encoding, DFT, etc., and is not limited here.

[0012] In this application, the information to be transmitted is processed via the OCC element corresponding to the information to be transmitted in the OCC sequence. Sometimes it is described as the information to be transmitted being processed via the OCC sequence. Processing via the OCC sequence can also be described as using the OCC sequence, or as performing OCC extension, or as performing code division extension or code division multiplexing, etc. It can also be described as performing OCC extension and repetition, or as processing the information to be transmitted using the OCC element corresponding to the information to be transmitted in the OCC sequence. In this application, the resource element can include a resource element (RE), or it can include a time element. Optionally, the time element can include at least one of the following: a time slot, a micro-time slot, a symbol, or it can include a symbol group consisting of multiple symbols, etc., without limitation.

[0013] In conjunction with the first or second aspect, in some possible implementations, the configuration parameters of the OCC sequence include at least one of the code length of the OCC sequence and the index of the OCC sequence. It is understood that when the first information is used to indicate the index and code length of the OCC sequence, the OCC sequence and its code length can be determined. When the first information is used solely to indicate the index of the OCC sequence, the OCC sequence corresponding to the index indicated by the first information and its code length can be determined based on the mapping relationship between the OCC sequence index and the OCC sequence. When the first information is used solely to indicate the code length of the OCC sequence, the code length of the OCC sequence can be determined; if a mapping relationship exists between the code length and the OCC sequence, the OCC sequence can be determined based on the code length indicated by the first information.

[0014] The mapping relationship between the index of an OCC sequence and the OCC sequence itself can be a mapping relationship between the index of the OCC sequence and all or some of the OCC elements in the OCC sequence. The following example illustrates the mapping relationship between the index of an OCC sequence and some of its OCC elements. For instance, if an OCC sequence of length 4 is obtained by repeating an OCC sequence of length 2, the OCC sequence that maps to the index corresponding to the OCC sequence of length 4 can be an OCC sequence of length 2, such as [1 -1]. Therefore, the OCC sequence corresponding to length 4 can be determined as [1 -1 1 -1], and the OCC sequence corresponding to length 2 can be [1 -1]. These two OCC sequences can correspond to the same index, and the OCC sequence indicated by that index is [1 -1]. For example, the index corresponding to an all-1 sequence in an OCC sequence can indicate that the OCC sequence is 1, or not indicate the OCC sequence at all. In this case, if the code length is 2, the OCC sequence is [1 1]; if the code length is 4, the OCC sequence is [1 1 1 1], and so on. The mapping relationship between the above index and the OCC sequence is only an example, and this application does not limit it. In some other possible implementations, the OCC sequence can be indicated by other OCC sequence indication information besides the index, such as the OCC sequence identifier, the OCC sequence sequence, etc., which are not limited here.

[0015] The mapping relationship between the code length of an OCC sequence and the OCC sequence can be an example of the mapping relationship between some OCC elements and the code length mentioned above, or it can be a correspondence between the code length of an OCC sequence and an orthogonal matrix, and a correspondence between the sequence corresponding to the value of each row or column in the orthogonal matrix and different communication devices, etc., which is not limited here. In this way, the OCC sequence corresponding to the first communication device can be determined from the orthogonal matrix corresponding to the code length of the OCC sequence.

[0016] In conjunction with the first or second aspect, in some possible implementations, the configuration parameters of the OCC sequence further include an OCC enable indicator (such as OCC-enabled) for indicating that the OCC sequence is used to process the data to be transmitted.

[0017] For example, the OCC enable indicator can be set to 0 to indicate that the first communication device uses the OCC sequence to process the data to be transmitted, and 1 to indicate that the first communication device does not use the OCC sequence to process the data to be transmitted. Alternatively, the OCC enable indicator can be set to 1 to indicate that the first communication device uses the OCC sequence to process the data to be transmitted, and 0 to indicate that the first communication device does not use the OCC sequence to process the data to be transmitted. As another example, the OCC enable indicator can be set to yes or enabled to indicate that the first communication device uses the OCC sequence to process the data to be transmitted, and no or disabled to indicate that the first communication device does not use the OCC sequence to process the data to be transmitted.

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

[0019] In this application, the information to be transmitted is carried on the PUSCH. The information carried on the PUSCH is usually referred to as data, such as data from the uplink shared channel (UL-SCH). This application does not limit the data type. The resource units occupied by the PUSCH can be determined through time-domain resource configuration, which will not be described in detail here.

[0020] 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. The first information may or may not be used to indicate other information besides the configuration parameters used to indicate the OCC sequence, and is not limited thereto. For example, the first information may include the OCC sequence, thereby allowing the code length and / or index of the OCC sequence to be determined based on the OCC sequence. Where the first information includes the OCC sequence, the first information may not include the code length and / or index of the OCC sequence.

[0021] In some possible implementations, the first information is also used to indicate the transmission mode of the uplink data. The uplink data is the data to be transmitted on the PUSCH multiplied by the OCC elements corresponding to resource units in the OCC sequence. The transmission mode of the uplink data can be indicated by the redundancy version (RV) field in the downlink control information (DCI), or by other information, which is not limited here. The transmission mode of the uplink data can be understood as the transmission mode of the data corresponding to each redundancy version when considering the processing of the data to be transmitted via the OCC elements in the OCC sequence, and can be represented by the number of resource units occupied by the data corresponding to each redundancy version. This application does not limit the number of resource units occupied by the data corresponding to each redundancy version, and it can be an integer multiple of L. The default execution order of the redundancy version cycle (RV cyling) is RV0, RV2, RV3, RV1.

[0022] This invention does not limit the execution order in RV cyling. That is, in addition to the default execution order (RV0, RV2, RV3, RV1) described above, different execution orders are also possible, such as RV1, RV2, RV3, RV0. For example, data corresponding to RV1 can be sent first, and if resources are available, data corresponding to RV2 can be sent, data corresponding to RV3 can be sent, data corresponding to RV0 can be sent, and data corresponding to RV1 can be sent, etc.

[0023] In Method 1, the uplink data is transmitted by transmitting uplink data corresponding to at least one redundant version, processed by each OCC element in the OCC sequence. The number of resource units occupied by the data corresponding to each redundant version is L. It can be understood that transmitting data according to the principle of repeating the transmission of each redundant version a maximum of L times facilitates network despreading to obtain the correct data.

[0024] Method 2: The uplink data is transmitted by transmitting data corresponding to a redundant version, processed by each OCC element in the OCC sequence. In other words, the redundant versions of the uplink data are identical. This application does not limit the redundant version; for example, the redundant version can be RV2 or others. It is understood that transmitting data with the same redundant version facilitates network-side despreading to obtain the correct data.

[0025] Method 3: The uplink data transmission method involves transmitting data corresponding to at least one redundant version after processing by each OCC element in the OCC sequence. The number of resource units occupied by the data corresponding to each redundant version is K, and K is a fixed value. That is, the data corresponding to each redundant version is transmitted with a fixed number of repetitions. This application does not limit the size of K; K is an integer multiple of L, where L is the code length of the OCC sequence. It can be understood that transmitting the data corresponding to the same redundant version with a fixed number of repetitions facilitates network-side despreading to obtain the correct data. At the same time, it also enables the network side to simultaneously schedule terminal devices with an OCC sequence code length of 2 and terminal devices with an OCC sequence code length of 4 on the same resources.

[0026] The above three methods are merely examples of uplink data transmission methods. In reality, other uplink data transmission methods may also exist, which will not be elaborated upon here. It can be understood that the uplink data transmission method can be determined through the first information. Thus, after the first communication device sends uplink data processed by the OCC elements in the OCC sequence based on this transmission method, the network side can despread the data based on this transmission method to obtain the correct data.

[0027] In some possible implementations, the uplink data transmission mode can be indicated by 2 bits in the RV field. These 2 bits can be used to indicate at least one of the aforementioned modes one, two, and three, or other transmission modes. Thus, indicating the uplink data transmission mode through the RV field avoids introducing new indications and saves signaling overhead.

[0028] In some other possible implementations, the uplink data transmission mode can be indicated by one bit in the RV field. For example, one bit in the RV can indicate one of {Opt1, Opt2}. Opt1 can be mode one as described above, and Opt2 can be mode two as described above. Thus, by indicating the uplink data transmission mode using the RV, the introduction of new indications can be avoided, saving signaling overhead. This application does not limit the other bit in the RV field that is not used to indicate the uplink data transmission mode; it can indicate other information or not indicate any information at all. Furthermore, it does not limit the content of the indicated information or the transmission mode.

[0029] In some possible implementations, the configuration parameters of the OCC sequence can be indicated by 1 bit in the RV field. For example, the 1 bit in the RV field is used to indicate the code length of the OCC sequence (e.g., a value of 0 indicates OCC sequence 2, and a value of 1 indicates OCC sequence code length 4) or the OCC enable indication (e.g., a value of 0 indicates using the OCC sequence to process the data to be transmitted, and a value of 1 indicates not using the OCC sequence to process the data to be transmitted). As another example, when the OCC sequence code length is 2, the 1 bit in the RV field can be used to indicate the index of the OCC sequence, such as a value of 0 indicating the aforementioned W1, and a value of 1 indicating the aforementioned W2, etc. In this way, the configuration parameters of the OCC sequence can be indicated by the RV field, avoiding the introduction of new indications and saving signaling overhead.

[0030] In this application, one bit of the two bits occupied by the RV field can be used to indicate the uplink data transmission mode, and the other bit can be used to indicate the configuration parameters of the OCC sequence. Alternatively, one bit of the RV field can be used to indicate the uplink data transmission mode, while the other bit is not used to indicate the configuration parameters of the OCC sequence. Alternatively, one bit of the RV field can be used to indicate the configuration parameters of the OCC sequence, while the other bit can be used to indicate the uplink data transmission mode. Alternatively, both bits of the RV field can be used to indicate the uplink data transmission mode, etc. This application does not limit the content indicated by the two bits occupied by the RV field.

[0031] In this application, the OCC enable indication is optional information. If there is no OCC enable indication, the decision to use the OCC sequence for processing the data to be transmitted can be determined based on whether the first information indicates the code length of the OCC sequence. For example, if the first information indicates the code length of the OCC sequence, the first communication device defaults to using the OCC sequence for processing the data to be transmitted. Conversely, if the first information does not indicate the code length of the OCC sequence, the first communication device defaults to not using the OCC sequence for processing the data to be transmitted. If the OCC enable indication is that the OCC sequence is not used for processing the data to be transmitted, then even if the first information indicates the code length and / or index of the OCC sequence, the first communication device also does not use the OCC sequence for processing the data to be transmitted, thus allowing the first communication device to transmit the data carried on the PUSCH without OCC extension.

[0032] In conjunction with the first or second aspect, in some possible implementations, the first information indicates the configuration parameters of the OCC sequence using 3 or 4 bits of information. That is, 3 or 4 bits of information in the first information are used to indicate the configuration parameters of the OCC sequence. If the number of bits occupied by the first information is greater than 3 or 4, the remaining information may be used to indicate other information, or may not indicate any information, which is not limited here.

[0033] In some possible implementations, the 4 bits used to indicate the configuration parameters of the OCC sequence can be split into three parts. These three parts occupy 1 bit, 1 bit, and 2 bits respectively. One bit can serve as an OCC enable indicator, indicating whether the first communication device uses the OCC sequence without OCC extension to transmit the data carried on the PUSCH. Another bit of the 4 bits can be used to indicate the code length of the OCC sequence, such as 2 or 4 bits. The remaining 2 bits of the 4 bits can be used to indicate the index of the OCC sequence. For example, when the code length of the OCC sequence is 2, the OCC sequence corresponding to index 0 is [1 1], and the OCC sequence corresponding to index 1 is [1 -1]. When the code length of the OCC sequence is 4, the OCC sequence corresponding to index 0 is [1 1 1 1], the OCC sequence corresponding to index 1 is [1 -1 1 -1], the OCC sequence corresponding to index 2 is [1 1 -1 -1], and the OCC sequence corresponding to index 1 is [1 -1 -1 1].

[0034] For example, 2 bits can be 00, 01, 10, and 11. 00 indicates an OCC sequence of all 1s, 01 indicates an OCC sequence of [1 -1], 10 indicates an OCC sequence of [1 1 -1 -1], and 11 indicates an OCC sequence of [1 -1 -1 1]. Thus, by representing possible OCC sequences with a small number of values, signaling overhead can be saved.

[0035] For example, the 2 bits can be 01, 10, and 11 as mentioned above, excluding 00. A value of 00 in the first information can indicate that the OCC sequence is an all-1 sequence. Thus, the network side does not need to directly configure the index of the OCC sequence corresponding to the all-1 sequence. Instead, it determines whether the index in the first information corresponds to an all-1 sequence by the correspondence between the OCC sequence corresponding to the all-1 sequence and the index corresponding to that OCC sequence, further saving signaling overhead.

[0036] The above indices and their corresponding OCC sequences are merely examples, and this application does not limit them. When the code length is 2, the configuration parameters of the OCC sequence are indicated by 3 bits, and these 3 bits are not split. The value corresponding to the 3 bits is used to indicate the code length and / or index of the OCC sequence, or it can also be used to indicate the OCC enable indication. Alternatively, when the code length is 2, each configuration parameter can be indicated by 1 bit. Therefore, the code length, index, and enable indication of the OCC sequence can be indicated by 3 bits, or by 2 bits, or by 1 bit. Alternatively, when the code length is 2, 1 bit is used to indicate the code length of the OCC sequence, and 2 bits are used to indicate the index and enable indication of the OCC sequence. Alternatively, when the code length is 2, 1 bit is used to indicate the index of the OCC sequence, and 1 bit can also be used to indicate the OCC enable indication, etc., without limitation. The configuration parameters of the OCC sequence may not include the OCC enable indication.

[0037] With a code length of 4, the configuration parameters of the OCC sequence are indicated by 3 bits, and these 3 bits are not split. The value of these 3 bits is used to indicate the code length and / or index of the OCC sequence, or it can also be used to indicate the OCC enable indicator. Alternatively, with a code length of 4, the code length of the OCC sequence can be indicated by 1 bit and / or the index of the OCC sequence can be indicated by 2 bits, and the OCC enable indicator can also be indicated by 1 bit. Alternatively, with a code length of 4, the code length of the OCC sequence can be indicated by 1 bit, and the index of the OCC sequence and the OCC enable indicator can also be indicated by 3 bits. Alternatively, with a code length of 4, the index of the OCC sequence can be indicated by 2 bits, and the OCC enable indicator can also be indicated by 1 bit; there are no limitations here.

[0038] The correspondence between the number of bits and the configuration parameters of the OCC sequence in the above examples is merely illustrative and not intended to be limiting. The above three parts can reside in one or more first pieces of information. When three parts of a 4-bit information are split into one first piece of information, this application does not limit the order in which these three parts are sent. When three parts of a 4-bit information are split into multiple first pieces of information, this application does not limit the order in which each first piece of information is sent to the first communication device. Three bits can also be split and used separately to indicate the configuration parameters of the OCC sequence. The split bits can reside in one or more first pieces of information, and this application does not limit the information corresponding to the configuration parameters of each OCC sequence in one first piece of information or the order in which each first piece of information is sent.

[0039] In conjunction with the first or second aspect, in some possible implementations, the first information is carried in at least one of the following: Downlink Control Information (DCI), Radio Resource Control (RRC) signaling, and Medium Access Control (MAC) Control Element (CE) signaling. This application exemplifies the use of the first information carried in DCI and / or RRC signaling. For cases where it is carried in MAC CE signaling, one approach can be referenced, for example, replacing DCI or RRC signaling with MAC CE signaling.

[0040] For example, the code length of the OCC sequence can be indicated by 1 bit in the RRC signaling. If the OCC sequence code length is 2, the index of the OCC sequence can be indicated by 1 bit in the DCI, or the index of the OCC sequence and the enable indication of the OC column can be indicated by 2 bits in the DCI. If the OCC sequence code length is 4, the index of the OCC sequence can be indicated by 2 bits in the DCI, or the index of the OCC sequence and the enable indication of the OCC can be indicated by 3 bits in the DCI. Alternatively, only the code length of the OCC sequence can be indicated by 1 bit in the RRC signaling, without indicating the enable indication of the OCC. Furthermore, the DCI may include information indicating the enable indication of the OCC and / or the code length of the OCC sequence, etc. This application does not limit the signaling carrying the first information.

[0041] In conjunction with the first or second aspect, in some possible implementations, when the first information is carried in the DCI, the DCI includes a hybrid automatic repeat request (HARQ) process number, which is used to indicate the configuration parameters of the OCC sequence. Thus, by indicating the configuration parameters of the OCC sequence through the HARQ process number, no new indication information is introduced, saving signaling overhead. The HARQ process number can indicate the configuration parameters of all OCC sequences, or it can indicate the configuration parameters of some OCC sequences, with the remaining configuration parameters indicated by other first information.

[0042] This implementation can be applied to situations where the network side provides one or more configuration information for grant type 2 PUSCH transmissions, or to situations where the network side configures grant type 1 PUSCH transmissions, or even to situations where PUSCH transmissions are dynamically scheduled with UL grants in DCI; no limitation is made here. The terminal device can obtain a configuration provided by the network side for grant type 2 PUSCH transmissions based on the HARQ process number. In this case, using the HARQ process number to indicate the configuration parameters of the OCC sequence can reduce signaling overhead.

[0043] In conjunction with the first or second aspect, in some possible implementations, the configuration parameters of the OCC sequence include a first parameter and a second parameter. When the first information is carried in the DCI and the RRC signaling, the HARQ process number is used to indicate the first parameter, and the second parameter is indicated through the RRC signaling. The first information may not be indicated through the HARQ process number, but rather through other information in the DCI, such as RV, antenna port, etc. The second parameter can be configured through ConfiguredGrantConfig or rrc-ConfiguredUplinkGrant in the RRC, and this application does not limit this. Thus, the configuration parameters of the OCC sequence can be indicated jointly by the HARQ process number in the DCI and the RRC signaling.

[0044] In conjunction with the first or second aspect, in some possible implementations, where the first information is carried in the RRC signaling, the RRC signaling includes a configured authorization configuration index, ConfiguredGrantConfigIndex, which is used to indicate the configuration parameters of the OCC sequence.

[0045] The implementation of using `ConfiguredGrantConfigIndex` to indicate the configuration parameters of the OCC sequence can be applied to situations where the network side provides one or more configuration information for grant type 2 PUSCH transmissions, or to situations where the network side configures grant type 1 PUSCH transmissions, or even to situations where the PUSCH transmission is dynamically scheduled with UL authorization in DCI; no limitation is made here. The terminal device can obtain multiple configurations provided by the network side for grant type 2 PUSCH transmissions based on the configuration of `ConfiguredGrantConfigIndex`. In this case, indicating the configuration parameters of the OCC sequence through `ConfiguredGrantConfigIndex` can reduce signaling overhead.

[0046] This application may also indicate the configuration parameters of the OCC sequence through other information, such as RV, antenna port, n SCID The following parameters are not limited here: the value of the code division multiplexing (CDM) group of the downlink demodulation reference signal (DMRS) without data, the value λ of the CDM group, the parameter Δ, the extra position of DMRS, the DMRS type, the PUSCH DMRS time index l′, the sounding reference signal (SRS) request message, the SRS resource setting indication, the SRS offset indication, the phase tracking reference signal (PT-RS)-DMRS association, the precoding information and layer number, the channel state information (CSI) request, the transmission power control (TPC) command of the PUSCH schedule, the code block group (CBG) transmission information, the beta_offset indication, etc.

[0047] In conjunction with the first or second aspect, in some possible implementations, the configuration parameters of the OCC sequence are included in the time domain resource assignment (TDRA) of the PUSCH. This time domain resource assignment may also be a list of time domain resources containing one or more time domain resource assignments. The time domain resource assignment may be carried in at least one of RRC signaling, DCI, or MAC CE signaling, and is not limited thereto.

[0048] This application does not limit the position of the OCC sequence configuration parameters in the time-domain resource configuration. They can be included in the time-domain resource parameters in protocol R15 or R16, such as in information elements like PUSCH-TimeDomainResourceAllocation, PUSCH-TimeDomainResourceAllocation-r16, PUSCH-TimeDomainResourceAllocationList, and PUSCH-TimeDomainResourceAllocationList-r16. These information elements can be set in existing time-domain resource configurations or lists, or in new sets of information elements; no limitation is imposed here.

[0049] In some possible implementations, the time-domain resource configuration list includes one or more time-domain resource configurations. Each time-domain resource configuration in the list may correspond to the same configuration parameters for the same OCC sequence, or it may correspond to a separate set of configuration parameters for an OCC sequence, such as a list including configuration parameters for at least one OCC sequence.

[0050] In some possible implementations, if the PUSCH configuration information does not include a time-domain resource configuration for the PUSCH, the first communication device can use default information to determine the configuration parameters of the OCC sequence. The PUSCH configuration information may include configurations applicable to all PUSCHs (e.g., PUSCH-ConfigCommon) or configurations applicable to a single PUSCH (e.g., pusch-Config), and the default information may be a default table (e.g., Default A), etc., without limitation. The code length of the OCC sequence in the default OCC sequence configuration parameters can be 2, also without limitation. Alternatively, the first communication device can use the default information to determine the code length of the OCC sequence, and other configuration parameters of the OCC sequence, such as at least one of the OCC sequence index and OCC enable indication, can be indicated by DCI, RRC signaling, or MAC CE signaling.

[0051] In some possible implementations, the first information may include a row index in the time-domain resource configuration, which indicates the configuration parameters of the OCC sequence. This can save signaling overhead.

[0052] In some other possible implementations, the first information may include a SLIV (Signature Indicator Variable) used to indicate configuration parameters of the OCC sequence. At least one bit in the SLIV can be used to indicate the configuration parameters of the OCC sequence. Thus, if the SLIV and the configuration parameters of the OCC sequence can jointly occupy 8 bits, 1 bit can be used to indicate the configuration parameters of the OCC sequence, and the remaining 7 bits can be used to indicate the SLIV. Alternatively, the configuration parameters of the OCC sequence can occupy 3 or 4 bits in the SLIV. These 3 or 4 bits can occupy the 8 bits occupied by the SLIV, or they can be added to the traditional 7 bits occupied by the SLIV by adding 3 or 4 bits occupied by the configuration parameters of the OCC sequence; this is not limited here.

[0053] In other possible implementations, the configuration parameters of the OCC sequence may occupy other information, or may occupy at least one bit of the SLIV and other information, etc., without limitation. In this way, the configuration parameters of the OCC sequence can be indicated by unused bits in the existing information, which can save signaling overhead.

[0054] This application does not limit the number of bits occupied by the configuration parameters of the OCC sequence. It can refer to the aforementioned 3-bit or 4-bit description, or it can be related to the reporting capability of the first communication device. That is, the number of bits occupied by the configuration parameters of the OCC sequence is determined according to the reporting capability of the first communication device. For example, if the first communication device supports information reporting with an OCC sequence code length of 2, but does not support information reporting with an OCC sequence code length of 4, one bit can be used to indicate the index of the OCC sequence, and the code length of the OCC sequence may not be indicated; the code length can be defaulted to 2. As another example, if the first communication device supports information reporting with an OCC sequence code length of 4, two bits can be used to indicate the index of the OCC sequence. The code length of the OCC sequence may default to 4, or another bit can be used to indicate the code length of the OCC sequence. In both of these examples, one bit can also be used to indicate the OCC enable indication. In the case of using the redundant transmission method with OCC sequence extension described in Method 2 or Method 3, the length of the OCC sequence may not be indicated. The configuration parameters for the OCC sequence can be carried in at least one of DCI, RRC signaling, and MAC CE.

[0055] Optionally, the method may further include receiving information A. Information A is used to indicate the resources of the PUSCH, such as one or more resource units occupied by the PUSCH.

[0056] Information A can be TDRA and / or frequency domain resource assignment (FDRA). Optionally, information A can be system information, such as a system information block (SIB). Alternatively, it can be configuration information, for example, higher-layer signaling such as RRC signaling or MAC CE signaling. Information A can also be physical layer signaling, such as DCI.

[0057] Optionally, information A is also used to indicate the number of times PUSCH is repeated.

[0058] This application does not limit the number of resource units occupied by a PUSCH; it can be one or more. Optionally, the number of resource units occupied by a PUSCH is an integer multiple of L, where L is the code length of the OCC sequence. The data carried on each PUSCH should be the same, or it can be data from the same transport block. By transmitting the data carried by the PUSCH multiplied by the corresponding OCC element in the OCC sequence on the PUSCH of each resource unit, data expansion and repeated transmission can be achieved through the OCC sequence, which can improve system capacity and system performance.

[0059] Thirdly, this application discloses a communication device, including units, modules, or means for performing the steps of the first or second aspect or any of the implementation methods described above. The modules, units, or means can be implemented by software, hardware, or a combination of software and hardware.

[0060] Fourthly, 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 or second aspects or any possible implementations described above are implemented. Optionally, the communication device further includes a memory.

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

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

[0063] Fifthly, 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 performs the methods described in the first aspect or in feasible examples thereof. When the second communication device operates in the communication system, it performs the methods described in the second aspect or in feasible examples thereof.

[0064] Sixthly, this application provides another communication system, which includes communication devices as described in any of the possible embodiments of the third or fourth aspect.

[0065] In conjunction with the third, fourth, fifth, or sixth aspects, in some feasible examples, the communication device may be a first communication device. The first communication device may be a terminal device or a communication module in the terminal, or a circuit or chip in the terminal responsible for communication functions (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).

[0066] In some feasible examples, the communication device can be a second communication device. This second communication device can be a network device, a communication module within a network device, a combination device or component with network device functionality, or a circuit or chip within a network device responsible for communication functions. In one implementation, the second communication device can be a non-terrestrial network device, such as a satellite.

[0067] In a seventh aspect, 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 or second aspects or any possible implementation thereof to be implemented.

[0068] Eighthly, 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 or second aspects or any possible implementation thereof to be implemented.

[0069] Ninthly, 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 or second aspects or any possible implementation thereof.

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

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

[0072] In a tenth 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 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.

[0073] In one 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 computer programs or instructions to perform the methods in any of the above aspects or possible embodiments.

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

[0075] Furthermore, in the process of performing the methods described in the first or second aspect and any possible implementation, the processes related to sending and / or receiving information can be understood as the process of the processor outputting information and / or the processor receiving input information. When outputting information, the processor can output the information to a transceiver (or communication interface or transmitting module) for transmission. After the information is output by the processor, it may require further 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 to the processor. Furthermore, after the transceiver receives the information, it may require further processing before being input to the processor.

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

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

[0078] Optionally, in performing the methods of the first or second aspect and any possible implementation described above, the processor may be a processor specifically designed to perform these methods, or it may be a processor that performs 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

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

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

[0081] Figure 2 is a schematic diagram of the architecture of an NTN communication system provided in an embodiment of this application;

[0082] Figure 3 is a flowchart illustrating a communication method provided in an embodiment of this application;

[0083] Figures 4A to 4D are schematic diagrams of an uplink data transmission method provided in an embodiment of this application;

[0084] Figures 5A to 5E are schematic diagrams of a time-domain resource configuration provided in an embodiment of this application;

[0085] Figure 6 is a schematic diagram of an OCC sequence code length indication method provided in an embodiment of this application;

[0086] Figure 7 is a schematic diagram of the structure of a communication device provided in an embodiment of this application;

[0087] Figure 8 is a schematic diagram of another communication device provided in an embodiment of this application;

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

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

[0090] 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-A 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, non-terrestrial network (NTN) communication systems, wireless projection communication systems, integrated access and backhaul (IAB) communication systems, public land mobile network (PLMN) communication systems, and non-public networks. The term "Network Network" (NPN) refers to any communication system, including those used in future communication systems, or those not part of the 3rd Generation Partnership Project (3GPP) communication system, without limitation. Specifically, 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 and IoT NTN.

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

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

[0093] 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. Hereinafter, it is sometimes simply referred to as a terminal.

[0094] In Figure 1, network devices are exemplified using an access network (AN) node. An access network node can also be called a radio access network (RAN) node, or simply an access network. 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.

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

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

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

[0098] 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 connected to the satellite communication terminal.

[0099] In the network architecture shown in Figure 1, network devices are exemplified using access network nodes. Optionally, the communication system may also include network devices not shown in Figure 1, such as core network (CN) devices, data network devices, etc.

[0100] Furthermore, the number and types of network devices and terminal devices included in the network architecture shown in Figure 1 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. As another example, it may also 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.

[0101] Optionally, the communication system may also include network devices not shown in Figure 1, such as core network (CN) devices, data network devices, etc.

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

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

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

[0105] 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 may include a private network, such as a local area network (LAN). The data network may also include an external network not managed by an operator, such as the Internet. Alternatively, the data network may include a proprietary network jointly deployed by operators, such as a network providing Internet Protocol Multimedia Subsystem (IMS) services.

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

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

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

[0109] Please refer to Figure 2, which is a schematic diagram of the architecture of an NTN communication system provided in an embodiment of this application. Figure 2 uses an NTN communication system integrated with a 5G communication system as an example. It should be understood that the solution provided in this embodiment can be applied to NTN systems integrated with 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 the 5G control plane processing unit and the 5G user plane processing unit shown in Figure 2. The 5G control plane processing unit can include the Access and Mobility Management Function (AMF) network element and the Location Management Function (LMF) network element shown in Figure 2, and can also include PCF network elements, UDM network elements, AF network elements, SMF network elements, etc., not shown in the figure. The architecture shown in Figure 2 can be understood as an NTN-based NG-RAN architecture.

[0110] 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, as shown in Figure 2, including the interface between the 5G base station and the ground station, the interface between the ground station and the 5G user plane processing unit, and the interface between the ground station and the AMF network element. It is 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, as shown in Figure 2, between two 5G base stations, and is mainly used for exchanging handover signaling. The N6 interface can be the interface between the core network and the data network.

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

[0112] As shown in Figure 2, 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.

[0113] As shown in Figure 2, satellites can have inter-satellite links (ISLs) with each other. These satellites can be referred to as regenerative sanitary systems with inter-satellite links. The ISL between two satellites is connected via the Xn interface. Signaling interaction and user data transmission between access network devices can be completed between satellites. Alternatively, satellites may not have inter-satellite links.

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

[0115] 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, and access networks (such as base stations) within terrestrial network devices can perform RAN functions (access 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 transmission and forwarding, acting as a layer 1 relay to regenerate physical layer signals, without involving any higher protocol layers.

[0116] The number and types of communication devices included in the network architecture shown in Figures 1 and 2 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.

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

[0118] (1) Time-frequency resources can include time-domain resources and frequency-domain resources.

[0119] In this context, 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. At the physical layer, an RB is called a physical resource block (PRB). Frequency domain resource units can include subcarriers, subcarrier spacing (SCS), bandwidth, RBs, RB groups (RBGs), bandwidth parts (BWPs), component carriers, etc.

[0120] 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 referred to as 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.

[0121] In this embodiment, the resource unit may include a RE (Resource Element) or a time unit. The time unit may be the aforementioned time-domain resource unit, or it may be a unit composed of multiple time-domain resource units, such as a symbol group composed of multiple symbols. This application does not limit the number of symbols within a symbol group; it can be a positive integer greater than 1. The symbols may be modulation symbols or orthogonal frequency division multiplexing (OFDM) symbols.

[0122] (2) 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.

[0123] In the embodiments of this application, the code length of an OCC sequence refers to the number of bits in an OCC sequence. A bit in an OCC sequence may be called an OCC element, and the code length may be called the spreading factor or spreading factor, or the OCC sequence length. Spreading is also called block spreading or block-like spreading, and when spreading in the frequency domain, it may also be called spread spectrum. This application does not limit the size of the code length, for example, 2, 4, 8, etc.

[0124] The basic principle of OCC (Optical Code Correction) is to multiply the information to be transmitted by the terminal device with each OCC element in the terminal device's OCC sequence. This results in the multiplied information being expanded and orthogonal in the code domain, thus ensuring that information transmission between terminal devices does not interfere with each other. 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 usually used in scenarios that enhance system capacity and increase the transmission rate of terminal devices.

[0125] In the embodiments of this application, the information may include data and / or signaling. The information to be transmitted by different terminal devices is processed by the corresponding OCC element in their configured OCC sequence. That is, the information to be transmitted by each terminal device is processed by the corresponding OCC element in its configured OCC sequence. The processing may include extension, code division multiplexing, multiplication, etc., and is not limited here. In some cases, no processing may be performed. For example, when the OCC element is 1, the transmitted information may be sent without processing, i.e., the information itself may be sent. In some cases, the above processing may also be an inversion operation. For example, when the OCC element is -1, the processing of the information to be transmitted may be an inversion operation on each information element of the information to be transmitted (e.g., inverting an information element value of 1 to 0, and inverting an information element value of 0 to 1). In some cases, in addition to processing by OCC elements, the information to be transmitted may also undergo encoding, DFT, etc., and is not limited here.

[0126] In the embodiments of this application, the information to be transmitted is processed via the OCC element corresponding to the information to be transmitted in the OCC sequence. Sometimes it is described as the information to be transmitted being processed via the OCC sequence. Processing via the OCC sequence can also be described as using the OCC sequence, or as performing OCC extension, or as performing code division extension or code division multiplexing, or as performing OCC extension and repetition, or as using the OCC element corresponding to the information to be transmitted in the OCC sequence to process the information to be transmitted.

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

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

[0129] Optionally, when the code length of the OCC sequence 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.

[0130] Taking matrix A as an example, if terminal A transmits information X and terminal B transmits information Y, in repeated transmissions, 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, resulting in the received repeated transmission information being X+Y and XY, respectively. The receiving side can multiply the received information by the OCC elements in W1 and then combine (add) them to obtain 2X, thus obtaining the information transmitted by terminal A. The receiving side can also multiply the received information by the OCC elements in W2 and then combine (add) them to obtain 2Y, thus obtaining the information transmitted by terminal B.

[0131] Based on resource units, OCCs can be divided into inter-slot OCCs (OCCs across slots), inter-symbol OCCs (OCCs across OFDM symbols), inter-symbol group OCCs (OCCs across OFDM symbols), and intra-symbol OCCs (OCCs within an OFDM symbol). Inter-symbol OCCs and inter-symbol group OCCs can be collectively referred to as multiple inter-symbol(s) OCCs.

[0132] 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 inter-slot OCC, or simply 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.

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

[0134] In this embodiment, the OCC element corresponding to a resource unit refers to the OCC element used to process the information to be transmitted on that resource unit, such as the OCC element multiplied by the information to be transmitted during OCC extension. That is, inter-slot OCC extension multiplies the information to be transmitted on each of multiple time slots with the OCC element corresponding to that time slot. Inter-symbol OCC extension multiplies the information to be transmitted on each of multiple symbols with the OCC element corresponding to that symbol. Inter-symbol OCC extension multiplies the information to be transmitted on each of multiple symbol groups with the OCC element corresponding to that symbol group. Intra-symbol OCC extension multiplies the information to be transmitted on each of multiple REs with the OCC element corresponding to that RE.

[0135] An OCC sequence with L resource units can be called an OCC group. Here, L is the code length of the OCC sequence. Each resource unit in an OCC group corresponds to one 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.

[0136] The signal processing procedures for inter-slot OCC spreading, inter-symbol OCC spreading, and inter-symbol group OCC spreading can be executed after DFT, while the signal processing procedure for intra-symbol OCC spreading can be executed before DFT. That is, after DFT processing, OCC spreading can be performed using at least one of these methods, enabling repeated transmission and spreading of data across different time slots or symbols. Alternatively, intra-symbol OCC spreading can be performed on modulated data, followed by DFT, allowing repeated transmission and spreading of data across different REs within the same symbol. This paper typically uses inter-slot OCC as an example; however, other types of OCC spreading can be applied to data carried on the PUSCH.

[0137] (3) DCI is information transmitted through the Radio Network Temporary Identifier (RNTI) protocol for one or more cells. Depending on the content of the control information, DCI can be divided into multiple DCI formats. For example, DCI formats may include: DCI format 0_0, DCI format 0_1, DCI format 0_2, DCI format 1_0, DCI format 1_1, DCI format 1_2, DCI format 4_1, DCI format 4_2, etc.

[0138] DCI can include frequency domain resource assignment (FDRA), time domain resource assignment (TDRA), modulation and coding scheme (MCS), new data indicator (NDI), DCI field indicator (DFI), redundancy version (RV), hybrid automatic repeat request (HARQ) process number, and transmission power control (TPC) instructions scheduled by PUSCH.

[0139] FDRA can occupy 4 bits to indicate the resource block for data transmission. TDRA can occupy 4 bits to indicate the time-domain resources for data transmission. The TPC instruction for PUSCH scheduling is used to notify the terminal device to adjust the PUSCH transmit power. DFI can occupy 1 bit, and when the value of DFI is 0, it is used to activate or release type 2 transmission.

[0140] MCS can be understood as a combination of factors affecting the physical transmission rate, used to indicate the modulation scheme, coding rate, and spectral efficiency (SE) employed in the transmission. Each uplink and downlink carrier in NR supports a maximum of 16 HARQ processes, so a 4-bit HARQ process number can be used to indicate the process number. After data transmission, a HARQ-ACK message needs to be returned to indicate whether it is a retransmission or an acknowledgment. NID can occupy 1 bit to indicate whether the scheduled data is a new transmission or a retransmission. Data is retransmitted according to different redundancy versions; that is, each retransmitted data has a different redundancy version. The order of the redundancy versions can be default; for example, the default redundancy version cycling order is RV0, RV2, RV3, and RV1.

[0141] In some DCI formats, the DCI may also include information about reference signals. For example, Sound Reference Signal Request (SRS request), SRS Resource Set Indicator (SRS resource set indicator), SRS Offset Indicator (SRS offset indicator), Channel State Information (CSI) Request (CSI-request), and Phase Follower Signal-Demodulation Reference Signal Association (PTRS-DMRS association), etc.

[0142] In some DCI formats, the DCI may also include an antenna port, precoding information and layer number, beta_offset indicator, etc.

[0143] (4) PUSCH is a channel for transmitting data and some control information (such as DCI) on terminal equipment. Information carried on the PUSCH is transmitted in subframes. In the time domain, the demodulation reference signal (DMRS) and the PUSCH are transmitted on different symbols. The PUSCH supports repeatable transmission based on slots and mini-slots. This application does not limit the data type transmitted on the PUSCH; it can be data from the uplink shared channel (UL-SCH) or other data. In the following text, UL-SCH data is sometimes simply referred to as data or uplink data.

[0144] The PUSCH's TDRA (PUSCH-TimeDomainResourceAllocation) is used to configure the time-domain relationship between the PDCCH and PUSCH, and can be used to determine the time-domain resources occupied by the PUSCH. There can be one or more PUSCH TDRAs, which can be included in a time-domain resource configuration list, such as PUSCH-TimeDomainResourceAllocationList, PUSCH-TimeDomainResourceAllocationList-r16, etc. The network side instructs the terminal device in the UL authorization which time-domain allocation of the UL authorization configuration should be requested.

[0145] The information element (IE) in the PUSCH TDRA 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.

[0146] The PUSCH repetition types include PUSCH repetition type A and PUSCH repetition type B. PUSCH repetition type A is a slot-level repetition type, while 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 value (SLIV). For PUSCH repetition type B, the start symbol and length can be directly indicated. The PUSCH mapping type defines the combination of the start symbol and length of the PUSCH resource. PUSCH mapping types include PUSCH mapping type A and PUSCH mapping type B. PUSCH mapping type A defines that the start symbol of the PUSCH resource in a 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 a time slot can begin from any symbol position.

[0147] 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 physical downlink control channel (PDCCH) that schedules the DCI.

[0148] The terminal device verifies uplink grant type 2 (UL grant Type 2) scheduling. For example, section 10.2 of 3GPP protocol TS38.213 version v16.0.0 states that the terminal device verifies the UL grant Type 2 PDCCH configuration for scheduling activation or release. The protocol also states that if a single configuration for UL grant Type 2 PUSCH is provided to the terminal device, DCI format verification can be achieved by setting all fields of the DCI format according to Table 10.2-1 or Table 10.2-2. If multiple configurations for UL grant Type 2 PUSCH are provided to the terminal device, the value of the HARQ process number field in the DCI format indicates the activation of the corresponding UL grant Type 2 PUSCH configuration, and its value is configured with the configured grant configuration index (ConfiguredGrantConfigIndex). DCI format verification can be achieved if the RV field of the DCI format is set as shown in Table 10.2-3.

[0149] The `ConfiguredGrantConfigIndex` is used to indicate the index of the `Configured Grant` configuration within a BWP. Multiple `Configured Grant` configurations can be configured in a single BWP of the serving cell. `ConfiguredGrantConfig` is used to configure uplink transmissions without dynamic grants according to two possible schemes: uplink grants can be configured via RRC (Type 1) or provided via PDCCH (Configured Scheduling RNTI, CS-RNTI) (Type 2).

[0150] PUSCH transmissions can be dynamically scheduled by uplink grant in the DCI, or the transmission can correspond to either configured grant type 1 or configured grant type 2. Configured grant type 1 PUSCH transmissions are semi-statically configured to operate upon receiving higher-layer parameters of the configured grant configuration, including rrc-ConfigurationUplinkGrant, without checking the uplink grant in the DCI. According to section 10.2 of 3GPP protocol TS38.213 version v16.0.0, configured grant type 2 PUSCH transmissions are semi-statically scheduled by UL grant in the effectively active DCI after receiving the higher-layer parameter configurationGrantConfig, which does not include rrc-ConfigureUplinkGrant. If configurationGrantConfigToAddModList is configured, multiple configured grant configurations of configured grant type 1 and / or configured grant type 2 can be activated simultaneously on the active BWP of the serving cell. In other words, for PUSCH transport configured with authorization type 2, the configuredGrantConfig does not include rrc-ConfigureUplinkGrant during configuration, and the relevant parameters are indicated by DCI during actual scheduling.

[0151] This application proposes a communication method that explicitly defines the configuration parameters of the OCC sequence. By extending and repeating the uplink data carried on the PUSCH to be transmitted through the OCC sequence, system capacity and performance can be improved.

[0152] 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 the description in Figure 1 or Figure 2, and will not be repeated here.

[0153] This application can be applied to situations where only one or more Configured grant type 2 PUSCH transmissions are configured on the network side, or it can be applied to situations where the Configured grant type 1 PUSCH transmissions are configured on the network side, or even to situations where the PUSCH transmission is dynamically scheduled by UL authorization in DCI, without any limitation.

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

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

[0156] Please refer to Figure 3, which is a flowchart illustrating a communication method provided in an embodiment of this application. As shown in Figure 3, the method includes, but is not limited to, the following steps:

[0157] S301, the second communication device sends first information to the first communication device, the first information being used to indicate the configuration parameters of the OCC sequence.

[0158] Correspondingly, the first communication device receives the first information from the second communication device.

[0159] This application does not limit the configuration parameters of the OCC sequence. In some possible implementations, the configuration parameters of the OCC sequence include at least one of the code length of the OCC sequence and the index of the OCC sequence.

[0160] The code length of the OCC sequence can be referred to above and will not be repeated here. The index of the OCC sequence is used to determine the OCC sequence. The mapping relationship between the index of the OCC sequence and the OCC sequence can be a mapping relationship between the index of the OCC sequence and all or part of the OCC elements in the OCC sequence. The following is an example of the mapping relationship between the index of the OCC sequence and part of the OCC elements. For example, if the OCC sequence with a code length of 4 is obtained by repeating the OCC sequence with a code length of 2, the OCC sequence that has a mapping relationship with the index corresponding to the OCC sequence with a code length of 4 can be the OCC sequence with a code length of 2, such as [1 -1]. Then it can be determined that the OCC sequence corresponding to the code length of 4 is [1 -1 1 -1], and the OCC sequence corresponding to the code length of 2 is [1 -1]. These two OCC sequences can correspond to the same index, and the OCC sequence indicated by the index is [1 -1]. For example, the index corresponding to an all-1 sequence in an OCC sequence can indicate that the OCC sequence is 1, or it can not indicate that the OCC sequence is 1. In this case, if the code length is 2, the OCC sequence is [1 1]; if the code length is 4, the OCC sequence is [1 1 1 1], and so on. The mapping relationship between the above indexes and OCC sequences is only an example, and this application does not limit it.

[0161] The configuration parameters of an OCC sequence include at least one of the code length and index of the OCC sequence. That is, the configuration parameters of an OCC sequence include the code length of the OCC sequence but do not include the index of the OCC sequence; or the configuration parameters of an OCC sequence include the index of the OCC sequence but do not include the code length of the OCC sequence; or the configuration parameters of an OCC sequence include both the code length and the index of the OCC sequence.

[0162] It is understandable that when the first information is used to indicate the index and code length of the OCC sequence, the OCC sequence and its code length can be determined. When the first information is used solely to indicate the index of the OCC sequence, the OCC sequence corresponding to the index indicated by the first information and its code length can be determined based on the mapping relationship between the OCC sequence index and the OCC sequence. When the first information is used solely to indicate the code length of the OCC sequence, the code length of the OCC sequence can be determined. If there is a mapping relationship between the code length of the OCC sequence and the OCC sequence, the OCC sequence can be determined based on the code length indicated by the first information.

[0163] The mapping relationship between the code length and the OCC sequence can be an example of the mapping relationship between some OCC elements and the code length mentioned above, or it can be a correspondence between the code length of the OCC sequence and an orthogonal matrix, and a correspondence between the sequence corresponding to the value of each row or column in the orthogonal matrix and different communication devices. Thus, the OCC sequence corresponding to the first communication device can be determined from the orthogonal matrix corresponding to the code length of the OCC sequence.

[0164] For example, if the first information indicates that the code length of the OCC sequence is 2, then the orthogonal matrix corresponding to this code length can be determined to be the aforementioned matrix A. If the OCC sequence used by the first communication device by default is the sequence corresponding to the values ​​in the first row or the first column of the orthogonal matrix, then the OCC sequence sent by the first communication device can be determined to be the sequence corresponding to the values ​​in the first row or the first column of matrix A, i.e., W1.

[0165] The index in the above example is only an example. In other possible implementations, the OCC sequence can be indicated by other OCC sequence indication information besides the index, such as the identifier of the OCC sequence, the sequence of the OCC sequence, etc., which are not limited here.

[0166] In some other possible implementations, the configuration parameters for the OCC sequence also include an OCC enable indicator. This OCC enable indicator, for example, OCC-enabled, indicates whether the first communication device uses the OCC sequence to process the information to be transmitted.

[0167] For example, the OCC enable indicator can be set to 0 to indicate that the first communication device uses the OCC sequence to process the information to be transmitted (i.e., uses the OCC sequence to process the data to be transmitted), and 1 to indicate that the first communication device does not use the OCC sequence to process the information to be transmitted (i.e., does not use the OCC sequence to process the data to be transmitted). Alternatively, the OCC enable indicator can be set to 1 to indicate that the first communication device uses the OCC sequence to process the information to be transmitted, and 0 to indicate that the first communication device does not use the OCC sequence to process the information to be transmitted. As another example, the OCC enable indicator can be set to yes or enabled to indicate that the first communication device uses the OCC sequence to process the information to be transmitted, and no or disabled to indicate that the first communication device does not use the OCC sequence to process the information to be transmitted.

[0168] In this embodiment, the information to be transmitted is carried on the PUSCH. The information to be transmitted on the PUSCH is generally referred to as data, such as data from the UL-SCH. This application does not limit the data type. The resource units occupied by the PUSCH can be determined through the time-domain resource configuration described above or below, and will not be elaborated here. The data to be transmitted is processed using an OCC sequence, which involves multiplying the data to be transmitted on the PUSCH by the OCC element corresponding to the resource unit occupied by the PUSCH in the OCC sequence.

[0169] For example, please refer to Figure 4A. In Figure 4A, resource units are time slots, and OCC sequences are [1 1] for the first communication device A and [1 -1] for the first communication device B. The OCC sequence for the first communication device A includes OCC elements w(1) and w(2), where w(1) and w(2) can both be 1. The OCC sequence for the first communication device B includes OCC elements w(3) and w(4), where w(3) can be 1 and w(4) can be -1. In Figure 4A, the horizontal axis represents the time domain, with two time slots: slot#0 and slot#1. Each time slot in slot#0 and slot#1 includes two OFDM symbols occupied by DMRS, and may also include 12 OFDM symbols used to carry data to be transmitted. These OFDM symbols represent the same data to be transmitted on these OFDM symbols by using the same number to represent the same number of OFDM symbols. For example, the data to be transmitted on OS#0 in slot#0 and slot#1 of the first communication device A is the same, and the data to be transmitted is the data corresponding to 0. The processing of the data to be transmitted using the OCC sequence can be done by multiplying the OCC element in the OCC sequence with the resource unit corresponding to the data to be transmitted. As shown in Figure 4A, the data to be transmitted on the OFDM symbols in slot#0 of the first communication device A other than the OFDM symbols occupied by DMRS can be multiplied by w(1), and the data to be transmitted on the OFDM symbols in slot#1 of the first communication device A other than the OFDM symbols occupied by DMRS can be multiplied by w(2). In slot #0, the first communication device B can multiply the data to be transmitted on the OFDM symbols other than those occupied by DMRS by w(3). In slot #1, the first communication device B can multiply the data to be transmitted on the OFDM symbols other than those occupied by DMRS by w(4). In this way, different first communication devices can use the same time-frequency resources to transmit the data processed by their corresponding OCC sequences, and can realize OCC extension and repeated transmission between time slots.

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

[0171] 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. The first information may or may not be used to indicate other information besides the configuration parameters of the OCC sequence, and is not limited thereto. For example, the first information may include the OCC sequence, thereby allowing the code length and / or index of the OCC sequence to be determined based on the OCC sequence. When the first information includes the OCC sequence, the first information may not include the code length and / or index of the OCC sequence.

[0172] In some possible implementations, the first information is also used to indicate the transmission method of the uplink data.

[0173] The uplink data refers to the data to be transmitted on the PUSCH multiplied by the OCC elements corresponding to the resource units in the OCC sequence. The transmission method of the uplink data can be indicated by the RV field in the DCI, or by other information; no limitation is made here. The transmission method of the uplink data can be understood as the transmission method corresponding to each redundant version of the data, considering the processing of the data to be transmitted via the OCC elements in the OCC sequence. This can be represented by the number of resource units occupied by the data corresponding to each redundant version. This application does not limit the number of resource units occupied by the data corresponding to each redundant version; it can be an integer multiple of L.

[0174] Method 1: The uplink data transmission method is to transmit uplink data corresponding to at least one redundant version after processing by each OCC element in the OCC sequence. The number of resource units occupied by the data corresponding to each redundant version is L.

[0175] Please refer to Figure 4B. Figure 4B uses 8 resource units (resource units are time slots) occupied by PUSCH as an example, and follows the execution order of the default redundant version cycle of data (RV0, RV2, RV3, RV1), with multiplication as the processing method. As shown in Figure 4B, when the code length of the OCC sequence is 2, the number of resource units occupied by the data corresponding to each redundant version can be 2. For example, in slots #0 and #1, the uplink data corresponding to RV0 is multiplied by the corresponding OCC element (such as W(1) for slot #0 and W(2) for slot #1). In slots #2 and #3, the uplink data corresponding to RV2 is multiplied by the corresponding OCC element (such as W(1) for slot #2 and W(2) for slot #3). In slots #4 and #5, the uplink data corresponding to RV3 is multiplied by the corresponding OCC element (such as W(1) for slot #4 and W(2) for slot #5). In slots #6 and #7, the uplink data corresponding to RV1 is multiplied by the corresponding OCC element (such as W(1) for slot #6 and W(2) for slot #7). When the code length of the OCC sequence is 4, the number of resource units occupied by the data corresponding to each redundant version can be 4. For example, in slots #0 to #3, the uplink data corresponding to RV0 is transmitted multiplied by the corresponding OCC element (such as W(1) for slot #0, W(2) for slot #1, W(3) for slot #2, and W(4) for slot #3). In slots #4 to #7, the uplink data corresponding to RV2 is transmitted multiplied by the corresponding OCC element (such as W(1) for slot #4, W(2) for slot #5, W(3) for slot #6, and W(4) for slot #7). It can be understood that transmitting data according to the number of times L corresponding to each redundant version is repeated is beneficial for the network side to despread and obtain the correct data.

[0176] This invention does not limit the execution order in RV cyling. That is, in addition to the default execution order (RV0, RV2, RV3, RV1) described above, different execution orders are also possible, such as RV1, RV2, RV3, RV0. For example, data corresponding to RV1 can be sent first, and if resources are available, data corresponding to RV2 can be sent, data corresponding to RV3 can be sent, data corresponding to RV0 can be sent, and data corresponding to RV1 can be sent, etc.

[0177] Method 2: The uplink data is transmitted by transmitting a redundant version of the data after processing by each OCC element in the OCC sequence. In other words, the redundant versions of the uplink data are identical.

[0178] This application does not limit the redundant version of the uplink data transmitted in Method 2. Please refer to Figure 4C, which uses 8 resource units (resource units are time slots) occupied by PUSCH as an example, and multiplication as the processing method, with RV0 as the redundant version in Method 2. As shown in Figure 4C, when the code length of the OCC sequence is 2 or 4, the uplink data corresponding to RV0 multiplied by the OCC element corresponding to that time slot can be sent on slots #0 to #7 respectively. Since the redundant version of the uplink data transmitted in this method is the same, that is, the data corresponding to one redundant version is transmitted, it can be understood as the case of no redundant version cycle or no RV cycling. This application does not limit RV.

[0179] Method 3: The uplink data transmission method involves transmitting data corresponding to at least one redundant version after processing by each OCC element in the OCC sequence. The number of resource units occupied by the data corresponding to each redundant version is K, where K is an integer multiple of L, and K is a fixed value. In other words, the data corresponding to each redundant version is transmitted with a fixed number of repetitions.

[0180] Please refer to Figure 4D. Figure 4D illustrates the use of 8 resource units (resource units being time slots) occupied by PUSCH, with multiplication as the processing method, and demonstrates the execution order of K being 4 and the default redundant version cycle. As shown in Figure 4D, when the OCC sequence code length is 2 or 4, uplink data multiplied by the OCC element corresponding to RV0 and the corresponding time slot can be sent on slots #0 to #3 respectively. Similarly, uplink data multiplied by the OCC element corresponding to RV2 and the corresponding time slot can be sent on slots #4 to #7 respectively. Transmitting data corresponding to the same redundant version with a fixed number of repetitions facilitates network-side despreading to obtain correct data. Simultaneously, it enables the network to simultaneously schedule terminal devices with an OCC sequence code length of 2 and terminal devices with an OCC sequence code length of 4 on the same resources.

[0181] The above three methods are merely examples of uplink data transmission methods. In reality, other uplink data transmission methods may also exist, which will not be elaborated upon here. It can be understood that the uplink data transmission method can be determined through the first information. Thus, after the first communication device sends uplink data processed by the OCC elements in the OCC sequence based on this transmission method, the network side can despread the data based on this transmission method to obtain the correct data.

[0182] In some possible implementations, the transmission mode of uplink data can be indicated by the 2 bits occupied by the RV field.

[0183] For example, please refer to Table 1, which describes the correspondence between the transmission method of uplink data and the bit value represented by the 2 bits occupied by the RV field.

[0184] Table 1

[0185] Among them, Method 1, Method 2, and Method 3 can correspond to the aforementioned methods, or they can not correspond to the aforementioned methods. For example, Method 1 can correspond to Method 2, that is, no RV cycling is performed, and the redundant versions of the transmitted data are the same. Method 2 can correspond to Method 1, that is, the number of times the data corresponding to each redundant version is repeatedly transmitted is L. Method 3 can correspond to Method 3, that is, the number of times the data corresponding to each redundant version is repeatedly transmitted is K. In this way, by using the 2 bits occupied by the RV field to indicate the transmission method of the uplink data, the introduction of new indications can be avoided, and signaling overhead can be saved.

[0186] In some other possible implementations, the transmission mode of uplink data can be indicated by the 1 bit occupied by the RV field.

[0187] Since one bit can only indicate two uplink data transmission modes, two uplink data transmission modes can be selected. For example, choosing mode one and mode two, one bit in RV can indicate one of {Opt1, Opt2}. Opt1 can be mode one, and Opt2 can be mode two. The other bit in the RV field that is not used to indicate the uplink data transmission mode can indicate other information or not indicate any information; this is not limited here, nor are the indicated information content or transmission mode limited.

[0188] In some implementations, the configuration parameters of the OCC sequence can be indicated by the 1 bit occupied by the RV field.

[0189] For example, the 1 bit occupied by the RV field is used to indicate the code length of the OCC sequence (e.g., a value of 0 indicates OCC sequence 2, and a value of 1 indicates OCC sequence code length 4) or the OCC enable indicator (e.g., a value of 0 indicates using the OCC sequence to process the data to be transmitted, and a value of 1 indicates not using the OCC sequence to process the data to be transmitted). As another example, when the OCC sequence code length is 2, the 1 bit occupied by the RV field can be used to indicate the index of the OCC sequence, such as a value of 0 indicating the aforementioned W1, and a value of 1 indicating the aforementioned W2, etc. It can be understood that by indicating the configuration parameters of the OCC sequence through the RV field, the introduction of new indicators can be avoided, thus saving overhead.

[0190] In this embodiment, one bit of the two bits occupied by the RV field can be used to indicate the uplink data transmission mode, and the other bit can be used to indicate the configuration parameters of the OCC sequence. Alternatively, one bit of the RV field can be used to indicate the uplink data transmission mode, while the other bit is not used to indicate the configuration parameters of the OCC sequence. Alternatively, one bit of the RV field can be used to indicate the configuration parameters of the OCC sequence, while the other bit can be used to indicate the uplink data transmission mode. Alternatively, both bits of the RV field can be used to indicate the uplink data transmission mode, etc. This application does not limit the content indicated by the two bits occupied by the RV field.

[0191] In this embodiment, the second communication device may send the first information to the first communication device individually, or it may send the first information via broadcast, or it may send the first information to a designated communication device via multicast or multi-cast; no limitation is made here. The multicast or multi-cast communication devices may be communication devices capable of reusing the same resources, i.e., communication devices using the same OCC sequence. The number of multicast or multicast communication devices may be equal to the code length of the OCC sequence. For the broadcast, multicast, or multicast first information, the first communication device may determine the configuration parameters of the OCC sequence it sends based on a pre-agreed protocol or configuration information issued by the network side.

[0192] In some possible implementations, the first information indicates the configuration parameters of the OCC sequence using 3 or 4 bits. That is, the 3 or 4 bits in the first information are used to indicate the configuration parameters of the OCC sequence. If the number of bits occupied by the first information is greater than 3 or 4, the remaining information may be used to indicate other information, or may not indicate any information, which is not limited here.

[0193] The following table 2 illustrates how the configuration parameters of the OCC sequence are indicated using 3 bits of information.

[0194] Table 2

[0195] Thus, when the first information includes the values ​​in Table 2, the configuration parameters of the OCC sequence corresponding to the values ​​in the first information can be determined based on the correspondence between the values ​​described in Table 2 and the configuration parameters of the OCC sequence. For example, if the value in the first information is 0, the OCC enable indication can be determined, and the OCC enable indication is determined to be that the OCC sequence is not used to process the data to be transmitted. Therefore, it is not necessary to further determine other configuration parameters of the OCC sequence, such as the code length of the OCC sequence, the index of the OCC sequence, etc., nor is it necessary to determine the OCC sequence itself. As another example, if the value in the first information is 2, the code length of the OCC sequence can be determined to be 2, and the index of the OCC sequence is 1. Therefore, the OCC sequence can be determined based on the index of the OCC sequence. In the method shown in Table 2, the OCC enable indications corresponding to values ​​other than 0 are all used to indicate that the OCC sequence is used to process the data to be transmitted.

[0196] In this embodiment, the OCC enable indication is optional. If there is no OCC enable indication, the decision to use the OCC sequence to process the data to be transmitted can be determined based on whether the first information indicates the code length of the OCC sequence. For example, if the first information indicates the code length of the OCC sequence, the first communication device defaults to using the OCC sequence to process the data to be transmitted. Conversely, if the first information does not indicate the code length of the OCC sequence, the first communication device defaults to not using the OCC sequence to process the data to be transmitted. If the OCC enable indication is that the OCC sequence is not used to process the data to be transmitted, then even if the first information indicates the code length and / or index of the OCC sequence, the first communication device also does not use the OCC sequence to process the data to be transmitted, thus allowing the first communication device to transmit the data to be transmitted on the PUSCH without using the OCC sequence.

[0197] It should be understood that Table 2 is merely an example of the configuration parameters for a 3-bit OCC sequence. In practice, the configuration parameters for a 3-bit OCC sequence can be indicated using other tables or other methods. The configuration parameters for the OCC sequence corresponding to the values ​​in other tables may be the same as or different from those in Table 1. For example, the code length of the OCC sequence corresponding to a value of 2 in another table may be the same as in Table 2, i.e., 2, but the index of the OCC sequence may be 0 instead of 1 in Table 2. Another example is that other tables may not have a value corresponding to the enable indication of not using OCC, such as other tables not including the row corresponding to 0 in Table 2, while the other rows are the same as in Table 2. This application does not limit the order of each row in Table 2; that is, the 3-bit value may or may not correspond to the configuration parameters for the OCC sequence in Table 2.

[0198] In some possible implementations, the 4 bits used to indicate the configuration parameters of the OCC sequence can be split into three parts. These three parts occupy 1 bit, 1 bit, and 2 bits respectively. The 1 bit can serve as an OCC enable indicator, indicating whether the first communication device uses the OCC sequence to process the data to be transmitted. For example, the 1 bit can be 0 or 1; 0 indicates that the first communication device uses the OCC sequence to process the data to be transmitted, and 1 indicates that the first communication device does not use the OCC sequence to process the data to be transmitted. Alternatively, 1 indicates that the first communication device uses the OCC sequence to process the data to be transmitted, and 0 indicates that the first communication device does not use the OCC sequence to process the data to be transmitted.

[0199] The other bit in the 4 bits can be used to indicate the code length of the OCC sequence. For example, the bit can be 0 or 1. 0 indicates a code length of 2, and 1 indicates a code length of 4; or 0 indicates a code length of 4, and 1 indicates a code length of 2.

[0200] The remaining 2 bits of the 4 bits can be used to indicate the index of the OCC sequence. For example, when the code length of the OCC sequence is 2, the OCC sequence corresponding to index 0 is [1 1], and the OCC sequence corresponding to index 1 is [1 -1]. When the code length of the OCC sequence is 4, the OCC sequence corresponding to index 0 is [1 1 1 1], the OCC sequence corresponding to index 1 is [1 -1 1 -1], the OCC sequence corresponding to index 2 is [1 1 -1 -1], and the OCC sequence corresponding to index 1 is [1 -1 -1 1].

[0201] For example, the 2 bits can be 00, 01, 10, and 11. Here, 00 indicates an OCC sequence of all 1s, 01 indicates an OCC sequence of [1 -1], 10 indicates an OCC sequence of [1 1 -1 -1], and 11 indicates an OCC sequence of [1 -1 -1 1]. When the OCC sequence code length is 2 and the 2-bit value is 00, the OCC sequence can be [1 1]. When the OCC sequence code length is 4 and the 2-bit value is 00, the OCC sequence can be [1 1 1 1]. When the OCC sequence code length is 2 and the 2-bit value is 01, the OCC sequence can be [1 -1]. When the OCC sequence code length is 4 and the 2-bit value is 01, the OCC sequence is [1 -1 1 -1]. Thus, by representing possible OCC sequences with a small number of values, signaling overhead can be saved. When the code length of the OCC sequence is 2, the index of the OCC sequence can be indicated by 1 bit.

[0202] For example, the 2 bits can be 01, 10, and 11 as mentioned above, excluding 00. A value of 00 in the first information can indicate that the OCC sequence is an all-1 sequence. Thus, the network side does not need to directly configure the index of the OCC sequence corresponding to the all-1 sequence. Instead, it determines whether the index in the first information corresponds to an all-1 sequence by the correspondence between the OCC sequence corresponding to the all-1 sequence and the index corresponding to that OCC sequence, further saving signaling overhead.

[0203] The above indices and their corresponding OCC sequences are merely examples, and this application does not limit their scope. When the code length is 2, the indication method for the configuration parameters of the OCC sequence can differ from that in Table 1 above. Each configuration parameter can be indicated by 1 bit, so the code length, index, and enable indication of the OCC sequence can be indicated by 3 bits, or by 2 bits, or by 1 bit. Alternatively, when the code length is 2, 1 bit can be used to indicate the code length of the OCC sequence, and 2 bits can be used to indicate the index and enable indication of the OCC sequence. Or, when the code length is 2, 1 bit can be used to indicate the index of the OCC sequence, and 1 bit can also be used to indicate the enable indication of the OCC, etc., without limitation. The configuration parameters of the OCC sequence may not include the enable indication of the OCC.

[0204] When the code length is 4, the configuration parameters of the OCC sequence are indicated by 3 bits, and these 3 bits are not split. The value of these 3 bits is used to indicate at least one of the code length and index of the OCC sequence, or it can also be used to indicate the OCC enable indicator. Alternatively, when the code length is 4, at least one of the code length and index of the OCC sequence can be indicated by 1 bit, and at least one of the index of the OCC sequence can be indicated by 2 bits, and at least one of the OCC enable indicator can also be indicated by 1 bit. Alternatively, when the code length is 4, the code length of the OCC sequence can be indicated by 1 bit, and at least one of the index and enable indicator of the OCC sequence can also be indicated by 3 bits. Alternatively, when the code length is 4, the index of the OCC sequence can be indicated by 2 bits, and at least one of the OCC enable indicator can also be indicated by 1 bit, etc., without limitation.

[0205] The correspondence between the number of bits and the configuration parameters of the OCC sequence in the above examples is merely illustrative and not intended to be limiting. The above three parts can reside in one or more first pieces of information. When three parts of a 4-bit information are split into one first piece of information, this application does not limit the order in which these three parts are sent. When three parts of a 4-bit information are split into multiple first pieces of information, this application does not limit the order in which each first piece of information is sent to the first communication device. Three bits can also be split and used separately to indicate the configuration parameters of the OCC sequence. The split bits can reside in one or more first pieces of information, and this application does not limit the information corresponding to the configuration parameters of each OCC sequence in one first piece of information or the order in which each first piece of information is sent.

[0206] This application does not limit the type of the first information. Optionally, the first information can be system information, such as SIB, or configuration information. For example, the first information can be higher-layer signaling, such as RRC signaling or MAC CE signaling. The first information can also be physical layer signaling, such as DCI. Furthermore, the first information includes DCI carried on the downlink channel that schedules the PUSCH. The downlink channel may include PDCCH.

[0207] This application does not limit the number of first pieces of information; there can be one or more. In some possible implementations, the first information is carried in at least one of the following: DCI, RRC signaling, and MAC CE signaling. That is, the first information can be carried only in DCI, or RRC signaling, or MAC CE signaling; or the first information can be carried in DCI and RRC signaling, or in DCI and MAC CE signaling, or in RRC signaling and MAC CE signaling, or in DCI, RRC signaling, and MAC CE signaling. Examples of the first information being carried in DCI and / or RRC signaling are given below. For the case of carrying it in MAC CE signaling, one of these methods can be referred to, for example, replacing DCI or RRC signaling with MAC CE signaling.

[0208] Example 1: The first information is carried in RRC signaling and DCI signaling.

[0209] In the first implementation, the code length of the OCC sequence (e.g., OCC-length) is indicated by 1 bit in the RRC signaling. The index of the OCC sequence (e.g., OCC-index) is indicated by 1, 2, or 3 bits in the DCI. The correspondence between the 1-bit value and the OCC sequence index can be found in Table 3. The correspondence between the 2-bit value and the OCC sequence index can be found in Table 4 or Table 5, and the correspondence between the 3-bit value and the OCC sequence index can be found in Table 6. Tables 3 and 4 apply to the case where the OCC sequence code length is 2, while Tables 5 and 6 apply to the case where the OCC sequence code length is 4.

[0210] Table 3

[0211] Table 4

[0212] As shown in Tables 3 and 4, when the OCC sequence has a code length of 2, the OCC sequence corresponding to index 0 can be [1 1], and the OCC sequence corresponding to index 1 can be [1 -1]. In Table 4, a bit value of 00 does not correspond to any OCC sequence index, but rather to the OCC enable indicator, indicating that the first communication device does not use the OCC sequence to process the data to be transmitted, thus eliminating the need to determine the OCC sequence based on its index. When the bit value in Table 4 is 01, the OCC sequence index is 0. When the bit value in Table 4 is 10, the OCC sequence index is 1. Thus, when using 1 bit to indicate the index of an OCC sequence with a code length of 2, the OCC enable indicator can be indicated by other first information, or it can be indicated without using first information. When using 2 bits to indicate an OCC sequence with a code length of 2, the OCC enable indicator does not need to be indicated by other first information. Alternatively, the bit values ​​in Table 4 can occupy 1 bit and indicate the OCC sequence through 1 bit, as shown in Table 3, or not as shown in Table 3, such as using 1 bit to indicate the OCC sequence with index 0, and using 0 bit to indicate the OCC sequence with index 1.

[0213] Table 5

[0214] Table 6

[0215] As shown in Tables 5 and 6, when the OCC sequence has a code length of 4, the OCC sequence corresponding to index 0 can be [1 1 1 1], the OCC sequence corresponding to index 1 can be [1 -1 1 -1], the OCC sequence corresponding to index 2 can be [1 1 -1 -1], and the OCC sequence corresponding to index 3 can be [1 -1 -1 1]. The bit value 000 in Table 6 does not correspond to any OCC sequence index, but rather to the OCC enable indicator, used to indicate that the first communication device does not use the OCC sequence to process the data to be transmitted. Thus, when using 2 bits to indicate the index of the OCC sequence with a code length of 4, the OCC enable indicator can be indicated by other first information, or it can be indicated without using the first information. When using 3 bits to indicate the OCC sequence with a code length of 4, the OCC enable indicator does not need to be indicated by other first information. Alternatively, the bit values ​​in Table 6 can occupy 2 bits, and these 2 bits can be used to indicate the OCC sequence, as shown in Table 5. Or, unlike Table 5, a bit value of 01 can be used to indicate the OCC sequence at index 0, a bit value of 10 can be used to indicate the OCC sequence at index 1, a bit value of 10 can be used to indicate the OCC sequence at index 2, and a bit value of 00 can be used to indicate the OCC sequence at index 3. Alternatively, the bit values ​​corresponding to the all-1 sequences can be omitted, and the bit values ​​corresponding to other non-all-1 sequences can be indicated instead.

[0216] Optionally, when the first information is used to indicate the OCC enable indication, this first information may be carried in 1 bit of the DCI, RRC signaling, or MAC CE signaling, without limitation. For example, 1 bit in the RRC signaling is used to indicate the code length of the OCC sequence, another 1 bit in the RRC signaling or 1 bit in another RRC signaling is used to indicate the OCC enable indication, and 1 bit, 2 bits, or 3 bits in the DCI are used to indicate the index of the OCC sequence. As another example, 1 bit in the RRC signaling is used to indicate the code length of the OCC sequence, and the DCI is used to indicate the index of the OCC sequence and the OCC enable indication. Here, the OCC enable indication occupies 1 bit in the DCI, and the OCC sequence index may occupy one or more bits in the DCI.

[0217] The OCC sequences corresponding to the indices of the OCC sequences described above are merely examples. In reality, the indices of the OCC sequences may not be as described above. For example, in Tables 3 and 4, the OCC sequence corresponding to index 0 could be [1 -1], and the OCC sequence corresponding to index 1 could be [1 1]. Furthermore, the correspondence between the bit values ​​and the OCC sequence indices can be as shown in any of Tables 3 to 6, or it can be different from what is shown in Tables 3 to 6; this is not limited here.

[0218] The first implementation is exemplified by indicating the code length of the OCC sequence in an RRC signaling message and the configuration parameters of the OCC sequence in a DCI signaling message. This application also protects cases where any of the other DCI, RRC, and MAC CE signaling messages carries the first information. For example, the DCI includes information indicating at least one of an OCC enable indication and the code length of the OCC sequence. Furthermore, this application also includes some of the cases described above, such as using only 1 bit in the RRC signaling message to indicate the code length of the OCC sequence, without indicating the OCC enable indication.

[0219] This application does not limit which information in the RRC signaling and DCI carries the first information in the first implementation. For example, at least one of the HARQ process number, RV, SLIV, antenna port, etc. in the DCI is used to carry the first information, and the ConfiguredGrantConfig or rrc-ConfiguredUplinkGrant in the RRC signaling is used to carry another piece of first information. Please refer to the description of Example 2 or Example 3.

[0220] Example 2: The first information is carried only in the DCI.

[0221] For example, if the first information is carried in the DCI, the DCI may include a HARQ process number, which is used to indicate the configuration parameters of the OCC sequence.

[0222] This application does not limit the configuration parameters for the number of bits occupied in the HARQ process number indicating the OCC sequence. Refer to Tables 3 to 6 for details. For example, 1 bit can indicate the code length of the OCC sequence, and 1, 2, or 3 bits can indicate the index of the OCC sequence. Optionally, the remaining 1 bit can indicate the OCC enable indicator, or the OCC enable indicator can be omitted regardless of whether there are remaining bits.

[0223] This implementation can be applied to situations where the network side provides one or more configuration information for grant type 2 PUSCH transmissions, or to situations where the network side configures grant type 1 PUSCH transmissions, or even to situations where PUSCH transmissions are dynamically scheduled with UL authorization in DCI; no limitation is made here. As mentioned earlier, the terminal device can obtain a configuration provided by the network side for grant type 2 PUSCH transmissions based on the HARQ process number. In this case, the configuration parameters of the OCC sequence indicated by the HARQ process number can reduce signaling overhead.

[0224] It is understandable that using the HARQ process number to indicate the configuration parameters of an OCC sequence can save signaling overhead by avoiding the introduction of new indication information. The HARQ process number can indicate the configuration parameters of all OCC sequences, or it can indicate the configuration parameters of a subset of OCC sequences, with the remaining configuration parameters indicated by other first information. For example, when the first information is carried in both DCI and RRC signaling, the HARQ process number can be used to indicate the first parameter in the configuration parameters of the OCC sequence, while the second parameter can be indicated by RRC signaling.

[0225] The first and second parameters can be configuration parameters for different OCC sequences, and this application does not limit their types. For example, the first parameter can be at least one of the code length of the OCC sequence and the OCC enable indication, and the second parameter can be the index of the OCC sequence, etc. In this way, the configuration parameters of the OCC sequence can be indicated by the HARQ process number in the DCI and the RRC signaling. For example, when the HARQ process number occupies 4 bits, 2 bits can be used to indicate the index of the OCC sequence, and the remaining 2 bits can be set to 0 or other values, which is not limited in this application. The second parameter can be configured through ConfiguredGrantConfig or rrc-ConfiguredUplinkGrant in the RRC, which is not limited in this application.

[0226] The above example uses the HARQ process number. In reality, at least one of the first and second parameters can be indicated through other information in the DCI. That is, other information in the DCI can be used to indicate all or some of the configuration parameters of the OCC sequence. This other information can include RV, antenna port, n, etc. SCIDThe following are not limited to: the CDM group value of the DMRS without data, the CDM group value λ, the parameter Δ, the DMRS extra position, the DMRS type, the PUSCH DMRS time index, the request message of the probe reference signal SRS, the SRS resource setting indication, the SRS offset indication, the PT-RS-DMRS association, the precoding information and layer number, the CSI request, the TPC command of the PUSCH schedule, the CBG transmission information, the beta_offset indication, etc.

[0227] The following example uses an antenna port. For instance, when the first information is carried in the DCI, the DCI may include an antenna port used to indicate configuration parameters of the OCC sequence. For example, please refer to Table 7, which describes a mapping relationship between an antenna port and configuration parameters of the OCC sequence provided in this application.

[0228] Table 7

[0229] As shown in Table 7, when the antenna port is 1000, there is no index or code length corresponding to any OCC sequence; instead, there is an OCC enable indication, used to indicate that the first communication device does not use the OCC sequence to process the data to be transmitted. When the antenna port is any one of 1001 to 1006, the first communication device can use the OCC sequence, and the index and code length of the corresponding OCC sequence can be determined according to Table 7. In some other possible embodiments, Table 7 may not indicate the OCC enable indication. In some other possible embodiments, the configuration parameters of the antenna port and its corresponding OCC sequence may not be as shown in Table 7. For example, when the antenna port is 1005, the OCC enable indication may be indicated as not using the OCC sequence to process the data to be transmitted, or the code length of the OCC sequence may be indicated as 2, and the index of the OCC sequence as 1, etc., which will not be described in detail here. The antenna ports or their corresponding values ​​and the configuration parameters of the OCC sequences are merely examples, and this application does not limit them.

[0230] Example 3: The first information is carried only in the RRC.

[0231] For example, when the first information is carried in the RRC, the RRC may include a ConfiguredGrantConfigIndex, which is used to indicate the configuration parameters of the OCC sequence. For example, please refer to Table 8, which describes a mapping relationship between a ConfiguredGrantConfigIndex and the configuration parameters of an OCC sequence provided in this application.

[0232] Table 8

[0233] As shown in Table 8, "N" indicates that the first communication device does not use the OCC sequence to process the data to be transmitted, while "Y" indicates that the first communication device uses the OCC sequence to process the data to be transmitted. That is, when ConfiguredGrantConfigIndex is 0, there is no indication of the OCC sequence index or code length; instead, it corresponds to an OCC enable indication, indicating that the first communication device does not use the OCC sequence to process the data to be transmitted. When ConfiguredGrantConfigIndex is a value other than 0, the first communication device can use the OCC sequence, and the index and code length of the OCC sequence to be used can be determined according to Table 8. In some other possible implementations, Table 8 may not indicate the OCC enable indication, i.e., it may not include the row corresponding to ConfiguredGrantConfigIndex being 0. In some other possible implementations, the configuration parameters of ConfiguredGrantConfigIndex and its corresponding OCC sequence may not be as shown in Table 8. For example, a ConfiguredGrantConfigIndex of 2 can indicate that the OCC enable is to not use the OCC sequence to process the data to be transmitted (or N), or it can indicate that the code length of the OCC sequence is 2 and the index of the OCC sequence is 0, etc. These will not be described in detail here.

[0234] The implementation of using `ConfiguredGrantConfigIndex` to indicate the configuration parameters of the OCC sequence can be applied to situations where the network side provides one or more configuration information for grant type 2 PUSCH transmissions, or to situations where the network side configures grant type 1 PUSCH transmissions, or even to situations where the PUSCH transmission is dynamically scheduled with UL authorization in DCI; no limitation is made here. As mentioned earlier, the terminal device can obtain one or more configurations provided by the network side for grant type 2 PUSCH transmissions based on the configuration of `ConfiguredGrantConfigIndex`. In this case, indicating the configuration parameters of the OCC sequence through `ConfiguredGrantConfigIndex` can reduce signaling overhead.

[0235] For example, if the value of ConfiguredGrantConfigIndex is 2, the code length of the OCC sequence can be 2, and the index of the OCC sequence is 2. The ConfiguredGrantConfigIndex in the RRC can also determine all or part of the configuration parameters of the OCC sequence. The remaining configuration parameters can be indicated by information in the DCI (such as the HARQ process number) as described in Example 2, or by other information, which is not limited here.

[0236] In some possible implementations, the configuration parameters of the OCC sequence may be included in the time-domain resource configuration of the PUSCH.

[0237] The time-domain resource configuration can be the aforementioned TDRA, or it can be the aforementioned time-domain resource list containing one or more time-domain resource configurations. The time-domain resource configuration can be carried in at least one of RRC signaling, DCI, or MAC CE signaling, and is not limited thereto. This application does not limit the position of the OCC sequence configuration parameters in the time-domain resource configuration. The following examples, with reference to Figures 5A to 5E, illustrate the configuration parameters of OCC sequences at different positions. In these examples, the OCC sequence configuration parameters include at least one of the following: OCC enable indication, OCC sequence code length, and OCC sequence index.

[0238] As shown in Figure 5A, at least one of the configuration parameters of the OCC sequence, such as the OCC enable indicator (e.g., occ-enabled), the OCC sequence code length (e.g., occ-length), and the OCC sequence index (e.g., occ-index), can be included in the PUSCH TDRA (e.g., PUSCH-TimeDomainResourceAllocation). This time-domain resource configuration can be the time-domain resource parameters in protocol R15. In addition to the OCC sequence configuration parameters, it can also include the PUSCH slot offset value (e.g., K2), mapping type (e.g., mappingType), start symbol, and length (e.g., startSymbolAndLength), etc. These IEs can be represented by a sequence.

[0239] The offset value of the PUSCH slot can be of integer type (INTEGER), with a value between 0 and 32. The start symbol and length are also of integer type, with a value between 0 and 127. The mapping type is of enumerated type (ENUMNERATED), which can include type A and type B, as described above, and will not be repeated here. The configuration parameters of the OCC sequence can also be of enumerated type, as shown in Figure 5A. The OCC enable indicator can be used to indicate the use of the OCC sequence (e.g., enable) or to indicate the disuse of the OCC sequence (e.g., disable). The code length of the OCC sequence can be 2 or 4, and the index of the OCC sequence can be 0, 1, 2, or 3. In some other possible implementations, the data types of the code length and index of the OCC sequence can be integer, etc., which are not limited here.

[0240] As shown in Figure 5B, at least one of the configuration parameters of the OCC sequence, such as the OCC enable indicator (e.g., occ-enabled), the code length of the OCC sequence (e.g., occ-length), and the index of the OCC sequence (e.g., occ-index), can be included in the time-domain resource configuration of PUSCH in R16 version (e.g., PUSCH-TimeDomainResourceAllocation-r16). The IE in this time-domain resource configuration can be represented by a sequence, and may include the offset value of the PUSCH slot (e.g., K2-r16) and the time-domain resource configuration list of PUSCH (e.g., puschAllocationList-r16). The IE in the time-domain resource configuration list of PUSCH can also be represented by a sequence, and may include the number of PUSCHs (e.g., SIZE(1 maxNrofMultiplePUSCHs-r16) OF PUSCH-Allocation-r16) and the configuration parameters of the OCC sequence. The offset value of the PUSCH slot and the configuration parameters of the OCC sequence can be referred to the description in Figure 5A, and will not be repeated here. The range of values ​​for K2-r16 is the same as the range of values ​​for K2 in Figure 5A.

[0241] As shown in Figure 5C, at least one of the configuration parameters of the OCC sequence, such as the OCC enable indicator (e.g., occ-enabled), the OCC sequence code length (e.g., occ-length), and the OCC sequence index (e.g., occ-index), can be included in the PUSCH time-domain resource allocation list (e.g., PUSCH-TimeDomainResourceAllocationList). The configuration parameters of the OCC sequence can be referred to the description in Figure 5A, and will not be repeated here. The time-domain resource allocation list shown in Figure 5C includes one or more time-domain resource configurations, each of which can be an R15 version time-domain resource configuration. The configuration parameters of the OCC sequences corresponding to the time-domain resource allocation list are the same; that is, one or more time-domain resource configurations in the time-domain resource allocation list correspond to the same OCC sequence configuration parameters.

[0242] In other possible implementations, the PUSCH time-domain resource configuration list may include multiple time-domain resource configurations, and each time-domain resource configuration may correspond to a different list of configuration parameters for the OCC sequence. That is, different time-domain resource configurations in the time-domain resource configuration list correspond to different lists of configuration parameters for the OCC sequence. This list of configuration parameters for the OCC sequence includes configuration parameters for at least one OCC sequence. For example, please refer to Table 9, which describes the correspondence between the lists of time-domain resource configurations and the lists of configuration parameters for the OCC sequences.

[0243] Table 9

[0244] In this table, PUSCH-allocation#1 represents the first time-domain resource configuration in the PUSCH time-domain resource configuration list, PUSCH-allocation#2 represents the second time-domain resource configuration in the PUSCH time-domain resource configuration list, and so on. As shown in Table 9, the code length and index of the OCC sequence can be used as a list of configuration parameters for an OCC sequence (or described as a group or set of configuration parameters, etc.). In fact, the list of configuration parameters for the OCC sequence can also include the OCC enable indication. The index value of the time-domain resource configuration can be its corresponding row. For example, if the index value of the first row is 1, it corresponds to the list of configuration parameters for PUSCH-allocation#1 and the first OCC sequence. Thus, the list of configuration parameters for the OCC sequence corresponding to the time-domain resource configuration can be determined according to Table 9, and the code length and index of the OCC sequence in the list of configuration parameters can then be determined.

[0245] The configuration parameters of the OCC sequence shown in Figure 5C are located in a time-domain resource configuration that also includes other IEs, such as the number of time-domain resource configurations for PUSCH, which can be configured using the IE represented by SIZE(1..maxNrofUL-Allocations))OF PUSCH-TimeDomainResourceAllocation. These other IEs can be understood as IEs included in the time-domain resource configuration without considering OCC extensions; that is, the configuration parameters of the OCC sequence are newly added IEs in at least one of the existing time-domain resource configurations and time-domain resource configuration lists. In some other possible implementations, the configuration parameters of the OCC sequence can be located in a new time-domain resource configuration list. That is, the time-domain resource configuration list (such as PUSCH-TimeDomainResourceAllocationList) can be located in a new sequence of IEs, and this sequence of IEs includes the configuration parameters of the OCC sequence. This time-domain resource configuration list can include one or more time-domain resource configurations, and multiple time-domain resource configurations can correspond to the same configuration parameters of the OCC sequence, or they can correspond to configuration parameters of different OCC sequences.

[0246] As shown in Figure 5D, at least one of the configuration parameters of the OCC sequence, such as the OCC enable indicator (e.g., occ-enabled), the code length of the OCC sequence (e.g., occ-length), and the index of the OCC sequence (e.g., occ-index), can be included in the time-domain resource configuration list (e.g., PUSCH-TimeDomainResourceAllocationList-r16) of the R16 version of PUSCH. This time-domain resource configuration list includes one or more time-domain resource configurations, and each time-domain resource configuration can correspond to the same configuration parameters of the OCC sequence. The configuration parameters of the OCC sequence can be referred to the description in Figure 5A, and the configuration parameters of the OCC sequence corresponding to each time-domain resource configuration can be referred to the description in Table 8, which will not be repeated here. The number of time-domain resource configurations of the R16 version of PUSCH can be configured using the IE represented by SIZE(1..maxNrofUL-Allocations))OF PUSCH-TimeDomainResourceAllocation-r16. The configuration parameters of the OCC sequence shown in Figure 5E can be understood as newly added IEs in at least one of the existing time-domain resource configurations and time-domain resource configuration lists. In some other possible implementations, the configuration parameters of the OCC sequence may be located in a new time-domain resource configuration list, and the new time-domain resource configuration list may be the time-domain resource configuration list of PUSCH version R16 or other versions of the time-domain resource configuration list. This time-domain resource configuration list may include one or more time-domain resource configurations, and multiple time-domain resource configurations may correspond to the same configuration parameters of the OCC sequence, or they may correspond to the configuration parameters of different OCC sequences.

[0247] As shown in Figure 5E, at least one of the configuration parameters of the OCC sequence, such as the OCC enable indicator (e.g., occ-enabled), the OCC sequence code length (e.g., occ-length), and the OCC sequence index (e.g., occ-index), can be included in the time-domain resource configuration of the R16 version of PUSCH. This time-domain resource configuration can be represented by sequences and may include the PUSCH slot offset value (e.g., K2-r16, extendedK2-r17), mapping type (e.g., mappingType-r16), start symbol and length (e.g., startSymbolAndLength-r16), length (e.g., length-r16), number of repetitions (e.g., numberOfRepetitionsExt-r17), number of slots (e.g., numberOfSlotsTBoMS-r17)), OCC enable indicator (e.g., occ-enabled), OCC sequence code length (e.g., occ-length), and OCC sequence index (e.g., occ-index), etc. The offset value, mapping type, start symbol and length of the PUSCH slot, the OCC enable indicator, the code length of the OCC sequence, and the index of the OCC sequence can be referred to the description in Figure 5A, and will not be repeated here. The value range of K2-r16 is consistent with the value range of K2 in Figure 5A, and the value range of extendedK2-r17 is larger than the value range of K2 in Figure 5A, and can be an integer from 0 to 128. The data type of the length is integer, and the value is an integer between 1 and 14, which can be understood as the number of symbols in the slot. The data type of the repetition count and the number of slots of TBoMS can be enumerated.

[0248] Figures 5A to 5E are merely examples, and the optional ones are also just examples. For instance, Figures 5A to 5E above may not have an IE indicating OCC enable. If the first information indicates the code length of the OCC sequence, the default OCC enable is to use the OCC sequence. The configuration parameters for the above OCC sequence can occupy 3 or 4 bits, as described above, and will not be repeated here.

[0249] In some other possible implementations, the configuration parameters of the OCC sequence may not be as shown in any of Figures 5A to 5E, and the order of the configuration parameters of each OCC sequence may also not be as shown in Figures 5A to 5E. Furthermore, in Figures 5A to 5E, the configuration parameters of the OCC sequence include an OCC enable indicator, the code length of the OCC sequence, and the index of the OCC sequence. In some other possible implementations, the configuration parameters of the OCC sequence in the time-domain resource configuration may, as described above, include only at least one of the code length and the index of the OCC sequence. If the time-domain resource configuration does not include an OCC enable indicator, and if the time-domain resource configuration includes at least one of the code length and the index of the OCC sequence, the first communication device defaults to using the OCC sequence. The data to be transmitted on the first communication device can be multiplied by the OCC element corresponding to the resource unit occupied by the data to be transmitted in the OCC sequence to achieve data expansion and repeated transmission.

[0250] The time-domain resource configuration or time-domain resource configuration list shown in Figures 5A to 5E can be understood as the configuration of the parameter range of the OCC sequence configuration parameters. This time-domain resource configuration or time-domain resource configuration list can be configured or pre-configured before the first information, such as when the network side issues RRC signaling. The configuration parameters of the OCC sequence indicated in the first information can be understood as the configuration parameters of the OCC sequence specifically used by the first communication device.

[0251] In some possible implementations, if the PUSCH configuration information does not include the configuration of the PUSCH time-domain resources, the first communication device can use the default information to determine the configuration parameters of the OCC sequence.

[0252] The time-domain resource configuration of the PUSCH may include at least one of the aforementioned TDRA and time-domain resource configuration lists. The PUSCH configuration information may include configurations applicable to all PUSCHs (e.g., PUSCH-ConfigCommon) or configurations applicable to a single PUSCH (e.g., pusch-Config). Default information may be a default table (e.g., Default A), etc., without limitation. The code length of the OCC sequence in the default OCC sequence configuration parameters may be 2, without limitation. Alternatively, the first communication device may use the default information to determine the code length of the OCC sequence. Other configuration parameters of the OCC sequence, such as at least one of the OCC sequence index and OCC enable indication, may be indicated by DCI, RRC signaling, or MAC CE signaling.

[0253] Tables 2 to 9 above can be understood as newly created tables for the configuration parameters of OCC sequences. In some other possible implementations, the configuration parameters of OCC sequences can be associated with existing tables.

[0254] For example, the configuration parameters of the OCC sequence can be associated with the row index in the time-domain resource configuration, as shown in Table 10.

[0255] Table 10

[0256] The row indexes in Table 10 can be Table 6.1.2.1.1-2 or Table 6.1.2.1.1-3 in 3GPP protocol TS38.214 version v16.0.0. The code lengths and indexes of the OCC sequences in Table 10 are merely examples and are not limited in this application. That is, the OCC sequences corresponding to the row indexes may or may not be as shown in Table 10. In some other possible implementations, the row indexes may not be bound to the code lengths or indexes of the OCC sequences; that is, the columns corresponding to the code lengths or indexes of the OCC sequences in Table 10 may be deleted. In some other possible implementations, Table 10 may add a column as shown in Table 8, used solely to indicate the OCC enable indication. That is, the row indexes may be used to indicate the code lengths, indexes, or enable indications of the OCC sequences, or may indicate at least two of the code lengths, indexes, and enable indications of the OCC sequences. Alternatively, instead of referring to Table 10, one could refer to Tables 2, 4, or 6, associating the OCC enable indicator with a row index, without associating it with at least one of the OCC sequence code length and OCC sequence index. Of course, a new table could also be generated for the row index and the OCC sequence configuration parameters. The mapping relationship between the row index and the OCC sequence configuration parameters above is merely an example and is not limited here. It is understandable that indicating the OCC sequence configuration parameters through the row index in the time-domain resource configuration can save signaling overhead.

[0257] For example, the configuration parameters of the OCC sequence can be associated with the SLIV in the time-domain resource configuration, as shown in Table 11 or Table 12.

[0258] Table 11

[0259] Table 12

[0260] The OCC sequences shown in Tables 11 and 12 do not indicate an OCC enable signal. As shown in Table 11, for SLIVs of 0–127, there is no corresponding OCC sequence code length and index as shown in Table 12. For SLIVs of 0–104, there is no corresponding OCC sequence code length and index. If an SLIV does not have at least one of the corresponding OCC sequence code length and index, it can be determined that the OCC sequence will not be used to process the data to be transmitted. If other SLIVs have at least one of the corresponding OCC sequence code length and index, it is assumed that the first communication device can use the OCC sequence to process the data to be transmitted, and the OCC sequence code length and index can be determined based on the value corresponding to the SLIV. SLIVs in Tables 11 and 12 may correspond to the same or different OCC sequence code lengths or indices.

[0261] For example, with SLIV 212, according to Table 11 or Table 12, the code length of the OCC sequence is 2 and the index of the OCC sequence is 1. With SLIV 422, according to Table 11, the code length of the OCC sequence is 4 and the index of the OCC sequence is 0; according to Table 12, the code length of the OCC sequence is 4 and the index of the OCC sequence is 1. With SLIV 382, ​​according to Table 11, the code length of the OCC sequence is 2 and the index of the OCC sequence is 1; according to Table 12, the code length of the OCC sequence is 4 and the index of the OCC sequence is 0.

[0262] The SLIVs and their corresponding OCC sequence code lengths and indices in Tables 11 and 12 above are examples. In some other possible implementations, the SLIV may also indicate an OCC enable indicator. Alternatively, in some other possible implementations, the SLIV may indicate either the OCC sequence index or the OCC sequence code length. Or, in some other possible implementations, the OCC sequence index and OCC sequence code length indicated by the SLIV may differ from the values ​​in Tables 11 or 12, or at least one of the OCC sequence and OCC sequence index indicated by the SLIV may differ from those in Tables 11 or 12. This application does not limit the configuration parameters of the OCC sequence corresponding to the SLIV or the mapping relationship between them.

[0263] In some other possible implementations, at least one bit in the SLIV can be used to indicate configuration parameters of the OCC sequence.

[0264] The SLIV can be a traditional SLIV, occupying 7 bits to represent a value from 0 to 104. Thus, when the configuration parameters of the SLIV and OCC sequence can share 8 bits, the configuration parameters of the OCC sequence can be indicated using 1 bit. Taking the OCC sequence code length occupying 1 bit as an example, referring to Figure 6, the OCC sequence code length occupies the first bit of the 8 bits, with the remaining 7 bits used to indicate the SLIV. When the first bit is 0, the OCC sequence code length can be 2. When the first bit is 1, the OCC sequence code length can be 4.

[0265] Alternatively, the configuration parameters of the OCC sequence can occupy 3 or 4 bits in the SLIV. Thus, with the OCC sequence configuration parameters occupying 3 bits, the remaining 5 bits of the 8 bits occupied by the SLIV are used to indicate the SLIV. With the OCC sequence configuration parameters occupying 4 bits, the remaining 4 bits of the 8 bits occupied by the SLIV are used to indicate the SLIV. Alternatively, in addition to the traditional 7 bits occupied by the SLIV, 3 or 4 bits can be added for the OCC sequence configuration parameters. That is, with the OCC sequence configuration parameters occupying 3 bits, the SLIV and OCC sequence configuration parameters can together occupy 10 bits. With the OCC sequence configuration parameters occupying 4 bits, the SLIV and OCC sequence configuration parameters can together occupy 11 bits. The method of using 3 or 4 bits to indicate the OCC sequence configuration parameters can be referred to the above and will not be repeated here.

[0266] In other possible implementations, the configuration parameters of the OCC sequence may occupy other information, or may occupy at least one bit of the SLIV and other information, etc., without limitation. In this way, the configuration parameters of the OCC sequence can be indicated by unused bits in the existing information, which can save signaling overhead.

[0267] This application does not limit the number of bits occupied by the configuration parameters of the OCC sequence. It can refer to the aforementioned 3-bit or 4-bit description, or it can be related to the reporting capability of the first communication device. That is, the number of bits occupied by the configuration parameters of the OCC sequence is determined according to the reporting capability of the first communication device. For example, if the first communication device supports reporting information with an OCC sequence code length of 2, but does not support reporting information with an OCC sequence code length of 4, one bit can be used to indicate the index of the OCC sequence, and the code length of the OCC sequence may not be indicated; the code length can be defaulted to 2. As another example, if the first communication device supports reporting information with an OCC sequence code length of 4, two bits can be used to indicate the index of the OCC sequence. The code length of the OCC sequence may default to 4, or another bit can be used to indicate the code length of the OCC sequence. In both of these examples, one bit can also be used to indicate the OCC enable indication. When using the uplink data transmission method described in Method 2 or Method 3, the length of the OCC sequence may not be indicated. The configuration parameters for the OCC sequence can be carried in at least one of DCI, RRC signaling, and MAC CE.

[0268] In some possible implementations, step S302 can be executed when the OCC enable indication is used to process the data to be transmitted using the OCC sequence. Alternatively, step S302 can be executed when the first information is used to indicate at least one of the code length and index of the OCC sequence, and is used to indicate no OCC enable indication. Alternatively, when the first information is used to indicate at least one of the code length and index of the OCC sequence, and is used to indicate an OCC enable indication, if the OCC enable indication is used to instruct the first communication device to process the data to be transmitted using the OCC sequence, step S302 can be executed.

[0269] S302, the first communication device sends uplink data to the second communication device on the resource unit occupied by the PUSCH. The uplink data is the data to be sent on the PUSCH after being processed by the OCC element corresponding to the resource unit in the OCC sequence.

[0270] Correspondingly, the second communication device receives uplink data from the first communication device on the resource unit occupied by the PUSCH.

[0271] This application does not limit the number of resource units occupied by a PUSCH; it can be one or more. Optionally, the number of resource units occupied by a PUSCH is an integer multiple of L, where L is the code length of the OCC sequence. The data carried on each PUSCH should be the same, or it can be data from the same transport block. By transmitting the data carried by the PUSCH multiplied by the corresponding OCC element in the OCC sequence on the PUSCH of each resource unit, data expansion and repeated transmission can be achieved through the OCC sequence, which can improve system capacity and system performance.

[0272] Optionally, the method may further include receiving information A. Information A is used to indicate the resources of the PUSCH, such as one or more resource units occupied by the PUSCH.

[0273] Information A can refer to the description of at least one of the aforementioned TDRA and FDRA, which will not be repeated here. Optionally, information A can be system information, such as SIB. Or it can be configuration information, for example, information A can be higher-layer signaling, such as RRC signaling, MAC CE signaling, etc. Information A can also be physical layer signaling, such as DCI, etc.

[0274] Optionally, information A may also be used to indicate the number of times PUSCH is repeated. This number of repetitions may be an integer multiple of L, and is not limited here.

[0275] It is understood that in the method shown in Figure 3, the configuration parameters of the OCC sequence can be clearly defined through the first information. The OCC element corresponding to the data to be sent on the PUSCH in the OCC sequence can be used to process the data to be sent, thereby enabling data expansion and repeated transmission, which can improve system capacity and system performance.

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

[0277] Please refer to Figure 7, which is a schematic diagram of a communication device provided in an embodiment of this application. The communication device may include a transceiver unit 701 and a processing unit 702. The transceiver unit 701 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 702 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.

[0278] When the communication device is the first communication device, wherein:

[0279] The transceiver unit 701 is used to receive first information; wherein the first information is used to indicate the configuration parameters of the orthogonal overlay code (OCC) sequence;

[0280] Processing unit 702 is used to determine uplink data, wherein the uplink data is the data to be transmitted on the Physical Uplink Shared Channel (PUSCH) after being processed by the OCC element corresponding to the resource unit in the OCC sequence;

[0281] The transceiver unit 701 is also used to send the uplink data on the resource unit occupied by the PUSCH.

[0282] In some possible implementations, the configuration parameters of the OCC sequence include at least one of the code length of the OCC sequence and the index of the OCC sequence.

[0283] In some possible implementations, the configuration parameters of the OCC sequence may also include an OCC enable indicator, which is used to indicate that the data to be transmitted is processed using the OCC sequence.

[0284] In some possible implementations, the first information indicates the configuration parameters of the OCC sequence via 3 or 4 bits of information.

[0285] In some possible implementations, the first information is carried in at least one of the following: Downlink Control Information (DCI), Radio Resource Control (RRC) signaling, and Media Access Control (MAC) Control Unit (CE) signaling.

[0286] In some possible implementations, where the first information is carried in the DCI, the DCI includes a Hybrid Automatic Repeat Request (HARQ) process number, which is used to indicate configuration parameters of the OCC sequence.

[0287] In some possible implementations, the configuration parameters of the OCC sequence include a first parameter and a second parameter. When the first information is carried in the DCI and the RRC signaling, the HARQ process number is used to indicate the first parameter, and the second parameter is indicated by the RRC signaling.

[0288] In some possible implementations, where the first information is carried in the RRC signaling, the RRC signaling includes a configured authorization configuration index, ConfiguredGrantConfigIndex, which is used to indicate the configuration parameters of the OCC sequence.

[0289] In some possible implementations, the configuration parameters of the OCC sequence are included in the time-domain resource configuration of the PUSCH.

[0290] When the communication device is a second communication device, wherein:

[0291] Processing unit 702 is used to determine the configuration parameters of the orthogonal overlay code (OCC) sequence;

[0292] The transceiver unit 701 is used to send first information; wherein the first information is used to indicate the configuration parameters of the OCC sequence;

[0293] The transceiver unit 701 is also used to receive uplink data on the resource unit occupied by the Physical Uplink Shared Channel (PUSCH), wherein the uplink data is the data to be transmitted on the PUSCH after being processed by the OCC element corresponding to the resource unit in the OCC sequence.

[0294] In some possible implementations, the configuration parameters of the OCC sequence include at least one of the code length of the OCC sequence and the index of the OCC sequence.

[0295] In some possible implementations, the configuration parameters of the OCC sequence may also include an OCC enable indicator, which is used to indicate that the data to be transmitted is processed using the OCC sequence.

[0296] In some possible implementations, the first information indicates the configuration parameters of the OCC sequence via 3 or 4 bits of information.

[0297] In some possible implementations, the first information is carried in at least one of the following: Downlink Control Information (DCI), Radio Resource Control (RRC) signaling, and Media Access Control (MAC) Control Unit (CE) signaling.

[0298] In some possible implementations, where the first information is carried in the DCI, the DCI includes a Hybrid Automatic Repeat Request (HARQ) process number, which is used to indicate configuration parameters of the OCC sequence.

[0299] In some possible implementations, the configuration parameters of the OCC sequence include a first parameter and a second parameter. When the first information is carried in the DCI and the RRC signaling, the HARQ process number is used to indicate the first parameter, and the second parameter is indicated by the RRC signaling.

[0300] In some possible implementations, where the first information is carried in the RRC signaling, the RRC signaling includes a configured authorization configuration index, ConfiguredGrantConfigIndex, which is used to indicate the configuration parameters of the OCC sequence.

[0301] In some possible implementations, the configuration parameters of the OCC sequence are included in the time-domain resource configuration of the PUSCH.

[0302] The implementation of the above-mentioned transceiver unit 701 and processing unit 702 can be referred to the relevant description of the method embodiment shown in FIG3, which will not be repeated here.

[0303] Please refer to Figure 8, which is a schematic diagram of another communication device provided in an embodiment of this application. As shown in Figure 8, the communication device may include a processor 111. The processor 111 may also be referred to as a processing unit, which can implement certain control functions. When the processor 111 is running, it causes the communication device to execute any of the methods described in Figure 3 in the embodiment of this application.

[0304] The communication device shown in Figure 8 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 any of the methods described in Figure 3 of this application embodiment.

[0305] Optionally, the processor 111 may include instructions 113 that can be executed on the processor 111 to cause the communication device to perform any of the methods described in FIG3 in the embodiments of this application.

[0306] 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:

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

[0308] (2) A set of one or more ICs, wherein the set of ICs may optionally include at least one of a storage component for storing data and instructions;

[0309] (3) Application-specific integrated circuits (ASICs), such as modems;

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

[0311] Please refer to Figure 9, which is a schematic diagram of the structure of a terminal device provided in an embodiment of this application. For ease of explanation, Figure 9 only shows the main components of the terminal device. As shown in Figure 9, the terminal device includes a processor, a memory, a control circuit, an antenna, and input / output devices. The processor is mainly used to process communication protocols and communication data, control the entire terminal device, execute software programs, and process the data of the software programs. The memory is mainly used to store software programs and data. The radio frequency circuit is mainly used for the conversion between baseband signals and radio frequency signals and the processing of radio frequency signals. The antenna is mainly used for transmitting and receiving radio frequency signals in the form of electromagnetic waves. Input / output devices, such as touch screens, displays, and keyboards, are mainly used to receive user input data and output data to the user.

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

[0313] For ease of explanation, Figure 9 shows only one memory and processor. In actual terminal devices, multiple processors and memories may exist. Memory may also be referred to as storage medium or storage device, etc., and the embodiments of this application do not limit this.

[0314] In one embodiment, the antenna is used to perform the operations performed by the transceiver unit 701 in the above embodiment. The processor can be used to perform the operations performed by the processing unit 702 in the above embodiment.

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

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

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

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

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

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

[0321] This application also provides a communication system, which includes a first communication device and a second communication device. For a detailed description, please refer to the method shown in FIG3.

[0322] The first communication device in this application embodiment can be a terminal as a final product, a component or module with terminal functions, or a communication chip (e.g., processor, baseband chip, or chip system) that can be applied in a terminal. The second communication device in this application embodiment can be a second communication device as a final product, a component or module with second communication device functions, or a communication chip (e.g., processor, baseband chip, or chip system) that can be applied in a second communication device.

[0323] 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), a read-only memory (ROM), a programmable read-only memory (PROM), an erasable programmable read-only memory (EPROM), an electrically erasable programmable read-only memory (EEPROM), or flash memory. Volatile memory can be random access memory (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, used to store at least one of program instructions and data.

[0324] 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), 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.

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

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

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

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

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

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

[0331] 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 first communication device may not perform the steps performed by the first 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.

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

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

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

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

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

[0337] 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 other content besides B, or that A and B are the same content.

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

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

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

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

[0342] 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 in that, include: The first communication device receives first information; wherein the first information is used to indicate the configuration parameters of the orthogonal coverage code (OCC) sequence; The first communication device transmits uplink data on the resource unit occupied by the Physical Uplink Shared Channel (PUSCH). The uplink data is the data to be transmitted on the PUSCH after being processed by the OCC element corresponding to the resource unit in the OCC sequence.

2. The method according to claim 1, characterized in that, The configuration parameters of the OCC sequence include at least one of the following: the code length of the OCC sequence and the index of the OCC sequence.

3. The method according to claim 2, characterized in that, The configuration parameters of the OCC sequence also include an OCC enable indicator, which is used to indicate that the OCC sequence is used to process the data to be transmitted.

4. The method according to any one of claims 1 to 3, characterized in that, The first information indicates the configuration parameters of the OCC sequence through 3 or 4 bits of information.

5. The method according to any one of claims 1 to 4, characterized in that, The first information is carried in at least one of the following: Downlink Control Information (DCI), Radio Resource Control (RRC) signaling, and Media Access Control (MAC) Control Unit (CE) signaling.

6. The method according to claim 5, characterized in that, When the first information is carried in the DCI, the DCI includes a Hybrid Automatic Repeat Request (HARQ) process number, which is used to indicate the configuration parameters of the OCC sequence.

7. The method according to claim 6, characterized in that, The configuration parameters of the OCC sequence include a first parameter and a second parameter. When the first information is carried in the DCI and the RRC signaling, the HARQ process number is used to indicate the first parameter, and the second parameter is indicated by the RRC signaling.

8. The method according to claim 5, characterized in that, When the first information is carried in the RRC signaling, the RRC signaling includes a configured authorization configuration index, ConfiguredGrantConfigIndex, which is used to indicate the configuration parameters of the OCC sequence.

9. The method according to any one of claims 1 to 8, characterized in that, The configuration parameters of the OCC sequence are included in the time-domain resource configuration of the PUSCH.

10. A communication method, characterized in that, include: The second communication device sends first information; wherein the first information is used to indicate the configuration parameters of the orthogonal coverage code (OCC) sequence; The second communication device receives uplink data on the resource unit occupied by the Physical Uplink Shared Channel (PUSCH). The uplink data is the data to be transmitted on the PUSCH multiplied by the OCC element corresponding to the resource unit in the OCC sequence.

11. The method according to claim 10, characterized in that, The configuration parameters of the OCC sequence include at least one of the following: the code length of the OCC sequence and the index of the OCC sequence.

12. The method according to claim 11, characterized in that, The configuration parameters of the OCC sequence also include an OCC enable indicator, which is used to indicate that the OCC sequence is used to process the data to be transmitted.

13. The method according to any one of claims 10 to 12, characterized in that, The first information indicates the configuration parameters of the OCC sequence through 3 or 4 bits of information.

14. The method according to any one of claims 10 to 13, characterized in that, The first information is carried in at least one of the following: Downlink Control Information (DCI), Radio Resource Control (RRC) signaling, and Media Access Control (MAC) Control Unit (CE) signaling.

15. The method according to claim 14, characterized in that, When the first information is carried in the DCI, the DCI includes a Hybrid Automatic Repeat Request (HARQ) process number, which is used to indicate the configuration parameters of the OCC sequence.

16. The method according to claim 15, characterized in that, The configuration parameters of the OCC sequence include a first parameter and a second parameter. When the first information is carried in the DCI and the RRC signaling, the HARQ process number is used to indicate the first parameter, and the second parameter is indicated by the RRC signaling.

17. The method according to claim 14, characterized in that, When the first information is carried in the RRC signaling, the RRC signaling includes a configured authorization configuration index, ConfiguredGrantConfigIndex, which is used to indicate the configuration parameters of the OCC sequence.

18. The method according to any one of claims 1 to 8, characterized in that, The configuration parameters of the OCC sequence are included in the time-domain resource configuration of the PUSCH.

19. A communication device, characterized in that, Includes units for performing the method as described in any one of claims 1 to 18.

20. A communication device, characterized in that, It includes at least one processor, which, when running, causes the method according to any one of claims 1 to 18 to be performed.

21. A computer-readable storage medium, characterized in that, The computer-readable storage medium stores a computer program or instructions that, when executed, cause the method according to any one of claims 1 to 18 to be performed.

22. A computer program product, characterized in that, Includes a computer program or instructions that, when executed, cause the method according to any one of claims 1 to 18 to be performed.

Images