Communication method, communication node, and storage medium

Abstract

The application provides a communication method, a communication node and a computer readable storage medium. The method is applied to a first communication node. The method comprises the following steps: determining a transmission parameter of a first message; and sending the first message to a second communication node according to the transmission parameter of the first message. The transmission parameter of the first message at least comprises a repetition factor. In the method, the first communication node can repeatedly send the first message to the second communication node based on the transmission parameter at least comprising the repetition factor, so that the repetition of the first message is supported. In this way, even if the first message is a PUSCH message with a similar payload as a Msg4 message, the repetition can be supported, thereby overcoming the problem that some messages do not support repetition.

Description

Technical Field

[0001] The embodiments of this application relate to, but are not limited to, the field of communication technology, and in particular to a communication method, a communication node, and a storage medium. Background Technology

[0002] 3GPP supports Non-Terrestrial Networks (NTNs), whose network coverage performance is crucial for operators. In Release 17, coverage enhancements were implemented for Physical Uplink Shared Channel (PUSCH) messages (such as the Msg3 message) during random access procedures, supporting retransmission. Release 18 enhanced coverage for Physical Random Access Channel (PRACH) messages (such as the Msg1 message) and PUCCH messages carrying Msg4 HARQ-ACK, including PRACH message retransmission and PUCCH message retransmission carrying Msg4 HARQ-ACK. In Release 19, due to coverage bottlenecks, coverage enhancements for the Msg4 message are under discussion, including supporting retransmission, with a maximum retransmission count of 2 or 4 times. To support the repeated transmission of Msg4 messages, the corresponding configuration methods for the repetition factor, such as dynamic indication via Downlink Control Information (DCI), indication via System Information Block (SIB), or implicit indication via SIB PDSCH repetition, are under discussion. Msg4 messages typically carry around 1000 bits, while PUSCH messages with similar payloads (such as Msg5 messages scheduled by DCI format 0_0 (e.g., RRC establishment completion messages, RRC recovery completion messages, etc.), whose payloads are approximately 984 bits, currently do not support repetition. Summary of the Invention

[0003] This application provides a communication method, a communication node, and a storage medium.

[0004] On one hand, embodiments of this application provide a communication method applied to a first communication node, the method comprising: determining transmission parameters of a first message; sending the first message to a second communication node according to the transmission parameters of the first message; wherein the transmission parameters of the first message include at least a repetition factor.

[0005] On the other hand, embodiments of this application also provide a communication node, including: at least one processor; at least one memory for storing at least one program; at least one program is executed by at least one processor to perform the communication method as described above.

[0006] On the other hand, embodiments of this application also provide a computer-readable storage medium storing computer-executable instructions for performing the communication method as described above.

[0007] On the other hand, embodiments of this application also provide a computer program product, including a computer program or computer instructions, wherein the computer program or computer instructions are stored in a computer-readable storage medium, and the processor of the communication node reads the computer program or computer instructions from the computer-readable storage medium and executes the computer program or computer instructions, causing the communication node to perform the communication method as described above.

[0008] In this embodiment, the first communication node first determines the transmission parameters of the first message, wherein the transmission parameters of the first message include at least a repetition factor. Then, the first communication node sends the first message to the second communication node according to the transmission parameters of the first message. In this way, the first communication node can repeatedly send the first message to the second communication node based on the transmission parameters that include at least a repetition factor, thus supporting the repetition of the first message. Therefore, even if the first message is a PUSCH message with a similar payload to the Msg4 message, repetition can be supported, thereby overcoming the current problem that some messages do not support repetition. Attached Figure Description

[0009] Figure 1 This is a schematic diagram of the architecture of an NTN communication system in the prior art;

[0010] Figure 2 This is a schematic diagram of the random access process provided in an embodiment of this disclosure;

[0011] Figure 3 This is a flowchart of a communication method provided in an embodiment of this disclosure;

[0012] Figure 4 This is a schematic diagram of the structure of the PUSCH provided in the embodiments of this disclosure;

[0013] Figure 5 This is a schematic diagram of the OCC application provided in the embodiments of this disclosure;

[0014] Figure 6 This is a schematic diagram of the physical resource mapping of NPUSCH codewords (configured for 8 repetitions) for multi-tone transmission provided in this embodiment of the disclosure;

[0015] Figure 7 This is a schematic diagram of the physical resource mapping of NPUSCH codewords (configured for 2 repetitions) for single-tone transmission provided in this embodiment of the disclosure;

[0016] Figure 8 This is a schematic diagram of a communication node provided in an embodiment of this disclosure. Detailed Implementation

[0017] To make the objectives, technical methods, and advantages of this application clearer, the following detailed description is provided in conjunction with the accompanying drawings and embodiments. It should be understood that the specific embodiments described herein are merely illustrative and not intended to limit the scope of this application.

[0018] It should be noted that although the flowchart shows a logical order, in some cases, the steps shown or described may be executed in a different order than that shown in the flowchart. In the description of the specification, claims, and the above-mentioned figures, "multiple" means two or more; "greater than," "less than," and "exceeding" are understood to exclude the stated number; "above," "below," and "within" are understood to include the stated number. The use of terms such as "first," "second," etc., is merely for distinguishing technical features and should not be construed as indicating or implying relative importance, or implicitly specifying the number of indicated technical features, or implicitly indicating the order of the indicated technical features. Furthermore, in the description of the specification, claims, and the above-mentioned figures, various values ​​mentioned (such as first value, second value, target value, etc.) can be flexibly represented as single numeric codes or enumerated type values. These values ​​can clearly guide and control the execution flow and behavior patterns of various functional modules, ensuring the efficiency of decoding or encoding.

[0019] Reference Figure 1 As shown, Figure 1 This is a schematic diagram of the architecture of an NTN communication system in the existing technology. Figure 1 In the NTN communication system shown, the link between terminal 110 (i.e., UE) and satellite 120 is service link 130, and the link between access network equipment 140 (such as base station, gateway, etc.) and satellite 120 is feeder link 150. Furthermore, for all terminals 110 (e.g., UE, UE, etc.) within the same cell... Figure 1 All terminals shown in the image are public.

[0020] When a terminal accesses the network, a random access procedure is performed with the network side. (Refer to...) Figure 2 As shown, Figure 2 This is an example illustration of the random access procedure (using a four-step random access method as an example). Figure 2 In China, the random access process mainly includes the following steps:

[0021] (1) The terminal sends a random access preamble sequence (i.e., Msg1 message) to the network side. The time-frequency resources occupied by sending the random access preamble sequence are called PRACH resources (the time-frequency resources that the network side broadcasts to all terminals in the SIB signaling that are allowed to be used to send the random access preamble sequence). The terminal selects a random access preamble sequence and sends it on the PRACH resource, which has a specific random access identifier (RA-RNTI).

[0022] (2) The network side detects multiple possible random access attempts (such as random access from different terminals) and responds to the detected random access. The Random Access Response (RAR) is transmitted on the Downlink Shared Channel (DL-SCH), and the DCI signaling transmitted in the Physical Downlink Control Channel (PDCCH) is scrambled with the Random Access Radio Network Temporary Identifier (RA-RNTI) to instruct the terminal to receive. The terminal attempts to detect the L1 / L2 control channel within a configurable time window to receive the random access response sent by the network side (including the Random Access Preamble Identifier (RAPID), Temporary Cell Radio Network Temporary Identifier (TC-RNTI), etc.), and checks whether the identifier contained in the random access response (such as RAPID) matches the identifier sent by the terminal to the network side.

[0023] (3) When the terminal detects a random access response from the network side within this time window, the terminal uses the Uplink Shared Channel (UL-SCH) resource indicated by the random access response to send a Msg3 message to the network side. If the terminal has a unique identifier, such as a Cell Radio Network Temporary Identifier (C-RNTI), the C-RNTI will be carried in the Msg3 message; otherwise, the terminal's identifier in the core network will be carried in the Msg3 message. This Msg3 message can be used for Radio Resource Control (RRC) establishment requests.

[0024] (4) The network side sends a contention resolution message, namely Msg4 message. If the Msg3 message carries C-RNTI, the network side uses C-RNTI to scramble the PDCCH message; otherwise, it uses TC-RNTI to scramble the PDCCH message.

[0025] in:

[0026] Terminals with a unique identifier (such as C-RNTI) use C-RNTI to address on the PDCCH. If a PDCCH message scrambled with C-RNTI (specifically DCI signaling) is detected, the contention is successful and random access is successful.

[0027] Terminals without a unique identifier use TC-RNTI for addressing on the PDCCH. Their scheduled DL-SCH contains a contention resolution message. The core network identifier contained in the contention resolution message is compared with the one sent by the terminal in the Msg3 message. If they match, the contention is successful and random access is successful. Here, C-RNTI = TC-RNTI. The terminal will send a Hybrid Automatic Repeat reQuest (HARQ) response uplink.

[0028] (5) When the terminal is restoring or rebuilding an RRC connection and the network is unable to retrieve or verify the terminal context, after the terminal receives the RRC setup (i.e., RRCSetup in the Msg4 message), it will send an RRC setup completion message to the network side as a response (i.e., RRCSetupComplete in the Msg5 message), which is carried by the PUSCH channel. This PUSCH is scheduled by DCI format 0_0, and the terminal sends the RRC setup completion message according to the scheduling information in the DCI.

[0029] The following is about Figure 2 This will provide a detailed explanation of some of the messages.

[0030] The Msg1 message is the first step in the random access procedure: the terminal sends the random access preamble sequence, i.e., the Msg1 message. The time-frequency resources occupied by sending the random access preamble sequence are called PRACH resources (which are broadcast by the network side to all terminals in the SIB signaling to allow the use of random access preamble sequences). The terminal selects a random access preamble sequence and sends it on the PRACH resources.

[0031] Msg2 message is a type of DCI signaling, carried on PDCCH resources or as one of the random access responses scheduled by DCI signaling / PDCCH signaling.

[0032] The Msg3 message is transmitted on the UL-SCH and contains either a C-RNTIMAC CE or a CCCH SDU (core network identifier). The Msg3 message is also used for multiplexing the Dedicated Traffic Channel (DTCH) in User Plane Embedded Deterministic Test (UP-EDT). As part of the random access procedure, the Msg3 message is submitted from the upper layer and associated with terminal contention for identity resolution.

[0033] Msg4 is a type of DCI signaling, carried on PDCCH resources or scheduled by DCI signaling / PDCCH signaling as one of the contention resolution messages. The contention resolution window can be mac-ContentionResolutionTimer, which can specify the number of consecutive subframes the MAC entity monitors the PDCCH after the Msg3 message is sent.

[0034] Msg5 is an RRC establishment completion message or an RRC recovery completion message, carried on the PUSCH resource, indicating that the terminal enters the RRC connection state.

[0035] For example Figure 2 The random access procedure shown in the R17 standard enhances the coverage of PUSCH messages (such as the Msg3 message) to support repeated transmission. In the R18 standard, coverage is enhanced for PRACH messages (such as the Msg1 message) and PUCCH messages carrying Msg4 HARQ-ACK, such as repeating PRACH messages and repeating PUCCH messages carrying Msg4 HARQ-ACK. In the R19 standard, due to coverage bottlenecks, coverage enhancement for the Msg4 message is under discussion, including supporting repeated transmission, with a maximum repetition count of 2 or 4 times. To support repeated transmission of the Msg4 message, the corresponding repetition factor configuration methods, such as dynamic indication via DCI signaling, indication via higher-layer parameters (SIB), or implicit indication via SIBPDSCH repetition, are under discussion. Msg4 messages typically carry around 1000 bits, while PUSCH messages with similar payloads (such as Msg5 messages scheduled by DCI format 0_0, such as RRC Setup Complete message, RRC Resume Complete message, etc., with an effective payload of approximately 984 bits) do not currently support repetition.

[0036] To overcome the current problem that some messages (such as RRC establishment completion messages and RRC recovery completion messages with similar payloads to the Msg4 message) do not support repetition, embodiments of this application provide a communication method, a communication node, a computer-readable storage medium, and a computer program product. A first communication node first determines the transmission parameters of a first message, wherein the transmission parameters of the first message include at least a repetition factor. Then, the first communication node sends the first message to a second communication node according to the transmission parameters of the first message. In this way, the first communication node can repeatedly send the first message to the second communication node based on transmission parameters that include at least a repetition factor, thus supporting the repetition of the first message. Therefore, even if the first message is a PUSCH message with a similar payload to the Msg4 message, repetition can be supported, thereby overcoming the current problem that some messages do not support repetition.

[0037] The technical solutions provided in this application can be applied to contention-based four-step random access, two-step random access, non-contention-based random access, or random access without Msg1 and Msg2 messages in NR, LTE, LTE-A, eMTC, NB-IoT, and future mobile communications. That is, when it is necessary to send an RRC establishment completion response or RRC recovery completion response message, the communication method in this application can be used to achieve coverage enhancement.

[0038] Furthermore, the technical solutions provided in this application embodiment can also be applied to the Random Access-Small Data Transmission (RA-SDT) process in the RRC_IDLE state or the RRC_INACTIVE state. For this process, the configuration information can be configured in the RRC release message or in the SIB signaling. It is worth noting that the former is a signaling that is different from other processes.

[0039] The communication method provided in the embodiments of this application will be further described below.

[0040] Reference Figure 3 , Figure 3 This is a flowchart of a communication method provided in an embodiment of this application, which is applied to a first communication node. Figure 3 In this process, the communication method may include, but is not limited to, steps S310 to S320.

[0041] Step S310: Determine the transmission parameters of the first message;

[0042] Step S320: Send the first message to the second communication node according to the transmission parameters of the first message.

[0043] In some embodiments, the transmission parameters of the first message include at least a repetition factor.

[0044] Through the communication method described in steps S310 to S320, the first communication node first determines the transmission parameters of the first message, wherein the transmission parameters of the first message include at least a repetition factor. Then, the first communication node sends the first message to the second communication node according to the transmission parameters of the first message. In this way, the first communication node can repeatedly send the first message to the second communication node based on transmission parameters that include at least a repetition factor, thus supporting the repetition of the first message. Therefore, even if the first message is a PUSCH message with a similar payload to the Msg4 message, repetition can be supported, thereby overcoming the current problem that some messages do not support repetition.

[0045] In some embodiments, the first communication node may be a terminal (i.e., UE), and the corresponding second communication node may be a base station.

[0046] In some embodiments, the first message includes a PUSCH message. This PUSCH message may include at least one of the following: an RRC establishment completion response message, an RRC recovery completion response message, a Msg3 message, a PUSCH message retransmitted during Small Data Transmission (SDT), a PUSCH message during the SDT process, and a PUSCH message when a dedicated resource is not configured. This allows at least one of the above-mentioned messages to support repetition, thereby overcoming the current problem that some messages do not support repetition.

[0047] In some embodiments, the repetition factor of the first message can be determined by the transmission parameters of the second message. The second message may include at least one of the following: a control message for scheduling a random access response message, a random access response message, a control message for scheduling contention resolution messages, a contention resolution message, a control message for scheduling an RRC establishment completion response message, a control message for scheduling an RRC recovery completion response message, a random access preamble message, a Msg3 message, a PUCCH message for carrying HARQ-ACK feedback for the contention resolution message, a Physical Downlink Shared Channel (PDSCH) message, a PUSCH message transmitted initially during SDT, a msgA PUSCH message during two-step random access, and a common PUCCH message. The transmission parameters of the second message may include at least one of the following: repetition factor, transport block scaling (TB scaling), modulation and coding scheme (MCS), time-domain resource allocation, frequency-domain resource allocation, period, and power. This allows for flexible determination of the repetition factor of the first message, thereby meeting the needs of different scenarios. It is worth noting that, generally, the second message will be sent or received before the first message is sent.

[0048] In some embodiments, the repetition factor of the first message can be specifically determined by the repetition factor of the second message. This improves the efficiency of determining the repetition factor of the first message.

[0049] In some embodiments, the repetition factor of the first message can be determined by the second communication node through a first DCI signaling indication, wherein the repetition factor of the first message indicated by the first DCI signaling is one of a plurality of repetition factors of the second messages.

[0050] In some embodiments, the repetition factor of the first message may also be determined by the second communication node through higher-layer signaling.

[0051] In some embodiments, the repetition factor of the first message can also be determined by the second communication node through a second DCI signaling indication. In this case, the repetition factor of the first message is directly indicated by the second DCI signaling.

[0052] In some embodiments, the repetition factor of the first message can be equal to the repetition factor of the second message, wherein the repetition factor of the second message is determined by the second communication node through a second DCI signaling instruction. In this case, the repetition factor of the second message is first determined through the second DCI signaling, and then the repetition factor of the first message is equal to the repetition factor of the second message.

[0053] In some embodiments, the repetition factor of the first message can be the repetition factor that the first communication node selects from among the repetition factors of multiple second messages to report.

[0054] In some embodiments, the repetition factor of the first message may also be the repetition factor that the first communication node selects from a plurality of repetition factors of the second message to report and apply to the first message.

[0055] In some embodiments, the repetition factor of the first message may be determined by the second communication node through the first DCI signaling in the repetition factor reported by the first communication node.

[0056] In some embodiments, the repetition factor of the first message may also be determined by the second communication node through the second DCI signaling in the repetition factor reported by the first communication node.

[0057] In the above embodiments, the first DCI signaling may include one of the following: a newly added field in the DCI signaling for scheduling the first message, or an existing target field in the DCI signaling for scheduling the first message. The second DCI signaling may include one of the following: a newly added field in the DCI signaling for scheduling the second message, or an existing target field in the DCI signaling for scheduling the first message. The existing target field may include one of the following: a modulation and coding field, a redundancy version field, a new data indication field, a time-domain resource allocation field, a frequency-domain resource allocation field, a power control field, or a reserved field. In a possible implementation, the existing target field may include, in addition to one of the above fields, a target bit, a target state, or a target code point from one of the above fields; this embodiment does not specifically limit this.

[0058] In some embodiments, where the repetition factor of the first message is determined by the second communication node through the first DCI signaling in the repetition factor reported by the first communication node, the first DCI signaling can be used by the first communication node to perform at least one of a plurality of first operations and / or perform one of a plurality of second operations. The plurality of first operations include: sending the first message using the reported repetition factor when the first DCI signaling indicates that the repetition factor reported by the first communication node is used; sending the first message without using the reported repetition factor or without retransmitting the first message when the first DCI signaling indicates that the repetition factor reported by the first communication node is not used; and sending the first message without using the reported repetition factor and using the repetition factor indicated by the first DCI signaling when the first DCI signaling indicates that other repetition factors are used. The plurality of second operations include: sending the first message using the reported repetition factor when the first DCI signaling does not indicate a repetition factor; and sending the first message without using the reported repetition factor or without retransmitting the first message when the first DCI signaling does not indicate a repetition factor.

[0059] In some embodiments, the repetition factor of the first message can also be determined by scaling the repetition factor of the second message according to a scaling factor, wherein the scaling factor is a predefined factor or is indicated by the second communication node through higher-layer signaling or third DCI signaling. The repetition factor of the second message can be a predefined factor or is indicated by the second communication node through higher-layer signaling or second DCI signaling. After scaling the repetition factor of the second message according to the scaling factor, the scaled repetition factor is used by the first communication node to send the first message.

[0060] In some embodiments, the third DCI signaling may include one of the following: a newly added field in the DCI signaling of the scheduling second message, a newly added field in the DCI signaling of the scheduling first message, an existing target field in the DCI signaling of the scheduling second message, or an existing target field in the DCI signaling of the scheduling first message. The existing target field may include one of the following: a modulation and coding field, a redundancy version field, a new data indication field, a time-domain resource allocation field, a frequency-domain resource allocation field, a power control field, or a reserved field.

[0061] In some embodiments, the repetition factor of the first message can also be determined based on the transport block scaling parameter or the MCS parameter of the second message. Each value of the transport block scaling parameter corresponds to a repetition factor of the first message; each value or set of values ​​of the MCS parameter corresponds to a repetition factor of the first message.

[0062] In some embodiments, the repetition factor of the first message may also be determined by a common repetition factor indicated by the second communication node. In this case, the common repetition factor determined by the second communication node may also be used by the first communication node to receive or send the third message. The third message may include at least one of the following: a random access preamble sequence, a random access response message, an RRC establishment request message, a contention resolution message, a PUCCH message for carrying HARQ-ACK feedback of the contention resolution message, an RRC establishment complete message, and an RRC recovery complete message.

[0063] In some embodiments, the repetition factor of the third message can be determined by the first communication node by scaling the common repetition factor indicated by the second communication node according to a common scaling factor. This common scaling factor can be a predefined factor, or it can be indicated by the second communication node via higher-layer signaling or fourth DCI signaling.

[0064] In some embodiments, the fourth DCI signaling may include one of the following: DCI for scheduling random access response, DCI for scheduling contention resolution message, DCI for scheduling RRC establishment completion response message, DCI for scheduling RRC recovery completion response message, and common DCI.

[0065] In some embodiments, when the third message includes multiple messages, the repetition factor corresponding to one of the multiple messages included in the third message can be determined by the common repetition factor corresponding to another message included in the multiple messages, wherein one of the multiple messages is transmitted after the other message in the multiple messages.

[0066] In some embodiments, when the third message includes multiple messages, the request for duplication or duplication capability reporting of another message among the multiple messages included in the third message may be the same as the request for duplication or duplication capability reporting of one message among the multiple messages included in the third message.

[0067] In some cases, certain terminals (such as some first communication nodes) may not have the capability to repeat PUSCH messages. Therefore, these terminals need to send a PUSCH message repetition request or report their repetition capability to the network side (such as the base station) so that the network side (such as the base station) can confirm which terminals have the capability to repeat PUSCH messages. Therefore, in some embodiments, the first communication node can also send a request for repetition or a repetition capability report to the second communication node via a fourth message. The fourth message may include one of the following: Msg3 message, random access preamble message, or common PUCCH message.

[0068] In some embodiments, the request for repetition or repetition capability reporting in the first message may be the same as the request for repetition or repetition capability reporting in the second message.

[0069] In some embodiments, the request for duplication or duplication capability reporting in the first message may be the same as the request for duplication or duplication capability reporting in one of the multiple messages included in the third message. The third message may include at least one of the following: a random access preamble sequence, a random access response message, an RRC establishment request message, a contention resolution message, a PUCCH message for carrying HARQ-ACK feedback of the contention resolution message, an RRC establishment complete message, and an RRC recovery complete message.

[0070] In some embodiments, the request for repetition or repetition capability reporting may be carried in one of the following ways: higher-layer signaling carried in the Msg3 message, physical-layer signaling carried in the Msg3 message, target value of the identity carried in the scrambled Msg3 message, payload of higher-layer signaling carried in the Msg3 message, target preamble sequence carried in the random access preamble message, target random access timing carried in the random access preamble message, or target time-frequency resource carried in the random access preamble message.

[0071] In some embodiments, if the request for duplication or duplication capability reporting of another message among the plurality of messages included in the third message is the same as the request for duplication or duplication capability reporting of one message among the plurality of messages included in the third message, or if the request for duplication or duplication capability reporting of the first message is the same as the request for duplication or duplication capability reporting of the second message, or if the request for duplication or duplication capability reporting of the first message is the same as the request for duplication or duplication capability reporting of one message among the plurality of messages included in the third message, at least one of the following conditions must be met:

[0072] The second communication node indicates one or more repetition factors, the second communication node indicates one or more scaling factors, the signal quality measured by the first communication node is lower than a first threshold configured by the second communication node, the second communication node enables repetition for the first message, the second communication node enables repetition for the second message, and the second communication node enables repetition for the third message.

[0073] In some embodiments, the first communication node may perform the determination of repetition factors if at least one of the following conditions is met: the signal quality measured by the first communication node is lower than a first threshold configured by the second communication node; the first communication node sends a request for repetition or a repetition capability report to the second communication node; the second communication node indicates multiple repetition factors; the second communication node indicates multiple scaling factors; the second communication node enables repetition for a first message; the second communication node enables repetition for a second message; or the second communication node enables repetition for a third message.

[0074] It should be noted that, in the above embodiments, the specific value of the first threshold can be appropriately selected according to actual application needs, and this embodiment does not impose a specific limitation on it. For example, in a feasible implementation, the value of the first threshold can be 99 or other values.

[0075] Through the above embodiments, the first communication node can repeatedly send the first message to the second communication node based on transmission parameters that include at least a repetition factor, thereby supporting the repetition of the first message. In this way, even if the first message is a PUSCH message with a similar payload to the Msg4 message, repetition can be supported, thus overcoming the current problem that some messages do not support repetition.

[0076] The communication method provided in this application will be described in detail below with specific embodiments.

[0077] It should be noted that the coverage performance of PUSCH messages can be enhanced through the specific embodiments described below.

[0078] Example 1: PUSCH message repetition factor configuration / indication

[0079] 1. The repetition factor of the PUSCH message can be configured / indicated by the network side (such as RRC signaling, MAC CE signaling, SIB signaling, MIB signaling). For example, the network side can configure / indicate one repetition factor or multiple repetition factors.

[0080] 1.1 When configuring / indicating a repetition factor on the network side, it can be configured / indicated through higher-layer signaling, and the terminal uses the repetition factor to send PUSCH messages.

[0081] 1.2 When the network side configures / indicates multiple repetition factors, it can dynamically indicate the specific repetition factor to the terminal through the first DCI signaling, and the terminal uses the specific repetition factor to send the PUSCH message.

[0082] The first DCI signaling can be the DCI signaling for scheduling PUSCH messages (such as RRC establishment completion response or RRC reply completion response). For example, it can be a newly added or dedicated field in the DCI signaling, or it can be some fields reused in the DCI, such as a redundancy version field, a new data indication field, a time domain resource allocation field, a frequency domain resource allocation field, a power control field, or a reserved field. The reused fields in the DCI may be certain bits of certain fields, certain states of certain fields, or certain codepoints of certain fields.

[0083] 2. The repetition factor of the PUSCH message can reuse the repetition factor configuration / indication of the second message. Specifically, such as reusing the repetition factor of the random access response message (Msg2 message), or reusing the repetition factor of the contention resolution message (Msg4 message), or reusing the repetition factor of the common PDSCH message.

[0084] 2.1 When the network side only configures / indicates a repetition factor for the second message, the repetition factor can be used for the repetition factors of the second message and the PUSCH message. The terminal uses the repetition factor to receive the second message and uses the repetition factor to send the PUSCH message.

[0085] 2.2 When the network side configures / indicates multiple repetition factors for the second message, the terminal-specific repetition factor is indicated by the second DCI signaling. That is, the second DCI signaling is used to indicate the terminal-specific repetition factor. This repetition factor can be used for the repetition factors of the second message and the PUSCH message. The terminal uses the indicated repetition factor to receive the second message and uses the indicated repetition factor to send the PUSCH message.

[0086] The second DCI signaling can be DCI signaling that schedules the second message. For example, it can be a newly added field in the DCI signaling, or it can be some fields that are reused in the DCI, such as the index field assigned in the following row.

[0087] 2.3 When the network side configures / indicates multiple repetition factors for the second message, the terminal reuses these repetition factors, reports (requested / suggested) repetition factors, and uses the repetition factors.

[0088] 2.4 When the network side configures / indicates multiple repetition factors for the second message, the terminal reuses these repetition factors and reports (requested / suggested) repetition factors. The network side indicates whether to use the repetition factors reported by the terminal through the first DCI signaling.

[0089] 2.4.1 If the first DCI signaling indicates the use of the repetition factor reported by the terminal, the terminal sends a PUSCH message using the reported repetition factor.

[0090] 2.4.2 If the first DCI signaling indicates that the repetition factor reported by the terminal is not used, then the terminal will not use the reported repetition factor to send the PUSCH message, or will not resend the PUSCH message.

[0091] 2.4.3 If the first DCI signaling instructs the terminal to use a different repetition factor, the terminal will send the PUSCH message using the repetition factor indicated by the network instead of the reported repetition factor.

[0092] 2.4.4 If the first DCI signaling does not indicate the repetition factor, the terminal directly uses the reported repetition factor to send the PUSCH message.

[0093] 2.4.5 If the first DCI signaling does not indicate a repetition factor, the terminal will not use the reported repetition factor to send the PUSCH message, or will not resend the PUSCH message.

[0094] 3. The repetition factor of the PUSCH message can be scaled by reusing the repetition factor configuration / indication of a second message. The second message can be a random access response message, a contention resolution message, or a common PDSCH message (SIB1 PDSCH). Specifically, it can reuse and scale the repetition factor of a random access response message (Msg2 message), or reuse and scale the repetition factor of a contention resolution message (Msg4 message), or reuse and scale the repetition factor of a common PDSCH message. The scaling factor can be configured / indicated by higher-layer configuration signaling (such as RRC signaling, MAC CE signaling, SIB signaling, MIB signaling), or it can be predefined.

[0095] 3.1 When the network side configures / indicates a repetition factor only for the second message, and the network side configures / indicates a scaling factor only for the PUSCH message or the standard predefines a scaling factor, the repetition factor can be used for the repetition factor of the second message, and the repetition factor of the second message is scaled to obtain the actual repetition factor of the PUSCH message. The terminal uses the repetition factor of the second message to receive the second message, and uses the actual repetition factor to send the PUSCH message.

[0096] 3.2 When the network side configures / indicates only one repetition factor for the second message, and the network side configures / indicates multiple scaling factors for the PUSCH message or the standard predefines multiple scaling factors, the repetition factor can be used as the repetition factor of the second message, and the third DCI signaling is used to indicate the specific scaling factor of the PUSCH message. Then the terminal uses the indicated scaling factor to scale the repetition factor of the second message to obtain the actual repetition factor of the PUSCH message. The terminal uses the repetition factor of the second message to receive the second message, and uses the actual repetition factor to send the PUSCH message.

[0097] The third DCI signaling can be DCI signaling that schedules the second message, or it can be DCI signaling that schedules the PUSCH message (such as RRC establishment completion response or RRC reply completion response). For example, it can be a newly added field or some fields in the DCI that are reused.

[0098] 3.3 When the network side configures / indicates multiple repetition factors for the second message, and the terminal-specific repetition factor is indicated by the second DCI signaling or by the second message (such as a random access response message), that is, the terminal-specific repetition factor is indicated by the second DCI signaling or the random access response message, and the network side only configures / indicates one scaling factor for the PUSCH message, the repetition factor can be used for the repetition factor of the second message. The repetition factor of the second message can be scaled using the repetition factor configured / indicated by the network side to obtain the actual repetition factor of the PUSCH message. The terminal uses the indicated repetition factor to receive the second message and uses the actual repetition factor to send the PUSCH message.

[0099] 3.4 When the network side configures / indicates multiple repetition factors for the second message, and the terminal-specific repetition factor is indicated by the second DCI signaling or by the second message (such as a random access response message), that is, the terminal-specific repetition factor is indicated by the second DCI signaling or the random access response message, and the network side configures / indicates multiple scaling factors for the PUSCH message and uses the third DCI signaling to indicate the specific scaling factor of the PUSCH message, the indicated repetition factor can be used for the repetition factor of the second message. Then, the terminal uses the indicated scaling factor to scale the indicated repetition factor of the second message to obtain the actual repetition factor of the PUSCH message. The terminal uses the repetition factor of the second message to receive the second message and uses the actual repetition factor to send the PUSCH message.

[0100] 4. The repetition factor of the PUSCH message can be associated with parameters of the second message. These parameters may include one of the following: MCS, TB scaling, time-domain resource allocation, frequency-domain resource allocation, period, power, etc. For the parameters of the second message, each configuration / indication / value corresponds to a repetition factor of the PUSCH message. The terminal uses / determines the repetition factor of the PUSCH message based on the parameter configuration / indication of the second message. For example:

[0101] 4.1 For the TB scaling parameter of the Msg2 message, each value corresponds to a repetition factor of the PUSCH message. For example, when the TB scaling field configuration / indication is 00, the corresponding TB scaling factor of the Msg2 message is 1, and it can also correspond to a repetition factor X of the PUSCH message; when the TB scaling field configuration / indication is 01, the corresponding TB scaling factor of the Msg2 message is 0.5, and it can also correspond to a repetition factor Y of the PUSCH message; and so on. Since a larger TB scaling factor for the Msg2 message usually corresponds to a higher code rate, which usually means better channel conditions, it corresponds to a lower repetition factor of the PUSCH message.

[0102] 4.2 For the MCS parameter of the second message, each value or set of values ​​corresponds to the repetition factor of a PUSCH message. MCS values ​​[0, ..., M] correspond to the repetition factor X of the PUSCH message; MCS values ​​[M+1, ..., N] correspond to the repetition factor Y of the PUSCH message; and so on. Since a larger MCS for the second message usually corresponds to a higher code rate, which generally means better channel conditions, it corresponds to a lower repetition factor for the PUSCH message.

[0103] 5. The network side configures / indicates a common repetition factor. The terminal determines whether to receive or send the third message using this repetition factor. The third message can be a random access preamble (Msg1 message), a random access response message (Msg2 message), an RRC establishment request message (Msg3 message), a contention resolution message (Msg4 message), a PUCCH message carrying the HARQ-ACK feedback of the contention resolution message, an RRC establishment completion message or an RRC recovery completion message (Msg5 message).

[0104] 6. Configure / indicate a common repetition factor on the network side, and configure a common scaling factor.

[0105] 6.1 The terminal determines whether to receive or send the third message using the repetition factor.

[0106] 6.2. The terminal determines that the third message uses the repetition factor and obtains a new repetition factor after scaling, and then receives or sends the message.

[0107] 6.3 The terminal determines that a certain message of the aforementioned third message is received or sent following the repetition factor of another message of the aforementioned third message, wherein the other message is transmitted before the certain message.

[0108] 7. Configure / indicate a common repetition factor on the network side, and configure multiple common scaling factors.

[0109] 7.1 The terminal determines whether to receive or send the third message using the repetition factor.

[0110] 7.2 The network side configures / indicates a specific scaling factor through the fourth DCI signaling. The terminal determines that the third message uses the repetition factor and scales it using the indicated scaling factor to obtain a new repetition factor for receiving or sending.

[0111] 7.3 The terminal determines that a certain message of the aforementioned third message is received or sent following the repetition factor of another message of the aforementioned third message, wherein the other message is transmitted before the certain message.

[0112] 8. Configure / indicate multiple common repetition factors on the network side, and configure / indicate a common scaling factor.

[0113] 8.1 The network side configures / indicates the specific repetition factor through the fourth DCI signaling, and the terminal determines whether to receive or send the third message using the repetition factor.

[0114] 8.2 The network side configures / indicates the specific repetition factor through the fourth DCI signaling. The terminal determines that the third message uses the repetition factor and scales it using a scaling factor before receiving or sending it.

[0115] 8.3 The terminal determines that a certain message of the aforementioned third message is received or sent following the repetition factor of another message of the aforementioned third message, wherein the other message is transmitted before the certain message.

[0116] 9. Configure / indicate multiple common repetition factors on the network side, and configure / indicate multiple common scaling factors.

[0117] 9.1 The network side configures / indicates the specific repetition factor through the fourth DCI signaling, and the terminal determines whether to receive or send the third message using the repetition factor.

[0118] 9.2 The network side configures / indicates the specific repetition factor through the fourth DCI signaling, and configures / indicates the specific scaling factor through the fourth DCI signaling. The terminal determines that the third message uses the repetition factor and scales it using the scaling factor before receiving or sending it.

[0119] 9.3 The terminal determines that a certain message of the aforementioned third message is received or sent following the repetition factor of another message of the aforementioned third message, wherein the other message is transmitted before the certain message.

[0120] The fourth DCI signaling can be a DCI for a scheduling random access response, a DCI for a scheduling contention resolution message, a DCI for a scheduling RRC establishment completion response message or an RRC recovery completion response message, or a common DCI.

[0121] It should be noted that when DCI indicates a specific repetition factor for a terminal, each code point or state may correspond to a repetition factor, or an index of a repetition factor. For example, the standard may define the alternative values ​​for the repetition factor as 1, 2, 4, and 8. DCI uses 2 bits or 4 code points / states (e.g., 00, 01, 10, 11) to indicate the repetition factor. The 4 code points may then correspond to repetition factors 1, 2, 4, and 8, respectively. Alternatively, the 4 code points may correspond to the 1st, 2nd, 3rd, and 4th repetition factors configured / indicated by the standard or network side.

[0122] Example 2: Reporting of duplicate requests or duplicate capability for PUSCH messages

[0123] Some terminals may not have the ability to repeat PUSCH messages. Therefore, the terminal needs to send a PUSCH message repetition request to the network side or report the repetition capability. At least one of the following methods can be used:

[0124] 1. If the terminal sends a request for duplication or duplication capability reporting in response to the second message via the fourth message, then the terminal reuses the request for duplication or duplication capability reporting as a request for duplication or duplication capability reporting for the PUSCH message. That is, when the terminal sends a request for duplication or duplication capability reporting in response to the second message via the fourth message, the terminal considers that it has sent a request for duplication or duplication capability reporting for the PUSCH message.

[0125] The fourth message can be a Msg3 message, a Msg1 message, or a public PUCCH message (such as a PUCCH that carries a contention resolution message HARQ-ACK feedback).

[0126] The request for repetition or repetition capability reporting can be carried by the higher-layer signaling of the Msg3 message (such as LCID or MAC subheader), or by the physical layer signaling of the Msg3 message (such as DMRS port) or a specific value of the identity identifier of the scrambled Msg3 message, or by the payload of the higher-layer signaling of the Msg3 message (such as CCCH, MAC CE or MAC PDU), or by the specific preamble sequence, specific random access timing or specific time-frequency resources used by the Msg1 message.

[0127] 2. If the terminal has sent a request for duplication or duplication capability reporting for a certain message in the third message, the terminal will reuse the request for duplication or duplication capability reporting as a request for duplication or duplication capability reporting for the PUSCH message.

[0128] 3. If the terminal has sent a request for duplication or duplication capability reporting for a certain message in the third message, the terminal reuses the request for duplication or duplication capability reporting as a request for duplication or duplication capability reporting for another message in the third message, and the other message is transmitted after the first message.

[0129] Example 3: Conditions for capability reporting and / or determination of the repeatability factor

[0130] 1. Conditions for reporting duplicate requests or duplicate capabilities in PUSCH messages.

[0131] In the previously described embodiment 2, a method for repeating requests or repeating capability reports for PUSCH messages was defined, that is, the terminal reuses the repeating request or capability reporting signaling of the second message. However, the terminal needs to meet certain conditions to determine whether to repeat the PUSCH message based on the current channel state.

[0132] Whether a terminal sends a request for duplicate or duplicate capability reporting in response to a PUSCH message or a third message requires at least one of the following conditions to be met:

[0133] (1) When the network side configures / indicates one or more repetition factors, wherein the repetition factor is a repetition factor configured / indicated by the network side and the repetition factor of the second message can be reused.

[0134] (2) When the network side configures / indicates one or more scaling factors, wherein the scaling factor is a scaling factor configured / indicated by the network side and can reuse the factor of the second message.

[0135] (3) When the measured signal quality is lower than the first threshold configured / indicated by the network side, wherein the first threshold is the threshold configured / indicated by the network side for the terminal to determine whether to send a request for PUSCH message repetition or the PUSCH message repetition capability report. The first threshold can reuse the corresponding threshold of the second message or be a newly defined threshold.

[0136] (4) When the network side enables the repetition of the second message.

[0137] (5) When the network side enables the repetition of PUSCH messages.

[0138] (6) When the network side enables the repetition of third messages.

[0139] Specifically, for example, when a terminal sends a request for duplication or duplication capability reporting in response to a second message via a third message, if the signal quality measured by the terminal is lower than the first threshold configured / indicated by the network side, the terminal considers that it has sent a request for duplication or duplication capability reporting in response to the PUSCH message.

[0140] 2. Conditions for determining the repetition factor of the PUSCH message

[0141] In Embodiment 1 described above, a method for configuring / indicating one or more repetition factors or scaling factors on the network side is defined. Further, when configuring / indicating multiple repetition factors or scaling factors, DCI signaling is required to indicate specific repetition factors or scaling factors.

[0142] When configuring / indicating one or more repetition factors or scaling factors on the network side, or indicating a specific repetition factor or scaling factor via DCI signaling, the terminal must meet at least one of the following conditions when determining the repetition factor or scaling factor of the PUSCH message or third message:

[0143] (1) When the measured signal quality is lower than the first threshold configured / indicated by the network side, wherein the first threshold can also be interpreted as the threshold of the dynamic indication configured / indicated by the network side for the terminal to determine whether to reuse certain fields in the DCI as a repetition factor.

[0144] (2) When the terminal sends a request to repeat or a repeat capability report.

[0145] (3) When the network side configures / indicates multiple repetition factors, the repetition factor is the repetition factor configured / indicated by the network side, and the repetition factor of the second message can be reused.

[0146] (4) When the network side configures / indicates multiple scaling factors, the scaling factor is the scaling factor configured / indicated by the network side, and the factor of the second message can be reused.

[0147] (5) When the network side enables the repetition of the second message.

[0148] (6) When the network side enables the repetition of PUSCH messages.

[0149] (7) When the network side enables the repetition of third messages.

[0150] 3. Repeated execution process of PUSCH messages

[0151] 3.1 When no first threshold is configured / indicated

[0152] The network side configures / indicates a repetition factor, and the PUSCH message reuses the repetition factor of the second message:

[0153] 3.1.1 When the terminal sends a request for repetition or repetition capability reporting in response to the second message via a third message, the terminal uses the repetition factor to send a PUSCH message for repetition.

[0154] 3.1.2 Use the repetition factor to send PUSCH messages repeatedly.

[0155] 3.2 When configuring / indicating the first threshold

[0156] The network side configures / indicates a repetition factor, and the PUSCH message reuses the repetition factor of the second message:

[0157] 3.2.1 When the terminal sends a request for repetition or repetition capability reporting in response to the second message via the third message, if the measured signal quality is lower than the first threshold, the repetition factor is used to send the PUSCH message again; if the measured signal quality is higher than the first threshold, the repetition transmission of the PUSCH message is not performed.

[0158] 3.2.2 If the measured signal quality is lower than the first threshold, the terminal uses the repetition factor to send the PUSCH message repeatedly; if the measured signal quality is higher than the first threshold, the PUSCH message is not retransmitted.

[0159] 3.2.3 When the terminal sends a request for repetition or a repetition capability report in response to the second message via a third message, if the measured signal quality is lower than the first threshold and the terminal sends / indicates a request for PUSCH message repetition or PUSCH message repetition capability, then the repetition factor is used to send PUSCH message repetition; if the measured signal quality is higher than the first threshold and the terminal does not send / indicate a request for PUSCH message repetition or PUSCH message repetition capability, then the repetition transmission of the PUSCH message is not performed.

[0160] 3.2.4 If the measured signal quality is lower than the first threshold and the terminal sends / indicates a request for PUSCH message repetition or PUSCH message repetition capability, the terminal shall use the repetition factor to send PUSCH message repetition; if the measured signal quality is higher than the first threshold and the terminal does not send / indicate a request for PUSCH message repetition or PUSCH message repetition capability, the repetition transmission of PUSCH message shall not be performed.

[0161] 3.3 When no first threshold is configured / indicated

[0162] The network side configures / indicates a repetition factor and configures / indicates a scaling factor for PUSCH message repetition:

[0163] 3.3.1 When the terminal sends a request for repetition or repetition capability reporting in response to the second message via a third message, the terminal uses the repetition factor obtained by scaling the repetition factor with the scaling factor to send a PUSCH message for repetition.

[0164] 3.3.2. Use the repeat factor obtained by scaling the repeat factor with the scaling factor to send the PUSCH message to repeat.

[0165] 3.4 When configuring / indicating the first threshold

[0166] The network side configures / indicates a repetition factor and configures / indicates a scaling factor for PUSCH message repetition:

[0167] 3.4.1 When the terminal sends a request for repetition or repetition capability reporting in response to the second message via a third message, if the measured signal quality is lower than the first threshold, the terminal sends the PUSCH message to repetite using the repetition factor obtained by scaling the repetition factor with the scaling factor; if the measured signal quality is higher than the first threshold, the repetition transmission of the PUSCH message is not performed.

[0168] 3.4.2 If the measured signal quality is lower than the first threshold, the terminal uses the repetition factor obtained by scaling the repetition factor with the scaling factor to send the PUSCH message repeatedly; if the measured signal quality is higher than the first threshold, the PUSCH message is not retransmitted repeatedly.

[0169] 3.4.3 When the terminal sends a request for repetition or a repetition capability report in response to the second message via a third message, if the measured signal quality is lower than the first threshold and the terminal sends / indicates a request for PUSCH message repetition or PUSCH message repetition capability, the terminal will use the repetition factor obtained by scaling the repetition factor with the scaling factor to send the PUSCH message repetition; if the measured signal quality is higher than the first threshold and the terminal does not send / indicate a request for PUSCH message repetition or PUSCH message repetition capability, the repetition transmission of the PUSCH message will not be performed.

[0170] 3.4.4 If the measured signal quality is lower than the first threshold and the terminal sends / indicates a request for PUSCH message repetition or PUSCH message repetition capability, the terminal uses the repetition factor obtained by scaling the repetition factor with the scaling factor to send PUSCH message repetition; if the measured signal quality is higher than the first threshold and the terminal does not send / indicate a request for PUSCH message repetition or PUSCH message repetition capability, the repetition transmission of PUSCH message is not performed.

[0171] 3.5. When no first threshold is configured / indicated

[0172] The network side configures / indicates a repetition factor and configures / indicates a scaling factor for the repetition of multiple PUSCH messages:

[0173] 3.5.1 When the terminal sends a request for repetition or repetition capability reporting in response to the second message via a third message, and the network side indicates a specific scaling factor via a third DCI signaling, the terminal sends a PUSCH message for repetition using the repetition factor obtained by scaling the repetition factor with the scaling factor.

[0174] 3.5.2 The network side indicates the specific scaling factor through the third DCI signaling. The terminal uses the scaling factor to obtain the repetition factor after scaling the repetition factor to send the PUSCH message for repetition.

[0175] 3.6 When configuring / indicating the first threshold

[0176] The network side configures / indicates a repetition factor and configures / indicates a scaling factor for the repetition of multiple PUSCH messages:

[0177] 3.6.1 When the terminal sends a request for repetition or repetition capability reporting in response to the second message via the third message, if the measured signal quality is lower than the first threshold and the network side indicates a specific scaling factor through the third DCI signaling, the terminal sends the PUSCH message to repetite using the repetition factor obtained by scaling the repetition factor with the scaling factor; if the measured signal quality is higher than the first threshold, the repetition transmission of the PUSCH message is not performed.

[0178] 3.6.2 If the measured signal quality is lower than the first threshold and the network side indicates a specific scaling factor through the third DCI signaling, the terminal uses the scaling factor to obtain the repetition factor after scaling the repetition factor to send the PUSCH message repeatedly; if the measured signal quality is higher than the first threshold, the repetition transmission of the PUSCH message is not performed.

[0179] 3.6.3 When the terminal sends a request for repetition or repetition capability reporting via a third message in response to the second message, if the measured signal quality is lower than the first threshold, and the terminal sends / indicates a request for PUSCH message repetition or PUSCH message repetition capability, and the network side indicates a specific scaling factor via the third DCI signaling, then the terminal uses the repetition factor obtained by scaling the repetition factor using the scaling factor to send the PUSCH message repetition; if the measured signal quality is higher than the first threshold, and the terminal does not send / indicate a request for PUSCH message repetition or PUSCH message repetition capability, then the repetition transmission of the PUSCH message is not performed.

[0180] 3.6.4 If the measured signal quality is lower than the first threshold, and the terminal sends / indicates a request for PUSCH repetition or PUSCH repetition capability, and the network side indicates a specific scaling factor through the third DCI signaling, then the terminal uses the repetition factor obtained by scaling the repetition factor with the scaling factor to send PUSCH message repetition; if the measured signal quality is higher than the first threshold, and the terminal does not send / indicate a request for PUSCH message repetition or PUSCH message repetition capability, then PUSCH message repetition transmission is not performed.

[0181] 3.7 When no first threshold is configured / indicated

[0182] The network side configures / indicates multiple repetition factors and configures / indicates a scaling factor for PUSCH message repetition:

[0183] 3.7.1 When the terminal sends a request for repetition or repetition capability reporting in response to the second message via the third message, and reuses the specific repetition factor indicated by the second DCI signaling, the terminal sends a PUSCH message for repetition using the repetition factor obtained by scaling the repetition factor with a scaling factor.

[0184] 3.7.2. Reuse the specific repetition factor indicated by the second DCI signaling, and the terminal uses the scaling factor to scale the repetition factor to obtain the repetition factor and sends the PUSCH message to repeat it.

[0185] 3.8 When configuring / indicating the first threshold

[0186] The network side configures / indicates multiple repetition factors and configures / indicates a scaling factor for PUSCH message repetition:

[0187] 3.8.1. The terminal sends a request for repetition or repetition capability reporting via a third message in response to the second message. If the measured signal quality is lower than the first threshold, the specific repetition factor indicated by the second DCI signaling is reused. The terminal uses the repetition factor obtained by scaling the repetition factor with a scaling factor to send the PUSCH message for repetition. If the measured signal quality is higher than the first threshold, the repetition transmission of the PUSCH message is not performed.

[0188] 3.8.2 If the measured signal quality is lower than the first threshold, the specific repetition factor indicated by the second DCI signaling is reused, and the terminal uses the repetition factor obtained by scaling the repetition factor with a scaling factor to send the PUSCH message repeatedly; if the measured signal quality is higher than the first threshold, the repetition transmission of the PUSCH message is not performed.

[0189] 3.8.3 When the terminal sends a request for repetition or a repetition capability report in response to the second message via a third message, if the measured signal quality is lower than the first threshold and the terminal sends / indicates a request for PUSCH message repetition or PUSCH message repetition capability, the specific repetition factor indicated by the second DCI signaling is reused, and the terminal uses the repetition factor obtained by scaling the repetition factor with the scaling factor to send PUSCH message repetition; if the measured signal quality is higher than the first threshold and the terminal does not send / indicate a request for PUSCH message repetition or PUSCH message repetition capability, the repetition transmission of the PUSCH message is not performed.

[0190] 3.8.4 If the measured signal quality is lower than the first threshold and the terminal sends / indicates a request for PUSCH message repetition or PUSCH message repetition capability, the specific repetition factor indicated by the second DCI signaling is reused, and the terminal uses the repetition factor obtained by scaling the repetition factor with the scaling factor to send PUSCH message repetition; if the measured signal quality is higher than the first threshold and the terminal does not send / indicate a request for PUSCH message repetition or PUSCH message repetition capability, the repetition transmission of PUSCH messages is not performed.

[0191] 3.9 When no first threshold is configured / indicated

[0192] The network side configures / indicates multiple repetition factors and configures / indicates scaling factors for multiple PUSCH message repetitions:

[0193] 3.9.1 When the terminal sends a request for repetition or repetition capability reporting in response to the second message via the third message, reuses the second DCI signaling to indicate the specific repetition factor, and the network side indicates the specific scaling factor via the third DCI signaling, the terminal sends the PUSCH message for repetition using the repetition factor obtained by scaling the repetition factor with the scaling factor.

[0194] 3.9.2 If the second DCI signaling indicates the specific repetition factor, and the network side indicates the specific scaling factor through the third DCI signaling, then the terminal uses the repetition factor obtained by scaling the repetition factor to send the PUSCH message for repetition.

[0195] 3.10. When configuring / indicating the first threshold

[0196] The network side configures / indicates multiple repetition factors and configures / indicates a scaling factor for PUSCH message repetition:

[0197] 3.10.1 When the terminal sends a request for repetition or repetition capability reporting in response to the second message via the third message, if the measured signal quality is lower than the first threshold, the specific repetition factor indicated by the second DCI signaling is reused, and the terminal sends the PUSCH message for repetition using the repetition factor obtained by scaling the repetition factor with a scaling factor; if the measured signal quality is higher than the first threshold, the repetition transmission of the PUSCH message is not performed.

[0198] 3.10.2 If the measured signal quality is lower than the first threshold, the specific repetition factor indicated by the second DCI signaling is reused, and the terminal uses the repetition factor obtained by scaling the repetition factor with a scaling factor to send the PUSCH message repeatedly; if the measured signal quality is higher than the first threshold, the repetition transmission of the PUSCH message is not performed.

[0199] 3.10.3 When the terminal sends a request for repetition or a repetition capability report in response to the second message via a third message, if the measured signal quality is lower than the first threshold and the terminal sends / indicates a request for PUSCH message repetition or PUSCH message repetition capability, the specific repetition factor indicated by the second DCI signaling is reused, and the terminal uses the repetition factor obtained by scaling the repetition factor with the scaling factor to send the PUSCH message repetition; if the measured signal quality is higher than the first threshold and the terminal does not send / indicate a request for PUSCH message repetition or PUSCH message repetition capability, then the repetition transmission of the PUSCH message is not performed.

[0200] 3.10.4 If the measured signal quality is lower than the first threshold and the terminal sends / indicates a request for PUSCH message repetition or PUSCH message repetition capability, the specific repetition factor indicated by the second DCI signaling is reused, and the terminal uses the repetition factor obtained by scaling the repetition factor with the scaling factor to send PUSCH message repetition; if the measured signal quality is higher than the first threshold and the terminal does not send / indicate a request for PUSCH message repetition or PUSCH message repetition capability, then the repetition transmission of PUSCH messages is not performed.

[0201] 3.11. When no first threshold is configured / indicated

[0202] The network side configures / indicates multiple repetition factors, and the PUSCH message reuses the repetition factor of the second message:

[0203] 3.11.1 When the terminal sends a request for repetition or repetition capability reporting in response to the second message via the third message, and reuses the specific repetition factor indicated by the second DCI signaling, the terminal uses the repetition factor to send the PUSCH message for repetition.

[0204] 3.11.2. Reuse the specific repetition factor indicated by the second DCI signaling and use the repetition factor to send PUSCH message repetitions.

[0205] 3.12. When configuring / indicating the first threshold

[0206] The network side configures / indicates multiple repetition factors, and the PUSCH message reuses the repetition factor of the second message:

[0207] 3.12.1 When the terminal sends a request for repetition or repetition capability reporting in response to the second message via the third message, if the measured signal quality is lower than the first threshold, the specific repetition factor indicated by the second DCI signaling is reused, and the terminal uses the repetition factor to send the PUSCH message repeatedly; if the measured signal quality is higher than the first threshold, the repetition transmission of the PUSCH message is not performed.

[0208] 3.12.2 If the measured signal quality is lower than the first threshold, the specific repetition factor indicated by the second DCI signaling is reused, and the terminal uses the repetition factor to send the PUSCH message repeatedly; if the measured signal quality is higher than the first threshold, the PUSCH message is not retransmitted.

[0209] 3.12.3 When the terminal sends a request for repetition or repetition capability reporting via a third message in response to the second message, if the measured signal quality is lower than the first threshold and the terminal sends / indicates a request for PUSCH message repetition or PUSCH message repetition capability, the specific repetition factor indicated by the second DCI signaling is reused, and the terminal uses this repetition factor to send PUSCH message repetition; if the measured signal quality is higher than the first threshold and the terminal does not send / indicate a request for PUSCH message repetition or PUSCH message repetition capability, then the repetition transmission of the PUSCH message is not performed.

[0210] 3.12.4 If the measured signal quality is lower than the first threshold and the terminal sends / indicates a request for PUSCH message repetition or PUSCH message repetition capability, the specific repetition factor indicated by the second DCI signaling is reused, and the terminal uses the repetition factor to send PUSCH message repetition; if the measured signal quality is higher than the first threshold and the terminal does not send / indicate a request for PUSCH message repetition or PUSCH message repetition capability, then the repetition transmission of PUSCH messages is not performed.

[0211] In this embodiment of the disclosure, the 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-granted PUSCH transmission; multiple repetitions of PUSCH transmission in pre-configured uplink resources (PUR); and multiple repetitions of PUSCH transmission in early data transmission (EDT).

[0212] For example, multiple repetitions of PUSCH transmissions scheduled by RAR messages can be msg3 scheduled by RAR(msg2) during a 4-step random access channel (RACH) process. As another example, multiple repetitions of PUSCH transmissions scheduled by fallback RAR messages can be msg3 scheduled by fallback RAR(msgB) during a 2-step RACH process.

[0213] 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 (uRLLCPUSCH), and massive machine type communications physical uplink shared channel (mMTC PUSCH).

[0214] Code division multiplexing is performed on the UE.

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

[0216] 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, a time granularity of one time slot, such as... Figure 2 As shown, assuming there are two UEs (UE1 and UE2), a 4-length OCC sequence is used, with the sequence [Si,1,Si,2,Si,3,Si,4], where i is the user's number. The data in each time slot is repeated four times and continuously mapped to the four time slots, with each time slot multiplied by an OCC codeword.

[0217] 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 that code sequence. The PUSCH groups within a PUSCH 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. These 16 repetition units can be divided into 4 PUSCH groups. Within each group, the content of each repetition must be completely identical for code sequence merging to be possible.

[0218] For example, such as Figure 4 As shown, the code sequence is 2-bit long, i.e., [s1, s2]. The PUSCH contains 8 PUSCH repeating units, each repeating unit being one time slot in length. If the PUSCH overlaps with repeating unit 3, then as shown in the figure, the first group of the PUSCH contains time slots n and n+1, while the PUSCH group overlapping with the PUSCH is the second group of the PUSCH, containing time slots n+2 and n+3.

[0219] Existing protocols include a mechanism for UCI multiplexing. For example, when the Physical Uplink Control Channel (PUCCH) and the PUSCH overlap in the time domain, the UCI on the PUCCH can be multiplexed onto the PUSCH. The UCI can include one or more of the following information: Acknowledgement (ACK) / Negative Acknowledgement (NACK) information, and Channel State Information (CSI). When the UCI is multiplexed onto the PUSCH, it occupies some time-frequency domain resources originally used for data transmission. These resources include those occupied by the data portion, the UCI, and the Demodulation Reference Signal (DMRS). Figure 2 As shown. When a PUSCH is repeatedly transmitted, the UCI is not multiplexed onto every PUSCH repeat transmission. Therefore, PUSCHs without multiplexed UCI are as follows: Figure 3As shown, it can be seen that the data components (time-frequency resource count, bitrate, etc.) may differ for each repetition.

[0220] However, when PUSCH is repeatedly transmitted, UCI is not multiplexed onto each PUSCH retransmission. Therefore, the signals of PUSCH retransmissions with multiplexed UCI and those without will be different. When the OCC sequence is added to different signals, the orthogonality between different UEs is disrupted, causing interference between users.

[0221] To address the aforementioned technical issues, one of the following methods can be used to avoid the violation of OCC sequence orthogonality, where PUCCH refers to a PUCCH that does not contain repeating units:

[0222] Option 1: When a PUCCH overlaps with a PUSCH repeating unit within a PUSCH group, if UCI multiplexing on the first PUSCH repeating unit of the PUSCH group can meet the timing requirements, then UCI can be multiplexed on every PUSCH repeating unit within the PUSCH group.

[0223] Otherwise, it is necessary to determine whether discarding the first PUSCH repeating unit in the PUSCH group meets the timing requirements. If the timing requirements are met, then all PUSCH repeating units in the PUSCH group are discarded.

[0224] If the timing requirements are not met, the PUCCH is discarded.

[0225] It should be understood that, in this scheme and the following schemes, meeting the timing requirements means that the user equipment has enough time to process a certain operation. For example, meeting the timing requirements for UCI multiplexing requires that the user equipment has enough processing time to make UCI multiplexed on each PUSCH repeating unit in the PUSCH group. Similarly, meeting the timing requirements for PUSCH discarding requires that the user equipment has enough time to discard all PUSCH repeating units in the PUSCH group.

[0226] Furthermore, it should be understood that in this scheme and the following schemes, UCI multiplexing on the first PUSCH repeating unit of the PUSCH group can meet the timing requirements, which is equivalent to UCI multiplexing on all PUSCH repeating units of the PUSCH group; discarding the first PUSCH repeating unit in the PUSCH group can meet the timing requirements, which is equivalent to discarding all PUSCH repeating units in the PUSCH group.

[0227] Option 2: By using base station scheduling to ensure that the PUCCH does not overlap with any non-first PUSCH repeating unit in any PUSCH group, and that multiplexing the UCI on the first PUSCH repeating unit of the PUSCH group can meet the timing requirements, the UCI is multiplexed on each PUSCH repeating unit in the PUSCH group.

[0228] It should be understood that, in this scheme and other schemes, the guarantee through base station scheduling can also be described from the user equipment side. For example, this scheme can be stated as follows: if the user equipment does not expect the PUCCH to overlap with any non-first PUSCH repeating unit in any PUSCH group, and if multiplexing the UCI on the first PUSCH repeating unit of the PUSCH group can meet the timing requirements, then the UCI is multiplexed on each PUSCH repeating unit in the PUSCH group.

[0229] Option 3: Base station scheduling is used to ensure that the PUCCH does not overlap with any non-first PUSCH repeating unit in any PUSCH group. When the PUCCH overlaps with the first PUSCH repeating unit in a certain PUSCH group, if the timing requirements can be met by multiplexing the UCI on the first PUSCH repeating unit of the PUSCH group, then the UCI is multiplexed on every PUSCH repeating unit in the PUSCH group.

[0230] Otherwise, it is necessary to determine whether discarding the first PUSCH repeating unit in the PUSCH group meets the timing requirements. If the timing requirements are met, then all PUSCH repeating units in the PUSCH group are discarded.

[0231] If the timing requirements are not met, the PUCCH is discarded.

[0232] Option 4: When a PUCCH overlaps with a PUSCH repeating unit within a PUSCH group, if UCI multiplexing on the first PUSCH repeating unit of the PUSCH group can meet the timing requirements, then UCI is multiplexed on every PUSCH repeating unit within the PUSCH group.

[0233] Otherwise, discard the PUCCH.

[0234] Option 5: Use base station scheduling to ensure that the PUCCH does not overlap with any non-first PUSCH repeating unit in any PUSCH group. When the PUCCH overlaps with the first PUSCH repeating unit in a certain PUSCH group, if the timing requirements can be met by multiplexing the UCI on the first PUSCH repeating unit of the PUSCH group, then the UCI can be multiplexed on every PUSCH repeating unit in the PUSCH group.

[0235] Otherwise, discard the PUCCH.

[0236] Option 6: When a PUCCH overlaps with a PUSCH repeating unit within a PUSCH group, if discarding the first PUSCH repeating unit within that PUSCH group can satisfy the timing requirements, then discard all PUSCHs within that PUSCH group.

[0237] If the timing requirements are not met, the PUCCH is discarded.

[0238] It should be understood that the above six schemes can be applied when PUSCH and PUCCH have the same priority. When PUCCH overlaps with a PUSCH repeating unit within a PUSCH group, if PUSCH has a higher priority than PUCCH, PUCCH needs to be discarded, and if PUCCH has a higher priority than PUSCH, all PUSCH repeating units within that PUSCH group need to be discarded.

[0239] In some embodiments, the network side can configure an OCC index parameter for the user equipment in Radio Resource Control (RRC) signaling. This parameter can indicate one or more OCC sequences, which in some embodiments include OCC sequences of different lengths. For example, this parameter can configure OCC for dynamically scheduled PUSCH transmissions, and can be configured in PUSCH-Config or PUSCH-Allocation-r1 IE. Alternatively, this parameter can also configure OCC for authorized PUSCH transmissions, and can be configured in configuredGrantConfig IE. For example, as shown in Table 1 below, the OCC index indicates the following OCC sequences when it ranges from 0 to 5.

[0240] Table 1

[0241] OCC Index OCC sequence OCC Index 0 [+1+1] OCC Index 1 [+1-1] OCC Index 2 [+1+1+1+1] OCC Index 3 [+1-1 +1-1] OCC Index 4 [+1 +1-1-1] OCC Index 5 [+1-1-1+1]

[0242] In some embodiments, the network side uses RRC signaling to configure an OCC index parameter, or an OCC index table, as shown in Table 2 below. The table defines special states / indexes to enable or disable OCC sequence functionality, such as the first or last index. Alternatively, in some embodiments, this special state / index can be used to modify / overwrite OCC sequence functionality enabled based on higher-layer signaling (e.g., RRC, MAC CE).

[0243] Table 2

[0244] OCC Index OCC sequence OCC Index 0 [+1+1] OCC Index 1 [+1-1] OCC Index 2 [+1+1+1+1] OCC Index 3 [+1-1 +1-1] OCC Index 4 [+1 +1-1-1] OCC Index 5 [+1-1-1+1] OCC Index 6 Enable / De-enable

[0245] In some embodiments, the network side may additionally use MAC CE signaling to select one or more indexes from the OCC index parameters or tables indicated by the RRC signaling. In some embodiments, when multiple indexes are selected, a specific field in the DCI (e.g., antenna port field, DMRS port field, MCS field, RV field, etc.) may be mapped to multiple indexes selected by MAC CE.

[0246] In some embodiments, the above table is predefined, and when the network side enables OCC function / table indication via higher-layer signaling (e.g., RRC, MAC CE), specific fields in DCI (e.g., antenna port field, DMRS port field, MCS field, RV field, etc.) can be mapped to the table.

[0247] In some embodiments, the OCC index parameter can indicate one or more OCC indices, and the user equipment determines which OCC sequence and OCC length to transmit by mapping specific fields in the DCI (e.g., antenna port field, DMRS port field, MCS field, RV field, etc.) to the OCC index parameter (e.g., configured by RRC or MAC CE). For example, the OCC index can indicate {0, 1, 2, 3}, that is, the index indicates 4 sequences, and these four indices are mapped sequentially to the antenna ports. Assuming there are 8 antenna ports, the mapping relationship is shown in Table 3 below. When the user equipment uses antenna port 5, the user equipment selects OCC index 1, the corresponding OCC sequence is [+1 -1], and the corresponding OCC length is 2.

[0248] Table 3

[0249] Antenna port OCC Index OCC sequence 0 0 [+1+1] 1 1 [+1-1] 2 2 [+1+1+1+1] 3 3 [+1 -1+1-1] 4 0 [+1+1] 5 1 [+1-1] 6 2 [+1+1+1+1] 7 3 [+1 -1+1-1]

[0250] For example, the OCC index can indicate {5, 4, 2, 3, 1}, that is, the index indicates 5 sequences, and these 5 indices are mapped to the antenna ports in sequence. Assuming there are 8 antenna ports, the mapping relationship is as shown in Table 4 below. When the user equipment uses antenna port 1, the user equipment selects OCC index 4, the corresponding OCC sequence is [+1+1 -1-1], and the corresponding OCC length is 4.

[0251] Table 4

[0252] Antenna port OCC Index OCC sequence 0 5 [+1-1-1+1] 1 4 [+1+1-1-1] 2 2 [+1+1+1+1] 3 3 [+1 -1+1-1] 4 1 [+1-1] 5 5 [+1-1-1+1] 6 4 [+1+1-1-1] 7 2 [+1+1+1+1]

[0253] For example, the OCC index can indicate {0, 1, 2, 3, 4, 5}, that is, the index indicates 6 sequences, and these 6 indices are mapped to the antenna ports in sequence. Assuming there are 8 antenna ports, the mapping relationship is as shown in Table 5 below. When the antenna port used by the user equipment is 1, the OCC index selected by the user equipment is 1, the corresponding OCC sequence is [+1 -1], and the corresponding OCC length is 2.

[0254] Table 5

[0255] Antenna port OCC Index OCC sequence 0 0 [+1+1] 1 1 [+1-1] 2 2 [+1+1+1+1] 3 3 [+1 -1+1-1] 4 4 [+1+1-1-1] 5 5 [+1-1-1+1] 6 0 [+1+1] 7 1 [+1-1]

[0256] Methods for handling IoT-NTN OCC transmission and interval overlap

[0257] The technical terms involved in the embodiments of this disclosure will be described below.

[0258] 1. OCC

[0259] The granularity of orthogonal covering code (OCC) application can be symbol level, time slot level, multiple time slot level (e.g., two time slots), repetition level, etc., and the application operation can be multiplication operation.

[0260] In the symbol-level OCC resource mapping scheme, when the mapping is performed, the data (e.g., complex modulation symbols) on multiple consecutive symbols used to apply the OCC are kept consistent across symbols during the mapping process.

[0261] When the resource mapping scheme corresponding to the slot-level OCC is executed, the data (e.g., complex modulation symbols) on multiple consecutive time slots used to apply the OCC remains consistent across time slots during the mapping process.

[0262] When the resource mapping scheme corresponding to multiple time slot levels (or time slot groups) of OCC is executed, the data (e.g., complex modulation symbols) on multiple consecutive time slot groups used to apply the OCC remains consistent across time slot groups during the mapping process.

[0263] In data transmission, there are various types of intervals (such as uplink transmission intervals, intervals caused by narrowband physical random access channel (NPRACH) transmission, uplink timing adjustment intervals, pre-compensation segmentation intervals, and 3.75kHz-specific transmission intervals). These intervals may cause OCC to be transmitted across intervals or the orthogonality / integrity of OCC may be compromised due to the dropping of certain time slots / symbols, thereby reducing the demodulation accuracy.

[0264] Furthermore, the demodulation reference signal (DMRS) in existing IoT systems only supports single-user transmission. Therefore, when multiple users' data (NPUSCH) are transmitted simultaneously on the same video resource, it becomes particularly important to support the transmission of DMRS for multiple users so that it can be accurately used for video bias estimation, compensation, and channel estimation.

[0265] For example, such as Figure 2 As shown, taking the OCC sequence [+1+1; +1 -1] as an example, UE1 selects the sequence [+1+1], and UE2 selects the sequence [+1 -1]. Each UE repeats this sequence twice, with the same content. UE1 and UE2 transmit X1 and X2 respectively on the same time and frequency domain resources. Therefore, the signals superimposed at the positions of the first and second repetitions can be represented as Y1 and Y2.

[0266] Where H represents channel state information, for example, H1,1 represents the first time-frequency resource of UE1, Y1 = X1H1,1 + X2H2,1, Y2 = X2H2,1 + X2H2,2. As shown in the figure below, X1 and X2 can be calculated as functions of Y1 and Y2 and their corresponding channel state information.

[0267] 2. Uplink transmission gap (UL gap) and gap caused by NPRACH transmission (Gaps around NPRACH)

[0268] In traditional Internet of Things (IoT), there are half-duplex (HD) gaps, such as uplink transmission gaps (UL transmission gaps). There are also gaps caused by NPRACH, for example, when NPUSCH and NPRACH resources overlap, a delay occurs, resulting in a gap in NPUSCH transmissions on both sides of the NPRACH resource. In the embodiments of this disclosure, the gap can also be referred to as an interval.

[0269] The uplink transmission interval is the interval formed by the NB-IoT terminal (user equipment, UE) stopping uplink transmission and receiving downlink signals in the next 40ms after a continuous 256ms uplink transmission.

[0270] The NPRACH interval is defined as the time when the UE must stop its ongoing continuous uplink transmission to transmit NPRACH. These times are known to the UE (notified via broadcast signaling SIB), and these uplink NPRACH transmission times may also be included within 256ms. In this case, whether it is NPUSCH transmission, NPRACH transmission, or both, the UE must stop transmitting uplink after 256ms to receive DL information.

[0271] Intervals are caused by the demodulation reference signal (DMRS) interval or by DMRS dropping / not transmitting / mute. For example, when using time-division DMRS, the DMRS may drop / not transmit / mute on some symbols, resulting in intervals.

[0272] Due to the duration of these intervals, the orthogonality of OCC codes will be broken when the applied OCC unit is before or after an interval (i.e., when there is cross-interval OCC application). Furthermore, for symbol-level OCC, this also occurs for symbols located at interval boundaries, which may also be DMRS symbols.

[0273] 3. Uplink timing advance (ULTA gaps) and segment transmission intervals

[0274] In traditional IoT, link budget is enhanced through repetition, including repetition of NPUSCH / NPRACH transmissions. In related technologies, when the number of repetitions is large, segmented transmission is defined in NTN, where the total repetition transmission is divided into multiple segments. Time / frequency adjustment can be performed on a segment-by-segment basis to handle synchronization drift caused by satellite motion. Between segments, partial data transmission needs to be discarded to form intervals, which can be used for TA adjustment. Data transmissions discarded on resources may correspond to partial data within a certain OCC cell, leading to a disruption of OCC orthogonality.

[0275] The mapping process of physical resources describes the transmission of data portions and the formation process of transmission intervals during data transmission.

[0276] The transmission interval depends on the UE's capability ntn-SegmentedPrecompensationGaps-r17, which supports a transmission interval of 1 symbol, 1 time slot, or 2 time slots. Different UEs may support different transmission intervals.

[0277] For UEs communicating via NTN, there is a delay in transmission (and / or due to NPRACH). After the time unit, for frame structure type 1, according to the specified UE capability NTN-Segmented precompensation Gaps-r17, the following should be performed: The transmission interval of a time unit is included in the NPUSCH resource mapping, but is not used for NPUSCH transmission. The quantity is provided by higher-ups. The value is configured by a higher layer based on the UE's capabilities (if there is a signal).

[0278] For NB-IoT UEs communicating via NTN, time and frequency pre-compensation adjustments are performed for each uplink segment, with a transmission duration of [duration value missing]. Time unit, of which Provided by a higher level.

[0279] NTN segmentation pre-compensation gap indicates the minimum interval length supported between segments in the segmented uplink transmission. The value sym1 corresponds to 1 symbol, the value sl1 corresponds to 1 time slot, and the value sf1 corresponds to 1 subframe.

[0280] The IE UE capability NB is used to convey NB-IoT UE radio access capability parameters; see related technologies. The IE UE capability NB is transmitted only in NB-IoT.

[0281] In NTN scenarios, the configuration of the interval used for TA pre-compensation in NB-IoT indicates the minimum interval length supported between segmented uplink transmission segments. The value sym1 corresponds to 1 symbol, the value sl1 corresponds to 1 time slot, and the value sl2 corresponds to 2 time slots.

[0282] When transmitting data, the first node can process the data using a cover code. Different first nodes use different cover code sequences. Thus, different first nodes obtain different signals based on the cover code. In this case, multiple first nodes can transmit signals on the same time-frequency resources, while the second node can decode the signals transmitted by different first nodes based on the cover code, thereby improving resource utilization and increasing the uplink transmission system capacity. The following description will use an orthogonal cover code (OCC) as an example. The cover code in this embodiment can be any code or cover code, including orthogonal and non-orthogonal codes. For example, codes composed of any orthogonal code sequences include, but are not limited to, Walsh codes, Discrete Fourier Transform (DFT) codes, etc. Codes composed of non-orthogonal code sequences include, but are not limited to, Non-Orthogonal Multiple Access (NOMA) codes or access codes.

[0283] However, for the above signals to be correctly decoded, the orthogonality and integrity of the OCC used by the first node when transmitting the signal must not be compromised; otherwise, the second node will not be able to correctly decode the signal transmitted by the first node. It should be noted that transmission systems may have various intervals during data transmission, and the data used in OCC applications may also have intervals during transmission, thus compromising the orthogonality and integrity of the OCC. To address this issue, the following will describe different types of intervals.

[0284] Case 1: The transmission interval is a Type I transmission interval.

[0285] The first type of transmission interval includes at least one of the following: uplink transmission interval / half-duplex communication interval, interval caused by narrowband physical random access channel (NPRACH), DMRS interval or interval caused by DMRS drop / non-transmission / mute, uplink timing adjustment interval, and segmented transmission interval. Alternatively, the first type of transmission interval is the union of at least one of the above intervals. For example, if the uplink transmission interval overlaps with the interval caused by NPRACH, then the first type of transmission interval is the time resource occupied by the uplink transmission interval and the interval caused by NPRACH.

[0286] When OCC is applied across this interval, the duration of the interval may alter the phase continuity, thereby disrupting the orthogonality of the OCC. Consider at least one of the following enhancement methods:

[0287] Method 1-1: When multiple application units used in an OOC transmission overlap or partially overlap with the first type of transmission interval in the time domain, the signal transmission on multiple application units is abandoned / discarded / not transmitted / set to zero.

[0288] Methods 1-2, where multiple application units applied in a single OCC transmission overlap or partially overlap with the first type of transmission interval in the time domain, delay the signal transmission in multiple application units. For example, delay the transmission corresponding to each element of the OCC code to after the interval, or delay the transmission corresponding to each element of the OCC code to the time resources of the next OCC code application. The delay may be measured in units of the duration / time resources of a single OCC transmission. For example,

[0289] The delay duration is an integer multiple of the duration of one OCC transmission / time resource, and is greater than the first type of transmission interval.

[0290] Alternatively, the slot / subframe / symbol corresponding to the first application unit of the OCC satisfies n mod D = 0, where n is the slot number / subframe number / symbol number corresponding to the first application unit, and D corresponds to the duration / time resources (e.g., number of symbols, number of subframes, number of slots) of one OCC transmission. D may be equal to Nocc * Nunit of slots / subframes / symbols, where Nocc is the length of the OCC, and Nunit is the length / duration / time resources (e.g., number of symbols, number of subframes, number of slots) of one application unit.

[0291] Alternatively, after the delay, the slot / subframe / symbol corresponding to the first application unit of the OCC satisfies n mod D = 0, where n is the slot number / subframe number / symbol number corresponding to the first application unit, and D corresponds to the duration / time resources (e.g., number of symbols, number of slots) of one OCC transmission. D may be equal to Nocc * Nunit of slots / subframes / symbols, where Nocc is the length of the OCC, and Nunit is the length / duration / time resources (e.g., number of symbols, number of subframes, number of slots) of one application unit.

[0292] Alternatively, after the delay, the slot / subframe / symbol corresponding to the first application unit of the OCC satisfies n mod D = K, where n is the slot number / subframe number / symbol number corresponding to the first application unit, and D corresponds to the duration / time resources (e.g., number of symbols, number of slots) of one OCC transmission. D may be equal to Nocc * Nunit of slots / subframes / symbols, where Nocc is the length of the OCC, and Nunit is the length / duration / time resources (e.g., number of symbols, number of subframes, number of slots) of one application unit. K may be a value configured on the network side or predefined by the protocol. Alternatively, K = ns mod D, where ns is the slot number / subframe number / symbol number corresponding to the start time of the NPUSCH transmission.

[0293] Case 2: The transmission interval is a Type II transmission interval.

[0294] The second type of transmission interval includes at least one of the following: DMRS interval or interval caused by DMRS dropping / not transmitting / mute, uplink timing adjustment interval, and segmented transmission interval.

[0295] For example, taking the second type of transmission interval as the segmented transmission interval, when segmented transmission is enabled, considering the duration of the interval between segmented transmissions, the network side ensures that the application of OCC should not cross intervals when configuring, that is, there are no elements belonging to the same OCC that are separated by intervals when applied.

[0296] Additionally, when segmented transmission is enabled, some data transmission needs to be discarded during the intervals between segments. The discarded transmission unit can be one symbol, one time slot, or multiple time slots, depending on the UE's capabilities. If the unit used by OCC (which carries data) is discarded, the integrity of OCC is compromised.

[0297] Method 2-1: When multiple application units used in an OOC transmission overlap or partially overlap with the second type of transmission interval in the time domain, signal transmission on multiple application units is abandoned or delayed. The specific method is the same as that for the first type of transmission interval.

[0298] Method 2-2: Restrict the configuration of the Type II transmission interval. For example, the Type II transmission interval needs to be configured as an integer multiple of the duration of one OCC transmission or 0.

[0299] Public PDCCH retransmission

[0300] A public PDCCH includes at least one of the PDCCH public search space CSS and / or at least one of the PDCCHs that use cell-level PDCCH parameters (PDCCH-ConfigCommon); a public PDCCH may include at least one of the following:

[0301] Type0-PDCCH CSS

[0302] Type0A-PDCCH CSS

[0303] Type0B-PDCCH CSS

[0304] Type 1-PDCCH CSS

[0305] Type1A-PDCCH CSS

[0306] Type2-PDCCH CSS

[0307] Type2A-PDCCH CSS

[0308] Type3-PDCCH CSS

[0309] SS0 (searchSpaceZero)

[0310] Type0-PDCCH CSS on SS0

[0311] Type0A-PDCCH CSS on SS0

[0312] Type0B-PDCCH CSS on SS0

[0313] Type 1-PDCCH CSS on SS0

[0314] Type 1A-PDCCH CSS on SS0

[0315] Type 2-PDCCH CSS on SS0

[0316] Type2A-PDCCH CSS on SS0

[0317] Type 3-PDCCH CSS on SS0

[0318] The PDCCH corresponding to the SS configured in searchSpaceSIB1

[0319] The PDCCH corresponding to the SS configured in searchSpaceOtherSystemInformation

[0320] The PDCCH corresponding to the SS configured in pagingSearchSpace

[0321] The PDCCH corresponding to SS configured in ra-SearchSpace

[0322] The searchSpaceMCCH configuration corresponds to the PDCCH of the SS.

[0323] The searchSpaceMTCH configuration corresponds to the PDCCH of the SS.

[0324] The searchSpaceMulticastMCCH configuration corresponds to the PDCCH of the SS.

[0325] The searchSpaceMulticastMTCH configuration corresponds to the PDCCH of the SS.

[0326] peiSearchSpace's configured SS corresponding to PDCCH

[0327] The PDCCH corresponding to SS configured in sdt-SearchSpace

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

[0329] The current protocol already supports repeated PDCCH transmission within a time slot. More specifically, if a network node configures two search spaces (SSs) for a user and sets the same searchSpaceLinkingId in both SSs, then the two SSs can be 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 SIB (System Information Block) scheduling, initial access scheduling, paging scheduling, or SDT (Small Data Transmission) scheduling. Current PDCCH repetition only supports repetitive transmission within a time slot, hence it is also called intra-time slot repetitive transmission. This scheme can be called intra-time slot repetitive transmission.

[0330] 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 (Security Stream), and within the time slot determined by the SS, there are multiple time-domain resources that can be used for PDCCH transmission. These time-domain resources may be control resource sets (CORESET), SS timing, consecutive symbols, etc. These time-domain resources may be consecutive. Alternatively, they may be discontinuous, for example, adjacent time-domain resources may have a time interval X. X may be configured by the network side or predefined by the protocol. The 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 for PDCCH repetitive transmission.

[0331] In addition to intra-slot PDCCH repetition, inter-slot PDCCH repetition can also be considered. For example, in the intra-slot repetition scheme, the associated SSs are not in the same slot, but have an interval / offset of more than one slot, or an interval / offset based on a slot. This scheme can be called inter-slot repetition.

[0332] Besides the aforementioned inter-slot repetitive transmission, other inter-slot repetitive transmission methods may exist. For example, inter-slot repetitive transmission: the network side configures an SS (Secondary Switching Module), and starting from the detection time corresponding to the SS, PDCCH repetitive transmission is performed in multiple consecutive or discontinuous time slots. In these discontinuous time slots, adjacent time slots may have a time interval X. X may be configured by the network side or predefined by the protocol. The 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 the multiple time slots where PDCCH repetitive transmission is performed.

[0333] In summary, the PDCCH retransmission method may include at least one of the following: retransmission within a first time slot, retransmission within a second time slot, retransmission between first time slots, and retransmission between second time slots.

[0334] Different PDCCH retransmission methods may be used for different types of public PDCCHs. For example, a first retransmission method may be used for type I public PDCCHs, and a second retransmission method may be used for type II public PDCCHs. Type I or Type II public PDCCHs may be at least one of the aforementioned public PDCCH types. The first or second retransmission method may be at least one of the aforementioned PDCCH retransmission methods. Different signaling or parameter configurations may be used for the first and second retransmission methods. For example, the first signaling may indicate the enabling of the first retransmission method, the number of retransmissions, or the SS association (such as association ID), and the second signaling may indicate the enabling of the second retransmission method, the number of retransmissions, or the SS association (such as association ID).

[0335] Specifically, for example:

[0336] Example 1: For public PDCCH on SS0, the first retransmission method is used; for public PDCCH on SSs other than SS0, the second retransmission method is used. The first retransmission method is either inter-slot retransmission or inter-slot retransmission, and the second retransmission method is either intra-slot retransmission or intra-slot retransmission. The enabling of the first retransmission method, the number of retransmissions, or the SS association (such as association ID) may be indicated by MIB, PBCH, or SIB1, or predefined by the protocol; the enabling of the second retransmission method, the number of retransmissions, or the SS association (such as association ID) may be indicated by SIB1, SIBx (x>1), or dedicated RRC signaling, or predefined by the protocol.

[0337] Example 2: For Type 0 PDCCH CSS on SS0, the first retransmission method is used; for Type 0 PDCCH CSS on SSs other than SS0, the second retransmission method is used. The first retransmission method is either inter-slot retransmission or inter-slot retransmission, and the second retransmission method is either intra-slot retransmission or intra-slot retransmission. The enabling of the first retransmission method, the number of retransmissions, or the SS association (such as association ID) may be indicated by MIB, PBCH, or SIB1 or predefined by the protocol; the enabling of the second retransmission method, the number of retransmissions, or the SS association (such as association ID) may be indicated by SIB1 or SIBx (x>1) or dedicated RRC signaling or predefined by the protocol.

[0338] Example 3: For Type 0A PDCCH CSS on SS0, use the first retransmission method; for Type 0A PDCCH CSS on SSs other than SS0, use the second retransmission method. The first retransmission method is either inter-slot retransmission or inter-slot retransmission, and the second retransmission method is either intra-slot retransmission or intra-slot retransmission. The enabling of the first retransmission method, the number of retransmissions, or the SS association (such as association ID) may be indicated by MIB, PBCH, or SIB1 or predefined by the protocol; the enabling of the second retransmission method, the number of retransmissions, or the SS association (such as association ID) may be indicated by SIB1 or SIBx (x>1) or dedicated RRC signaling or predefined by the protocol.

[0339] Example 4: For Type 0B PDCCH CSS on SS0, use the first retransmission method; for Type 0B PDCCH CSS on SSs other than SS0, use the second retransmission method. The first retransmission method is either inter-slot retransmission or inter-slot retransmission, and the second retransmission method is either intra-slot retransmission or intra-slot retransmission. The enabling of the first retransmission method, the number of retransmissions, or the SS association (such as association ID) may be indicated by MIB, PBCH, or SIB1, or predefined by the protocol; the enabling of the second retransmission method, the number of retransmissions, or the SS association (such as association ID) may be indicated by SIB1 or SIBx (x>1) or dedicated RRC signaling, or predefined by the protocol.

[0340] Example 5: For Type 1 PDCCH CSS on SS0, use the first retransmission method; for Type 1 PDCCH CSS on SSs other than SS0, use the second retransmission method. The first retransmission method is either inter-slot retransmission or inter-slot retransmission, and the second retransmission method is either intra-slot retransmission or intra-slot retransmission. The enabling of the first retransmission method, the number of retransmissions, or the SS association (such as association ID) may be indicated by MIB, PBCH, or SIB1, or predefined by the protocol; the enabling of the second retransmission method, the number of retransmissions, or the SS association (such as association ID) may be indicated by SIB1, SIBx (x>1), or dedicated RRC signaling, or predefined by the protocol.

[0341] Example 6: For Type 1A PDCCH CSS on SS0, use the first retransmission method; for Type 1A PDCCH CSS on SSs other than SS0, use the second retransmission method. The first retransmission method is either inter-slot retransmission or inter-slot retransmission, and the second retransmission method is either intra-slot retransmission or intra-slot retransmission. The enabling of the first retransmission method, the number of retransmissions, or the SS association (such as association ID) may be indicated by MIB, PBCH, or SIB1, or predefined by the protocol; the enabling of the second retransmission method, the number of retransmissions, or the SS association (such as association ID) may be indicated by SIB1 or SIBx (x>1) or dedicated RRC signaling, or predefined by the protocol.

[0342] Example 7: For Type 2 PDCCH CSS on SS0, use the first retransmission method; for Type 2 PDCCH CSS on SSs other than SS0, use the second retransmission method. The first retransmission method is either inter-slot retransmission or inter-slot retransmission, and the second retransmission method is either intra-slot retransmission or intra-slot retransmission. The enabling of the first retransmission method, the number of retransmissions, or the SS association (such as association ID) may be indicated by MIB, PBCH, or SIB1 or predefined by the protocol; the enabling of the second retransmission method, the number of retransmissions, or the SS association (such as association ID) may be indicated by SIB1 or SIBx (x>1) or dedicated RRC signaling or predefined by the protocol.

[0343] Example 8: For Type 2A PDCCH CSS on SS0, use the first retransmission method; for Type 2A PDCCH CSS on SSs other than SS0, use the second retransmission method. The first retransmission method is either inter-slot retransmission or inter-slot retransmission, and the second retransmission method is either intra-slot retransmission or intra-slot retransmission. The enabling of the first retransmission method, the number of retransmissions, or the SS association (such as association ID) may be indicated by MIB, PBCH, or SIB1, or predefined by the protocol; the enabling of the second retransmission method, the number of retransmissions, or the SS association (such as association ID) may be indicated by SIB1 or SIBx (x>1) or dedicated RRC signaling, or predefined by the protocol.

[0344] Example 9: For Type 3 PDCCH CSS on SS0, use the first retransmission method; for Type 3 PDCCH CSS on SSs other than SS0, use the second retransmission method. The first retransmission method is either inter-slot retransmission or inter-slot retransmission, and the second retransmission method is either intra-slot retransmission or intra-slot retransmission. The enabling of the first retransmission method, the number of retransmissions, or the SS association (such as association ID) may be indicated by MIB, PBCH, or SIB1, or predefined by the protocol; the enabling of the second retransmission method, the number of retransmissions, or the SS association (such as association ID) may be indicated by SIB1 or SIBx (x>1) or dedicated RRC signaling, or predefined by the protocol.

[0345] Example 10: For Type 0 PDCCH CSS on SS0, use the first retransmission method; for Type 0 PDCCH CSS on SSs other than SS0, do not perform PDCCH retransmission. The first retransmission method is either a first time slot retransmission or a second time slot retransmission. The enabling of the first retransmission method, the number of retransmissions, or SS associations (such as association IDs) may be indicated by MIB, PBCH, or SIB1, or predefined by the protocol.

[0346] Example 11: For Type 0A PDCCH CSS on SS0, no PDCCH retransmission is performed; for Type 0A PDCCH CSS on SSs other than SS0, a second retransmission method is used. The second retransmission method is either retransmission within the first time slot or retransmission within the second time slot. The enabling of the second retransmission method, the number of retransmissions, or the SS association (such as association ID) may be indicated by SIB1 or SIBx (x>1) or dedicated RRC signaling or predefined by the protocol.

[0347] Example 12: For Type 0B PDCCH CSS on SS0, no PDCCH retransmission is performed; for Type 0B PDCCH CSS on SSs other than SS0, a second retransmission method is used. The second retransmission method is either retransmission within the first time slot or retransmission within the second time slot. The enabling of the second retransmission method, the number of retransmissions, or SS association (such as association ID) may be indicated by SIB1 or SIBx (x>1) or dedicated RRC signaling or predefined by the protocol.

[0348] Example 13: For Type 1 PDCCH CSS on SS0, no PDCCH retransmission is performed; for Type 1 PDCCH CSS on SSs other than SS0, a second retransmission method is used. The second retransmission method is either retransmission within the first time slot or retransmission within the second time slot. The enabling of the second retransmission method, the number of retransmissions, or SS association (such as association ID) may be indicated by SIB1 or SIBx (x>1) or dedicated RRC signaling or predefined by the protocol.

[0349] Example 14: For Type 1A PDCCH CSS on SS0, no PDCCH retransmission is performed; for Type 1A PDCCH CSS on SSs other than SS0, a second retransmission method is used. The second retransmission method is either retransmission within the first time slot or retransmission within the second time slot. The enabling of the second retransmission method, the number of retransmissions, or the SS association (such as association ID) may be indicated by SIB1 or SIBx (x>1) or dedicated RRC signaling or predefined by the protocol.

[0350] Example 15: For Type 2 PDCCH CSS on SS0, no PDCCH retransmission is performed; for Type 2 PDCCH CSS on SSs other than SS0, a second retransmission method is used. The second retransmission method is either retransmission within the first time slot or retransmission within the second time slot. The enabling of the second retransmission method, the number of retransmissions, or SS association (such as association ID) may be indicated by SIB1 or SIBx (x>1) or dedicated RRC signaling or predefined by the protocol.

[0351] Example 16: For Type 2A PDCCH CSS on SS0, no PDCCH retransmission is performed; for Type 2A PDCCH CSS on SSs other than SS0, a second retransmission method is used. The second retransmission method is either retransmission within the first time slot or retransmission within the second time slot. The enabling of the second retransmission method, the number of retransmissions, or the SS association (such as association ID) may be indicated by SIB1 or SIBx (x>1) or dedicated RRC signaling or predefined by the protocol.

[0352] Example 17: For Type 3 PDCCH CSS on SS0, no PDCCH retransmission is performed; for Type 3 PDCCH CSS on SSs other than SS0, a second retransmission method is used. The second retransmission method is either retransmission within the first time slot or retransmission within the second time slot. The enabling of the second retransmission method, the number of retransmissions, or the SS association (such as association ID) may be indicated by SIB1 or SIBx (x>1) or dedicated RRC signaling or predefined by the protocol.

[0353] 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), Radio Resource Control (RRC) signaling, Media Access Control Unit (MAC CE), MAC header, MAC subheader, and Downlink Control Information (DCI) signaling.

[0354] In other words, the first or second signaling (which may notify configuration, signaling, or instruction implementation) may include at least one of the following: MIB, PBCH, SIB1, SIBx (x>=1), RRC signaling, MAC CE, MAC header, MAC subheader, DCI signaling, etc. Specific instruction methods may include:

[0355] Define a new / dedicated bit field to indicate,

[0356] Multiplexing / reinterpreting existing bit fields to indicate

[0357] Multiplexing / reinterpreting one or more states / code points of an existing bit field to indicate,

[0358] Introduce new information elements (IEs) to indicate (e.g., enumerate multiple candidate values, indicate one from multiple candidate values, or indicate a specific value).

[0359] Introduce a new MAC CE and use MAC CE for indication.

[0360] A new MAC subheader is introduced, indicated by LCID code points.

[0361] Use relevant information about the scrambling code to indicate (such as RNTI, code sequence, root of the generator code, seed of the generator code, etc.).

[0362] When indicating via DCI, such as introducing a new / dedicated bit field or reusing an existing bit field, corresponding enable / activation signaling may be introduced, for example via MIB / PBCH / SIB / RRC / MAC CE.

[0363] Alternatively, when the network side configures multiple parameters via higher-layer signaling (e.g., SIB1, SIBx, RRC), DCI may be used to further indicate one of the parameters. The DCI will only include new / dedicated bit fields, or reuse / reinterpret existing bit fields, when multiple parameters are enabled / activated / configured by the network side. When indicated via MAC CE or MAC header / subheader, for example, by introducing new / dedicated bit fields or reusing existing bit fields, corresponding enable / activation signaling may be introduced, such as via MIB / PBCH / SIB / RRC.

[0364] Alternatively, when the network side configures multiple parameters via higher-layer signaling (e.g., SIB1, SIBx, RRC), it may use MACCE or MAC header / subheader to further indicate one of the parameters. New / dedicated bit fields will only be included in the MAC CE or MAC header / subheader when multiple parameters are enabled / activated / configured by the network side, or when existing bit fields are reused / reinterpreted.

[0365] 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 multiplexing / reinterpreting idle / reserved bits in existing 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.

[0366] IoT-NTN OCC Transmission, RV Determination, and Resource Mapping Processing Methods

[0367] The technical terms involved in the embodiments of this disclosure will be described below.

[0368] 1. OCC

[0369] The granularity of orthogonal covering code (OCC) application can be symbol level, time slot level, multiple time slot level (e.g., two time slots), repetition level, etc., and the application operation can be multiplication operation.

[0370] In the symbol-level OCC resource mapping scheme, when the mapping is performed, the data (e.g., complex modulation symbols) on multiple consecutive symbols used to apply the OCC are kept consistent across symbols during the mapping process.

[0371] When the resource mapping scheme corresponding to the slot-level OCC is executed, the data (e.g., complex modulation symbols) used to apply the OCC on multiple consecutive slots remains consistent across the slots during the mapping process.

[0372] When the resource mapping scheme corresponding to multiple time slot levels (or time slot groups) of OCC is executed, the data (e.g., complex modulation symbols) on multiple consecutive time slot groups used to apply the OCC remains consistent across time slot groups during the mapping process.

[0373] In the current specification, resource units are used to describe the mapping from PUSCH to resource elements. Resource units are defined in the time domain. Symbolic and frequency domain Continuous subcarriers, where and The following are given by frame structure type 1 in Table 6.

[0374] Table 6

[0375]

[0376] Physical resource mapping:

[0377] Each NPUSCH codeword can be mapped to one or more resource units N. RU Each resource unit should be transmitted Number of times. The complex value sign should be multiplied by the amplitude scaling factor β. NPUSCH And starting from the subcarrier z(0) allocated for PUSCH transmission, it is mapped sequentially to the resource element (k,l) corresponding to the subcarrier allocated for transmission but not for transmitting the reference signal, starting from the first slot in the allocated resource element, in ascending order of index k followed by index l. 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, of which:

[0378]

[0379] For multi-tone transmission, such as Figure 6 As shown. Figure 6 This is a schematic diagram of the physical resource mapping of NPUSCH codewords (configured for 8 repetitions) for multi-tone transmission provided in this embodiment of the disclosure.

[0380] For monotone transmission, such as Figure 7 As shown. Figure 7 This is a schematic diagram of the physical resource mapping of NPUSCH codewords (configured for 2 repetitions) for single-tone transmission provided in the embodiments of this disclosure.

[0381] For PUSCH transmission, the NPUSCH (Narrowband Physical Uplink Shared Channel) transmission associated with a TB (Transmission Block) and the determination of RV are as follows: transmission occurs in N time slots in the NB-IoT uplink, denoted by ni, where i = 0, 1, ..., N-1. For the NPUSCH transmission corresponding to the j-th TB, it is transmitted in B consecutive NB-IoT uplink time slots, ni, i = jB + b, b = 0, 1, K, B-1, j = 0, 1, K. :in The redundant version (rv) associated with this TB idx (j) is determined as follows: rv idx (j)=2·mod(rv DCI +j,2), where if Then L = 1, otherwise In the NPUSCH codeword, 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 is performed on each slot. When the subcarrier spacing is Δf = 3.75kHz, the slot mapping method in the NB-IoT UL slots associated with TB is ni. When l = 0, 1, K, L-1; and the subcarrier spacing is Δf = 15 kHz, the slot mapping method in the NB-IoT UL slots associated with TB is ni. The determination of RV in the current protocol is as follows:

[0382]

[0383] When applying OCC, the above-mentioned RV-related determination method should be enhanced as follows:

[0384] For a 3.75kHz single-carrier configuration: Modify L = OCC length, where the OCC length is indicated / configured by the network side:

[0385] Transmission occurs in N time slots of the NB-IoT uplink, denoted by ni, where i = 0, 1, ..., N-1. For the NPUSCH transmission corresponding to the j-th TB, it is transmitted in B consecutive NB-IoT uplink time slots, ni, i = jB + b, b = 0, 1, K, B-1, j = 0, 1, K. :in The redundant version (rv) associated with this TB idx(j) is determined as follows: rv idx (j)=2·mod(rv DCI +j,2), where if Then L = OCC length. In the NPUSCH codeword, 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 is performed on each slot. When the subcarrier spacing is Δf = 3.75kHz, the slot mapping method in the NB-IoT UL slots associated with TB is ni. l = 0, 1, K, L-1; Example

[0386]

[0387]

[0388] For a 15kHz single-carrier configuration: modify L = OCC length or L = min(4, OCC length) or L = min(4, N_rep / 2, OCC length); modify the slot mapping method to ni l = 0, 1, K, L-1, that is:

[0389] Transmission occurs in N time slots of the NB-IoT uplink, denoted by ni, where i = 0, 1, ..., N-1. For the NPUSCH transmission corresponding to the j-th TB, it is transmitted in B consecutive NB-IoT uplink time slots, ni, i = jB + b, b = 0, 1, K, B-1, j = 0, 1, K. :in The redundant version (rv) associated with this TB idx (j) is determined as follows: rv idx (j)=2·mod(rv DCI +j,2), where if N s R c If U = 1, then L = OCC length. In the NPUSCH codeword, 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 is performed on each slot. When the subcarrier spacing is Δf = 3.75kHz, the slot mapping method in the NB-IoT UL slots associated with TB is ni. l = 0, 1, K, L-1; Example:

[0390]

[0391] For a 15kHz multicarrier configuration, the current structure can be reused or the L=OCC length or L=min(4,OCC length) or L=min(4,N_rep / 2,OCC length) can be modified; for example, 8 repetitions, each repetition or transmission occupies 2 resource units, and the codeword mapping method is used when applying slot-level OCC.

[0392] For physical resource mapping, the physical resource mapping of the time slot-level OCC-level scheme is enhanced as follows:

[0393] For a 3.75kHz single-carrier configuration, the physical resource mapping rule for PUSCH codewords is as follows: After mapping to M symbols, the mapping should be repeated for M symbols before continuing to map z(·) to the next symbol. Next, of which: length, Length or (4, OCC length) or (4, N_rep / 2, OCC length) M = 1;

[0394] For a 15kHz single-carrier configuration, the physical resource mapping rule for PUSCH codewords is as follows: After mapping to N time slots, the mapping should be repeated for N time slots before continuing to map z(·) to the next time slot. Next, of which: length, Length or (4, OCC length) or (4, N_rep / 2, OCC length) N = 1;

[0395] For a 15kHz multicarrier configuration, the physical resource mapping rules for PUSCH codewords are as follows: After mapping to O time slots, the mapping should be repeated for O time slots before continuing to map z(·) to the next time slot. Next, of which: length, Length or (4, OCC length) or (4, N_rep / 2, OCC length) or (4, N_rep / 2), O = 2.

[0396] Additionally, the network side can configure or indicate OCC-related information for the UE. This includes OCC function enable / disable, OCC sequence, OCC sequence index, OCC activation / deactivation, and whether the OCC sequence is applied. If the network side enables OCC but does not activate it, the UE may not use or apply the OCC sequence.

[0397] The configuration or indication of the above-mentioned OCC-related information may be through at least one of the following: Master Information Block (MIB), System Information Block (SIB), Physical Broadcast Channel (PBCH), Radio Resource Control (RRC) signaling, Media Access Control Unit (MAC CE), MAC header, MAC subheader, and Downlink Control Information (DCI) signaling.

[0398] If indicated via MAC CE, at least one of the following methods may be considered:

[0399] Method 1: Define a new / corresponding MAC CE or MAC header / subheader. The MAC header / subheader may be used to indicate information, for example, through the LCID field, reserved bits, or reserved fields. Specifically, it may be indicated by at least one code point or status of the LCID. For example, the first code point indicates OCC activation, and the second code point indicates OCC deactivation. The MAC CE or MAC PDU may be 0 bits. It is worth noting that multiple code points may be used to jointly indicate multiple functions.

[0400] Method 2: Define a new / corresponding MAC CE. Indicate this through bit fields in the MAC CE or MAC PDU. For example, if the MAC CE is 8 bits long, use at least one bit to indicate whether the OCC is active. For instance, a bit '0' indicates deactivation, and '1' indicates activation; or vice versa.

[0401] Method 3: Reuse at least one bit or code point / status from an existing or other MAC CE, MAC PDU, MAC header, or MAC RAR to indicate whether OCC is active. This bit or code point / status may be a reserved bit / code point / status. For example, reuse / reinterpret 1 bit (e.g., the highest bit) from a TA command MAC CE to indicate whether OCC is active. Alternatively, reuse a reserved bit from a Differential Koffset MAC Control Element. Specific methods for indicating using bits or code points / status are as described above. Reusing other MAC CEs or MAC PDUs can also be considered. Examples include GNSS MeasurementCommand MAC CE, UL Transmission Extension Update MAC CE, Differential Koffset MAC Control Element, etc.

[0402] When the UE receives a MAC CE or MAC header / subheader indicating OCC activation, the OCC sequence is applied in subsequent PUSCH transmissions. This application of the OCC sequence may occur after the MAC CE or MAC header / subheader takes effect. Conversely, when the UE receives a MAC CE or MAC header / subheader indicating OCC deactivation, the OCC sequence is not applied in subsequent PUSCH transmissions. This non-application of the OCC sequence may also occur after the MAC CE or MAC header / subheader takes effect. The aforementioned MAC CE or MAC header / subheader may only be applied / taken effect after the OCC function is enabled.

[0403] When OCC is activated, DCI may be used to indicate the OCC index, or the bit fields of DCI may be reinterpreted. When OCC is deactivated, DCI may not be used to indicate the OCC index, or the information indicated by DCI may be the same as that of traditional DCI or DCI when OCC is not used.

[0404] The aforementioned DCI fields can be existing fields, such as the remaining bit field, subcarrier indication field, resource allocation field, modulation and coding scheme field, repeating digital segment, DCI subframe repeating digital segment, or redundant version field, new data indication field, HARQ process digital segment, unicast scheduling TB digital segment, resource reservation field, or newly defined fields.

[0405] Additionally, refer to Figure 8An embodiment of this disclosure also discloses a communication node 800, which includes at least one processor 810; at least one memory 820 for storing at least one program; and when the at least one program is executed by the at least one processor 810, it implements the communication method as in any of the preceding embodiments.

[0406] In addition, one embodiment of this application discloses a computer-readable storage medium storing computer-executable instructions for performing the communication methods as described in any of the preceding embodiments.

[0407] Furthermore, one embodiment of this application also discloses a computer program product, including a computer program or computer instructions, which are stored in a computer-readable storage medium. The processor of the communication node reads the computer program or computer instructions from the computer-readable storage medium and executes the computer program or computer instructions, causing the communication node to perform the communication method as described in any of the preceding embodiments.

[0408] It will be understood by those skilled in the art that all or some of the steps and systems in the methods disclosed above can be implemented as software, firmware, hardware, and suitable combinations thereof. Some or all of the physical components can be implemented as software executed by a processor, such as a central processing unit, digital signal processor, or microprocessor, or as hardware, or as an integrated circuit, such as an application-specific integrated circuit. Such software can be distributed on a computer-readable medium, which can include computer storage media (or non-transitory media) and communication media (or transient media). As is known to those skilled in the art, the term computer storage media includes volatile and non-volatile, removable and non-removable media implemented in any method or technology for storing information (such as computer-readable instructions, data structures, program modules, or other data). Computer storage media includes, but is not limited to, RAM, ROM, EEPROM, flash memory or other memory technologies, CD-ROM, digital versatile disc (DVD) or other optical disc storage, magnetic cartridges, magnetic tape, disk storage or other magnetic storage devices, or any other medium that can be used to store desired information and is accessible to a computer. Furthermore, as is known to those skilled in the art, communication media typically contain computer-readable instructions, data structures, program modules, or other data in modulated data signals such as carrier waves or other transmission mechanisms, and may include any information delivery medium.

[0409] The above is a detailed description of the preferred embodiments of this application. However, this application is not limited to the above embodiments. Those skilled in the art can make various equivalent modifications or substitutions without departing from the spirit of this application. All such equivalent modifications or substitutions are included within the scope defined by the claims of this application.

Claims

1. A communication method applied to a first communication node, the method comprising: Determine the transmission parameters of the first message; The first message is sent to the second communication node according to the transmission parameters of the first message; The transmission parameters of the first message include at least a repetition factor.

2. The method according to claim 1, characterized in that, The first message includes a Physical Uplink Shared Channel (PUSCH) message; The PUSCH message includes at least one of the following: Radio Resource Control (RRC) establishment completion response message, RRC recovery completion response message, Msg3 message, PUSCH message retransmitted during Small Data Transmission (SDT) process, PUSCH message during SDT process, and PUSCH message when dedicated resources are not configured.

3. The method according to claim 1, characterized in that, The repetition factor of the first message is determined by the transmission parameters of the second message; The transmission parameters of the second message include at least one of the following: Repetition factor, transport block scaling (TB), modulation and coding scheme (MCS), time-domain resource allocation, frequency-domain resource allocation, period, power; The second message includes at least one of the following: Control messages for scheduling random access response messages, random access response messages, control messages for scheduling contention resolution messages, contention resolution messages, control messages for scheduling RRC establishment completion response messages, control messages for scheduling RRC recovery completion response messages, random access preamble messages, Msg3 messages, physical uplink control channel (PUCCH) messages used to carry HARQ-ACK feedback for contention resolution messages, common physical downlink shared channel (PDSCH) messages, PUSCH messages for the initial transmission during SDT, msgA PUSCH messages during two-step random access processes, and common PUCCH messages.

4. The method according to claim 3, characterized in that, The repetition factor of the first message is determined by the repetition factor of the second message.

5. The method according to claim 4, Its characteristics are: The repetition factor of the first message is determined by the second communication node through a first downlink control information (DCI) signaling, wherein the repetition factor of the first message indicated by the first DCI signaling is one of a plurality of repetition factors of the second message; or, The repetition factor of the first message is determined by the second communication node via a second DCI signaling instruction; or, The repetition factor of the first message is equal to the repetition factor of the second message, and the repetition factor of the second message is determined by the second communication node through a second DCI signaling instruction; or, The repetition factor of the first message is the repetition factor that the first communication node selects and reports from among multiple repetition factors of the second message. or, The repetition factor of the first message is the repetition factor that the first communication node selects and reports from among multiple repetition factors of the second message and applies to the first message. The first DCI signaling includes one of the following: The newly added fields in the DCI signaling of the first message are scheduled, and the existing target fields in the DCI signaling of the first message are scheduled. The second DCI signaling includes one of the following: The newly added fields in the DCI signaling of the second message are scheduled, and the existing target fields in the DCI signaling of the first message are scheduled.

6. The method according to claim 5, characterized in that; The repetition factor of the first message is determined by the second communication node through the first DCI signaling in the repetition factor reported by the first communication node; or, The repetition factor of the first message is determined by the second communication node through the second DCI signaling in the repetition factor reported by the first communication node.

7. The method according to claim 5, characterized in that, The existing target fields include one of the following: Modulation coding field, redundancy version field, new data indication field, time domain resource allocation field, frequency domain resource allocation field, power control field, reserved field.

8. The method according to claim 3, characterized in that, The repetition factor of the first message is determined by scaling the repetition factor of the second message based on the scaling factor; The scaling factor is a predefined factor, or is indicated by the second communication node through higher-layer signaling or third DCI signaling; The repetition factor of the second message is a predefined factor, or is indicated by the second communication node through higher-layer signaling or second DCI signaling.

9. The method according to claim 8, characterized in that, The third DCI signaling includes one of the following: Schedule the newly added fields in the DCI signaling of the second message, schedule the newly added fields in the DCI signaling of the first message, schedule the existing target fields in the DCI signaling of the second message, and schedule the existing target fields in the DCI signaling of the first message. The existing target fields include one of the following: Modulation coding field, redundancy version field, new data indication field, time domain resource allocation field, frequency domain resource allocation field, power control field, reserved field.

10. The method according to claim 8, characterized in that: The scaled repetition factor is used by the first communication node to send the first message.

11. The method according to claim 3, characterized in that, The repetition factor of the first message is determined based on the transport block scaling parameter or MCS parameter of the second message.

12. The method according to claim 11, characterized in that, Each value of the transport block scaling parameter corresponds to a repetition factor of the first message; or, Each value or set of values ​​of the MCS parameter corresponds to a repetition factor of the first message.

13. The method according to claim 1, characterized in that, The repetition factor of the first message is determined by the common repetition factor indicated by the second communication node.

14. The method according to claim 13, characterized in that, The second communication node indicates that the determined common repetition factor is used by the first communication node to receive or send the third message; The third message includes at least one of the following: Random access preamble, random access response message, RRC establishment request message, contention resolution message, PUCCH message for carrying HARQ-ACK feedback of contention resolution message, RRC establishment complete message, and RRC recovery complete message.

15. The method according to claim 14, characterized in that: The repetition factor of the third message is determined by the first communication node by scaling the common repetition factor indicated by the second communication node according to a common scaling factor; or... The repetition factor corresponding to one of the multiple messages included in the third message is determined by the common repetition factor corresponding to another message included in the multiple messages, wherein one of the multiple messages is transmitted after the other message in the multiple messages; The common scaling factor is a predefined factor, or it is indicated by the second communication node through higher-layer signaling or fourth DCI signaling.

16. The method according to claim 15, characterized in that, The fourth DCI signaling includes one of the following: The DCI for scheduling random access response, the DCI for scheduling contention resolution message, the DCI for scheduling RRC establishment completion response message, the DCI for scheduling RRC recovery completion response message, and the common DCI.

17. The method according to claim 15, characterized in that: The request for duplication or duplication capability reporting of another message among the multiple messages included in the third message is the same as the request for duplication or duplication capability reporting of one of the multiple messages included in the third message.

18. The method according to claim 1, characterized in that, The method further includes: The fourth message is sent to the second communication node to request the repetition or repetition capability reporting of the second message. The fourth message includes one of the following: Msg3 message, random access preamble message, and public PUCCH message.

19. The method according to claim 18, characterized in that: The request for duplication or duplication capability reporting in the first message is the same as the request for duplication or duplication capability reporting in the second message; or, The request for duplication or duplication capability reporting in the first message is the same as the request for duplication or duplication capability reporting in one of the multiple messages included in the third message.

20. The method according to claim 19, characterized in that, The request for repetition or repetition capability reporting is carried out in one of the following ways: The higher-layer signaling carried in the Msg3 message, the physical layer signaling carried in the Msg3 message, the target value of the identity identifier carried in the scrambled Msg3 message, the payload of the higher-layer signaling carried in the Msg3 message, the target preamble sequence carried in the random access preamble message, the target random access timing carried in the random access preamble message, and the target time-frequency resources carried in the random access preamble message.

21. The method according to claim 17 or 19, characterized in that, A message whose request for duplication or duplication capability is reported is the same as that of one of the messages included in the third message if at least one of the following conditions is met: or the request for duplication or duplication capability is reported the same as that of the first message and the second message; or the request for duplication or duplication capability is reported the same as that of the first message and the third message. The second communication node indicates one or more repetition factors; The second communication node indicates one or more scaling factors; The signal quality measured by the first communication node is lower than the first threshold configured by the second communication node; The second communication node enabled repetition for the first message; The second communication node enabled repetition for the second message; The second communication node enabled the repetition of the third message.

22. The method according to claim 1, characterized in that, The first communication node performs the operation to determine the repetition factor if at least one of the following conditions is met: The signal quality measured by the first communication node is lower than the first threshold configured by the second communication node; The first communication node sent a request for repetition or repetition capability reporting to the second communication node; The second communication node indicates multiple repetition factors; The second communication node indicates multiple scaling factors; The second communication node enabled repetition for the first message; The second communication node enabled repetition for the second message; The second communication node enabled the repetition of the third message.

23. A communication node, comprising: At least one processor; At least one memory for storing at least one program; At least one of the programs is executed by at least one of the processors to perform the communication method according to any one of claims 1 to 22.

24. A computer-readable storage medium storing computer-executable instructions, characterized in that, The computer-executable instructions are used to execute the communication method according to any one of claims 1 to 22.

25. A computer program product, comprising a computer program or computer instructions, characterized in that, The computer program or the computer instructions are stored in a computer-readable storage medium. The processor of the communication node reads the computer program or the computer instructions from the computer-readable storage medium and executes the computer program or the computer instructions, causing the communication node to perform the communication method according to any one of claims 1 to 22.

Images