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

By receiving and sending OCC configuration information, extending DMRS sequences and data, the problem of OCC orthogonality being violated in the Internet of Things is solved, system capacity is improved, and it is applicable to various wireless communication systems.

WO2026233014A1PCT designated stage Publication Date: 2026-11-12ZTE CORP
View PDF 0 Cites 0 Cited by

Patent Information

Application Number
PCT/CN2026/086238
Authority / Receiving Office
WO · WO
Patent Type
Applications
Current Assignee / Owner
Priority Date
2025-05-09
Filing Date
2026-03-26
Publication Date
2026-11-12

AI Technical Summary

Technical Problem

In IoT scenarios, repeated transmissions lead to resource constraints, and how to improve system capacity has become an urgent problem to be solved, especially in terrestrial and non-terrestrial networks, where the orthogonality of OCC is destroyed during transmission gaps and when data is dropped.

Method used

By receiving OCC configuration information, the extended information of OCC is determined, and the extended information of OCC, including the extension of DMRS sequence and data, is sent to the second communication node to ensure the orthogonality of OCC during transmission gaps and data drop, thereby improving system capacity.

Benefits of technology

It achieves the maintenance of OCC orthogonality during transmission gaps and data drop-off, improves system capacity, and is suitable for various wireless communication systems including LTE, 5G, new radio systems and future 6G systems.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN2026086238_12112026_PF_FP_ABST
    Figure CN2026086238_12112026_PF_FP_ABST
Patent Text Reader

Abstract

The information sending method comprises: receiving OCC configuration information sent by a second communication node; on the basis of the OCC configuration information, determining OCC extended information; and sending the OCC extended information to the second communication node.
Need to check novelty before this filing date? Find Prior Art

Description

Information sending and receiving methods, uplink transmission methods, communication nodes and media Technical Field

[0001] This application relates to the field of communication technology, such as an information sending and receiving method, an uplink transmission method, a communication node, and a medium. Background Technology

[0002] With the continuous advancement of radio technology, a wide variety of radio services have emerged. In addition to cellular services, Long Term Evolution (LTE) and New Radio (NR) systems also include Internet of Things (IoT) services.

[0003] Prior to Release 19 (Rel-19), both terrestrial networks (TN) and non-terrestrial networks (NTN) supported the use of repetition technology to enhance uplink coverage. However, IoT scenarios typically involve a large number of IoT terminals, while available resources are limited. Repetitive transmissions further constrain resources, making it crucial to address how to improve system capacity. Summary of the Invention

[0004] This application provides an information sending method applied to a first communication node, the method comprising:

[0005] Receive OCC configuration information sent by the second communication node;

[0006] Determine the extended information of the OCC based on the OCC configuration information;

[0007] The OCC-extended information is sent to the second communication node.

[0008] This application provides an information receiving method applied to a second communication node, the method comprising:

[0009] Send orthogonal coverage code (OCC) configuration information to the first communication node;

[0010] The system receives OCC-extended information sent by the first communication node, wherein the OCC-extended information is information determined by the first communication node based on the OCC configuration information.

[0011] This application provides an uplink transmission method, the method comprising:

[0012] The first communication node determines the uplink channel configuration that carries the uplink transmission;

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

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

[0015] This application also provides a computer-readable storage medium storing a computer program, which, when executed by a processor, implements the method of any of the above embodiments.

[0016] Further details regarding the above embodiments and other aspects of this application, as well as their implementations, are provided in the accompanying drawings, detailed description, and claims. Attached Figure Description

[0017] Figure 1 is a network diagram of an NTN system provided in an embodiment of this application;

[0018] Figure 2 is a schematic diagram of the physical resource mapping of PUSCH codewords in multi-tone transmission provided in the embodiments of this application;

[0019] Figure 3 is a schematic diagram of the physical resource mapping of PUSCH codewords in single-tone transmission provided in the embodiments of this application;

[0020] Figure 4 is a flowchart illustrating an information sending method provided in an embodiment of this application;

[0021] Figure 5 is a flowchart illustrating another information sending method provided in an embodiment of this application;

[0022] Figure 6 is a schematic diagram of signal acquisition in code division multiplexing provided in an embodiment of this application;

[0023] Figure 7 is a schematic diagram of the transmission / mapping / multiplexing of DMRS sequences provided in an embodiment of this application;

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

[0025] Figure 9 is a schematic diagram illustrating the information delay after OCC extension according to an embodiment of this application;

[0026] Figure 10 is a schematic diagram illustrating another OCC-extended information delay provided in an embodiment of this application;

[0027] Figure 11 is a flowchart illustrating an information receiving method provided in an embodiment of this application;

[0028] Figure 12 is a flowchart illustrating an uplink transmission method provided in an embodiment of this application;

[0029] Figure 13 is a schematic diagram of signaling interaction in the uplink transmission method provided in the embodiment of this application;

[0030] Figure 14 is a schematic diagram of the transmission resources corresponding to two copies of a transmission provided in an embodiment of this application;

[0031] Figure 15 is a schematic diagram of the transmission of two copies of a single transmission provided in an embodiment of this application;

[0032] Figure 16 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, according to an embodiment of this application.

[0033] Figure 17 is a schematic diagram of a time-slot-based OCC application provided in an embodiment of this application;

[0034] Figure 18 is a schematic diagram of the structure of a terminal provided in an embodiment of this application;

[0035] Figure 19 is a schematic diagram of the structure of a base station provided in an embodiment of this application. Detailed Implementation

[0036] It should be understood that the specific embodiments described herein are merely illustrative and not intended to limit the scope of this application. The embodiments of this application will be described in detail below with reference to the accompanying drawings.

[0037] In the Rel-19 IoT-NTN uplink capacity enhancement project, Orthogonal Cover Code (OCC) was used to enhance uplink capacity, and OCC-related configurations were discussed, such as OCC enabling, OCC activation / deactivation, and OCC index / codeword. Simultaneously, the capacity of the Demodulation Reference Signal (DMRS) was enhanced, such as supporting time-division multiplexing (TDM) DMRS. For Narrowband Physical Uplink Shared Channel (NPUSCH) format 1 with a 3.75 kHz subcarrier spacing (SCS) OCC, TDM DMRS transmission over four time slots was supported. The DMRS was transmitted in the first two time slots and omitted in the last two, or the DMRS was transmitted in the last two time slots and omitted in the first two. When multiple users reuse their devices, each terminal needs to know the time-domain symbol position of its own DMRS and reserve DMRS symbols for other reused terminals. Therefore, a method for terminals to determine DMRS mapping needs to be defined.

[0038] Meanwhile, 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, or pre-compensated segmentation gaps). These gaps may cause OCC to be transmitted across gaps or the orthogonality of OCC may be destroyed due to the dropping of certain time slots / symbols. Therefore, it is necessary to study methods to ensure the orthogonality of OCC.

[0039] The current protocol already supports enabling OCC functionality via Radio Resource Control (RRC) signaling specific to User Equipment (UE). However, the configuration scheme for the signaling, the method for the terminal to determine the DMRS mapping, the OCC application / extension method, and the issue of OCC orthogonality disruption caused by transmission gaps are still under discussion. Therefore, the information transmission and reception methods provided in this application enhance the above aspects.

[0040] The information transmission and information reception methods provided in this application can be applied to TN and NTN.

[0041] In this embodiment, TN 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. Wireless communication systems include terminal equipment, access network equipment, and core network equipment. In this embodiment, the Physical Uplink Shared Channel (PUSCH) can also be an NPUSCH, or other types of physical uplink data channels with similar functions.

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

[0043] Terminal equipment can be a device with wireless transceiver capabilities, which can be deployed on land (such as indoors or outdoors, handheld, wearable or vehicle-mounted); on water (such as ships); or in the air (such as airplanes, balloons and satellites). Examples of terminal devices include: wireless terminals, user equipment (UE), mobile phones, mobile stations, tablets, laptops, ultra-mobile personal computers (UMPCs), handheld computers, netbooks, personal digital assistants (PDAs), and other network-connected user devices; virtual reality (VR) terminals, augmented reality (AR) terminals, wireless terminals in industrial control, wireless terminals in self-driving, wireless terminals in remote medical care, wireless terminals in smart grids, wireless terminals in transportation safety, wireless terminals in smart cities, wireless terminals in smart homes, etc.; IoT nodes in the Internet of Things (IoT); in-vehicle communication devices in the Internet of Vehicles (IoV); entertainment and gaming devices or systems; and GPS devices, etc. The embodiments of this application do not limit the specific technologies or device forms used in the terminal devices. Furthermore, the term "terminal device" can be simply referred to as "terminal."

[0044] Access network equipment refers to the access devices that enable terminal devices to wirelessly access the wireless communication system. These can be readers / writers, base stations, evolved NodeBs (eNBs or eNodeBs) in Long Term Evolution Advanced (LTE), transmission reception points (TRPs), base stations in 5G mobile communication systems, next-generation NodeBs (gNBs), base stations in future mobile communication systems, or access nodes in Wireless Fidelity (WiFi) systems. Base stations can include various macro base stations, micro base stations, femtocell base stations, wireless extensions, routers, WiFi devices, or various network-side devices such as primary cells and secondary cells, as well as location management function (LMF) devices. They can also be modules or units that perform some of the base station's functions; for example, they can be central units (CUs) or distributed units (DUs). The embodiments of this application do not limit the specific technology or equipment form used in the access network equipment. In addition, the access network equipment can be referred to as a base station.

[0045] Core network equipment may include access and mobility management network elements and session management network elements. For example, a terminal device can access the core network through access network equipment to enable data transmission.

[0046] To facilitate subsequent understanding, the concepts involved in this application will be introduced below.

[0047] For resource units:

[0048] In the current specification, resource elements are used to describe the mapping from the Physical Uplink Shared Channel (PUSCH) to resource elements. Resource elements are defined in the time domain. Orthogonal Frequency Division Multiplexing (OFDM) symbols and frequency domain Continuous subcarriers, where and The following are given in Table 1, Frame Structure Type 1. This indicates the number of symbols included in a time slot. This indicates the number of time slots included in a resource unit. Δf represents the number of consecutive subcarriers, and Δf represents the subcarrier spacing.

[0049] Table 1 Frame Structure Type 1

[0050] For physical resource mapping:

[0051] The binary bits are added using Cyclic Redundancy Check (CRC), channel coded, rate matched, interleaved, and then scrambled. For repeated transmissions, the scrambling sequence is applied every... Reinitialization is performed after each repeated transmission, where The definition is given by the following formula.

[0052] Each PUSCH codeword (referred to as the first PUSCH codeword in subsequent embodiments) can be mapped to one or more resource units N. RU , per N RU Resource units should be transmitted Number of times. That is, N represents the PUSCH codeword mapping RU The number of repetitions per resource unit. The complex modulation symbol should be multiplied by the amplitude scaling factor β. PUSCH The subcarrier z(0) allocated for PUSCH transmission is mapped sequentially to the resource element (k, l) corresponding to the subcarrier allocated for data transmission. Starting from the first time slot in the allocated resource element, the mapping proceeds in ascending order of index k followed by index l. Here, k represents the subcarrier index, and l represents the symbol index in the first time slot. Mapping to N... slots After a time slot, N should be repeated before continuing to map z(·) to the next time slot. slots Time slot Next. N slots This indicates the number of consecutive time slots. Where:

[0053] Methods for determining Redundancy Versions (RVs):

[0054] For PUSCH transmission, the PUSCH transmission associated with a Transport Block (TB) and the determination of the RV are as follows: transmission occurs in N time slots in the Narrow Band Internet of Things (NB-IoT) uplink, and these time slots are denoted by n. iLet i = 0, 1, ..., N-1. For the PUSCH transmission corresponding to the j-th TB, in B consecutive NB-IoT uplink slots n i Transmission occurs during this process, where i = jB + b, b = 0, 1, ..., B-1. in Redundant version rv associated with TB idx The method for determining (j) is as follows: rvidx(j) = 2·mod(rvDCI+j,2), where, if Then L = 1, otherwise rv DCI This indicates a redundant version of the instruction. In the PUSCH codeword, it is related to rv. idx (j) (as defined in specification 6.3.2) The associated part will be mapped to the assigned N. RU The first resource unit (RU) in Transmission occurs on each slot. With a subcarrier spacing of Δf = 3.75 kHz, in the NB-IoT uplink (UL) slots associated with TB, slot n... i The mapping method is When the subcarrier spacing is Δf = 15kHz, in the NB-IoT UL slots associated with TB, slot n i The mapping method is

[0055] As can be seen from the above physical resource mapping and RV determination process, for the repeated transmission of PUSCH codewords, RV will cycle between every L repetitions, where L=1 when the number of consecutive subcarriers is 1, and L=1 when the number of consecutive subcarriers is multiple.

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

[0057] Figure 2 is a schematic diagram of the physical resource mapping of PUSCH codewords in multi-tone transmission provided in an embodiment of this application. Figure 2 corresponds to a subcarrier spacing of 15kHz. For 12, For 2, For 8, N RU For 2 and N slots The case is 2. In Figure 2, one PUSCH occupies 2 RUs, and 1 RU includes 2 time slots, meaning one PUSCH occupies 4 time slots, and the number of consecutive time slots is N. slots The number of repetitions in consecutive time slots 1 and 2 is 2. Therefore, in Figure 2, time slots 1 and 2 are repeated before being mapped to consecutive time slots 3 and 4. This means it is repeated 3 times. The number of repetitions for consecutive time slots 3 and 4 is 4 times. Based on the RV determination method described above, the RV number and the subsequent physical resource mapping process, repeated 5 to 8 times, can be determined.

[0058] Figure 3 is a schematic diagram of the physical resource mapping of PUSCH codewords in single-tone transmission provided in an embodiment of this application. Figure 3 corresponds to a subcarrier spacing of 3.75kHz. For 16, For 2, N RU For 1 and N slots The case where the value is 1. Based on the above physical resource mapping process and RV determination method, the physical resource mapping process shown in Figure 3 can be determined.

[0059] For Downlink Control Information (DCI) (e.g., DCI format N0):

[0060] The fields of the DCI for scheduling PUSCH include: modulation and coding scheme field, repeat digital segment, redundancy version field, TB digital segment for unicast scheduling, subcarrier indication field, resource reservation field, resource allocation field, scheduling delay field, new data indicator field, DCI subframe repeat digital segment, and Hybrid Automatic Repeat Request (HARQ) process digital segment. Each field is described in detail below:

[0061] The modulation and coding scheme field occupies 4 bits and indicates the modulation and coding index. Different indices correspond to a specific modulation and transport block size (TBS) index. When the CRC of DCI format N0 is scrambled by the Preconfigured Uplink Resource Radio Network Temporary Identifier (PUR-RNTI), the modulation and coding scheme field is absent. When npusch-16QAM-Config is configured and the modulation and coding scheme field indicates "1111", it represents a Quadrature Amplitude Modulation (QAM) modulation indicator.

[0062] The repeating number field occupies 3 bits and indicates the repeating number index. Different indices correspond to different repeating numbers. If 16QAM is indicated, the repeating number field is used as the modulation and coding scheme field.

[0063] The redundant version field occupies 1 bit and indicates the index associated with the redundant version.

[0064] The TB digital segment for unicast scheduling occupies 1 bit. The TB digital segment for unicast scheduling only exists when the higher-layer parameter npusch-MultiTB-Config is configured to be enabled and the corresponding DCI (Downlink Control Information Cyclic Redundancy Check, DCI CRC) is scrambled by the 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 the SPS C-RNTI, the TB digital segment is set to 0.

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

[0066] Table 2 shows the relationship between the subcarrier indication field and the allocated subcarrier set.

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

[0068] The resource allocation field occupies 3 bits and indicates the number of resource units, indexed from 0 to 7. Different indices correspond to different numbers of resource units.

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

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

[0071] The DCI subframe repeat digital segment occupies 2 bits and indicates the DCI repeat count;

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

[0073] Regarding uplink transmission gaps and gaps caused by NPRACH transmission (UL gap and Gaps around NPRACH):

[0074] In traditional Internet of Things (IoT), there are gaps: half-duplex (HD) gap and NPRACH gap.

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

[0076] The NPRACH gap occurs when the UE must halt ongoing continuous uplink transmissions to transmit NPRACH. These gaps are known to the UE (notified via broadcast signaling System Information Blocks (SIBs)), and these uplink NPRACH transmission gaps may also be included within 256ms. In this case, whether NPUSCH, NPRACH, or both are transmitted, the UE must stop transmitting uplink transmissions after 256ms to receive downlink (DL) information.

[0077] Due to the duration of these gaps, the orthogonality of the OCC code will be broken when the applied OCC code crosses the gap.

[0078] Regarding uplink timing advance gaps and segmented transmission (UL TA gaps and segment):

[0079] In traditional IoT, link budget is enhanced through repetition, including repetition of NPUSCH / NPRACH transmissions. In Release 17 (R17), when the number of repetitions is high, the 3rd Generation Partnership Project (3GPP) defines segmented transmission in the NTN, where the total repetition transmission is divided into multiple segments. Time / frequency adjustments can be performed on a segment-by-segment basis to handle synchronization drift caused by satellite motion. Between segments, some data transmission needs to be discarded to form a Type 3 gap, which can be used for Timing Advance (TA) adjustments. The discarded data transmissions on resources may correspond to a portion of data in a particular OCC (Optical Channel Control) cell, thus disrupting OCC orthogonality.

[0080] In this application embodiment, an information transmission and reception method, communication node and storage medium that can operate in the above-mentioned wireless communication system are provided. By determining the OCC extended information according to the OCC configuration information, the OCC extended information is sent to the second communication node, thereby improving the system capacity.

[0081] Figure 4 is a flowchart illustrating an information sending method according to an embodiment of this application. The information sending method provided in this embodiment is applied to a first communication node. The first communication node in this embodiment can be a terminal device. As shown in Figure 4, the information sending method provided in this embodiment includes steps 401-403.

[0082] In 401: Receive OCC configuration information sent by the second communication node.

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

[0084] In one embodiment, the OCC configuration information includes at least one of the following: a first indication for indicating whether the OCC function is enabled or disabled; a second indication for indicating whether the OCC is activated or deactivated; a third indication for indicating the OCC length; or a fourth indication for indicating the OCC sequence parameters, wherein the OCC sequence parameters include: the OCC sequence or the OCC index.

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

[0086] Optionally, the first indication may be indicated by higher-level signaling. For example, the higher-level signaling here may be RRC signaling.

[0087] Optionally, the second indication is indicated by at least one of the following fields in the DCI: modulation and coding scheme field, repeating digital segment, redundancy version field, unicast scheduled TB digital segment, subcarrier indication field, or resource reservation field.

[0088] Optionally, the second indication is used to indicate OCC activation or deactivation if 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 subcarrier spacing is configured to 15 kHz, wherein the subcarrier spacing is indicated by higher-layer parameters or by the uplink subcarrier spacing in the random access response grant; the subcarrier spacing is configured to 3.75 kHz, wherein the subcarrier spacing is indicated by higher-layer parameters or by the uplink subcarrier spacing in the random access response grant; or the DCI CRC is scrambled by C-RNTI.

[0089] Optionally, the third instruction can be a DCI instruction from higher-level signaling or a dispatch PUSCH.

[0090] Optionally, the third indication is used to indicate the OCC length when at least one of the following conditions is met, or the OCC length is a preset value: the first indication indicates that the OCC function is enabled or the first indication is configured; or the second indication indicates that the OCC is activated.

[0091] Optionally, the fourth indication may be indicated by one of the following methods: by at least one of the following fields in the DCI: modulation and coding scheme field, repeating digital segment, redundancy version field, unicast scheduled TB digital segment, subcarrier indication field, or resource reservation field; by 2 bits from at least one field or a newly added field, wherein the 2 bits are also used to indicate OCC activation or OCC deactivation; by the index set corresponding to the subcarrier indication field in the DCI, wherein the index set is also used to indicate OCC activation or OCC deactivation; by the index set corresponding to the subcarrier indication field in the DCI; or by an existing field in the DCI as a new indication field.

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

[0093] Optionally, the new indication field includes modulation and coding scheme and subcarrier indication fields to indicate the modulation and coding scheme index and the corresponding subcarrier index, or to indicate the subcarrier index and the corresponding modulation and coding scheme index, or to indicate the modulation and coding scheme index and the subcarrier index. Wherein, each modulation and coding scheme index 0 to A corresponds to subcarrier indices 0 to B; or, each subcarrier index 0 to B corresponds to modulation and coding scheme indices 0 to A; or, each modulation and coding scheme index 0 to C corresponds to subcarrier indices 0 to D; or, each subcarrier index 0 to D corresponds to modulation and coding scheme indices 0 to C.

[0094] For example, A can be 10, B can be 47, C can be 15, and D can be 18.

[0095] Optionally, for a single-carrier 3.75kHz 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.

[0096] Optionally, the fourth indication is used to indicate the OCC sequence parameters if 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 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 subcarrier spacing is configured to 15 kHz, wherein the subcarrier spacing is indicated by higher-layer parameters or by the uplink subcarrier spacing in the random access response grant; the subcarrier spacing is configured to 3.75 kHz, wherein the subcarrier spacing is indicated by higher-layer parameters or by the uplink subcarrier spacing in the random access response grant; or the DCI CRC is scrambled by C-RNTI.

[0097] In 402: Determine the extended information of OCC based on the OCC configuration information.

[0098] In 402, data or reference signals can be extended based on OCC configuration information to obtain OCC extended information.

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

[0100] In one implementation, the information after OCC extension includes a DMRS sequence. Correspondingly, the implementation process of 402 can be: determining the length of the DMRS sequence based on the OCC length in the OCC configuration information, and generating the DMRS sequence. In this implementation, the information transmission method provided in this embodiment may further include: determining the time slot subgroup for the first communication node to transmit or map the DMRS sequence based on the OCC sequence parameters in the OCC configuration information.

[0101] In another implementation, the information after OCC expansion includes the data after OCC expansion. Correspondingly, the implementation process of 402 can be as follows: the data after OCC expansion can be determined based on the OCC configuration information and the complex modulation symbols. In this implementation, the OCC sequence can be obtained based on the OCC configuration information, and the OCC sequence and the complex modulation symbols can be multiplied to obtain the data after OCC expansion.

[0102] In another implementation, the information after OCC expansion includes the OCC-expanded DMRS sequence. Correspondingly, the implementation process of 402 can be as follows: determine the length of the unexpanded DMRS sequence based on the OCC length in the OCC configuration information, obtain the OCC sequence based on the OCC configuration information, and determine the OCC-expanded DMRS sequence based on the OCC sequence and the unexpanded DMRS sequence. In this implementation, a dot product operation can be performed on the OCC sequence and the unexpanded DMRS sequence to obtain the OCC-expanded DMRS sequence.

[0103] In another implementation, the information after OCC extension includes the DMRS sequence after OCC extension. Correspondingly, the implementation process of 402 can be as follows: determine the frequency domain length of the DMRS sequence before extension based on the number of consecutive subcarriers, obtain the OCC sequence based on the OCC configuration information, and determine the DMRS sequence after OCC extension based on the OCC sequence and the DMRS sequence before extension.

[0104] In 403: Send the OCC-extended information to the second communication node.

[0105] Optionally, the first communication node can send the OCC-extended information to the second communication node through a physical resource mapping process. The specific implementation will be described in detail in subsequent embodiments.

[0106] Optionally, the OCC-extended data in this embodiment can 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: PUSCH messages on pre-configured uplink resources (PUR), contention-based Msg3 messages, four-step random access Msg3 messages, and two-step random access Msg B PUSCH messages in idle / connected / inactive states.

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

[0108] Figure 5 is a flowchart illustrating another information sending method provided in this application embodiment. Based on the embodiment shown in Figure 4 and various optional implementations, this embodiment details how to determine the OCC-extended information according to the OCC configuration information. In this embodiment, the OCC-extended information includes OCC-extended data. As shown in Figure 5, the information sending method provided in this embodiment includes steps 501-505.

[0109] In 501: Receive OCC configuration information sent by the second communication node.

[0110] The implementation process and technical principles of 501 and 401 are similar, and will not be repeated here.

[0111] In 502: Determine the OCC sequence parameters based on the OCC configuration information.

[0112] In 503: The OCC sequence is determined based on the OCC sequence parameters.

[0113] Optionally, the OCC sequence parameters can be determined according to the fourth instruction. Once the OCC sequence parameters are determined, the OCC sequence can be determined.

[0114] In 504: Based on the OCC sequence and the complex modulation symbols, determine the data after OCC expansion.

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

[0116] Optionally, the implementation process of 504 includes at least one of the following: extending the complex modulation symbols on each time-domain symbol block of the multiple time-domain symbol blocks obtained by dividing the complex modulation symbols with the OCC sequence to obtain the OCC-extended data; extending the complex modulation symbols on each time-slot block of the multiple time-slot blocks obtained by dividing the complex modulation symbols with the OCC sequence to obtain the OCC-extended data; or extending the complex modulation symbols on each repeating unit block of the multiple repeating unit blocks obtained by dividing the complex modulation symbols with the OCC sequence to obtain the OCC-extended data. It should be noted that extending the complex modulation symbols with the OCC sequence here refers to performing a multiplication operation on the complex modulation symbols and the OCC sequence.

[0117] Optionally, the step of determining the OCC-extended data based on the OCC sequence and the complex modulation symbols is determined if at least one of the following conditions is met: a first indication indicates that the OCC function is enabled or a first indication is configured; a second indication indicates that the OCC is activated; a third indication indicates a specific OCC length; the OCC length is determined as a specific OCC length according to the first indication and / or the second indication; a fourth indication indicates specific OCC sequence parameters; the subcarrier spacing is configured to 15 kHz, wherein the subcarrier spacing is indicated by higher-layer parameters or by the uplink subcarrier spacing in the random access response grant; the subcarrier spacing is configured to 3.75 kHz, wherein the subcarrier spacing is indicated by higher-layer parameters or by the uplink subcarrier spacing in the random access response grant; or the number of consecutive subcarriers is configured to multiple carriers, wherein the number of subcarriers is indicated by the subcarrier indication field in the DCI of the scheduled PUSCH.

[0118] In 505: Send the OCC-extended data to the second communication node.

[0119] Optionally, in this embodiment, the data after OCC expansion includes a second PUSCH codeword. The information transmission method provided in this embodiment further includes the following steps: the scrambling sequence of the first PUSCH codeword is scrambled once per OCC length or... After each repeated transmission, reinitialization is performed. N represents the mapping of the first PUSCH codeword before OCC extension. RU The number of repetitions of each resource unit; mapping the second PUSCH codeword to N RU,enH There are N resource units, of which N RU,enh N represents the number of resource units. RU,enh The number N of resource units mapped by the OCC length and the first PUSCH codeword RU Determined, for each N RU,enh One resource unit was transmitted Second-rate, length.

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

[0121] Optionally, the second PUSCH codeword is mapped to N. RU,enh Each resource unit includes any one of the following: mapped to N slots After a time slot, N should be repeated before continuing to map z(·) to the next time slot. slots Time slot Next, among them Equals 1, N represents the number of repetitions of consecutive time slots. slots Indicates the number of consecutive time slots; mapped to OCC length * N slots After a time slot, before continuing to map z(·) to the next time slot, the OCC length * N should be repeated. slots Time slot Second-rate, equal Length or

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

[0123] For the second PUSCH codeword corresponding to the j-th TB, in B consecutive time slots n i Transmission occurs during this process, where i = jB + b, b = 0, 1, ..., B-1. Redundant version rv associated with the TB idx (j) is determined as follows: rv idx (j) = 2 * mod(rv) enh +j,2), if Then L=1, and the second PUSCH codeword is related to rv idx (j) The associated part will be mapped to the assigned N. RU,enh The resource unit in the first Transmission is performed on each time slot. The number of time slots included in a resource unit, rv enh The redundant version field in the DCI is indicated or predefined. Indicates the number of consecutive subcarriers;

[0124] For the second PUSCH codeword corresponding to the j-th TB, in B consecutive time slots n i Transmission occurs during this process, where i = jB + b, b = 0, 1, ..., B-1. Redundant version rv associated with the TBidx (j) is determined as follows: rv idx (j) = 2 * mod(rv) enh +j,2), if Then L = 1, otherwise

[0125] With a subcarrier spacing of 3.75 kHz, in the uplink time slot associated with TB, time slot n i The mapping method is With a subcarrier spacing of 15kHz, in the uplink time slot associated with TB, time slot n i The mapping method is

[0126] The information transmission method provided in this embodiment can determine the OCC sequence parameters based on the OCC configuration information, determine the OCC sequence based on the OCC sequence parameters, determine the OCC extended data based on the OCC sequence and the complex modulation symbols, and send the OCC extended data to the second communication node, thereby improving the system capacity.

[0127] In another embodiment, the OCC-extended information includes the DMRS sequence. The implementation process of 402 can be as follows: according to the formula... The length of the DMRS sequence is determined, and the DMRS sequence is generated. Wherein, N represents the mapping of the first PUSCH codeword before OCC extension. RU The number of times a resource unit is repeated. N represents the number of time slots included in a resource unit. RU This indicates the number of resource units mapped to the first PUSCH codeword before OCC extension. The OCC length can be determined based on the OCC configuration information. The method for generating the DMRS sequence can be found in the relevant protocols.

[0128] In this embodiment, the DMRS sequence can be a time-division multiplexed DMRS sequence. Therefore, the information transmission 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 based on the OCC sequence parameters and the number of time slot subgroups; or determining the time slot subgroup for the first communication node to transmit or map the DMRS sequence based on the mapping relationship between the OCC sequence parameters and the time slot subgroups. The OCC sequence parameters can be determined based on the OCC configuration information.

[0129] This embodiment may also include 401 and 403, which will not be described in detail here.

[0130] In 403, this embodiment can send a DMRS sequence to a second communication node based on a determined time slot subgroup.

[0131] The information transmission 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.

[0132] In another embodiment, the OCC-extended information includes the OCC-extended DMRS sequence. The implementation of 402 may include any of the following:

[0133] According to the formula The length is determined by the DMRS sequence before expansion, and the DMRS sequence after OCC expansion is determined based on the OCC sequence and the DMRS sequence before expansion, where the OCC sequence is information determined according to the OCC configuration information. N represents the mapping of the first PUSCH codeword before OCC extension. RU The number of repetitions of each resource unit, N RU This indicates the number of resource units mapped by the first PUSCH codeword. Indicates the number of time slots included in a resource unit;

[0134] The frequency domain length of the DMRS sequence before expansion is determined based on the number of consecutive subcarriers; the DMRS sequence after OCC expansion is determined based on the OCC sequence and the DMRS sequence before expansion; or

[0135] The frequency domain length of the DMRS sequence before expansion is determined based on the number of consecutive subcarriers. The DMRS sequence after OCC expansion is determined based on the cyclic shift and the DMRS base sequence, where the cyclic shift is related to the OCC sequence.

[0136] This embodiment may also include 401 and 403, which will not be described in detail here.

[0137] Optionally, the DMRS in this embodiment can be a time-domain code division multiplexing DMRS or a frequency-domain code division multiplexing DMRS.

[0138] Optionally, the step of determining the extended OCC information based on the OCC configuration information is determined if at least one of the following conditions is met: a first indication indicates that the OCC function is enabled or a first indication is configured; a second indication indicates that the OCC is activated; a third indication indicates a specific OCC length; the OCC length is determined as a specific OCC length according to the first indication and / or the second indication; a fourth indication indicates a specific OCC sequence parameter; the subcarrier spacing is configured to 15 kHz, wherein the subcarrier spacing is indicated by higher-layer parameters or by the uplink subcarrier spacing in the random access response grant; the subcarrier spacing is configured to 3.75 kHz, wherein the subcarrier spacing is indicated by higher-layer parameters or by the uplink subcarrier spacing in the random access response grant; the number of consecutive subcarriers is configured to 1, wherein the number of subcarriers is indicated by the subcarrier indication field in the DCI of the scheduling PUSCH; or the number of consecutive subcarriers is configured to multiple carriers, wherein the number of subcarriers is indicated by the subcarrier indication field in the DCI of the scheduling PUSCH.

[0139] The information transmission method provided in this embodiment can perform OCC extension on the DMRS sequence, thereby improving system capacity.

[0140] In another embodiment, the OCC-extended information includes at least one of the following: a DMRS sequence, OCC-extended data, or an OCC-extended DMRS sequence. The information transmission method further includes at least one of the following: when the OCC-extended information is delayed, delaying based on an OCC group, wherein the OCC group is the longer of the OCC-extended data and the OCC-extended DMRS sequence; or after the OCC-extended information is delayed, delaying by a delay time, wherein the delay time is an integer multiple of the OCC alignment length, and the OCC alignment length is the duration of the OCC group.

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

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

[0143] Since the various gaps described above may cause OCC to be transmitted across gaps or the orthogonality of OCC to be destroyed due to the dropping of certain time slots / symbols, in this embodiment, the delay can be based on the OCC group and / or delayed by the delay time, thereby ensuring the orthogonality of OCC during transmission.

[0144] The above information sending method is illustrated below with several detailed embodiments.

[0145] In this embodiment, the method is applicable to the following PUSCH messages in NR, LTE, NB-IoT, and eMTC systems: PUSCH messages on pre-configured uplink resources (PUR), contention-based Msg3 messages, four-step random access Msg3 messages, and two-step random access Msg B PUSCH messages in idle / connected / inactive states. To enhance PUSCH capacity, one of the following methods can be considered.

[0146] For code division multiplexing:

[0147] The following example uses the first communication node as the UE. Assume the signal is X (X can be data or DMRS), and two UEs are multiplexed: UE1 OCC sequence [+1+1], UE2 OCC sequence [+1-1]. Each UE's signal is transmitted twice with identical content. UE1 and UE2 transmit signals X1 and X2 respectively on the same time-frequency domain resources. Therefore, the superimposed signals generated at the first and second repetition positions can be represented as Y1 and Y2, where Y1 = H1,1X1 + H2,1X2 and Y2 = H1,2X1 - H2,2X2, where Hm,n is the channel of UEm in the nth repetition. Assuming the channel remains consistent at different repetition positions, i.e., H1 = H1,1 = H1,2 and H2 = H2,1 = H2,2, then the signals of UE1 and UE2 can be demultiplexed and obtained as follows: X1 = (Y1 + Y2) / 2H1, X2 = (Y1 - Y2) / 2H2.

[0148] Figure 6 is a schematic diagram of signal acquisition in code division multiplexing provided in an embodiment of this application. As shown in Figure 6, X1 and X2 can be calculated as functions of Y1 and Y2 and their corresponding channel state information.

[0149] Example 1: Regarding OCC configuration information:

[0150] Example 1 mainly describes the implementation of multiple instructions.

[0151] The DCI field for scheduling PUSCH includes: modulation and coding scheme field, repeating digital segment, redundancy version field, TB digital segment for unicast scheduling, subcarrier indication field, resource reservation field, resource allocation field, scheduling delay field, new data indication field, DCI subframe repeating digital segment, HARQ process digital segment, antenna port field, DMRS port field, and time domain resource allocation field.

[0152] Regarding the OCC activation instruction (first instruction):

[0153] 1) The OCC enable indication (first indication) can be indicated by RRC signaling, such as 0 indicating that the OCC function is disabled and 1 indicating that the OCC function is enabled; or, 1 indicating that the OCC function is disabled and 0 indicating that the OCC function is enabled; or it can be indicated by the OCC length or OCC sequence parameters (such as the OCC index or OCC sequence). For example, when the OCC length is indicated as a valid value (such as OCC length of 2 or OCC length of 4), it indicates that the OCC function is enabled; otherwise, it indicates that the OCC function is disabled. Receive the OCC enable indication.

[0154] Regarding the OCC activation instruction (second instruction):

[0155] 2) OCC activation (second indication) is indicated by the DCI indication of the scheduling PUSCH (e.g., DCI format N0), such as by reinterpreting the above fields (e.g., modulation and coding scheme field, repeating digital segment, redundancy version field, TB digital segment of unicast scheduling, subcarrier indication field, resource reservation field, resource allocation field, scheduling delay field, new data indication field, DCI subframe repeating digital segment, HARQ process digital segment) or by adding new fields to indicate OCC activation or deactivation:

[0156] a. One bit in the field indicates whether the OCC is activated or deactivated (e.g., by reinterpreting the most significant bit (MSB) or least significant bit (LSB) of the relevant field, or by adding a new dedicated 1-bit field). 0 indicates OCC deactivation, and 1 indicates OCC activation; or, 1 indicates OCC deactivation, and 0 indicates OCC activation; for example:

[0157] a) Modulation coding scheme field, example:

[0158] i. When the OCC enable indicator is configured to enable the OCC function or when the OCC enable indicator is configured:

[0159] i) One bit is used to indicate OCC activation or deactivation. This may be considered part of the modulation coding scheme field or a new field;

[0160] ii) 3 bits are used to indicate the modulation and coding scheme;

[0161] ii. Otherwise, follow the relevant rules. For example, 4 bits are used to indicate the modulation and coding scheme.

[0162] b) Repeated number segments, example:

[0163] i. When the OCC enable indicator is configured to enable the OCC function or when the OCC enable indicator is configured:

[0164] i) One bit is used to indicate OCC activation or deactivation. This may be considered part of a repeating digit segment or a new field;

[0165] ii) Two bits are used to indicate the number of repetitions;

[0166] ii. Otherwise, follow the relevant rules. For example, 3 bits are used to indicate the number of repetitions.

[0167] c) Redundant version field, example:

[0168] i. When the OCC enable indicator is configured to enable the OCC function or when the OCC enable indicator is configured:

[0169] i) One bit is used to indicate OCC activation or deactivation. This may be considered part of a redundant version field or a new field.

[0170] ii) Set the redundant version to 0 or 2, or set the redundant version to cycle starting from 0 or 2;

[0171] ii. Otherwise, follow the relevant rules. For example, 1 bit is used to indicate a redundant version.

[0172] d) TB digital segments for unicast scheduling, example:

[0173] i. When the OCC enable indicator is configured to enable the OCC function:

[0174] i) One bit is used to indicate OCC activation or deactivation. This may be considered as part of the TB digital segment for unicast scheduling, or as a new field;

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

[0176] ii. Otherwise, follow the relevant rules. For example, 1 bit is used to indicate the number of TBs in the unicast scheduling.

[0177] e) Subcarrier indication field, example:

[0178] i) When the OCC enable indicator is configured to enable the OCC function or when the OCC enable indicator is configured, and / or when the subcarrier spacing is configured to 15kHz:

[0179] i) One bit is used to indicate OCC activation or deactivation. This may be considered part of the subcarrier indication field, or a new field.

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

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

[0182] ii. Otherwise, follow the relevant rules. For example, 6 bits are used to indicate the subcarrier.

[0183] Table 3 shows the subcarriers allocated for PUSCH when the subcarrier spacing is 15kHz.

[0184] f) Resource reservation field, example:

[0185] i. The OCC enable indicator is configured to enable the OCC function or the OCC enable indicator is configured as follows:

[0186] i) One bit is used to indicate OCC activation or deactivation. This may be considered part of the resource reservation field or a new field;

[0187] ii) Depending on the higher-layer parameters, reserved subframes are not considered NB-IoT uplink subframes. Alternatively, the configuration of reserved subframes in the higher-layer parameters can be ignored.

[0188] ii. Otherwise, follow the relevant rules. For example, 1 bit is used to indicate a reserved subframe.

[0189] g) New / Dedicated Fields:

[0190] i. The OCC enable indicator is configured to enable the OCC function or the OCC enable indicator is configured as follows:

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

[0192] ii. Otherwise, the newly added / dedicated field does not exist;

[0193] iii. OCC may not be enabled simultaneously with multi-TB scheduling. Alternatively, OCC may not be enabled simultaneously with resource reservation. For example, this might manifest as follows:

[0194] i) The newly added / dedicated field may not coexist with the TB digital segment of unicast scheduling. Alternatively, the newly added / dedicated field may not coexist with the resource reservation field. Alternatively, the UE does not expect the newly added / dedicated field to coexist with the TB digital segment of unicast scheduling. Alternatively, the UE does not expect the newly added / dedicated field to coexist with the resource reservation field.

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

[0196] b. The OCC activation indicator (second indicator) is used to indicate OCC activation or deactivation when at least one of the following conditions is met:

[0197] a) The OCC enable indicator (first indicator) indicates that the OCC function is enabled or the OCC enable indicator is configured;

[0198] b) When the subcarrier spacing is configured to 15kHz, the subcarrier spacing is indicated by higher-layer parameters or by the uplink subcarrier spacing in the random access response grant;

[0199] c) When the subcarrier spacing is configured to 3.75 kHz, wherein the subcarrier spacing is indicated by higher-layer parameters or by the uplink subcarrier spacing in the random access response grant; or

[0200] d) DCI CRC is scrambled by C-RNTI.

[0201] Regarding the OCC length indication (third indication):

[0202] 3) The OCC length (third indication) can be determined by the DCI indication of higher-layer signaling or scheduling PUSCH (reusing the above DCI fields or adding new fields), or implicitly by the first indication and / or the second indication:

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

[0204] a) An OCC enable indicator (first indicator) indicates that the OCC function is enabled or that an OCC enable indicator is configured; or

[0205] b) OCC activation indicator (second indicator) activates OCC;

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

[0207] a) An OCC enable indicator (first indicator) indicates that the OCC function is enabled or that an OCC enable indicator is configured; or

[0208] b) OCC activation indicator (second indicator) indicates that OCC is activated.

[0209] For OCC index / sequence indication (fourth indication):

[0210] 4) The OCC sequence index (fourth indicator) is indicated by the DCI indicator of the scheduling PUSCH (e.g., DCI format N1), such as by reinterpreting the above fields (e.g., modulation and coding scheme field, repeating digital segment, redundancy version field, TB digital segment of unicast scheduling, subcarrier indicator field, resource reservation field, resource allocation field, scheduling delay field, new data indicator field, DCI subframe repeating digital segment, and HARQ process digital segment) or by adding new fields to indicate the OCC index / sequence:

[0211] a. The OCC index / sequence is indicated by 1 bit of the field. 0 indicates OCC index 0, 1 indicates OCC index 1, or 1 indicates OCC index 0, 0 indicates OCC index 1; or 0 indicates OCC sequence [1 1], 1 indicates OCC sequence [1 -1], or 1 indicates OCC sequence [1 1], 0 indicates OCC sequence [1 -1]; for example,

[0212] a) Modulation coding scheme field, where the most significant or least significant bit is used as an OCC index / sequence indicator. Example:

[0213] i. When the OCC enable indicator (first indicator) is configured to enable the OCC function or the OCC enable indicator is configured, and / or the OCC activation indicator (second indicator) indicates that OCC is activated:

[0214] i) One bit is used to indicate the OCC index / sequence. This may be considered part of the modulation coding scheme field, or a new field;

[0215] ii) 3 bits are used to indicate the modulation and coding scheme.

[0216] ii. Otherwise, follow the relevant rules. For example, 4 bits are used to indicate the modulation and coding scheme.

[0217] b) Repeated number segments, example:

[0218] i. When the OCC enable indicator (first indicator) is configured to enable the OCC function or the OCC enable indicator is configured, and / or the OCC activation indicator (second indicator) indicates that OCC is activated:

[0219] i) One bit is used to indicate the OCC index / sequence. This may be considered part of a repeating number segment or a new field;

[0220] ii) 2 bits are used to indicate the number of repetitions.

[0221] ii. Otherwise, follow the relevant rules. For example, 3 bits are used to indicate the number of repetitions.

[0222] c) Redundant version field, example:

[0223] i. When the OCC enable indicator (first indicator) is configured to enable the OCC function or the OCC enable indicator is configured, and / or the OCC activation indicator (second indicator) indicates that OCC is activated:

[0224] i) One bit is used to indicate the OCC index / sequence. This may be considered part of a redundant version field or a new field;

[0225] ii) Set the redundant version to 0 or 2, or set the redundant version to cycle starting from 0 or 2.

[0226] ii. Otherwise, follow the relevant rules. For example, 1 bit is used to indicate a redundant version.

[0227] d) TB digital segments for unicast scheduling, example:

[0228] i. When the OCC enable indicator (first indicator) is configured to enable the OCC function or the OCC enable indicator is configured, and / or the OCC activation indicator (second indicator) indicates that OCC is activated:

[0229] i) One bit is used to indicate the OCC index / sequence. This may be considered as part of a TB digital segment for unicast scheduling, or as a new field;

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

[0231] ii. Otherwise, follow the relevant rules. For example, 1 bit is used to indicate the number of TBs in the unicast scheduling.

[0232] e) Subcarrier indication field, example:

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

[0234] i) One bit is used to indicate the OCC index / sequence. This may be considered part of the subcarrier indication field, or a new field;

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

[0236] ii. Otherwise, follow the relevant rules. For example, 6 bits are used to indicate the subcarrier.

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

[0238] f) Resource reservation field:

[0239] i. The OCC enable indicator (first indicator) is configured to enable the OCC function or the OCC enable indicator is configured, and / or the OCC activation indicator (second indicator) indicates that OCC is activated;

[0240] i) One bit is used to indicate the OCC index / sequence. This may be considered part of a resource reservation field or a new field;

[0241] ii) Depending on the higher-layer parameters, reserved subframes are not considered NB-IoT uplink subframes. Alternatively, the configuration of reserved subframes in the higher-layer parameters can be ignored.

[0242] ii. Otherwise, follow the relevant rules. For example, 1 bit is used to indicate whether to determine a reserved subframe based on higher-layer parameters.

[0243] g) New / Dedicated Fields:

[0244] i. When the OCC enable indicator (first indicator) is configured to enable the OCC function or the OCC enable indicator is configured, and / or the OCC activation indicator (second indicator) indicates that OCC is activated:

[0245] i) 1 bit is used to indicate the OCC index / sequence;

[0246] ii. Otherwise, the newly added / dedicated field does not exist;

[0247] iii. OCC may not be enabled simultaneously with multi-TB scheduling. Alternatively, OCC may not be enabled simultaneously with resource reservation. For example, this might manifest as follows:

[0248] i) The newly added / dedicated field may not coexist with the TB digital segment of unicast scheduling. Alternatively, the newly added / dedicated field may not coexist with the resource reservation field. Alternatively, the UE does not expect the newly added / dedicated field to coexist with the TB digital segment of unicast scheduling. Alternatively, the UE does not expect the newly added / dedicated field to coexist with the resource reservation field.

[0249] iv. The OCC enable indicator may not be configured simultaneously with the multi-TB scheduling enable indicator (e.g., npusch-MultiTB-Config). Alternatively, the OCC enable indicator may not be configured simultaneously with the resource reservation indicator (e.g., resourceReservationConfigUL).

[0250] h), or in other methods, the fields mentioned above occupy 2 bits:

[0251] i. The OCC enable indicator (first indicator) is configured to enable the OCC function or the OCC enable indicator is configured as follows:

[0252] i) Two bits are used to indicate the OCC index / sequence and OCC activation or deactivation, example:

[0253] “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.

[0254] ii. Otherwise, the newly added / dedicated field does not exist.

[0255] b. The index set corresponding to the field indicates the OCC index / sequence. For example, indexes a to b represent OCC index 0 or OCC sequence [1 1] (implicitly indicating OCC activation), indexes c to d represent OCC index 1 or OCC sequence [1 -1] (implicitly indicating OCC activation), and indexes e to f indicate OCC deactivation. Other indexes are reserved settings, and other correspondences are not excluded.

[0256] a) For example, the subcarrier indication field:

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

[0258] i) Indexes 0 to 18 represent OCC index 0 or OCC sequence [1 1], indices 19 to 37 represent OCC index 1 or OCC sequence [1 -1], and indices 38 to 56 represent OCC deactivation. At this time, the correspondence between the subcarrier indication field and the subcarrier set allocated for PUSCH is shown in Table 4. Other correspondences are not excluded.

[0259] ii. Otherwise, follow the relevant rules and instructions.

[0260] c. The OCC index / sequence is indicated by the index set corresponding to the field. For example, indexes a to b represent OCC index 0 or OCC sequence [1 1], and indexes c to d represent OCC index 1 or OCC sequence [1 -1]. Other indexes are reserved settings and other correspondences are not excluded.

[0261] a) For example, the subcarrier indication field:

[0262] i. When the OCC enable indicator (first indicator) is configured to enable the OCC function or when the OCC enable indicator is configured, the OCC activation indicator (second indicator) indicates that OCC is activated, and the subcarrier spacing is configured to 15kHz:

[0263] i) Indexes 0 to 18 represent OCC index 0 or OCC sequence [1 1], and indices 19 to 37 represent OCC index 1 or OCC sequence [1 -1]. In this case, the correspondence between the subcarrier indication field and the subcarrier set allocated for PUSCH is shown in Table 5. Other correspondences are not excluded.

[0264] ii. Otherwise, follow the relevant rules and instructions.

[0265] Table 4 shows a schematic diagram of the subcarriers allocated for PUSCH when the subcarrier spacing is 15kHz.

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

[0267] Table 4-1 shows another illustration of the subcarriers allocated for PUSCH when the subcarrier spacing is 15kHz.

[0268] Table 5 shows the subcarriers allocated for PUSCH when the subcarrier spacing is 15kHz.

[0269] d. In the above method, the reuse or addition of fields indicating the OCC index or OCC sequence is defined. The existence of these fields is affected by the relevant configurations defined in e, such as OCC enable indication and OCC activation indication. Similarly, the above method can also be described as follows: When the relevant configurations defined in e are configured, such as OCC enable indication and OCC activation indication, the original field's occupied bits exist as a new indication field. An example method is as follows:

[0270] a) When at least one of the conditions defined in e is met, at least one of the following is absent: the redundancy version field, the modulation and coding field, the subcarrier indication field, the resource reservation field, or the TB digital segment of unicast scheduling, and the following fields are indicated in the DCI:

[0271] i. OCC activation indicator, occupying 1 bit, 0 indicates deactivation of OCC, 1 indicates activation of OCC, or 1 indicates deactivation of OCC, 0 indicates activation of OCC;

[0272] ii. OCC index / sequence indicator, occupying 1 bit, 0 represents OCC index 0, 1 represents OCC index 1, and vice versa; or 0 represents OCC sequence [1 1], 1 represents OCC sequence [1 -1], and vice versa;

[0273] iii. Modulation and coding scheme and subcarrier indication, occupying 9 bits:

[0274] i) For a single-carrier 3.75kHz subcarrier spacing configuration: the effective index number of the modulation and coding scheme is 11, i.e., 0 to 10, and the effective index of the subcarrier is 0 to 47. The following method can be used:

[0275] a) Each index in the modulation and coding scheme indices 0-10 corresponds to subcarrier indices 0-47, resulting in 11 * 48 = 528 combinations. Since 9 bits may not be able to fully accommodate all 512 indices, one modulation and coding scheme index corresponds to a subset of subcarriers (i.e., the number of corresponding subcarriers is less than 48). This could be 0-31, 16-47, or one of the 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 and subcarrier indices is shown in Table 6. Table 6 is only an example and does not exclude other correspondences.

[0276] Table 6. A Relationship Between Modulation Coding Scheme and Subcarrier Indication Fields and Modulation Coding Scheme Index and Subcarrier Index.

[0277] (b) Alternatively, each index in subcarrier indices 0-47 corresponds to modulation and coding scheme indices 0-10, resulting in a total of 48 * 11 = 528 combinations. In this case, 9 bits may not be able to fully carry all 512 indices, meaning some subcarrier indices cannot correspond to all modulation and coding scheme indices. For example, some subcarrier indices might correspond to 0-2, 8-10, or certain subcarrier indices specified from 0-10. The relationship between the modulation and coding scheme and subcarrier indication fields and the subcarrier and modulation and coding scheme indices is shown in Table 7. Table 7 is only an example and does not exclude other correspondences.

[0278] Table 7. A Relationship Between Modulation Coding Scheme and Subcarrier Indication Fields and Subcarrier Index and Modulation Coding Scheme Index

[0279] ii) For a single-carrier 15kHz subcarrier spacing configuration: the effective index number of the modulation and coding scheme is 16, i.e., 0 to 15, and the effective index number of the subcarrier is 19, i.e., 0 to 18. The following method can be used:

[0280] a) Each index in the modulation and coding scheme indices 0 to 15 corresponds to a subcarrier index 0 to 18, resulting in a total of 16 * 19 = 304 combinations. In this case, 9 bits can fully carry (512 indices), including 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 an example and does not exclude other correspondences.

[0281] Table 8. Another relationship between the modulation coding and subcarrier indicator fields and the modulation coding index and subcarrier index.

[0282] (b) Each subcarrier index from 0 to 18 corresponds to a modulation and coding scheme index from 0 to 15, resulting in a total of 19 * 16 = 304 combinations. In this case, 9 bits can fully carry (512 indices), including reserved states. The relationship between the modulation and coding scheme and subcarrier indication fields and the subcarrier and modulation and coding scheme indices is shown in Table 9. Table 9 is only an example and does not exclude other correspondences.

[0283] Table 9 Modulation coding scheme and subcarrier indication fields, along with subcarrier index and modulation coding scheme index.

[0284] iv. The above fields exist or are used to indicate the corresponding function when at least one of the conditions defined in e is met.

[0285] e. The OCC index indicator (fourth indicator) is used to indicate the OCC index when at least one of the following conditions is met:

[0286] a) The OCC enable indicator (first indicator) indicates that the OCC function is enabled or the OCC enable indicator is configured;

[0287] b) OCC activation indicator (second indicator) activates OCC;

[0288] c) The OCC length indicator (third indicator) indicates the specific OCC length;

[0289] d) The OCC length is determined to be a specific OCC length according to a certain indication (such as a first indication or a second indication);

[0290] e) When the subcarrier spacing is configured to 15 kHz, the subcarrier spacing is indicated by higher-layer parameters or by the uplink subcarrier spacing in the random access response grant.

[0291] f) When the subcarrier spacing is configured to 3.75 kHz, wherein the subcarrier spacing is indicated by higher-layer parameters or by the uplink subcarrier spacing in the random access response grant; or

[0292] g) DCI CRC is scrambled by C-RNTI.

[0293] It should be noted that the OCC activation indicator and the OCC index indicator 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 and the MCS field to indicate the OCC index; or, using the MCS field to indicate OCC activation or deactivation and the RV field to indicate the OCC index; or, using the RV field to indicate OCC activation or deactivation and the resource reservation field to indicate the OCC index; or, using the resource reservation field to indicate OCC activation or deactivation and the RV field to indicate the OCC index; or, using the RV field to indicate OCC activation or deactivation and the new / dedicated field to indicate the OCC index; or, using... The OCC activation / deactivation indicator can be created using a new / dedicated field, with the RV field indicating the OCC index; or, the RV field can be used to indicate OCC activation / deactivation, with the TB segment of unicast scheduling indicating the OCC index; or, the TB segment of unicast scheduling can be used to indicate OCC activation / deactivation, with the RV field indicating the OCC index; or, the resource reservation field can be used to indicate OCC activation / deactivation, with the TB segment of unicast scheduling indicating the OCC index; or, the TB segment of unicast scheduling can be used to indicate OCC activation / deactivation, with the resource reservation field indicating the OCC index. In other words, the above OCC activation indication can be combined with the OCC index indication to represent different OCC activation and OCC index indication methods.

[0294] Example 2: For OCC applications or extended / chunked extensions:

[0295] Example 2 mainly describes the process of OCC extension or OCC application of complex modulation symbols based on OCC configuration information. In this example, OCC sequence parameters can be determined based on OCC configuration information, and an OCC sequence can be determined based on the OCC sequence parameters. Example 2 corresponds to the example shown in Figure 5. In this example, the complex modulation symbol is used as an example for illustration.

[0296] 5) OCC application or OCC extension, or using OCC for block extension, can be symbol-level (e.g., OCC application based on a single symbol granularity), 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 repeating unit granularity), and the application or extension operation is a multiplication operation.

[0297] a. OCC applications or extensions at the single-symbol granularity:

[0298] a) The modulated complex symbols are divided into multiple time-domain symbol blocks d(0),...,d(N-1), and the complex 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 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), containing one or more complex symbols, for example, 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 can be represented as a row vector w, for example, w = [w...]. 0 ,...,w Nocc-1 Nocc represents the OCC length. Therefore, the OCC application or OCC extension process might be represented as d(n)*w, for example, d(n)*w = [w 0 d(n),...,w Nocc-1 That is, expanding a time-domain symbol block d(n) into Nocc symbol blocks w. 0 d(n),...,w Nocc-1 After OCC application or OCC extension, N time-domain symbol blocks d(0),...,d(N-1) may be transformed into N*Nocc symbol blocks:

[0299] 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, assuming that after OCC application or OCC extension, we obtain N*Nocc symbol blocks y(0),...,y(N*Nocc-1), then the column vector y(i*Nocc+k) corresponding to the symbol blocks is w k d(i), where i = 0, ..., N-1, k = 0, ..., Nocc-1. After completing the OCC application or extension, resource mapping is then performed on the generated symbol blocks.

[0300] b. For OCC applications or extensions at the single time slot granularity:

[0301] a) The modulated complex symbols are divided into multiple time slot blocks a(0),...,a(S-1), and the complex symbol block in each time slot is 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. S is the number of time slot blocks before OCC application or OCC extension. The s-th time slot block can be represented as a column vector a(s), containing one or more complex modulation symbols, for example, represented as... Where M is the number of subcarriers, and a(s) represents the complex modulation symbols on all subcarriers across all time-domain symbols in a time slot block, i.e., a(s) consists of Nsymb1 d(n), where 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 The OCC application or OCC extension process might then be represented as a(s)*w, for example, a(s)*w=[w 0 a(s),,...,w Nocc-1 That is, expanding a time slot block a(s) into Nocc time slot blocks w. 0 a(s),...,w Nocc-1 a(s). After OCC application or OCC extension, S time slot blocks d(0),...,d(S-1) may be transformed into S*Nocc time slot blocks:

[0302] w 0 a(0),...,w Nocc-1 a(0),w 0 a(1),...,w Nocc-1 a(1),...,w 0 a(S-1),...,w Nocc-1 a(S-1). Alternatively, assuming that after OCC application or OCC expansion, 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 is w k a(i), where i = 0, ..., S-1, k = 0, ..., Nocc-1. After completing the OCC application or extension, resource mapping is then performed on the generated symbol blocks.

[0303] b) Alternatively, a) above can also be described as follows:

[0304] The modulated complex symbols are divided into multiple time slot blocks d(0),...,d(N-1), and the complex symbols in each time slot block are extended by the OCC sequence. In this embodiment, each time slot block corresponds to the complex symbols on all subcarriers in a time slot. N is the number of time slot blocks before OCC application or OCC extension. The nth time slot block can be represented as a column vector d(n), containing one or more complex symbols, for example, d(n) = [d 0 (n),...,d M-1 (n)] T Where M is the number of subcarriers multiplied by 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 a time slot. The OCC sequence w may be represented as a row vector w, for example, w = [w 0 ,...,w Nocc-1 The OCC application or OCC extension process might then be represented as d(n)*w, for example, d(n)*w=[w 0 d(n),...,w Nocc-1 That is, expanding a time slot block d(n) into Nocc time slot blocks w. 0 d(n),...,w Nocc-1 After OCC application or OCC extension, N time slot blocks d(0),...,d(N-1) may be transformed into N*Nocc time slot blocks:

[0305] 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, assuming that after OCC application or OCC expansion, N*Nocc time slot blocks y(0),...,y(N*Nocc-1) are obtained, then the column vector y(i*Nocc+k) corresponding to the time slot block is w k d(i), where i = 0, ..., N-1, k = 0, ..., Nocc-1. After completing the OCC application or extension, resource mapping is then performed on the generated symbol blocks.

[0306] c. OCC application or extension for a single repeating unit granularity or two consecutive time slot granularities:

[0307] a) The modulated complex symbols are divided into multiple repeating unit blocks or multiple consecutive time slot blocks b(0),...,b(O-1). The following explanation uses two consecutive time slots as an example. The complex symbol block on each repeating unit or two consecutive time slots is extended by the OCC sequence. O represents the number of time slot blocks before OCC application or extension. The o-th time slot block can be represented as a column vector b(o), containing one or more complex symbols, for example, represented as... Where M is the number of subcarriers, b(o) represents the complex modulation symbol on all subcarriers across all time-domain symbols in a repeating unit or two consecutive time slots, i.e., b(o) consists of Nsymb2 d(n), where Nsymb2 represents the number of time-domain symbols used to carry the complex modulation symbol in a repeating 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 The OCC application or OCC extension process might then be represented as b(o)*w, for example, b(o)*w=[w 0 b(o),,...,w Nocc-1 That is, expanding one repeating unit or two consecutive time slots b(o) into Nocc repeating units or two consecutive time slots w. 0 b(o),...,w Nocc-1 b(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, assuming that after OCC application or OCC extension, we obtain O*Nocc repeating units or two consecutive time slot blocks y(0),...,y(O*Nocc-1), then the column vector y(i*Nocc+k) corresponding to the repeating unit or time slot block = w k b(i), where i = 0, ..., O-1, k = 0, ..., Nocc-1. After completing the OCC application or extension, resource mapping is then performed on the generated symbol blocks.

[0308] b) Alternatively, a) above can also be described as follows:

[0309] The modulated complex symbols are divided into multiple consecutive two-slot blocks d(0),...,d(N-1), and the complex symbols in each consecutive time slot block are extended by the OCC sequence. N is the number of consecutive time slot blocks before OCC application or extension. The nth consecutive time slot block can be represented as a column vector d(n), containing one or more complex symbols, for example, 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 consecutive time slots, or M is the number of subcarriers * the number of time-domain symbols carrying complex modulation symbols in time slots * the number of consecutive time slots, and d(n) represents the complex modulation symbols on all subcarriers in consecutive time slots. The OCC sequence w may be represented as a row vector w, for example, w = [w 0 ,...,w Nocc-1 The OCC application or OCC extension process might then be represented as d(n)*w, for example, d(n)*w=[w 0 d(n),...,w Nocc-1 [d(n)] That is, expanding a continuous time slot block d(n) into Nocc continuous time slot blocks w. 0 d(n),...,w Nocc-1 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-1 d(0),w 0 d(1),...,w Nocc-1 d(1),...,w 0 d(N-1),...,w Nocc-1 d(N-1). Alternatively, assuming that after OCC application or OCC extension, N*Nocc consecutive time slot blocks y(0),...,y(N*Nocc-1) are obtained, then the column vector y(i*Nocc+k) corresponding to the consecutive time slot blocks is w k d(i), where i = 0, ..., N-1, k = 0, ..., Nocc-1. After completing the OCC application or extension, resource mapping is then performed on the generated symbol blocks.

[0310] 6) The above defines various OCC application or extension schemes. To use a particular OCC application or extension scheme, at least one of the following conditions must be met:

[0311] a. The OCC enable indicator (first indicator) indicates that the OCC function is enabled or that the OCC enable indicator is configured.

[0312] b. OCC activation indicator (second indicator) activates OCC;

[0313] c. The OCC length indicator (third indicator) indicates a specific OCC length;

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

[0315] e. The OCC index indicator (fourth indicator) indicates a specific OCC index;

[0316] f. When the subcarrier spacing is configured to 15kHz, the subcarrier spacing is indicated by higher-layer parameters or by the uplink subcarrier spacing in the random access response grant.

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

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

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

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

[0321] a. The current protocol stipulates that each first PUSCH codeword can be mapped to one or more resource units, N RU Indicates the number of resource units, per N RU One resource unit was transmitted N times, of which RU Indicated by the resource allocation field in the DCI of the PUSCH scheduler. Indicated by the repeating digital segment of the DCI that schedules PUSCH. N represents the mapping of the first PUSCH codeword before OCC extension. RU The number of repetitions per resource unit. When applying OCC, the following methods should be used for enhancement:

[0322] a) The scrambling sequence of the first PUSCH codeword will be scrambled once every OCC length or Next or Reinitialization is performed after each repeated transmission, which is suitable for single-carrier or multi-carrier transmission.

[0323] b) The second PUSCH codeword can be mapped to one or more resource units, where the number of resource units N is... RU,enh Extended by the length of OCC, for example, N RU,enh equals N RU *OCC length; per N RU,enh One resource unit was transmitted Next, among them length;

[0324] i. For monophonic transmission, the physical resource mapping method is the same as that of related protocols, i.e. It equals 1;

[0325] ii. For multi-audio transmission, the physical resource mapping method is relevant. equal to 1 or equal Length or

[0326] 1. Mapping to N slots After a time slot, N should be repeated before continuing to map z(·) to the next time slot. slots Time slot Second-rate, Equal to 1; or,

[0327] 2. Map to OCC length * N slots After a time slot, before continuing to map z(·) to the next time slot, the OCC length * N should be repeated. slots Time slot Second-rate, equal Length or

[0328] c) Furthermore, in the relevant protocol, each transmission The RV is updated once per time slot. When applying OCC, the following methods should be used to enhance the relevant calculations:

[0329] i. Among them, and Regarding multi-tone transmission, or

[0330] 1. Transmission occurs in N time slots of the NB-IoT uplink, and these time slots are represented by n. iLet 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. i i = jB + b, b = 0, 1, ..., B-1, in Redundant version rv associated with TB idx (j) is determined as follows: rv idx (j) = 2 * mod(rv) enh +j,2), where if Then L = 1. The second PUSCH codeword is related to rv. idx (j) The associated part will be mapped to the assigned N. RU,enh The first resource unit (RU) in Transmission occurs on each time slot. When the subcarrier spacing is Δf = 3.75kHz, the time slot mapping method in the NB-IoT uplink time slot associated with TB is as follows: When the subcarrier spacing is Δf = 15kHz, the slot mapping method in the NB-IoT UL slots associated with TB is as follows: rv enh The redundant version field in the DCI indicates, or is set by default, to start from 0 or 2. And / or,

[0331] 2. Transmission occurs in N time slots of the NB-IoT uplink, and these time slots are represented by n. i Let 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. i i = jB + b, b = 0, 1, ..., B-1, in The redundant version (rv) associated with this TB idx (j) is determined as follows: rv idx (j) = 2 * mod(rv) enh +j,2), where if Then L = 1, otherwise The second PUSCH codeword is related to rv idx (j) The associated part will be mapped to the assigned N. RU,enh The first resource unit (RU) in Transmission occurs on each time slot. When the subcarrier spacing is Δf = 3.75kHz, the time slot mapping method in the NB-IoT uplink time slot associated with TB is as follows: When the subcarrier spacing is Δf = 15kHz, the slot mapping method in the NB-IoT UL slots associated with TB is as follows: rv enh The redundant version field in DCI indicates or is set to start from 0 or 2 by default.

[0332] b. Current number of repetitions The number of repetitions is determined by the repeating digits in the DCI of the PUSCH scheduler. However, after OCC extension, the determination of the number of repetitions indicated by the DCI can be done using one of the following methods:

[0333] a) Extend the number of repetitions indicated by DCI. For example, when the number of repetitions indicated by DCI is 8, after extension by OCC length of 2, the actual number of repetitions is extended to 16, and the corresponding physical resource mapping method remains unchanged.

[0334] Example 3: Determining the location of DMRS:

[0335] In this embodiment, the information after OCC extension includes the DMRS sequence or the extended DMRS sequence.

[0336] In traditional operations, users do not support time-division multiplexing and code-division multiplexing. DMRS is transmitted on DMRS symbols in each time slot of the time-frequency resource (that is, a user will occupy all DMRS symbols in all time slots of a single transmission). The length of its DMRS sequence is determined by the number of repetitions, the number of time slots contained in the uplink resource unit, and the number of uplink resource units.

[0337] When configuring different subcarrier intervals 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, and frequency domain code division multiplexing DMRS scheme.

[0338] For Time Division Multiplexing (DMRS): The length of the DMRS sequence is calculated as follows: The length, i.e. the length of the DMRS sequence, is scaled by the OCC length. The DMRS sequence is generated according to the method defined by the relevant protocol. Each terminal uses DMRS symbols on different time slots to transmit DMRS. The terminal only occupies DMRS symbols on a portion of the time slots for DMRS transmission, as defined in 8).

[0339] For Time-Domain Code Division Multiplexing (DMRS): The length of the DMRS sequence is calculated as follows: The length, i.e. the length of the DMRS sequence, is scaled by the OCC length. After the DMRS sequence is generated according to the method defined by the relevant protocol, the OCC expands each DMRS sequence element. Each terminal uses DMRS symbols on the same time slot to transmit DMRS. The terminal occupies all the DMRS symbols on the time slot in a transmission to transmit DMRS.

[0340] For 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 the cyclic shift. Each terminal uses DMRS symbols on the same time slot to transmit DMRS. The terminal occupies all DMRS symbols on all time slots in a transmission to transmit DMRS. The cyclic shift used by each terminal is related to the OCC index or the 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, or OCC index 1 corresponds to cyclic shift index 0 or cyclic shift value m, OCC index 0 corresponds to cyclic shift index 1 or cyclic shift value n; 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.

[0341] 8) For Time Division Multiplexing (DMRS), TDM DMRS based on time slot group transmission / mapping is supported (DMRS is transmitted only on DMRS symbols in time slots, and data information (such as PUSCH data) is transmitted on non-DMRS symbols):

[0342] a. The DMRS of each terminal is transmitted or mapped on which DMRS symbol in each 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, number of time slot subgroups in each time slot group);

[0343] b. Alternatively, the DMRS of a terminal with OCC index 0 is transmitted on the DMRS symbols of time slot subgroup 1 in each time slot group, and the DMRS of a terminal with OCC index 1 is transmitted on the DMRS symbols of time slot subgroup 2 in each time slot group; or, the DMRS of a terminal with OCC index 1 is transmitted on the DMRS symbols of time slot subgroup 1 in each time slot group, and the DMRS of a terminal with OCC index 0 is transmitted on the DMRS symbols of time slot subgroup 2 in each time slot group; or, the DMRS of a terminal with OCC index 0 is transmitted on the DMRS symbols of the first two time slots in each time slot group, and the DMRS of a terminal with OCC index 1 is transmitted on the DMRS symbols of the last two time slots in each time slot group; or, the DMRS of a terminal with OCC index 1 is transmitted on the DMRS symbols of the first two time slots in each time slot group, and the DMRS of a terminal with OCC index 0 is transmitted on the DMRS symbols of the last two time slots in each time slot group, wherein each time slot group contains 4 consecutive time slots:

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

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

[0346] c) Each time slot subgroup may contain one or n consecutive time slots:

[0347] i. Figure 7 is a schematic diagram of the transmission / mapping / multiplexing of the DMRS sequence provided in the embodiments of this application. As shown in Figure 7, assuming that one 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 terminal 1's DMRS 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, number of time slot subgroups in each time slot group) = mod(0,2) = 0, that is, terminal 1's DMRS is transmitted on time slot subgroup 1 in each time slot group. Similarly, terminal 2's DMRS is transmitted on time slot subgroup 2 in each time slot group, while terminal 1's DMRS on time slot subgroup 2 in each time slot group is omitted or discarded, and terminal 2's DMRS on time slot subgroup 1 in each time slot group is omitted or discarded. Here, the DMRS only occupies one or more DMRS symbols in each time slot of the time slot subgroup, and the DMRS symbols are generally predefined by the standard.

[0348] Figure 8 is a schematic diagram of the time slot expansion of the DMRS sequence transmission / mapping / multiplexing provided in the embodiments of this application. The DMRS transmission / mapping / multiplexing of two users based on the time slot group after time slot expansion is shown in Figure 8. The shaded symbols represent the DMRS symbols. In Figure 8, the DMRS of user 1 is the same as the DMRS of terminal 1 in Figure 7, and the DMRS of user 2 is the same as the DMRS of terminal 2 in Figure 7.

[0349] c. At least one of the schemes defined in Example 3 above shall be adopted when at least one of the following conditions is met:

[0350] a) The OCC enable indicator (first indicator) indicates that the OCC function is enabled or the OCC enable indicator is configured;

[0351] b) OCC activation indicator (second indicator) activates OCC;

[0352] c) The OCC length indicator (third indicator) indicates the specific OCC length;

[0353] d) The OCC length is determined to be a specific OCC length according to a certain indication (such as a first indication or a second indication);

[0354] e) The OCC index indicator (fourth indicator) indicates a specific OCC index;

[0355] f) When the subcarrier spacing is configured to 15 kHz, the subcarrier spacing is indicated by higher-layer parameters or by the uplink subcarrier spacing in the random access response grant.

[0356] g) When the subcarrier spacing is configured to 3.75 kHz, the subcarrier spacing is indicated by higher-layer parameters or by the uplink subcarrier spacing in the random access response grant;

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

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

[0359] Example 4: Addressing OCC Delay Caused by Transmission Gaps:

[0360] This embodiment mainly describes how, when 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.

[0361] During resource mapping, mechanisms to avoid resource collisions or provide synchronization opportunities may be introduced to reduce transmission delays. For example, in NB-IoT uplink transmission, the following delay mechanisms exist:

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

[0363] 2. In Frequency Division Duplex (FDD) or Frame Structure 1, a 40ms uplink interval is inserted every 256ms of NPUSCH transmission (including the delay caused by NPRACH), and the corresponding NPUSCH transmission is delayed. Moreover, the portion of the delay caused by NPRACH that overlaps with the uplink interval is included in the uplink interval.

[0364] 3. In IoT-NTN TDD mode, if NPUSCH or NPRACH overlaps with a non-uplink transmission time, the corresponding NPUSCH or NPRACH transmission will be delayed until the time resources for the next uplink transmission time are available.

[0365] To ensure the orthogonality of OCCs, different UEs need to maintain OCC alignment. This OCC alignment may include:

[0366] 1. (Data) OCC Group Alignment. For example, when OCC is applied in N time units (e.g., two consecutive time slots, time slots, symbols, subframes, etc.), these N time units can be called an OCC group. The (data) OCC groups of different UEs need to be aligned to ensure OCC orthogonality. It should be noted that the (data) OCC group here is the data after OCC extension in the aforementioned embodiment;

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

[0368] i) When using Code Division Multiplexing (DMRS), the DMRS groups of different UEs need to be aligned to ensure DMRS orthogonality. For example, N time slots may be grouped into one time slot group, and an N-length OCC code may be applied to the DMRS within the time slot group. In this case, the time slot groups of different UEs need to be aligned to ensure the orthogonality of the Code Division Multiplexing (DMRS).

[0369] ii. When using Time Division Multiplexing (TDM) DMRS, the DMRS groups of different UEs need to be aligned to ensure DMRS orthogonality. For example, as shown in Example 3, N time slots may be combined into a time slot group and further divided into Y time slot subgroups. Each UE may transmit DMRS on one of the subgroups and not transmit DMRS on the other subgroups. In this case, the time slot groups of different UEs need to be aligned or have a fixed time offset to ensure the orthogonality of the time division DMRS.

[0370] It should be noted that the DMRS group here refers to the DMRS sequence in the aforementioned embodiments or the DMRS sequence after OCC extension.

[0371] It is worth noting that (data)OCC group alignment and DMRS group alignment may correspond to different time lengths. OCC alignment may be based on the longest alignment length or the least common multiple of different alignment methods. For example, assuming that data transmission uses symbol-based OCC (length 2), while DMRS transmission uses time-division DMRS (4 time slots per group, 2 time slots per subgroup), then the (data)OCC group alignment length is 2 symbols, while the DMRS group alignment length is 4 time slots. In this case, the system may need to consider alignment based on 4 time slots.

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

[0373] To address the potential problems with the aforementioned delay mechanism, this embodiment introduces the following new delay mechanism.

[0374] 9) In the event of a delay, the delay should be based on the OCC group (e.g., the N mentioned in the standard protocol). slots One time slot changed to N slot,occ (N time slots). This ensures the integrity of the OCC group or DMRS group. The OCC group (duration is N) slot,occ Each time slot may be the longer of the (data) OCC group and DMRS group. For example, for a 3.75kHz subcarrier spacing, N slot,occ = 2 * OCClength; For a 15kHz subcarrier spacing, N slot,occ =OCClength or N slot,occ =N slots *OCC length For example, a delay might be implemented according to the following process:

[0375] a. (When OCC is enabled or activated) For PUSCH transport, if the mapped N slot,occ If a time slot contains resource elements that overlap or partially overlap with NPRACH resources, then these N... slot,occ PUSCH transmissions on each time slot are delayed until the next N-slot that does not overlap with NPRACH resources. slot,occ Each time slot.

[0376] b. (When OCC is enabled or activated) For PUSCH transfers, if the mapped N slot,occ If a time slot contains resource elements that overlap or partially overlap with the uplink interval, then these N time slots will be... slot,occ PUSCH transmissions on each time slot are delayed until the next N-slot that does not overlap with the uplink slot. slot,occ Each time slot.

[0377] c. (When OCC is enabled or activated) For PUSCH transport, if the mapped N slot,occ If a time slot contains resource elements that overlap or partially overlap with non-uplink time slots, then these N time slots will be... slot,occ PUSCH transmissions on each time slot are delayed until the next N-slot that does not overlap with a non-uplink time slot. slot,occ Each time slot.

[0378] d. (When OCC is enabled or activated) For PUSCH transfers, 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 the PUSCH transmissions on these N slots,occ time slots will be delayed until the next N slot that does not overlap with NPRACH resources or uplink intervals. slot,occ Each time slot.

[0379] It should be noted that in 9), when a delay occurs, N is used. slot,occ Each time slot is used as the smallest transmission unit for delayed transmission.

[0380] 10) After a delay occurs, the delay time must be an integer multiple of the OCC alignment length. The OCC alignment length is the duration of the OCC group. This ensures that the UEs can still maintain OCC alignment. Figure 10 is a schematic diagram of another information delay after OCC extension provided in an embodiment of this application. As shown in Figure 10, the PUSCH transmission of the first UE is delayed by an additional 4ms to ensure OCC alignment, so that the total delay is an integer multiple of the OCC alignment length (4 slots, 8ms). The total delay of the PUSCH transmission of the second UE is 48ms, 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.

[0381] During implementation, delays may be made based on the following criteria:

[0382] a. The first time slot of the delayed PUSCH transmission satisfies n s mod N slot,occ=X. Where X may be a protocol predefined value (e.g., predefined as 0), a network-side indication / configuration, determined by the start time of the entire PUSCH, or determined by the resources mapped before the delay. For example, X = n s,initial mod N slot,occ , where n s,initial This is the first time slot of the entire PUSCH transmission. Alternatively, X = n s,old mod N slot,occ , where n s,old This refers to the first time slot mapped before the PUSCH transmission delay. The implementation process might be as follows:

[0383] a) (When OCC is enabled or activated) For PUSCH transport, if the mapped N slot,occ If a time slot contains resource elements that overlap or partially overlap with NPRACH resources, then these N... slot,occ PUSCH transmissions on each time slot are delayed until the next N-slot that does not overlap with NPRACH resources. slot,occ There are n time slots, and the first time slot satisfies n s mod N slot,occ =X.

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

[0385] c) (When OCC is enabled or activated) For PUSCH transport, 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 each time slot are delayed until the next N-slot that does not overlap with NPRACH resources or uplink intervals. slot,occ There are n time slots, and the first time slot satisfies n s mod N slot,occ =X.

[0386] b. N of the delayed PUSCH transmission slot,occ The first time slot n in a time slot s Compared to its previous state N slot,occ The first time slot n in a time slot s,old , satisfying (n s-n s,old )mod N slot,occ =0. Where ns is the index of the first time slot after the delay, n s,old This is the index of the first time slot before the delay. Considering factors such as system frame wraparound, the influence of the radio frame number or superframe number may also need to be taken into account. For example:

[0387] a) N of the delayed PUSCH transmission slot,occ The first time slot n in a time slot s Compared to its previous state N slot,occ The first time slot n in a time slot s,old It needs to satisfy ((SFN) s -SFN s,old )*N slot,num +n s -n s,old )mod N slot,occ = 0, where SFNs is the index of the radio frame or system frame in which the first time slot after the delay is located, SFN s,old N is the index of the radio frame or system frame in which the first time slot before the delay occurs. slot,num The number of time slots within a radio frame or system frame.

[0388] b) Or, the delayed PUSCH transmission of N slot,occ The first time slot n in a time slot s Compared to its previous state N slot,occ The first time slot n in a time slot s,old It needs 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 H-SFN is the index of the superframe in which the first time slot after the delay belongs. s,old N is the index of the superframe in which the first time slot before the delay is located. SFN,num This refers to the number of radio frames within a superframe. H-SFN stands for Hyper SFN, and a superframe contains 1024 radio frames, or system frames.

[0389] 11) When at least one of the following conditions is met, delay the transmission of PUSCH using one of the above methods:

[0390] a. The OCC enable indicator (first indicator) indicates that the OCC function is enabled or that the OCC enable indicator is configured.

[0391] b. OCC activation indicator (second indicator) activates OCC;

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

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

[0394] e. The OCC index indicator (fourth indicator) indicates a specific OCC index;

[0395] f. When the subcarrier spacing is configured to 15kHz, the subcarrier spacing is indicated by higher-layer parameters or by the uplink subcarrier spacing in the random access response grant.

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

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

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

[0399] Example 3 can guarantee that the delay is based on the OCC group and / or the delay time, thereby ensuring the orthogonality of the OCC during the transmission process.

[0400] Figure 11 is a schematic flowchart of an information receiving method provided in an embodiment of this application. The information receiving method provided in this embodiment is applied to a second communication node. The second communication node in this embodiment can be an access network device. As shown in Figure 11, the information receiving method provided in this embodiment includes the following steps 1101-1102.

[0401] In 1101: Send OCC configuration information to the first communication node.

[0402] The implementation method of OCC configuration information in this embodiment can refer to the aforementioned embodiment, and will not be repeated here.

[0403] In 1102: Receive the OCC-extended information sent by the first communication node.

[0404] Among them, the information after OCC extension is the information determined by the first communication node according to the OCC configuration information.

[0405] The process by which the first communication node determines the extended information of the OCC based on the OCC configuration information can be referred to the aforementioned embodiment, and will not be repeated here.

[0406] The information receiving method provided in this embodiment improves system capacity by sending OCC configuration information to a first communication node and receiving OCC-extended information sent by the first communication node. The OCC-extended information is determined by the first communication node based on the OCC configuration information.

[0407] The following describes a method for uplink transmission.

[0408] Figure 12 is a schematic flowchart of an uplink transmission method provided in an embodiment of this application. The uplink transmission method is applied to a first communication node. In this embodiment, the first communication node 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 shown in Figure 12, the uplink transmission method includes the following steps 1201-1202.

[0409] In 1201: The first communication node determines the uplink channel configuration to carry uplink transmission.

[0410] In 1202: The first communication node sends the uplink channel carrying the uplink transmission.

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

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

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

[0414] Type I uplink transmission; wherein, Type I uplink transmission includes one of the following: contention-based uplink data transmission, contention-based Msg3 transmission, or, contention-based Type I random access first message transmission; or

[0415] Type II uplink transmission; wherein Type II uplink transmission includes one of the following: the first message (preamble) of contention-based Type II random access, or the first message transmission of contention-based Type I random access.

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

[0417] In one embodiment, the high-level information includes one of the following: public information (such as system message SIB); RRC release message; or switching configuration information.

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

[0419] 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; or the configured transmit power of the transmission.

[0420] In one embodiment, the transmission power parameter of the uplink channel used to carry the first type of uplink transmission is determined by at least one of the following parameters: first type of uplink transmission power control configuration information, the number of retransmissions of the first type of uplink transmission, or second type of uplink transmission power control configuration information.

[0421] In one embodiment, the target received power of the uplink channel used to carry the first type of uplink transmission is determined by one of the following parameters: the initial target received power of the uplink channel used to carry the first type of uplink transmission, or the number of retransmissions.

[0422] In one embodiment, the final transmit power of the uplink channel used to carry the first type of uplink transmission is determined by one of the following parameters: the number of retransmissions, or the transmission power boost value.

[0423] In one embodiment, the target received power of the uplink channel used to carry the first type of uplink transmission is determined by one of the following parameters: the number of retransmissions, or the initial target received power of the second type of transmission.

[0424] In one embodiment, the first transmission node switches from the first type of uplink transmission to the second type of uplink transmission when one of the following conditions is met: when the number of first type of uplink transmissions is greater than the maximum allowed number of retransmissions; or, when the number of first type of uplink transmissions is equal to the maximum allowed number of retransmissions, but is considered a transmission failure.

[0425] In one embodiment, the transmit power parameter of the uplink channel used to carry 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; or the number of retransmissions of the first type of uplink transmission.

[0426] In one embodiment, the first transmission node sends multiple copies for a single transmission when one of the following conditions is met: when the number of copies supported by a transmission indicated by the second communication node is greater than 1; or when the second communication node sends an enable message.

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

[0428] In one embodiment, when the first transmission node sends multiple copies for a single transmission, the number of repetitions supported by each copy is determined by one of the following methods: the second communication node is configured via higher-layer signaling; the number of repetitions for each copy is determined by the number of copies supported by a transmission and the number of repetitions for a transmission; or, the number of repetitions for each copy is the same as the number of repetitions for a transmission.

[0429] The following detailed embodiment illustrates the above process.

[0430] Example 5: A method for uplink transmission.

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

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

[0433] Obtain the resource configuration information required for uplink channel transmission, wherein the resource configuration information includes at least one of the following:

[0434] a. Time-domain or frequency-domain resource locations used by the uplink channel to carry transmission (such as Type I transmission); In some embodiments, the base station can configure more than one time-domain or frequency-domain resource location (i.e., the resource location occupied by the uplink channel), such as configuring a set of resources that can be used when the uplink channel is transmitted through a set or list, wherein any item in the set or list represents a set of resource information:

[0435] a) For example, a frequency domain resource bitmap, subcarrier, or PRB resource information represents a frequency domain resource used for transmission;

[0436] b) A temporal resource can be represented by a symbol, time slot, subframe information, or resource start position and length.

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

[0438] a) In some embodiments, a copy of a transmission refers to a transmission carried by the uplink channel after resource selection in the configured resources (resource pool).

[0439] b) In some embodiments, the terminal can randomly select one or more resources (time domain or frequency domain resources) from a configured pool of resources for one or more copy transmissions. Figure 14 is a schematic diagram of the transmission resources corresponding to two copies of a transmission provided in an embodiment of this application. As shown in Figure 14.

[0440] In some embodiments, the base station allows (enables or configures) the terminal to transmit multiple copies by one of the following methods.

[0441] Option 1: When a transmission is configured to support more than one replica (e.g., N is a number greater than one).

[0442] Option 2: When a number of replicas supported by a transmission is configured (e.g., N is a number greater than or equal to one); in this case, when N=1, it means that the terminal can only perform one replica transmission.

[0443] Option 3: When instructions are given via higher-level information, such as enable signaling:

[0444] i. In some embodiments, the enabling signaling is a multi-copy transmission enabling signaling;

[0445] ii. In some embodiments, the enabling signaling is a first type of transmission enabling signaling.

[0446] The first type of transmission includes one of the following:

[0447] i) Contention-based uplink data transmission (such as PUSCH, NPUSCH);

[0448] ii) Contention-based Msg3 transmission; or

[0449] iii) Transmission of the first message (Msg-A) of the first type of random access based on contention.

[0450] c. The number of repetitions of a transmission (M, where M is a number greater than or equal to 1). In some embodiments, the repetition of a transmission refers to the number of repetitions contained in the uplink channel carrying the transmission.

[0451] 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 for each copy is:

[0452] Option 1: The base station configures parameters through higher-layer signaling, such as setting the repetition count for each configuration to L;

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

[0454] Option 3: The number of repetitions supported by the nth replica is M. Figure 15 is a schematic diagram of the transmission of two replicas corresponding to one transmission provided in an embodiment of this application. As shown in Figure 15, the number of repetitions for each replica is M = 3;

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

[0456] In some embodiments, a retransmission of a transmission refers to the retransmission of the channel carrying the transmission.

[0457] In some embodiments, the maximum number of retransmissions allowed for a transmission refers to the number of times the terminal retransmits the transmission:

[0458] a) In some embodiments, retransmission by the terminal for a transmission includes retransmission of the transmission after the terminal has not received a response information (such as scheduling information) from the base station for the retransmission under predetermined conditions (such as within a time window).

[0459] b) In some embodiments, when the base station allows (enables or configures) the terminal to send multiple copies of a transmission, the maximum allowed number of retransmissions for that transmission is:

[0460] Option 1: The maximum number of retransmissions allowed in a single transmission (C);

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

[0462] Figure 16 is a schematic diagram of a second type of uplink transmission provided in an embodiment of this application when the first type of uplink transmission reaches the maximum number of retransmissions and the transmission fails. In some embodiments (as shown in Figure 16), when the terminal transmission fails, such as when the number of first type of uplink transmissions equals the maximum allowed number of retransmissions, but the transmission still fails (e.g., the predetermined conditions are not met), the terminal will switch to the second type of transmission, as shown in Figure 16. The second type of transmission includes: the first message (preamble) of the second type of random access based on contention; and the first message (Msg-A) of the first type of random access based on contention.

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

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

[0465] In some embodiments, at least one parameter used to determine the transmit power of the uplink channel carrying uplink transmission (such as a first-type transmission) is determined by the received uplink transmission (such as a first-type transmission) power control configuration information and the number of retransmissions of the uplink transmission (such as a first-type transmission):

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

[0467] b) When determining the transmit power of the uplink channel PUSCH / NPUSCH carrying contention-based Msg3, the nominal transmit power of the channel (e.g., P...) O_NOMINAL (p0-CB-Msg3) is determined by one of the following methods:

[0468] Option 1: Determined by the target received power of contention-based Msg3, the number of retransmissions of contention-based Msg3, and the power boost value of contention-based Msg3. For example:

[0469] P O_NOMINAL = Target received power for contention-based Msg3 + (Number of retransmissions for contention-based Msg3 - 1) * Power boost for contention-based Msg3;

[0470] Option 2: Determined by the initial target received power of contention-based Msg3, the number of retransmissions of contention-based Msg3, and the power boost value of contention-based Msg3. For example:

[0471] P O_NOMINAL = Initial target received power of contention-based Msg3 + (Number of retransmissions of contention-based Msg3 - 1) * Transmission power boost value of contention-based Msg3;

[0472] Option 3: Target received power based on contention-based Msg3. For example:

[0473] P O_NOMINAL =Target received power of Msg3 based on competition.

[0474] c) When determining the transmit power of the uplink channel PUSCH / NPUSCH carrying contention-based Msg3, the final transmit power of the channel (e.g., P...) CB-Msg3 The value is determined by one of the following parameters: the number of Msg3 retransmissions based on contention, the transmission power boost value of Msg3 based on contention, or the initial transmission final transmit power.

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

[0476] a) When determining the transmit power for a Type I transmission (the uplink channel PUSCH based on contention-based Msg3), the target receive power for contention-based Msg3 is determined by the initial target receive power for Type II transmissions (such as the first message of random access, i.e., the preamble), the number of retransmissions for contention-based Msg3, and the power boost value for contention-based Msg3, such as:

[0477] Contention-based Msg3 target received power = preamble initial target received power + (contention-based Msg3 retransmission count - 1) * contention-based Msg3 transmission power boost value;

[0478] b) When determining the transmission power for a Type I transmission (uplink channel PUSCH based on contention-based Msg3), the target receive power for contention-based Msg3 is determined by the initial target receive power for Type II transmissions (such as the first message of random access, i.e., preamble), the number of retransmissions for contention-based Msg3, and the power boost value for Type II transmissions (such as the first message of random access, i.e., preamble), as follows:

[0479] Contention-based Msg3 target received power = preamble initial target received power + (contention-based Msg3 retransmission count - 1) * preamble transmission power boost value.

[0480] In some embodiments, when a terminal switches a transmission from a first type of transmission to a second type of transmission, at least one parameter used to determine the transmit 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):

[0481] a) When determining the transmission power of a Type II transmission (such as the first message of random access, i.e., preamble), the target reception power of the Type II transmission (such as the first message of random access, i.e. preamble) is determined by the initial target reception power of the Type II transmission (such as the first message of random access, i.e. preamble), the number of retransmissions of the Type I transmission (such as contention-based Msg3), and the rise value of the Type II transmission (such as the first message of random access, i.e. preamble).

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

[0483] c) When determining the transmission power of a second type of transmission (such as the first message of random access, i.e., the data channel in Msg-A), its transmission power is determined by the number of retransmissions of a first type of transmission (such as the contention-based Msg3).

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

[0485] In some embodiments, after multiple transmission failures, the terminal can transmit according to a higher coverage level parameter. In this case, in some embodiments, when the terminal switches to a different coverage level for transmission, retransmission-related parameters, such as the retransmission counter and power accumulation value, are set to zero. In some embodiments, some retransmission-related parameters, such as the power accumulation value, can be inherited.

[0486] Example 6: Indicate OCC parameters, including one or more of OCC enable / disable, OCC length, and OCC sequence (e.g., sequence index), via RRC and / or DCI signaling.

[0487] In the embodiments of this application, uplink transmission includes at least one of the following: multiple repetitions of PUSCH transmission scheduled by DCI; multiple repetitions of PUSCH transmission scheduled by at least one of Random Access Response (RAR) message or Fallback RAR message; multiple repetitions of PUSCH transmission during random access; multiple repetitions of configuration grant PUSCH transmission; multiple repetitions of PUSCH transmission in pre-configured uplink resources (PUR); or multiple repetitions of PUSCH transmission in Early Data Transmission (EDT).

[0488] For example, multiple repetitions of PUSCH transmissions scheduled by RAR messages can be RAR(msg2) scheduling msg3 during a 4-step Random Access Channel (RACH) process. As another example, multiple repetitions of PUSCH transmissions scheduled by fallback RAR messages can be fallback RAR(msgB) scheduling msg3 during a 2-step RACH process.

[0489] For example, multiple repetitions of uplink physical shared channel transmissions scheduled by DCI may include multiple repetitions of PUSCH transmissions scheduled by DCI format 0_0,0_1,0_2,0_3. Multiple repetitions of configuration-granted PUSCH transmissions may include multiple repetitions of CG PUSCH Type 1 and CG PUSCH Type 2.

[0490] 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), or Massive Machine Type Communications Physical Uplink Shared Channel (mMTC PUSCH).

[0491] Code division multiplexing (CDM) is performed on the UE, which involves adding a corresponding code sequence (e.g., OCC) to the signals repeatedly transmitted by the UE (e.g., PUSCH, PUCCH), and then transmitting the signals of multiple UEs 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 combining, and decoding.

[0492] In this embodiment, the code sequence may include OCC (orthogonal cover code) sequences, NOMA (non-orthogonal multiple access) sequences, etc. OCC sequences can be based at least on DFT sequences, Walsh sequences, ZC sequences, Hadamard sequences, etc.

[0493] The code sequence 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 is a schematic diagram of a time slot-based OCC application provided by an embodiment of this application. As shown in Figure 17, assuming there are two UEs, using a 4-length OCC sequence, the sequence is [S i,1 ,S i,2 ,S i,3 ,S i,4 ], where i is the user's ID. The data in each time slot is repeated four times and mapped consecutively to four time slots, with each time slot multiplied by an OCC codeword.

[0494] For code division multiplexing:

[0495] This involves adding a corresponding code sequence (e.g., orthogonal cover code (OCC) sequence) to the signals repeatedly transmitted by the UE (e.g., PUSCH, PUCCH), and then transmitting the signals of multiple UEs on the same time-frequency resources. At the receiving end, the transmitted signals of each UE can be obtained through operations such as interference cancellation, OCC combining, and decoding.

[0496] A code sequence can be applied to one or more time slots, i.e., one or more time slots multiplied by an OCC codeword. For example, with a time granularity of one time slot, as shown in Figure 2, assuming there are two UEs (UE1 and UE2), using a 4-length OCC sequence, the sequence is [S i,1 ,S i,2 ,S i,3 ,S i,4 ], where i is the user's ID. The data in each time slot is repeated four times and mapped consecutively to four time slots, with each time slot multiplied by an OCC codeword.

[0497] For the PUSCH group (or OCC group):

[0498] PUSCH transmission can contain one or more PUSCH groups, also known as PUSCH repetition unit groups. Each group contains M PUSCH repetition units, where M is the code sequence length (e.g., OCC length), which can be represented by the number of elements in the code sequence used, or understood as the maximum number of multiplexed users that can be supported under the code sequence used. Multiple PUSCH groups are defined chronologically. For example, the first PUSCH group contains the earliest M PUSCH repetition units, the second PUSCH group contains the M PUSCH repetition units after the first PUSCH group, and so on. The number of PUSCH repetition units sent by the UE can be greater than the code sequence length. For example, the UE can send 16 repetitions, and the UE's code sequence length is 4. The 16 repetition units can be divided into 4 PUSCH groups. Within each group, the content of each repetition must be exactly the same before code sequence merging can be performed.

[0499] OCC signaling configuration must balance dynamism and signaling overhead. The basic principle is to minimize or avoid adding new bits to the DCI, while ensuring that OCC parameters are as dynamic as possible. One or more of the following schemes can be combined. In some embodiments, the OCC signaling indication uses the same scheme for both DCI-scheduled PUSCH and CG PUSCH Type 2. In some embodiments, the OCC signaling indication uses one of the following schemes for DCI-scheduled PUSCH, while for CG PUSCH Type 2, the OCC signaling indication uses another of the following schemes. In some embodiments, the following schemes are applicable to cases where conversion precoding is enabled, that is, applicable to uplink PUSCH transmissions using DFT-s-OFDM waveforms.

[0500] In the following scheme, condition A will be mentioned and defined as:

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

[0502] Option 1: Configure the OCC length in RRC, and implicitly determine whether OCC is enabled by the OCC length (for example, determine whether the UE decodes DCI in the way that OCC is enabled, which will be understood in the following options and will not be repeated). In DCI, the OCC sequence is implicitly indicated by the antenna port domain.

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

[0504] In some embodiments, a new parameter, such as occ-length, can be defined in the RRC. This parameter can be configured in PUSCH-Config, PUSCH-TimeDomainResourceAllocation, or PUSCH-Allocation. It can use one bit, where '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 an OCC-enabled manner. If this parameter is not configured, it indicates that OCC is not enabled or that the UE decodes DCI in a related manner (i.e., in the manner when OCC functionality is not available).

[0505] In some embodiments, a new parameter, such as occ-length, can be defined in the RRC. This parameter can be configured in PUSCH-Config, PUSCH-TimeDomainResourceAllocation, or PUSCH-Allocation and can use two bits: '00' corresponds to OCC length 1, '01' corresponds to OCC length 2, '10' corresponds to OCC length 4, and '11' is a reserved code bit. In some embodiments, if this parameter is configured to OCC length 2 or 4, it indicates that OCC is enabled. Similarly, if this parameter is configured to OCC length 2 or 4, it can also indicate that the UE can decode DCI in an OCC-enabled manner. If this parameter is not configured or is configured and is 1, it indicates that OCC is not enabled or that the UE decodes DCI in a related manner (i.e., in the manner when OCC functionality is not available).

[0506] Configuration of OCC sequences in DCI:

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

[0508] In some embodiments, without modifying the relevant antenna port table, the OCC sequence index is repeatedly mapped to the values ​​of the antenna port field in ascending order until all 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 obtain [0,1,0,1], which is mapped to the value [0,1,2,3] in Tables 7.3.1.1.2-6. As another example, when the OCC length is 4, the OCC sequence index [0,1,2,3] is mapped to the value [0,1,2,3] in Tables 7.3.1.1.2-6. For example, when the OCC length is 4, the OCC sequence index [0,1,2,3] is repeated three times to obtain [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.

[0509] In some embodiments, the relevant antenna port table is not modified, and the OCC sequence index is obtained based on the value of the antenna port field. For example, OCC sequence index = mod(value of antenna port field, OCC length).

[0510] In some embodiments, the relevant antenna port table is not modified, and the OCC sequence index is obtained based on the DMRS port. For example, OCC sequence index = mod(DMRS port, OCC length). Another example is that when condition A is met, OCC sequence index = mod(DMRS port, OCC length). Yet another example is that when condition A is not met, OCC sequence index = mod(DMRS port + n). SCID (OCC length).

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

[0512] In some embodiments, when the OCC length is 2, and the maximum number of current carrier DMRS symbols is 1 (i.e., maxLength = 1), and condition A is not met, the antenna port domain is 2 bits, using the following table 7.3.1.1.2-6-1.

[0513] Table 7.3.1.1.2-6-1

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

[0515] Table 7.3.1.1.2-6A-1

[0516] In some embodiments, when the OCC length is 2, and the maximum number of current carrier DMRS symbols is 2 (i.e., maxLength = 2), and condition A is not met, the antenna port domain is 4 bits, using the following table 7.3.1.1.2-7-1.

[0517] Table 7.3.1.1.2-7-1

[0518] In some embodiments, when the OCC length is 2, the maximum number of current carrier DMRS symbols is 2 (i.e., maxLength = 2), and condition A is met, the antenna port domain is 4 bits, using the following table 7.3.1.1.2-7A-1.

[0519] Table 7.3.1.1.2-7A-1

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

[0521] Table 7.3.1.1.2-6-2

[0522] In some embodiments, when the OCC length is 4, the maximum number of current carrier DMRS symbols is 1 (i.e., maxLength = 1), and condition A is met, the antenna port domain is 2 bits, using the following table 7.3.1.1.2-6A-2.

[0523] Table 7.3.1.1.2-6A-2

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

[0525] Table 7.3.1.1.2-7-2

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

[0527] Table 7.3.1.1.2-7A-2

[0528] Option 2: Configure a maximum OCC length in RRC, and implicitly determine whether OCC is enabled by the maximum OCC length. In DCI, the OCC sequence and OCC length are implicitly indicated by the antenna port field.

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

[0530] In some embodiments, a new parameter, such as occ-maxLength, can be defined in the RRC. This parameter can be configured in PUSCH-Config, PUSCH-TimeDomainResourceAllocation, or PUSCH-Allocation. It can use one bit, where '0' corresponds to a maximum OCC length of 2 and '1' corresponds to a maximum OCC length of 4. In some embodiments, if the new parameter is configured, it indicates that OCC is enabled. That is, if the new parameter is configured, it also indicates that the UE can decode DCI in an OCC-enabled manner. If the new parameter is not configured, it indicates that OCC is not enabled or that the UE decodes DCI in a related manner (i.e., in the manner when OCC functionality is not available).

[0531] In some embodiments, a new parameter, such as occ-maxLength, can be defined in the RRC. This parameter can be configured in PUSCH-Config, PUSCH-TimeDomainResourceAllocation, or PUSCH-Allocation and can use two bits: '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 bit. In some embodiments, if the new parameter is configured to a maximum OCC length of 2 or 4, it indicates that OCC is enabled. Similarly, if the new parameter is configured to a maximum OCC length of 2 or 4, it can also indicate that the UE can decode DCI in an OCC-enabled manner. If the new parameter is not configured or is configured and is 1, it indicates that OCC is not enabled or that the UE decodes DCI in a related manner (i.e., in the manner when OCC functionality is not available).

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

[0533] When OCC is enabled, the OCC sequence can be implicitly indicated in the DCI via 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, allowing selection of the appropriate available OCC length and OCC sequence within the maximum OCC length range.

[0534] 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 not met, the antenna port domain is 2 bits, using the following table 7.3.1.1.2-6-1.

[0535] Table 7.3.1.1.2-6-1

[0536] In some embodiments, when the maximum OCC length is 2, the maximum number of current carrier DMRS symbols is 1 (i.e., maxLength = 1), and condition A is met, the antenna port domain is 2 bits, using the following table 7.3.1.1.2-6A-1.

[0537] Table 7.3.1.1.2-6A-1

[0538] 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 met, the antenna port domain is 4 bits, using the following table 7.3.1.1.2-7-1.

[0539] Table 7.3.1.1.2-7-1

[0540] In some embodiments, when the maximum OCC length is 2, the maximum number of current carrier DMRS symbols is 2 (i.e., maxLength = 2), and condition A is met, the antenna port domain is 4 bits, using the following table 7.3.1.1.2-7A-1.

[0541] Table 7.3.1.1.2-7A-1

[0542] 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 met, the antenna port domain is 3 bits (1 bit more than when no OCC is used), as shown in Table 7.3.1.1.2-6-2 below.

[0543] Table 7.3.1.1.2-6-2

[0544] In some embodiments, when the maximum OCC length is 4, the maximum number of current carrier DMRS symbols is 1 (i.e., maxLength = 1), and condition A is met, the antenna port domain is 3 bits (1 bit more than when no OCC is used), as shown in Table 7.3.1.1.2-6A-2 below.

[0545] Table 7.3.1.1.2-6A-2

[0546] 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 met, the antenna port domain is 4 bits, as shown in Table 7.3.1.1.2-7-2 below.

[0547] Table 7.3.1.1.2-7-2

[0548] In some embodiments, when the maximum OCC length is 4, the maximum number of current carrier DMRS symbols is 2 (i.e., maxLength = 2), and condition A is met, the antenna port domain is 4 bits, using the following table 7.3.1.1.2-7A-2.

[0549] Table 7.3.1.1.2-7A-2

[0550] Option 3: Configure the candidate OCC length in RRC, and implicitly determine whether OCC is enabled by the candidate OCC length. In DCI, the OCC sequence and OCC length are implicitly indicated by the antenna port field.

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

[0552] In some embodiments, a new parameter, such as occ-candidateLength, can be defined in the RRC. This parameter can be configured in PUSCH-Config, PUSCH-TimeDomainResourceAllocation, or PUSCH-Allocation and can use two bits: '00' corresponds to OCC length 1, '01' corresponds to OCC length 2, '10' corresponds to OCC length 4, and '11' corresponds to both OCC lengths 2 and 4. In some embodiments, if the new parameter is configured, it indicates that OCC is enabled. That is, if the new parameter is configured, it also indicates that the UE can decode DCI in an OCC-enabled manner. If the new parameter is not configured, it indicates that OCC is not enabled or that the UE decodes DCI in a related manner (i.e., in the manner when OCC functionality is not available).

[0553] In some embodiments, a new parameter, such as occ-candidateLength, can be defined in the RRC. This parameter can be configured in PUSCH-Config, PUSCH-TimeDomainResourceAllocation, or PUSCH-Allocation and can use two bits: '00' corresponds to OCC length 1, '01' corresponds to OCC length 2, '10' corresponds to OCC length 4, and '11' corresponds to both OCC lengths 2 and 4. In some embodiments, if the new parameter does not indicate OCC length 1, it indicates that OCC is enabled, or that the UE can decode DCI in an OCC-enabled manner. If the new parameter is not configured or is configured and is 1, it indicates that OCC is not enabled or that the UE decodes DCI in a related manner (i.e., in the manner when OCC functionality is not available).

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

[0555] When OCC is enabled, the OCC sequence can be implicitly indicated in the DCI via 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 candidate OCC lengths. If there are more than one candidate OCC length, the corresponding OCC length and OCC sequence need to be selected in the antenna port table.

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

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

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

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

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

[0561] In some embodiments, when the candidate OCC length is 4, the maximum number of current carrier DMRS symbols is 1 (i.e., maxLength = 1), and condition A is met, the antenna port domain is 2 bits, using Table 7.3.1.1.2-6A-2 in Scheme 1.

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

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

[0564] In some embodiments, when the candidate OCC length is 2 or 4, and the maximum number of current carrier DMRS symbols is 1 (i.e., maxLength = 1), and condition A is not met, the antenna port domain is 3 bits, using Table 7.3.1.1.2-6-2 in Scheme 2.

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

[0566] In some embodiments, when the candidate OCC length is 2 or 4, and the maximum number of current carrier DMRS symbols is 2 (i.e., maxLength = 2), and condition A is not met, the antenna port domain is 4 bits, using Table 7.3.1.1.2-7-2 in Scheme 2.

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

[0568] Option 4: Configure a maximum OCC length in RRC, and implicitly determine whether OCC is enabled by the maximum OCC length. In DCI, the OCC sequence, OCC length, and OCC enable / de-enable (or activate / deactivate) are implicitly indicated by the antenna port field.

[0569] The configuration of the maximum length of OCC and whether OCC is enabled in RRC is the same as in Scheme 2, and will not be repeated here.

[0570] Configuration of OCC length, OCC sequence, and OCC de-enabling in DCI:

[0571] When OCC is implicitly enabled in RRC, the OCC sequence, OCC length, and OCC de-enable can be implicitly indicated in DCI through the antenna port field. In some embodiments, the mapping relationship between OCC sequence index, OCC length, OCC de-enable, and antenna port (or DMRS port) index can be represented in tabular form.

[0572] 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 not met, the antenna port field is 2 bits, using the following table 7.3.1.1.2-6-1, where when the OCC length indicator is 1, it indicates that the OCC is disabled.

[0573] Table 7.3.1.1.2-6-1

[0574] In some embodiments, when the maximum OCC length is 2, the maximum number of current carrier DMRS symbols is 1 (i.e., maxLength = 1), and condition A is met, the antenna port field is 2 bits, using the following table 7.3.1.1.2-6A-1, where when the OCC length indicator is 1, it indicates that the OCC is disabled.

[0575] Table 7.3.1.1.2-6A-1

[0576] 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 met, the antenna port field is 4 bits, using the following table 7.3.1.1.2-7-1, where when the OCC length indicator is 1, it indicates that the OCC is disabled.

[0577] Table 7.3.1.1.2-7-1

[0578] In some embodiments, when the maximum OCC length is 2, the maximum number of current carrier DMRS symbols is 2 (i.e., maxLength = 2), and condition A is met, the antenna port field is 4 bits, using the following table 7.3.1.1.2-7A-1, where when the OCC length indicator is 1, it indicates that the OCC is disabled.

[0579] Table 7.3.1.1.2-7A-1

[0580] 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 met, the antenna port field is 3 bits (1 bit more than when no OCC is used), using the following table 7.3.1.1.2-6-2, where when the OCC length indicator is 1, it indicates that the OCC is disabled.

[0581] Table 7.3.1.1.2-6-2

[0582] In some embodiments, when the maximum OCC length is 4, the maximum number of current carrier DMRS symbols is 1 (i.e., maxLength = 1), and condition A is met, the antenna port field is 3 bits (1 bit more than when no OCC is used), using the following table 7.3.1.1.2-6A-2, where when the OCC length indicator is 1, it indicates that the OCC is disabled.

[0583] Table 7.3.1.1.2-6A-2

[0584] 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 met, the antenna port field is 4 bits, using the following table 7.3.1.1.2-7-2, where when the OCC length indicator is 1, it indicates that the OCC is disabled.

[0585] Table 7.3.1.1.2-7-2

[0586] In some embodiments, when the maximum OCC length is 4, the maximum number of current carrier DMRS symbols is 2 (i.e., maxLength = 2), and condition A is met, the antenna port field is 4 bits, using the following table 7.3.1.1.2-7A-2, where when the OCC length indicator is 1, it indicates that the OCC is disabled.

[0587] Table 7.3.1.1.2-7A-2

[0588] Option 5: Configure the candidate OCC length in RRC, and implicitly determine whether OCC is enabled by the candidate OCC length. In DCI, the OCC sequence, OCC length and OCC enable / de-enable (or activate / de-activate) are implicitly indicated by the antenna port domain.

[0589] The configuration of candidate OCC length and whether OCC is enabled in RRC is the same as in Scheme 3.

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

[0591] When OCC is implicitly enabled in RRC, the OCC sequence, OCC length, and OCC de-enable can be implicitly indicated in DCI through the antenna port field. In some embodiments, the mapping relationship between OCC sequence index, OCC length, OCC de-enable, and antenna port (or DMRS port) index can be represented in tabular form.

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

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

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

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

[0596] In some embodiments, when the candidate OCC length is 2 or 4, and the maximum number of current carrier DMRS symbols is 1 (i.e., maxLength = 1), and condition A is not met, the antenna port domain is 3 bits, using Table 7.3.1.1.2-6-2 in Scheme 4.

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

[0598] In some embodiments, when the candidate OCC length is 2 or 4, and the maximum number of current carrier DMRS symbols is 2 (i.e., maxLength = 2), and condition A is not met, the antenna port domain is 4 bits, using Table 7.3.1.1.2-7-2 in Scheme 4.

[0599] In some embodiments, when the candidate OCC length is 2 or 4, and the maximum number of current carrier DMRS symbols is 2 (i.e., maxLength = 2), and condition A is satisfied, the antenna port domain is 4 bits, using Table 7.3.1.1.2-7A-2 in Scheme 4.

[0600] Option 6: In RRC, a new parameter is used to explicitly indicate whether OCC is enabled, while in DCI, the antenna port domain is used to implicitly indicate the OCC sequence and OCC length.

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

[0602] In some embodiments, a new parameter, such as occ-enabler, can be defined in RRC. This parameter can be configured in PUSCH-Config, PUSCH-TimeDomainResourceAllocation, or PUSCH-Allocation. It can use one bit, with '0' indicating OCC is enabled and '1' indicating OCC is disabled. Alternatively, the new parameter can be configured to enable OCC and not configured to disable OCC.

[0603] Configuration of OCC sequences in DCI:

[0604] When occ-enabler is configured in RRC or occ-enabler indicates OCC enable, the OCC sequence and OCC length can be implicitly indicated in DCI via the antenna port field. In some embodiments, the mapping relationship between OCC sequence index, OCC length, and antenna port (or DMRS port) index can be represented in tabular form.

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

[0606] In some embodiments, when the maximum number of carrier DMRS symbols is 1 (i.e., maxLength = 1) and condition A is not met, the antenna port domain is 2 bits, using Table 7.3.1.1.2-6-1 in Scheme 2.

[0607] In some embodiments, when the maximum number of carrier DMRS symbols is 1 (i.e., maxLength = 1) and condition A is not met, the antenna port domain is 2 bits, using Table 7.3.1.1.2-6A-1 in Scheme 2.

[0608] In some embodiments, when the maximum number of carrier DMRS symbols is 2 (i.e., maxLength = 2) and condition A is not met, the antenna port domain is 4 bits, using Table 7.3.1.1.2-7-1 in Scheme 2.

[0609] In some embodiments, when the maximum number of carrier DMRS symbols is 2 (i.e., maxLength = 2) and condition A is met, the antenna port domain is 4 bits, using Table 7.3.1.1.2-7A-1 in Scheme 2.

[0610] b. When the UE reports UE capability OCC-4, it means that the maximum supported OCC length is 4.

[0611] In some embodiments, when the maximum number of carrier DMRS symbols is 1 (i.e., maxLength = 1) and condition A is not met, the antenna port domain is 3 bits, using Table 7.3.1.1.2-6-2 in Scheme 2.

[0612] In some embodiments, when the maximum number of carrier DMRS symbols is 1 (i.e., maxLength = 1) and condition A is met, the antenna port domain is 3 bits, using Table 7.3.1.1.2-6A-2 in Scheme 2.

[0613] In some embodiments, when the maximum number of carrier DMRS symbols is 2 (i.e., maxLength = 2) and condition A is not met, the antenna port domain is 4 bits, using Table 7.3.1.1.2-7-2 in Scheme 2.

[0614] In some embodiments, when the maximum number of carrier DMRS symbols is 2 (i.e., maxLength = 2) and condition A is met, the antenna port domain is 4 bits, using Table 7.3.1.1.2-7A-2 in Scheme 2.

[0615] Option 7: In RRC, a new parameter is used to explicitly indicate whether OCC is enabled, while in DCI, the antenna port domain is used to implicitly indicate the OCC sequence, OCC length, and OCC enable / de-enable (or activate / deactivate).

[0616] The configuration of OCC length and whether OCC is enabled in RRC is the same as in Scheme 6.

[0617] Configuration of OCC sequences in DCI:

[0618] When occ-enabler is configured in RRC or occ-enabler indicates OCC enable, 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 OCC sequence index, OCC length, OCC disable, and antenna port (or DMRS port) index can be represented in tabular form.

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

[0620] In some embodiments, when the maximum number of carrier DMRS symbols is 1 (i.e., maxLength = 1) and condition A is not met, the antenna port domain is 2 bits, using Table 7.3.1.1.2-6-1 in Scheme 4.

[0621] In some embodiments, when the maximum number of carrier DMRS symbols is 1 (i.e., maxLength = 1) and condition A is not met, the antenna port domain is 2 bits, using Table 7.3.1.1.2-6A-1 in Scheme 4.

[0622] In some embodiments, when the maximum number of carrier DMRS symbols is 2 (i.e., maxLength = 2) and condition A is not met, the antenna port domain is 4 bits, using Table 7.3.1.1.2-7-1 in Scheme 4.

[0623] In some embodiments, the maximum number of carrier DMRS symbols is 2 (i.e., maxLength = 2), and when condition A is met, the antenna port domain is 4 bits, using Table 7.3.1.1.2-7A-1 in Scheme 4.

[0624] b. When the UE reports UE capability OCC-4, it means that the maximum supported OCC length is 4.

[0625] In some embodiments, when the maximum number of carrier DMRS symbols is 1 (i.e., maxLength = 1) and condition A is not met, the antenna port domain is 3 bits, using Table 7.3.1.1.2-6-2 in Scheme 4.

[0626] In some embodiments, when the maximum number of carrier DMRS symbols is 1 (i.e., maxLength = 1) and condition A is met, the antenna port domain is 3 bits, using Table 7.3.1.1.2-6A-2 in Scheme 4.

[0627] In some embodiments, when the maximum number of carrier DMRS symbols is 2 (i.e., maxLength = 2) and condition A is not met, the antenna port domain is 4 bits, using Table 7.3.1.1.2-7-2 in Scheme 4.

[0628] In some embodiments, the maximum number of carrier DMRS symbols is 2 (i.e., maxLength = 2), and when condition A is met, the antenna port domain is 4 bits, using Table 7.3.1.1.2-7A-2 in Scheme 4.

[0629] Example 7: Repeated Transmission of Common PDCCH

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

[0631] PDCCH repetition can be defined as follows: multiple PDCCHs transmit the same DCI (downlink control information) using the same AL (aggregation level), and the encoded bits carried in these multiple PDCCHs are also identical. In this application, "PDCCH repetition" is also referred to as "PDCCH repetition" or "PDCCH retransmission," and "PDCCH used for repetitive DCI transmission" can also be referred to as "repeated PDCCH." This will not be repeated below. The PDCCH described herein may include PDCCH candidates.

[0632] The current protocol already supports repeated PDCCH transmission within a time slot. If a network node configures two search spaces (SSs) for a user, and both SSs are configured with the same `searchSpaceLinkingId`, then the two SSs are considered associated. The network node can then transmit repeated PDCCHs between the two associated SSs. The user terminal improves PDCCH detection performance by detecting the repeated PDCCH transmissions. However, the above-mentioned SS association configuration can only be performed after the user enters the connected state. Furthermore, the following SSs do not support association with other SSs: `SS set 0,searchSpaceSIB1,searchSpaceOtherSystemInformation,pagingSearchSpace,ra-SearchSpace,searchSpaceMCCH,searchSpaceMTCH,peiSearchSpace, and sdt-SearchSpace`. Therefore, PDCCH repetition based on associated SS 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, and Type2A-PDCCH CSS. In other words, it cannot be used for System Information Block (SIB) scheduling, initial access scheduling, paging scheduling, or Small Data Transmission (SDT) scheduling. Currently, PDCCH repetition only supports repetition within a time slot, hence it is also called intra-time slot repetition. This scheme can be called first-time slot repetition. If the network side configures an SS associated with the PDCCH CSS, it may implicitly indicate that common PDCCH or PDCCH CSS repetition is enabled. Otherwise, it may implicitly indicate that common PDCCH or PDCCH CSS repetition is disabled.

[0633] Besides the aforementioned repetitive transmission within the first time slot, other methods of repetitive transmission within a time slot may exist. For example, repetitive transmission within the second time slot: the network side configures an SS (Search Service). Within the time slot determined by the SS, multiple time-domain resources exist that can be used for PDCCH transmission. Each repetitive PDCCH may occupy one time-domain resource. Repetitive PDCCH candidates may have the same aggregation level, coded 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 used for PDCCH repetitive transmission. The time-domain resources may be a control resource set (CORESET), SS timing, a set of consecutive symbols, etc. PDCCH repetitive transmission may correspond to the same search space or the same control resource set, but be repeated on different symbol sets. The time-domain resources may be consecutive. Alternatively, the time-domain resources may be discontinuous, for example, adjacent time-domain resources may have a time interval or offset X, or the i-th time-domain resource may have a time interval or offset X relative to the first time-domain resource. i X or X i This may be configured on 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 retransmission (e.g., X or X mentioned above), this will affect the PDCCH retransmission. i If the time interval is zero, then the multiple time-domain resources may be considered to be consecutive time-domain resources. For example:

[0634] a. For multiple time-domain resources used for PDCCH retransmission, 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 The time resources for the first transmission (e.g., the first PDCCH candidate or PDCCH transmission in a repeating transmission) are determined based on the configuration of the search space SS, and then the time resources for the subsequent repeating transmissions (e.g., the PDCCH candidate or PDCCH transmission other than the first in a repeating transmission) are determined based on the time interval or offset.

[0635] b. If no time interval or offset is configured on the network side, the multiple time-domain resources used for PDCCH retransmission are consecutive time resources, or consecutive available time resources, or consecutive time resources that do not contain DMRS symbols.

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

[0637] 1. For SS0, introduce information elements in PDCCH-ConfigCommon to configure or indicate the time interval or offset of multiple time-domain resources when PDCCH is repeatedly transmitted on SS0.

[0638] 2. For SSx (x>0), introduce information elements in the corresponding SearchSpace to configure or indicate the time interval or offset of multiple time-domain resources when PDCCH is repeatedly transmitted on SSx.

[0639] 3. For Type0A-PDCCH CSS or searchSpaceOtherSystemInformation, introduce information elements in PDCCH-ConfigCommon to configure or indicate the time interval or offset of multiple time-domain resources when Type0A-PDCCH CSS is repeatedly transmitted.

[0640] 4. For Type0B-PDCCH CSS or searchSpaceMCCH or searchSpaceMTCH, introduce information elements in PDCCH-ConfigCommon or in signaling containing searchSpaceMCCH or searchSpaceMTCH to configure or indicate the time interval or offset of multiple time-domain resources when Type0B-PDCCH CSS is repeatedly transmitted.

[0641] 5. For Type1-PDCCH CSS or ra-SearchSpace, introduce information elements in PDCCH-ConfigCommon to configure or indicate the time interval or offset of multiple time-domain resources when Type1-PDCCH CSS is repeatedly transmitted.

[0642] 6. For Type1A-PDCCH CSS or sdt-SearchSpace, introduce information elements in PDCCH-ConfigCommon to configure or indicate the time interval or offset of multiple time-domain resources when Type1A-PDCCH CSS is repeatedly transmitted.

[0643] 7. For Type2-PDCCH CSS or pagingSearchSpace, introduce information elements in PDCCH-ConfigCommon to configure or indicate the time interval or offset of multiple time-domain resources when Type2-PDCCH CSS is repeatedly transmitted.

[0644] 8. For Type2A-PDCCH CSS or pei-SearchSpace, introduce information elements in PDCCH-ConfigCommon to configure or indicate the time interval or offset of multiple time-domain resources when Type2A-PDCCH CSS is repeatedly transmitted.

[0645] 9. For Type0-PDCCH CSS or searchSpaceSIB1, introduce information elements in PDCCH-ConfigCommon to configure or indicate the time interval or offset of multiple time-domain resources when Type0-PDCCH CSS is repeatedly transmitted (corresponding to searchSpaceSIB1).

[0646] 10. For Type 0A / 0B / 1 / 1A / 2 / 2A-PDCCH CSS, introduce information elements in PDCCH-ConfigCommon to configure or indicate the time interval or offset of multiple time-domain resources when PDCCH CSS is repeatedly transmitted. This configuration applies to all CSS in Type 0A / 0B / 1 / 1A / 2 / 2A-PDCCH CSS.

[0647] For repeated transmissions within the second time slot, the network side may also configure the number of repeated transmissions or a repeated transmission enable signaling. If the network side configures the number of repeated transmissions, it may implicitly indicate that repeated transmissions of the common PDCCH or PDCCH CSS are enabled. Otherwise, it may implicitly indicate that repeated transmissions of the common PDCCH or PDCCH CSS are disabled. If the network side configures a repeated transmission enable signaling but does not configure the number of repeated transmissions, it may implicitly indicate that the number of repeated transmissions is 2, or other repetition transmission numbers predefined by the standard.

[0648] In summary, the method of repeating PDCCH transmission within a time slot may include at least one of the following: repeating transmission within a first time slot, or repeating transmission within a second time slot.

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

[0650] 1. Extend repeated transmissions within the first time slot to the public PDCCH or PDCCH CSS. For example, searchSpaceLinkingId can be configured for PDCCH CSS, or PDCCH CSS can be associated with other SSs.

[0651] 2. Support repeated transmission within the second time slot for public PDCCH or PDCCH CSS.

[0652] It should be noted that the configuration method for SS0 in the current standard protocol differs from that of other search spaces. SS0 can be configured via a bit field `searchSpaceZero` in either `PDCCH-ConfigSIB1` or `PDCCH-ConfigCommon`. This bit field may be 4 bits long. The user retrieves the search space configuration from a predefined table in the standard protocol based on the value indicated by the bit field. Therefore, it is difficult to directly include the aforementioned association identifiers (e.g., `searchSpaceLinkingID`) in the SS0 configuration. Consequently, repeated transmissions within the first time slot may be difficult to apply to SS0. To address this, the following approach might be considered:

[0653] 1. For public PDCCH or PDCCH CSS, repeat transmission within the second time slot is adopted.

[0654] 2. For public PDCCH or PDCCH CSS on SS0, repeated transmission within the second time slot is adopted; for public PDCCH or PDCCH CSS not on SS0, repeated transmission within the first time slot is adopted.

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

[0656] 4. For public PDCCH or PDCCH CSS, repeated transmission within the first time slot and repeated transmission within the second time slot are supported. If the SS containing the public PDCCH or PDCCH CSS is associated with other SSs, repeated transmission within the first time slot will be used. If the SS containing the public PDCCH or PDCCH CSS is not associated with other SSs, repeated transmission within the second time slot may be used in the following scenarios:

[0657] (1) The network side is configured with enable signaling to enable repeated transmission in the second time slot.

[0658] (2) The network side is configured with intervals or offsets of multiple time-domain resources (as described above).

[0659] (3) The network side has configured the enable signaling, but has not configured the above time interval or offset. In this case, the multiple time-domain resources used for PDCCH retransmission are continuous time resources.

[0660] It should be noted that the above method may only apply to some common PDCCH or PDCCH CSS. For example, PDCCH CSS other than Type0-PDCCH CSS and Type3-PDCCH CSS. Or, for example, at least one of Type0A / 0B / 1 / 1A / 2 / 2A-PDCCH CSS. Therefore, the above method 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 CSS". Additionally, the above method may also be applied to the following situations: changing "public PDCCH or PDCCH CSS" to "Type0-PDCCH CSS", or "searchSpaceSIB1", or "Type0-PDCCH CSS corresponding to searchSpaceSIB1". Furthermore, the above method may also be applied to the following situations: changing "public PDCCH or PDCCH CSS" to "Type3-PDCCH CSS".

[0661] The aforementioned network-side configuration may refer to the network side instructing UE parameters or configurations via first signaling. This signaling includes at least one of the following: Master Information Block (MIB), System Information Block (SIB), Physical Broadcast Channel (PBCH), or Radio Resource Control (RRC) signaling. The instruction method may include:

[0662] Define a new / dedicated bit field to indicate;

[0663] Multiplexing / reinterpreting relevant bit fields to indicate;

[0664] Multiplexing / reinterpreting one or more states / code points of the relevant bit field to indicate;

[0665] Introduce new Information Elements (IEs) to indicate (e.g., enumerate multiple candidate values, indicate one from multiple candidate values, or indicate a specific value);

[0666] For enable / activation indications, a corresponding information element (IE) may be introduced. When the network side configures / indicates this information element, it indicates enable / activation; when it is not configured / indicated, it indicates disable / de-enable / de-activation. Alternatively, for enable / activation indications, a new bit field or idle / reserved bits in related signaling may be introduced, such as MIB / PBCH / SIB1 / SIBx. When the bit indicates "1", it indicates enable / activation; when it indicates "0", it indicates disable / de-enable / de-activation; and vice versa.

[0667] This application also provides a communication node, including a processor configured to implement the methods provided in any embodiment of this application when executing a computer program. Exemplarily, the communication node can be a first communication node or a second communication node. The first communication node includes a processor configured to implement the information transmission method and uplink transmission method provided in any embodiment of this application when executing a computer program; the second communication node includes a processor configured to implement the information reception method provided in any embodiment of this application when executing a computer program. Exemplarily, the first communication node can be a terminal device, such as a UE, provided in any embodiment of this application; the second communication node can be an access network device, such as a base station, provided in any embodiment of this application. This application does not impose specific limitations in this regard.

[0668] For example, the following embodiments provide structural diagrams of communication nodes as terminals and base stations, respectively.

[0669] Figure 18 is a schematic diagram of the structure of a terminal provided in an embodiment of this application. The terminal can be implemented in various forms. The terminal in this application may include, but is not limited to, mobile terminal devices such as mobile phones, smartphones, laptops, digital broadcast receivers, personal digital assistants (PDAs), portable devices (PADs), portable media players (PMPs), navigation devices, in-vehicle terminal equipment, in-vehicle display terminals, in-vehicle electronic rearview mirrors, etc., as well as fixed terminal devices such as digital televisions (TVs), desktop computers, etc.

[0670] As shown in Figure 18, 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, and a power supply unit 59, etc. Figure 18 illustrates a terminal including multiple components; however, it should be understood that it is not required to implement all of the components shown. More or fewer components may be implemented alternatively.

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

[0672] The processor 58 executes at least one functional application and data processing by running a program stored in the memory 56, such as implementing the methods provided in the embodiments of this application.

[0673] Figure 19 is a schematic diagram of a base station structure provided in an embodiment of this application. As shown in Figure 19, the base station includes a processor 60, a memory 61, and a communication interface 62. The number of processors 60 in the base station can be one or more; Figure 19 shows an example of one processor 60. The processor 60, memory 61, and communication interface 62 in the base station can be connected via a bus or other means; Figure 19 shows an example of connection via a bus. The bus represents one or more types of bus structures, including a memory bus or memory controller, a peripheral bus, a graphics acceleration port, a processor, or a local bus using any of the various bus structures.

[0674] The memory 61, as 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 methods in the embodiments of this 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, thereby implementing the methods described above.

[0675] The memory 61 may include a program storage area and a data storage area. The program storage area may store the operating system and applications required for at least one function; the data storage area may store data created based on the use of the terminal. Furthermore, the memory 61 may include high-speed random access memory and may also include non-volatile memory, such as at least one disk storage device, flash memory device, or other non-volatile solid-state storage device. In some instances, the memory 61 may include memory remotely located relative to the processor 60, and this remote memory may be connected to a base station via a network. Examples of such networks include, but are not limited to, the Internet, corporate intranets, networks, mobile communication networks, and combinations thereof.

[0676] Communication interface 62 can be configured to receive and send data.

[0677] This application also provides a computer-readable storage medium storing a computer program that, when executed by a processor, implements the methods provided in any embodiment of this application.

[0678] The computer storage medium in this application embodiment can be 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. For example, a computer-readable storage medium can be, but is not limited to, an electrical, magnetic, optical, electromagnetic, infrared, or semiconductor system, apparatus, or device, or any combination thereof. Computer-readable storage media include (a non-exhaustive list): electrical connections having one or more wires, portable computer disks, hard disks, random access memory (RAM), read-only memory (ROM), electrically erasable, programmable read-only memory (EPROM), flash memory, optical fiber, portable compact disc read-only memory (CD-ROM), optical storage devices, magnetic storage devices, or any suitable combination thereof. In this application, the computer-readable storage medium can be any tangible medium containing or storing a program that can be used by or in conjunction with an instruction execution system, apparatus, or device.

[0679] Computer-readable signal media may include data signals propagated in baseband or as part of a carrier wave, the data signals carrying computer-readable program code. Such propagated data signals may take various forms, including but not limited to electromagnetic signals, optical signals, or any suitable combination thereof. Computer-readable signal media may also be any computer-readable medium other than computer-readable storage media, which can send, propagate, or transmit programs for use by or in conjunction with an instruction execution system, apparatus, or device.

[0680] Program code contained on a computer-readable medium may be transmitted using any suitable medium, including but not limited to wireless, wire, optical fiber, radio frequency (RF), or any suitable combination thereof.

[0681] Computer program code for performing the operations of this disclosure can be written in one or more programming languages ​​or a combination of programming languages, including object-oriented programming languages ​​(such as Java, Smalltalk, C++, Ruby, and Go) and conventional procedural programming languages ​​(such as the "C" language or similar programming languages). The program code can be executed entirely on the user's computer, partially on the user's computer, as a standalone software package, partially on the user's computer and partially on a remote computer, or entirely on a remote computer or server. In cases involving remote computers, the remote computer can be connected to the user's computer via any type of network (including a Local Area Network, LAN, or Wide Area Network, WAN), or it can be connected to an external computer (e.g., via the Internet using an Internet service provider).

[0682] This application also provides a computer program product that, when executed by a computer, implements any of the functions described in the above method embodiments.

[0683] Those skilled in the art will understand that the term user terminal encompasses any suitable type of wireless user equipment, such as mobile phones, portable data processing devices, portable web browsers, or vehicle-mounted mobile stations.

[0684] Generally, the various embodiments of this application can be implemented in hardware or dedicated circuitry, software, logic, or any combination thereof. For example, some aspects can be implemented in hardware, while others can be implemented in firmware or software that can be executed by a controller, microprocessor, or other computing device, although this application is not limited thereto.

[0685] Embodiments of this application can be implemented by executing computer program instructions through the data processor of a mobile device, for example, in a processor entity, or through hardware, or through a combination of software and hardware. The computer program instructions can be assembly instructions, Instruction Set Architecture (ISA) instructions, machine instructions, machine-dependent instructions, microcode, firmware instructions, status setting data, or source code or object code written in any combination of one or more programming languages.

[0686] Any block diagram of logical flow in the accompanying drawings of this application may represent program steps, or may represent interconnected logic circuits, modules, and functions, or may represent a combination of program steps and logic circuits, modules, and functions. The computer program may be stored in memory. The memory may be of any type suitable to the local technical environment and may be implemented using any suitable data storage technology, such as, but not limited to, read-only memory (ROM), random access memory (RAM), optical storage devices and systems (Digital Versatile Disc (DVD) or Compact Disc (CD)), etc. Computer-readable media may include non-transitory storage media. The data processor may be of any type suitable to the local technical environment, such as, but not limited to, general-purpose computers, special-purpose computers, microprocessors, digital signal processors (DSPs), application-specific integrated circuits (ASICs), field-programmable gate arrays (FPGAs), and processors based on multi-core processor architectures.

Claims

1. An information transmission method, applied to a first communication node, the method comprising: Receive the orthogonal coverage code (OCC) configuration information sent by the second communication node; Determine the extended information of the OCC based on the OCC configuration information; The OCC-extended information is sent to the second communication node.

2. The method according to claim 1, wherein, The OCC configuration information includes at least one of the following: The first instruction used to indicate whether the OCC function is enabled or disabled; A second indication used to indicate OCC activation or OCC deactivation; A third indicator used to indicate the length of the OCC; or A fourth indication for indicating OCC sequence parameters, wherein the OCC sequence parameters include: an OCC sequence or an OCC index.

3. The method according to claim 2, wherein, The instruction is indicated by at least one of the following methods: Instructed by high-level signaling; When the OCC length or OCC sequence parameter is indicated as a valid value, it means that the OCC function is enabled; When the OCC length or OCC sequence parameter is indicated as an invalid value, the OCC function is disabled. Indicated by existing or newly added fields in the Downlink Control Information (DCI) of the Physical Uplink Shared Channel (PUSCH); or Determined by the first instruction and / or the second instruction.

4. The method according to claim 3, wherein, The second indication is indicated by at least one of the following fields in the DCI: modulation and coding scheme field, repeating digital segment, redundancy version field, unicast scheduled transport block TB digital segment, subcarrier indication field, or resource reservation field.

5. The method according to claim 2, wherein, The second indication is used to indicate OCC activation or OCC deactivation if at least one of the following conditions is met: The first indication indicates that the OCC function is enabled or that the first indication is configured; The subcarrier spacing is configured to 15 kHz, wherein the subcarrier spacing is indicated by higher-layer parameters or by the uplink subcarrier spacing in the random access response grant; The subcarrier spacing is configured to 3.75 kHz, wherein the subcarrier spacing is indicated by higher-layer parameters or by the uplink subcarrier spacing in the random access response grant; or The Cyclic Redundancy Check (CRC) code of the Downlink Control Information (DCI) is scrambled by the Cell Radio Network Temporary Identifier (C-RNTI).

6. The method according to claim 2, wherein, The third indication is used to indicate the OCC length when at least one of the following conditions is met, or the OCC length is a preset value: The first indication indicates that the OCC function is enabled or that the first indication is configured; or The second instruction indicates that OCC is activated.

7. The method according to claim 3, wherein, The fourth instruction is indicated by one of the following methods: The DCI is indicated by at least one of the following fields: modulation and coding scheme field, repeating digital segment, redundancy version field, unicast scheduled TB digital segment, subcarrier indication field, or resource reservation field. The two bits in at least one of the fields or the newly added field indicate that the OCC is activated or deactivated. The index set corresponding to the subcarrier indication field in the DCI indicates that the index set is also used to indicate OCC activation or OCC deactivation. Indicated by the index set corresponding to the subcarrier indication field in the DCI; or The existing fields in the DCI are used as new indication fields.

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

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

10. The method according to claim 9, wherein, For a single-carrier 3.75kHz 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, The fourth indication is used to indicate OCC sequence parameters if at least one of the following conditions is met: The first indication indicates that the OCC function is enabled or that the first indication is configured; The second instruction indicates that OCC is activated; The third indication indicates a specific OCC length; The OCC length is determined as a specific OCC length according to the first instruction and / or the second instruction; The subcarrier spacing is configured to 15 kHz, wherein the subcarrier spacing is indicated by higher-layer parameters or by the uplink subcarrier spacing in the random access response grant; The subcarrier spacing is configured to 3.75 kHz, wherein the subcarrier spacing is indicated by higher-layer parameters or by the uplink subcarrier spacing in the random access response grant; or DCI CRC is scrambled by C-RNTI.

12. The method according to claim 1, wherein, The information after OCC expansion includes the data after OCC expansion; The step of determining the extended OCC information based on the OCC configuration information includes: Determine the OCC sequence parameters based on the OCC configuration information; Determine the OCC sequence based on the OCC sequence parameters; Based on the OCC sequence and the complex modulation symbols, the data after OCC expansion is determined.

13. The method according to claim 12, wherein, Determining the OCC-extended data based on the OCC sequence and the complex modulation symbols includes at least one of the following: The complex modulation symbols in each time-domain symbol block obtained by dividing the complex modulation symbols are expanded by the OCC sequence to obtain the OCC-expanded data; The complex modulation symbols in each time slot block of the multiple time slot blocks obtained by dividing the complex modulation symbols are expanded by the OCC sequence to obtain the data after OCC expansion; or The complex modulation symbols in each of the multiple repeating unit blocks obtained by dividing the complex modulation symbols are extended by the OCC sequence to obtain the OCC-extended data.

14. The method according to claim 12, further comprising: The step of determining the OCC-extended data based on the OCC sequence and the complex modulation symbols is determined to be performed if at least one of the following conditions is met: The first instruction indicates that the OCC function is enabled or that the first instruction is configured. The second instruction activates the OCC; The third indicator specifies the length of a particular OCC. The OCC length is determined as a specific OCC length according to the first instruction and / or the second instruction; The fourth indicator specifies the parameters of a particular OCC sequence; The subcarrier spacing is configured to 15 kHz, wherein the subcarrier spacing is indicated by higher-layer parameters or by the uplink subcarrier spacing in the random access response grant; The subcarrier spacing is configured to 3.75 kHz, wherein the subcarrier spacing is indicated by higher-layer parameters or by the uplink subcarrier spacing in the random access response grant; or 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 of the PUSCH scheduling.

15. The method according to claim 12, wherein, The OCC-extended data includes the second PUSCH codeword; The method further includes: The scrambling sequence of the first PUSCH codeword is scrambled 1 or 2 times per OCC length. After each repeated transmission, reinitialization is performed. N represents the mapping of the first PUSCH codeword before OCC extension. RU The number of times each resource unit is repeated; Map the second PUSCH codeword to N RU,enh There are N resource units, of which N RU,enh N represents the number of resource units. RU,enh The number N of resource units mapped by the OCC length and the first PUSCH codeword RU Determined, for each N RU,enh One resource unit was transmitted Second-rate, length.

16. The method according to claim 15, wherein, The second PUSCH codeword is mapped to N. RU,enh Each resource unit includes any one of the following: Mapping to N slots After a time slot, N should be repeated before continuing to map z(·) to the next time slot. slots Time slot Next, among them Equals 1, N represents the number of repetitions of consecutive time slots. slots Indicates the number of consecutive time slots; or Mapped to OCC length * N slots After a time slot, before continuing to map z(·) to the next time slot, the OCC length * N should be repeated. slots Time slot Second-rate, equal Length or 17. The method according to claim 15, wherein, Sending the OCC-extended information to the second communication node includes at least one of the following: For the second PUSCH codeword corresponding to the j-th TB, in B consecutive time slots n i Transmission occurs in the form of i = jB + b, where b = 0, 1, ..., B-1. Redundant version rv associated with the TB idx (j) is determined as follows: rv idx (j) = 2 * mod(rv) enh +j,2), if Then L=1, and the second PUSCH codeword is related to rv idx (j) The associated part will be mapped to the assigned N. RU,enh The resource unit in the first Transmission is performed on each time slot. The number of time slots included in a resource unit, rv enh The redundant version field in the DCI is indicated or predefined. Indicates the number of consecutive subcarriers; For the second PUSCH codeword corresponding to the j-th TB, in B consecutive time slots n i Transmission occurs in the form of i = jB + b, where b = 0, 1, ..., B-1. Redundant version rv associated with the TB idx (j) is determined as follows: rv idx (j) = 2 * mod(rv) enh +j,2), if Then L = 1, otherwise or With a subcarrier spacing of 3.75 kHz, in the uplink time slot associated with TB, time slot n i The mapping method is With a subcarrier spacing of 15kHz, in the uplink time slot associated with TB, time slot n i The mapping method is 18. The method according to claim 1, wherein, The extended information of the OCC includes the demodulation reference signal DMRS sequence; The step of determining the extended OCC information based on the OCC configuration information includes: According to the formula The length determines the length of the DMRS sequence, and the DMRS sequence is generated, wherein, N represents the mapping of the first PUSCH codeword before OCC extension. RU The number of times a resource unit is repeated. N represents the number of time slots included in a resource unit. RU This indicates the number of resource units mapped to the first PUSCH codeword before OCC extension.

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

20. The method of claim 1, wherein, The information after OCC expansion includes the OCC-expanded DMRS sequence; The step of determining the extended OCC information based on the OCC configuration information includes any one of the following: According to the formula The length of the DMRS sequence before expansion is determined, and the DMRS sequence after OCC expansion is determined based on the OCC sequence and the DMRS sequence before expansion, wherein the OCC sequence is information determined according to the OCC configuration information. N represents the mapping of the first PUSCH codeword before OCC extension. RU The number of repetitions of each resource unit, N RU This indicates the number of resource units mapped by the first PUSCH codeword. Indicates the number of time slots included in a resource unit; The frequency domain length of the DMRS sequence before expansion is determined based on the number of consecutive subcarriers; the expanded DMRS sequence is determined based on the OCC sequence and the DMRS sequence before expansion; or The frequency domain length of the DMRS sequence before extension is determined based on the number of consecutive subcarriers. The extended DMRS sequence after OCC is determined based on the cyclic shift and the DMRS base sequence, wherein the cyclic shift is related to the OCC sequence.

21. The method according to claim 18 or 20, further comprising: The step of determining the extended OCC information based on the OCC configuration information is determined if at least one of the following conditions is met: The first instruction indicates that the OCC function is enabled or that the first instruction is configured. The second instruction activates the OCC; The third indicator specifies the length of a particular OCC. The OCC length is determined as a specific OCC length according to the first instruction and / or the second instruction; The fourth indicator specifies the parameters of a particular OCC sequence; The subcarrier spacing is configured to 15 kHz, wherein the subcarrier spacing is indicated by higher-layer parameters or by the uplink subcarrier spacing in the random access response grant; The subcarrier spacing is configured to 3.75 kHz, wherein the subcarrier spacing is indicated by higher-layer parameters or by 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 of the scheduled PUSCH; or 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 of the PUSCH scheduling.

22. The method of claim 1, wherein, The OCC-extended information includes at least one of the following: DMRS sequence, OCC-extended data, or OCC-extended DMRS sequence; The method further includes at least one of the following: When the information after OCC extension is delayed, the delay is based on the OCC group, wherein the OCC group is the longer of the OCC-extended data and the OCC-extended DMRS sequence; or After the information after the OCC extension is delayed, a delay time is applied, wherein 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, further comprising: The procedure of delaying based on the OCC group or delaying based on the delay time shall be determined if at least one of the following conditions is met: The first instruction indicates that the OCC function is enabled or that the first instruction is configured. The second instruction activates the OCC; The third indicator specifies the length of a particular OCC. The OCC length is predefined as a valid value; The fourth indicator specifies the parameters of a particular OCC sequence; The subcarrier spacing is configured to 15 kHz, wherein the subcarrier spacing is indicated by higher-layer parameters or by the uplink subcarrier spacing in the random access response grant; The subcarrier spacing is configured to 3.75 kHz, wherein the subcarrier spacing is indicated by higher-layer parameters or by 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 of the scheduled PUSCH; or 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 of the PUSCH scheduling.

24. An information receiving method, applied to a second communication node, the method comprising: Send orthogonal coverage code (OCC) configuration information to the first communication node; The system receives OCC-extended information sent by the first communication node, wherein the OCC-extended information is information determined by the first communication node based on the OCC configuration information.

25. A method for uplink transmission, comprising: The first communication node determines the uplink channel configuration that carries the uplink transmission; The first communication node sends an uplink channel carrying the uplink transmission.

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

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

28. The method according to claim 25, wherein, The uplink transmission includes one of the following: Type I uplink transmission; wherein, Type I uplink transmission includes one of the following: contention-based uplink data transmission, contention-based message Msg3 transmission, or contention-based Type I random access first message transmission; or Type II uplink transmission; wherein Type II uplink transmission includes one of the following: a first message preamble for contention-based Type II random access, or a first message transmission for contention-based Type I random access.

29. The method according to claim 25, wherein, The first communication node will switch from Type I uplink transmission to Type II uplink transmission when one of the following conditions is met: When the number of uplink transmissions in the first category exceeds the maximum allowed retransmission count; or, When the number of Type I uplink transmissions equals the maximum allowed retransmissions, but is still considered a transmission failure.

30. The method according to claim 25, wherein, The first communication node sends multiple copies for a single transmission when one of the following conditions is met: When the number of replicas supported by a transmission indicated by the second communication node is greater than 1; or The second communication node sends an enable message.

31. The method according to claims 25 and 27, wherein, When the first communication node sends multiple copies for a single 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 a single transmission, the method for determining the number of repetitions supported for each copy includes one of the following methods: The second communication node is configured via higher-level signaling; The number of repetitions for each replica is determined by the number of replicas supported by a transmission and the number of repetitions for a transmission; or, Each copy is repeated the same number of times as a transfer.

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

34. A communication node, comprising: processor; The processor is configured to implement, when executing a computer program, the information transmission method as described in any one of claims 1 to 23, or the information reception method as described in claim 24, or the uplink transmission method as described in any one of claims 25 to 33.

35. A computer-readable storage medium storing a computer program, which, when executed by a processor, implements the information transmission method as described in any one of claims 1 to 23, or the information reception method as described in claim 24, or the uplink transmission method as described in any one of claims 25 to 33.