Information sending method, information receiving method, uplink transmission method, communication node and medium

Abstract

The invention discloses an information sending method, an information receiving method, an uplink transmission method, a communication node and a medium. The method comprises the following steps: receiving OCC configuration information sent by a second communication node; determining information after OCC expansion according to the OCC configuration information; and sending the information after the OCC extension to the second communication node.

Description

Technical Field

[0001] This application relates to the field of communication technologies, and for example, relates to a method for information sending and receiving, a method for uplink transmission, a communication node, and a medium. Background Art

[0002] With the continuous progress of radio technologies, a large number of various radio services have emerged. In addition to cellular services, the Long Term Evolution (LTE) system and the New Radio (NR) system also include Internet of Things (IoT) services.

[0003] In the related art, before Release 19 (Rel-19), the Terrestrial network (TN) and the Non-terrestrial network (NTN) support using the repetition technology to enhance the uplink coverage. At the same time, for the IoT scenario, there are usually a large number of IoT terminals, and the allocated resources are limited. Repetitive transmission will further limit the resources, so how to improve the system capacity has become an urgent problem to be solved. Summary of the Invention

[0004] An embodiment of this application provides a method for information sending, which is applied to a first communication node. The method includes:

[0005] Receiving Orthogonal Cover Code (OCC) configuration information sent by a second communication node;

[0006] Determining the OCC-expanded information according to the OCC configuration information;

[0007] Sending the OCC-expanded information to the second communication node.

[0008] An embodiment of this application provides a method for information receiving, which is applied to a second communication node. The method includes:

[0009] Sending Orthogonal Cover Code (OCC) configuration information to a first communication node;

[0010] Receiving the OCC-expanded information sent by the first communication node, where the OCC-expanded information is the information determined by the first communication node according to the OCC configuration information.

[0011] An embodiment of this application provides a method for uplink transmission. The method includes:

[0012] A first communication node determines an uplink channel configuration for carrying out uplink transmission;

[0013] The first communication node transmits an uplink channel carrying the uplink transmission.

[0014] An embodiment of the present application provides a communication node, including: a processor; the processor is configured to implement the method of any of the above embodiments when executing a computer program.

[0015] An embodiment of the present application further provides a computer-readable storage medium storing a computer program, and the computer program implements the method of any of the above embodiments when executed by a processor.

[0016] More descriptions about the above embodiments and other aspects of the present application and their implementation manners are provided in the accompanying drawings, the specific implementation manners, and the claims. Description of the Drawings

[0017] Figure 1 It is a schematic diagram of the networking of an NTN system provided by an embodiment;

[0018] Figure 2 It is a schematic diagram of the physical resource mapping of PUSCH codewords in multi-tone transmission provided by an embodiment;

[0019] Figure 3 It is a schematic diagram of the physical resource mapping of PUSCH codewords in single-tone transmission provided by an embodiment;

[0020] Figure 4 It is a schematic flowchart of a method for information transmission provided by an embodiment;

[0021] Figure 5 It is a schematic flowchart of another method for information transmission provided by an embodiment;

[0022] Figure 6 It is a schematic diagram of obtaining a signal in code division multiplexing provided by an embodiment;

[0023] Figure 7 It is a schematic diagram of the transmission / mapping / multiplexing of a DMRS sequence provided by an embodiment;

[0024] Figure 8 It is a schematic diagram after time slot expansion of the transmission / mapping / multiplexing of a DMRS sequence provided by an embodiment;

[0025] Figure 9 It is a schematic diagram of the information occurrence delay after OCC expansion provided by an embodiment;

[0026] Figure 10 It is a schematic diagram of another information occurrence delay after OCC expansion provided by an embodiment;

[0027] Figure 11 It is a schematic flowchart of a method for information reception provided by an embodiment;

[0028] Figure 12 It is a schematic flow chart of a method for uplink transmission provided by an embodiment;

[0029] Figure 13 It is a schematic diagram of signaling interaction in the method for uplink transmission provided by an embodiment;

[0030] Figure 14 It is a schematic diagram of transmission resources corresponding to two copies of a transmission provided by an embodiment;

[0031] Figure 15 It is a schematic diagram of a transmission corresponding to two copies of a transmission provided by an embodiment;

[0032] Figure 16 It is a schematic diagram of performing a second type of uplink transmission when the first type of uplink transmission reaches the maximum number of retransmissions and the transmission fails, provided by an embodiment;

[0033] Figure 17 It is a schematic diagram of the application of OCC based on time slots provided by an embodiment;

[0034] Figure 18 It is a schematic diagram of the structure of a terminal provided by an embodiment;

[0035] Figure 19 It is a schematic diagram of the structure of a base station provided by an embodiment. Detailed implementation manners

[0036] It should be understood that the specific embodiments described herein are only used to explain the present application and are not used to limit the present application. The embodiments of the present application will be described in detail below with reference to the accompanying drawings.

[0037] In the Rel-19 IoT-NTN uplink capacity enhancement issue, orthogonal cover code (OCC) is used for uplink capacity enhancement and the configurations related to OCC are discussed, such as OCC enabling, OCC activation / deactivation, OCC index / codeword. At the same time, the capacity of the demodulation reference signal (DMRS) is enhanced, such as supporting time-division multiplexed DMRS. For the 3.75 kilohertz (kHz) subcarrier spacing (SCS) OCC of narrowband physical uplink shared channel (NPUSCH) format 1, time-division multiplexing (TDM) DMRS on 4 time slots is supported, where DMRS is transmitted in the first 2 time slots and omitted in the next 2 time slots, and vice versa. When multi-user multiplexing is used, each terminal needs to clearly know the time-domain symbol position of its own DMRS and reserve DMRS symbols for the DMRS of other multiplexed terminals. Therefore, a method for the terminal to determine the DMRS mapping needs to be defined.

[0038] At the same time, in data transmission, there are various types of gaps (such as uplink transmission gaps, gaps caused by narrowband physical random access channel (NPRACH) transmission, uplink timing adjustment gaps, pre-compensation segment gaps). These gaps may cause OCC to transmit across gaps or the orthogonality of OCC to be destroyed due to the discarding of some time slots / symbols. Therefore, a method to ensure the orthogonality of OCC needs to be studied.

[0039] The current protocol already supports enabling the OCC function through user equipment (UE)-specific radio resource control (RRC) signaling. The configuration scheme of the signaling, the method for the terminal to determine the DMRS mapping, the OCC application / expansion method, and the problem of OCC orthogonality destruction caused by transmission gaps are under discussion. Therefore, the information sending method and information receiving method provided in this application enhance the above content.

[0040] The information sending method and information receiving method provided in this application can be applied to both TN and NTN.

[0041] TN in this embodiment refers to various wireless communication systems, such as Long Term Evolution (LTE) systems, 4th-generation (4G) systems, 5th-generation (5G) systems, LTE and 5G hybrid architecture systems, 5G New Radio (NR) systems, and new communication systems emerging in future communication development, such as 6th-generation (6G) systems, etc. The wireless communication system includes terminal devices, access network devices, and core network devices. The PUSCH in this embodiment may also be an NPUSCH, or other types of physical uplink data channels with similar functions.

[0042] Figure 1 is a network architecture diagram of an NTN system provided by an embodiment. As Figure 1 shown, in the NTN communication system, the link between the terminal device and the satellite is the serving link. The link between the access network device (such as a base station, a gateway station) and the satellite is the feeder link, and it is common for all terminal devices (such as Figure 1 the terminal device 1 and the terminal device x shown) within the same cell.

[0043] The terminal device can be a device with wireless transceiver functions, which can be deployed on land (such as indoors or outdoors, handheld, wearable or vehicle-mounted, etc.); it can also be deployed on the water surface (such as a ship, etc.); it can also be deployed in the air (such as an airplane, a balloon, a satellite, etc.). Some examples of terminal devices are: wireless terminals, user equipment (UE), mobile phones, mobile stations, tablet computers, laptop computers, ultra-mobile personal computers (UMPCs), handheld computers, netbooks, personal digital assistants (PDAs) and other connectable user devices, or virtual reality (VR) terminals, augmented reality (AR) terminals, wireless terminals in industrial control, wireless terminals in self-driving, wireless terminals in remote medical, wireless terminals in smart grid, wireless terminals in transportation safety, wireless terminals in smart city, wireless terminals in smart home, etc., or Internet of Things nodes in the Internet of Things, or vehicle-mounted communication devices in vehicle-to-everything, or entertainment, game devices or systems, or global positioning system devices, etc. The embodiments of the present application do not limit the specific technologies and specific device forms adopted by the terminal device. In addition, the terminal device can be abbreviated as the terminal.

[0044] An access network device is an access device through which a terminal device accesses the wireless communication system in a wireless manner. It can be a reader, a base station, an evolved NodeB (eNB or eNodeB) in Long Term Evolution Advanced (LTEA), a transmission reception point (TRP), a base station in a 5G mobile communication system or a next generation NodeB (gNB), a base station in a future mobile communication system, or an access node in a Wireless Fidelity (WiFi) system, etc. The base station can include various macro base stations, micro base stations, home base stations, remote radio heads, routers, WIFI devices, or various network-side devices such as a primary cell and a secondary cell, and a location management function (LMF) device. It can also be a module or unit that completes some functions of the base station. For example, it can be a central unit (CU) or a distributed unit (DU). The embodiments of the present application do not limit the specific technologies and specific device forms adopted by the access network device. In addition, the access network device can be abbreviated as a base station.

[0045] The core network device can include an access and mobility management network element and a session management network element. Exemplarily, the terminal device can access the core network through the access network device to achieve data transmission.

[0046] For the convenience of subsequent understanding, the concepts involved in the present application are introduced below.

[0047] Resource unit:

[0048] In the current specification, the resource unit is used to describe the mapping from the Physical Uplink Shared Channel (PUSCH) to resource elements. The resource unit is defined as an Orthogonal Frequency Division Multiplexing (OFDM) symbol in the time domain and continuous subcarriers in the frequency domain, where and are given by Table 1 Frame Structure Type 1 respectively. Among them, represents the number of symbols included in a time slot, represents the number of time slots included in the resource unit, and represents the number of consecutive subcarriers, and △f represents the subcarrier spacing.

[0049] Table 1 Frame Structure Type 1

[0050]

[0051] Physical resource mapping:

[0052] After binary bits are added with cyclic redundancy check (CRC), channel-coded, rate-matched, interleaved, they are then scrambled. For repeated transmission, the scrambling sequence is re-initialized after each repeated transmission, where is defined as shown by the following formula.

[0053] Each PUSCH codeword (which will be referred to as the first PUSCH codeword in subsequent embodiments) can be mapped to one or more resource units n RU , and every N RU resource units should be transmitted times. That is, represents the repetition times of the n RU resource units to which the PUSCH codeword is mapped. The complex modulation symbols should be multiplied by the amplitude scaling factor β PUsCH , and starting from the subcarrier z(0) assigned for PUSCH transmission, they are mapped in sequence to the resource elements (k, l) corresponding to the subcarriers assigned for data transmission. Starting from the first time slot in the allocated resource units, it is in the increasing order of index k first and then index l. Among them, k represents the index of the subcarrier, and l represents the index of the symbol in the first time slot. After being mapped to N slots time slots, before continuing to map z(·) to the next time slot, N slots time slots should be repeated slots times. N

[0054] Where:

[0055]

[0056] Redundancy Version (RV) determination method:

[0057] For PUSCH transmission, the determination of PUSCH transmission and RV associated with a transport block (TB) is as follows: The transmission is carried out in N time slots in the NB-IoT uplink. These time slots (Slots) are denoted by ni, where i = 0, 1,..., N - 1. For the PUSCH transmission corresponding to the jth TB, it is transmitted in B consecutive NB-IoT uplink time slots ni, where i = jB + b, b = 0, 1,..., B - 1. where the redundancy version rv idx (j) associated with this TB is determined as follows: rv idx (j) = 2·mod(rv DCI + j, 2), where if then L = 1, otherwise rv DCI represents the indicated redundancy version. The part of the PUSCH codeword associated with rv idx (j) (defined in Specification 6.3.2) will be mapped to the RU th slot among the allocated N resource units (RUs) for transmission. When the subcarrier spacing is Δf = 3.75 kHz, in the NB-IoT uplink (UL) slots associated with the TB, the mapping of slot ni is When the subcarrier spacing is Δf = 15 kHz, in the NB-IoT UL slots associated with the TB, the mapping of slot ni is

[0058] From the above physical resource mapping and RV determination process, it can be seen that for the repeated transmission of the PUSCH codeword, the RV will cycle between every L repetitions, where L = 1 when the number of consecutive subcarriers is 1, and when the number of consecutive subcarriers is multiple,

[0059]

[0060] The following uses two examples to illustrate the above physical resource mapping and RV determination process.

[0061] Figure 2 is a schematic diagram of the physical resource mapping of the PUSCH codeword in the multi-tone transmission provided by an embodiment. Figure 2 Corresponding to the subcarrier spacing of 15 kHz, being 12, being 2, being 8, n RU being 2, and N s'(ts being 2.Figure 2 In this case, one PUSCH occupies 2 RUs, and 1 RU includes 2 time slots, that is, one PUSCH occupies 4 time slots, and the number N of consecutive time slots s'(ts is 2. The repetition times of consecutive time slots 1 and 2 Therefore, in Figure 2 , before being mapped to consecutive time slots 3 and 4, consecutive time slots 1 and are repeated 3 times, that is, repeated 3 times. The repetition times of consecutive time slots 3 and 4 are also 4 times. Based on the above RV determination method, the RV number and the physical resource mapping process of subsequent repetitions 5 to 8 can be determined.

[0062] Figure 3 is a schematic diagram of the physical resource mapping of the PUSCH codeword in single-tone transmission provided by an embodiment. Figure 3 corresponding to a subcarrier spacing of 3.75 kHz, being 16, being 2, N RU being 1 and N s'(ts being 1. Based on the above physical resource mapping process and RV determination method, the physical resource mapping process as Figure 3 shown can be determined.

[0063] Downlink Control Information (DCI) (such as DCI format N0):

[0064] The DCI that schedules the PUSCH, and its fields include: modulation and coding scheme field, repetition number field, redundancy version field, unicast-scheduled TB number field, subcarrier indication field, resource reservation field, resource allocation field, scheduling delay field, new data indicator field, DCI subframe repetition number field, Hybrid Automatic Repeat Request (HARQ) process number field. Each field is introduced in detail below:

[0065] The modulation and coding scheme field occupies 4 bits and indicates the modulation and coding index. Different indexes correspond to a certain modulation and transport block size (TBS) index. When the CRC of DCI format N0 is scrambled by a preconfigured uplink resource radio network temporary identifier (PUR-RNTI), this field does not exist; when npusch-16QAM-Config is configured and this field indicates "1111", it represents a 16 Quadrature Amplitude Modulation (QAM) modulation indicator;

[0066] The repetition number field occupies 3 bits and indicates the repetition number index. Different indexes correspond to different repetition numbers. If 16QAM is indicated, this field serves as the modulation and coding scheme field;

[0067] The redundancy version field occupies 1 bit and indicates the index related to the redundancy version;

[0068] The unicast scheduled TB number field occupies 1 bit. This field exists only when the higher layer parameter npusch-MultiTB-Config is configured to be enabled and the corresponding DCI (DCI CRC is scrambled by a cell radio network temporary identifier (C-RNTI)) is mapped to the UE-specific search space, where 0 indicates a single TB and 1 indicates multiple TBs; if the DCI CRC is scrambled by an SPS C-RNTI, this field is set to 0;

[0069] The subcarrier indication field occupies 6 bits. This field corresponds to the subcarrier configuration and indicates the number of consecutive subcarriers allocated. For 3.75 kHz, the valid values are 0 to 47, and 48 to 63 are reserved settings; for 15 kHz, the valid values are 0 to 18, and 19 to 63 are reserved settings. The relationship between the subcarrier indication field and the allocated subcarrier set is shown in Table 2. 0 to 11 indicate that the number of consecutive subcarriers is 1, 12 to 15 indicate that the number of consecutive subcarriers is 3, 16 to 17 indicate that the number of consecutive subcarriers is 6, and 18 indicates that the number of consecutive subcarriers is 12:

[0070] Table 2 Relationship between the subcarrier indication field and the allocated subcarrier set

[0071] <![CDATA[Subcarrier indication field (I sc )]]> <![CDATA[Set of allocated subcarriers (n sc )]]> 0-11 <![CDATA[I sc > 12-15 <![CDATA[3(I sc -12)+{0,1,2}]]> 16-17 <![CDATA[6(I sc -16)+{0,1,2,3,4,5}]]> 18 {0,1,2,3,4,5,6,7,8,9,10,11} 19-63 Reserved

[0072] The resource reservation field occupies 1 bit and indicates whether a certain subframe is an uplink subframe. This field exists only when the higher-layer parameter resourceReservationConfigUL is configured and this DCI (DCI CRC is scrambled by C-RNTI) is mapped to the UE-specific search space;

[0073] The resource allocation field occupies 3 bits and indicates the resource element number index from 0 to 7. Different indexes correspond to different numbers of resource elements;

[0074] The scheduling delay field occupies 2 bits and indicates the index corresponding to the scheduling delay. Different indexes correspond to different scheduling delays;

[0075] The new data indicator field occupies 1 bit and indicates whether the data is newly transmitted. When multiple TBs are scheduled, it serves only as the new data indicator for the first TB;

[0076] The DCI subframe repetition number field occupies 2 bits and indicates the DCI repetition number;

[0077] The HARQ process number field occupies 1 bit. This field exists only when 2 HARQ processes are configured and the corresponding DCI (DCI CRC is scrambled by C-RNTI) is mapped to the UE-specific search space or when the TB number field for unicast scheduling exists; If multiple TBs are scheduled, this field serves as the new data indicator for the second TB.

[0078] Uplink transmission gaps and gaps caused by NPRACH transmission (UL gap and Gaps around NPRACH):

[0079] In traditional Internet of Things, there are gaps: Half Duplex (HD) gap and NPRACH gap.

[0080] The HD gap is that after 256 ms of continuous uplink transmission, the NB-IoT UE stops uplink transmission and receives downlink signals within the next 40 ms;

[0081] The NPRACH gap is that at the NPRACH occasion, the UE must stop the ongoing continuous uplink transmission to transmit NPRACH. These occasions are known to the UE (informed through the broadcast signaling System Information Block (SIB)), and these uplink NPRACH transmission occasions may also be included within 256 ms. In this case, whether it is NPUSCH transmission or NPRACH or both, the UE must stop uplink transmission after 256 ms to receive downlink (DL) information.

[0082] Due to the duration of these gaps, when the applied OCC spans the gaps, the orthogonality of the OCC codes will be disrupted.

[0083] Uplink Timing Advance gaps and segment:

[0084] In traditional Internet of Things (IoT), link budget is enhanced by using repetition, which also includes the repetition of NPUSCH / NPRACH transmissions. In R17, when the number of repetitions is large, the 3rd Generation Partnership Project (3GPP) defines segment transmission in NTN, that is, the total repeated transmission is divided into multiple segment transmissions. Time / frequency adjustment can be completed based on each segment to handle the synchronization drift caused by satellite movement. Between segments, part of the data transmission needs to be discarded to form a type-3 gap, which can be used for Timing Advance (TA) adjustment. The data transmission on the discarded resources is likely to correspond to part of the data in a certain OCC unit, resulting in the disruption of OCC orthogonality.

[0085] In an embodiment of the present application, there is provided a method for information sending and receiving, a communication node, and a storage medium that can operate in the above wireless communication system. By determining the extended OCC information according to the OCC configuration information and sending the extended OCC information to the second communication node, the system capacity is improved.

[0086] Next, the information sending method, information receiving method, communication node, and their technical effects will be described.

[0087] Figure 4 It is a schematic flowchart of an information sending method provided by an embodiment. The information sending method provided by this embodiment is applied to the first communication node. The first communication node in this embodiment can be a terminal device. As Figure 4 shown, the information sending method provided by this embodiment includes the following steps.

[0088] Step 401: Receive the OCC configuration information sent by the second communication node.

[0089] The second communication node in this embodiment can be an access network device. In the NTN scenario, the second communication node can send the OCC configuration information to the first communication node via a satellite.

[0090] In one embodiment, the OCC configuration information includes at least one of the following: a first indication for indicating to enable or disable the OCC function; a second indication for indicating OCC activation or OCC deactivation; a third indication for indicating the OCC length; a fourth indication for indicating the OCC sequence parameter, where the OCC sequence parameter includes: an OCC sequence or an OCC index.

[0091] In one embodiment, at least one of the above indications is indicated by at least one of the following means: indicated by high-layer signaling; when the OCC length or the OCC sequence parameter is indicated as a valid value, it indicates that the OCC function is enabled; when the OCC length or the OCC sequence parameter is indicated as an invalid value, it indicates that the OCC function is disabled; indicated by an existing field or a newly added field in the DCI for scheduling PUSCH; determined by the first indication and / or the second indication. The specific implementation manners of each indication will be described in detail in subsequent embodiments.

[0092] Optionally, the first indication may be indicated by high-layer signaling. Exemplarily, the high-layer signaling here may be RRC signaling.

[0093] Optionally, the second indication is indicated by at least one of the following fields in the DCI: modulation and coding scheme field, repetition field, redundancy version field, TB number field for unicast scheduling, subcarrier indication field, or resource reservation field.

[0094] Further, in at least one of the following conditions is met, the second indication is used to indicate OCC activation or OCC deactivation: the first indication indicates to enable the OCC function or the first indication is configured; the subcarrier spacing is configured to 15 kHz, where the subcarrier spacing is indicated by a high-layer parameter or the uplink subcarrier spacing in the random access response grant; the subcarrier spacing is configured to 3.75 kHz, where the subcarrier spacing is indicated by a high-layer parameter or the uplink subcarrier spacing in the random access response grant; the DCI CRC is scrambled by the C-RNTI.

[0095] Optionally, the third indication may be indicated by high-layer signaling or the DCI for scheduling PUSCH.

[0096] Further, when at least one of the following conditions is met, the third indication is used to indicate the OCC length, or the OCC length is a preset value: the first indication indicates to enable the OCC function or the first indication is configured; the second indication indicates to activate the OCC.

[0097] Optionally, the fourth indication is indicated by one of the following methods: indicated by at least one of the following fields in the DCI: modulation and coding scheme field, repetition field, redundancy version field, transport block (TB) field for unicast scheduling, subcarrier indication field, or resource reservation field; indicated by 2 bits in at least one field or a newly added field, where the 2 bits are also used to indicate OCC activation or OCC deactivation; indicated by an index set corresponding to the subcarrier indication field in the DCI, where the index set indication is also used to indicate OCC activation or OCC deactivation; indicated by an index set corresponding to the subcarrier indication field in the DCI; indicated by an existing field in the DCI as a new indication field.

[0098] Further, in the case where the fourth indication is indicated by an existing field in the DCI as a new indication field, the new indication field includes: the fourth indication, the second indication, the modulation and coding scheme, and the subcarrier indication field.

[0099] Further, the modulation and coding scheme and the subcarrier indication field included in the new indication field are used to indicate the modulation and coding scheme index and the subcarrier index corresponding to the modulation and coding scheme index, or are used to indicate the subcarrier index and the modulation and coding scheme index corresponding to the subcarrier index, or are used to indicate the modulation and coding scheme index and the subcarrier index. Wherein, each modulation and coding scheme index from 0 to A corresponds to a subcarrier index from 0 to B respectively; or, each subcarrier index from 0 to B corresponds to a modulation and coding scheme index from 0 to A respectively; or, each modulation and coding scheme index from 0 to C corresponds to a subcarrier index from 0 to D respectively; or, each subcarrier index from 0 to D corresponds to a modulation and coding scheme index from 0 to C respectively.

[0100] Exemplarily, A can be 10, B can be 47, C can be 15, and D can be 18.

[0101] Further, for the single-carrier 3.75 kHz subcarrier spacing configuration: the number of subcarrier indices corresponding to at least one modulation and coding scheme index is less than B + 1, or the number of modulation and coding scheme indices corresponding to at least one subcarrier index is less than A + 1.

[0102] Further, in the case of satisfying at least one of the following conditions, the fourth indication is used to indicate the OCC sequence parameter: the first indication indicates enabling the OCC function or the first indication is configured; the second indication indicates activating the OCC; the third indication indicates a specific OCC length; the OCC length is determined to be a specific OCC length according to the first indication and / or the second indication; the subcarrier spacing is configured to 15 kHz, where the subcarrier spacing is indicated by a high-layer parameter or the uplink subcarrier spacing in the random access response grant; the subcarrier spacing is configured to 3.75 kHz, where the subcarrier spacing is indicated by a high-layer parameter or the uplink subcarrier spacing in the random access response grant; the DCI CRC is scrambled by the C-RNTI.

[0103] Step 402: Determine the information after OCC extension according to the OCC configuration information.

[0104] In step 402, the information after OCC extension can be obtained by extending the data or the reference signal according to the OCC configuration information.

[0105] The information after OCC extension in this embodiment may include at least one of the following: the DMRS sequence, the data after OCC extension, and the DMRS sequence after OCC extension.

[0106] In one implementation, the information after OCC extension includes the DMRS sequence. Correspondingly, the implementation process of step 402 may be: determine the length of the DMRS sequence according to the OCC length in the OCC configuration information, and generate the DMRS sequence. In this implementation, the information sending method provided in this embodiment may further include: determine the time slot subgroup for the first communication node to transmit or map the DMRS sequence according to the OCC sequence parameter in the OCC configuration information.

[0107] In another implementation, the information after OCC extension includes the data after OCC extension. Correspondingly, the implementation process of step 402 may be: determine the data after OCC extension according to the OCC configuration information and the complex modulation symbol. In this implementation, the OCC sequence can be obtained according to the OCC configuration information, and the OCC sequence and the complex modulation symbol are multiplied point by point to obtain the data after OCC extension.

[0108] In another implementation manner, the information after OCC extension includes the DMRS sequence after OCC extension. Correspondingly, the implementation process of step 402 may be: determining the length of the DMRS sequence before extension according to the OCC length in the OCC configuration information, obtaining the OCC sequence according to the OCC configuration information, and determining the DMRS sequence after OCC extension according to the OCC sequence and the DMRS sequence before extension. In this implementation manner, a dot product operation may be performed on the OCC sequence and the DMRS sequence before extension to obtain the DMRS sequence after OCC extension.

[0109] In yet another implementation manner, the information after OCC extension includes the DMRS sequence after OCC extension. Correspondingly, the implementation process of step 402 may be: determining the frequency domain length of the DMRS sequence before extension according to the number of consecutive subcarriers, obtaining the OCC sequence according to the OCC configuration information, and determining the DMRS sequence after OCC extension according to the OCC sequence and the DMRS sequence before extension.

[0110] Step 403: Send the information after OCC extension to the second communication node.

[0111] Optionally, the first communication node may send the information after OCC extension to the second communication node through a physical resource mapping process. The specific implementation manner will be described in detail in the subsequent embodiments.

[0112] Optionally, the data after OCC extension in this embodiment may be transmitted in the PUSCH. This embodiment is applicable to the following PUSCH messages in NR, LTE, NB-IoT, and enhanced Machine-Type Communication (eMTC) systems: the PUSCH message on the preconfigured uplink resource PUR, the Msg3 message based on competition, the Msg3 message of four-step random access, the Msg B PUSCH of two-step random access, and the PUSCH messages in the idle state / connected state / inactive state.

[0113] The information sending method provided in this embodiment includes: receiving the OCC configuration information sent by the second communication node; determining the information after OCC extension according to the OCC configuration information; and sending the information after OCC extension to the second communication node. By determining the information after OCC extension according to the OCC configuration information and sending the information after OCC extension to the second communication node, the system capacity is improved.

[0114] Figure 5 It is a schematic flowchart of another information sending method provided by an embodiment. This embodiment is in Figure 4Based on the illustrated embodiments and various alternative implementations, the process of determining the extended OCC information according to the OCC configuration information will be described in detail. In this embodiment, the extended OCC information includes the extended OCC data. As Figure 5 shown, the information sending method provided in this embodiment includes the following steps.

[0115] Step 501: Receive the OCC configuration information sent by the second communication node.

[0116] The implementation process and technical principle of Step 501 are similar to those of Step 401, and will not be elaborated here.

[0117] Step 502: Determine the OCC sequence parameters according to the OCC configuration information.

[0118] Step 503: Determine the OCC sequence according to the OCC sequence parameters.

[0119] Optionally, the OCC sequence parameters can be determined according to the fourth indication. After the OCC sequence parameters are determined, the OCC sequence can be determined.

[0120] Step 504: Determine the extended OCC data according to the OCC sequence and the complex modulation symbols.

[0121] Optionally, the complex modulation symbols in this embodiment can be the modulated complex modulation symbols or other complex modulation symbols.

[0122] Optionally, the implementation process of Step 504 includes at least one of the following: extending the complex modulation symbols on each time-domain symbol block obtained by dividing the complex modulation symbols with the OCC sequence to obtain the extended OCC data; extending the complex modulation symbols on each time-slot block obtained by dividing the complex modulation symbols with the OCC sequence to obtain the extended OCC data; extending the complex modulation symbols on each repetition unit block obtained by dividing the complex modulation symbols with the OCC sequence to obtain the extended OCC data. It should be noted that the extension of the complex modulation symbols by the OCC sequence here refers to multiplying the complex modulation symbols and the OCC sequence.

[0123] Optionally, when at least one of the following conditions is met, the step of determining the OCC extended data according to the OCC sequence and the complex modulation symbol is determined: the first indication indicates that the OCC function is enabled or the first indication is configured; the second indication indicates that the OCC is activated; the third indication indicates a specific OCC length; the OCC length is determined to be a specific OCC length according to the first indication and / or the second indication; the fourth indication indicates a specific OCC sequence parameter; the subcarrier spacing is configured to 15kHz, wherein the subcarrier spacing is indicated by a high-level parameter or by an uplink subcarrier spacing in a random access response authorization; the subcarrier spacing is configured to 3.75kHz, wherein the subcarrier spacing is indicated by a high-level parameter or by an uplink subcarrier spacing in a random access response authorization; the number of consecutive subcarriers is configured as multiple carriers, wherein the number of subcarriers is indicated by the subcarrier indication field in the DCI that schedules the PUSCH.

[0124] Step 505: Send the OCC-extended data to the second communication node.

[0125] Optionally, in this embodiment, the data after OCC expansion includes a second PUSCH codeword. The information transmission method provided in this embodiment also includes the following steps: the scrambling sequence of the first PUSCH codeword is repeated every OCC length or Reinitialize after repeated transmissions, where N represents the first PUSCH codeword mapping before OCC extension RU The second PUSCH codeword is mapped to N RU,enh resource units, where N RU,enh Indicates the number of resource units, N RU,enh The number N of resource units mapped by the OCC length and the first PUSCH codeword RU OK, every N RU,enh Resource units are transmitted Second-rate, length.

[0126] For example, N RU,enh =N RU *OCC length.

[0127] Furthermore, the second PUSCH codeword is mapped to N RU,enh resource units, including any of the following: mapped to N s'(ts After a time slot, N times should be repeated before continuing to map z(·) to the next time slot. s'(ts Time slot times, among which, is equal to 1, Indicates the number of repetitions of consecutive time slots, Ns'(ts Indicates the number of consecutive time slots; mapped to OCC length * N ；:<7； After the time slot, before continuing to map z(·) to the next time slot, OCC length * N should be repeated ；:<7； Time slot times equals length or length

[0128] Optionally, step 505 includes at least one of the following:

[0129] For the second PUSCH codeword corresponding to the j-th TB, it is transmitted in B consecutive time slots ni, where i = jB + b, b = 0, 1,..., B - 1, Redundancy version rv associated with the TB ,-J (j) is determined as follows: rv ,-J (j) = 2 * mod(rv e.1 + j, 2), if then L = 1, and the part of the second PUSCH codeword associated with rv ,-J (j) will be mapped to the FU,e.1 th time slot among the allocated N resource units for transmission, represents the number of time slots included in the resource unit, and rv e.1 is indicated by the redundancy version field in the DCI or predefined, represents the number of consecutive subcarriers;

[0130] For the second PUSCH codeword corresponding to the j-th TB, it is transmitted in B consecutive time slots ni, where i = jB + b, b = 0, 1,..., B - 1, Redundancy version rv associated with the TB ,-J (j) is determined as follows: rv ,-J (j) = 2 * mod(rv e.1 + j, 2), if then L = 1, otherwise

[0131] In the case of a subcarrier spacing of 3.75 kHz, in the uplink time slot associated with the TB, the mapping of time slot n i is as follows In the case of a subcarrier spacing of 15 kHz, in the uplink time slot associated with the TB, the mapping of time slot ni is as follows

[0132] The information sending method provided in this embodiment can determine the OCC sequence parameters according to the OCC configuration information, determine the OCC sequence according to the OCC sequence parameters, determine the data after OCC extension according to the OCC sequence and the complex modulation symbols, and send the data after OCC extension to the second communication node, thereby improving the system capacity.

[0133] In another embodiment, the information after OCC extension includes a DMRS sequence. The implementation process of step 402 can be: determine the length of the DMRS sequence according to the formula and generate the DMRS sequence. Wherein, represents the repetition times of N FU resource units mapped by the first PUSCH codeword before OCC extension, represents the number of time slots included in the resource unit, and N FU represents the number of resource units mapped by the first PUSCH codeword before OCC extension. The OCC length can be determined according to the OCC configuration information. The method for generating the DMRS sequence can refer to the existing protocol.

[0134] The DMRS sequence in this embodiment can be a time-division multiplexed DMRS sequence. Therefore, the information sending method further includes at least one of the following: determining the time slot subgroup for the first communication node to transmit or map the DMRS sequence according to the OCC sequence parameters and the number of time slot subgroups; determining the time slot subgroup for the first communication node to transmit or map the DMRS sequence according to the mapping relationship between the OCC sequence parameters and the time slot subgroup. Among them, the OCC sequence parameters can be determined according to the OCC configuration information.

[0135] This embodiment may further include step 401 and step 403, which will not be elaborated here.

[0136] In step 403, this embodiment may send the DMRS sequence to the second communication node based on the determined time slot subgroup.

[0137] The information sending method provided in this embodiment can determine the length of the DMRS sequence according to the OCC configuration information, generate the DMRS sequence, and determine the time slot subgroup for the first communication node to transmit or map the DMRS sequence according to the OCC sequence parameters and the number of time slot subgroups. On the one hand, it improves the system capacity, and on the other hand, it avoids DMRS sequence conflicts and realizes time-division multiplexed DMRS.

[0138] In yet another embodiment, the information after OCC extension includes the DMRS sequence after OCC extension. The implementation process of step 402 can include any one of the following:

[0139] According to the formula Determine the length of the DMRS sequence before OCC expansion, and determine the DMRS sequence after OCC expansion according to the OCC sequence and the DMRS sequence before OCC expansion, where the OCC sequence is information determined according to OCC configuration information. Indicates the repetition times of N RU resource units mapped by the first PUSCH codeword before OCC expansion, and N RU indicates the number of resource units mapped by the first PUSCH codeword. Indicates the number of time slots included in the resource unit;

[0140] Determine the frequency-domain length of the DMRS sequence before OCC expansion according to the number of consecutive subcarriers, and determine the DMRS sequence after OCC expansion according to the OCC sequence and the DMRS sequence before OCC expansion;

[0141] Determine the frequency-domain length of the DMRS sequence before OCC expansion according to the number of consecutive subcarriers, and determine the DMRS sequence after OCC expansion according to the cyclic shift and the DMRS base sequence, where the cyclic shift is related to the OCC sequence.

[0142] This embodiment may further include step 401 and step 403, which will not be elaborated here.

[0143] Optionally, the DMRS in this embodiment may be time-domain code-division multiplexed DMRS or frequency-domain code-division multiplexed DMRS.

[0144] Further, when at least one of the following conditions is satisfied, determine to execute the step of determining the information after OCC expansion according to the OCC configuration information: the first indication indicates that the OCC function is enabled or the first indication is configured; the second indication indicates to activate OCC; the third indication indicates a specific OCC length; the OCC length is determined to be a specific OCC length according to the first indication and / or the second indication; the fourth indication indicates specific OCC sequence parameters; the subcarrier spacing is configured to 15 kHz, where the subcarrier spacing is indicated by a high-layer parameter or the uplink subcarrier spacing in the random access response grant; the subcarrier spacing is configured to 3.75 kHz, where the subcarrier spacing is indicated by a high-layer parameter or the uplink subcarrier spacing in the random access response grant; the number of consecutive subcarriers is configured to 1, where the number of subcarriers is indicated by the subcarrier indication field in the DCI scheduling the PUSCH; the number of consecutive subcarriers is configured to multiple carriers, where the number of subcarriers is indicated by the subcarrier indication field in the DCI scheduling the PUSCH.

[0145] The information sending method provided in this embodiment can realize OCC expansion of the DMRS sequence, thereby improving the system capacity.

[0146] In another embodiment, the information after OCC extension includes at least one of the following: DMRS sequence, data after OCC extension, and DMRS sequence after OCC extension. The method further includes at least one of the following: when the information after OCC extension is delayed, performing delay based on the OCC group, where the OCC group is the one with a longer duration among the data after OCC extension and the DMRS sequence after OCC extension; after the information after OCC extension is delayed, performing delay based on the delay time, where the delay time is an integer multiple of the OCC alignment length, and the OCC alignment length is the duration of the OCC group.

[0147] In this embodiment, performing delay based on the OCC group means that when a delay occurs, the OCC group is used as the minimum transmission unit for delayed transmission.

[0148] Further, the method further includes the following steps: determining to perform the step of delaying based on the OCC group or delaying based on the delay time when at least one of the following conditions is met: the first indication indicates that the OCC function is enabled or the first indication is configured; the second indication indicates the activation of OCC; the third indication indicates a specific OCC length; the OCC length is predefined as a valid value; the fourth indication indicates specific OCC sequence parameters; the subcarrier spacing is configured to 15 kHz, where the subcarrier spacing is indicated by a higher-layer parameter or the uplink subcarrier spacing in the random access response grant; the subcarrier spacing is configured to 3.75 kHz, where the subcarrier spacing is indicated by a higher-layer parameter or the uplink subcarrier spacing in the random access response grant; the number of consecutive subcarriers is configured to 1, where the number of subcarriers is indicated by the subcarrier indication field in the DCI scheduling the PUSCH; the number of consecutive subcarriers is configured to multiple carriers, where the number of subcarriers is indicated by the subcarrier indication field in the DCI scheduling the PUSCH.

[0149] Since the various gaps introduced above may cause OCC cross-gap transmission or the orthogonality of OCC to be destroyed due to the discarding of certain time slots / symbols, in this embodiment, delay can be performed based on the OCC group and / or based on the delay time, thereby ensuring the OCC orthogonality during the transmission process.

[0150] The following uses several specific embodiments to illustrate the above information sending method.

[0151] In the embodiments of the present application, the method is applicable to the following PUSCH messages in NR, LTE, NB-IoT, and eMTC systems: PUSCH messages on preconfigured uplink resource PUR, Msg3 messages based on contention, Msg3 messages for four-step random access, Msg B PUSCH for two-step random access, and PUSCH messages in idle / connected / inactive states. To enhance the capacity of PUSCH, one of the following methods can be considered.

[0152] Code division multiplexing:

[0153] The following uses the first communication node as the UE for illustration. Assume the signal is X (X can be data or DMRS), and two UEs are multiplexed. The OCC sequence of UE1 is [+1 +1], and the OCC sequence of UE2 is [+1 -1]. The signal of each UE is transmitted twice repetitively with the same content. UE1 and UE2 send signals X1 and X2 respectively on the same time-frequency domain resources. Therefore, the superimposed signals generated at the positions of the first repetition and the second repetition can be expressed as Y1 and Y2. Then Y1 = H 1,1 X1 + H 2, 1X2 and Y2 = H 1,2 X1 - H 2,2 X2, where Hm,n is the channel of UEm at the nth repetition. Assume the channel remains consistent at different repetitions, that is, H1 = H 1,1 = H 1,2 and H2 = H 2,1 = H 2,2 , then the signals of UE1 and UE2 can be demultiplexed and obtained in the following way: X1 = (Y1 + Y2) / 2H1, X2 = (Y1 - Y2) / 2H2.

[0154] Figure 6 is a schematic diagram of obtaining signals in code division multiplexing provided by an embodiment. As Figure 6 shown, X1 and X2 can be calculated as functions of Y1 and Y2 and their corresponding channel state information.

[0155] Embodiment 1: OCC configuration information

[0156] In Embodiment 1, the implementation methods of each indication are mainly described.

[0157] The fields included in the DCI for scheduling PUSCH are: modulation and coding scheme field, repetition field, redundancy version field, TB number field for unicast scheduling, subcarrier indication field, resource reservation field, resource allocation field, scheduling delay field, new data indication field, DCI subframe repetition field, HARQ process number field, antenna port field, DMRS port field, time-domain resource allocation field.

[0158] OCC Enable Indication (First Indication)

[0159] 1), The OCC Enable Indication (First Indication) can be indicated by RRC signaling. For example, 0 indicates disabling the OCC function, 1 indicates enabling the OCC function, and vice versa; or it can be indicated by the OCC length or OCC sequence parameter (such as OCC index, or OCC sequence) whether to enable. For example, when the OCC length is indicated as a valid value (such as OCC length is 2, OCC length is 4), it indicates enabling the OCC function, otherwise, it indicates disabling the OCC function to receive the OCC Enable Indication.

[0160] OCC Activation Indication (Second Indication)

[0161] 2), The OCC Activation (Second Indication) is indicated by the DCI that schedules PUSCH (such as DCI format N0). For example, reinterpreting the above fields (such as modulation and coding scheme field, repetition field, redundancy version field, TB number field for unicast scheduling, subcarrier indication field, resource reservation field, resource allocation field, scheduling delay field, new data indication field, DCI subframe repetition field, HARQ process number field) or adding new fields to indicate OCC activation or deactivation:

[0162] a, A 1-bit (bit) of the field indicates OCC activation or deactivation (for example, reinterpret the most significant bit (MSB) or least significant bit (LSB) of the existing field, or add a 1-bit dedicated field). 0 indicates deactivating OCC, 1 indicates activating OCC, and vice versa; such as:

[0163] a), Modulation and coding scheme field, example:

[0164] ⅰ, When the OCC Enable Indication is configured to enable the OCC function or when the OCC Enable Indication is configured:

[0165] ⅰ), 1 bit is used to indicate OCC activation or deactivation. This may be regarded as part of the modulation and coding scheme field, or regarded as a new field;

[0166] ⅱ), 3 bits are used to indicate the modulation and coding scheme;

[0167] ⅱ, Otherwise, it is indicated according to the existing rules. For example, 4 bits are used to indicate the modulation and coding scheme.

[0168] b), Repetition field, example:

[0169] ⅰ, When the OCC Enable Indication is configured to enable the OCC function or when the OCC Enable Indication is configured:

[0170] i), 1 bit is used to indicate the activation or deactivation of OCC. This may be regarded as part of a repeated field or as a new field;

[0171] ii), 2 bits are used to indicate the repetition number;

[0172] ii. Otherwise, it is indicated according to the existing rules. For example, 3 bits are used to indicate the repetition number.

[0173] c), Redundancy version field, example:

[0174] i. When the OCC enable indication is configured to enable the OCC function or when the OCC enable indication is configured:

[0175] i) 1 bit is used to indicate the activation or deactivation of OCC. This may be regarded as part of the redundancy version field or as a new field;

[0176] ii) The redundancy version is set to 0 or 2, or the redundancy version is set to cycle starting from 0 or 2;

[0177] ii. Otherwise, it is indicated according to the existing rules. For example, 1 bit is used to indicate the redundancy version.

[0178] d) TB number field for unicast scheduling, example:

[0179] i. When the OCC enable indication is configured to enable the OCC function:

[0180] i) 1 bit is used to indicate the activation or deactivation of OCC. This may be regarded as part of the TB number field for unicast scheduling or as a new field;

[0181] ii) The number of TBs for unicast scheduling is 1 or 2;

[0182] ii. Otherwise, it is indicated according to the existing rules. For example, 1 bit is used to indicate the number of TBs for unicast scheduling.

[0183] e) Subcarrier indication field, example:

[0184] i. When the OCC enable indication is configured to enable the OCC function or when the OCC enable indication is configured, and / or when the subcarrier spacing is configured to 15 kHz:

[0185] i) 1 bit is used to indicate the activation or deactivation of OCC. This may be regarded as part of the subcarrier indication field or as a new field;

[0186] ii) 5 bits are used to indicate the subcarrier:

[0187] Assuming that the most significant 1 bit is used to indicate OCC activation or deactivation, the correspondence between the subcarrier indication field and the set of subcarriers allocated for PUSCH is shown in Table 3. This table only applies to the 15 kHz subcarrier spacing configuration (i.e., one of the conditions to be met in b below), or when the subcarrier spacing is 3.75 kHz, 0 - 31 corresponds to subcarriers 0 to 31.

[0188] ii. Otherwise, indicate according to the existing rules. For example, 6 bits are used to indicate subcarriers.

[0189] Table 3 Subcarriers Allocated for PUSCH with a Subcarrier Spacing of 15 kHz

[0190]

[0191]

[0192] f) Resource reservation field, example:

[0193] i. The OCC enable indication is configured to enable the OCC function or the OCC enable indication is configured:

[0194] i). 1 bit is used to indicate OCC activation or deactivation. This may be regarded as part of the resource reservation field or as a new field;

[0195] ii). According to the higher layer parameters, the reserved subframes are not regarded as NB - IoT uplink subframes. Or, ignore the configuration of the higher layer parameters regarding the reserved subframes.

[0196] ii. Otherwise, indicate according to the existing rules. For example, 1 bit is used to indicate the reserved subframe.

[0197] g) New / dedicated field:

[0198] i. The OCC enable indication is configured to enable the OCC function or the OCC enable indication is configured:

[0199] i). 1 bit is used to indicate OCC activation or deactivation:

[0200] ii. Otherwise, this field does not exist;

[0201] iii. OCC may not be enabled simultaneously with multi - TB scheduling. Or, OCC may not be enabled simultaneously with resource reservation. Specifically, it may be manifested as:

[0202] i) This field may not co - exist with the TB number field of unicast scheduling. Or, this field may not co - exist with the resource reservation field. Or, the UE does not expect this field to co - exist with the TB number field of unicast scheduling. Or, the UE does not expect this field to co - exist with the resource reservation field.

[0203] ii) The OCC enabling indication may not be configured simultaneously with the multi-TB scheduling enabling indication (e.g., npusch-MultiTB-Config). Alternatively, the OCC enabling indication may not be configured simultaneously with the resource reservation indication (e.g., resourceReservationConfigUL).

[0204] b. When at least one of the following conditions is met, the OCC activation indication (the second indication) is used to indicate OCC activation or deactivation:

[0205] a. The OCC enabling indication (the first indication) indicates that the OCC function is enabled or the OCC enabling indication is configured;

[0206] b. When the subcarrier spacing is configured to 15 kHz, where the subcarrier spacing is indicated by a higher layer parameter or the uplink subcarrier spacing in the random access response grant;

[0207] c. When the subcarrier spacing is configured to 3.75 kHz, where the subcarrier spacing is indicated by a higher layer parameter or the uplink subcarrier spacing in the random access response grant;

[0208] d. The DCI CRC is scrambled by the C-RNTI.

[0209] OCC length indication (the third indication)

[0210] 3. The OCC length (the third indication) can be indicated by higher layer signaling or the DCI that schedules the PUSCH (reusing the above DCI fields or adding new fields), or implicitly determined by the first indication and / or the second indication:

[0211] a. Occupying 1 bit, 0 indicates that the OCC length is 1, 1 indicates that the OCC length is 2, and vice versa; or 0 indicates that the OCC length is 2, 1 indicates that the OCC length is 4, and vice versa; when at least one of the following conditions is met, the OCC length indication (the third indication) is used to indicate the OCC length:

[0212] a. The OCC enabling indication (the first indication) indicates that the OCC function is enabled or the OCC enabling indication is configured;

[0213] b. The OCC activation indication (the second indication) indicates OCC activation;

[0214] b. Or, when at least one of the following conditions is met, the OCC length is 2:

[0215] a. The OCC enabling indication (the first indication) indicates that the OCC function is enabled or the OCC enabling indication is configured;

[0216] b. The OCC activation indication (the second indication) indicates OCC activation.

[0217] OCC Index / Sequence Indication (Fourth Indication)

[0218] 4) The OCC sequence index (Fourth Indication) is indicated by the DCI that schedules the PUSCH (e.g., DCI format N1). If the above fields are reinterpreted (e.g., modulation and coding scheme field, repetition field, redundancy version field, TB number field for unicast scheduling, subcarrier indication field, resource reservation field, resource allocation field, scheduling delay field, new data indication field, DCI subframe repetition field, HARQ process number field) or new fields are added, they indicate the OCC index / sequence:

[0219] a. The OCC index / sequence is indicated by 1 bit of the field. 0 indicates OCC index 0, and 1 indicates OCC index 1, and vice versa; or 0 indicates OCC sequence [1 1], and 1 indicates OCC sequence [1 -1], and vice versa. For example,

[0220] a). For the modulation and coding scheme field, the most significant bit or the least significant bit is used as the OCC index / sequence indication. Example:

[0221] ⅰ. When the OCC enable indication (First Indication) is configured to enable the OCC function or the OCC enable indication is configured, and / or the OCC activation indication (Second Indication) indicates the activation of OCC:

[0222] ⅰ). 1 bit is used to indicate the OCC index / sequence. This may be regarded as part of the modulation and coding scheme field or as a new field;

[0223] ⅱ). 3 bits are used to indicate the modulation and coding scheme.

[0224] ⅱ. Otherwise, it is indicated according to the existing rules. For example, 4 bits are used to indicate the modulation and coding scheme.

[0225] b. For the repetition field, example:

[0226] ⅰ. When the OCC enable indication (First Indication) is configured to enable the OCC function or the OCC enable indication is configured, and / or the OCC activation indication (Second Indication) indicates the activation of OCC:

[0227] ⅰ). 1 bit is used to indicate the OCC index / sequence. This may be regarded as part of the repetition field or as a new field;

[0228] ⅱ). 2 bits are used to indicate the repetition number.

[0229] ⅱ. Otherwise, it is indicated according to the existing rules. For example, 3 bits are used to indicate the repetition number.

[0230] c. For the redundancy version field, example:

[0231] i. When the OCC enabling indication (first indication) is configured to enable the OCC function or the OCC enabling indication is configured, and / or when the OCC activation indication (second indication) indicates the activation of OCC:

[0232] i). 1 bit is used to indicate the OCC index / sequence. This may be regarded as part of the redundant version field or as a new field;

[0233] ii). The redundant version is set to 0 or 2, or the redundant version is set to cycle starting from 0 or 2.

[0234] ii. Otherwise, it is indicated according to the existing rules. For example, 1 bit is used to indicate the redundant version.

[0235] d). The TB number field for unicast scheduling, example:

[0236] i. When the OCC enabling indication (first indication) is configured to enable the OCC function or the OCC enabling indication is configured, and / or when the OCC activation indication (second indication) indicates the activation of OCC:

[0237] i). 1 bit is used to indicate the OCC index / sequence. This may be regarded as part of the TB number field for unicast scheduling or as a new field;

[0238] ii. The number of TBs for unicast scheduling is 1 or 2.

[0239] ii. Otherwise, it is indicated according to the existing rules. For example, 1 bit is used to indicate the number of TBs for unicast scheduling.

[0240] e). The subcarrier indication field, example:

[0241] i. When the OCC enabling indication (first indication) is configured to enable the OCC function, and / or when the OCC activation indication (second indication) indicates the activation of OCC, and / or when the subcarrier spacing is configured to 15 kHz:

[0242] i). 1 bit is used to indicate the OCC index / sequence. This may be regarded as part of the subcarrier indication field or as a new field;

[0243] ii). 5 bits are used to indicate the subcarrier.

[0244] ii. Otherwise, it is indicated according to the existing rules. For example, 6 bits are used to indicate the subcarrier.

[0245] Assuming that the most significant 1 bit is used to indicate the index, the correspondence between the subcarrier indication field and the set of subcarriers allocated for PUSCH is shown in Table 3.

[0246] f). The resource reservation field:

[0247] ⅰ. The OCC enabling indication (first indication) is configured to enable the OCC function or the OCC enabling indication is configured, and / or, when the OCC activation indication (second indication) indicates the activation of OCC;

[0248] ⅰ). 1 bit is used to indicate the OCC index / sequence. This may be regarded as part of the resource reservation field or as a new field;

[0249] ⅱ). According to the high-layer parameters, the reserved subframes are not regarded as NB-IoT uplink subframes. Alternatively, the configuration of the high-layer parameters regarding the reserved subframes is ignored.

[0250] ⅱ. Otherwise, it is indicated according to the existing rules. For example, 1 bit is used to indicate whether the reserved subframes are determined according to the high-layer parameters.

[0251] g) New / special fields:

[0252] ⅰ. When the OCC enabling indication (first indication) is configured to enable the OCC function or the OCC enabling indication is configured, and / or, when the OCC activation indication (second indication) indicates the activation of OCC:

[0253] ⅰ). 1 bit is used to indicate the OCC index / sequence;

[0254] ⅱ. Otherwise, this field does not exist;

[0255] ⅲ. OCC may not be enabled simultaneously with multi-TB scheduling. Alternatively, OCC may not be enabled simultaneously with resource reservation. Specifically, it may be manifested as:

[0256] ⅰ). This field may not coexist with the TB number field of unicast scheduling. Alternatively, this field may not coexist with the resource reservation field. Alternatively, the UE does not expect this field to coexist with the TB number field of unicast scheduling. Alternatively, the UE does not expect this field to coexist with the resource reservation field.

[0257] ⅳ. The OCC enabling indication may not be configured simultaneously with the multi-TB scheduling enabling indication (such as npusch-MultiTB-Config). Alternatively, the OCC enabling indication may not be configured simultaneously with the resource reservation indication (such as resourceReservationConfigUL).

[0258] h). Or in other methods, for the fields mentioned above, 2 bits are occupied:

[0259] ⅰ. When the OCC enabling indication (first indication) is configured to enable the OCC function or the OCC enabling indication is configured:

[0260] ⅰ). 2 bits are used to indicate the OCC index / sequence and OCC activation or deactivation, example:

[0261] "00" indicates OCC index 0 and OCC activation; "01" indicates OCC index 1 and OCC activation; "10" indicates OCC deactivation; or "00" indicates OCC sequence [1 1] and OCC activation; "01" indicates OCC sequence [1 -1] and OCC activation; "10" indicates OCC deactivation.

[0262] ii. Otherwise, this field does not exist.

[0263] b. The OCC index / sequence is indicated by the corresponding index set of the field. For example, index a~b represents OCC index 0 or OCC sequence [1 1] (implicitly indicating OCC activation), index c~d represents OCC index 1 or OCC sequence [1 -1] (implicitly indicating OCC activation), index e~f indicates OCC deactivation, and other indexes are reserved settings, without excluding other corresponding relationships;

[0264] a). For example, for the subcarrier indication field:

[0265] i. When the OCC enable indication (the first indication) is configured to enable the OCC function or the OCC enable indication is configured, and / or, when the OCC activation indication (the second indication) indicates OCC activation, and the subcarrier spacing is configured to 15 kHz:

[0266] i). Index 0~18 represents OCC index 0 or OCC sequence [1 1], index 19~37 represents OCC index 1 or OCC sequence [1 -1], index 38~56 represents OCC deactivation. At this time, the corresponding relationship between the subcarrier indication field and the set of subcarriers allocated for PUSCH is shown in Table 4, without excluding other corresponding relationships.

[0267] ii. Otherwise, it is indicated according to the existing rules.

[0268] c. The OCC index / sequence is indicated by the corresponding index set of the field. For example, index a~b represents OCC index 0 or OCC sequence [1 1], index c~d represents OCC index 1 or OCC sequence [1 -1], and other indexes are reserved settings, without excluding other corresponding relationships;

[0269] a). For example, for the subcarrier indication field:

[0270] i. When the OCC enable indication (the first indication) is configured to enable the OCC function or the OCC enable indication is configured, and the OCC activation indication (the second indication) indicates OCC activation, and the subcarrier spacing is configured to 15 kHz:

[0271] ⅰ). The indices 0 to 18 represent OCC index 0 or OCC sequence [1 1], and the indices 19 to 37 represent OCC index 1 or OCC sequence [1 -1]. At this time, the correspondence between the subcarrier indication field and the set of subcarriers allocated for PUSCH is shown in Table 5, without excluding other correspondences.

[0272] ⅱ. Otherwise, indicate according to the existing rules.

[0273] Table 4 A schematic diagram of the subcarriers allocated for PUSCH when the subcarrier spacing is 15 kHz

[0274]

[0275] In other correspondences, Table 4 can be Table 4-1.

[0276] Table 4-1 Another schematic diagram of the subcarriers allocated for PUSCH when the subcarrier spacing is 15 kHz

[0277]

[0278]

[0279] Table 5 The subcarriers allocated for PUSCH when the subcarrier spacing is 15 kHz

[0280]

[0281] d. In the above method, the indication of OCC index or OCC sequence for reused or newly added fields is defined. Whether the above fields exist is affected by the relevant configurations defined in e, such as OCC enable indication, OCC activation indication, etc. Similarly, the above method can also be described as when the relevant configurations defined in e are configured, such as OCC enable indication, OCC activation indication, and the original field occupancy bits exist as new indication fields. The example method is as follows:

[0282] a). When at least one of the conditions defined in e is met, at least one of the redundancy version field, modulation and coding field, subcarrier indication field, resource reservation field, and unicast scheduled TB number field does not exist, and the following fields are indicated in the DCI:

[0283] ⅰ. OCC activation indication, occupying 1 bit, 0 indicates deactivation of OCC, 1 indicates activation of OCC, and vice versa;

[0284] ⅱ. OCC index / sequence indication, occupying 1 bit, 0 indicates OCC index 0, 1 indicates OCC index 1, and vice versa; or 0 indicates OCC sequence [1 1], 1 indicates OCC sequence [1 -1], and vice versa;

[0285] ⅲ. Modulation and Coding Scheme and Subcarrier Indication, occupying 9 bits:

[0286] ⅰ). For the single - carrier 3.75 kHz subcarrier spacing configuration: The number of valid indices for the modulation and coding scheme is 11, i.e., 0 - 10, and the number of valid subcarrier indices is 0 - 47. The following method can be adopted:

[0287] a)). Each index from 0 - 10 of the modulation and coding scheme index corresponds to subcarrier indices from 0 - 47 respectively, that is, there are a total of 11 * 48 = 528 combinations. At this time, 9 bits may not be able to fully carry (512 indices), so there is a modulation and coding scheme index corresponding to some subcarriers (i.e., the corresponding number of subcarriers is less than 48), such as corresponding to 0 - 31 or 16 - 47 or 32 subcarrier indices specified from 0 - 48. The relationship between the modulation and coding scheme and subcarrier indication fields and the modulation and coding scheme index and subcarrier index is shown in Table 6. Table 6 is only for example and does not exclude other corresponding relationships. Table 6 A relationship between the modulation and coding scheme and subcarrier indication fields and the modulation and coding scheme index and subcarrier index

[0288] Modulation and Coding Scheme and Subcarrier Index Modulation and Coding Scheme Index Subcarrier Index 0-47 0 0-47 48-95 1 0-47 ... ... ... 480-511 10 0-31

[0289] b)). Or each index from 0 - 47 of the subcarrier index corresponds to the modulation and coding scheme index from 0 - 10 respectively, that is, there are a total of 48 * 11 = 528 combinations. At this time, 9 bits may not be able to fully carry (512 indices), so there are some subcarrier indices that do not correspond to all modulation and coding scheme indices, such as these subcarrier indices corresponding to 0 - 2 or 8 - 10 or some subcarrier indices specified from 0 - 10. The relationship between the modulation and coding scheme and subcarrier indication fields and the subcarrier index and modulation and coding scheme index is shown in Table 7. Table 7 is only for example and does not exclude other corresponding relationships.

[0290] Table 7 A relationship between the modulation and coding scheme and subcarrier indication fields and the subcarrier index and modulation and coding scheme index

[0291] Modulation and Coding Scheme and Subcarrier Index Subcarrier Index Modulation and Coding Scheme Index 0-10 0 0-10 11-21 1 0-10 ... ... ... 495-505 45 0-10 506-508 46 0-2 509-511 47 0-2

[0292] ⅱ). For the single - carrier 15 kHz subcarrier spacing configuration: The number of valid indices for the modulation and coding scheme is 16, i.e., 0 - 15, and the number of valid subcarrier indices is 19, i.e., 0 - 18. The following method can be adopted:

[0293] a)). Each index from 0 - 15 of the modulation and coding scheme index corresponds to subcarrier indices from 0 - 18 respectively, that is, there are a total of 16 * 19 = 304 combinations. At this time, 9 bits can fully carry (512 indices) and include reserved states. The relationship between the modulation and coding scheme and subcarrier indication fields and the modulation and coding scheme index and subcarrier index is shown in Table 8. Table 8 is only for example and does not exclude other corresponding relationships.

[0294] Table 8 Another relationship between the modulation and coding and subcarrier indication fields and the modulation and coding index and subcarrier index

[0295]

[0296]

[0297] b)) For each index from 0 to 18 of the subcarrier index, it respectively corresponds to the modulation and coding scheme index from 0 to 15. That is, there are a total of 19 * 16 = 304 combinations. At this time, 9 bits can fully carry (512 indexes) and include the reserved state. The relationship between the modulation and coding scheme and subcarrier indication fields and the subcarrier index and modulation and coding scheme index is shown in Table 9. Table 9 is only for example and does not exclude other corresponding relationships.

[0298] Table 9 Modulation and coding scheme and subcarrier indication fields and subcarrier index and modulation and coding scheme index

[0299] Modulation and Coding Scheme and Subcarrier Index Subcarrier Index Modulation and Coding Scheme Index 0-15 0 0-15 16-31 1 0-15 ... ... ... 288-303 18 0-15 304-511 Reserved Reserved

[0300] iv. When at least one of the conditions defined in e is met, the above fields exist or are used to indicate the corresponding functions.

[0301] e. When at least one of the following conditions is met, the OCC index indication (the fourth indication) is used to indicate the OCC index:

[0302] a). The OCC enable indication (the first indication) indicates that the OCC function is enabled or the OCC enable indication is configured;

[0303] b). The OCC activation indication (the second indication) indicates the activation of the OCC;

[0304] c). The OCC length indication (the third indication) indicates a specific OCC length;

[0305] d). The OCC length is determined to be a specific OCC length according to an indication (such as the first indication or the second indication);

[0306] e). When the subcarrier spacing is configured to 15 kHz, where the subcarrier spacing is indicated by a higher layer parameter or by the uplink subcarrier spacing indication in the random access response grant;

[0307] f). When the subcarrier spacing is configured to 3.75 kHz, where the subcarrier spacing is indicated by a higher layer parameter or by the uplink subcarrier spacing indication in the random access response grant;

[0308] g). The DCI CRC is scrambled by the C-RNTI.

[0309] It should be noted that the OCC activation indication and the OCC index indication can be indicated by the same field, as shown in h). Alternatively, they can be indicated by different fields, such as: using the RV field to indicate OCC activation or deactivation, using the MCS field to indicate the OCC index, and vice versa; or, using the RV field to indicate OCC activation or deactivation, using the resource reservation field to indicate the OCC index, and vice versa; or, using the RV field to indicate OCC activation or deactivation, using the new / additional dedicated field to indicate the OCC index, and vice versa; or, using the RV field to indicate OCC activation or deactivation, using the unicast scheduling TB number field to indicate the OCC index, and vice versa; or, using the resource reservation field to indicate OCC activation or deactivation, using the unicast scheduling TB number field to indicate the OCC index, and vice versa. That is, the above OCC activation indication can be combined with the OCC index indication to represent different OCC activation and OCC index indication methods.

[0310] Embodiment 2: OCC application or extension / slotted extension

[0311] In Embodiment 2, the process of performing OCC extension or OCC application on the complex modulated symbols based on the OCC configuration information is mainly described. In this embodiment, the OCC sequence parameters can be determined based on the OCC configuration information, and according to the OCC sequence parameters, the OCC sequence is determined. It corresponds to Figure 5 the embodiment shown. In this embodiment, the complex modulated symbol after modulation is taken as an example for illustration.

[0312] 5) The OCC application or OCC extension or slotted extension using OCC can be at the symbol level (e.g., OCC application based on a single symbol granularity), at the time slot level (e.g., OCC application based on a single time slot granularity, OCC application based on multiple time slot granularities, or OCC application based on a repeating unit granularity), and the application or extension operation is a multiplication operation.

[0313] a. For OCC application or extension at the single symbol granularity:

[0314] a). The complex modulated symbols after modulation are divided into multiple time domain symbol blocks d(0),..., d(N - 1), and the complex modulated symbols on each time domain symbol block are extended by the OCC sequence. In this embodiment, each time domain symbol block corresponds to the complex modulated symbols on all subcarriers of a time domain symbol. N is the number of symbol blocks before OCC application or OCC extension. The nth time domain symbol block can be represented as a column vector d(n), which contains one or more complex modulated symbols, for example, represented as d(n) = [d 0 (n),..., d M-1 (n)] T, where M is the number of subcarriers, and d(n) represents the complex modulation symbols on all subcarriers in a time-domain symbol block. The OCC sequence w may be represented as a row vector w, for example, w = [w 0 ,..., w Nocc-1 , and Nocc represents the OCC length. Then the OCC application or OCC extension process may be represented as d(n) * w, for example, d(n) * w = [w 0 d(n),..., w Nocc-1 d(n)]. That is, a time-domain symbol block d(n) is extended into Nocc symbol blocks w 0 d(n),..., w Nocc-1 d(n). After the OCC application or OCC extension, the N time-domain symbol blocks d(0),..., d(N - 1) may be transformed into N * Nocc symbol blocks:

[0315] w 0 d(0),..., w Nocc-1 d(0), w 0 d(1),..., w Nocc-1 d(1),..., w 0 d(N - 1),..., w Nocc- 1d(N - 1). Alternatively, assume that after the OCC application or OCC extension, N * Nocc symbol blocks y(0),..., y(N * Nocc - 1) are obtained. Then the column vector corresponding to the symbol block y(i * Nocc + k) = w k d(i), where i = 0,..., N - 1 and k = 0,..., Nocc - 1. After the OCC application or extension is completed, resource mapping is performed on the generated symbol blocks.

[0316] b. For OCC application or extension at the single time slot granularity:

[0317] a). The modulated complex modulation symbols are divided into multiple time slot blocks a(0),..., a(S - 1), and the complex modulation symbol blocks on each time slot are extended by the OCC sequence. In this embodiment, each time slot block corresponds to the complex modulation symbols on all subcarriers in a time slot. S is the number of time slot blocks before the OCC application or OCC extension. The s-th time slot block can be represented as a column vector a(s), which contains one or more complex modulation symbols, for example, represented as where M is the number of subcarriers, a(s) represents the complex modulation symbols on all subcarriers of all time-domain symbols in a time slot block, that is, a(s) consists of Nsymb1 d(n)'s, and Nsymb1 represents the number of time-domain symbols used to carry complex modulation symbols in a time slot. The OCC sequence w may be represented as a row vector w, for example, w = [w 0 ,..., w Nocc-1. Then the OCC application or OCC extension process may be expressed as a(s)*w. For example, a(s)*w = [w 0 a(s),,...,w Nocc-1 a(s)]. That is, a time slot block a(s) is extended to Nocc time slot blocks w 0 a(s),...,w Nocc-1 a(s). After the OCC application or OCC extension, S time slot blocks d(0),...,d(S-1) may be transformed into S*Nocc time slot blocks:

[0318] w 0 a(0),...,w Nocc-1 a(0),w 0 a(1),...,w Nocc- 1a(1),...,w 0 a(S-1),...,w Nocc-1 a(S-1). Alternatively, assume that after the OCC application or OCC extension, N*Nocc time slot blocks y(0),...,y(S*Nocc-1) are obtained. Then the column vector y(i*Nocc+k) corresponding to the time slot block = w k a(i), where i = 0,...,S-1 and k = 0,...,Nocc-1. After completing the OCC application or extension, resource mapping is performed on the generated symbol block.

[0319] b), or, the above a) can also be described as follows:

[0320] The modulated complex modulation symbols are divided into multiple time slot blocks d(0),...,d(N-1). The complex modulation symbols on each time slot block are extended by the OCC sequence. In this embodiment, each time slot block corresponds to the complex modulation symbols on all subcarriers in one time slot. N is the number of time slot blocks before the OCC application or OCC extension. The nth time slot block can be expressed as a column vector d(n), which contains one or more complex modulation symbols. For example, it is expressed as d(n) = [d 0 (n),...,d M-1 (n)] T , where M is the number of subcarriers * the number of time domain symbols carrying complex modulation symbols in a time slot, and d(n) represents the complex modulation symbols on all subcarriers in one time slot. The OCC sequence w may be expressed as a row vector w. For example, w = [w 0 ,...,w Nocc-1 . Then the OCC application or OCC extension process may be expressed as d(n)*w. For example, d(n)*w = [w 0 d(n),...,w Nocc-1 d(n)]. That is, a time slot block d(n) is extended to Nocc time slot blocks w0 d(n),...,w Nocc-1 d(n). After OCC application or OCC extension, the N time slot blocks d(0),..., d(N - 1) may be transformed into N * Nocc time slot blocks:

[0321] w 0 d(0),...,w Nocc-1 d(0),w 0 d(1),...,w Nocc-1 d(1),...,w 0 d(N - 1),...,w Nocc-1 d(N - 1). Alternatively, assume that after OCC application or OCC extension, N * Nocc time slot blocks y(0),..., y(N * Nocc - 1) are obtained. Then the column vector corresponding to the time slot block y(i * Nocc + k) = w k d(i), where i = 0,..., N - 1 and k = 0,..., Nocc - 1. After completing OCC application or extension, resource mapping is performed on the generated symbol blocks.

[0322] c. For OCC application or extension at the granularity of a single repetition unit or two consecutive time slots:

[0323] a). The complex modulated symbols after modulation are divided into multiple repetition unit blocks or multiple consecutive time slot blocks b(0),..., b(O - 1). Here, taking multiple consecutive time slots as two consecutive time slots as an example for illustration, the complex modulated symbol blocks on each repetition unit or two consecutive time slots are extended by the OCC sequence. O is the number of time slot blocks before OCC application or OCC extension. The o-th time slot block can be represented as a column vector b(o), which contains one or more complex modulated symbols, for example, represented as where M is the number of subcarriers, and b(o) represents the complex modulated symbols on all subcarriers of all time domain symbols on one repetition unit or two consecutive time slots. That is, b(o) is composed of Nsymb2 d(n)'s, and Nsymb2 represents the number of time domain symbols used to carry complex modulated symbols on one repetition unit or two consecutive time slots. The OCC sequence w may be represented as a row vector w, for example, w = [w 0 ,...,w Nocc-1 . Then the OCC application or OCC extension process may be represented as b(o) * w. For example, b(o) * w = [w 0 b(o),,...,w Nocc-1 b(o)]. That is, one repetition unit or two consecutive time slot block b(o) is extended to Nocc repetition units or two consecutive time slot blocks w 0 b(o),...,w Nocc-1b(o). After OCC application or OCC extension, O time slot blocks b(0),..., b(O-1) may be transformed into O*Nocc repeating units or two consecutive time slot blocks w 0 b(0),..., w Nocc-1 b(0), w 0 b(1),..., w Nocc-1 b(1),..., w 0 b(S-1),..., w Nocc-1 b(S-1). Alternatively, assume that after OCC application or OCC extension, O*Nocc repeating units or two consecutive time slot blocks y(0),..., y(O*Nocc-1) are obtained. Then the column vector corresponding to the repeating unit or time slot block is y(i*Nocc + k) = w k b(i), where i = 0,..., O-1 and k = 0,..., Nocc-1. After completing OCC application or extension, resource mapping is performed on the generated symbol block.

[0324] b), or, the above a) can also be described as follows:

[0325] The modulated complex modulation symbols are divided into multiple two-consecutive time slot blocks d(0),..., d(N-1). The complex modulation symbols on each consecutive time slot block are extended by the OCC sequence. N is the number of consecutive time slot blocks before OCC application or OCC extension. The nth consecutive time slot block can be represented as the column vector d(n), which contains one or more complex modulation symbols, for example, represented as d(n) = [d 0 (n),..., d M-1 (n)] T , where M is the number of subcarriers * the number of time domain symbols carrying complex modulation symbols within a continuous time slot or M is the number of subcarriers * the number of time domain symbols carrying complex modulation symbols within a time slot * the number of continuous time slots. d(n) represents the complex modulation symbols on all subcarriers in a continuous time slot. The OCC sequence w may be represented as a row vector w, for example, w = [w 0 ,..., w Nocc-1 . Then the OCC application or OCC extension process may be represented as d(n)*w, for example, d(n)*w = [w 0 d(n),..., w Nocc-1 d(n)]. That is, a continuous time slot block d(n) is extended to Nocc continuous time slot blocks w 0 d(n),..., w Nocc-1 d(n). After OCC application or OCC extension, N consecutive time slot blocks d(0),..., d(N-1) may be transformed into N*Nocc consecutive time slot blocks w 0 d(0),..., w Nocc-1d(0), w 0 d(1),..., w Nocc-1 d(1),..., w 0 d(N - 1),..., w Nocc-1 d(N - 1). Or, assume that after the OCC application or OCC extension, N * Nocc consecutive time slot blocks y(0),..., y(N * Nocc - 1) are obtained, then the column vector corresponding to the consecutive time slot blocks y(i * Nocc + k) = w k d(i), where i = 0,..., N - 1, k = 0,..., Nocc - 1. After completing the OCC application or extension, resource mapping is performed on the generated symbol blocks.

[0326] 6), The above defines multiple OCC application or extension schemes. When using a certain OCC application or extension scheme, at least one of the following conditions needs to be met:

[0327] a. The OCC enable indication (the first indication) indicates that the OCC function is enabled or the OCC enable indication is configured;;

[0328] b. The OCC activation indication (the second indication) indicates the activation of OCC;

[0329] c. The OCC length indication (the third indication) indicates a specific OCC length;

[0330] d. The OCC length is determined to be a specific OCC length according to an indication (such as the first indication or the second indication);

[0331] e. The OCC index indication (the fourth indication) indicates a specific OCC index;

[0332] f. When the subcarrier spacing is configured to 15 kHz, where the subcarrier spacing is indicated by a high - layer parameter or by the uplink subcarrier spacing in the random access response grant;

[0333] g. When the subcarrier spacing is configured to 3.75 kHz, where the subcarrier spacing is indicated by a high - layer parameter or by the uplink subcarrier spacing in the random access response grant;

[0334] h. When the number of consecutive subcarriers is configured to 1, where the number of subcarriers is indicated by the subcarrier indication field in the DCI scheduling the PUSCH;

[0335] i. When the number of consecutive subcarriers is configured to multiple carriers, where the number of subcarriers is indicated by the subcarrier indication field in the DCI scheduling the PUSCH.

[0336] 7) The following describes the actual repetition count, scrambling, repeated mapping, and the determination method of RV after OCC application or OCC extension. In this embodiment, the data after OCC extension includes the second PUSCH codeword.

[0337] a. In the current protocol, it is stipulated that each first PUSCH codeword can be mapped to one or more resource units, where N RU represents the number of resource units, and every N RU resource units are transmitted times, where N RU is indicated by the resource allocation field in the DCI that schedules the PUSCH, and is indicated by the repetition count field of the DCI that schedules the PUSCH, represents the repetition count of the n RU resource units mapped by the first PUSCH codeword before OCC extension. When applying OCC, the following method should be used for enhancement:

[0338] a). The scrambling sequence of the first PUSCH codeword will be re-initialized every OCC length times or times or max(OCC length, times) of repeated transmission, applicable to single-carrier transmission or multi-carrier transmission;

[0339] b. The second PUSCH codeword can be mapped to one or more resource units, and the number of resource units N RU,enh is extended by the OCC length. For example, N RU,enh is equal to N RU * OCC length; every N RU,enh resource units are transmitted times, where length;

[0340] ⅰ. For single-tone transmission, its physical resource mapping method is the same as the existing protocol, that is, is equal to 1;

[0341] ⅱ. For multi-tone transmission, the related to the physical resource mapping method is equal to 1 or is equal to length or

[0342] 1. After mapping to N ；:<7； time slots, before continuing to map the next time slot of z(·), N ；:<7； time slots should be repeated times,

[0343] is equal to 1; or,

[0343] 2. After mapping to OCC length * N；:<7； After the time slot, before continuing to map the next time slot of z(·), the OCC length * N should be repeated ；:<7； time slot times, equal to the length or the length.

[0344] c), and in the existing protocol, for each transmission time slot, the RV is updated once. When applying OCC, the following method should be used to enhance the relevant calculations:

[0345] ⅰ. Among them, related to For multi-tone transmission, or

[0346] 1. Transmissions are carried out in N time slots in the NB-IoT uplink. These time slots are represented by n i , where i = 0, 1,..., N - 1. For the PUSCH transmission corresponding to the jth TB (i.e., the second PUSCH codeword), it is transmitted in B consecutive NB-IoT uplink time slots n i , i = jB + b, b = 0, 1,..., B - 1, where the redundancy version rv idx (j) associated with this TB is determined as follows: rv idx (j) = 2 * mod(rv enh + j, 2), where if then L = 1. The part of the second PUSCH codeword associated with rv idx (j) will be mapped to the RU,enh th time slot among the N resource units (RUs) allocated for transmission. When the subcarrier spacing is Δf = 3.75 kHz, in the NB-IoT uplink time slots associated with the TB, the time slot mapping method is When the subcarrier spacing is Δf = 15 kHz, in the NB-IoT UL slots associated with the TB, the slot mapping method is where rv enh is indicated by the redundancy version field in the DCI or default set to start from 0 or 2. And / or,

[0347] 2. Transmissions are carried out in N time slots in the NB-IoT uplink. These time slots are represented by n idenotes, where i = 0, 1,..., N-1. For the PUSCH transmission corresponding to the j-th TB (i.e., the second PUSCH codeword), it is transmitted in B consecutive NB-IoT uplink time slots n i , i = jB + b, b = 0, 1,..., B-1, where the redundancy version rv idx (j) associated with this TB is determined as follows: rv idx (j) = 2 * mod(rv enh + j, 2), where, if then L = 1, otherwise the part of the second PUSCH codeword associated with rv idx (j) will be mapped to the RU,enh th time slot among the allocated N resource units (RUs) for transmission. When the subcarrier spacing is Δf = 3.75 kHz, in the NB-IoT uplink time slots associated with the TB, the time slot mapping method is When the subcarrier spacing is Δf = 15 kHz, in the NB-IoT UL slots associated with the TB, the slot mapping method is where rv enh is indicated by the redundancy version field in the DCI or is default set to start from 0 or 2.

[0348] b, the current repetition number is determined by the repetition number field in the DCI scheduling the PUSCH. However, after OCC expansion, for the repetition number indicated by the DCI, the determination of the repetition number can consider one of the following methods:

[0349] a), Expand the repetition number indicated by the DCI. For example, when the repetition number indicated by the DCI is 8, after expansion with an OCC length of 2, the actual repetition number is expanded to 16, and the corresponding physical resource mapping method remains unchanged.

[0350] Example 3: DMRS Position Determination

[0351] In this example, the information after OCC expansion includes the DMRS sequence or the expanded DMRS sequence.

[0352] In traditional behavior, users do not support time-division multiplexing and code-division multiplexing. DMRS is transmitted on DMRS symbols in each time slot in time-frequency resources (that is, one user occupies all DMRS symbols in all time slots in one transmission). The length of its DMRS sequence is determined by the repetition number, the number of time slots included in the uplink resource unit, and the number of uplink resource units, that is

[0353] When configuring different subcarrier spacings or different numbers of consecutive subcarriers, the DMRS multiplexing scheme may be different. The DMRS multiplexing scheme may include: time-division multiplexing DMRS scheme, code-division multiplexing DMRS scheme, frequency-domain code-division multiplexing DMRS scheme.

[0354] Time-division multiplexing DMRS: The length of the DMRS sequence is calculated as follows: The length, that is, the length of the DMRS sequence is scaled by the OCC length. The DMRS sequence is generated according to the method defined in the existing protocol. Each terminal uses DMRS symbols in different time slots to transmit DMRS. The terminal only occupies DMRS symbols in some time slots for DMRS transmission, such as the method defined in 8).

[0355] Time-domain code-division multiplexing DMRS: The length of the DMRS sequence is calculated as follows: The length, that is, the length of the DMRS sequence is scaled by the OCC length. After the DMRS sequence is generated according to the method defined in the existing protocol, each DMRS sequence element is extended by the OCC. Each terminal uses DMRS symbols in the same time slot to transmit DMRS. The terminal occupies all DMRS symbols in all time slots in one transmission for DMRS transmission.

[0356] Frequency-domain code-division multiplexing DMRS: The frequency-domain length of the DMRS sequence is determined by the number of consecutive subcarriers The DMRS sequence is determined by the base sequence and cyclic shift. Each terminal uses DMRS symbols in the same time slot to transmit DMRS. The terminal occupies all DMRS symbols in all time slots in one transmission for DMRS transmission. The cyclic shift used by each terminal is related to the OCC index or OCC sequence. For example, OCC index 0 corresponds to cyclic shift index 0 or cyclic shift value m, OCC index 1 corresponds to cyclic shift index 1 or cyclic shift value n, and vice versa; or OCC sequence [1 1] corresponds to cyclic shift index 0 or cyclic shift value m, OCC sequence [1 -1] corresponds to cyclic shift index 1 or cyclic shift value n.

[0357] 8). For time-division multiplexing DMRS, support TDM DMRS based on time-slot group transmission / mapping (DMRS is only transmitted on DMRS symbols in time slots, and the data information transmitted on non-DMRS symbols is, for example, PUSCH data):

[0358] a. The transmission or mapping of the DMRS of each terminal on the DMRS symbols in which time slot subgroup of each time slot group is determined by the OCC index and the number of time slot subgroups. For example, the time slot subgroup index = mod(OCC index, the number of time slot subgroups within each time slot group);

[0359] b. Or the DMRS of the terminal with OCC index 0 is transmitted on the DMRS symbols in time slot subgroup 1 of each time slot group; the DMRS of the terminal with OCC index 1 is transmitted on the DMRS symbols in time slot subgroup 2 of each time slot group, and vice versa. Or the DMRS of the terminal with OCC index 0 is transmitted on the DMRS symbols in the first 2 time slots of each time slot group; the DMRS of the terminal with OCC index 1 is transmitted on the DMRS symbols in the last 2 time slots of each time slot group, where each time slot group contains 4 consecutive time slots, and vice versa:

[0360] a). Each time slot group may contain n * OCC length time slots, n can be predefined or related to the subcarrier spacing. For example, n can be 2 (in this case each time slot group contains 4 consecutive time slots), and n is not equal to 1;

[0361] b. Each time slot group contains Y time slot subgroups, Y can be predefined or equal to the OCC length;

[0362] c. Each time slot subgroup may contain one or n consecutive time slots:

[0363] ⅰ. Figure 7 is a schematic diagram of the transmission / mapping / multiplexing of the DMRS sequence provided by an embodiment. As Figure 7 shown, assuming a transmission contains N time slot groups, for 2-user multiplexing, the orthogonal coverage code indices of terminals 1 and 2 are 0 and 1 respectively. The time slot subgroup of the DMRS of terminal 1 in each time slot group is determined by the OCC index and the number of time slot subgroups, that is, the time slot subgroup index = mod(OCC index, the number of time slot subgroups within each time slot group) = mod(0, 2) = 0, that is, the DMRS of terminal 1 is transmitted in time slot subgroup 1 of each time slot group. Similarly, the DMRS of terminal 2 is transmitted in time slot subgroup 2 of each time slot group, while the DMRS of terminal 1 in time slot subgroup 2 of each time slot group is omitted or discarded, and the DMRS of terminal 2 in time slot subgroup 1 of each time slot group is omitted or discarded. Among them, the DMRS only occupies one or more DMRS symbols in each time slot of the time slot subgroup, and this DMRS symbol is generally standard predefined.

[0364] Figure 8 is a schematic diagram after the time slot expansion of the transmission / mapping / multiplexing of the DMRS sequence provided by an embodiment. After the time slot expansion, the DMRS transmission / mapping / multiplexing of 2 users based on the time slot group is as Figure 8As shown, the shaded symbol is the symbol where the DMRS is located. Figure 8 The DMRS of User 1 in Figure 7 is the DMRS of Terminal 1, and the DMRS of User 2 is Figure 7 the DMRS of Terminal 2 in

[0365] c. When at least one of the following conditions is satisfied, at least one of the solutions defined in Embodiment 3 above is adopted:

[0366] a). The OCC enabling indication (the first indication) indicates that the OCC function is enabled or the OCC enabling indication is configured;

[0367] b). The OCC activation indication (the second indication) indicates the activation of the OCC;

[0368] c). The OCC length indication (the third indication) indicates a specific OCC length;

[0369] d). The OCC length is determined to be a specific OCC length according to an indication (such as the first indication or the second indication);

[0370] e). The OCC index indication (the fourth indication) indicates a specific OCC index;

[0371] f). When the subcarrier spacing is configured to 15 kHz, where the subcarrier spacing is indicated by a higher layer parameter or the uplink subcarrier spacing in the random access response grant;

[0372] g). When the subcarrier spacing is configured to 3.75 kHz, where the subcarrier spacing is indicated by a higher layer parameter or the uplink subcarrier spacing in the random access response grant;

[0373] h). When the number of consecutive subcarriers is configured to 1, where the number of subcarriers is indicated by the subcarrier indication field in the DCI scheduling the PUSCH;

[0374] i). When the number of consecutive subcarriers is configured to multiple carriers, where the number of subcarriers is indicated by the subcarrier indication field in the DCI scheduling the PUSCH.

[0375] Embodiment 4: Transmission gap causes OCC delay

[0376] This embodiment mainly describes that when the information after OCC extension is delayed, the delay is based on the OCC group or the delay time, where the delay time is an integer multiple of the OCC alignment length, and the OCC alignment length is the duration of the OCC group.

[0377] When mapping resources, in order to avoid resource collisions or provide synchronization opportunities, some transmission delay mechanisms may be introduced.

[0378] For example, in the uplink transmission of NB-IoT, the following latency mechanisms exist:

[0379] 1. When mapping NPUSCH resources, if the time unit group for resource mapping (e.g., the N slots time slots as described in the standard protocol) overlaps or partially overlaps with the NPRACH time resources, the corresponding transmission on this time unit group is delayed until the next time unit group that does not overlap with the NPRACH time resources;

[0380] 2. In Frequency Division Duplex (FDD) or frame structure 1, every 256 ms of NPUSCH transmission (including the latency caused by NPRACH), a 40-ms uplink gap is inserted and the corresponding NPUSCH transmission is delayed. Moreover, in the latency caused by NPRACH, the part that overlaps with the uplink gap is counted into the uplink gap.

[0381] 3. In the IoT-NTN TDD mode, if NPUSCH or NPRACH overlaps with non-uplink transmission time, the corresponding NPUSCH or NPRACH transmission is delayed until the time resources in the next uplink transmission time.

[0382] To ensure the orthogonality of OCC, different UEs need to keep the OCC aligned. The OCC alignment may include:

[0383] 1. (Data) OCC group alignment. For example, when applying OCC in N time units (e.g., 2 consecutive time slots, time slots, symbols, sub-frames, etc.), these N time units can be called an OCC group. The (data) OCC groups of different UEs need to be aligned to ensure the OCC orthogonality. It should be noted that the (data) OCC group here is the data after the OCC extension in the foregoing embodiments;

[0384] 2. DMRS group alignment. For example:

[0385] ⅰ. When using code-division multiplexed DMRS, the DMRS groups of different UEs need to be aligned to ensure the DMRS orthogonality. For example, N time slots may be regarded as a time slot group, and an N-length OCC code is applied to the DMRS within the time slot group. At this time, the time slot groups of different UEs need to be aligned to ensure the orthogonality of the code-division DMRS;

[0386] ⅱ. When time-division multiplexing DMRS is adopted, the DMRS groups of different UEs need to be aligned to ensure the orthogonality of DMRS. As shown in Embodiment 3, for example, N time slots may be used as a time slot group, which is further divided into Y time slot subgroups. Each UE may transmit DMRS on one of the subgroups and not transmit DMRS on other subgroups. At this time, the time slot groups of different UEs need to be aligned or there is a fixed time offset to ensure the orthogonality of time-division DMRS.

[0387] It should be noted that the DMRS group here is the DMRS sequence in the foregoing embodiment or the DMRS sequence after OCC extension.

[0388] It is worth noting that the alignment of the (data) OCC group and the alignment of the DMRS group may correspond to different time lengths. The OCC alignment may be based on the longest alignment length or the least common multiple of different alignment methods. For example, assume that symbol-based OCC (length of 2) is used for data transmission, and time-division DMRS (4 time slots as a group, and every 2 time slots as 1 subgroup) is used for DMRS transmission. Then the alignment length of the (data) OCC group is 2 symbols, and the alignment length of the DMRS group is 4 time slots. At this time, the system may need to consider the alignment based on 4 time slots as the benchmark.

[0389] The network side can simply ensure that the start time of the PUSCH transmission of the first UE is OCC-aligned with the PUSCH transmission of the second UE (the start times of the two may be different) through scheduling. However, if the above traditional PUSCH delay mechanism is used, the network side may not be able to ensure that different subsequent PUSCH transmissions always maintain OCC alignment. For example, assume that the subcarrier spacing is 3.75 kHz and time-division DMRS with 4 time slots as a group is used. Then the OCC alignment length that different UEs need to ensure is N slot,occ = 4 time slots, that is, 8 ms. Assume that the NPRACH length is 11.2 ms (corresponding to NPRACH format 0 repeated twice in FDD or frame structure 1), then the PUSCH overlapping with NPRACH needs to be delayed by at least 12 ms. Assume that the delay caused by the NPRACH of the first UE does not overlap with the uplink interval, and the delay caused by the NPRACH of the second UE overlaps with the uplink interval by 4 ms. Then the PUSCH of the first UE may be delayed by 12 ms, and the PUSCH of the second UE may be delayed by 12 ms + 40 ms - 4 ms = 48 ms. At this time, the delay difference between the two is 36 ms, which is not a multiple of 8 ms. This means that even if the first UE and the second UE were originally OCC-aligned, after the delay, subsequent PUSCH transmissions cannot maintain OCC alignment. Figure 9 It is a schematic diagram of the information delay after OCC extension provided by an embodiment. As Figure 9As shown, the PUSCH transmission of the first UE is delayed by 12 ms due to the NPRACH. The total delay of the PUSCH transmission of the second UE is 48 ms. This causes the PUSCH transmissions of the first UE and the second UE to no longer maintain OCC alignment.

[0390] To address the possible problems in the above delay mechanism, the present embodiment introduces the following new delay mechanism.

[0391] 9) When a delay occurs, it is necessary to perform the delay based on the OCC group (for example, changing the N slots time slots described in the standard protocol to N slot,occ time slots). In this way, the integrity of the OCC group or the DMRS group can be ensured. Among them, the OCC group (with a duration of N slot,occ time slots) may be the one with the larger duration among the (data) OCC group and the DMRS group. For example, for a 3.75 kHz subcarrier spacing, N slot,occ = 2 * OCC length ; for a 15 kHz subcarrier spacing, N slot,occ = OCC length or N slot,occ = N slots * OCC length .

[0392] Specifically, the delay may be performed according to the following process:

[0393] a. (When OCC is enabled or activated) For PUSCH transmission, if the mapped N slot,occ time slots contain resource elements that overlap or partially overlap with the NPRACH resources, the PUSCH transmission on these N slot,occ time slots is delayed until the next N slot,occ time slots that do not overlap with the NPRACH resources.

[0394] b. (When OCC is enabled or activated) For PUSCH transmission, if the mapped N slot,occ time slots contain resource elements that overlap or partially overlap with the uplink interval, the PUSCH transmission on these N slot,occ time slots is delayed until the next N slot,occ time slots that do not overlap with the uplink interval.

[0395] c. (When OCC is enabled or activated) For PUSCH transmission, if the mapped N slot,occ time slots contain resource elements that overlap or partially overlap with the non - uplink time, the PUSCH transmission on these N slot,occ time slots is delayed until the next N slot,occ time slots that do not overlap with the non - uplink time.

[0396] d. When OCC is enabled or activated, for PUSCH transmission, if the mapped N slot,occ time slots contain resource elements that overlap or partially overlap with NPRACH resources or uplink gaps, then the PUSCH transmission on these N slot,occ time slots is delayed until the next N slot,occ time slots that do not overlap with NPRACH resources or uplink gaps.

[0397] It should be noted that in 9), when the delay occurs, the minimum transmission unit for the delay transmission is N slot,occ time slots.

[0398] 10. After the delay occurs, the delay time needs to be an integer multiple of the OCC alignment length. The OCC alignment length is the duration of the OCC group. In this way, it can be ensured that the UEs can still maintain OCC alignment. Figure 10 It is a schematic diagram of the delay of another piece of information after OCC expansion provided by an embodiment. As Figure 10 shown, in order to ensure OCC alignment, the PUSCH transmission of the first UE is additionally delayed by 4 ms to ensure that the total delay is an integer multiple of the OCC alignment length (4 time slots, 8 ms). The total delay of the PUSCH transmission of the second UE is 48 ms, which is an integer multiple of the OCC alignment length. Therefore, after the delay, the PUSCH transmissions of the first UE and the second UE can maintain OCC alignment.

[0399] When specifically implemented, the delay may be carried out according to the following criteria:

[0400] a. The first time slot of the PUSCH transmission after the delay satisfies n s mod N slot,occ = X. Wherein, X may be predefined by the protocol (for example, predefined as 0), or indicated / configured by the network side, or determined according to the start time of the entire PUSCH, or determined according to the resources mapped before the delay. For example, X = n s,initial mod N slot,occ , where n s,initial is the first time slot of the entire PUSCH transmission. Or, X = n s,old mod N slot,occ , where n s,old is the first time slot mapped before the PUSCH transmission is delayed. The specific process may be as follows:

[0401] a). When OCC is enabled or activated, for PUSCH transmission, if the mapped N slot,occ time slots contain resource elements that overlap with NPRACH resources, then these Nslot,occ PUSCH transmissions on time slots are delayed until the next N time slots that do not overlap with NPRACH resources. slot,occ time slots and the first time slot satisfies ns mod N slot,occ =X.

[0402] b) (When OCC is enabled or activated) For PUSCH transmission, if the mapped N slot,occ If a time slot contains resource elements that overlap or partially overlap with the uplink interval, these N slot,occ PUSCH transmissions on time slots are delayed until the next N time slots that do not overlap with the uplink interval slot,occ time slots and the first time slot satisfies n s mod N slot,occ =X.

[0403] c) (When OCC is enabled or activated) For PUSCH transmission, if the mapped N slot,occ If a time slot contains resource elements that overlap or partially overlap with NPRACH resources or uplink intervals, then these N slot,occ PUSCH transmissions on timeslots N are delayed until the next N timeslots that do not overlap with NPRACH resources or uplink intervals slot,occ time slots and the first time slot satisfies n s mod N slot,occ =X.

[0404] b. N of delayed PUSCH transmission slot,occ The first time slot ns of the time slots is related to the N slot,occ The first time slot n of the s,old , satisfying (n s -n s,old )mod N slot,occ = 0. Where n s is the index of the first time slot after the delay, n s,old is the index of the first time slot before the delay. Furthermore, considering the impact of system frame wrapping, the impact of the radio frame number or superframe number may also need to be considered. For example:

[0405] a) N of delayed PUSCH transmission slot,occ The first time slot ns of the time slots is related to the N slot,occ The first time slot n of the s,old , need to meet ((SFN s -SFN s,old )*N slot,num +n s -n s,old )modN slot,occ= 0, where SFN s is the index of the radio frame or system frame in which the first time slot is located after the delay, SFN s,old is the index of the radio frame or system frame in which the first time slot is located before the delay, N slot,num is the number of time slots within a radio frame or system frame.

[0406] b), or, for the N slot,occ time slots of the PUSCH transmission after the delay, the first time slot n s and the first time slot n slot,occ in the N s,old time slots in which it was located before the delay need to satisfy ((H - SFN s - H - SFN s,old ) * N SFN,num * N slot,num + (SFN s - SFN s,old ) * N slot,num + n s - n s,old ) mod N slot,occ = 0, where H - SFN s is the index of the superframe in which the first time slot is located after the delay, H - SFN s,old is the index of the superframe in which the first time slot is located before the delay, N SFN,num is the number of radio frames within a superframe. H - SFN is the hyper SFN superframe, and a superframe contains 1024 radio frames or system frames.

[0407] 11), When at least one of the following conditions is met, the above - mentioned method is used to delay the PUSCH transmission:

[0408] a. The OCC enable indication (the first indication) indicates that the OCC function is enabled or the OCC enable indication is configured;

[0409] b. The OCC activation indication (the second indication) indicates the activation of the OCC;

[0410] c. The OCC length indication (the third indication) indicates that the OCC length is a valid value (e.g., the OCC length is 2, the OCC length is 4);

[0411] d. The OCC length is implicitly indicated as a valid value (e.g., the OCC length is 2, the OCC length is 4);

[0412] e. The OCC index indication (the fourth indication) indicates a specific OCC index;

[0413] f. When the sub - carrier spacing is configured to 15 kHz, where the sub - carrier spacing is indicated by a higher - layer parameter or the uplink sub - carrier spacing in the random access response grant;

[0414] g. When the subcarrier spacing is configured to 3.75 kHz, where the subcarrier spacing is indicated by a higher layer parameter or the uplink subcarrier spacing in the random access response grant;

[0415] h. When the number of consecutive subcarriers is configured to 1, where the number of subcarriers is indicated by the subcarrier indication field in the DCI scheduling the PUSCH;

[0416] i. When the number of consecutive subcarriers is configured to multiple carriers, where the number of subcarriers is indicated by the subcarrier indication field in the DCI scheduling the PUSCH.

[0417] Embodiment 3 can ensure that the delay is based on the OCC group and / or the delay is carried out according to the delay time, thereby ensuring the OCC orthogonality in the transmission process.

[0418] Figure 11 It is a schematic flow chart of an information receiving method provided by an embodiment. The information receiving method provided by this embodiment is applied to a second communication node. The second communication node in this embodiment can be an access network device. As Figure 11 shown, the information receiving method provided by this embodiment includes the following steps.

[0419] Step 1101: Send OCC configuration information to the first communication node.

[0420] The specific implementation manner of the OCC configuration information in this embodiment can refer to the foregoing embodiments and will not be elaborated here.

[0421] Step 1102: Receive the OCC-expanded information sent by the first communication node.

[0422] Among them, the OCC-expanded information is the information determined by the first communication node according to the OCC configuration information.

[0423] The process by which the first communication node determines the OCC-expanded information according to the OCC configuration information can refer to the foregoing embodiments and will not be elaborated here.

[0424] The information receiving method provided by this embodiment realizes the improvement of system capacity by sending OCC configuration information to the first communication node and receiving the OCC-expanded information sent by the first communication node, where the OCC-expanded information is the information determined by the first communication node according to the OCC configuration information.

[0425] The following introduces a method for uplink transmission.

[0426] Figure 12It is a schematic flowchart of a method for uplink transmission provided by an embodiment. This method for uplink transmission is applied to a first communication node. The first communication node in this embodiment can be an access network device or a terminal device. Correspondingly, the second communication node can be a terminal device or an access network device. As Figure 12 shown, the method for uplink transmission includes the following steps.

[0427] Step 1201: The first communication node determines the uplink channel configuration for carrying out uplink transmission.

[0428] Step 1202: The first communication node transmits the uplink channel for carrying out the uplink transmission.

[0429] In one embodiment, the uplink channel configuration includes at least one of the following: power information; time-domain resources; frequency-domain resources.

[0430] In one embodiment, the first communication node receives resource configuration information indicated by the second communication node through higher-layer information; or, the first communication node receives power control configuration information indicated by the second communication node through higher-layer information.

[0431] In one embodiment, the uplink transmission includes one of the following:

[0432] The first type of uplink transmission; wherein, the first type of uplink transmission includes one of the following: contention-based uplink data transmission, contention-based Msg3 transmission, or contention-based first-message transmission of the first type of random access;

[0433] The second type of uplink transmission; wherein, the second type of uplink transmission includes one of the following: the first message (preamble) of contention-based second type of random access, or contention-based first-message transmission of the first type of random access.

[0434] Among them, Msg3 is a message transmitted on the UL-SCH and contains a C-RNTI MAC CE or a CCCH SDU (core network identifier). Among them, Msg3 is also used for DTCH multiplexing of UP-EDT. As part of the random access procedure, Msg3 is submitted from the upper layer and is associated with UE contention resolution identity.

[0435] In one embodiment, the higher-layer information includes one of the following: common information (such as system message SIB); RRC release message; handover configuration information.

[0436] In one embodiment, the resource configuration information includes one of the following: a set of time-domain resources; a set of frequency-domain resources; the number of copies supported by one transmission; the number of repetitions of one transmission; the maximum number of retransmissions allowed for one transmission.

[0437] In one embodiment, the power control configuration information includes one of the following: the initial target received power of the transmission; the target received power of the transmission; the power boost value of the transmission; the nominal transmit power of the transmission; the configured transmit power of the transmission.

[0438] In one embodiment, the parameter of the transmit power of the uplink channel for carrying the first type of uplink transmission is determined by at least one of the following parameters: the first type of uplink transmission power control configuration information, the number of retransmissions of the first type of uplink transmission, the second type of uplink transmission power control configuration information.

[0439] In one embodiment, the target received power of the uplink channel for carrying the first type of uplink transmission is determined by one of the following parameters: the initial target received power of the channel, the number of retransmissions.

[0440] In one embodiment, the final transmit power of the uplink channel for carrying the first type of uplink transmission is determined by one of the following parameters: the number of retransmissions, the power boost value of the transmission.

[0441] In one embodiment, the target received power of the uplink channel for carrying the first type of uplink transmission is determined by one of the following parameters: the number of retransmissions, the initial target received power of the second type of transmission.

[0442] In one embodiment, when one of the following conditions is met, the first transmission node switches the first type of uplink transmission to the second type of uplink transmission: when the number of times of the first type of uplink transmission is greater than the allowed maximum number of retransmissions; or, when the number of times of the first type of uplink transmission is equal to the allowed maximum number of retransmissions, but it is determined as a transmission failure.

[0443] In one embodiment, the parameter of the transmit power of the uplink channel for carrying the second type of uplink transmission is determined by at least one of the following parameters: the second type of uplink transmission power control configuration information; the number of retransmissions of the first type of uplink transmission.

[0444] In one embodiment, when one of the following conditions is met, the first transmission node sends multiple copies for one transmission: when the number of copies supported by one transmission indicated by the second communication node is greater than 1; or, when the second communication node sends enabling information.

[0445] In one embodiment, when the first transmission node sends multiple copies for one transmission, the uplink transmission channel resources carrying each copy are randomly selected by the first communication node from the resource set.

[0446] In one embodiment, when the first transmission node sends multiple copies for one transmission, the determination of the number of repetitions supported by each copy includes one of the following methods: the second communication node configures through higher layer signaling; the number of repetitions of each copy is determined by the number of copies supported by one transmission and the number of repetitions of one transmission; or, the number of repetitions of each copy is the same as the number of repetitions of one transmission.

[0447] The following specific embodiment illustrates the above process.

[0448] Embodiment 5: A method for uplink transmission

[0449] In a communication system, when a terminal (such as a UE, IoT device) is in, for example, the RRC idle state or performing transmission during initial access, a method for uplink transmission is defined. Figure 13 It is a signaling interaction schematic diagram of the uplink transmission method provided by an embodiment. As Figure 13 shown, the method for uplink transmission includes the following steps: The terminal receives high-layer signaling from the base station; the terminal performs uplink transmission. For example, contention-based Msg-3 or contention-based NPUSCH / PUSCH.

[0450] In some embodiments, the terminal receives high-layer signaling from the base station, which at least includes one of the following: public information (such as system message SIB); RRC release message; handover configuration information.

[0451] Obtain the resource configuration information required for the uplink channel to perform transmission, where the resource configuration information at least includes one of the following:

[0452] a. The time-domain or frequency-domain resource position used by the uplink channel for carrying the transmission (such as the first type of transmission); In some embodiments, the base station can configure more than one time-domain or frequency-domain resource position (i.e., the resource position occupied by the uplink channel), such as configuring the resource set available for the uplink channel transmission through a set or a list, where any content in the set or list represents a piece of resource information:

[0453] a). For example, a frequency-domain resource bitmap, subcarrier or PRB resource information represents a frequency-domain resource for transmission;

[0454] b). For example, time-domain symbols, time slots, subframe information, or resource start position and length, etc.) represent a time-domain resource.

[0455] b. The number of replicas (N) supported by a transmission.

[0456] a). Among them, in some embodiments, a replica of a transmission refers to the transmission performed for the transmission after resource selection in the configured resources (resource pool) by the uplink channel carrying the transmission.

[0457] b). Among them, in some embodiments, the terminal can randomly select resources (time-domain or frequency-domain resources) for one or more replica transmissions from the configured multiple resources. Figure 14Schematic diagram of transmission resources corresponding to two copies of a transmission provided by an embodiment. As Figure 14 shown.

[0458] Among them, in some embodiments, the base station allows (enables or configures) the terminal to perform multiple-copy transmissions through one of the following solutions.

[0459] Solution 1: When the number of copies supported by a transmission is configured to be greater than 1 (e.g., N is a number greater than one).

[0460] Solution 2: When the number of copies supported by a transmission is configured (e.g., N is a number greater than or equal to one); at this time, when N = 1, it means that the terminal can only perform one-copy transmission.

[0461] Solution 3: When indicated by high-layer information, such as enabling signaling:

[0462] ⅰ. In some embodiments, the enabling signaling is multi-copy transmission enabling signaling;

[0463] ⅱ. In some embodiments, the enabling signaling is type-I transmission enabling signaling.

[0464] Among them, type-I transmission includes one of the following:

[0465] ⅰ). Contention-based uplink data transmission (such as PUSCH, NPUSCH);

[0466] ⅱ). Contention-based Msg3 transmission;

[0467] ⅲ). Contention-based first-message (Msg-A) transmission of the first type of random access.

[0468] c. The number of repetitions (M, M is a number greater than or equal to 1) of a transmission. Among them, in some embodiments, the repetition of a transmission refers to the number of repetitions included in the uplink channel carrying the transmission.

[0469] Among them, in some embodiments, when the base station allows (enables or configures) the terminal to send multiple copies for a transmission, the number of repetitions supported by each copy is:

[0470] Solution 1: Parameters configured by the base station through high-layer signaling, such as each configured number of repetitions is configured to be L;

[0471] Solution 2: The number of repetitions supported by the nth copy is determined by M and N, such as M / N. In some cases, when M / N cannot be evenly divided, the number of repetitions of one of them (such as the first or the Nth) copy is M - ceil(M / N) * (N - 1);

[0472] Solution 3: The number of repetitions supported by the nth copy is M.Figure 15 is a schematic diagram of two copies of a transmission provided by an embodiment. As Figure 15 shown, the repetition times M of each copy is 3;

[0473] d. The maximum number of retransmissions (C) allowed for a transmission.

[0474] Among them, in some embodiments, the retransmission of a transmission refers to the re - sending of the channel carrying the transmission.

[0475] In some embodiments, the maximum number of retransmissions allowed for a transmission refers to the number of times the terminal re - sends for this transmission:

[0476] a). Among them, in some embodiments, the terminal re - sending for a transmission includes that after the terminal does not receive the response information (such as scheduling information, etc.) for this re - transmission from the base station under a predetermined condition (such as within a time window), the terminal re - transmits for this transmission;

[0477] b). Among them, in some embodiments, when the base station allows (enables or configures) the terminal to send multiple copies for a transmission, the maximum number of retransmissions allowed for this transmission is:

[0478] Solution 1: The maximum number of retransmissions allowed for a transmission (C);

[0479] Solution 2: Determined by C and N, such as ceil(C / N).

[0480] Among them, Figure 16 is a schematic diagram of performing a second - type uplink transmission when the first - type uplink transmission reaches the maximum number of retransmissions and the transmission fails. In some embodiments (such as Figure 16 shown), when the terminal's transmission fails, such as when the number of times of the first - type uplink transmission is equal to the maximum number of retransmissions allowed, but still fails (such as not meeting the predetermined conditions), the terminal will switch to the second - type transmission, as Figure 16 shown, where the second - type transmission includes: the first message (preamble) of contention - based second - type random access; the transmission of the first message (Msg - A) of contention - based first - type random access.

[0481] In some embodiments, the terminal receives from the base station's higher - layer signaling, including at least one of the following: public information (such as system message SIB), RRC release message, handover configuration information.

[0482] Obtain the power control configuration information required for uplink channel transmission, where the power control configuration information includes at least one of the following: the initial target receiving power of the transmission; the target receiving power of the transmission; the power boost value of the transmission; the nominal transmission power of the transmission, such as p0-CB-Msg3; the configured transmission power of the transmission, such as p0-nominal-CB-Msg3.

[0483] For example, in some embodiments, at least one parameter for determining the transmission power of the uplink channel carrying the uplink transmission (such as the first type of transmission) is determined by the received uplink transmission (such as the first type of transmission) power control configuration information and the number of retransmissions of the uplink transmission (such as the first type of transmission):

[0484] a), When determining the transmission power of the PUSCH of the uplink channel carrying the contention-based Msg3, the target receiving power of the contention-based Msg3 is determined by the initial target receiving power of the contention-based Msg3, the number of retransmissions of the contention-based Msg3, and the power boost value of the contention-based Msg3. For example: the target receiving power of the contention-based Msg3 = the initial target receiving power of the contention-based Msg3 + (the number of retransmissions of the contention-based Msg3 - 1) * the power boost value of the contention-based Msg3;

[0485] b), When determining the transmission power of the PUSCH / NPUSCH of the uplink channel carrying the contention-based Msg3, the nominal transmission power of this channel (such as P O_NOMpN·G , p0-CB-Msg3) is determined by one of the following methods:

[0486] Solution 1: It is determined by the target receiving power of the contention-based Msg3, the number of retransmissions of the contention-based Msg3, and the power boost value of the contention-based Msg3. For example:

[0487] P O_NOMpN·G = the target receiving power of the contention-based Msg3 + (the number of retransmissions of the contention-based Msg3 - 1) * the power boost value of the contention-based Msg3;

[0488] Solution 2: It is determined by the initial target receiving power of the contention-based Msg3, the number of retransmissions of the contention-based Msg3, and the power boost value of the contention-based Msg3. For example:

[0489] P O_NOMpN·G = the initial target receiving power of the contention-based Msg3 + (the number of retransmissions of the contention-based Msg3 - 1) * the power boost value of the contention-based Msg3;

[0490] Solution 3: It is determined by the target receiving power of the contention-based Msg3. For example:

[0491] PO_NOMpN·G = Target receiving power of contention-based Msg3.

[0492] c), When determining the transmission power of the uplink channel PUSCH / NPUSCH carrying contention-based Msg3, the final transmission power of this channel (such as P CB-Msg3 ) is determined by one of the following parameters: the number of retransmissions of contention-based Msg3, the transmission power boost value of contention-based Msg3, and the final transmission power of the initial transmission.

[0493] In some embodiments, at least one parameter for determining the transmission power of the uplink channel carrying the uplink transmission (such as the first type of transmission) is determined by the received uplink transmission (such as the second type of transmission) power control configuration information and the number of retransmissions of the uplink transmission (such as the first type of transmission):

[0494] a), When determining the transmission power of the uplink channel (PUSCH of the uplink channel of contention-based Msg3) carrying the first type of transmission, the target receiving power of contention-based Msg3 is determined by the initial target receiving power of the second type of transmission (such as the first message of random access, that is, preamble), the number of retransmissions of contention-based Msg3, and the transmission power boost value of contention-based Msg3. For example:

[0495] Target receiving power of contention-based Msg3 = Initial target receiving power of preamble + (Number of retransmissions of contention-based Msg3 - 1) * Transmission power boost value of contention-based Msg3;

[0496] b), When determining the transmission power of the uplink channel (PUSCH of the uplink channel of contention-based Msg3) carrying the first type of transmission, the target receiving power of contention-based Msg3 is determined by the initial target receiving power of the second type of transmission (such as the first message of random access, that is, preamble), the number of retransmissions of contention-based Msg3, and the transmission power boost value of the second type of transmission (such as the first message of random access, that is, preamble). For example:

[0497] Target receiving power of contention-based Msg3 = Initial target receiving power of preamble + (Number of retransmissions of contention-based Msg3 - 1) * Transmission power boost value of preamble.

[0498] In some embodiments, when the terminal switches the transmission from the first type of transmission to the second type of transmission, at least one parameter for determining the transmission power of the uplink channel carrying the uplink transmission (such as the second type of transmission) is determined by the received uplink transmission (such as the second type of transmission) power control configuration information and / or the number of retransmissions of the uplink transmission (such as the first type of transmission):

[0499] a) When determining the transmission power of the second type of transmission (such as the first message of random access, i.e., preamble), the target reception power of the second type of transmission (such as the first message of random access, i.e., preamble) is determined by the initial target reception power of the second type of transmission (such as the first message of random access, i.e., preamble), the retransmission times of the first type of transmission (such as contention-based Msg3), and the uplift value of the second type of transmission (such as the first message of random access, i.e., preamble);

[0500] b) When determining the transmission power of the second type of transmission (such as the data channel in Msg-A, which is the first message of random access), its transmission power is equal to that of the first type of transmission (such as contention-based Msg3);

[0501] c) When determining the transmission power of the second type of transmission (such as the data channel in Msg-A, which is the first message of random access), its transmission power is determined by the retransmission times of the first type of transmission (such as contention-based Msg3).

[0502] In some embodiments, the configuration of parameters (such as power control parameters) can be independently configured for each coverage enhancement level.

[0503] In some embodiments, when multiple transmission failures occur, the terminal can perform transmissions according to higher coverage level parameters. At this time, in some embodiments, when the terminal switches to different coverage levels for transmission, retransmission-related parameters, such as the retransmission counter and the power accumulation value, are set to zero. In some embodiments, some retransmission-related parameters can be inherited, such as the power accumulation value.

[0504] Embodiment 6: Use RRC and / or DCI signaling to indicate OCC parameters, including one or more of OCC enable / disable, OCC length, and OCC sequence (e.g., sequence index)

[0505] In an embodiment of the present application, uplink transmission includes at least one of the following: multiple repetitions of Physical Uplink Shared Channel (PUSCH) transmission scheduled by DCI; multiple repetitions of Physical Uplink Shared Channel (PUSCH) transmission scheduled by at least one of a Random Access Response (RAR) message or a fallback RAR message; multiple repetitions of PUSCH transmission in a random access procedure; multiple repetitions of configured grant PUSCH transmission; multiple repetitions of PUSCH transmission in Pre-configured Uplink Resources (PUR); multiple repetitions of PUSCH transmission in Early Data Transmission (EDT).

[0506] Exemplarily, multiple repetitions of PUSCH transmission scheduled by an RAR message may be that RAR (msg2) schedules msg3 in a 4-step Random Access Channel (RACH) procedure. Another example is that multiple repetitions of PUSCH transmission scheduled by a fallback RAR message may be that the fallback RAR (msgB) schedules msg3 in a 2-step RACH procedure.

[0507] Exemplarily, multiple repetitions of uplink physical shared channel transmission scheduled by DCI may include multiple repetitions of PUSCH transmission scheduled by DCI formats 0_0, 0_1, 0_2, 0_3. Multiple repetitions of configured grant PUSCH transmission may include multiple repetitions of CG PUSCH Type 1 and CG PUSCH Type 2.

[0508] In some embodiments, the physical uplink shared channel may include at least one of the following: Narrow Band Internet of Things Physical Uplink Shared Channel (NPUSCH), Enhanced Mobile Broadband Physical Uplink Shared Channel (eMBB PUSCH), Ultra-Reliable and Low-Latency Communications Physical Uplink Shared Channel (uRLLC PUSCH), Massive Machine Type Communications Physical Uplink Shared Channel (mMTC PUSCH).

[0509] Code division multiplexing is performed on the UEs, that is, a corresponding code sequence (such as an OCC) is added to the signals repeatedly transmitted by the UEs (such as PUSCH and PUCCH), and then the transmission signals of multiple UEs are transmitted on the same time-frequency resources. At the receiving end, the transmission signals of each UE can be obtained through operations such as interference cancellation, OCC combination, and decoding.

[0510] In this disclosure, the code sequence may include an OCC (orthogonal cover code) sequence, a NOMA (non-orthogonal multiple access) sequence, and so on. The OCC sequence may be based at least on a DFT sequence, a walsh sequence, a ZC sequence, a Hadamard sequence, and so on.

[0511] The code sequences considered in the above solutions can be applied to one or more time slots, that is, one or more time slots multiplied by an OCC codeword. For example, the time granularity is one time slot. Figure 17 It is a schematic diagram of the slot-based OCC application provided by an embodiment. As Figure 17 shown, assuming there are two UEs and a 4-length OCC sequence is used, and the sequence is [S i,1 , S i,2 , S i,3 , S i,4 , where i is the user number. The data in each time slot is repeatedly mapped four times continuously to 4 time slots, and each time slot is multiplied by an OCC codeword.

[0512] Code division multiplexing

[0513] That is, a corresponding code sequence (such as an orthogonal cover code (OCC) sequence) is added to the signals (such as PUSCH, PUCCH) repeated by the UE, and then the transmission signals of multiple UEs are transmitted on the same time-frequency resources. At the receiving end, the transmission signals of each UE can be obtained through operations such as interference cancellation, OCC merging, and decoding.

[0514] The code sequence can be applied to one or more time slots, that is, one or more time slots are multiplied by an OCC codeword. For example, the time granularity is one time slot, as Figure 2 shown. Suppose there are two UEs (UE1 and UE2), using a 4-length OCC sequence, and the sequence is [Si,1,Si,2,Si,3,Si,4], where i is the user number. The data in each time slot is repeatedly mapped to 4 time slots continuously, and each time slot is multiplied by an OCC codeword.

[0515] PUSCH group (or OCC group)

[0516] The PUSCH transmission can include one or more PUSCH groups (also called PUSCH repetition unit groups), where each group contains M PUSCH repetition units in the PUSCH, where M is the code sequence length (such as the OCC length), which can be expressed as the number of elements in the used code sequence, or can be understood as the maximum number of multiplexed users supported under this code sequence. Each PUSCH group in the PUSCH is defined in chronological order. For example, the first PUSCH group of the PUSCH contains the earliest M PUSCH repetition units in the PUSCH, the second PUSCH group of the PUSCH contains the M PUSCH repetition units after the first PUSCH group, and so on, which will not be elaborated below. The number of repetition units of the PUSCH sent by the UE can be greater than the code sequence length. For example, the UE can send 16 repetitions, and the code sequence length of the UE is 4, then the 16 repetition units can be divided into 4 PUSCH groups. Within each or more groups, it is necessary to ensure that the content of each repetition is exactly the same before the code sequence can be merged.

[0517] The OCC signaling configuration should balance dynamism and signaling overhead. The basic principle is to minimize or avoid adding new bits in DCI. However, the OCC parameters should be as dynamic as possible. One or more of the following schemes can be combined for use. In some embodiments, for the PUSCH and CG PUSCH Type 2 scheduled by DCI, the OCC signaling indication adopts the same one of the following schemes. In some embodiments, for the PUSCH scheduled by DCI, the OCC signaling indication adopts one of the following schemes, while for CG PUSCH Type 2, the OCC signaling indication adopts another one of the following schemes. In some embodiments, the following schemes apply to the case where transform precoding is enabled, that is, they apply to the uplink PUSCH transmission using the DFT-s-OFDM waveform.

[0518] In the following schemes, Condition A will be mentioned, which is defined as:

[0519] Condition A is that both dmrs-UplinkTransformPrecoding and tp-pi2BPSK are configured and π / 2-BPSK modulation is used.

[0520] Scheme 1: Configure the OCC length in RRC. Implicitly determine whether OCC is enabled based on the OCC length (for example, determine whether the UE decodes DCI in the way that OCC is enabled. The same understanding applies in the subsequent schemes and will not be elaborated further). Implicitly indicate the OCC sequence through the antenna port field in DCI.

[0521] Configuration of the OCC length and whether OCC is enabled in RRC:

[0522] In some embodiments, a new parameter can be defined in RRC, such as occ-length, which can be configured in PUSCH-Config or PUSCH-TimeDomainResourceAllocation or PUSCH-Allocation. 1 bit can be used. '0' corresponds to an OCC length of 2, and '1' corresponds to an OCC length of 4. In some embodiments, if this parameter is configured, it indicates that OCC is enabled. Similarly, if this parameter is configured, it can also indicate that the UE can decode DCI in the way that OCC is enabled. If this parameter is not configured, it indicates that OCC is not enabled or the UE decodes DCI in the existing way (i.e., the way without OCC function).

[0523] In some embodiments, a new parameter, such as occ-length, can be defined in RRC. It can be configured in PUSCH-Config or PUSCH-TimeDomainResourceAllocation or PUSCH-Allocation, and 2 bits can be used. '00' corresponds to an OCC length of 1, '01' corresponds to an OCC length of 2, '10' corresponds to an OCC length of 4, and '11' is a reserved code position. In some embodiments, if this parameter is configured with an OCC length of 2 or 4, it indicates that OCC is enabled. Similarly, if this parameter is configured with an OCC length of 2 or 4, it can also indicate that the UE can decode DCI in the way that OCC is enabled. If this parameter is not configured or is configured and is 1, it indicates that OCC is not enabled or the UE decodes DCI in the existing way (i.e., the way without OCC function).

[0524] Configuration of the OCC sequence in DCI:

[0525] When OCC is implicitly indicated to be enabled in RRC, the OCC sequence can be implicitly indicated through the antenna port field in DCI.

[0526] In some embodiments, without modifying the existing antenna port table, the OCC sequence index is repeatedly mapped to the values of the antenna port field in ascending order until the non-reserved values in the antenna port field are used up. For example, when the OCC length is 2, the OCC sequence index [0,1] is repeated twice to get [0,1,0,1], which is mapped to the values [0,1,2,3] in Table 7.3.1.1.2-6. Another example, when the OCC length is 4, the OCC sequence index [0,1,2,3] is mapped to the values [0,1,2,3] in Table 7.3.1.1.2-6. Another example, when the OCC length is 4, the OCC sequence index [0,1,2,3] is repeated three times to get [0,1,2,3,0,1,2,3,0,1,2,3], which is mapped to the non-reserved values [0,1,2,3,4,5,6,7,8,9,10,11] in Table 7.3.1.1.2-7.

[0527] In some embodiments, without modifying the existing antenna port table, the OCC sequence index can be obtained according to the value of the antenna port field. For example, OCC sequence index = mod (value of the antenna port field, OCC length).

[0528] In some embodiments, without modifying the existing antenna port table, the OCC sequence index is obtained according to the DMRS port. For example, OCC sequence index = mod(DMRS port, OCC length). For another example, when condition A is satisfied, OCC sequence index = mod(DMRS port, OCC length). For another example, when condition A is not satisfied, OCC sequence index = mod(DMRS port + n SCID , OCC length).

[0529] In some embodiments, the mapping relationship between the OCC sequence index and the antenna port (or DMRS port) index can be represented in the form of a table.

[0530] In some embodiments, when the OCC length is 2, the maximum number of DMRS symbols on the current carrier is 1 (i.e., maxLength = 1), and condition A is not satisfied, the antenna port field is 2 bits, and the following table is used.

[0531] Table 7.3.1.1.2-6-1

[0532] Value Number of CDM Groups without Data DMRS Port OCC Sequence Index 0 2 0 0 1 2 1 1 2 2 2 0 3 2 3 1

[0533] In some embodiments, when the OCC length is 2, the maximum number of DMRS symbols on the current carrier is 1 (i.e., maxLength = 1), and condition A is satisfied, the antenna port field is 2 bits, and the following table is used.

[0534] Table 7.3.1.1.2-6A-1

[0535] Value Number of CDM Groups without Data DMRS Port OCC Sequence Index 0 2 <![CDATA[0,n SCID = 0]]> 0 1 2 <![CDATA[0,n SCID = 1]]> 1 2 2 <![CDATA[2,n SCID = 0]]> 0 3 2 <![CDATA[2,n SCID = 1]]> 1

[0536] In some embodiments, when the OCC length is 2, the maximum number of DMRS symbols on the current carrier is 2 (i.e., maxLength = 2), and condition A is not satisfied, the antenna port field is 4 bits, and the following table is used.

[0537] Table 7.3.1.1.2-7-1

[0538] Value Number of CDM Groups without Data DMRS Port Number of Preamble Symbols OCC Sequence Index 0 2 0 1 0 1 2 1 1 1 2 2 2 1 0 3 2 3 1 1 4 2 0 2 0 5 2 1 2 1 6 2 2 2 0 7 2 3 2 1 8 2 4 2 0 9 2 5 2 1 10 2 6 2 0 11 2 7 2 1 12-15 Reserved Reserved Reserved

[0539] In some embodiments, when the OCC length is 2, the maximum number of DMRS symbols on the current carrier is 2 (i.e., maxLength = 2), and condition A is satisfied, the antenna port field is 4 bits, and the following Table 7.3.1.1.2-7A-1 is used.

[0540] Table 7.3.1.1.2-7A-1

[0541] Value Number of CDM Groups without Data DMRS Port Number of Preamble Symbols OCC Sequence Index 0 2 <![CDATA[0,n SCID = 0]]> 1 0 1 2 <![CDATA[0,n SCID = 1]]> 1 1 2 2 <![CDATA[2,n SCID = 0]]> 1 0 3 2 <![CDATA[2,n SCID = 1]]> 1 1 4 2 <![CDATA[0,n SCID =0]]> 2 0 5 2 <![CDATA[0,n SCID = 1]]> 2 1 6 2 <![CDATA[2,n SCID = 0]]> 2 0 7 2 <![CDATA[2,n SCID = 1]]> 2 1 8 2 <![CDATA[4,n SCID = 0]]> 2 0 9 2 <![CDATA[4,n SCID = 1]]> 2 1 10 2 <![CDATA[6,n SCID =0]]> 2 0 11 2 <![CDATA[6,n SCID = 1]]> 2 1 12-15 Reserved Reserved Reserved

[0542] In some embodiments, when the OCC length is 4, the maximum number of current DMRS symbols is 1 (i.e., maxLength = 1), and condition A is not satisfied, the antenna port field is 2 bits, and the following table is used.

[0543] Table 7.3.1.1.2-6-2

[0544]

[0545]

[0546] In some embodiments, when the OCC length is 4, the maximum number of current DMRS symbols is 1 (i.e., maxLength = 1), and condition A is satisfied, the antenna port field is 2 bits, and the following table is used.

[0547] Table 7.3.1.1.2-6A-2

[0548] Value Number of CDM Groups without Data DMRS Port OCC Sequence Index 0 2 <![CDATA[0,n SCID = 0]]> 0 1 2 <![CDATA[0,n SCID = 1]]> 1 2 2 <![CDATA[2,n SCID = 0]]> 2 3 2 <![CDATA[2,n SCID = 1]]> 3

[0549] In some embodiments, when the OCC length is 4, the maximum number of current DMRS symbols is 2 (i.e., maxLength = 2), and condition A is not satisfied, the antenna port field is 4 bits, and the following table is used.

[0550] Table 7.3.1.1.2-7-2

[0551] Value Number of CDM Groups without Data DMRS Port Number of Preamble Symbols OCC Sequence Index 0 2 0 1 0 1 2 1 1 1 2 2 2 1 2 3 2 3 1 3 4 2 0 2 0 5 2 1 2 1 6 2 2 2 2 7 2 3 2 3 8 2 4 2 0 9 2 5 2 1 10 2 6 2 2 11 2 7 2 3 12-15 Reserved Reserved Reserved

[0552] In some embodiments, when the OCC length is 4, the maximum number of current DMRS symbols is 2 (i.e., maxLength = 2), and condition A is satisfied, the antenna port field is 4 bits, and the following table is used.

[0553] Table 7.3.1.1.2-7A-2

[0554]

[0555] Solution 2: Configure a maximum OCC length in RRC, implicitly determine whether OCC is enabled through the maximum OCC length, and implicitly indicate the OCC sequence and OCC length in DCI through the antenna port field.

[0556] Configuration of the maximum OCC length and whether OCC is enabled in RRC:

[0557] In some embodiments, a new parameter can be defined in RRC, such as occ-maxLength, which can be configured in PUSCH-Config or PUSCH-TimeDomainResourceAllocation or PUSCH-Allocation. 1 bit can be used, where '0' corresponds to a maximum OCC length of 2 and '1' corresponds to a maximum OCC length of 4. In some embodiments, if this parameter is configured, it indicates that OCC is enabled, that is, if this parameter is configured, it can also indicate that the UE can decode DCI in the OCC-enabled manner. If this parameter is not configured, it indicates that OCC is not enabled or the UE decodes DCI in the existing manner (i.e., the manner without the OCC function).

[0558] In some embodiments, a new parameter can be defined in RRC, such as occ-maxLength, which can be configured in PUSCH-Config or PUSCH-TimeDomainResourceAllocation or PUSCH-Allocation. 2 bits can be used, where '00' corresponds to a maximum OCC length of 1, '01' corresponds to a maximum OCC length of 2, '10' corresponds to a maximum OCC length of 4, and '11' is a reserved code position. In some embodiments, if this parameter is configured with a maximum OCC length of 2 or 4, it indicates that OCC is enabled. Similarly, if this parameter is configured with a maximum OCC length of 2 or 4, it can also indicate that the UE can decode DCI in the OCC-enabled manner. If this parameter is not configured or is configured and is 1, it indicates that OCC is not enabled or the UE decodes DCI in the existing manner (i.e., the manner without the OCC function).

[0559] Configuration of the OCC length and OCC sequence in DCI:

[0560] When OCC is enabled, the OCC sequence can be implicitly indicated in DCI through the antenna port field. In some embodiments, the mapping relationship between the OCC sequence index, OCC length, and antenna port (or DMRS port) index can be represented in tabular form. The design idea here is to design corresponding tables for different maximum OCC lengths, and corresponding available OCC lengths and OCC sequences can be selected within the maximum OCC length.

[0561] In some embodiments, when the maximum OCC length is 2, and the maximum number of DMRS symbols in the current carrier is 1 (i.e., maxLength = 1), and condition A is not met, the antenna port field is 2 bits, and the following table is used.

[0562] Table 7.3.1.1.2-6-1

[0563] Value Number of CDM Groups without Data DMRS Port OCC Sequence Index OCC Length 0 2 0 0 2 1 2 1 1 2 2 2 2 0 2 3 2 3 1 2

[0564] In some embodiments, when the maximum OCC length is 2, and the maximum number of current-carrier DMRS symbols is 1 (i.e., maxLength = 1), and condition A is satisfied, the antenna port field is 2 bits, and the following table is used.

[0565] Table 7.3.1.1.2-6A-1

[0566] Value Number of CDM Groups without Data DMRS Port OCC Sequence Index OCC Length 0 2 <![CDATA[0,n SCID = 0]]> 0 2 1 2 <![CDATA[0,n SCID = 1]]> 1 2 2 2 <![CDATA[2,n SCID = 0]]> 0 2 3 2 <![CDATA[2,n SCID = 1]]> 1 2

[0567] In some embodiments, when the maximum OCC length is 2, and the maximum number of current-carrier DMRS symbols is 2 (i.e., maxLength = 2), and condition A is not satisfied, the antenna port field is 4 bits, and the following table is used.

[0568] Table 7.3.1.1.2-7-1

[0569] Value Number of CDM Groups without Data DMRS Port Number of Preamble Symbols OCC Sequence Index OCC Length 0 2 0 1 0 2 1 2 1 1 1 2 2 2 2 1 0 2 3 2 3 1 1 2 4 2 0 2 0 2 5 2 1 2 1 2 6 2 2 2 0 2 7 2 3 2 1 2 8 2 4 2 0 2 9 2 5 2 1 2 10 2 6 2 0 2 11 2 7 2 1 2 12-15 Reserved Reserved Reserved

[0570] In some embodiments, when the maximum OCC length is 2, and the maximum number of current-carrier DMRS symbols is 2 (i.e., maxLength = 2), and condition A is satisfied, the antenna port field is 4 bits, and the following table is used.

[0571] Table 7.3.1.1.2-7A-1

[0572] Value Number of CDM Groups without Data DMRS Port Number of Preamble Symbols OCC Sequence Index OCC Length 0 2 <![CDATA[0,n SCID =0]]> 1 0 2 1 2 <![CDATA[0,n SCID =1]]> 1 1 2 2 2 <![CDATA[2,n SCID = 0]]> 1 0 2 3 2 <![CDATA[2,n SCID = 1]]> 1 1 2 4 2 <![CDATA[0,n SCID = 0]]> 2 0 2 5 2 <![CDATA[0,n SCID =1]]> 2 1 2 6 2 <![CDATA[2,n SCID = 0]]> 2 0 2 7 2 <![CDATA[2,n SCID = 1]]> 2 1 2 8 2 <![CDATA[4,n SCID =0]]> 2 0 2 9 2 <![CDATA[4,n SCID = 1]]> 2 1 2 10 2 <![CDATA[6,n SCID =0]]> 2 0 2 11 2 <![CDATA[6,n SCID = 1]]> 2 1 2 12-15 Reserved Reserved Reserved

[0573] In some embodiments, when the maximum OCC length is 4, and the maximum number of current-carrier DMRS symbols is 1 (i.e., maxLength = 1), and condition A is not satisfied, the antenna port field is 3 bits (1 bit more than when not using OCC), and the following table is used.

[0574] Table 7.3.1.1.2-6-2

[0575] Value Number of CDM Groups without Data DMRS Port OCC Sequence Index OCC Length 0 2 0 0 2 1 2 1 1 2 2 2 2 0 2 3 2 3 1 2 4 2 0 0 4 5 2 1 1 4 6 2 2 2 4 7 2 3 3 4

[0576] In some embodiments, when the maximum OCC length is 4, and the maximum number of current-carrier DMRS symbols is 1 (i.e., maxLength = 1), and condition A is satisfied, the antenna port field is 3 bits (1 bit more than when not using OCC), and the following table is used.

[0577] Table 7.3.1.1.2-6A-2

[0578] Value Number of CDM Groups without Data DMRS Port OCC Sequence Index OCC Length 0 2 <![CDATA[0,n SCID =0]]> 0 2 1 2 <![CDATA[0,n SCID = 1]]> 1 2 2 2 <![CDATA[2,n SCID = 0]]> 0 2 3 2 <![CDATA[2,n SCID = 1]]> 1 2 4 2 <![CDATA[0,n SCID = 0]]> 0 4 5 2 <![CDATA[0,n SCID = 1]]> 1 4 6 2 <![CDATA[2,n SCID = 0]]> 2 4 7 2 <![CDATA[2,n SCID = 1]]> 3 4

[0579] In some embodiments, when the maximum OCC length is 4, and the maximum number of current DMRS symbols is 2 (i.e., maxLength = 2), and condition A is not satisfied, the antenna port field is 4 bits, and the following table is used.

[0580] Table 7.3.1.1.2-7-2

[0581] Value Number of CDM Groups without Data DMRS Port Number of Preamble Symbols OCC Sequence Index OCC Length 0 2 0 1 0 2 1 2 1 1 1 2 2 2 2 1 0 2 3 2 3 1 1 2 4 2 0 1 0 4 5 2 1 1 1 4 6 2 2 1 2 4 7 2 3 1 3 4 8 2 0 2 0 4 9 2 1 2 1 4 10 2 2 2 2 4 11 2 3 2 3 4 12-15 Reserved Reserved Reserved

[0582] In some embodiments, when the maximum OCC length is 4, and the maximum number of current DMRS symbols is 2 (i.e., maxLength = 2), and condition A is satisfied, the antenna port field is 4 bits, and the following table is used.

[0583] Table 7.3.1.1.2-7A-2

[0584]

[0585] Solution 3: Configure the candidate OCC length in RRC, implicitly determine whether OCC is enabled through the candidate OCC length, and implicitly indicate the OCC sequence and OCC length in the DCI through the antenna port field.

[0586] Configuration of candidate OCC length and whether OCC is enabled in RRC:

[0587] In some embodiments, a new parameter can be defined in RRC, such as occ-candidateLength, which can be configured in PUSCH-Config or PUSCH-TimeDomainResourceAllocation or PUSCH-Allocation. 2 bits can be used, where '00' corresponds to OCC length 1, '01' corresponds to OCC length 2, '10' corresponds to OCC length 4, and '11' corresponds to OCC lengths 2 and 4. In some embodiments, if this parameter is configured, it indicates that OCC is enabled, that is, if this parameter is configured, it can also indicate that the UE can decode the DCI in the way that OCC is enabled. If this parameter is not configured, it indicates that OCC is not enabled or the UE decodes the DCI in the existing way (i.e., the way without the OCC function).

[0588] In some embodiments, a new parameter may be defined in RRC, such as occ-candidateLength, which can be configured in PUSCH-Config or PUSCH-TimeDomainResourceAllocation or PUSCH-Allocation. 2 bits can be used, where '00' corresponds to an OCC length of 1, '01' corresponds to an OCC length of 2, '10' corresponds to an OCC length of 4, and '11' corresponds to OCC lengths of 2 and 4. In some embodiments, if this parameter does not indicate an OCC length of 1, it means OCC is enabled, and it can also mean that the UE can decode DCI in the way that OCC is enabled. If this parameter is not configured or is configured and is 1, it means OCC is not enabled or the UE decodes DCI in the existing way (i.e., the way without the OCC function).

[0589] Configuration of OCC length and OCC sequence in DCI:

[0590] When OCC is enabled, the OCC sequence can be implicitly indicated in the DCI through the antenna port field. In some embodiments, the mapping relationship between the OCC sequence index, OCC length, and antenna port (or DMRS port) index can be represented in the form of a table. The design idea here is to design a corresponding table for different candidate OCC lengths. If there is more than one candidate OCC length, the corresponding OCC length and OCC sequence need to be selected in the antenna port table.

[0591] In some embodiments, when the candidate OCC length is 2, the maximum number of DMRS symbols on the current carrier is 1 (i.e., maxLength = 1), and condition A is not met, the antenna port field is 2 bits, and Table 7.3.1.1.2-6-1 in Solution 1 is used.

[0592] In some embodiments, when the candidate OCC length is 2, the maximum number of DMRS symbols on the current carrier is 1 (i.e., maxLength = 1), and condition A is not met, the antenna port field is 2 bits, and Table 7.3.1.1.2-6A-1 in Solution 1 is used.

[0593] In some embodiments, when the candidate OCC length is 2, the maximum number of DMRS symbols on the current carrier is 2 (i.e., maxLength = 2), and condition A is not met, the antenna port field is 4 bits, and Table 7.3.1.1.2-7-1 in Solution 1 is used.

[0594] In some embodiments, when the candidate OCC length is 2, and the maximum number of current DMRS symbols is 2 (i.e., maxLength = 2), and condition A is satisfied, the antenna port field is 4 bits, and Table 7.3.1.1.2-7A-1 in Solution 1 is used.

[0595] In some embodiments, when the candidate OCC length is 4, and the maximum number of current DMRS symbols is 1 (i.e., maxLength = 1), and condition A is not satisfied, the antenna port field is 2 bits, and Table 7.3.1.1.2-6-2 in Solution 1 is used.

[0596] In some embodiments, when the candidate OCC length is 4, and the maximum number of current DMRS symbols is 1 (i.e., maxLength = 1), and condition A is satisfied, the antenna port field is 2 bits, and Table 7.3.1.1.2-6A-2 in Solution 1 is used.

[0597] In some embodiments, when the candidate OCC length is 4, and the maximum number of current DMRS symbols is 2 (i.e., maxLength = 2), and condition A is not satisfied, the antenna port field is 4 bits, and Table 7.3.1.1.2-7-2 in Solution 1 is used.

[0598] In some embodiments, when the candidate OCC length is 4, and the maximum number of current DMRS symbols is 2 (i.e., maxLength = 2), and condition A is satisfied, the antenna port field is 4 bits, and Table 7.3.1.1.2-7A-2 in Solution 1 is used.

[0599] In some embodiments, when the candidate OCC length is 2 and 4, and the maximum number of current DMRS symbols is 1 (i.e., maxLength = 1), and condition A is not satisfied, the antenna port field is 3 bits, and Table 7.3.1.1.2-6-2 in Solution 2 is used.

[0600] In some embodiments, when the candidate OCC length is 2 and 4, and the maximum number of current DMRS symbols is 1 (i.e., maxLength = 1), and condition A is satisfied, the antenna port field is 3 bits, and Table 7.3.1.1.2-6A-2 in Solution 2 is used.

[0601] In some embodiments, when the candidate OCC length is 2 and 4, and the maximum number of current DMRS symbols is 2 (i.e., maxLength = 2), and condition A is not satisfied, the antenna port field is 4 bits, and Table 7.3.1.1.2-7-2 in Solution 2 is used.

[0602] In some embodiments, when the candidate OCC length is 2 and 4, the maximum number of current DMRS symbols is 2 (i.e., maxLength = 2), and condition A is satisfied, the antenna port field is 4 bits, and Table 7.3.1.1.2-7A-2 in Solution 2 is used.

[0603] Solution 4: Configure a maximum OCC length in RRC to implicitly determine whether OCC is enabled. In DCI, implicitly indicate the OCC sequence, OCC length, and OCC enable / disable (or activate / deactivate) through the antenna port field.

[0604] Configuration of the maximum OCC length and whether OCC is enabled in RRC: The same as in Solution 2, which will not be elaborated here.

[0605] Configuration of the OCC length, OCC sequence, and OCC disable in DCI:

[0606] When it is implicitly determined in RRC that OCC is enabled, the OCC sequence, OCC length, and OCC disable can be implicitly indicated through the antenna port field in DCI. In some embodiments, the mapping relationship between the OCC sequence index, OCC length, OCC disable, and antenna port (or DMRS port) index can be represented in the form of a table.

[0607] In some embodiments, when the maximum OCC length is 2, the maximum number of current DMRS symbols is 1 (i.e., maxLength = 1), and condition A is not satisfied, the antenna port field is 2 bits, and the following table is used, where when the OCC length indication is 1, it means OCC is disabled.

[0608] Table 7.3.1.1.2-6-1

[0609] Value Number of CDM Groups without Data DMRS Port OCC Sequence Index OCC Length 0 2 0 0 2 1 2 1 1 2 2 2 2 - 1 3 2 3 - 1

[0610] In some embodiments, when the maximum OCC length is 2, the maximum number of current DMRS symbols is 1 (i.e., maxLength = 1), and condition A is satisfied, the antenna port field is 2 bits, and the following table is used, where when the OCC length indication is 1, it means OCC is disabled.

[0611] Table 7.3.1.1.2-6A-1

[0612] Value Number of CDM Groups without Data DMRS Port OCC Sequence Index OCC Length 0 2 0, nSCID = 0 0 2 1 2 0, nSCID = 1 1 2 2 2 2, nSCID = 0 - 1 3 2 2, nSCID = 1 - 1

[0613] In some embodiments, when the maximum OCC length is 2, and the maximum number of current-carrier DMRS symbols is 2 (i.e., maxLength = 2), and condition A is not satisfied, the antenna port field is 4 bits, and the following table is used, where when the OCC length indication is 1, it means that OCC is disabled.

[0614] Table 7.3.1.1.2-7-1

[0615]

[0616] In some embodiments, when the maximum OCC length is 2, and the maximum number of current-carrier DMRS symbols is 2 (i.e., maxLength = 2), and condition A is satisfied, the antenna port field is 4 bits, and the following table is used, where when the OCC length indication is 1, it means that OCC is disabled.

[0617] Table 7.3.1.1.2-7A-1

[0618]

[0619] In some embodiments, when the maximum OCC length is 4, and the maximum number of current-carrier DMRS symbols is 1 (i.e., maxLength = 1), and condition A is not satisfied, the antenna port field is 3 bits (1 bit more than when not using OCC), and the following table is used, where when the OCC length indication is 1, it means that OCC is disabled.

[0620] Table 7.3.1.1.2-6-2

[0621] Value Number of CDM Groups without Data DMRS Port OCC Sequence Index OCC Length 0 2 0 0 2 1 2 1 1 2 2 2 2 - 1 3 2 3 - 1 4 2 0 0 4 5 2 1 1 4 6 2 2 2 4 7 2 3 3 4

[0622] In some embodiments, when the maximum OCC length is 4, and the maximum number of current-carrier DMRS symbols is 1 (i.e., maxLength = 1), and condition A is satisfied, the antenna port field is 3 bits (1 bit more than when not using OCC), and the following table is used, where when the OCC length indication is 1, it means that OCC is disabled.

[0623] Table 7.3.1.1.2-6A-2

[0624] Value Number of CDM Groups without Data DMRS Port OCC Sequence Index OCC Length 0 2 0, nSCID = 0 0 2 1 2 0, nSCID = 1 - 1 2 2 2, nSCID = 0 0 2 3 2 2, nSCID = 1 - 1 4 2 0, nSCID = 0 0 4 5 2 0, nSCID = 1 1 4 6 2 2, nSCID = 0 2 4 7 2 2, nSCID = 1 3 4

[0625] In some embodiments, when the maximum OCC length is 4, and the maximum number of current-carrier DMRS symbols is 2 (i.e., maxLength = 2), and condition A is not satisfied, the antenna port field is 4 bits, and the following table is used, where when the OCC length indication is 1, it means that OCC is disabled.

[0626] Table 7.3.1.1.2-7-2

[0627]

[0628] In some embodiments, when the maximum OCC length is 4, and the maximum number of current DMRS symbols is 2 (i.e., maxLength = 2), and condition A is satisfied, the antenna port field is 4 bits. The following table is used, where when the OCC length indication is 1, it means that OCC is disabled.

[0629] Table 7.3.1.1.2-7A-2

[0630]

[0631] Solution 5: Configure candidate OCC lengths in RRC, implicitly determine whether OCC is enabled through the candidate OCC lengths, and implicitly indicate the OCC sequence, OCC length, and OCC enable / disable (or activate / deactivate) in DCI through the antenna port field.

[0632] Configuration of candidate OCC lengths and whether OCC is enabled in RRC: The same as Solution 3.

[0633] Configuration of OCC length and OCC sequence in DCI:

[0634] When it is implicitly determined in RRC that OCC is enabled, the OCC sequence, OCC length, and OCC disable can be implicitly indicated in DCI through the antenna port field. In some embodiments, the mapping relationship between the OCC sequence index, OCC length, OCC disable, and antenna port (or DMRS port) index can be represented in the form of a table.

[0635] In some embodiments, when the candidate OCC length is 2, and the maximum number of current DMRS symbols is 1 (i.e., maxLength = 1), and condition A is not satisfied, the antenna port field is 2 bits, and Table 7.3.1.1.2-6-1 in Solution 4 is used.

[0636] In some embodiments, when the candidate OCC length is 2, and the maximum number of current DMRS symbols is 1 (i.e., maxLength = 1), and condition A is not satisfied, the antenna port field is 2 bits, and Table 7.3.1.1.2-6A-1 in Solution 4 is used.

[0637] In some embodiments, when the candidate OCC length is 2, and the maximum number of current DMRS symbols is 2 (i.e., maxLength = 2), and condition A is not satisfied, the antenna port field is 4 bits, and Table 7.3.1.1.2-7-1 in Solution 4 is used.

[0638] In some embodiments, when the candidate OCC length is 2, and the maximum number of current DMRS symbols is 2 (i.e., maxLength = 2), and condition A is satisfied, the antenna port field is 4 bits, and Table 7.3.1.1.2-7A-1 in Solution 4 is used.

[0639] In some embodiments, when the candidate OCC lengths are 2 and 4, and the maximum number of current DMRS symbols is 1 (i.e., maxLength = 1), and condition A is not satisfied, the antenna port field is 3 bits, and Table 7.3.1.1.2-6-2 in Solution 4 is used.

[0641] In some embodiments, when the candidate OCC lengths are 2 and 4, and the maximum number of current DMRS symbols is 1 (i.e., maxLength = 1), and condition A is satisfied, the antenna port field is 3 bits, and Table 7.3.1.1.2-6A-2 in Solution 4 is used.

[0643] In some embodiments, when the candidate OCC lengths are 2 and 4, and the maximum number of current DMRS symbols is 2 (i.e., maxLength = 2), and condition A is not satisfied, the antenna port field is 4 bits, and Table 7.3.1.1.2-7-2 in Solution 4 is used.

[0645] In some embodiments, when the candidate OCC lengths are 2 and 4, and the maximum number of current DMRS symbols is 2 (i.e., maxLength = 2), and condition A is satisfied, the antenna port field is 4 bits, and Table 7.3.1.1.2-7A-2 in Solution 4 is used.

[0647] Solution 6: In RRC, a new parameter is used to explicitly indicate whether OCC is enabled, and in DCI, the OCC sequence and OCC length are implicitly indicated through the antenna port field.

[0648] Configuration of OCC length and whether OCC is enabled in RRC:

[0649] In some embodiments, a new parameter can be defined in RRC, such as occ-enabler, which can be configured in PUSCH-Config or PUSCH-TimeDomainResourceAllocation or PUSCH-Allocation. 1 bit can be used, where '0' corresponds to OCC enabled and '1' corresponds to OCC not enabled. It can also be configured such that when the parameter is present, it indicates OCC enabled, and when not configured, it indicates OCC not enabled.

[0650] Configuration of OCC sequence in DCI:

[0651] When the occ-enabler is configured in RRC or the occ-enabler indicates that OCC is enabled, the OCC sequence and OCC length can be implicitly indicated through the antenna port field in the DCI. In some embodiments, the mapping relationship between the OCC sequence index, the OCC length, and the antenna port (or DMRS port) index can be represented in the form of a table.

[0652] a. When the UE reports UE capability OCC-2 but does not report UE capability OCC-4, it indicates that the maximum OCC length that can be supported is 2.

[0653] In some embodiments, when the maximum number of current-carrier DMRS symbols is 1 (i.e., maxLength = 1) and condition A is not satisfied, the antenna port field is 2 bits, and Table 7.3.1.1.2-6-1 in Solution 2 is used.

[0654] In some embodiments, when the maximum number of current-carrier DMRS symbols is 1 (i.e., maxLength = 1) and condition A is not satisfied, the antenna port field is 2 bits, and Table 7.3.1.1.2-6A-1 in Solution 2 is used.

[0655] In some embodiments, when the maximum number of current-carrier DMRS symbols is 2 (i.e., maxLength = 2) and condition A is not satisfied, the antenna port field is 4 bits, and Table 7.3.1.1.2-7-1 in Solution 2 is used.

[0656] In some embodiments, when the maximum number of current-carrier DMRS symbols is 2 (i.e., maxLength = 2) and condition A is satisfied, the antenna port field is 4 bits, and Table 7.3.1.1.2-7A-1 in Solution 2 is used.

[0657] b. When the UE reports UE capability OCC-4, it indicates that the maximum OCC length that can be supported is 4.

[0658] In some embodiments, when the maximum number of current-carrier DMRS symbols is 1 (i.e., maxLength = 1) and condition A is not satisfied, the antenna port field is 3 bits, and Table 7.3.1.1.2-6-2 in Solution 2 is used.

[0659] In some embodiments, when the maximum number of current-carrier DMRS symbols is 1 (i.e., maxLength = 1) and condition A is satisfied, the antenna port field is 3 bits, and Table 7.3.1.1.2-6A-2 in Solution 2 is used.

[0660] In some embodiments, when the maximum number of current DMRS symbols is 2 (i.e., maxLength = 2) and condition A is not satisfied, the antenna port field is 4 bits, and Table 7.3.1.1.2-7-2 in Solution 2 is used.

[0661] In some embodiments, when the maximum number of current DMRS symbols is 2 (i.e., maxLength = 2) and condition A is satisfied, the antenna port field is 4 bits, and Table 7.3.1.1.2-7A-2 in Solution 2 is used.

[0662] Solution 7: In RRC, a new parameter is used to explicitly indicate whether OCC is enabled. In DCI, the OCC sequence, OCC length, and OCC enable / disable (or activate / deactivate) are implicitly indicated through the antenna port field.

[0663] Configuration of OCC length and whether OCC is enabled in RRC: The same as Solution 6.

[0664] Configuration of OCC sequence in DCI:

[0665] When occ-enabler is configured in RRC or occ-enabler indicates that OCC is enabled, in DCI, the OCC sequence, OCC length, and OCC disable can be implicitly indicated through the antenna port field. In some embodiments, the mapping relationship between the OCC sequence index, OCC length, OCC disable, and antenna port (or DMRS port) index can be represented in the form of a table.

[0666] a. When the UE reports UE capability OCC-2 but does not report UE capability OCC-4, it indicates that the maximum OCC length that can be supported is 2.

[0667] In some embodiments, when the maximum number of current DMRS symbols is 1 (i.e., maxLength = 1) and condition A is not satisfied, the antenna port field is 2 bits, and Table 7.3.1.1.2-6-1 in Solution 4 is used.

[0668] In some embodiments, when the maximum number of current DMRS symbols is 1 (i.e., maxLength = 1) and condition A is not satisfied, the antenna port field is 2 bits, and Table 7.3.1.1.2-6A-1 in Solution 4 is used.

[0669] In some embodiments, when the maximum number of current DMRS symbols is 2 (i.e., maxLength = 2) and condition A is not satisfied, the antenna port field is 4 bits, and Table 7.3.1.1.2-7-1 in Solution 4 is used.

[0670] In some embodiments, when the maximum number of current DMRS symbols is 2 (i.e., maxLength = 2) and condition A is satisfied, the antenna port field is 4 bits, and Table 7.3.1.1.2-7A-1 in Solution 4 is used.

[0671] b. When the UE reports UE capability OCC-4, it indicates that the maximum OCC length that can be supported is 4.

[0672] In some embodiments, when the maximum number of current DMRS symbols is 1 (i.e., maxLength = 1) and condition A is not satisfied, the antenna port field is 3 bits, and Table 7.3.1.1.2-6-2 in Solution 4 is used.

[0673] In some embodiments, when the maximum number of current DMRS symbols is 1 (i.e., maxLength = 1) and condition A is satisfied, the antenna port field is 3 bits, and Table 7.3.1.1.2-6A-2 in Solution 4 is used.

[0674] In some embodiments, when the maximum number of current DMRS symbols is 2 (i.e., maxLength = 2) and condition A is not satisfied, the antenna port field is 4 bits, and Table 7.3.1.1.2-7-2 in Solution 4 is used.

[0675] In some embodiments, when the maximum number of current DMRS symbols is 2 (i.e., maxLength = 2) and condition A is satisfied, the antenna port field is 4 bits, and Table 7.3.1.1.2-7A-2 in Solution 4 is used.

[0676] Embodiment 7: Common PDCCH Repetition Transmission

[0677] The public PDCCH may refer to at least one of the PDCCH CSSs, or the PDCCH using cell-level PDCCH parameters (PDCCH-ConfigCommon). The public PDCCH may include: Type0-PDCCH CSS or the PDCCH corresponding to it on the Type0-PDCCH CSS, Type0A-PDCCH CSS or the PDCCH corresponding to it on the Type0A-PDCCH CSS, Type0B-PDCCH CSS or the PDCCH corresponding to it on the Type0B-PDCCH CSS, Type1-PDCCH CSS or the PDCCH corresponding to it on the Type1-PDCCH CSS, Type1A-PDCCH CSS or the PDCCH corresponding to it on the Type1A-PDCCH CSS, Type2-PDCCH CSS or the PDCCH corresponding to it on the Type2-PDCCH CSS, Type2A-PDCCH CSS or the PDCCH corresponding to it on the Type2A-PDCCH CSS, Type3-PDCCH CSS or the PDCCH corresponding to it on the Type3-PDCCH CSS, SS0 or the PDCCH corresponding to it on SS0, the PDCCH corresponding to the SS configured by searchSpaceSIB1, the PDCCH corresponding to the SS configured by searchSpaceOtherSystemInformation, the PDCCH corresponding to the SS configured by pagingSearchSpace, the PDCCH corresponding to the SS configured by ra-SearchSpace, the PDCCH corresponding to the SS configured by searchSpaceMCCH, the PDCCH corresponding to the SS configured by searchSpaceMTCH, the PDCCH corresponding to the SS configured by searchSpaceMulticastMCCH, the PDCCH corresponding to the SS configured by searchSpaceMulticastMTCH, the PDCCH corresponding to the SS configured by peiSearchSpace, and the PDCCH corresponding to the SS configured by sdt-SearchSpace. SS0 refers to search space 0, which may include searchSpaceZero configured in the MIB (e.g., through PDCCH-ConfigSIB1) or searchSpaceZero configured in SIB1 / SIBx / RRC (e.g., through PDCCH-ConfigCommon). For the sake of simplicity in description, the PDCCH CSS described in this patent may refer to the PDCCH corresponding to this CSS.

[0678] The PDCCH repeated transmission can be defined as follows: multiple PDCCHs transmit the same DCI (downlink control information) with the same AL (aggregation level), and the encoded bits carried in the multiple PDCCHs are also the same. In this application, "the repeated transmission of PDCCH" is also referred to as "PDCCH repetition" or "PDCCH repeated transmission" (PDCCH repetition), and "the PDCCH for repeating the transmission of DCI" can also be referred to as "the repeated PDCCH" (repeated PDCCH). This will not be repeated hereinafter. The PDCCH described in this article may include PDCCH candidates.

[0679] In the current protocol, PDCCH retransmission within a time slot is already supported. More specifically, the network node configures two search spaces (SS) for the user, and if the same searchSpaceLinkingId is configured in the configurations of the two SSs, the two SSs can be considered associated. Then, the network node can transmit duplicate PDCCHs in the two associated SSs. The user terminal improves the detection performance of the PDCCH by detecting the retransmitted PDCCH. However, the above configuration of associated SSs can only be performed after the user enters the connected state. Moreover, the following SSs do not support being associated with other SSs: SS set 0, searchSpaceSIB1, searchSpaceOtherSystemInformation, pagingSearchSpace, ra-SearchSpace, searchSpaceMCCH, searchSpaceMTCH, peiSearchSpace, and sdt-SearchSpace. Therefore, PDCCH retransmission based on associated SSs is not applicable to common PDCCH CSSs such as Type0-PDCCH CSS, Type0A-PDCCH CSS, Type0B-PDCCH CSS, Type1-PDCCH CSS, Type1A-PDCCH CSS, Type2-PDCCH CSS, Type2A-PDCCH CSS, etc., that is, it cannot be used for scheduling of SIB (System Information Block), scheduling during the initial access process, scheduling of paging, and scheduling of SDT (Small Data Transmission). The current PDCCH retransmission only supports retransmission within a time slot, so it is also called in-slot retransmission. This scheme can be called the first in-slot retransmission. If the network side configures an SS associated with the PDCCH CSS, it may implicitly indicate enabling the retransmission of the common PDCCH or PDCCH CSS. Otherwise, it may implicitly indicate disabling the retransmission of the common PDCCH or PDCCH CSS.

[0680] In addition to the repeated transmission in the above-mentioned first time slot, there may be other repeated transmission methods in other time slots. For example, repeated transmission in the second time slot: The network side configures an SS. Among the time slots determined according to the SS, there are multiple time domain resources that can be used for PDCCH transmission. Each repeated PDCCH may occupy one time domain resource. The PDCCH candidates for repeated transmission may have the same aggregation level, coding bits, DCI payload, and CCE index. The UE may detect the same PDCCH candidate or PDCCH candidates with the same index / number within multiple time domain resources for PDCCH repeated transmission. The time domain resources may be a control resource set (CORESET), an SS occasion, a set composed of consecutive symbols, etc. The PDCCH repeated transmission may correspond to the same search space or the same control resource set, but is repeated on different symbol sets. The time domain resources may be consecutive time domain resources. Or, the time domain resources may be discontinuous time domain resources. For example, there is a time interval or offset X between adjacent time domain resources, or there is a time interval or offset X between the i-th time domain resource and the first time domain resource i 。X or X i may be configured by the network side or predefined by the protocol. If the network side does not configure the time interval or offset of multiple time domain resources for PDCCH repeated transmission (such as the above X or X i ), then it may be considered that the time interval is 0 or the multiple time domain resources are consecutive time domain resources. Specifically:

[0681] a. For multiple time domain resources for PDCCH repeated transmission, if the network side configures a time interval or offset, such as the interval or offset X between adjacent time domain resources or the interval or offset X relative to the first time domain resource i , then determine the time resource of the first transmission (such as the first PDCCH candidate or PDCCH transmission in the repeated transmission) according to the configuration of the search space SS, and then determine the time resources of subsequent repeated transmissions (such as PDCCH candidates or PDCCH transmissions other than the first one in the repeated transmission) according to the time interval or offset.

[0682] b. If the network side does not configure a time interval or offset, then the multiple time domain resources for PDCCH repeated transmission are consecutive time resources, or consecutive available time resources, or consecutive time resources without DMRS symbols.

[0683] The configuration may be included in the SS configuration (e.g., in the SearchSpace), or define a new information element or signaling (e.g., in PDCCH-ConfigCommon). The configuration may be different for different SSs (e.g., SSs with different IDs) or different types of SSs (e.g., Type0A / 0B / 1 / 1A / 2 / 2A, etc.), or be per-SS configuration. For example, at least one of the following configurations is supported:

[0684] 1. For SS0, introduce an information element in PDCCH-ConfigCommon to configure or indicate the time interval or offset of multiple time-domain resources during PDCCH retransmission on SS0.

[0685] 2. For SSx (x > 0), introduce an information element in the corresponding SearchSpace to configure or indicate the time interval or offset of multiple time-domain resources during PDCCH retransmission on SSx.

[0686] 3. For Type0A-PDCCH CSS or searchSpaceOtherSystemInformation, introduce an information element in PDCCH-ConfigCommon to configure or indicate the time interval or offset of multiple time-domain resources during Type0A-PDCCH CSS retransmission.

[0687] 4. For Type0B-PDCCH CSS or searchSpaceMCCH or searchSpaceMTCH, introduce an information element in PDCCH-ConfigCommon or in the signaling containing searchSpaceMCCH or searchSpaceMTCH to configure or indicate the time interval or offset of multiple time-domain resources during Type0B-PDCCH CSS retransmission.

[0688] 5. For Type1-PDCCH CSS or ra-SearchSpace, introduce an information element in PDCCH-ConfigCommon to configure or indicate the time interval or offset of multiple time-domain resources during Type1-PDCCH CSS retransmission.

[0689] 6. For Type1A-PDCCH CSS or sdt-SearchSpace, introduce an information element in PDCCH-ConfigCommon to configure or indicate the time interval or offset of multiple time-domain resources during Type1A-PDCCH CSS retransmission.

[0690] 7. For Type2-PDCCH CSS or pagingSearchSpace, introduce an information element in PDCCH-ConfigCommon to configure or indicate the time interval or offset of multiple time-domain resources during the repeated transmission of Type2-PDCCH CSS.

[0691] 8. For Type2A-PDCCH CSS or pei-SearchSpace, introduce an information element in PDCCH-ConfigCommon to configure or indicate the time interval or offset of multiple time-domain resources during the repeated transmission of Type2A-PDCCH CSS.

[0692] 9. For Type0-PDCCH CSS or searchSpaceSIB1, introduce an information element in PDCCH-ConfigCommon to configure or indicate the time interval or offset of multiple time-domain resources during the repeated transmission of Type0-PDCCH CSS (corresponding to searchSpaceSIB1).

[0693] 10. For Type0A / 0B / 1 / 1A / 2 / 2A-PDCCH CSS, introduce an information element in PDCCH-ConfigCommon to configure or indicate the time interval or offset of multiple time-domain resources during the repeated transmission of PDCCH CSS. The configuration takes effect for all CSSs in Type0A / 0B / 1 / 1A / 2 / 2A-PDCCH CSS.

[0694] For the repeated transmission in the second time slot, the network side may also configure the number of repeated transmissions or the repeated transmission enabling signaling. If the network side configures the number of repeated transmissions, it may implicitly indicate the enabling of the common PDCCH or PDCCH CSS repeated transmission. Otherwise, it may implicitly indicate the disabling of the common PDCCH or PDCCH CSS repeated transmission. If the network side configures the repeated transmission enabling signaling but does not configure the number of repeated transmissions, it may implicitly indicate that the number of repeated transmissions is 2, or other standard predefined numbers of repeated transmissions.

[0695] In summary, the method for the repeated transmission of PDCCH within a time slot may include at least one of the following: repeated transmission in the first time slot, repeated transmission in the second time slot.

[0696] To support the repeated transmission of the common PDCCH, the following methods may be considered:

[0697] 1. Extend the repeated transmission in the first time slot to the common PDCCH or PDCCH CSS. For example, for PDCCH CSS, the searchSpaceLinkingId can also be configured, or support associating PDCCH CSS with other SSs.

[0698] 2. Support the repeated transmission in the second time slot for the common PDCCH or PDCCH CSS.

[0699] It should be noted that in the current standard protocol, the configuration method of SS0 is different from that of other search spaces. SS0 can be configured through a bit field searchSpaceZero in either PDCCH-ConfigSIB1 or PDCCH-ConfigCommon. This bit field may be 4 bits long. Users look up the search space configuration in a predefined table in the standard protocol according to the value indicated by the bit field. Therefore, it is difficult to directly include the above-mentioned association identifier (such as searchSpaceLinkingID) in the configuration of SS0. Therefore, the repeated transmission in the first time slot may be difficult to apply to SS0. For this situation, the following methods may be considered:

[0700] 1. For the common PDCCH or PDCCH CSS, adopt the repeated transmission in the second time slot.

[0701] 2. For the common PDCCH or PDCCH CSS on SS0, adopt the repeated transmission in the second time slot; for the common PDCCH or PDCCH CSS not on SS0, adopt the repeated transmission in the first time slot.

[0702] 3. For the common PDCCH or PDCCH CSS, adopt the repeated transmission in the first time slot. If the common PDCCH or PDCCH CSS is on SS0, it is considered to be associated with an SS containing a specific association identifier. The specific association representation may be predefined in the protocol or configured by the network side.

[0703] 4. For the common PDCCH or PDCCH CSS, support the repeated transmission in the first time slot and the repeated transmission in the second time slot. If the SS where the common PDCCH or PDCCH CSS is located is associated with other SSs, use the repeated transmission in the first time slot. If the SS where the common PDCCH or PDCCH CSS is located is not associated with other SSs, the repeated transmission in the second time slot may be used in the following scenarios:

[0704] (1). The network side configures an enabling signaling to enable the repeated transmission in the second time slot.

[0705] (2). The network side configures the interval or offset of multiple time domain resources (as described above).

[0706] (3) The network side configures enabling signaling, but does not configure the above time interval or offset. In this case, multiple time domain resources for PDCCH repeated transmission are consecutive time resources.

[0707] It should be noted that the above method may only be applicable to some common PDCCHs or PDCCH CSSs. For example, PDCCH CSSs other than Type0-PDCCH CSS and Type3-PDCCH CSS. For another example, at least one of Type0A / 0B / 1 / 1A / 2 / 2A-PDCCH CSSs. Therefore, in the above method, it can also be applied to the following situations: changing "common PDCCH or PDCCH CSS" to "Type0A-PDCCH CSS", or "Type0B-PDCCH CSS", or "Type1-PDCCH CSS", or "Type1A-PDCCH CSS", or "Type2-PDCCH CSS", or "Type2A-PDCCH CSS", or "Type0A / 0B / 1 / 1A / 2 / 2A-PDCCH CSS", or "at least one of Type0A / 0B / 1 / 1A / 2 / 2A-PDCCH CSSs". In addition, in the above method, it may also be applied to the following situations: changing "common PDCCH or PDCCH CSS" to "Type0-PDCCH CSS", or "searchSpaceSIB1", or "Type0-PDCCH CSS corresponding to searchSpaceSIB1". In addition, in the above method, it may also be applied to the following situations: changing "common PDCCH or PDCCH CSS" to "Type3-PDCCH CSS".

[0708] The above network side configuration may refer to the network side indicating UE parameters or configurations through the first signaling. The above signaling includes at least one of the following: Master Information Block MIB, System Information Block SIB, Physical Broadcast Channel PBCH, Radio Resource Control RRC signaling. Specific indication methods may include:

[0709] Defining a new / special bit field to indicate;

[0710] Reusing / reinterpreting an existing bit field to indicate;

[0711] Reusing / reinterpreting a certain or some states / code points of an existing bit field to indicate;

[0712] Introducing a new Information Element IE to indicate (such as enumerating multiple alternative values, indicating one from multiple alternative values, or indicating a specific value);

[0713] For the enable / activate indication, corresponding information elements (IEs) may be introduced. When the network side configures / indicates such information elements, it indicates enable / activate, and when there is no configuration / indication, it indicates disable / deactivate. Alternatively, for the enable / activate indication, a new bit field may be introduced or the idle / reserved bits in the existing signaling may be multiplexed / reinterpreted, such as in MIB / PBCH / SIB1 / SIBx. When the bit indicates "1", it represents enable / activate, and when it indicates "0", it represents disable / deactivate; vice versa.

[0714] An embodiment of the present application further provides a communication node, including: a processor, which is configured to implement the method provided in any embodiment of the present application when executing a computer program. Specifically, the communication node may be a first communication node or a second communication node. The first communication node includes: a processor, which is configured to implement the information sending method and the uplink transmission method provided in any embodiment of the present application when executing a computer program; the second communication node includes: a processor, which is configured to implement the information receiving method provided in any embodiment of the present application when executing a computer program. Exemplarily, the first communication node may be a terminal device provided in any embodiment of the present application, such as a UE; the second communication node may be an access network device provided in any embodiment of the present application, such as a base station, and the present application does not make specific limitations in this regard.

[0715] Exemplarily, the following embodiments respectively provide a schematic structural diagram of a communication node being a terminal and a base station.

[0716] Figure 18 It is a schematic structural diagram of a terminal provided by an embodiment. The terminal can be implemented in various forms. The terminal in the present application may include, but is not limited to, mobile terminal devices such as mobile phones, smart phones, laptop computers, digital broadcast receivers, personal digital assistants (PDAs), tablet computers (PADs), portable media players (PMPs), navigation devices, in-vehicle terminal devices, in-vehicle display terminals, in-vehicle electronic rearview mirrors, etc., and fixed terminal devices such as digital televisions (TVs), desktop computers, etc.

[0717] As Figure 18 shown, the terminal 50 may include a wireless communication unit 51, an audio / video (A / V) input unit 52, a user input unit 53, a sensing unit 54, an output unit 55, a memory 56, an interface unit 57, a processor 58, a power supply unit 59, and so on. Figure 18A terminal including various components is shown, but it should be understood that it is not required to implement all the shown components. Instead, more or fewer components may be implemented.

[0718] In this embodiment, the wireless communication unit 51 allows radio communication between the terminal 50 and a base station or a network. The A / V input unit 52 is configured to receive an audio or video signal. The user input unit 53 may generate key input data according to a command input by a user to control various operations of the terminal 50. The sensing unit 54 monitors the current state of the terminal 50, the position of the terminal 50, the presence or absence of a touch input by the user to the terminal 50, the orientation of the terminal 50, the acceleration or deceleration movement and direction of the terminal 50, etc., and generates a command or signal for controlling the operation of the terminal 50. The interface unit 57 serves as an interface through which at least one external device can be connected to the terminal 50. The output unit 55 is configured to provide an output signal in a visual, audio, and / or tactile manner. The memory 56 may store software programs for processing and control operations executed by the processor 58, etc., or may temporarily store data that has been output or is to be output. The memory 56 may include at least one type of storage medium. Moreover, the terminal 50 may cooperate with a network storage device that performs the storage function of the memory 56 through a network connection. The processor 58 generally controls the overall operation of the terminal 50. The power supply unit 59 receives external power or internal power under the control of the processor 58 and provides appropriate power required to operate various elements and components.

[0719] The processor 58 executes at least one functional application and data processing by running a program stored in the memory 56, for example, implementing the method provided by the embodiments of the present application.

[0720] Figure 19 It is a schematic structural diagram of a base station provided by an embodiment. As Figure 19 shown, the base station includes a processor 60, a memory 61, and a communication interface 62; the number of processors 60 in the base station may be one or more, Figure 19 and one processor 60 is taken as an example herein; the processor 60, the memory 61, and the communication interface 62 in the base station may be connected through a bus or other means, Figure 19 and taking connection through a bus as an example herein. The bus represents one or more of several types of bus structures, including a memory bus or a memory controller, a peripheral bus, a graphics acceleration port, a processor, or a local bus using any bus structure in a variety of bus structures.

[0721] The memory 61, being a computer-readable storage medium, can be configured to store software programs, computer-executable programs, and modules, such as the program instructions / modules corresponding to the method in the embodiments of the present application. The processor 60 executes at least one functional application and data processing of the base station by running the software programs, instructions, and modules stored in the memory 61, thus implementing the above-mentioned method.

[0722] The memory 61 may include a program storage area and a data storage area. Among them, the program storage area can store an operating system and application programs required for at least one function; the data storage area can store data created according to the use of the terminal, etc. In addition, the memory 61 may include high-speed random access memory and may also include non-volatile memory, such as at least one magnetic disk storage device, a flash memory device, or other non-volatile solid-state storage devices. In some instances, the memory 61 may include a memory remotely disposed relative to the processor 60, and these remote memories can be connected to the base station through a network. Examples of the above network include but are not limited to the Internet, an enterprise intranet, a network, a mobile communication network, and combinations thereof.

[0723] The communication interface 62 can be configured for receiving and sending data.

[0724] The embodiments of the present application also provide a computer-readable storage medium, on which a computer program is stored. When the computer program is executed by a processor, it implements the method provided in any embodiment of the present application.

[0725] The computer storage medium of the embodiments of the present application can adopt any combination of one or more computer-readable media. The computer-readable medium can be a computer-readable signal medium or a computer-readable storage medium. The computer-readable storage medium can be, for example, but not limited to: an electrical, magnetic, optical, electromagnetic, infrared, or semiconductor system, apparatus, or device, or any combination of the above. The computer-readable storage medium includes (a non-exhaustive list): an electrical connection having one or more wires, a portable computer disk, a hard disk, a random access memory (RAM), a read-only memory (ROM), an electrically erasable, programmable read-only memory (EPROM), a flash memory, an optical fiber, a portable compact disc read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination of the above. In the present application, the computer-readable storage medium can be any tangible medium that contains or stores a program, and this program can be used by or in combination with an instruction execution system, apparatus, or device.

[0726] A computer-readable signal medium may include a data signal propagated in a baseband or as part of a carrier wave, in which a computer-readable program code is carried. Such a propagated data signal may take many forms, including but not limited to electromagnetic signals, optical signals, or any suitable combination of the foregoing. The computer-readable signal medium may also be any computer-readable medium other than a computer-readable storage medium, which can send, propagate, or transmit a program for use by or in connection with an instruction execution system, apparatus, or device.

[0727] The program code contained on the computer-readable medium may be transmitted by any appropriate medium, including but not limited to wireless, wireline, optical fiber cable, radio frequency (RF), etc., or any suitable combination of the foregoing.

[0728] The computer program code for performing the operations of the present disclosure may be written in one or more programming languages or a combination of multiple programming languages. The programming languages include object-oriented programming languages (such as Java, Smalltalk, C++, Ruby, Go), and also include conventional procedural programming languages (such as the "C" language or similar programming languages). The program code may be executed entirely on the user's computer, partially on the user's computer, executed as a stand-alone software package, partially on the user's computer and partially on a remote computer, or entirely on a remote computer or server. In the case of a remote computer, the remote computer may be connected to the user's computer through any type of network (including a local area network (LAN) or a wide area network (WAN)), or may be connected to an external computer (e.g., by connecting through the Internet using an Internet service provider).

[0729] The present application also provides a computer program product that, when executed by a computer, implements any one of the functions in the foregoing method embodiments.

[0730] Those skilled in the art should understand that the term user terminal covers any suitable type of wireless user equipment, such as a mobile phone, a portable data processing device, a portable network browser, or an in-vehicle mobile station.

[0731] Generally speaking, various embodiments of the present application may be implemented in hardware or a dedicated circuit, software, logic, or any combination thereof. For example, some aspects may be implemented in hardware, while other aspects may be implemented in firmware or software that can be executed by a controller, a microprocessor, or other computing devices, although the present application is not limited thereto.

[0732] Embodiments of the present application can be implemented by a data processor of a mobile device executing computer program instructions, for example, in a processor entity, or by hardware, or by a combination of software and hardware. The computer program instructions can be assembly instructions, instruction set architecture (ISA) instructions, machine instructions, machine-related instructions, microcode, firmware instructions, status setting data, or source code or object code written in any combination of one or more programming languages.

[0733] Any block diagram of a logical process in the drawings of the present application can represent program steps, or can represent interconnected logical circuits, modules, and functions, or can represent a combination of program steps and logical circuits, modules, and functions. The computer program can be stored in a memory. The memory can have any type suitable for the local technical environment and can be implemented using any suitable data storage technology, such as but not limited to read-only memory (ROM), random access memory (RAM), optical memory devices and systems (digital versatile disc DVD or CD disc), etc. The computer-readable medium can include a non-transitory storage medium. The data processor can be any type suitable for the local technical environment, such as but not limited to a general-purpose computer, a special-purpose computer, a microprocessor, a digital signal processor (DSP), an application-specific integrated circuit (ASIC), a field-programmable gate array (FPGA), and a processor based on a multi-core processor architecture.

Claims

1. An information sending method, characterized in that, Applied to a first communication node, the method includes: Receiving orthogonal coverage code (OCC) configuration information sent by a second communication node; Determining the information after OCC extension according to the OCC configuration information; Sending the information after OCC extension to the second communication node.

2. The method according to claim 1, wherein The OCC configuration information includes at least one of the following: A first indication for indicating to enable or disable the OCC function; A second indication for indicating OCC activation or OCC deactivation; A third indication for indicating the OCC length; A fourth indication for indicating OCC sequence parameters, where the OCC sequence parameters include: an OCC sequence or an OCC index.

3. The method according to claim 2, wherein The indication is indicated by at least one of the following ways: Indicated by a high-layer signaling; When the OCC length or the OCC sequence parameters are indicated as valid values, it indicates to enable the OCC function; When the OCC length or the OCC sequence parameters are indicated as invalid values, it indicates to disable the OCC function; Indicated by an existing field or a newly added field in the DCI scheduling PUSCH; Determined by the first indication and / or the second indication.

4. The method according to claim 3, wherein The second indication is indicated by at least one of the following fields in the DCI: a modulation and coding scheme field, a repetition field, a redundancy version field, a TB number field for unicast scheduling, a subcarrier indication field, or a resource reservation field.

5. The method according to claim 2, wherein In the case of satisfying at least one of the following conditions, the second indication is used to indicate OCC activation or OCC deactivation: The first indication indicates to enable the OCC function or the first indication is configured; The subcarrier spacing is configured to 15 kHz, where the subcarrier spacing is indicated by a high-layer parameter or the uplink subcarrier spacing in the random access response grant; The subcarrier spacing is configured to 3.75 kHz, where the subcarrier spacing is indicated by a high-layer parameter or the uplink subcarrier spacing in the random access response grant; The DCI CRC is scrambled by a C-RNTI.

6. The method according to claim 2, wherein When at least one of the following conditions is satisfied, the third indication is used to indicate the OCC length, or the OCC length is a preset value: The first indication indicates to enable the OCC function or the first indication is configured; The second indication indicates to activate the OCC.

7. The method according to claim 3, characterized in that, The fourth indication is indicated by one of the following ways: Indicated by at least one of the following fields in the DCI: a modulation and coding scheme field, a repetition field, a redundancy version field, a TB number field for unicast scheduling, a subcarrier indication field, or a resource reservation field; Indicated by 2 bits in the at least one field or the newly added field, where the 2 bits are also used to indicate OCC activation or OCC deactivation; Indicated by an index set corresponding to the subcarrier indication field in the DCI, where the index set indication is also used to indicate OCC activation or OCC deactivation; Indicated by an index set corresponding to the subcarrier indication field in the DCI; Indicated by an existing field in the DCI as a new indication field.

8. The method according to claim 7, wherein The new indication field includes: the fourth indication, the second indication, a modulation and coding scheme, and a subcarrier indication field.

9. The method according to claim 8, wherein The modulation and coding scheme and the subcarrier indication field are used to indicate the modulation and coding scheme index and the subcarrier index corresponding to the modulation and coding scheme index, or are used to indicate the subcarrier index and the modulation and coding scheme index corresponding to the subcarrier index, or are used to indicate the modulation and coding scheme index and the subcarrier index; Each modulation and coding scheme index from 0 to A corresponds to a subcarrier index from 0 to B respectively; Alternatively, each subcarrier index from 0 to B corresponds to a modulation and coding scheme index from 0 to A respectively; Alternatively, each modulation and coding scheme index from 0 to C corresponds to a subcarrier index from 0 to D respectively; or each subcarrier index from 0 to D corresponds to a modulation and coding scheme index from 0 to C respectively.

10. The method according to claim 9, wherein For the single-carrier 3.75 kHz subcarrier spacing configuration: the number of subcarrier indices corresponding to at least one modulation and coding scheme index is less than B + 1, or the number of modulation and coding scheme indices corresponding to at least one subcarrier index is less than A + 1.

11. The method according to claim 2, wherein In the case of satisfying at least one of the following conditions, the fourth indication is used to indicate the OCC sequence parameters: The first indication indicates enabling the OCC function or the first indication is configured; The second indication indicates activating the OCC; The third indication indicates a specific OCC length; The OCC length is determined to be a specific OCC length according to the first indication and / or the second indication; The subcarrier spacing is configured to 15 kHz, where the subcarrier spacing is indicated by a higher layer parameter or the uplink subcarrier spacing in the random access response grant; The subcarrier spacing is configured to 3.75 kHz, where the subcarrier spacing is indicated by a higher layer parameter or the uplink subcarrier spacing in the random access response grant; The DCI CRC is scrambled by the C-RNTI.

12. The method according to claim 1, wherein The information after OCC extension includes the data after OCC extension; Determining the information after OCC extension according to the OCC configuration information includes: Determining the OCC sequence parameters according to the OCC configuration information; Determining the OCC sequence according to the OCC sequence parameters; Determining the data after OCC extension according to the OCC sequence and the complex modulation symbols.

13. The method according to claim 12, characterized in that, Determining the data after OCC extension according to the OCC sequence and the complex modulation symbols includes at least one of the following: Extending the complex modulation symbols on each time-domain symbol block obtained by dividing the complex modulation symbols by the OCC sequence to obtain the data after OCC extension; Extending the complex modulation symbols on each time slot block obtained by dividing the complex modulation symbols by the OCC sequence to obtain the data after OCC extension; Extending the complex modulation symbols on each repetition unit block obtained by dividing the complex modulation symbols by the OCC sequence to obtain the data after OCC extension.

14. The method according to claim 12, wherein The method further includes: In the case of satisfying at least one of the following conditions, determining to perform the step of determining the data after OCC extension according to the OCC sequence and the complex modulation symbols: The first indication indicates enabling the OCC function or the first indication is configured; The second indication indicates activating the OCC; The third indication indicates a specific OCC length; The OCC length is determined to be a specific OCC length according to the first indication and / or the second indication; The fourth indication indicates specific OCC sequence parameters; The subcarrier spacing is configured to 15 kHz, where the subcarrier spacing is indicated by a higher layer parameter or the uplink subcarrier spacing in the random access response grant; The subcarrier spacing is configured to 3.75 kHz, where the subcarrier spacing is indicated by a higher layer parameter or the uplink subcarrier spacing in the random access response grant; The number of consecutive subcarriers is configured to multiple carriers, where the number of subcarriers is indicated by the subcarrier indication field in the DCI scheduling the PUSCH.

15. The method according to claim 12, wherein The data after OCC extension includes a second PUSCH codeword; The method further includes: The scrambling sequence of the first PUSCH codeword is re-initialized every OCC length times or after each repeated transmission, where represents the number of repetitions of N RU resource elements mapped by the first PUSCH codeword before OCC expansion; Map the second PUSCH codeword to N RU,enh resource elements, where N RU,enh represents the number of resource elements, and N RU,enh is determined by the OCC length and the number of resource elements N RU to which the first PUSCH codeword is mapped. Every N RU,enh resource elements are transmitted once, length.

16. The method according to claim 15, wherein Mapping the second PUSCH codeword to N RU,enh resource elements, including any one of the following: Mapped to N s'(ts After the time slot, before continuing to map z(·) to the next time slot, N s'(ts time slots times should be repeated, where is equal to 1, represents the number of repetitions of consecutive time slots, N s'(ts represents the number of consecutive time slots; Mapped to the OCC length * N ；:<7； After the time slot, before continuing to map z(·) to the next time slot, the OCC length * n should be repeated ；:<7； Time slot times Equal to Length or Length 17. The method according to claim 15, characterized in that, Sending the information after OCC extension to the second communication node includes at least one of the following: For the second PUSCH codeword corresponding to the j-th TB, it is transmitted in B consecutive time slots ni, where i = jB + b, b = 0, 1,..., B - 1, The redundancy version rv associated with the TB ,-J (j) is determined as follows: rv ,-J (j) = 2 * mod(rv e.1 + j, 2), if then L = 1, and the part of the second PUSCH codeword associated with rv ,-J (j) will be mapped to the FU,e.1 th time slot among the allocated N resource units for transmission, represents the number of time slots included in the resource unit, and rv e.1 is indicated by the redundancy version field in the DCI or predefined, represents the number of consecutive subcarriers; For the second PUSCH codeword corresponding to the j-th TB, it is transmitted in B consecutive time slots ni, where i = jB + b, b = 0, 1,..., B - 1, the redundancy version rv associated with the TB ,-J The determination method of (j) is as follows: rv ,-J (j) = 2 * mod(rv e.1 + j, 2), if then L = 1, otherwise In the case of a subcarrier spacing of 3.75 kHz, in the uplink time slot associated with the TB, the mapping method of time slot ni is In the case of a subcarrier spacing of 15 kHz, in the uplink time slot associated with the TB, the mapping method of time slot ni is 18. The method according to claim 1, characterized in that The information after OCC extension includes a DMRS sequence; Determining the information after OCC extension according to the OCC configuration information includes: According to the formula determine the length of the DMRS sequence and generate the DMRS sequence, where represents the number of repetitions of N resource units mapped by the first PUSCH codeword before OCC expansion FU resource units, represents the number of time slots included in the resource unit, and N FU represents the number of resource units mapped by the first PUSCH codeword before OCC expansion.

19. The method according to claim 18, wherein The method further includes at least one of the following: Determining the time slot subgroup for the first communication node to transmit or map the DMRS sequence according to the OCC sequence parameters and the number of time slot subgroups; Determining the time slot subgroup for the first communication node to transmit or map the DMRS sequence according to the mapping relationship between the OCC sequence parameters and the time slot subgroup.

20. The method according to claim 1, characterized in that, The information after OCC extension includes the DMRS sequence after OCC extension; Determining the information after OCC extension according to the OCC configuration information includes any one of the following: According to the formula Determine the length of the DMRS sequence before expansion according to the length, and determine the DMRS sequence after OCC expansion according to the OCC sequence and the DMRS sequence before expansion, where the OCC sequence is information determined according to the OCC configuration information. Represents the number of repetitions of n RU resource units mapped by the first PUSCH codeword before OCC expansion, and n RU represents the number of resource units mapped by the first PUSCH codeword. Represents the number of time slots included in the resource unit. Determining the frequency domain length of the DMRS sequence before extension according to the number of consecutive subcarriers, and determining the DMRS sequence after OCC extension according to the OCC sequence and the DMRS sequence before extension; Determining the frequency domain length of the DMRS sequence before extension according to the number of consecutive subcarriers, and determining the DMRS sequence after OCC extension according to the cyclic shift and the DMRS base sequence, where the cyclic shift is related to the OCC sequence.

21. The method according to claim 18 or 20, characterized in that, The method further includes: Determining to perform the step of determining the information after OCC extension according to the OCC configuration information when at least one of the following conditions is satisfied: The first indication indicates that the OCC function is enabled or the first indication is configured; The second indication indicates the activation of OCC; The third indication indicates a specific OCC length; The OCC length is determined to be a specific OCC length according to the first indication and / or the second indication; The fourth indication indicates specific OCC sequence parameters; The subcarrier spacing is configured to 15 kHz, where the subcarrier spacing is indicated by a higher layer parameter or the uplink subcarrier spacing in the random access response grant; The subcarrier spacing is configured to 3.75 kHz, where the subcarrier spacing is indicated by a higher layer parameter or the uplink subcarrier spacing in the random access response grant; The number of consecutive subcarriers is configured to 1, where the number of subcarriers is indicated by the subcarrier indication field in the DCI scheduling the PUSCH; The number of consecutive subcarriers is configured to multiple carriers, where the number of subcarriers is indicated by the subcarrier indication field in the DCI scheduling the PUSCH.

22. The method according to claim 1, characterized in that, The information after OCC extension includes at least one of the following: DMRS sequence, data after OCC extension, DMRS sequence after OCC extension; The method further includes at least one of the following: When the information after OCC extension is delayed, perform the delay based on the OCC group, where the OCC group is the one with a larger duration among the data after OCC extension and the DMRS sequence after OCC extension; After the information after OCC extension is delayed, perform the delay by the delay time, where the delay time is an integer multiple of the OCC alignment length, and the OCC alignment length is the duration of the OCC group.

23. The method according to claim 22, wherein The method further includes: When at least one of the following conditions is met, determine to perform the step of delaying based on the OCC group or delaying by the delay time: The first indication indicates that the OCC function is enabled or the first indication is configured; The second indication indicates the activation of OCC; The third indication indicates a specific OCC length; The OCC length is predefined as a valid value; The fourth indication indicates specific OCC sequence parameters; The subcarrier spacing is configured to 15 kHz, where the subcarrier spacing is indicated by a high-layer parameter or the uplink subcarrier spacing in the random access response grant; The subcarrier spacing is configured to 3.75 kHz, where the subcarrier spacing is indicated by a high-layer parameter or the uplink subcarrier spacing in the random access response grant; The number of consecutive subcarriers is configured to 1, where the number of subcarriers is indicated by the subcarrier indication field in the DCI scheduling the PUSCH; The number of consecutive subcarriers is configured to multiple carriers, where the number of subcarriers is indicated by the subcarrier indication field in the DCI scheduling the PUSCH.

24. An information receiving method, characterized in that, Applied to the second communication node, the method includes: Send orthogonal cover code OCC configuration information to the first communication node; Receive the information after OCC extension sent by the first communication node, where the information after OCC extension is the information determined by the first communication node according to the OCC configuration information.

25. A method for uplink transmission, characterized in that, Includes: The first communication node determines the uplink channel configuration for carrying the uplink transmission; The first communication node sends the uplink channel for carrying the uplink transmission.

26. The method according to claim 25, wherein The uplink channel configuration includes at least one of the following: Power information; Time-domain resources; Frequency-domain resources.

27. The method according to claim 25, wherein The first communication node receives the resource configuration information indicated by the second communication node through high-layer information; or The first communication node receives the power control configuration information indicated by the second communication node through high-layer information.

28. The method according to claim 25, wherein the uplink transmission includes one of the following: The first type of uplink transmission; wherein, The first type of uplink transmission includes one of the following: contention-based uplink data transmission, contention-based Msg3 transmission, or the first message transmission of contention-based first type of random access; The second type of uplink transmission; where the second type of uplink transmission includes one of the following: The preamble of the first message of contention-based second type of random access, or The first message transmission of contention-based first type of random access.

29. The method according to claim 25, wherein When one of the following conditions is satisfied, the first communication node switches the first type of uplink transmission to the second type of uplink transmission: When the number of times of the first type of uplink transmission is greater than the maximum allowed retransmission times; or, When the number of times of the first type of uplink transmission is equal to the maximum allowed retransmission times, but it is determined as a transmission failure.

30. The method according to claim 25, wherein When one of the following conditions is satisfied, the first communication node sends multiple copies for one transmission: When the number of copies supported by one transmission indicated by the second communication node is greater than 1; The second communication node sends enabling information.

31. The method according to claims 25 and 27, characterized in that, When the first communication node sends multiple copies for one transmission, the uplink transmission channel resources carrying each copy are randomly selected by the first communication node from the resource set.

32. The method according to claim 25, wherein When the first communication node sends multiple copies for one transmission, the determination of the repetition times supported by each copy includes one of the following methods: Configured by the second communication node through higher layer signaling; The repetition times of each copy are determined by the number of copies supported by one transmission and the repetition times of one transmission; or, The repetition times of each copy are the same as the repetition times of one transmission.

33. The method according to claim 27, wherein, The power control configuration information includes one of the following: The initial target received power of the transmission; The target received power of the transmission; The power boost value of the transmission; The nominal transmit power of the transmission; The configured transmit power of the transmission.

34. A communication node, characterized in that, Comprising: A processor; The processor is used to implement the information sending method according to any one of claims 1 to 23, or implement the information receiving method according to claim 24, or implement the uplink transmission method according to any one of claims 25 to 33 when executing a computer program.

35. A computer-readable storage medium stores a computer program, characterized in that, When the computer program is executed by the processor, it implements the information sending method according to any one of claims 1 to 23, or implements the information receiving method according to claim 24, or implements the uplink transmission method according to any one of claims 25 to 33.

Images