Method and apparatus for uplink capacity enhancement in NR NTN system

Abstract

Provided in the present application are a method and apparatus for uplink capacity enhancement in an NR NTN system. The method comprises: receiving at least one of the following pieces of information: first information, which is used for determining an orthogonal cover code (OCC) scheme for a physical uplink shared channel (PUSCH); second information, which is used for determining an OCC sequence table used for the PUSCH; and third information, which is used for determining an OCC sequence from the OCC sequence table; and sending the PUSCH.

Description

A method and device for enhancing uplink capacity in NR NTN system Technical Field

[0001] The present application relates to the field of communications, and more specifically, to a communication method, and more specifically, to a communication method and apparatus for enhancing uplink capacity in a New Radio Non-terrestrial Network (NR NTN) system. Background Art

[0002] In the NTN system, satellite beams offer a much larger coverage area compared to traditional terrestrial networks due to the greater transmission distance between satellites and UEs. For example, the diameter of a satellite cell can reach 1000 km. Given the large coverage area of ​​satellite beams, the number of UEs within the coverage area is very large. The NTN network already supports IoT device access, and Release 19 also aims to support NR-based RedCap devices. This will inevitably lead to a surge in the number of devices within the coverage area, resulting in very limited uplink spectrum resources for each device in the NTN network. Furthermore, to achieve varying levels of coverage, satellites are generally categorized by altitude into LEO, MEO, and GEO. Even the lowest LEO satellites typically reach an altitude of 600 km, so uplink signals will undoubtedly experience significant path loss during transmission. Due to limited device transmit power and limited uplink resources, the uplink is considered the bottleneck channel in the NTN network.

[0003] Summary of the Invention

[0004] In view of this, one aspect of the present application provides a communication method performed by a UE, the communication method comprising: receiving at least one of the following information: first information for determining an orthogonal cover code OCC scheme for a physical uplink shared channel PUSCH, second information for determining an OCC sequence table for the PUSCH, and third information for determining an OCC sequence in the OCC sequence table; and sending the PUSCH.

[0005] Another aspect of the present application provides an OCC determination method performed by a UE, the OCC determination method including: receiving configuration information; and enabling Type B PUSCH OCC based on the configuration information.

[0006] Another aspect of the present application provides an OCC determination method performed by a UE, the OCC determination method including: receiving configuration information; and enabling PUSCH OCC based on the configuration information.

[0007] Another aspect of the present application provides a communication method performed by a base station, the communication method comprising: receiving at least one of the following information: first information for determining an orthogonal cover code OCC scheme for a physical uplink shared channel PUSCH, second information for determining an OCC sequence table for PUSCH, and third information for determining an OCC sequence in the OCC sequence table; and sending PUSCH.

[0008] Another aspect of the present application provides a computer-readable storage medium, which is used to store a computer program, wherein the computer program enables a computer to execute the above method. BRIEF DESCRIPTION OF THE DRAWINGS

[0009] FIG1 shows a schematic diagram of a communication system according to an embodiment of the present application.

[0010] FIG2 shows a schematic diagram of a communication method according to an embodiment of the present application.

[0011] FIG. 3 is a graph of a Rademacher function according to the related art.

[0012] FIG4 shows a schematic diagram of a communication method according to an embodiment of the present application.

[0013] FIG5 shows a schematic diagram of a nominal PUSCH with unusable symbols according to an embodiment of the present application.

[0014] FIG6 shows a schematic diagram of an OCC determination method according to an embodiment of the present application.

[0015] FIG7 shows a schematic diagram of a PUSCH supporting an OCC solution according to an embodiment of the present application.

[0016] FIG8 shows a schematic diagram of using a PUSCH to support an OCC solution according to an embodiment of the present application.

[0017] FIG9 shows a schematic diagram of an OCC determination method according to an embodiment of the present application.

[0018] FIG10 shows a flowchart of a PUSCH supporting an OCC solution according to an embodiment of the present application.

[0019] FIG11 shows a schematic diagram of a PUSCH supporting an OCC solution according to an embodiment of the present application.

[0020] FIG12 is a block diagram of an example system for wireless communication according to an embodiment of the present application. DETAILED DESCRIPTION

[0021] The following describes the technical solutions in the embodiments of this application in conjunction with the accompanying drawings. It should be understood that the described embodiments are only a portion of the embodiments of this application, not all of them. All other embodiments derived by persons of ordinary skill in the art without inventive effort regarding the embodiments of this application are within the scope of protection of this application. In the embodiments of this application, "configured to," "set to," or "set to" can be implemented by pre-storing corresponding codes, tables, or other methods for indicating relevant information in a device (e.g., an AP or a base station). This application does not limit the specific implementation methods. For example, "defined" or "predefined" can refer to definitions in a protocol. Unless otherwise specified, "multiple" means two or more than two. Furthermore, " / " indicates that the objects associated with each other are in an "or" relationship. For example, A / B can mean either A or B. "And / or" in this application is merely information describing the association of associated objects, indicating that three possible relationships exist. For example, "A and / or B" can mean: A exists alone, A and B exist simultaneously, or B exists alone. A and B can be singular or plural. The terms "first," "second," and so on in this specification are used to distinguish between different objects, not to describe a specific order. A first element / value discussed below could be termed a second element / value without departing from the teachings of one or more embodiments. Describing an element as a "first" element may not require or imply the presence of a second element / value or other elements / values.

[0022] In this application, words such as "exemplary" or "for example" are used to indicate examples, illustrations, or descriptions. Any embodiment or design described in this application as "exemplary" or "for example" should not be construed as preferred or advantageous over other embodiments or designs. Rather, the use of words such as "exemplary" or "for example" is intended to present the relevant concepts in a concrete manner.

[0023] It should be understood that references to "embodiments" throughout this specification mean that a particular feature, structure, or characteristic associated with the embodiment is included in at least one embodiment of the present application. Therefore, various embodiments throughout this specification do not necessarily refer to the same embodiment. Furthermore, these particular features, structures, or characteristics may be combined in any suitable manner in one or more embodiments.

[0024] Section headings are used in this application to improve readability of the specification and do not in any way limit the discussion or embodiments to only the corresponding sections. Furthermore, it is noted that the description given herein focuses on 3GPP cellular communication systems and, therefore, often uses 3GPP terminology or terms similar to 3GPP terminology. However, the concepts disclosed herein are not limited to 3GPP systems.

[0025] Figure 1 is a schematic diagram of the network architecture of a communication system. The communication system may include one or more user equipment (UE) 10 and one or more base stations (BS) 20. Figure 1 is merely a schematic diagram and does not limit the applicable scenarios of the technical solutions provided in the embodiments of this application.

[0026] The UE 10 may include various UE devices, such as mobile phones (or "cellular" phones), computers with mobile UEs, portable, pocket-sized, handheld, or computer-built-in mobile devices, etc. For example, Personal Communication Service (PCS) phones, cordless phones, Session Initiation Protocol (SIP) phones, Wireless Local Loop (WLL) stations, Personal Digital Assistants (PDAs), and other devices, as well as limited devices (e.g., devices with low power consumption, or devices with limited storage capacity or computing capacity), are not limited here.

[0027] The technology described in this application can be implemented by devices in a wireless communication system 100. The communication system 100 shown in FIG1 can also be an NTN system. Specifically, NTN technology generally uses satellite communications to provide communication services to terrestrial users. In other words, the network device 110 in FIG1 can be a satellite.

[0028] Base station 20 is the access device that allows UEs to wirelessly access the mobile communication system. The base station transmits wireless signals to UEs in the wireless network. This type of transmission is commonly referred to as uplink or uplink transmission. For some other transmissions, the direction of transmission can be reversed. Although for convenience, this application primarily uses the terms "downlink" and "uplink," similar techniques can also be used in other situations involving bidirectional transmission.

[0029] In a frequency division multiplexing (FDM) network, transmissions to and from a base station may occupy different frequency bands (each frequency band may occupy a continuous or non-contiguous spectrum). In a time division multiplexing (TDM) network, transmissions to and from a base station occupy the same frequency band but are separated in the time domain using TDM mechanisms (e.g., slot-based transmissions). Other types of multiplexing may also be used (e.g., code division multiple access, OTFS multiplexing, spatial multiplexing, etc.). In general, various multiplexing schemes may be combined with one another. For example, in a spatial multiplexing system, transmissions between two different user devices may be isolated from one another by utilizing a directional difference or azimuth difference between the two endpoints (e.g., a user device and a network station such as a base station).

[0030] Starting from R16, research on uplink channel enhancement in NR has begun. UE can achieve uplink coverage enhancement by repeatedly transmitting PUSCH / PUCCH channels multiple times. In the coverage enhancement WID of R17, the number of PUSCH repetitions has increased from 16 to 32 times. Although multiple repeated transmissions improve communication reliability, it means that more resources are used to transmit the same data, which sacrifices the transmission capacity of the system. Therefore, orthogonal cover codes (OCC) have been introduced to enhance the physical uplink control channel (PUCCH). Different OCC codes can be multiplied on the repeated signals, and multiple UEs can be multiplexed on the same time-frequency domain resources, thereby improving system capacity and throughput. The WID of R19 mentioned that the OCC codes across OFDM symbols, across time slots, and within OFDM symbols can be considered to enhance the PUSCH channel.

[0031] This application further describes the mapping mechanism between OCC and PUSCH.

[0032] Embodiments of the present application provide a communication method performed by a user equipment (UE), the communication method comprising: receiving at least one of first information, second information, and third information, the first information being used to determine an orthogonal cover code (OCC) scheme for a physical uplink shared channel (PUSCH), the second information being used to determine an OCC sequence table for the PUSCH, and the third information being used to determine an OCC sequence in the OCC sequence table; and transmitting the PUSCH, as shown in FIG2 . Therefore, by utilizing OCC to enhance the PUSCH channel, i.e., by multiplying repeated signals with different OCC codes, multiple UEs can be multiplexed on the same time-frequency domain resources, thereby improving system capacity and throughput.

[0033] The first information, the second information, and the third information may be the same or different information and may be received simultaneously or at different times. At least one of the first information, the second information, and the third information is carried in at least one of RRC signaling, a medium access control-control element MAC-CE, downlink control information DCI, a system information block SIB, and a random access response RAR. Here, after multiple types of OCC schemes / OCC sequence tables / OCC sequences are configured in RRC signaling, one of the multiple types of OCC schemes OCC sequence tables / OCC sequences will be activated by medium access control-control element (MAC-CE) or radio resource control layer (RRC) signaling. For ease of description, the following description of the step of activating one of the multiple types of OCC schemes OCC sequence tables / OCC sequences may be omitted. The first to third information and the configuration method for indicating the OCC scheme, OCC sequence table, and OCC sequence will be described below.

[0034] First, first information for indicating an OCC scheme and a configuration method of the first information are described.

[0035] 1. Indications for different OCC schemes

[0036] The OCC scheme includes six types: inter-symbol OCC, inter-symbol group OCC, inter-time slot OCC, inter-time slot group OCC, inter-redundancy version RV OCC and intra-symbol OCC. In the current protocol, the physical uplink shared channel (PUSCH) does not support the OCC scheme, and the user equipment may have multiple mapping methods. For example: in a time slot, the UE repeats 4 times. At this time, the OCC scheme can be cross-symbol group or cross-symbol. Therefore, during actual scheduling, the base station needs to indicate the OCC scheme. The OCC scheme here can also be called OCC mapping or OCC mapping scheme.

[0037] RRC configures the predetermined OCC solution

[0038] In some embodiments, the first information is used to indicate an OCC scheme for a PUSCH. The first information is carried in radio resource control (RRC) signaling. The RRC signaling includes PUSCH-Config or ConfiguredGrantConfig, and a parameter PUSCH-OCCScheme is configured in the PUSCH-Config or ConfiguredGrantConfig to a first predetermined value to determine a predetermined OCC scheme.

[0039] In some examples, the base station configures the parameter PUSCH-OCCScheme to a predetermined value to determine a predetermined OCC scheme. For example, the parameter PUSCH-OCCScheme is configured to 0 to indicate that the OCC scheme is inter-slot OCC; the parameter PUSCH-OCCScheme is configured to 1 to indicate that the OCC scheme is inter-symbol OCC; the parameter PUSCH-OCCScheme is configured to 2 to indicate that the OCC scheme is intra-symbol OCC; the parameter PUSCH-OCCScheme is configured to 3 to indicate that the OCC scheme is inter-redundancy version RV OCC; the parameter PUSCH-OCCScheme is configured to 4 to indicate that the OCC scheme is inter-symbol group OCC; or the parameter PUSCH-OCCScheme is configured to 5 to indicate that the OCC scheme is inter-slot group OCC. It is well known to those skilled in the art that although six types of OCC schemes are given in the above examples, the present application is not limited thereto.

[0040] Configure multiple OCC schemes and activate one of them through Media Access Control-Control Element (MAC-CE) or Radio Resource Control (RRC) signaling

[0041] In some embodiments, the first information is used to indicate the OCC scheme for PUSCH, thereby determining the OCC scheme for PUSCH. For dynamically scheduled PUSCH, the first information is carried on RRC signaling. RRC signaling includes PUSCH-Config, and the parameter PUSCH-OCCScheme is defined in PUSCH-Config to indicate multiple types of OCC schemes. For example, as shown below, the parameter PUSCH-OCCSchemelist (or referred to as the first parameter) is defined in the signaling PUSCH-Config to indicate inter-symbol OCC, inter-symbol group OCC, inter-time slot OCC, inter-time slot group OCC, OCC between redundant versions RV and intra-symbol OCC. PUSCH-OCCScheme represents any one of these six schemes. The UE receives one of the multiple types of OCC schemes activated by the medium access control-control element MAC-CE or the radio resource control layer RRC. Here, for ease of description, the expression "determining the OCC scheme / OCC sequence table / OCC sequence for PUSCH by indicating the OCC scheme / OCC sequence table / OCC sequence for PUSCH" will be abbreviated as "indicating the OCC scheme / OCC sequence table / OCC sequence for PUSCH".

[0042] Reinterpret the DCI field to indicate the OCC scheme

[0043] In some embodiments, the first information may be carried on a Directed Commitment Information (DCI), where the DCI includes a first field for indicating one or more OCC schemes. The field includes one of a Modulation and Coding Scheme (MCS) field, a Hybrid Automatic Repeat Request (HARQ) field, and a Time Domain Resource Allocation (TDRA) field, to indicate the OCC scheme used for the PUSCH. In some examples of the present application, the first information is carried on Downlink Control Information (DCI). After RRC is enabled, the DCI field includes several bits for indicating several OCC schemes. For example, an existing field in the DCI may be reinterpreted so that the ceil(log2(N)) bits in the field indicate N types of OCC schemes. For example, the OCC scheme may be indicated by adding a new field, OCCScheme, to the DCI. The OCCScheme field may also be referred to as the OCCScheme field. For example, the OCC scheme may be indicated by the ceil(log2(N)) bits in the DCI field, where N is the number of OCC scheme types and ceil is a rounding function. Alternatively, the OCC scheme may be indicated using joint coding of the DCI field or by several bits in the field.

[0044] A column of parameters PUSCH-OCCIndex is added to TDRA and a parameter PUSCH-OCCScheme is defined in TDRA to indicate the OCC scheme. Each row of the parameter PUSCH-OCCScheme indicates any OCC scheme.

[0045] Because the information transmission rate in NTN scenarios is currently not very high, the demand for high-order modulation is not very high. In addition, due to the long transmission distance, the signal quality is relatively poor, and high-order modulation has poorer anti-interference capabilities than low-order modulation, so the demand for high-order modulation is not high. In the prior art, the modulation and coding scheme (MCS) field of the DCI has 5 bits to indicate 32 states. In some examples of this application, 2 bits in the MCS field of the DCI can be used to indicate the OCC scheme, and the remaining 3 bits in the MCS field can be used to indicate 8 of the 32 states. For example, the 8 states are 8 states corresponding to 2nd-order modulation. Alternatively, the 8 states include 2 states corresponding to 2nd-order modulation, 2 states corresponding to 4th-order modulation, and 2 states corresponding to 6th-order modulation. This application is not limited to this. In the above embodiments of this application, 2 bits in the MCS field of the DCI are used to indicate the OCC scheme, but the number of bits used to indicate the OCC scheme is not limited to this. The OCC scheme can be indicated using 1 bit, 3 bits, or more bits in the MCS field of the DCI. Here, the MCS domain may also be referred to as domain MCS.

[0046] In some examples of the present application, the OCC scheme can be indicated by 2 bits in the hybrid automatic repeat request (HARQ) field of the DCI. For example, in one example, for DCI format 0_0, the HARQ field has 4 bits. The OCC scheme can be indicated by 2 bits in the HARQ field of the DCI, and the remaining 2 bits in the HARQ field are used to indicate that the maximum supported HARQ number is 4. In one example, for DCI format 1_0, if the high-level parameter harq-ProcessNumberSizeDCI-0-1 is configured, the HARQ field has 5 bits. The OCC scheme can be indicated by 2 bits in the HARQ field of the DCI, and the remaining 3 bits in the HARQ field are used to indicate that the maximum supported HARQ number is 8. In one example, for DCI format 0_2, the high-level parameter harq-ProcessNumberSizeDCI-0-2-r17 can configure the HARQ domain to be 0, 1 bit, 2 bits, 3 bits, 4 bits, or 5 bits. The 2 bits in the HARQ domain of the DCI can be used to indicate the OCC scheme, and the remaining 0 bits, 1 bit, 2 bits, or 3 bits in the HARQ domain are not limited to this. The number of bits used to indicate the OCC scheme in the HARQ domain in this application is not limited to this, and it can be 1 bit, 3 bits, or more bits. The HARQ domain here may also be referred to as domain HARQ.

[0047] MAC-CE activates a group of OCC schemes, and DCI indicates one OCC scheme in the group

[0048] In some embodiments, for dynamically scheduled PUSCH, the first information is carried on the radio resource control RRC signaling. The RRC signaling includes PUSCH-Config, and the parameter PUSCH-OCCSchemelist is defined in PUSCH-Config to indicate multiple types of OCC schemes. For example, as shown below, the parameter PUSCH-OCCSchemelist is defined in the signaling PUSCH-Config to indicate inter-symbol OCC, inter-symbol group OCC, inter-time slot OCC, inter-time slot group OCC, inter-redundancy version RV OCC and intra-symbol OCC respectively. After configuring N types of OCC schemes, the UE receives a group of OCC schemes from the multiple types of OCC schemes activated by the medium access control-control element MAC-CE or the radio resource control layer RRC, and one of the OCC schemes in the group is indicated by downlink control information (DCI), and the group of OCC schemes includes more than one OCC scheme. In some embodiments, one of the OCC schemes in the group is indicated by the MCS domain, HARQ domain or a newly added domain of the downlink control information (DCI). Here, the HARQ domain may also be referred to as domain HARQ.

[0049] In some examples of the present application, two OCC schemes are activated by MAC-CE. The value of a bit (e.g., MSB bit) in the MCS field of the DCI is set to 1 to indicate one of the two OCC schemes, and the value of the 1 bit is set to 0 to indicate the other of the two OCC schemes. In some examples of the present application, two OCC schemes are activated by MAC-CE. The value of a bit (e.g., MSB bit) in the HARQ field of the DCI is set to 0 to indicate one of the two OCC schemes, and the value of the 1 bit (e.g., MSB bit) is set to 1 to indicate the other of the two OCC schemes. In some examples of the present application, two OCC schemes are activated by MAC-CE. In some examples of the present application, two OCC schemes are activated by MAC-CE. The OCC scheme is indicated by a newly added field of at least 1 bit in the DCI.

[0050] Implicit OCC scheme

[0051] In some embodiments, the OCC scheme includes inter-symbol OCC, inter-symbol group OCC, inter-slot OCC, inter-slot group OCC, inter-redundancy version RV OCC, and / or intra-symbol OCC. The transmission type of the PUSCH can be determined according to the PUSCH configuration information, and the OCC scheme can be determined according to the transmission type of the PUSCH. Determining the OCC scheme according to the transmission type of the PUSCH includes: when the transmission type of the PUSCH is a non-repeated PUSCH, the OCC scheme is inter-symbol OCC or intra-symbol OCC; when the transmission type of the PUSCH is a PUSCH with mapping type B repetition, the OCC scheme is inter-repetition OCC or inter-symbol group OCC; when the transmission type of the PUSCH is a PUSCH with mapping type A repetition, the OCC scheme is inter-slot OCC or inter-slot group OCC.

[0052] The above describes the communication method performed by the UE. Correspondingly, the corresponding communication method can be performed by the base station, and a detailed description will not be given here.

[0053] 2. Indication of orthogonal sequence mapping tables of different lengths

[0054] After the OCC scheme is determined, the OCC multiplexing granularity in different schemes is determined, and the sequence type and the length of the OCC sequence need to be further determined. The length of the OCC sequence is related to the number of repetitions, the number of scheduled time slots, and the number of resource blocks (RBs) in the symbol, respectively. However, the length of the OCC sequence in different OCC schemes is different, and the corresponding OCC sequence tables are also different. As for the sequence type, the sequence types used in existing protocols are mainly Walsh sequences and DFT sequences. The Walsh sequence is suitable for OCC sequence lengths that are integer powers of 2, and the length of the DFT sequence can be either odd or even. For these two sequence types, how to indicate OCC sequence tables of different lengths is a topic currently under study.

[0055] To this end, a communication method performed by a UE is provided, the communication method at least comprising: receiving second information to indicate an OCC sequence table for an uplink physical shared channel (PUSCH). The second information for indicating the OCC sequence table and a method for configuring the second information will be described below.

[0056] RRC configuration specific OCC sequence table

[0057] In some embodiments, the second information is used to determine an OCC sequence table for an uplink physical shared channel (PUSCH). The second information is carried in RRC signaling, which includes PUSCH-Config or ConfiguredGrantConfig. A predetermined parameter PUSCH-OCCTable is configured in PUSCH-Config or ConfiguredGrantConfig to determine a predetermined OCC sequence table. The parameter PUSCH-OCCTable is set to a predetermined value to determine an OCC sequence table of a predetermined length.

[0058] RRC configures OCC tables of different lengths and activates one of them through MAC-CE or RRC

[0059] In some embodiments, the second information is used to indicate an OCC sequence table for an uplink shared physical channel (PUSCH), and the second information is carried in RRC signaling; one of the OCC sequence tables with different lengths is activated by medium access control-control element MAC-CE signaling. The configuration method of the second information on the base station side is as follows:

[0060] RRC signaling includes PUSCH-Config, in which the base station defines the parameter PUSCH-OCCTable to indicate OCC sequence tables of different lengths, regardless of whether the OCC sequence type is a Walsh sequence or a DFT sequence. For example, an OCC sequence of length 2 is shown in Table 1, an OCC sequence of length 4 is shown in Table 2, and an OCC sequence of length 8 is shown in Table 1. Where Index n represents the index of the sequence in the OCC sequence table, and W(i) represents the sequence in the OCC sequence table. For example, in a sequence table with an OCC length of 2, index n in the second row is 1, and [1 -1] indicates that W(0) is 1 and W(1) is -1.

[0061] Table 1 Sequence list of OCC length 2

[0062] Table 2 Sequence list of OCC length 4

[0063] Table 3 Sequence list with OCC length of 8

[0064] In some examples, a parameter PUSCH-OCCTable is defined in PUSCH-Config to indicate OCC sequence tables (also known as orthogonal sequence tables) of different or identical lengths, thereby pre-defining OCC sequence tables of different lengths, including either Walsh sequences or DFT sequences. The OCC sequence tables of different or identical lengths are then activated by the MAC-CE signaling or the RRC signaling.

[0065] For example, the maximum length of the OCC sequence is M, and based on the Walsh sequence, the lengths are defined as 2, 4, ..., 2. N+1 The OCC sequence table is allocated to the UE through RRC. For example, the parameter PUSCH-OCCTable is defined in the PUSCH-Config in the signaling RRC to indicate the OCC sequence table of different lengths. The parameter PUSCH-OCCTable can be set to take values ​​from 0, 1, ..., N. When the parameter PUSCH-OCCTable is set to take values ​​from 0, 1, ..., or N, it indicates that the length is 2, 4, ..., or 2 N+1 The OCC sequence table is an integer greater than or equal to 0. Based on the DFT sequence, the parameter PUSCH-OCCTable is set to take values ​​from N+1, N+2, ..., M. When the parameter PUSCH-OCCTable is set to take values ​​from N+1, N+2, ..., or M, it indicates an OCC sequence table with lengths of N+1, N+2, ..., or M, respectively. In summary, the parameter PUSCH-OCCTable is defined in PUSCH-Config in the signaling RRC, and the parameter PUSCH-OCCTable can be set to 0, 1, ..., or M.

[0066] For example, the maximum length of the OCC sequence is 8. Based on the Walsh sequence, OCC sequence tables with lengths of 2, 4, and 8 are defined. The parameter PUSCH-OCCTable is defined in the PUSCH-Config in the signaling RRC to indicate OCC sequence tables of different lengths. The parameter PUSCH-OCCTable takes values ​​of {0, 1, 2}. When the parameter PUSCH-OCCTable is set to 0, 1, or 2, it indicates an OCC sequence table with a length of 2, 4, or 8. Based on the DFT sequence, the parameter PUSCH-OCCTable takes values ​​of {3, 4, ..., 8}. When the parameter PUSCH-OCCTable is set to 3, 4, ..., or 8, it indicates an OCC sequence table with a length of 3, 4, ..., 8, respectively.

[0067] OCC sequence table for reusing existing PUCCH

[0068] In some embodiments, the PUCCH OCC table is multiplexed into the PUSCH OCC sequence table. For example, PUCCH OCC tables with lengths of 2 and 4 are multiplexed into the PUSCH OCC sequence table. The multiplexed PUCCH OCC sequence table is determined based on the PUSCH symbol length or the number of PUSCH repetitions. For example, if the PUSCH repetition number is 4, the PUCCH OCC table with length 4 is multiplexed.

[0069] UE generates OCC sequence table through formula

[0070] In some embodiments, the second information is used to indicate an OCC sequence table for an uplink shared physical channel (PUSCH). The second information is carried on RRC signaling. The RRC signaling includes PUSCH-Config or ConfiguredGrantConfig. A parameter PUSCH-OCCSequence (hereinafter referred to as the third parameter) is defined in PUSCH-Config or ConfiguredGrantConfig, wherein the value of the parameter PUSCH-OCCSequence is set to Walsh or DFT to indicate that the sequence type is a Walsh sequence or a DFT sequence, respectively. The RRC signaling is also used to indicate the length of the OCC sequence, so that the UE generates an OCC sequence table based on the sequence type and sequence length.

[0071] In some examples, the second information is used to indicate an OCC sequence table for an uplink shared physical channel PUSCH. The second information is carried on RRC signaling. RRC signaling includes PUSCH-Config or ConfiguredGrantConfig. The parameter PUSCH-OCCSequence and the parameter OCC-PUSCHLength (or referred to as the fourth parameter) are defined in PUSCH-Config or ConfiguredGrantConfig, wherein the value of the parameter PUSCH-OCCSequence is set to Walsh or DFT to indicate that the sequence type is a Walsh sequence or a DFT sequence, respectively. The value of the parameter OCC-PUSCHLength is set to a predetermined value for determining the length of a predetermined OCC sequence, and MAC-CE activates a specific OCC sequence type, so that the UE generates an OCC sequence table based on the activated sequence type and the predetermined OCC sequence length.

[0072] In some examples, the second information is used to indicate an OCC sequence table for an uplink shared physical channel PUSCH. The second information is carried on RRC signaling. RRC signaling includes PUSCH-Config or ConfiguredGrantConfig. The parameter PUSCH-OCCSequence and the parameter OCC-PUSCHLength are defined in PUSCH-Config or ConfiguredGrantConfig, wherein the value of the parameter PUSCH-OCCSequence is set to Walsh or DFT to indicate that the sequence type is a Walsh sequence or a DFT sequence, respectively. The value of the parameter OCC-PUSCHLength is set to 1, 2, 3, ..., N to indicate OCC sequences of different lengths, respectively (where N is an integer greater than 0). MAC-CE activates a specific OCC sequence type and OCC sequence length, so that the UE generates an OCC sequence table based on the sequence type and sequence length. In one example, the value of the parameter OCC-PUSCHLength is set to 1, 2, 3, ..., 8 to indicate predetermined OCC sequences of different lengths, respectively.

[0073] In some examples, the second information is used to indicate an OCC sequence table for an uplink shared physical channel PUSCH. The second information is carried on RRC signaling. RRC signaling includes PUSCH-Config or ConfiguredGrantConfig. The parameter PUSCH-OCCSequence is defined in PUSCH-Config or ConfiguredGrantConfig, wherein the value of the parameter PUSCH-OCCSequence is set to Walsh or DFT to indicate that the sequence type is a Walsh sequence or a DFT sequence, respectively. The PUSCH repetition number indicates the length of the OCC sequence. After the OCC scheme has been determined, the granularity of OCC multiplexing has actually been determined. In one example, the sequence length of the OCC sequence is based on the repetition number of PUSCH-TimeDomainResourceAllocation in the PUSCH-Config, or based on the PUSCH repetition number or the number of symbols not transmitted repeatedly, or based on the number of RBs.

[0074] The formula for generating a sequence table using the sequence type and the length of the OCC sequence will be described below.

[0075] For Walsh sequences, taking the OCC length of 8 as an example:

[0076] Walsh function of Hadamard sorting:

[0077] where R (k+1,t)is an arbitrary Rademaker function, k > represents the kth digit of the binary code in reverse order, where P is a positive integer such that p = log2M, where M represents the sequence length. For example, if M = 8, p = log28 = 3.

[0078] Rademacher function: R(n,t)=sign[sin(2 n πt)]

[0079] Therefore, according to the formula (the corresponding curve is shown in Figure 3), we can get: R(0,t)=1 t∈[0,1)

[0080] R(m,t)=R(1,2 m-1 ·t) t∈[0,1) m=2,3,…,

[0081] We can further get 8 W(i,t): Wal H (0,t)=1------————————--{1,1,1,1,1,1,1,1} Wal H (1,t)=R(3,t)------{1,-1,1,-1,1,-1,1,-1} Wal H (2,t)=R(2,t)------{1,1,-1,-1,1,1,-1,-1} Wal H (3,t)=R(2,t)R(3,t)---————-{1,-1,-1,1,1,-1,-1,1} Wal H (4,t)=R(1,t)------————--{1,1,1,1,-1,-1,-1,1} Wal H (5,t)=R(1,t)R(3,t)-------{1,-1,1,-1,-1,-1,-1,1} Wal H (6,t)=R(1,t)R(2,t)--------{1,1,-1,-1,-1,-1,1,1} Wal H (7,t)=R(1,t)R(2,t)R(3,t)--——-{1,-1,-1,-1,1,1,-1}

[0082] For a DFT sequence, taking OCC length 4 as an example:

[0083] The orthogonal sequence based on DFT can be expressed by the formula ​Produced, where N SF Indicates the length of the OCC sequence, m = 0, 1, ..., N SF represents the row index of the orthogonal sequence, and i represents the sequence column index.

[0084] When the OCC length is 4, the generated orthogonal sequence is:

[0085] m=0,W0=1,W1=1,W2=1

[0086] m=1,W0=1,,

[0087] m=2,W0=1,,

[0088] m=3,W0=1,,

[0089] Likewise, the inner product between any two rows is 0, satisfying orthogonality.

[0090] The above describes a communication method performed by a UE. Correspondingly, a corresponding communication method can be performed by a base station. That is, a communication method performed by a base station, the communication method comprising: receiving at least one of first information, second information, and third information, the first information being used to determine an orthogonal cover code OCC scheme for a physical uplink shared channel PUSCH, the second information being used to determine an OCC sequence table for PUSCH, and the third information being used to determine an OCC sequence in the OCC sequence table; and sending PUSCH, as shown in FIG4 . Therefore, by utilizing OCC to enhance the PUSCH channel, that is, by multiplying different OCC codes on repeated signals, multiple UEs can be multiplexed on the same time-frequency domain resources, thereby improving system capacity and throughput. A detailed description will not be given here.

[0091] 3. Indication of sequences in the OCC sequence listing

[0092] After determining the OCC scheme and OCC sequence table, different OCC sequences need to be selected based on the sequence index in the OCC sequence table. Here, "indicating an OCC sequence" includes indicating the OCC sequence index to determine the OCC sequence. For example, if the OCC sequence length is 8, this indicates that the OCC sequence table contains eight orthogonal OCC sequences corresponding to eight states. Accordingly, three bits are required to indicate the eight indices in the OCC sequence table.

[0093] To this end, embodiments of the present application provide a communication method performed by a UE, the communication method comprising at least receiving third information indicating an index of an OCC sequence in a table of orthogonal cover codes (OCC) for a PUSCH. The third information indicating the OCC sequence and a method for configuring the third information will be described below.

[0094] OCC sequence index in the RRC or MAC-CE indication table

[0095] In some embodiments, for dynamically scheduled PUSCH, the third information is carried in RRC signaling or MAC-CE. The parameter OCC-Index (or referred to as the fifth parameter) is defined in PUSCH-Config. The parameter OCC-Index represents a sequence in the OCC sequence table and takes values ​​{0, 1, 2, ..., N-1}, where N is the length of the OCC sequence table and N is an integer greater than 0. One of the OCC sequences is determined by MAC-CE or RRC signaling. Taking the OCC sequence table as having a length of 8 (indicating 8 states) as an example, each state represents an OCC sequence, and the parameter OCC-Index takes values ​​{0, 1, 2, ..., 7}.

[0096] A new field is defined in DCI to indicate the index of the OCC sequence

[0097] In some embodiments, the OCC sequences in the OCC sequence table are orthogonal to each other. For example, the third information carried in the DCI includes a second field for indicating the OCC sequence.

[0098] In one example, PUSCH-OCCTable (as the second field) is defined in DCI to indicate the OCC sequence. The field PUSCH-OCCTable includes a field for indicating 2 N The OCC sequence is N bits long, where N is an integer greater than 0; DCI is received to indicate the index of the OCC sequence in the orthogonal cover code OCC sequence table used for PUSCH. For example, a new field PUSCH-OCCTable (also referred to as PUSCH-OCCTableIndex field; similar terms such as *field and field* below may represent the same field) is defined in the DCI to indicate the OCC sequence. For example, taking an OCC length of 8 as an example, the PUSCH-OCCTable field requires 3 bits to indicate 8 states.

[0099] Defining a new field in DCI also introduces a new problem: this undoubtedly changes the size of the DCI. If a new field is added to the DCI used for uplink scheduling, the size of the DCI used for uplink scheduling will differ from the size of the DCI used for downlink scheduling. Therefore, the size of the DCI used for downlink scheduling also needs to be changed accordingly. The purpose of this is to align the size of the DCI used for uplink scheduling with the size of the DCI used for downlink scheduling, reduce the number of blind detections of the UE, and thus save UE energy consumption. The following provides some examples of methods for solving the above problems according to the present application.

[0100] To this end, in some embodiments, when it is determined that the size of the uplink scheduled DCI is larger than the size of the downlink scheduled DCI, N bits of zero padding are generated in the downlink scheduled DCI until the size of the uplink scheduled DCI is equal to the size of the downlink scheduled DCI. In some examples of the present application, when the DCI with the new field added is DCI format 0_0, if the size of DCI 0_0 is larger than the size of DCI 1_0, then N bits of zero (0) padding are generated in DCI 1_0 until the size of DCI 1_0 is equal to DCI 0_0, and N may be equal to or not equal to the size of the PUSCH-OCCTable field. In some examples of the present application, when the DCI with the new field added is DCI format 0_1, if the size of DCI 0_1 is larger than the size of DCI 1_1, then N bits of zero (0) padding are generated in DCI 1_1 until the size of DCI 1_1 is equal to DCI 0_1, and N may be equal to or not equal to the size of the PUSCH-OCCTable field. In some examples of the present application, when the DCI with a new field added is DCI format 0_2, if the size of DCI 0_2 is larger than the size of DCI 1_2, then N bits of zero (0) padding bits are generated in DCI 1_2 until the size of DCI 1_2 is equal to DCI 0_2, and N may be equal to or not equal to the size of the PUSCH-OCCTable field. In some examples of the present application, when the DCI with a new field added is DCI format 0_3, if the size of DCI 0_3 is larger than the size of DCI 1_3, then N bits of zero (0) padding bits are generated in DCI 1_3 until the size of DCI 1_3 is equal to DCI 0_3, and N may be equal to or not equal to the size of the PUSCH-OCCTable field.

[0101] Joint coding with TDRA in the DCI domain

[0102] In one example, the third information carried in the DCI includes a second field for indicating an OCC sequence. In another example, the third information is carried in the DCI and is associated with a TDRA table carrying OCC sequence-related parameters. In some examples, a parameter column PUSCH-OCCIndex (or referred to as a sixth parameter) is added to the TDRA and the parameter PUSCH-OCCIndex is defined in the TDRA to indicate the OCC sequence, with each row indicating any row of the OCC sequence in the OCC sequence table.

[0103] Reinterpret some fields in the existing DCI

[0104] In some embodiments, the third information carried in the DCI includes a second field for indicating the OCC sequence. In some examples of the present application, the third information is carried on the DCI that carries parameters related to the OCC sequence. For example, the OCC sequence in the OCC sequence table is indicated by the ceil(log2(N)) bits in the field (as the second field) of the downlink control information DCI, where N is the number of types of OCC schemes and ceil is a rounding function. For example, the existing field in the DCI can be reinterpreted as the second field so that the ceil(log2(N)) bits in the field are used to indicate the OCC sequence in the OCC sequence table. For example, the OCC sequence in the OCC sequence table can be indicated by adding a new field OCCScheme (also referred to as the OCCScheme field, as the second field) in the DCI.

[0105] Because the current information transmission rate in the NTN scenario is not very high, the demand for high-order modulation is not very high. In addition, due to the long transmission distance, the signal quality is relatively poor. Since high-order modulation has worse anti-interference capability than low-order modulation, the demand for high-order modulation is not high. Therefore, 2 bits can be extracted from the MCS field to indicate the OCC sequence in the OCC sequence table.

[0106] In the prior art, the MCS field of the DCI (as the second field) has 5 bits to indicate 32 states. In some examples of the present application, 2 bits in the MCS field of the DCI can be used to indicate the OCC sequence in the OCC sequence table, and the remaining 3 bits in the MCS field can be used to indicate 8 of the 32 states. For example, the 8 states can be 8 states corresponding to 2-order modulation. Alternatively, the 8 states can include 2 states corresponding to 2-order modulation, 2 states corresponding to 4-order modulation, and 2 states corresponding to 6-order modulation. In the above embodiment of the present application, 2 bits in the MCS field of the DCI are used to indicate the OCC sequence in the OCC sequence table, but the number of bits used to indicate the OCC sequence in the OCC sequence table is not limited to this. 3 bits or more in the MCS field of the DCI can be used to indicate the OCC sequence in the OCC sequence table. The number of bits in the DCI field used to indicate the OCC sequence in the OCC sequence table in the present application is not limited to this, and can be 1 bit or 3 bits or more.

[0107] In some examples of the present application, 1 bit of the HARQ process number field (as the second field) of the hybrid automatic repeat request (HARQ) of the DCI can be used to indicate the OCC sequence in the OCC sequence table. For example, in one example, for DCI format 0_0, the HARQ field has 4 bits. 1 bit in the HARQ field of the DCI can be used to indicate the OCC sequence in the OCC sequence table, and the remaining 3 bits in the HARQ field are used to indicate that the maximum supported HARQ number is 8. In one example, for DCI format 1_0, if the high-level parameter harq-ProcessNumberSizeDCI-0-1 is configured, the HARQ field has 5 bits. 1 bit in the HARQ field of the DCI can be used to indicate the OCC sequence, and the remaining 4 bits in the HARQ field are used to indicate that the maximum supported HARQ number is 16. In one example, for DCI format 0_2, the high-level parameter harq-ProcessNumberSizeDCI-0-2-r17 can configure the HARQ field to 0, 1 bit, 2 bits, 3 bits, 4 bits, or 5 bits. The 2 bits in the HARQ field of the DCI can be used to indicate the OCC sequence. In this case, 0 bits, 1 bit, 2 bits, 3 bits, or 4 bits remain in the HARQ field. The number of bits in the HARQ field used to indicate the OCC sequence in the OCC sequence table in the present application is not limited thereto and can be 2 bits or more.

[0108] The above describes the communication method performed by the UE. Correspondingly, the corresponding communication method can be performed by the base station, and a detailed description will not be given here.

[0109] 4. How does msg3 PUSCH indicate the OCC sequence index?

[0110] Unlike PUSCH dynamically scheduled by DCI, for Msg 3 PUSCH scheduling, the UE monitors the PDCCH carrying RAR scheduling information within a configured time window, and the corresponding DCI is scrambled by the RA-RNTI. According to existing standards, DCI scrambled by the RA-RNTI has a reserved bit (16-A), where A represents the least significant bit (LSB) of the system frame number (SFN). Therefore, the OCC can be indicated by the DCI scheduling the RAR.

[0111] When the UE receives the RAR message, it will send msg3PUSCH according to the uplink information configured by the RAR. In order to enable OCC for Msg3PUSCH, the following communication method is proposed.

[0112] Some embodiments of the present application provide a communication method performed by a UE, the communication method comprising at least: receiving first information, the first information being used to indicate an OCC scheme for Msg3 PUSCH, receiving second information, the second information being used to indicate an OCC sequence table for Msg3 PUSCH; receiving third information, the third information being carried in a random access response RAR, the RAR including a field for indicating an OCC sequence in the OCC sequence table; and sending PUSCH.

[0113] The OCC sequence is indicated by RA-RNTI scrambling DCI

[0114] In some embodiments, since Msg3 PUSCH currently only supports Type A PUSCH, it is possible to directly define Msg3 PUSCH to be associated with a fixed OCC scheme, such as one of inter-symbol OCC, inter-symbol group OCC, inter-slot OCC, inter-slot group OCC, inter-redundancy version RV OCC, and intra-symbol OCC.

[0115] In some examples, a communication method includes at least: receiving first information indicating an orthogonal cover code (OCC) scheme for a Msg3 PUSCH; receiving second information indicating an OCC sequence table for the PUSCH; and receiving third information indicating an OCC sequence in the OCC sequence table. A fixed OCC scheme is defined as being associated with the Msg3 PUSCH, wherein the fixed OCC scheme includes one of inter-symbol OCC, inter-symbol group OCC, inter-slot OCC, inter-slot group OCC, inter-redundancy version (RV) OCC, and intra-symbol OCC. The second information is carried in SIB information, which indicates the OCC sequence table. The third information is carried in RA-RNTI scrambled DCI. The TDRA table includes a parameter PUSCH-OCCIndex (or sixth parameter), wherein each row of the parameter PUSCH-OCCIndex indicates any OCC sequence in the OCC sequence table. Here, Table 4 only schematically shows the PUSCH-OCCIndex column, and the specific configuration of PUSCH-OCCIndex can be set according to actual needs, and no specific value is given here.

[0116] The following describes the configuration method of the first to third information in this example. Specifically, define Msg3 PUSCH to associate with a fixed OCC scheme; directly indicate the OCC sequence table in the SIB information to indicate the OCC sequence table corresponding to the index; define the parameter PUSCH-OCCIndex in the TDRA table to indicate 2 N OCC sequences, wherein each row of the parameter PUSCH-OCCIndex indicates any OCC sequence in the OCC sequence table; the UE receives at least SIB information and TDRA table to enable OCC based on Msg3 PUSCH.

[0117] In another example, a communication method includes at least: receiving first information indicating an orthogonal cover code (OCC) scheme for Msg3PUSCH; receiving second information indicating an OCC sequence table for PUSCH; and receiving third information indicating an OCC sequence in the OCC sequence table, directly defining that Msg3PUSCH is associated with a fixed OCC scheme and a fixed OCC sequence table, wherein the third information is carried in RA-RNTI-scrambled DCI and is associated with a TDRA table, wherein the TDRA table includes a sixth parameter, wherein the sixth parameter includes an index of multiple OCC sequences to determine the OCC sequence. The fixed OCC scheme includes one of inter-symbol OCC, inter-symbol group OCC, inter-slot OCC, inter-slot group OCC, inter-redundancy version (RV) OCC, and intra-symbol OCC.

[0118] Table 4 TDRA table after PUSCH enables OCC

[0119] The following describes the configuration method of the first to third information in this example. Specifically, define the Msg3 PUSCH associated with the fixed OCC scheme and the fixed OCC sequence table; define the parameter PUSCH-OCCIndex in the TDRA table to include 2 in the fixed OCC sequence table. N The UE receives the index of the OCC sequence to determine the OCC sequence; the UE receives the TDRA table to enable OCC based on the Msg3 PUSCH.

[0120] In one embodiment, Msg3 is defined to be associated with a fixed OCC scheme, such as one of inter-symbol OCC, inter-symbol group OCC, inter-timeslot OCC, inter-timeslot group OCC, inter-redundancy version RV OCC, and intra-symbol OCC. After the OCC sequence table is determined, the N reserved bits in the RA-RNTI scrambled DCI are redefined to indicate the OCC sequence of the OCC sequence table, including the reserved bits used to indicate 2 N N bits of an OCC sequence.

[0121] In another example, the communication method includes at least: receiving first information, the first information being used to indicate an orthogonal cover code (OCC) scheme for Msg3 PUSCH; receiving second information, the second information being used to indicate an OCC sequence table for Msg3 PUSCH; and receiving third information, the third information being used to indicate an OCC sequence in the OCC sequence table. A fixed OCC scheme is directly defined to be associated with Msg3 PUSCH. The fixed OCC scheme includes one of inter-symbol OCC, inter-symbol group OCC, inter-timeslot OCC, inter-timeslot group OCC, inter-redundancy version RV OCC, and intra-symbol OCC. The second and third information are carried in RA-RNTI-scrambled DCI, the RA-RNTI-scrambled DCI is associated with a TDRA table, and is used to indicate the OCC sequence table. The reserved bits in the RA-RNTI-scrambled DCI are defined to indicate the OCC sequence.

[0122] Specifically, Msg3 is defined to be associated with a preset OCC scheme, such as inter-symbol OCC, inter-symbol group OCC, inter-timeslot OCC, inter-timeslot group OCC, inter-redundancy version RV OCC, and intra-symbol OCC. A new parameter PUSCH-OCCTable (see Table 5) is added to the TDRA table to indicate the OCC sequence table. The reserved bits in the RA-RNTI scrambled DCI are redefined to indicate the OCC sequence of the OCC sequence table. The reserved bits include the OCC sequence used to indicate 2 NN bits of an OCC sequence. For example, if the OCC sequence length is 8, there are 8 types of OCC sequences, and the sequence in the OCC sequence table requires 3 bits. Here, Table 5 only schematically shows the PUSCH-OCCTable column, and the specific configuration of PUSCH-OCCTable can be set according to actual needs. Specific values ​​are not given here.

[0123] Table 5 TDRA table after PUSCH enables OCC

[0124] In one example, a communication method includes: receiving first information, the first information being used to indicate an orthogonal cover code (OCC) scheme for Msg3 PUSCH; receiving second information, the second information being used to indicate an OCC sequence table for PUSCH; and receiving third information, the third information being used to indicate an OCC sequence in the OCC sequence table. A fixed OCC scheme is directly defined to be associated with Msg3 PUSCH. The fixed OCC scheme includes one of inter-symbol OCC, inter-symbol group OCC, inter-timeslot OCC, inter-timeslot group OCC, inter-redundancy version RV OCC, and intra-symbol OCC. The second and third information are carried on RA-RNTI-scrambled DCI, including a first reserved bit for indicating the OCC sequence table and a second reserved bit for indicating an index of the OCC sequence to determine the OCC sequence.

[0125] The configuration method of the first to third information in this example will be described below. Specifically, since Msg3 currently only supports TypeA PUSCH, it is possible to directly define Msg3 to be associated with a preset OCC scheme, such as inter-symbol OCC, inter-symbol group OCC, inter-time slot OCC, inter-time slot group OCC, OCC between redundant versions RV, and intra-symbol OCC. The reserved bits in the RA-RNTI scrambled DCI are redefined to indicate the OCC sequence table and the OCC sequence of the OCC sequence table, respectively. The reserved bits include multiple bits used to indicate the OCC sequence table and the OCC sequence. For example, if the OCC sequence length is 8, there are 8 types of OCC sequences, and the sequence in the OCC sequence table requires 3 bits.

[0126] In one example, a communication method includes: receiving first information indicating an orthogonal cover code (OCC) scheme for a Msg3 PUSCH; receiving second information indicating an OCC sequence table for the PUSCH; and receiving third information indicating an OCC sequence in the OCC sequence table. The first, second, and third information are carried on RA-RNTI-scrambled directive information (DCI), including a first reserved bit for indicating the OCC sequence table, a second reserved bit for indicating an index for indicating the OCC sequence, and a third reserved bit for indicating the OCC scheme. Specifically, the reserved bits in the RA-RNTI-scrambled DCI are redefined to indicate the OCC scheme, multiple OCC sequence tables, and multiple OCC sequences in the OCC sequence table, respectively.

[0127] The following describes the configuration method for the first to third information in this example. Specifically, the reserved bits in the RA-RNTI-scrambled DCI are redefined to indicate the predetermined OCC scheme, OCC sequence table, and OCC sequence, respectively. The base station transmits a PDCCH carrying the RA-RNTI-scrambled DCI to the UE to enable OCC based on the Msg3 PUSCH. For example, if the OCC sequence length is 8, 3 bits are required to indicate the 8-length OCC sequence table. Since the orthogonal sequence length is 8, an additional 3 bits are required to indicate the sequence in the OCC sequence table.

[0128] Furthermore, a new problem is introduced: how to make the existing DCI and the enhanced DCI compatible. The incompatibility between the existing DCI and the enhanced DCI will lead to inconsistent understanding between the base station and the UE.

[0129] To this end, in one example, a reserved bit of 1 bit in the reserved bits in the DCI is defined as an extended field to indicate whether the DCI is an enhanced DCI, thereby unifying the understanding of the UE and the base station.

[0130] In one example, a first RA-RNTI is defined to scramble DCI. The value of the first RA-RNTI is obtained by adding a preset offset value (e.g., an integer with an offset value of 1) to a value calculated based on RO to distinguish between two different DCIs. The first RA-RNTI is a newly added RA-RNTI to avoid conflict with DCI scrambled by an existing RA-RNTI.

[0131] Extend the RAR field to indicate the OCC sequence in the OCC table

[0132] The OCC index field (as shown in Table 6) is directly added to the UL authorization content field to indicate the OCC sequence in the OCC sequence table. For example, when the OCC sequence length is 8, there are 8 OCC sequences, so 3 bits are required to indicate 8 OCC sequences. However, RRC has not yet been fully established, so the OCC type and OCC sequence table cannot be indicated through RRC.

[0133] Table 6 Random Access Response Authorization Content Field

[0134] To this end, some embodiments of the present application provide a communication method, comprising: receiving first information, the first information being used to indicate an orthogonal cover code OCC scheme for Msg3 PUSCH; receiving second information, the second information being used to indicate an OCC sequence table for PUSCH; and receiving third information, the third information being carried in a random access response RAR, the RAR including a third field for indicating an OCC sequence in the OCC sequence table.

[0135] The following describes the configuration method for the first to third information in this embodiment. Specifically, a new field (hereinafter referred to as the third field, used to define the index of the sequence in the OCC sequence table) is proposed in the RAR to include a third field for indicating the OCC sequence. In the above-described embodiment of the present application, the first and second information do not include RRC, but instead use DCI or implicit means to indicate the OCC type and OCC sequence table. A detailed description is provided below.

[0136] In some examples, the communication method includes: receiving first information, the first information is used to indicate that a fixed OCC scheme is supported in initial access; receiving second information, the second information is carried on an RA-RNTI-scrambled DCI, the RA-RNTI-scrambled DCI is associated with a TDRA table, the TDRA table includes a second parameter for indicating an OCC sequence table; receiving third information, the third information is carried in a random access response RAR, the RAR includes a third field for indicating an OCC sequence in the OCC sequence table.

[0137] The configuration method of the first information to the third information in this example will be described below. Specifically, the fixed OCC scheme may include one of inter-symbol OCC, inter-symbol group OCC, inter-time slot OCC, inter-time slot group OCC, OCC between redundant versions RV and intra-symbol OCC. After the OCC scheme is determined, the TDRA is associated with the OCC sequence table, and a new column of parameters (or called the second parameter) is added to the TDRA table through joint coding to indicate the OCC sequence table. Similar steps have been described in detail above and will not be repeated here. Finally, a new field (third field) is established in the RAR to define the index of the sequence in the OCC table. For example, the orthogonal sequence is based on the Walsh code. Assuming that the maximum OCC sequence length is 8, there are 8 mutually orthogonal OCC sequences. At this time, it is necessary to define 3 bits in the third field to indicate the index of the OCC sequence.

[0138] In some examples, the communication method includes: receiving first information, the first information being used to indicate that a fixed OCC scheme is supported in initial access; receiving second information, including a first reserved bit in an RA-RNTI scrambled DCI, the first reserved bit being used to indicate an OCC sequence table; receiving third information, the third information being carried in a random access response RAR, the RAR including a third field for indicating an OCC sequence in the OCC sequence table.

[0139] The following describes the configuration method for the first to third information in this example. Specifically, the fixed OCC scheme can include one of inter-symbol OCC, inter-symbol group OCC, inter-timeslot OCC, inter-timeslot group OCC, inter-redundancy version RV OCC, and intra-symbol OCC. After determining the OCC scheme, different OCC sequence tables are indicated by defining reserved bits in the RA-RNTI scrambled DCI. Finally, a new field (the third field) is established in the RAR to define the sequences in the OCC sequence table. As described above, this will not be described in detail here.

[0140] In some examples, the communication method includes: receiving first information and second information, the first information and the second information are carried on the RA-RNTI encrypted DCI, including a third reserved bit for indicating the OCC scheme, and also including a first reserved bit for indicating the OCC sequence table; sending third information, the third information is carried on the random access response RAR, and the RAR includes a third field for indicating the OCC sequence.

[0141] The configuration method of the first to third information in this example will be described below. Specifically, the reserved bits in the RA-RNTI-scrambled DCI are used to indicate the OCC type and the OCC sequence table, respectively. Since the OCC scheme includes six types of inter-symbol OCC, inter-symbol group OCC, inter-timeslot OCC, inter-timeslot group OCC, inter-redundancy version RV OCC, and intra-symbol OCC as described above, it is necessary to define a third reserved bit of 3 bits in the RA-RNTI-scrambled DCI to indicate these six types. When the value of the first reserved bit used to indicate the OCC sequence table is set to 0, 1, ..., or N, different OCC sequence tables are indicated. Finally, a new field (third field) is established in the RAR to indicate the OCC sequence in the OCC sequence table. The specific operations are the same as the corresponding steps in the above embodiment and will not be described in detail here.

[0142] In some examples, a communication method includes: receiving first information and second information, the first information and the second information being carried on a RA-RNTI-scrambled DCI, including a third reserved bit for indicating an OCC scheme, and including a fourth reserved bit for indicating a sequence type, wherein the sequence type includes a Walsh sequence and a DFT sequence. A PUSCH repetition number is used to indicate the length of the OCC sequence, so that the UE generates an OCC sequence table based on the sequence type and the sequence length; and receiving third information, the third information being carried on a random access response (RAR), wherein the RAR includes a third field for indicating an index of the OCC sequence.

[0143] The configuration method of the first to third information in this example will be described below. Specifically, the reserved bits in the RA-RNTI-scrambled DCI are used to indicate the OCC type and OCC sequence type, respectively. The indication of the OCC type is the same as the indication of the OCC type in the above method, and a detailed description will not be given here. As for the indication of the OCC sequence table, the OCC sequence type and OCC sequence length can be determined separately, and then based on the generation formula of the two sequences, the UE generates an OCC mapping table according to the sequence type and sequence length. Specifically, with respect to the indication of the OCC sequence type, the fourth reserved bit in the RA-RNTI-scrambled DCI is defined to indicate the OCC sequence type, and the fourth reserved bit has 1 bit. For example, the value of the fourth reserved bit is set to 0 to indicate that the OCC sequence type is a Walsh sequence, and the value of the fourth reserved bit is set to 1 to indicate that the OCC sequence type is a DFT sequence. The present application is not limited to this. With respect to the OCC sequence length, the OCC sequence length can be determined by implication. For example, the OCC length is associated with the number of PUSCH repetitions, and the number of repetitions is determined by the number of repetitions numberOfRepetitions in the resource allocation table, or the length of the OCC sequence is determined by the number of RBs. After the OCC sequence table is determined, a new field (third field) is created in the RAR to indicate the OCC sequence in the OCC sequence table. The specific operations are the same as the corresponding steps in the above embodiment and will not be described in detail here.

[0144] The above describes the communication method performed by the UE. Correspondingly, the corresponding communication method can be performed by the base station, and a detailed description will not be given here.

[0145] 5. CG type PUSCH

[0146] For CG type PUSCH, the scheduling method is slightly different from other PUSCHs. CG Type 1 PUSCH can be configured through high-layer parameters, while CG Type 2 PUSCH requires CS-DCI to activate the CG configuration. Therefore, in order to support CG PUSCH to enable OCC, the following method is proposed:

[0147] For CG Type 1 PUSCH:

[0148] In one embodiment, some embodiments of the present application provide a communication method, comprising: receiving first information, second information, and third information, the first information being used to indicate an orthogonal cover code OCC scheme for CG Type1 PUSCH, the second information being used to indicate an OCC sequence table for PUSCH, and the third information being used to indicate an OCC sequence in the OCC sequence table, wherein ConfiguredGrantConfig includes parameters for CG Type1 type PUSCH, parameters for indicating the OCC scheme, and parameters for indicating the OCC sequence table, and rrc-ConfiguredUplinkGrant in ConfiguredGrantConfig includes a parameter to indicate the OCC sequence.

[0149] The following describes the configuration method of the first to third information in this embodiment. Specifically, by configuring the traditional configuration parameters for the CG Type 1 PUSCH, the newly added parameter OCCScheme for indicating the OCC scheme, and the parameter OCCTable for indicating the OCC sequence table in ConfiguredGrantConfig, and adding the parameter OCCIndex for indicating the OCC sequence in rrc-ConfiguredUplinkGrant, the CG Type 1 PUSCH supports the OCC scheme.

[0150] In one embodiment, some embodiments of the present application provide a communication method, the communication method comprising: receiving first information, second information, and third information, the first information being used to indicate an orthogonal cover code (OCC) scheme for a CG Type 1 PUSCH, the second information being used to indicate an OCC sequence table for the PUSCH, and the third information being used to indicate an OCC sequence in the OCC sequence table; wherein ConfiguredGrantConfig includes parameters for a CG Type 1 PUSCH, parameters for indicating OCC schemes for multiple sequence types, and a ninth parameter, wherein the value of the ninth parameter is set to Walsh or DFT to indicate that the sequence type is a Walsh sequence or a DFT sequence, respectively. The length of the OCC sequence is determined by the number of PUSCH repetitions, which is determined by a parameter repk (or a seventh parameter), or the length of the OCC sequence is determined by the number of RBs, so that a UE generates an OCC sequence table based on the sequence type and sequence length; and the eighth parameter in rrc-ConfiguredUplinkGrant is defined as the index of the OCC sequence indicated by the third information; and receiving an index of a sequence in the OCC sequence table activated by MAC-CE or RRC signaling.

[0151] The configuration method of the first to third information in this embodiment will be described below. Specifically, the parameters OCCScheme and OCCSequence are newly added to ConfiguredGrantConfig, and the newly added parameter OCCScheme is defined to indicate the OCC scheme and the parameter OCCSequence is defined to indicate whether the sequence type of the OCC is a Walsh sequence or a DFT sequence. The parameter OCCScheme is defined to have 3 bits, which are used to indicate one of inter-symbol OCC, inter-symbol group OCC, inter-timeslot OCC, inter-timeslot group OCC, inter-redundancy version RV OCC, and intra-symbol OCC. Regarding the indication of the OCC sequence table, the OCC sequence type and OCC sequence length can be determined separately, and then based on the generation formula of the two sequences, the UE generates an OCC mapping table according to the sequence type and sequence length. Specifically, regarding the indication of the OCC sequence type, a ninth parameter is defined to indicate the OCC sequence type, and the ninth parameter has 1 bit. For example, the value of the ninth parameter is set to 0 to indicate that the OCC sequence type is a Walsh sequence, and the value of the fourth reserved bit is set to 1 to indicate that the OCC sequence type is a DFT sequence. The present application is not limited to this. Regarding the OCC sequence length, the OCC sequence length can be determined by an implicit method (for example, the implicit method described above can be used). Finally, a new parameter OCCIndex (or called the eighth parameter) is added to rrc-ConfiguredUplinkGrant to indicate an OCC sequence in the OCC table.

[0152] For CG Type 2 PUSCH:

[0153] For CG Type2 PUSCH, the traditional configuration parameters, the newly added parameter OCCScheme for indicating the OCC scheme, and the parameter OCCTable for indicating the OCC sequence table can be configured in ConfiguredGrantConfig. Unlike CG Type1 PUSCH, the high-level parameters received by CG Type2 PUSCH do not include rrc-ConfiguredUplinkGrant. Considering that the configuration of CG Type2 PUSCH is activated by DCI scrambled by CS-RNTI, in order to indicate the OCC sequence, the following method is proposed:

[0154] In one embodiment, some embodiments of the present application provide a communication method, the communication method comprising: receiving first information, second information, and third information, wherein the first information is used to indicate an orthogonal cover code (OCC) scheme for a CG Type 2 PUSCH, the second information is used to indicate an OCC sequence table for the PUSCH, and the third information is used to indicate an OCC sequence in the OCC sequence table, wherein ConfiguredGrantConfig includes a parameter for indicating the OCC scheme and a parameter for indicating the OCC sequence table. The third information is carried on a DCI scrambled by a CS-RNTI, and a new parameter OCCIndex is added to a TDRA table associated with the CS-RNTI scrambled DCI to indicate the OCC sequence.

[0155] The following describes the configuration method of the first to third information in this embodiment. Specifically, for CG Type 2 PUSCH, traditional configuration parameters, a newly added parameter OCCScheme for indicating the OCC scheme, and a parameter OCCTable for indicating the OCC sequence table can be configured in ConfiguredGrantConfig. When the OCC scheme and OCC sequence table are determined, TDRA is associated with the OCC sequence table, and a new column of parameters is added to the TDRA table through joint coding to indicate the OCC sequence.

[0156] In one embodiment, some embodiments of the present application provide a communication method, the communication method comprising: receiving first information, second information, and third information, wherein the first information is used to indicate an orthogonal cover code (OCC) scheme for a CG Type 2 PUSCH, the second information is used to indicate an OCC sequence table for the PUSCH, and the third information is used to indicate an OCC sequence in the OCC sequence table, wherein ConfiguredGrantConfig includes parameters for indicating the OCC scheme and parameters for indicating the OCC sequence table. The DCI scrambled by the CS-RNTI includes a fourth field, wherein the fourth field is defined with several special states to indicate the OCC sequence.

[0157] The configuration method of the first information to the third information in this embodiment will be described below. Specifically, the activation DCI of CG Type2 is scrambled by CS-RNTI, and special states of some fields are set. Some fields (or called the fourth field) can be reinterpreted to indicate the OCC sequence. For example, the fourth field may include the HARQ field and the RV field. For example, when the length of the OCC sequence is 8, the fourth field needs to occupy 3 bits. The HARQ process number field occupies 4 bits but is all set to zero, so the field can be reinterpreted (or redefined), and the remaining bits are still all set to zero, as shown in Table 7.

[0158] Table 7: Special state configuration of the DCI field for activating CS-RNTI scrambling of CG Type 2 PUSCH with OCC enabled

[0159] Note: A represents the number of bits occupied

[0160] In addition to the HARQ process number field, the Redundacy version field is also set to all zeros. When the OCC sequence length is 8, a 3-bit field is required as the fourth field. In this case, the 2 bits of the Redundacy version field in the HARQ field and the 1 bit of the HARQ process number field in the HARQ field can be directly used as the fourth field. The remaining 3 bits in the HARQ field are still set to all zeros.

[0161] Table 8: Special state configuration of the DCI field for activating CS-RNTI scrambling of CG Type 2 PUSCH with OCC enabled

[0162] The above embodiment reinterprets some fields of the DCI scrambled by the CS-RNTI, which will change the configuration of the DCI. To distinguish it from the traditional PUSCH and ensure consistent understanding between the UE and the gNB, the following improvements are proposed:

[0163] In one example, a new CS-RNTI is configured to distinguish between the traditional CG Type 2 PUSCH and the enhanced CG Type 2 PUSCH (corresponding to the above-mentioned reinterpreted DCI), and the enhanced Type 2 CG PUSCH supports OCC.

[0164] In one example, whether the OCC sequence needs to be indicated through the HARQ domain is indicated in the RRC. Specifically, the parameter HARQIndicateOCC (or called the eighth parameter) is configured in the ConfiguredGrantConfig, and the HARQ domain indication OCC sequence is triggered by enabling, as shown below.

[0165] For CG Type 1 PUSCH and CG Type 2 PUSCH

[0166] For CG Type 1 PUSCH and CG Type 2 PUSCH, some embodiments of the present application provide a communication method, which includes: receiving first information, second information and third information, the first information is used to indicate the orthogonal cover code OCC scheme used for CG PUSCH, the second information is used to indicate the OCC sequence table used for PUSCH, and the third information is used to indicate the OCC sequence in the OCC sequence table, and configuring parameters for indicating the OCC scheme, parameters for indicating the OCC sequence table and parameters for indicating the OCC sequence in ConfiguredGrantConfig.

[0167] The configuration method of the first to third information in this embodiment will be described below. Specifically, the parameter OCCScheme for indicating the OCC scheme, the parameter OCCTable for indicating the OCC sequence table, and the parameter OCCIndex for indicating the index of the OCC sequence are configured in ConfiguredGrantConfig.

[0168] For CG Type 1 PUSCH and CG Type 2 PUSCH, some embodiments of the present application provide a communication method, which includes: receiving first information, second information, and third information, the first information being used to indicate an orthogonal cover code OCC scheme for a physical uplink shared channel PUSCH, the second information being used to indicate an OCC sequence table for CG PUSCH, and the third information being used to indicate an OCC sequence in the OCC sequence table, configuring parameters for CG type PUSCH, parameters for indicating the OCC scheme, a ninth parameter, and parameters for indicating the OCC sequence in ConfiguredGrantConfig, wherein the value of the ninth parameter is set to Wal or DFT to indicate that the sequence type is a Walsh sequence or a DFT sequence, respectively. The PUSCH repetition number is used to indicate the length of the OCC sequence, so that the UE generates an OCC sequence table based on the sequence type and sequence length.

[0169] The following describes the configuration method for the first to third information in this embodiment. Specifically, the parameter OCCScheme, which indicates the OCC scheme, the OCC sequence type OCCSequence (also known as the ninth parameter), and the sequence index OCCIndex are configured in ConfiguredGrantConfig. The number of CG repetitions is determined by the repetition (repK) or the number of RBs, and the associated OCC sequence length. The UE can generate it according to a formula based on the sequence.

[0170] The above describes the communication method performed by the UE. Correspondingly, the corresponding communication method can be performed by the base station, and a detailed description will not be given here.

[0171] 6. Is the granularity of PUSCH repetition Type B multiplexing OCC based on nominal repetition or actual repetition?

[0172] For repetition Type A, the SLIV field is determined by indicating the continuous transmission symbols L and the starting symbol position S, indicating the specific transmission starting position. S must be 0, but the sum of the two cannot be greater than 14. Therefore, each Type A transmission must start at the start symbol of the time slot and cannot exceed one time slot. As shown in Figure 5, for Type B, the restriction of S being 0 is removed, and the sum of the two can be a maximum of 27. Therefore, timeslot crossing may occur. If unavailable symbols are encountered, the nominal PUSCH (Nominal PUSCH) will be split into one or more actual PUSCHs (Actual PUSCH), such as Actual#1 and Actual#2, as shown in Figure 5. Therefore, if OCC is multiplexed, it is necessary to determine whether the OCC granularity is based on the nominal PUSCH or the actual PUSCH.

[0173] To this end, some embodiments of the present application provide an OCC determination method performed by a UE, the OCC determination method including: receiving configuration information, and the UE enabling Type B PUSCH OCC based on the configuration information, as shown in FIG6 .

[0174] The configuration information is conventional configuration information well known to those skilled in the art and will not be described here. The following describes how to determine the OCC granularity.

[0175] OCC granularity is based on Nominal PUSCH

[0176] In some embodiments, when determining that the repetition type is Type B PUSCH (PUSCH repetition Type B), enabling the PUSCH to support the OCC scheme includes: splitting the Nominal PUSCH into multiple actual PUSCHs (e.g., Actual#1 and Actual#2 in FIG. 7 ) by unavailable symbols or time slot boundaries, and performing OCC mapping according to the Nominal PUSCH configuration OCC sequence, as shown in FIG. Although FIG. 7 shows two UEs, the number of UEs is not limited thereto.

[0177] For example, multiple actual PUSCHs split from the Nominal PUSCH are bundled together into the Nominal'PUSCH, and the previous RV is continued to be used, and the OCC is still configured with the OCC sequence of the original Nominal PUSCH.

[0178] For example, unusable symbols can be left unchanged (i.e., the mapped bit stream is discarded / deleted), and the previous RV can be used. The OCC sequence is still configured with the original Nominal PUSCH OCC sequence, as shown in Figure 5. If the Demodulation Reference Signal (DMRS) is discarded due to unusable symbols, a supplementary DMRS is used, or a new DMRS is generated based on the new actual PUSCH symbols.

[0179] Multiple OCC granularity coupling and multiplexing

[0180] If the OCC granularity is configured based on the Nominal PUSCH, the OCC sequence length is equal to the transmission length of the PUSCH. The Nominal PUSCH becomes the actual PUSCH due to the presence of unavailable symbols during transmission. In some embodiments of the present application, the OCC sequence can be truncated multiple times to reuse the OCC in segments. In the example, the length of the OCC sequence is N, and the N nominal PUSCHs are split into M actual PUSCHs by unavailable symbols or time slot boundaries, where N is an integer greater than 1 and M is an integer greater than N. The first N actual PUSCHs of the M actual PUSCHs are demodulated using the OCC sequence; the OCC sequence is truncated into a first OCC sequence of length MN and a second OCC sequence of length 2N-M; the remaining actual PUSCHs are demodulated using the first OCC sequence, where the first OCC sequence has orthogonality.

[0181] For example, as shown in Figure 8, only the overlap of available PUSCH time-frequency resources between UE1 (or the first UE) and UE2 (or the second UE) is considered. Due to the presence of unusable symbols, the four nominal PUSCHs become six PUSCHs (e.g., two nominal PUSCHs, Actual #1, Actual #2, Actual #3, and Actual #4 in Figure 8). OCC sequence truncation can be performed in two steps. The first four PUSCHs (i.e., two nominal PUSCHs and two actual PUSCHs) still use the configured OCC sequence (e.g., +1+1+1+1 for UE1 in Figure 8), with a configured OCC sequence length of 4. For the last two actual PUSCHs (e.g., Actual #3 and Actual #4 for UE1 in Figure 8), the configured OCC sequence length of 4 can be truncated to a sequence length of 2 and assigned to the last two actual PUSCHs. This achieves segmented data demodulation. Although FIG. 8 shows two UEs, the number of UEs is not limited thereto.

[0182] The lengths of the OCC sequences multiplexed between multiple UEs in the overlapping part of the time-frequency domain resources are different

[0183] For various types of PUSCHs, and the lengths of OCC sequences multiplexed between multiple UEs in the overlapping part of time-frequency domain resources are different, the present application provides an OCC determination method performed by the UE, the OCC determination method including: receiving configuration information; and enabling PUSCH OCC based on the configuration information, as shown in Figure 9.

[0184] For various types of PUSCH, when the OCC sequence length is equal to the transmission length of the PUSCH and UE1 and UE2 repeat the transmission for different times in the overlapping part of the time-frequency domain resources, one of UE1 and UE2 is re-divided so that the OCC sequence granularity of UE1 and UE2 is the same; the OCC sequence corresponding to the one of UE1 and UE2 is multiplexed into an OCC sequence with the same length as the OCC sequence granularity through repetition, and configured to the one of UE1 and UE2.

[0185] For example, if two UEs repeat transmission for different times in the overlapping part, OCC sequences of different lengths will be multiplexed. For example, as shown in FIG10 , UE1 repeats transmission 2 times (such as the two repetitions in FIG10 ), and the length of the available OCC sequence is 2 (such as W(1)' and W(2)' in FIG10 ), and UE2 repeats transmission 4 times, and the length of the available OCC sequence is 4. As shown in FIG10 , UE 1 is re-divided into four actual PUSCHs, and the OCC sequence granularity of UE 1 and UE 2 in the overlapping part is the same. The OCC sequence of length 2 originally configured for UE1 (such as W(1)' and W(2)' in FIG10 ) is multiplexed into an OCC sequence of length 4 (such as W(1)', W(2)', W(3)' and W(4)' in FIG10 ) by repetition, and configured for the re-divided UE 1. Although FIG10 shows two UEs, the number of UEs is not limited to this.

[0186] PUSCH length is inconsistent with OCC

[0187] The base station configures an OCC sequence for the UE. However, during scheduling, the UE adjusts the number of repetitions to ensure reliable transmission, resulting in a mismatch between the sequence length and the UE's repetition length. The following describes two possible solutions.

[0188] When the configured OCC sequence length is greater than the PUSCH transmission length, sequence truncation can be used to ensure that the overlapping portion remains OCC-enabled. For example, as shown in Figure 11, the base station configures a Walsh code-based OCC sequence of length 8, but the UE only has 4 available symbols, time slots, or repetitions, resulting in length misalignment. When applying the OCC sequence, the UE can truncate the OCC sequence, retaining only the 4-length sequence of the repetition portion.

[0189] When the configured OCC sequence length is smaller than the PUSCH transmission length, the OCC sequence is expanded by repetition to keep consistent with the number of resources in the overlapping part of the time-frequency domain resources between multiple UEs, wherein the expanded OCC sequence has orthogonality.

[0190] For example, as shown in Figure 11, the base station configures a Walsh code-based OCC sequence of length 4, but the UE actually has eight available symbols, time slots, or repetitions, resulting in length misalignment. To enable OCC, the UE can replicate the OCC sequence, extending the length from 4 to 8, to match the number of resources in the repeated portion between UE1 and UE2. Due to the properties of Walsh codes, higher-order OCC matrices can be generated from lower-order matrices, so the expanded OCC sequences remain orthogonal.

[0191] Unless explicitly stated to the contrary, the above-described embodiments / examples may be combined with any other embodiment(s) / examples.

[0192] An embodiment of the present application further provides a base station, which includes a processor and a memory, wherein the memory is used to store a computer program, and the processor is used to call and run the computer program stored in the memory to execute the method described in the above embodiment.

[0193] An embodiment of the present application further provides a UE, which includes a processor and a memory, wherein the memory is used to store a computer program, and the processor is used to call and run the computer program stored in the memory to execute the method described in the above embodiment.

[0194] An embodiment of the present application also provides a non-transitory computer-readable storage medium, which includes a processor for calling and running a computer program from a memory, so that a device equipped with the chip executes the method described in the above embodiment.

[0195] An embodiment of the present application further provides a computer program product for storing a computer program, wherein the computer program product enables a computer to execute the method described in the above embodiment.

[0196] Figure 12 is a block diagram of an example system 1100 for wireless communication according to an embodiment of the present application. The embodiments of the present application can be implemented in the system using any appropriately configured hardware and / or software. Figure 12 shows system 1100, which includes at least a radio frequency (RF) circuit 1110, a baseband circuit 1120, an application circuit 1130, a memory / storage 1140, a display 1150, a camera 1160, a sensor 1170, and an input / output (I / O) interface 1180 coupled to each other. The application circuit 1130 may include circuits such as, but not limited to, one or more single-core or multi-core processors. The processor may include any combination of general-purpose processors and special-purpose processors, such as a graphics processor or an application processor. The processor may be coupled to the memory / storage and configured to execute instructions stored in the memory / storage device to enable various applications and / or operating systems running on the system. In various embodiments, the above-mentioned communication method for a base station and a UE may be embodied in whole or in part in one or more of the RF circuit, the baseband circuit, and / or the application circuit.

[0197] This document uses specific examples to illustrate the principles and implementation methods of this application. The description of the above embodiments is only used to help understand the method and core ideas of this application. At the same time, for technical personnel in this field, based on the ideas of this application, there will be changes in the specific implementation methods and application scope. In summary, the content of this specification should not be understood as limiting this application.

Claims

1. A communication method, performed by a UE, comprising: Receive at least one of the following information: The first information is used to determine an orthogonal cover code (OCC) scheme for a physical uplink shared channel (PUSCH). Second information, used to determine the OCC sequence table for PUSCH, and The third information is used to determine the OCC sequence in the OCC sequence table; and Send PUSCH.

2. The communication method according to claim 1, wherein: At least one of the first information, the second information and the third information is carried in at least one of RRC signaling, medium access control-control element MAC-CE, downlink control information DCI, system information block SIB and random access response RAR.

3. The communication method according to claim 2, wherein: The first information carried in the RRC signaling includes a first parameter used to indicate one or more types of OCC schemes. The communication method according to claim 3 , wherein: The step of receiving the first information includes: receiving the one or more types of OCC schemes activated by DCI, MAC-CE or the RRC signaling. The communication method according to claim 2 , wherein: The step of receiving the first information includes: indicating one or more OCC schemes by a first field of DCI, wherein the field includes one of a modulation and coding scheme MCS field, a hybrid automatic repeat request HARQ field, and a time domain resource allocation TDRA field. The communication method according to claim 2 , wherein: The step of receiving the first information includes: determining a PUSCH transmission type according to configuration information; and determining the OCC scheme according to the PUSCH transmission type.

7. The communication method according to claim 6, wherein: Determining the OCC scheme according to the transmission type of the PUSCH includes at least one of the following: When the transmission type of the PUSCH is non-repeated PUSCH, the OCC scheme is inter-symbol OCC or intra-symbol OCC; When the transmission type of the PUSCH is PUSCH with mapping type B repetition, the OCC scheme is inter-repetition OCC or inter-symbol group OCC; When the transmission type of the PUSCH is PUSCH with mapping type A repetition, the OCC scheme is inter-slot OCC or inter-slot group OCC.

8. The communication method according to claim 2, wherein: The second information carried in the RRC signaling includes a second parameter used to indicate different OCC sequence tables, The step of receiving the second information includes: receiving one or more of the different OCC sequence tables activated by MAC-CE signaling or the RRC signaling.

9. The communication method according to claim 2, wherein: The second information includes the OCC table of PUCCH, the OCC table of PUSCH multiplexed with PUCCH, The communication method includes: a UE determines an OCC sequence table of a multiplexed PUCCH based on a symbol length of a PUSCH or a repetition number of the PUSCH.

10. The communication method according to claim 2, wherein: The RRC signaling includes a third parameter for indicating the OCC sequence type, The step of receiving the second information includes receiving at least one of the sequence types activated by MAC-CE. The communication method according to claim 10 , wherein: The RRC signaling includes a fourth parameter for indicating the sequence length of the OCC sequence. Receiving at least one of the sequence types activated by the MAC-CE includes receiving at least one of the sequence types activated by the MAC-CE and at least one of the sequence lengths to generate an OCC sequence table based on the activated sequence type and the activated sequence length.

12. The communication method according to claim 10, wherein: The sequence length of the OCC sequence is determined based on the number of repetitions of PUSCH-TimeDomainResourceAllocation in PUSCH-Config or the number of PUSCH repetitions or the number of symbols or resource blocks (RBs) for non-repeated transmission. The step of receiving the second information further includes: receiving the activated sequence type and the activated sequence length to generate an OCC sequence table based on the activated sequence type and the activated sequence length.

13. The communication method according to claim 2, wherein: The third information carried in the RRC signaling or the MAC-CE includes a fifth parameter, where the fifth parameter is used to indicate an OCC sequence. The communication method further includes: receiving one or more OCC sequences activated by MAC-CE signaling or the RRC signaling.

14. The communication method according to claim 2, in, The third information carried in the DCI includes a second field for indicating an OCC sequence.

15. The communication method according to claim 14, wherein: The communication method also includes: determining whether the size of the uplink scheduled DCI is greater than the size of the downlink scheduled DCI; when it is determined that the size of the uplink scheduled DCI is greater than the size of the downlink scheduled DCI, generating N bits of zero padding in the downlink scheduled DCI until the size of the uplink scheduled DCI is equal to the size of the downlink scheduled DCI.

16. The communication method according to claim 14, wherein: The hybrid automatic repeat request HARQ process number field or the MCS field in the DCI is used to indicate the OCC sequence in the OCC sequence table.

17. The communication method according to claim 2, wherein: The DCI is associated with a TDRA table carrying parameters related to the OCC sequence, The TDRA table includes a sixth parameter including an OCC sequence indicating an OCC sequence table.

18. The communication method according to claim 2, wherein: The DCI is a random access radio network temporary identifier RA-RNTI scrambled DCI, and is used to determine at least one of the following: a third message Msg 3 PUSCH OCC scheme, an Msg 3 PUSCH OCC sequence table, an Msg 3 PUSCH OCC sequence type, and an Msg 3 PUSCH OCC sequence.

19. The communication method according to claim 18, wherein: The RA-RNTI scrambled DCI is associated with a TDRA table, where the TDRA table includes a parameter or a group of parameters, and the parameter or the group of parameters is used to determine at least one of an OCC scheme, an OCC sequence table, an OCC sequence type, and an OCC sequence.

20. The communication method according to claim 18, wherein: In the DCI, the RA-RNTI is used to scramble bits in the DCI to indicate at least one of an OCC scheme, an OCC sequence table, an OCC sequence type, and an OCC sequence.

21. The communication method according to claim 20, wherein: A first RA-RNTI is defined to scramble the DCI, where a value of the first RA-RNTI is determined based on a random access occasion (RO) and a predefined offset value.

22. The communication method according to claim 2, further comprising using a third field in the RAR to indicate an OCC sequence in an OCC sequence table.

23. The communication method according to claim 22, further comprising: The length of the OCC sequence is associated with the number of PUSCH repetitions or is determined by the number of RBs, wherein the number of repetitions is determined by the number of repetitions numberOfRepetitions in the resource allocation table.

24. The communication method according to claim 2, wherein: The RRC signaling includes ConfiguredGrantConfig, and the ConfiguredGrantConfig includes a parameter for determining at least one of an OCC scheme, an OCC sequence table, an OCC sequence type, and an OCC sequence.

25. The communication method according to claim 24, wherein: The OCC sequence of the PUSCH OCC sequence table configured with grant type 1CG is indicated by rrc-ConfiguredUplinkGrant.

26. The communication method according to claim 24, wherein: The length of the OCC sequence is determined by the number of repetitions of the PUSCH or the length of the OCC sequence is determined by the number of RBs, wherein the number of repetitions is determined by the seventh parameter.

27. The communication method according to claim 24, further comprising: The CS-RNTI scrambled DCI is associated with a TDRA table carrying the OCC sequence related parameters, The TDRA table includes a sixth parameter, which is used to indicate the OCC sequence in the OCC sequence table.

28. The communication method according to claim 24, further comprising: Several special states are defined in the fourth field of the CS-RNTI scrambled DCI to determine the OCC sequence.

29. The communication method according to claim 28, wherein: The fourth field includes a HARQ process number field and a redundancy version RV field.

30. The communication method according to claim 28 or 29, wherein: The CS-RNTI corresponds to the OCC scheme and is different from the CS-RNTI corresponding to the non-OCC scheme.

31. The communication method according to claim 28 or 29, wherein the signaling ConfiguredGrantConfig includes an eighth parameter, which triggers the HARQ domain in an enabling manner to indicate the OCC sequence.

32. A method for determining an OCC, performed by a UE, the method comprising: Receive configuration information; as well as Enable Type B PUSCH OCC based on configuration information.

33. The OCC determination method according to claim 32, wherein: When a nominal PUSCH is split into multiple actual PUSCHs by unavailable symbols or time slot boundaries, OCC mapping is performed according to the nominal PUSCH.

34. The OCC determination method according to claim 33, wherein: The multiple actual PUSCHs are bundled, and the bundled PUSCHs are used as a nominal PUSCH for OCC mapping.

35. The OCC determination method according to claim 32, comprising: When the nominal PUSCH is split into multiple actual PUSCHs by unavailable symbols or time slot boundaries, the OCC sequence length does not match the PUSCH length. The OCC sequence is truncated once or multiple times, and the OCC sequence is configured in part of the PUSCH, and the remaining part of the PUSCH is configured with the truncated OCC sequence.

36. A method for determining an OCC, performed by a UE, the method comprising: Receive configuration information; as well as Enable PUSCH OCC based on the configuration information.

37. The OCC determination method according to claim 36, wherein: The OCC sequence length is equal to the PUSCH transmission length, wherein the OCC determination method includes: when the UE has different repeated transmission times, re-dividing at least one UE; and multiplexing the OCC sequence corresponding to the at least one UE in a repeated manner.

38. The OCC determination method according to claim 36, comprising: When the OCC sequence length is not equal to the PUSCH transmission length, the OCC sequence is truncated or repeatedly extended to make the OCC sequence length equal to the PUSCH transmission length.

39. A communication method, performed by a base station, the communication method comprising: Send at least one of the following information: The first information is used to determine an orthogonal cover code (OCC) scheme for a physical uplink shared channel (PUSCH). Second information, used to determine the OCC sequence table for PUSCH, and The third information is used to determine the OCC sequence in the OCC sequence table, and Receive PUSCH.

40. The communication method according to claim 39, wherein: At least one of the first information, the second information and the third information is carried in at least one of RRC signaling, medium access control-control element MAC-CE, downlink control information DCI, system information block SIB and random access response RAR.

41. The communication method according to claim 40, wherein: The first information carried in the RRC signaling includes a first parameter used to indicate one or more types of OCC schemes.

42. The communication method according to claim 41, wherein: The step of sending the first information includes: activating the one or more types of OCC schemes by DCI, MAC-CE or the RRC signaling.

43. The communication method according to claim 40, wherein: The step of sending the first information includes: indicating one or more OCC schemes by a first field of DCI, wherein the field includes one of a coding modulation scheme MCS field, a hybrid automatic repeat request HARQ field and a time domain resource allocation TDRA field.

44. The communication method according to claim 40, wherein: The step of sending the first information includes: determining a PUSCH transmission type according to configuration information; and determining the OCC scheme according to the PUSCH transmission type.

45. The communication method according to claim 44, wherein: Determining the OCC scheme according to the transmission type of the PUSCH includes at least one of the following: When the transmission type of the PUSCH is non-repeated PUSCH, the OCC scheme is inter-symbol OCC or intra-symbol OCC; When the transmission type of the PUSCH is PUSCH with mapping type B repetition, the OCC scheme is inter-repetition OCC or inter-symbol group OCC; When the transmission type of the PUSCH is PUSCH with mapping type A repetition, the OCC scheme is inter-slot OCC or inter-slot group OCC.

46. ​​The communication method according to claim 40, wherein: The second information carried in the RRC signaling includes a second parameter used to indicate different OCC sequence tables, The step of sending the second information includes: activating one or more of the different OCC sequence tables by MAC-CE signaling or the RRC signaling.

47. The communication method according to claim 40, wherein: The second information includes the OCC table of PUCCH, the OCC table of PUSCH multiplexed with PUCCH, The second information is sent to enable the UE to determine the OCC sequence table of the multiplexed PUCCH based on the symbol length of the PUSCH or the number of repetitions of the PUSCH.

48. The communication method according to claim 40, wherein: The RRC signaling includes a third parameter for indicating the OCC sequence type, The step of sending the second information includes: activating at least one of the sequence types through MAC-CE.

49. The communication method according to claim 48, wherein: The RRC signaling includes a fourth parameter for indicating the sequence length of the OCC sequence. Activating at least one of the sequence types through MAC-CE includes: activating at least one of the sequence types and at least one of the sequence lengths through MAC-CE so that the UE generates an OCC sequence table based on the activated sequence type and the activated sequence length.

50. The communication method according to claim 48, wherein: The sequence length of the OCC sequence is determined based on the number of repetitions of PUSCH-TimeDomainResourceAllocation in PUSCH-Config, the number of PUSCH repetitions or the number of symbols or resource blocks (RBs) that are not repeated. The step of sending the second information further includes: sending the activated sequence type and the activated sequence length so that the UE generates an OCC sequence table based on the activated sequence type and the activated sequence length.

51. The communication method according to claim 40, wherein: The third information carried in the RRC signaling includes a fifth parameter, where the fifth parameter is used to indicate an OCC sequence. The communication method further includes: activating one or more OCC sequences by MAC-CE signaling or the RRC signaling.

52. The communication method according to claim 40, in, The third information carried in the DCI includes a second field for indicating an OCC sequence.

53. The communication method according to claim 52, wherein: The communication method also includes: determining whether the size of the uplink scheduled DCI is greater than the size of the downlink scheduled DCI; when it is determined that the size of the uplink scheduled DCI is greater than the size of the downlink scheduled DCI, generating N bits of zero padding in the downlink scheduled DCI until the size of the uplink scheduled DCI is equal to the size of the downlink scheduled DCI.

54. The communication method according to claim 52, wherein: The hybrid automatic repeat request HARQ process number field or the MCS field in the DCI is used to indicate the OCC sequence in the OCC sequence table.

55. The communication method according to claim 40, wherein: The DCI is associated with a TDRA table carrying parameters related to the OCC sequence, The TDRA table includes a sixth parameter including an OCC sequence indicating an OCC sequence table.

56. The communication method according to claim 40, wherein: The DCI is a random access radio network temporary identifier RA-RNTI scrambled DCI, and is used to determine at least one of the following: a third message Msg 3 PUSCH OCC scheme, an Msg 3 PUSCH OCC sequence table, an Msg 3 PUSCH OCC sequence type, and an Msg 3 PUSCH OCC sequence.

57. The communication method according to claim 56, wherein: The RA-RNTI scrambled DCI is associated with a TDRA table, where the TDRA table includes a parameter or a group of parameters, and the parameter or the group of parameters is used to determine at least one of an OCC scheme, an OCC sequence table, an OCC sequence type, and an OCC sequence.

58. The communication method according to claim 56, wherein: In the DCI, the RA-RNTI is used to scramble bits in the DCI to indicate at least one of an OCC scheme, an OCC sequence table, an OCC sequence type, and an OCC sequence.

59. The communication method according to claim 58, wherein: A first RA-RNTI is defined to scramble the DCI, where a value of the first RA-RNTI is determined based on a random access occasion (RO) and a predefined offset value.

60. The communication method according to claim 40, further comprising using a third field in the RAR to indicate an OCC sequence in an OCC sequence table.

61. The communication method according to claim 60, further comprising: The length of the OCC sequence is associated with the number of PUSCH repetitions or is determined by the number of RBs, wherein the number of repetitions is determined by the number of repetitions numberOfRepetitions in the resource allocation table.

62. The communication method according to claim 40, wherein: The RRC signaling includes ConfiguredGrantConfig, and the ConfiguredGrantConfig includes a parameter for determining at least one of an OCC scheme, an OCC sequence table, an OCC sequence type, and an OCC sequence.

63. The communication method according to claim 62, wherein: The OCC sequence of the PUSCH OCC sequence table of configuration grant type 1 CG Type 1 is indicated by rrc-ConfiguredUplinkGrant.

64. The communication method according to claim 62, wherein: The length of the OCC sequence is determined by the number of repetitions of the PUSCH or the length of the OCC sequence is determined by the number of RBs, wherein the number of repetitions is determined by the seventh parameter.

65. The communication method according to claim 64, further comprising: The CS-RNTI scrambled DCI is associated with a TDRA table carrying the OCC sequence related parameters, The TDRA table includes a fifth parameter, and the sixth parameter is used to indicate the OCC sequence of the OCC sequence table.

66. The communication method according to claim 64, further comprising: Several special states are defined in the fourth field of the CS-RNTI scrambled DCI to determine the OCC sequence.

67. The communication method according to claim 66, wherein: The fourth field includes a HARQ process number field and a redundancy version RV field.

68. The communication method according to claim 66 or 67, wherein: The CS-RNTI corresponds to the OCC scheme and is different from the CS-RNTI corresponding to the non-OCC scheme.

69. The communication method according to claim 66 or 67, wherein: The signaling ConfiguredGrantConfig includes an eighth parameter, which triggers the HARQ domain in an enabling manner to indicate the OCC sequence.

70. A user equipment comprising: A processor and a memory, the memory being used to store a computer program, the processor being used to call and run the computer program stored in the memory, and execute the communication method according to any one of claims 1 to 31.

71. A user equipment comprising: A processor and a memory, the memory being used to store a computer program, the processor being used to call and run the computer program stored in the memory to perform the OCC determination method according to any one of claims 32 to 35 and claims 36 to 38.

72. A base station, comprising: A processor and a memory, the memory being used to store a computer program, the processor being used to call and run the computer program stored in the memory, and execute the communication method according to any one of claims 39 to 69.

73. A non-transitory computer-readable storage medium, wherein: Used to store a computer program, the computer program causing a computer to execute the communication method according to any one of claims 1 to 31.

74. A non-transitory computer-readable storage medium, wherein: Used to store a computer program, the computer program causing a computer to execute the OCC determination method according to any one of claims 32 to 35 and claims 36 to 38.

75. A non-transitory computer-readable storage medium, wherein: Used to store a computer program, the computer program causing a computer to execute the communication method according to any one of claims 39 to 69.

Images