Method and apparatus for supporting transmission of a pusch

Abstract

The disclosure relates to a 5G or 6G communication system for supporting a higher data transmission rate. The disclosure involves a method performed by a user equipment (UE) in a wireless communication system, comprising: identifying first information that configures or schedules transmission of a physical uplink shared channel (PUSCH); identifying second information which is redundancy version repetition related information; transmitting the PUSCH based on the first information and the second information, wherein the second information indicates a length of an orthogonal coverage code (OCC).

Description

METHOD AND APPARATUS FOR SUPPORTING TRANSMISSION OF A PUSCH

[0001] The present disclosure relates to a field of communication, and in particularly, to a first communication node and a method performed by the same, and a second communication node and a method performed by the same.

[0002] 5G mobile communication technologies define broad frequency bands such that high transmission rates and new services are possible, and can be implemented not only in "Sub 6GHz" bands such as 3.5GHz, but also in "Above 6GHz" bands referred to as mmWave including 28GHz and 39GHz. In addition, it has been considered to implement 6G mobile communication technologies (referred to as Beyond 5G systems) in terahertz bands (for example, 95GHz to 3THz bands) in order to accomplish transmission rates fifty times faster than 5G mobile communication technologies and ultra-low latencies one-tenth of 5G mobile communication technologies.

[0003] At the beginning of the development of 5G mobile communication technologies, in order to support services and to satisfy performance requirements in connection with enhanced Mobile BroadBand (eMBB), Ultra Reliable Low Latency Communications (URLLC), and massive Machine-Type Communications (mMTC), there has been ongoing standardization regarding beamforming and massive MIMO for mitigating radio-wave path loss and increasing radio-wave transmission distances in mmWave, supporting numerologies (for example, operating multiple subcarrier spacings) for efficiently utilizing mmWave resources and dynamic operation of slot formats, initial access technologies for supporting multi-beam transmission and broadbands, definition and operation of BWP (BandWidth Part), new channel coding methods such as a LDPC (Low Density Parity Check) code for large amount of data transmission and a polar code for highly reliable transmission of control information, L2 pre-processing, and network slicing for providing a dedicated network specialized to a specific service.

[0004] Currently, there are ongoing discussions regarding improvement and performance enhancement of initial 5G mobile communication technologies in view of services to be supported by 5G mobile communication technologies, and there has been physical layer standardization regarding technologies such as V2X (Vehicle-to-everything) for aiding driving determination by autonomous vehicles based on information regarding positions and states of vehicles transmitted by the vehicles and for enhancing user convenience, NR-U (New Radio Unlicensed) aimed at system operations conforming to various regulation-related requirements in unlicensed bands, NR UE Power Saving, Non-Terrestrial Network (NTN) which is UE-satellite direct communication for providing coverage in an area in which communication with terrestrial networks is unavailable, and positioning.

[0005] Moreover, there has been ongoing standardization in air interface architecture / protocol regarding technologies such as Industrial Internet of Things (IIoT) for supporting new services through interworking and convergence with other industries, IAB (Integrated Access and Backhaul) for providing a node for network service area expansion by supporting a wireless backhaul link and an access link in an integrated manner, mobility enhancement including conditional handover and DAPS (Dual Active Protocol Stack) handover, and two-step random access for simplifying random access procedures (2-step RACH for NR). There also has been ongoing standardization in system architecture / service regarding a 5G baseline architecture (for example, service based architecture or service based interface) for combining Network Functions Virtualization (NFV) and Software-Defined Networking (SDN) technologies, and Mobile Edge Computing (MEC) for receiving services based on UE positions.

[0006] As 5G mobile communication systems are commercialized, connected devices that have been exponentially increasing will be connected to communication networks, and it is accordingly expected that enhanced functions and performances of 5G mobile communication systems and integrated operations of connected devices will be necessary. To this end, new research is scheduled in connection with eXtended Reality (XR) for efficiently supporting AR (Augmented Reality), VR (Virtual Reality), MR (Mixed Reality) and the like, 5G performance improvement and complexity reduction by utilizing Artificial Intelligence (AI) and Machine Learning (ML), AI service support, metaverse service support, and drone communication.

[0007] Furthermore, such development of 5G mobile communication systems will serve as a basis for developing not only new waveforms for providing coverage in terahertz bands of 6G mobile communication technologies, multi-antenna transmission technologies such as Full Dimensional MIMO (FD-MIMO), array antennas and large-scale antennas, metamaterial-based lenses and antennas for improving coverage of terahertz band signals, high-dimensional space multiplexing technology using OAM (Orbital Angular Momentum), and RIS (Reconfigurable Intelligent Surface), but also full-duplex technology for increasing frequency efficiency of 6G mobile communication technologies and improving system networks, AI-based communication technology for implementing system optimization by utilizing satellites and AI (Artificial Intelligence) from the design stage and internalizing end-to-end AI support functions, and next-generation distributed computing technology for implementing services at levels of complexity exceeding the limit of UE operation capability by utilizing ultra-high-performance communication and computing resources.

[0008] In order to meet the increasing demand for wireless data communication services since the deployment of 4G communication systems, efforts have been made to develop improved 5G or pre-5G communication systems. Therefore, 5G or pre-5G communication systems are also called "Beyond 4G networks" or "Post-LTE systems".

[0009] In order to achieve a higher data rate, 5G communication systems are implemented in higher frequency (millimeter, mmWave) bands, e.g., 60 GHz bands. In order to reduce propagation loss of radio waves and increase a transmission distance, technologies such as beamforming, massive multiple-input multiple-output (MIMO), full-dimensional MIMO (FD-MIMO), array antenna, analog beamforming and large-scale antenna are discussed in 5G communication systems.

[0010] In addition, in 5G communication systems, developments of system network improvement are underway based on advanced small cell, cloud radio access network (RAN), ultra-dense network, device-to-device (D2D) communication, wireless backhaul, mobile network, cooperative communication, coordinated multi-points (CoMP), reception-end interference cancellation, etc.

[0011] In 5G systems, hybrid FSK and QAM modulation (FQAM) and sliding window superposition coding (SWSC) as advanced coding modulation (ACM), and filter bank multicarrier (FBMC), non-orthogonal multiple access (NOMA) and sparse code multiple access (SCMA) as advanced access technologies have been developed.

[0012] According to a first aspect of an embodiment of the present application, there is provided a method performed by a user equipment (UE) in a wireless communication system, comprising: identifying first information that configures or schedules transmission of a physical uplink shared channel (PUSCH); identifying second information which is redundancy version repetition related information; transmitting the PUSCH based on the first information and the second information, wherein the second information indicates a length of an orthogonal coverage code (OCC).

[0013] According to a another aspect of an embodiment of the present application, there is provided a method performed by a communication node in a wireless communication system, comprising: transmitting first information that configures or schedules transmission of a physical uplink shared channel (PUSCH); transmitting second information that is redundancy version repetition related information; wherein, a redundancy version to be applied to a n-th transmission occasion in the transmission of the PUSCH is the redundancy version configured or indicated by the first information, or the redundancy version to be applied to the n-th transmission occasion in the transmission of the PUSCH is determined based on the redundancy version indicated by the first information, and the second information, and wherein the n is an integer between 0 and K-1.

[0014] According to a another aspect of an embodiment of the present application, there is provided a method performed by a first communication node including: receiving information related to an orthogonal coverage code (OCC) and / or information for indicating an OCC sequence; transmitting a physical uplink shared channel (PUSCH), wherein physical resources for the transmission of the PUSCH are determined based on the information related to the OCC and / or the information for indicating the OCC sequence.

[0015] Alternatively, the receiving of the information related to the orthogonal coverage code (OCC) and / or the information for indicating the OCC sequence includes: receiving first information including the information related to the orthogonal coverage code (OCC); and / or receiving second information including the information for indicating the OCC sequence.

[0016] Alternatively, the first information is first radio resource control (RRC) configuration information, the second information is second RRC configuration information or downlink control information (DCI).

[0017] Alternatively, the method further includes: determining the physical resources for the transmission of the PUSCH based on the information related to the OCC and / or the information for indicating the OCC sequence, wherein the physical resources include at least one of time-domain resources, frequency-domain resources and code-domain resources.

[0018] Alternatively, the determining of the physical resources for the transmission of the PUSCH includes: determining the code-domain resources, based on the information related to the OCC and / or the information for indicating the OCC sequence, or based on the information related to the OCC and / or the information for indicating the OCC sequence as well as a rule predefined by a protocol, wherein the code-domain resources include the OCC sequence applied to the PUSCH, the OCC sequence being used to perform time-domain extension and / or frequency-domain extension on the PUSCH.

[0019] Alternatively, the determining of the physical resources for the transmission of the PUSCH includes:

[0020] determining the time-domain resources for transmitting the PUSCH based on the number of time units corresponding to the transmission of the PUSCH and a time unit at which the PUSCH should be transmitted, wherein the number of the time units corresponding to the transmission of the PUSCH and the time unit at which the PUSCH should be transmitted are determined based on the information related to the OCC and / or the information for indicating the OCC sequence; or

[0021] if a parameter related to repetition of the PUSCH and / or a parameter related to transmission block processing over multiple slots (TBoMS) is configured for the first communication node, determining the time-domain resources for transmitting the PUSCH, based on the parameter related to the repetition of the PUSCH and / or the parameter related to the TBoMS, as well as the information related to the OCC and / or information for indicating the OCC sequence.

[0022] Alternatively, the time unit at which the PUSCH should be transmitted is determined based on a value of a domain related to assignment of the time-domain resources in the downlink control information (DCI) and the information related to the OCC, wherein the value of the domain related to the assignment of the time-domain resources indicates an time unit offset between the PUSCH and the DCI.

[0023] Alternatively, the time unit offset is determined based on a resource assignment table, the information related to the OCC, and / or the information for indicating the OCC sequence.

[0024] Alternatively, wherein the resource assignment table includes the time unit offset, or includes the time unit offset and a parameter related to a length of the OCC sequence; or wherein the time unit offset is defined based on the length of the OCC sequence.

[0025] Alternatively, the determining of the physical resources for the transmission of the PUSCH includes: if a parameter related to frequency hopping is configured for the first communication node, determining the frequency-domain resources for the transmission of the PUSCH based on the parameter related to the frequency hopping, as well as the information related to the OCC and / or the information for indicating the OCC sequence.

[0026] Alternatively, the information related to the OCC includes at least one of:

[0027] information for indicating whether to enable the OCC or not;

[0028] information for indicating the length of the OCC sequence;

[0029] information for indicating the OCC sequence applied to the PUSCH;

[0030] information for indicating the number of OCC groups;

[0031] information for indicating an OCC occasion;

[0032] information for indicating the number of PUSCH transmission occasions corresponding to a transmission block (TB);

[0033] information for indicating a starting time unit for an initial transmission of the TB.

[0034] Alternatively, the information for indicating the OCC sequence includes at least one of:

[0035] information for indicating whether to enable the OCC or not;

[0036] information for indicating the length of the OCC sequence;

[0037] information for indicating the OCC sequence applied to the PUSCH;

[0038] information for indicating the number of OCC groups;

[0039] information for indicating the OCC occasion;

[0040] information for indicating the number of the time units corresponding to the transmission of the PUSCH;

[0041] information for indicating the time unit at which the PUSCH should be transmitted.

[0042] Alternatively, the rule predefined by the protocol includes at least one of:

[0043] a rule for determining whether to enable the OCC or not;

[0044] a rule for determining the length of the OCC sequence;

[0045] a rule for determining the OCC sequence applied to the PUSCH;

[0046] a rule for determining the OCC occasion;

[0047] a rule for determining the number of the PUSCH transmission occasions corresponding to the transmission block (TB);

[0048] a rule for determining the starting time unit for the initial transmission of the TB;

[0049] a rule for determining the number of the time units corresponding to the transmission of the PUSCH;

[0050] a rule for determining the time unit at which the PUSCH should be transmitted.

[0051] Alternatively, the first information and / or the second information further includes information for indicating a redundancy version to be applied to a n-th PUSCH transmission occasion, the method further includes: determining the redundancy version to be applied to the n-th PUSCH transmission occasion based on the information for indicating the redundancy version to be applied to the n-th PUSCH transmission occasion, wherein n includes an integer greater than or equal to zero.

[0052] Alternatively, the second information is a DCI from a second communication node, and the method further includes: when it is determined, based on the information for indicating the OCC sequence included in the DCI, that a starting time unit which is indicated for the transmission of the PUSCH is different from a starting time unit of the OCC occasion, the first communication node ignores scheduling of the PUSCH by the second communication node, or, the first communication node determines a starting time unit at which the PUSCH should be transmitted based on the starting time unit which is indicated for the transmission of the PUSCH and a parameter related to the OCC occasion.

[0053] Alternatively, the method further includes: transmitting first capability information to the second communication node, wherein the first capability information indicates whether the first communication node supports applying the OCC sequence to the transmission of the PUSCH or not.

[0054] According to a second aspect of an embodiment of the present application, there is provided a method performed by a first communication node including: receiving or detecting third information that configures or schedules transmission of a physical uplink shared channel (PUSCH) in K time units, wherein the K is an integer greater than 1; receiving fourth information that is redundancy version repetition related information; transmitting the PUSCH based on the third information and the fourth information, wherein a redundancy version to be applied to a n-th transmission occasion in the transmission of the PUSCH is the redundancy version configured or indicated by the third information, or the redundancy version to be applied to the n-th transmission occasion in the transmission of the PUSCH is determined based on the redundancy version indicated by the third information, and the fourth information, wherein the n is an integer between 0 and K-1.

[0055] Alternatively, the fourth information configures or indicates at least one of:

[0056] all of redundancy versions of repetition transmission of the PUSCH being the redundancy version configured or indicated by the third information;

[0057] activating that all of the redundancy versions of the repetition transmission of the PUSCH are the redundancy versions configured or indicated by the third information;

[0058] deactivating use of different redundancy versions in the repetition transmission of the PUSCH;

[0059] deactivating redundancy version rotation;

[0060] redundancy version repetition;

[0061] activating redundancy version repetition;

[0062] repetition number of the redundancy version.

[0063] Alternatively, the redundancy version to be applied to the n-th transmission occasion in the transmission of the PUSCH being determined based on the redundancy version indicated by the third information, and the fourth information, includes: the redundancy version to be applied to the n-th transmission occasion in the transmission of the PUSCH is determined based on the redundancy version indicated by the third information and the repetition number of the redundancy version indicated by the fourth information as well as the n.

[0064] Alternatively, wherein the fourth information indicates at least one of:

[0065] not activating that all of redundancy versions of repetition transmission of the PUSCH are the redundancy versions configured or indicated by the third information;

[0066] deactivating that all of the redundancy versions of the repetition transmission of the PUSCH are the redundancy versions configured or indicated by the third information;

[0067] not deactivating use of different redundancy versions in the repetition transmission of the PUSCH;

[0068] activating the use of different redundancy versions in the repetition transmission of the PUSCH;

[0069] the use of different redundancy versions in the repetition transmission of the PUSCH;

[0070] not deactivating redundancy version rotation;

[0071] activating the redundancy version rotation;

[0072] the redundancy version rotation;

[0073] not activating redundancy version repetition;

[0074] deactivating the redundancy version repetition, and

[0075] wherein the redundancy version to be applied to the n-th transmission occasion in the transmission of the PUSCH being determined based on the redundancy version indicated by the third information, and the fourth information, includes: the redundancy version to be applied to the n-th transmission occasion in the transmission of the PUSCH is determined based on the redundancy version indicated by the third information as well as the n.

[0076] Alternatively, a spreading based on an orthogonal code is configured or indicated for the PUSCH.

[0077] Alternatively, when the spreading based on the orthogonal code is configured or indicated for the PUSCH, the redundancy version to be applied to the n-th transmission occasion in the transmission of the PUSCH is determined based on the redundancy version indicated by the third information and a parameter related to the orthogonal code; or the redundancy version to be applied to the n-th transmission occasion in the transmission of the PUSCH is the redundancy version configured or indicated by the third information; or the redundancy version to be applied to the n-th transmission occasion in the transmission of the PUSCH is determined based on the redundancy version indicated by the third information, and the fourth information.

[0078] Alternatively, the redundancy version to be applied to the n-th transmission occasion in the transmission of the PUSCH being determined based on the redundancy version indicated by the third information and the parameter related to the orthogonal code, includes: the redundancy version to be applied to the n-th transmission occasion in the transmission of the PUSCH is determined based on the redundancy version indicated by the third information, as well as the orthogonal code or a code length of the orthogonal code.

[0079] Alternatively, the redundancy version to be applied to the n-th transmission occasion in the transmission of the PUSCH being determined based on the redundancy version indicated by the third information and the parameter related to the orthogonal code, includes: the redundancy version to be applied to the n-th transmission occasion in the transmission of the PUSCH is determined based on the redundancy version indicated by the third information, and information indicating repetition number of the redundancy version among information for configuring the spreading.

[0080] Alternatively, a spreading based on an orthogonal code is not configured or indicated for the PUSCH.

[0081] Alternatively, transmission block processing over multiple slots (TBoMS) is configured or indicated for the PUSCH, wherein the redundancy version to be applied to the n-th transmission occasion in the transmission of the PUSCH being determined based on the redundancy version indicated by the third information, and the fourth information, includes that: the redundancy version to be applied to the n-th transmission occasion in the transmission of the PUSCH is determined based on the redundancy version indicated by the third information, the fourth information, as well as the number of time units for determining a transmission block size.

[0082] Alternatively, the orthogonal code includes an orthogonal coverage code (OCC).

[0083] Alternatively, when spreading is configured or indicated for the PUSCH, the fourth information indicates at least one of: an orthogonal coverage code (OCC); a length of the orthogonal coverage code (OCC).

[0084] Alternatively, when the spreading is grouped into one or more PUSCH transmission occasion groups, the fourth information indicates at least one of: the number of PUSCH transmission occasions contained in the PUSCH transmission occasion group; the number of the PUSCH transmission occasion groups.

[0085] Alternatively, the redundancy version to be applied to the n-th transmission occasion in the transmission of the PUSCH being determined based on the redundancy version indicated by the third information, and the fourth information, includes:

[0086] the redundancy version to be applied to the n-th transmission occasion in the transmission of the PUSCH is determined based on the redundancy version indicated by the third information, as well as the number of the PUSCH transmission occasions contained in the PUSCH transmission occasion group or the number of the PUSCH transmission occasion groups.

[0087] Alternatively, the third information is indicated by one DCI format.

[0088] Alternatively, the third information is configured by higher level signaling, and the transmission of PUSCH is the transmission of a configured grant PUSCH (CG PUSCH).

[0089] Alternatively, the method further includes: transmitting second capability information to the second communication node, wherein the second capability information indicates whether a UE supports one of: all of the redundancy versions of the repetition transmission of the PUSCH being the redundancy versions configured or indicated by the third information; determining the redundancy version to be applied to the n-th transmission occasion based on the redundancy version repetition related information.

[0090] Alternatively, the method further includes: receiving information related to an orthogonal coverage code (OCC) and / or information for indicating an OCC sequence, wherein physical resources for the transmission of the PUSCH are determined based on the information related to the OCC and / or the information for indicating the OCC sequence.

[0091] Alternatively, the receiving the information related to the orthogonal coverage code (OCC) and / or the information for indicating the OCC sequence includes: receiving first information including the information related to the orthogonal coverage code (OCC); and / or receiving second information including the information for indicating the OCC sequence.

[0092] Alternatively, the first information is first radio resource control (RRC) configuration information, the second information is second RRC configuration information or downlink control information (DCI).

[0093] Alternatively, the method further includes: determining the physical resources for the transmission of the PUSCH based on the information related to the OCC and / or the information for indicating the OCC sequence, wherein the physical resources include at least one of time-domain resources, frequency-domain resources and code-domain resources.

[0094] Alternatively, the determining of the physical resources for the transmission of the PUSCH includes: determining the code-domain resources based on the information related to the OCC and / or the information for indicating the OCC sequence, or based on the information related to the OCC and / or the information for indicating the OCC sequence, and a rule predefined by a protocol, wherein the code-domain resources include the OCC sequence applied to the PUSCH, the OCC sequence being used to perform time-domain extension and / or frequency-domain extension on the PUSCH.

[0095] Alternatively, the determining of the physical resources for the transmission of the PUSCH includes:

[0096] determining the time-domain resources for transmitting the PUSCH based on number of time units corresponding to the transmission of the PUSCH and a time unit at which the PUSCH should be transmitted, wherein the number of the time units corresponding to the transmission of the PUSCH and the time unit at which the PUSCH should be transmitted are determined based on the information related to the OCC and / or the information for indicating the OCC sequence; or

[0097] if a parameter related to repetition of the PUSCH and / or a parameter related to transmission block processing over multiple slots (TBoMS) is configured for the first communication node, determining the time-domain resources for transmitting the PUSCH, based on the parameter related to the repetition of the PUSCH and / or the parameter related to the TBoMS, as well as the information related to the OCC and / or information for indicating the OCC sequence.

[0098] Alternatively, the time unit at which the PUSCH should be transmitted is determined based on a value of a domain related to assignment of the time-domain resources in the downlink control information (DCI) and the information related to the OCC, wherein the value of the domain related to the assignment of the time-domain resources indicates an time unit offset between the PUSCH and the DCI.

[0099] Alternatively, the time unit offset is determined based on a resource assignment table, the information related to the OCC, and / or the information for indicating the OCC sequence.

[0100] Alternatively, wherein the resource assignment table includes the time unit offset, or includes the time unit offset and a parameter related to a length of the OCC sequence; or wherein the time unit offset is defined based on the length of the OCC sequence.

[0101] Alternatively, the determining of the physical resources for the transmission of the PUSCH includes: if a parameter related to frequency hopping is configured for the first communication node, determining the frequency-domain resources for the transmission of the PUSCH based on the parameter related to the frequency hopping, as well as the information related to the OCC and / or the information for indicating the OCC sequence.

[0102] Alternatively, the information related to the OCC includes at least one of:

[0103] information for indicating whether to enable the OCC or not;

[0104] information for indicating the length of the OCC sequence;

[0105] information for indicating the OCC sequence applied to the PUSCH;

[0106] information for indicating the number of OCC groups;

[0107] information for indicating an OCC occasion;

[0108] information for indicating the number of PUSCH transmission occasions corresponding to a transmission block (TB);

[0109] information for indicating a starting time unit for an initial transmission of the TB.

[0110] Alternatively, the information for indicating the OCC sequence includes at least one of:

[0111] information for indicating whether to enable the OCC or not;

[0112] information for indicating the length of the OCC sequence;

[0113] information for indicating the OCC sequence applied to the PUSCH;

[0114] information for indicating the number of OCC groups;

[0115] information for indicating the OCC occasion;

[0116] information for indicating the number of the time units corresponding to the transmission of the PUSCH;

[0117] information for indicating the time unit at which the PUSCH should be transmitted.

[0118] Alternatively, the rule predefined by the protocol includes at least one of:

[0119] a rule for determining whether to enable the OCC or not;

[0120] a rule for determining the length of the OCC sequence;

[0121] a rule for determining the OCC sequence applied to the PUSCH;

[0122] a rule for determining the OCC occasion;

[0123] a rule for determining the number of the PUSCH transmission occasions corresponding to the transmission block (TB);

[0124] a rule for determining the starting time unit for the initial transmission of the TB;

[0125] a rule for determining the number of the time units corresponding to the transmission of the PUSCH;

[0126] a rule for determining the time unit at which the PUSCH should be transmitted.

[0127] Alternatively, the first information and / or the second information further includes information for indicating a redundancy version to be applied to a n-th PUSCH transmission occasion, wherein the fourth information is information for indicating the redundancy version to be applied to the n-th PUSCH transmission occasion, or information determined based on information for indicating the redundancy version to be applied to the n-th PUSCH transmission occasion,

[0128] the method further includes: determining the redundancy version to be applied to the n-th PUSCH transmission occasion based on the fourth information.

[0129] Alternatively, the second information is a DCI from the second communication node, and the method further includes: the first communication node ignores scheduling of the PUSCH by the second communication node when it is determined, based on the information included in the DCI for indicating the OCC sequence, that the starting time unit which is indicated for the transmission of the PUSCH is different from a starting time unit for the OCC occasion, or, the first communication node determines a starting time unit of the PUSCH should be transmitted based on the starting time unit which is indicated for the transmission of the PUSCH and a parameter related to the OCC occasion.

[0130] Alternatively, the method further includes: transmitting first capability information to the second communication node, wherein the first capability information indicates whether the first communication node supports applying the OCC sequence to the transmission of the PUSCH or not.

[0131] According to a third aspect of an embodiment of the present application, there is provided a method performed by a second communication node, including: transmitting information related to an orthogonal coverage code (OCC) and / or information for indicating an OCC sequence; and receiving a physical uplink shared channel (PUSCH), wherein physical resources for the transmission of the PUSCH are determined based on the information related to the OCC and / or the information for indicating the OCC sequence.

[0132] Alternatively, the transmitting of the information related to the orthogonal coverage code (OCC) and / or the information for indicating the OCC sequence, includes: transmitting first information including the information related to the orthogonal coverage code (OCC); and / or transmitting second information including the information for indicating the OCC sequence.

[0133] Alternatively, the first information is first radio resource control (RRC) configuration information, the second information is second RRC configuration information or downlink control information (DCI).

[0134] Alternatively, the information related to the OCC includes at least one of:

[0135] information for indicating whether to enable the OCC or not;

[0136] information for indicating the length of the OCC sequence;

[0137] information for indicating the OCC sequence applied to the PUSCH;

[0138] information for indicating the number of OCC groups;

[0139] information for indicating an OCC occasion;

[0140] information for indicating the number of PUSCH transmission occasions corresponding to a transmission block (TB);

[0141] information for indicating a starting time unit for an initial transmission of the TB.

[0142] Alternatively, the information for indicating the OCC sequence includes at least one of:

[0143] information for indicating whether to enable the OCC or not;

[0144] information for indicating the length of the OCC sequence;

[0145] information for indicating the OCC sequence applied to the PUSCH;

[0146] information for indicating the number of OCC groups;

[0147] information for indicating the OCC occasion;

[0148] information for indicating the number of the time units corresponding to the transmission of the PUSCH;

[0149] information for indicating the time unit at which the PUSCH should be transmitted.

[0150] Alternatively, the first information and / or the second information further includes information for indicating the redundancy version to be applied to the n-th PUSCH transmission occasion, wherein the redundancy version to be applied to the n-th PUSCH transmission occasion is determined based on the information for indicating the redundancy version to be applied to the n-th PUSCH transmission occasion, wherein n includes an integer greater than or equal to zero.

[0151] Alternatively, the method further includes: receiving first capability information from the first communication node, wherein the first capability information indicates whether the first communication node supports applying the OCC sequence to the transmission of the PUSCH or not.

[0152] According to a fourth aspect of an embodiment of the present application, there is provided a method performed by a second communication node, including: transmitting third information that configures or schedules transmission of a physical uplink shared channel (PUSCH) in K time units, wherein the K is an integer greater than 1; transmitting fourth information that is redundancy version repetition related information; wherein, a redundancy version to be applied to a n-th transmission occasion in the transmission of the PUSCH is the redundancy version configured or indicated by the third information, or the redundancy version to be applied to the n-th transmission occasion in the transmission of the PUSCH is determined based on the redundancy version indicated by the third information, and the fourth information, wherein the n is an integer between 0 and K-1.

[0153] Alternatively, the fourth information configures or indicates at least one of:

[0154] all of redundancy versions of repetition transmission of the PUSCH being the redundancy version configured or indicated by the third information;

[0155] activating that all of the redundancy versions of the repetition transmission of the PUSCH are the redundancy versions configured or indicated by the third information;

[0156] deactivating use of different redundancy versions in the repetition transmission of the PUSCH;

[0157] deactivating redundancy version rotation;

[0158] redundancy version repetition;

[0159] activating redundancy version repetition;

[0160] repetition number of the redundancy version.

[0161] Alternatively, the redundancy version to be applied to the n-th transmission occasion in the transmission of the PUSCH being determined based on the redundancy version indicated by the third information, and the fourth information, includes: the redundancy version to be applied to the n-th transmission occasion in the transmission of the PUSCH is determined based on the redundancy version indicated by the third information and the repetition number of the redundancy version indicated by the fourth information as well as the n.

[0162] Alternatively, the fourth information indicates at least one of:

[0163] the fourth information indicates at least one of:

[0164] not activating that all of redundancy versions of repetition transmission of the PUSCH are the redundancy versions configured or indicated by the third information;

[0165] deactivating that all of the redundancy versions of the repetition transmission of the PUSCH are the redundancy versions configured or indicated by the third information;

[0166] not deactivating use of different redundancy versions in the repetition transmission of the PUSCH;

[0167] activating the use of different redundancy versions in the repetition transmission of the PUSCH;

[0168] the use of different redundancy versions in the repetition transmission of the PUSCH;

[0169] not deactivating redundancy version rotation;

[0170] activating the redundancy version rotation;

[0171] the redundancy version rotation;

[0172] not activating redundancy version repetition;

[0173] deactivating the redundancy version repetition, and

[0174] wherein the redundancy version to be applied to the n-th transmission occasion in the transmission of the PUSCH being determined based on the redundancy version indicated by the third information, and the fourth information, includes: the redundancy version to be applied to the n-th transmission occasion in the transmission of the PUSCH is determined based on the redundancy version indicated by the third information as well as the n.

[0175] Alternatively, spreading based on an orthogonal code is configured or indicated for the PUSCH.

[0176] Alternatively, when the spreading based on the orthogonal code is configured or indicated for the PUSCH,

[0177] the redundancy version to be applied to the n-th transmission occasion in the transmission of the PUSCH is determined based on the redundancy version indicated by the third information and a parameter related to the orthogonal code; or

[0178] the redundancy version to be applied to the n-th transmission occasion in the transmission of the PUSCH is the redundancy version configured or indicated by the third information; or

[0179] the redundancy version to be applied to the n-th transmission occasion in the transmission of the PUSCH is determined based on the redundancy version indicated by the third information, and the fourth information.

[0180] Alternatively, the redundancy version to be applied to the n-th transmission occasion in the transmission of the PUSCH being determined based on the redundancy version indicated by the third information and the parameter related to the orthogonal code, includes: the redundancy version to be applied to the n-th transmission occasion in the transmission of the PUSCH is determined based on the redundancy version indicated by the third information, as well as the orthogonal code or a code length of the orthogonal code;

[0181] Alternatively, the redundancy version to be applied to the n-th transmission occasion in the transmission of the PUSCH being determined based on the redundancy version indicated by the third information and the parameter related to the orthogonal code, includes: the redundancy version to be applied to the n-th transmission occasion in the transmission of the PUSCH is determined based on the redundancy version indicated by the third information, and information indicating repetition number of the redundancy version among information for configuring the spreading.

[0182] Alternatively, a spreading based on an orthogonal code is not configured or indicated for the PUSCH.

[0183] Alternatively, transmission block processing over multiple slots (TBoMS) is configured or indicated for the PUSCH,

[0184] wherein the redundancy version to be applied to the n-th transmission occasion in the transmission of the PUSCH being determined based on the redundancy version indicated by the third information, and the fourth information, includes: the redundancy version to be applied to the n-th transmission occasion in the transmission of the PUSCH is determined based on the redundancy version indicated by the third information, the fourth information, as well as the number of time units for determining a transmission block size.

[0185] Alternatively, the orthogonal code includes an orthogonal coverage code (OCC).

[0186] Alternatively, when a spreading is configured or indicated for the PUSCH, the fourth information indicates at least one of: an orthogonal coverage code (OCC); a length of the orthogonal coverage code (OCC).

[0187] Alternatively, when the spreading is grouped into one or more PUSCH transmission occasion groups, the fourth information indicates at least one of: the number of PUSCH transmission occasions contained in the PUSCH transmission occasion group; the number of the PUSCH transmission occasion groups.

[0188] Alternatively, the redundancy version to be applied to the n-th transmission occasion in the transmission of the PUSCH being determined based on the redundancy version indicated by the third information, and the fourth information, includes: the redundancy version to be applied to the n-th transmission occasion in the transmission of the PUSCH is determined based on the redundancy version indicated by the third information, as well as the number of the PUSCH transmission occasions contained in the PUSCH transmission occasion group or the number of the PUSCH transmission occasion groups.

[0189] Alternatively, the third information is indicated by one DCI format.

[0190] Alternatively, the third information is configured by higher level signaling, and the transmission of PUSCH is the transmission of a configured grant PUSCH (CG PUSCH).

[0191] Alternatively, the method further includes: receiving second capability information from the first communication node, wherein the second capability information indicates whether a UE supports one of: all of the redundancy versions of the repetition transmission of the PUSCH being the redundancy versions configured or indicated by the third information; determining the redundancy version to be applied to the n-th transmission occasion based on the redundancy version repetition related information.

[0192] Alternatively, the method further includes: transmitting information related to an orthogonal coverage code (OCC) and / or information for indicating an OCC sequence, wherein physical resources for the transmission of the PUSCH are determined based on the information related to the OCC and / or the information for indicating the OCC sequence.

[0193] Alternatively, the transmitting the information related to the orthogonal coverage code (OCC) and / or the information for indicating the OCC sequence includes: transmitting first information including the information related to the orthogonal coverage code (OCC); and / or transmitting second information including the information for indicating the OCC sequence.

[0194] Alternatively, the first information is first radio resource control (RRC) configuration information, the second information is second RRC configuration information or downlink control information (DCI).

[0195] Alternatively, the information related to the OCC includes at least one of:

[0196] information for indicating whether to enable the OCC or not;

[0197] information for indicating the length of the OCC sequence;

[0198] information for indicating the OCC sequence applied to the PUSCH;

[0199] information for indicating the number of OCC groups;

[0200] information for indicating an OCC occasion;

[0201] information for indicating the number of PUSCH transmission occasions corresponding to a transmission block (TB);

[0202] information for indicating a starting time unit for an initial transmission of the TB.

[0203] Alternatively, the information for indicating the OCC sequence includes at least one of:

[0204] information for indicating whether to enable the OCC or not;

[0205] information for indicating the length of the OCC sequence;

[0206] information for indicating the OCC sequence applied to the PUSCH;

[0207] information for indicating the number of OCC groups;

[0208] information for indicating the OCC occasion;

[0209] information for indicating the number of the time units corresponding to the transmission of the PUSCH;

[0210] information for indicating the time unit at which the PUSCH should be transmitted.

[0211] Alternatively, the first information and / or the second information further includes information for indicating a redundancy version to be applied to a n-th PUSCH transmission occasion, wherein the fourth information is information for indicating the redundancy version to be applied to the n-th PUSCH transmission occasion, or information determined based on information for indicating the redundancy version to be applied to the n-th PUSCH transmission occasion.

[0212] Alternatively, the method further includes: receiving first capability information from the first communication node, wherein the first capability information indicates whether the first communication node supports applying the OCC sequence to the transmission of the PUSCH or not.

[0213] According to a fifth aspect of an embodiment of the present application, there is provided a first communication node, including: a transceiver; a processor coupled to the transceiver and configured to control the transceiver to perform the method performed by the first communication node as described above.

[0214] According to a sixth aspect of an embodiment of the present application, there is provided a second communication node, including: a transceiver; a processor coupled to the transceiver and configured to control the transceiver to perform the method performed by the second communication node as described above.

[0215] According to a seventh aspect of an embodiment of the present application, there is provided a computer-readable storage medium storing instructions that, when being executed by at least one processor, cause the at least one processor to perform any one of the methods as described above.

[0216] According to the technical solution provided by the embodiment of the present disclosure, the first communication node receives the information related to the OCC and / or the information for indicating the OCC sequence, and transmits the physical uplink shared channel (PUSCH), and since the physical resources for the transmission of the PUSCH are determined based on the information related to the OCC and / or the information for indicating the OCC sequence, it is possible to facilitate flexibly applying the OCC on the PUSCH, so that the first communication node can transmit the PUSCH on the same time-frequency resources as another communication node, thereby improving spectral efficiency and reducing transmission delay.

[0217] According to a technical solution provided by the embodiment of the present disclosure, the first communication node receives or detects the third information that configures or schedules the transmission of the PUSCH in K time units, receives the fourth information (the fourth information being the redundancy version repetition related information), and transmits the PUSCH based on the third information and the fourth information, wherein the redundancy version to be applied to a n-th transmission occasion in the transmission of the PUSCH is the redundancy version configured or indicated by the third information, or the redundancy version to be applied to the n-th transmission occasion in the transmission of the PUSCH is determined based on the redundancy version indicated by the third information, and the fourth information, in this manner, regardless of whether the first communication node supports the OCC or not, the first communication node is capable of transmitting the PUSCH on the same time-frequency resources as another communication node, thereby improving the spectral efficiency and reducing the transmission delay.

[0218] According to the inventive concept of the present disclosure, a communication node is able to transmit the PUSCH on the same time-frequency resources as another communication node, regardless of whether the communication node supports the OCC or not, thereby improving the spectral efficiency and reducing the transmission delay.

[0219] It should be understood that the above general descriptions and the detailed descriptions in the followings are exemplary and explanatory only and do not limit the present disclosure.

[0220] The accompanying drawings herein, which are incorporated into and form a part of the present specification, illustrate exemplary embodiments consistent with the present disclosure and are used in conjunction with the specification to explain the principle of the present disclosure and do not constitute an improper limitation of the present disclosure.

[0221] FIG. 1 illustrates an example wireless network 100 according to various embodiments of the present disclosure.

[0222] FIGs. 2a and 2b illustrate example wireless transmission and reception paths according to the present disclosure.

[0223] FIG. 3a illustrates an example UE 116 according to the present disclosure.

[0224] FIG. 3b illustrates an example gNB 102 according to the present disclosure.

[0225] FIG. 4 is a flowchart illustrating a method performed by a first communication node according to an embodiment of the present disclosure.

[0226] FIG. 5 is a flowchart illustrating a method performed by a first communication node according to an embodiment of the present disclosure.

[0227] FIG. 6 is a flowchart illustrating a method performed by a second communication node according to an embodiment of the present disclosure.

[0228] FIG. 7 is a flowchart illustrating a method performed by a second communication node according to an embodiment of the present disclosure.

[0229] FIG. 8 is a block diagram illustrating a first communication node according to an embodiment of the present disclosure.

[0230] FIG. 9 is a block diagram illustrating a second communication node according to an embodiment of the present disclosure.

[0231] The following description with reference to the accompanying drawings is provided to assist in a comprehensive understanding of various embodiments of the present disclosure as defined by the claims and their equivalents. It includes various specific details to assist in that understanding but these are to be regarded as merely exemplary. Accordingly, those of ordinary skill in the art will recognize that various changes and modifications of the various embodiments described herein can be made without departing from the scope and spirit of the present disclosure. In addition, descriptions of well-known functions and constructions may be omitted for clarity and conciseness.

[0232] The terms and words used in the following description and claims are not limited to the bibliographical meanings, but, are merely used by the inventor to enable a clear and consistent understanding of the present disclosure. Accordingly, it should be apparent to those skilled in the art that the following description of various embodiments of the present disclosure is provided for illustration purpose only and not for the purpose of limiting the present disclosure as defined by the appended claims and their equivalents.

[0233] It is to be understood that the singular forms “a,” “an,” and “the” include plural referents unless the context clearly dictates otherwise. Thus, for example, reference to “a component surface” includes reference to one or more of such surfaces.

[0234] The term “include” or “may include” refers to the existence of a corresponding disclosed function, operation or component which can be used in various embodiments of the present disclosure and does not limit one or more additional functions, operations, or components. The terms such as “include” and / or “have” may be construed to denote a certain characteristic, number, step, operation, constituent element, component or a combination thereof, but may not be construed to exclude the existence of or a possibility of addition of one or more other characteristics, numbers, steps, operations, constituent elements, components or combinations thereof.

[0235] The term “or” used in various embodiments of the present disclosure includes any or all of combinations of listed words. For example, the expression “A or B” may include A, may include B, or may include both A and B.

[0236] Unless defined differently, all terms used herein, which include technical terminologies or scientific terminologies, have the same meaning as that understood by a person skilled in the art to which the present disclosure belongs. Such terms as those defined in a generally used dictionary are to be interpreted to have the meanings equal to the contextual meanings in the relevant field of art, and are not to be interpreted to have ideal or excessively formal meanings unless clearly defined in the present disclosure.

[0237] The various embodiments of the present disclosure can be applied to various communication systems, such as: global system for mobile communications (GSM) system, code division multiple access (CDMA) system, broadband code division multiple access (WCDMA) system, general packet radio service (GPRS), long term evolution (LTE) system Frequency division duplex (FDD) systems, time division duplex (TDD) systems, universal mobile telecommunications systems (UMTS), global interoperability for microwave access (WiMAX) communication systems, fifth generation (5G) systems or new wireless (NR) systems, etc. In addition, the various embodiments of the present disclosure can be applied to future oriented communication technologies.

[0238] FIG. 1 illustrates an example wireless network 100 according to various embodiments of the present disclosure. The embodiment of the wireless network 100 shown in FIG. 1 is for illustration only. Other embodiments of the wireless network 100 can be used without departing from the scope of the present disclosure.

[0239] The wireless network 100 includes a gNodeB (gNB) 101, a gNB 102, and a gNB 103. gNB 101 communicates with gNB 102 and gNB 103. gNB 101 also communicates with at least one Internet Protocol (IP) network 130, such as the Internet, a private IP network, or other data networks.

[0240] Depending on a type of the network, other well-known terms such as "base station" or "access point" can be used instead of "gNodeB" or "gNB". For convenience, the terms "gNodeB" and "gNB" are used in this patent document to refer to network infrastructure components that provide wireless access for remote terminals. And, depending on the type of the network, other well-known terms such as "mobile station", "user station", "remote terminal", "wireless terminal" or "user apparatus" can be used instead of "user equipment" or "UE". For convenience, the terms "user equipment" and "UE" are used in this patent document to refer to remote wireless devices that wirelessly access the gNB, no matter whether the UE is a mobile device (such as a mobile phone or a smart phone) or a fixed device (such as a desktop computer or a vending machine).

[0241] gNB 102 provides wireless broadband access to the network 130 for a first plurality of User Equipments (UEs) within a coverage area 120 of gNB 102. The first plurality of UEs include a UE 111, which may be located in a Small Business (SB); a UE 112, which may be located in an enterprise (E); a UE 113, which may be located in a WiFi Hotspot (HS); a UE 114, which may be located in a first residence (R); a UE 115, which may be located in a second residence (R); a UE 116, which may be a mobile device (M), such as a cellular phone, a wireless laptop computer, a wireless PDA, etc. GNB 103 provides wireless broadband access to network 130 for a second plurality of UEs within a coverage area 125 of gNB 103. The second plurality of UEs include a UE 115 and a UE 116. In some embodiments, one or more of gNBs 101-103 can communicate with each other and with UEs 111-116 using 5G, Long Term Evolution (LTE), LTE-A, WiMAX or other advanced wireless communication technologies.

[0242] The dashed lines show approximate ranges of the coverage areas 120 and 125, and the ranges are shown as approximate circles merely for illustration and explanation purposes. It should be clearly understood that the coverage areas associated with the gNBs, such as the coverage areas 120 and 125, may have other shapes, including irregular shapes, depending on configurations of the gNBs and changes in the radio environment associated with natural obstacles and man-made obstacles.

[0243] As will be described in more detail below, one or more of gNB 101, gNB 102, and gNB 103 include a 2D antenna array as described in embodiments of the present disclosure. In some embodiments, one or more of gNB 101, gNB 102, and gNB 103 support codebook designs and structures for systems with 2D antenna arrays.

[0244] Although FIG. 1 illustrates an example of the wireless network 100, various changes can be made to FIG. 1. The wireless network 100 can include any number of gNBs and any number of UEs in any suitable arrangement, for example. Furthermore, gNB 101 can directly communicate with any number of UEs and provide wireless broadband access to the network 130 for those UEs. Similarly, each gNB 102-103 can directly communicate with the network 130 and provide direct wireless broadband access to the network 130 for the UEs. In addition, gNB 101, 102 and / or 103 can provide access to other or additional external networks, such as external telephone networks or other types of data networks.

[0245] FIGs. 2a and 2b illustrate example wireless transmission and reception paths according to the present disclosure. In the following description, the transmission path 200 can be described as being implemented in a gNB, such as gNB 102, and the reception path 250 can be described as being implemented in a UE, such as UE 116. However, it should be understood that the reception path 250 can be implemented in a gNB and the transmission path 200 can be implemented in a UE. In some embodiments, the reception path 250 is configured to support codebook designs and structures for systems with 2D antenna arrays as described in embodiments of the present disclosure.

[0246] The transmission path 200 includes a channel coding and modulation block 205, a Serial-to-Parallel (S-to-P) block 210, a size N Inverse Fast Fourier Transform (IFFT) block 215, a Parallel-to-Serial (P-to-S) block 220, a cyclic prefix addition block 225, and an up-converter (UC) 230. The reception path 250 includes a down-converter (DC) 255, a cyclic prefix removal block 260, a Serial-to-Parallel (S-to-P) block 265, a size N Fast Fourier Transform (FFT) block 270, a Parallel-to-Serial (P-to-S) block 275, and a channel decoding and demodulation block 280.

[0247] In the transmission path 200, the channel coding and modulation block 205 receives a set of information bits, applies coding (such as Low Density Parity Check (LDPC) coding), and modulates the input bits (such as using Quadrature Phase Shift Keying (QPSK) or Quadrature Amplitude Modulation (QAM)) to generate a sequence of frequency-domain modulated symbols. The Serial-to-Parallel (S-to-P) block 210 converts (such as demultiplexes) serial modulated symbols into parallel data to generate N parallel symbol streams, where N is a size of the IFFT / FFT used in gNB 102 and UE 116. The size N IFFT block 215 performs IFFT operations on the N parallel symbol streams to generate a time-domain output signal. The Parallel-to-Serial block 220 converts (such as multiplexes) parallel time-domain output symbols from the Size N IFFT block 215 to generate a serial time-domain signal. The cyclic prefix addition block 225 inserts a cyclic prefix into the time-domain signal. The up-converter 230 modulates (such as up-converts) the output of the cyclic prefix addition block 225 to an RF frequency for transmission via a wireless channel. The signal can also be filtered at a baseband before switching to the RF frequency.

[0248] The RF signal transmitted from gNB 102 arrives at UE 116 after passing through the wireless channel, and operations in reverse to those at gNB 102 are performed at UE 116. The down-converter 255 down-converts the received signal to a baseband frequency, and the cyclic prefix removal block 260 removes the cyclic prefix to generate a serial time-domain baseband signal. The Serial-to-Parallel block 265 converts the time-domain baseband signal into a parallel time-domain signal. The Size N FFT block 270 performs an FFT algorithm to generate N parallel frequency-domain signals. The Parallel-to-Serial block 275 converts the parallel frequency-domain signal into a sequence of modulated data symbols. The channel decoding and demodulation block 280 demodulates and decodes the modulated symbols to recover the original input data stream.

[0249] Each of gNBs 101-103 may implement a transmission path 200 similar to that for transmitting to UEs 111-116 in the downlink, and may implement a reception path 250 similar to that for receiving from UEs 111-116 in the uplink. Similarly, each of UEs 111-116 may implement a transmission path 200 for transmitting to gNBs 101-103 in the uplink, and may implement a reception path 250 for receiving from gNBs 101-103 in the downlink.

[0250] Each of the components in FIGs. 2a and 2b can be implemented using only hardware, or using a combination of hardware and software / firmware. As a specific example, at least some of the components in FIGs. 2a and 2b may be implemented in software, while other components may be implemented in configurable hardware or a combination of software and configurable hardware. For example, the FFT block 270 and IFFT block 215 may be implemented as configurable software algorithms, in which the value of the size N may be modified according to the implementation.

[0251] Furthermore, although described as using FFT and IFFT, this is only illustrative and should not be interpreted as limiting the scope of the present disclosure. Other types of transforms can be used, such as Discrete Fourier transform (DFT) and Inverse Discrete Fourier Transform (IDFT) functions. It should be understood that for DFT and IDFT functions, the value of variable N may be any integer (such as 1, 2, 3, 4, etc.), while for FFT and IFFT functions, the value of variable N may be any integer which is a power of 2 (such as 1, 2, 4, 8, 16, etc.).

[0252] Although FIGs. 2a and 2b illustrate examples of wireless transmission and reception paths, various changes may be made to FIGs. 2a and 2b. For example, various components in FIGs. 2a and 2b can be combined, further subdivided or omitted, and additional components can be added according to specific requirements. Furthermore, FIGs. 2a and 2b are intended to illustrate examples of types of transmission and reception paths that can be used in a wireless network. Any other suitable architecture can be used to support wireless communication in a wireless network.

[0253] FIG. 3a illustrates an example UE 116 according to the present disclosure. The embodiment of UE 116 shown in FIG. 3a is for illustration only, and UEs 111-115 of FIG. 1 can have the same or similar configuration. However, a UE has various configurations, and FIG. 3a does not limit the scope of the present disclosure to any specific implementation of the UE.

[0254] UE 116 includes an antenna 301, a radio frequency (RF) transceiver 302, a transmission (TX) processing circuit 303, a microphone 304, and a reception (RX) processing circuit 305. UE 116 also includes a speaker 306, a controller / processor 307, an input / output (I / O) interface 308, an input device(s) 309, a display 310, and a memory 311. The memory 311 includes an operating system (OS) 312 and one or more applications 313.

[0255] The RF transceiver 302 receives an incoming RF signal transmitted by a gNB of the wireless network 100 from the antenna 301. The RF transceiver 302 down-converts the incoming RF signal to generate an intermediate frequency (IF) or baseband signal. The IF or baseband signal is transmitted to the RX processing circuit 305, where the RX processing circuit 305 generates a processed baseband signal by filtering, decoding and / or digitizing the baseband or IF signal. The RX processing circuit 305 transmits the processed baseband signal to speaker 306 (such as for voice data) or to controller / processor 307 for further processing (such as for web browsing data).

[0256] The TX processing circuit 303 receives analog or digital voice data from microphone 304 or other outgoing baseband data (such as network data, email or interactive video game data) from controller / processor 307. The TX processing circuit 303 encodes, multiplexes, and / or digitizes the outgoing baseband data to generate a processed baseband or IF signal. The RF transceiver 302 receives the outgoing processed baseband or IF signal from the TX processing circuit 303 and up-converts the baseband or IF signal into an RF signal transmitted via the antenna 301.

[0257] The controller / processor 307 can include one or more processors or other processing devices and execute an OS 312 stored in the memory 311 in order to control the overall operation of UE 116. For example, the controller / processor 307 can control the reception of forward channel signals and the transmission of backward channel signals through the RF transceiver 302, the RX processing circuit 305 and the TX processing circuit 303 according to well-known principles. In some embodiments, the controller / processor 307 includes at least one microprocessor or microcontroller.

[0258] The controller / processor 307 is also capable of executing other processes and programs residing in the memory 311, such as operations for channel quality measurement and reporting for systems with 2D antenna arrays as described in embodiments of the present disclosure. The controller / processor 307 can move data into or out of the memory 311 as required by an execution process. In some embodiments, the controller / processor 307 is configured to execute the application 313 based on the OS 312 or in response to signals received from the gNB or the operator. The controller / processor 307 is also coupled to an I / O interface 308, where the I / O interface 308 provides UE 116 with the ability to connect to other devices such as laptop computers and handheld computers. I / O interface 308 is a communication path between these accessories and the controller / processor 307.

[0259] The controller / processor 307 is also coupled to the input device(s) 309 and the display 310. An operator of UE 116 can input data into UE 116 using the input device(s) 309. The display 310 may be a liquid crystal display or other display capable of presenting text and / or at least limited graphics (such as from a website). The memory 311 is coupled to the controller / processor 307. A part of the memory 311 can include a random access memory (RAM), while another part of the memory 311 can include a flash memory or other read-only memory (ROM).

[0260] Although FIG. 3a illustrates an example of UE 116, various changes can be made to FIG. 3a. For example, various components in FIG. 3a can be combined, further subdivided or omitted, and additional components can be added according to specific requirements. As a specific example, the controller / processor 307 can be divided into a plurality of processors, such as one or more central processing units (CPUs) and one or more graphics processing units (GPUs). Furthermore, although FIG. 3a illustrates that the UE 116 is configured as a mobile phone or a smart phone, UEs can be configured to operate as other types of mobile or fixed devices.

[0261] FIG. 3b illustrates an example gNB 102 according to the present disclosure. The embodiment of gNB 102 shown in FIG. 3b is for illustration only, and other gNBs of FIG. 1 can have the same or similar configuration. However, a gNB has various configurations, and FIG. 3b does not limit the scope of the present disclosure to any specific implementation of a gNB. It should be noted that gNB 101 and gNB 103 can include the same or similar structures as gNB 102.

[0262] As shown in FIG. 3b, gNB 102 includes a plurality of antennas 370a-370n, a plurality of RF transceivers 372a-372n, a transmission (TX) processing circuit 374, and a reception (RX) processing circuit 376. In certain embodiments, one or more of the plurality of antennas 370a-370n include a 2D antenna array. gNB 102 also includes a controller / processor 378, a memory 380, and a backhaul or network interface 382.

[0263] RF transceivers 372a-372n receive an incoming RF signal from antennas 370a-370n, such as a signal transmitted by UEs or other gNBs. RF transceivers 372a-372n down-convert the incoming RF signal to generate an IF or baseband signal. The IF or baseband signal is transmitted to the RX processing circuit 376, where the RX processing circuit 376 generates a processed baseband signal by filtering, decoding and / or digitizing the baseband or IF signal. RX processing circuit 376 transmits the processed baseband signal to controller / processor 378 for further processing.

[0264] The TX processing circuit 374 receives analog or digital data (such as voice data, network data, email or interactive video game data) from the controller / processor 378. TX processing circuit 374 encodes, multiplexes and / or digitizes outgoing baseband data to generate a processed baseband or IF signal. RF transceivers 372a-372n receive the outgoing processed baseband or IF signal from TX processing circuit 374 and up-convert the baseband or IF signal into an RF signal transmitted via antennas 370a-370n.

[0265] The controller / processor 378 can include one or more processors or other processing devices that control the overall operation of gNB 102. For example, the controller / processor 378 can control the reception of forward channel signals and the transmission of backward channel signals through the RF transceivers 372a-372n, the RX processing circuit 376 and the TX processing circuit 374 according to well-known principles. The controller / processor 378 can also support additional functions, such as higher-level wireless communication functions. For example, the controller / processor 378 can perform a Blind Interference Sensing (BIS) process such as that performed through a BIS algorithm, and decode a received signal from which an interference signal is subtracted. A controller / processor 378 may support any of a variety of other functions in gNB 102. In some embodiments, the controller / processor 378 includes at least one microprocessor or microcontroller.

[0266] The controller / processor 378 is also capable of executing programs and other processes residing in the memory 380, such as a basic OS. The controller / processor 378 can also support channel quality measurement and reporting for systems with 2D antenna arrays as described in embodiments of the present disclosure. In some embodiments, the controller / processor 378 supports communication between entities such as web RTCs. The controller / processor 378 can move data into or out of the memory 380 as required by an execution process.

[0267] The controller / processor 378 is also coupled to the backhaul or network interface 382. The backhaul or network interface 382 allows gNB 102 to communicate with other devices or systems through a backhaul connection or through a network. The backhaul or network interface 382 can support communication over any suitable wired or wireless connection(s). For example, when gNB 102 is implemented as a part of a cellular communication system, such as a cellular communication system supporting 5G or new radio access technology or NR, LTE or LTE-A, the backhaul or network interface 382 can allow gNB 102 to communicate with other gNBs through wired or wireless backhaul connections. When gNB 102 is implemented as an access point, the backhaul or network interface 382 can allow gNB 102 to communicate with a larger network, such as the Internet, through a wired or wireless local area network or through a wired or wireless connection. The backhaul or network interface 382 includes any suitable structure that supports communication through a wired or wireless connection, such as an Ethernet or an RF transceiver.

[0268] The memory 380 is coupled to the controller / processor 378. A part of the memory 380 can include an RAM, while another part of the memory 380 can include a flash memory or other ROMs. In certain embodiments, a plurality of instructions, such as the BIS algorithm, are stored in the memory. The plurality of instructions are configured to cause the controller / processor 378 to execute the BIS process and decode the received signal after subtracting at least one interference signal determined by the BIS algorithm.

[0269] As will be described in more detail below, the transmission and reception paths of gNB 102 (implemented using RF transceivers 372a-372n, TX processing circuit 374 and / or RX processing circuit 376) support aggregated communication with FDD cells and TDD cells.

[0270] Although FIG. 3b illustrates an example of gNB 102, various changes may be made to FIG. 3b. For example, gNB 102 can include any number of each component shown in FIG. 3a. As a specific example, the access point can include many backhaul or network interfaces 382, and the controller / processor 378 can support routing functions to route data between different network addresses. As another specific example, although shown as including a single instance of the TX processing circuit 374 and a single instance of the RX processing circuit 376, gNB 102 can include multiple instances of each (such as one for each RF transceiver).

[0271] The exemplary embodiments of the present disclosure are further described below in conjunction with the accompanying drawings.

[0272] The text and drawings are provided as examples only to help readers understand the present disclosure. They are not intended and should not be interpreted as limiting the scope of the present disclosure in any way. Although certain embodiments and examples have been provided, based on the content disclosed herein, it is obvious to those skilled in the art that modifications to the illustrated embodiments and examples can be made without departing from the scope of the present disclosure.

[0273] In a NR communication system, a Physical Uplink Shared Channel (PUSCH) may be used to transmit application data and control information of a user equipment (UE). However, there is still a need to further reduce a transmission delay of the PUSCH of the UE and improve spectral efficiency. In order to further reduce the transmission delay of the PUSCH of the UE, the present disclosure provides an enhanced transmission method of the PUSCH.

[0274] For example, according to a method of an embodiment of the present disclosure, it can enable different communication nodes to flexibly transmit a PUSCH on the same time-frequency resource, thereby reducing the transmission delay of the communication nodes and improving the spectral efficiency.

[0275] According to a method of an embodiment of the present disclosure, by applying an Orthogonal Cover Code (OCC) on a PUSCH, different communication nodes may be allowed to transmit the PUSCH on the same time-frequency resource, thereby reducing the transmission delay of the communication nodes. For a communication node capable of supporting the OCC, the present disclosure provides a method that enables a communication node to flexibly apply the OCC on the PUSCH so that the communication node is able to transmit the PUSCH on the same time-frequency resource as another communication node (e.g., another communication node that supports the OCC or another communication node that does not support OCC), thereby improving the spectral efficiency and reducing the transmission delay. For a communication node that does not support OCC, the present disclosure provides a method that enables the communication node to still transmit the PUSCH on the same time-frequency resource as another communication node (e.g., another communication node that supports the OCC or another communication node that does not support the OCC), thereby improving the spectral efficiency and reducing the transmission delay. Finally, according to the inventive concept of the present disclosure, the communication node is able to transmit the PUSCH on the same time-frequency resources as another communication node, regardless of whether the communication node supports the OCC or not, the spectral efficiency is improved and the transmission delay is reduced.

[0276] Specifically, embodiments of the present disclosure provide a method performed by a first communication node, the first communication node, a method performed by a second communication node, and the second communication node in a wireless communication system. In the followings, various embodiments of the present disclosure will be described in detail with reference to the accompanying drawings.

[0277] In the embodiments of the present disclosure, for ease of description, a first communication node and a second communication node are defined. For example, the first communication node may be a UE and the second communication node may be a base station. As another example, the embodiments of the present disclosure may be applicable to a side-link communication scenario, in this case, the first communication node may be a UE and the second communication node may be another UE. Thus, the first communication node and the second communication node may each be any suitable communication node. In the following description, the first communication node is illustrated as an example of a UE and the second communication node is illustrated as an example of a base station.

[0278] In describing a wireless communication system and in the present disclosure described below, higher level signaling (also referred to as “higher level signaling”) or a higher level signal may be a signal transfer method that is used to transfer information from a base station to a terminal through a downlink data channel of a physical layer or transfer information from the terminal to the base station through an uplink data channel of the physical layer, and an example of the signal transfer method may include a signal transfer method for transferring information through radio resource control (RRC) signaling, packet data convergence protocol (PDCP) signaling, or medium access control (MAC) control element (CE).

[0279] In the following description of the present disclosure, the higher level signaling may be signaling corresponding to at least one or a combination of one or more of the following signaling.

[0280] - an MIB (Master Information Block)

[0281] - a SIB (System Information Block) or SIB X (X=1, 2, ...)

[0282] - RRC signaling

[0283] - an MAC CE

[0284] Physical layer (Layer 1 (L1)) signaling may be signaling corresponding to at least one or a combination of one or more of the following signaling.

[0285] - a PDCCH (Physical Downlink Control Channel)

[0286] - a DCI (Downlink Control Information)

[0287] - a UE-specific DCI

[0288] - a group-common DCI

[0289] - a common DCI

[0290] - a scheduling DCI (e.g., a DCI that schedules downlink or uplink data)

[0291] - a non-scheduling DCI (e.g., a DCI other than the DCI that schedules downlink or uplink data)

[0292] - a PUCCH (Physical Uplink Control Channel)

[0293] - a UCI (Uplink Control Information)

[0294] In the embodiment of the present disclosure, uplink control signaling may include the physical layer signaling and / or the higher layer signaling. As described above, the physical layer signaling may include the UCI and / or PUCCH, and the higher layer signaling may include the RRC signaling and / or the MAC CE.

[0295] In the embodiment of the present disclosure, downlink control signaling may include the physical layer signaling and / or the higher layer signaling. As described above, the physical layer signaling may include one or more of the PDCCH, the DCI, the UE-specific DCI, the group-common DCI, the common DCI, the scheduling DCI (e.g., the DCI for scheduling the downlink or uplink data), the non-scheduling DCI, and the higher layer signaling may include one or more of the MIB, the SIB, or the SIB X (X=1, 2, ... ), the RRC signaling or the MAC CE. Thus, “configuring or indicating X through the downlink control signaling” will be understood to configure or indicate the X through the physical layer signaling, or to configure or indicate the X through the higher layer signaling, or to configure or indicate the X through a combination of the higher layer signaling and the physical layer signaling.

[0296] FIG. 4 is a flowchart illustrating a method performed by a first communication node according to an embodiment of the present disclosure. Referring to FIG. 4, at step S410, information related to an orthogonal coverage code (OCC) and / or information for indicating an OCC sequence is received. For example, the first communication node receives the information related to the OCC and / or the information for indicating the OCC sequence from the second communication node. According to an embodiment, step S410 may include: receiving first information including the information related to the orthogonal coverage code (OCC); and / or receiving second information including the information for indicating the OCC sequence. For example, the first information may be first radio resource control (RRC) configuration information and the second information may be second RRC configuration information or downlink control information (DCI). In the above example, the information related to the orthogonal coverage code (OCC) is received in the first information and the information for indicating the OCC sequence is received in the second information, but the manner of receiving the information related to the orthogonal coverage code (OCC) and / or the information for indicating the OCC sequence is not limited to this, for example, it is also possible to receive both in single information.

[0297] Next, at step S420, a physical uplink shared channel (PUSCH) is transmitted, wherein physical resources for the transmission of the PUSCH are determined based on the information related to the OCC and / or the information for indicating the OCC sequence.

[0298] In the followings, the information related to the orthogonal coverage code (OCC） and the information for indicating the OCC sequence is described in detail.

[0299] According to an embodiment, the information related to the OCC may include at least one of:

[0300] information for indicating whether to enable the OCC or not;

[0301] information for indicating the length of the OCC sequence;

[0302] information for indicating the OCC sequence applied to the PUSCH;

[0303] information for indicating the number of OCC groups;

[0304] information for indicating an OCC occasion;

[0305] information for indicating the number of PUSCH transmission occasions corresponding to a transmission block (TB);

[0306] information for indicating a starting time unit for an initial transmission of the TB.

[0307] However, the information related to the OCC is not limited to the above items.

[0308] Below, each of the above information is presented, respectively.

[0309] ●The information for indicating whether to enable the OCC or not

[0310] ◆The information for indicating whether to enable the OCC or not may be in a form of a table, or in a form of a separate RRC parameter, the present disclosure is not limited to this. If in the form of the table, the table may indicate whether OCC is enabled or not, in addition, may also indicate whether redundancy version rotation (RV rotation) is disabled or not, and may also contain sequences that are orthogonal to each other, which may be of the same or different lengths, and the table may indicate the number of PUSCH transmission occasions corresponding to the TB, etc., and the present disclosure has no limitation to the specific form in which the table is presented.

[0311] ◆The UE may determine whether to apply the OCC sequence on the PUSCH through this information, for example, the first information contains a (high-level) parameterPUSCH-OCCenabled. In one particular implementation, for the transmission of the PUSCH, if the parameterPUSCH-OCCenabledis configured, the OCC is enabled, and the PUSCH transmitted by the UE is time-domain extended, and if the parameterPUSCH-OCCenabledis default, the OCC is disabled and the PUSCH transmitted by the UE is not time-domain extended. In one particular implementation, for the transmission of the PUSCH, if the parameterPUSCH-OCCenabledis configured and a value of the parameterPUSCH-OCCenabledis 1, the OCC is enabled and the PUSCH transmitted by the UE is time-domain-extended, and if the parameterPUSCH-OCCenabledis default or the value of the parameterPUSCH-OCCenabledis 0, the OCC is disabled and the PUSCH transmitted by the UE is not time-domain-extended. If the OCC is enabled, the UE may determine the OCC sequence applied to the PUSCH based on the information for indicating whether to enable the OCC or not, according to other information or a rule predefined by a protocol.

[0312] ●The information for indicating the length of the OCC sequence

[0313] ◆The information for indicating the length of the OCC sequence may be in an explicit manner: for example, in a form of a table, or a separate RRC parameter. Alternatively, the information for indicating the length of the OCC sequence may be in an implicit manner, e.g., if a parameter related to repetition of the PUSCHrepetitionis configured, the length of the OCC sequence is related torepetition(which is equal to the number of times ofrepetition, or equal to a number predefined by the protocol)

[0314] ◆The UE may determine the length of the OCC sequence applied on the PUSCH through this information, e.g., the first information contains a (high-level) parameterPUSCH-OCClength. In one particular implementation, for the transmission of the PUSCH, if the parameterPUSCH-OCClengthis configured, the length of the OCC sequence for the transmission of the PUSCH is indicated by the parameterPUSCH-OCClength. For example, a possible value ofPUSCH-OCClengthis n2, n4, n8. IfPUSCH-OCClengthtakes the value of n2, the length of the OCC sequence for transmission of the PUSCH is 2, ifPUSCH-OCClengthtakes the value of n4, the length of the OCC sequence for transmission of the PUSCH is 4, and if PUSCH- OCClength takes the value n8, the length of the OCC sequence for transmission of the PUSCH is 8; the UE may determine the OCC sequence applied to transmission of the PUSCH based on the length of the OCC sequence applied to transmission of the PUSCH, according to other information or a rule predefined by the protocol.

[0315] ◆Alternatively, the UE may determine the form of the OCC sequence applied to the PUSCH through this information, e.g., the first information contains the (high-level) parameterPUSCH-OCClength. In one particular implementation, for the transmission of the PUSCH, if the parameterPUSCH-OCClengthis configured, selection of the table of the OCC sequence applied to the transmission of the PUSCH is indicated by the parameterPUSCH-OCClength. For example, a manner of the selection of the table of the OCC sequence applied to the transmission of the PUSCH being indicated by the parameterPUSCH-OCClengthmay be that a relationship between the table of the OCC sequence applied to the transmission of the PUSCH and the parameterPUSCH-OCClengthis predefined by the protocol, as shown in a table below:

[0316]

[0317] One example of Table 1 may be

[0318] Row indexOCC sequence1Sequence 1, e.g., {+1 +1}2Sequence 2, e.g., {+1 -1}

[0319] One example of Table 2 may be

[0320] Row indexOCC sequence1Sequence 3, e.g., {+1 +1 +1 +1}2Sequence 4, e.g., {+1 +1 -1 -1}3Sequence 5, e.g., {+1 -1 -1 +1}4Sequence 6, e.g., {+1 -1 +1 -1}

[0321] The UE may determine the OCC sequence applied to the transmission of the PUSCH based on the table of the OCC sequence applied to the PUSCH, according to other information or a rule predefined by the protocol;

[0322] ◆Alternatively, the UE may determine the length of the OCC sequence based on the parameter related to the repetition of the PUSCH. For example, if the repetition of the PUSCH is configured for the UE, the length of the OCC sequence is related to the parameter related to the repetition. The relationship between the length of the OCC sequence and the parameter related to the repetition may be predetermined by the protocol. In one particular implementation,pusch-AggregationFactoris configured for the UE, the length of the OCC sequence applied to the PUSCH is equal topusch-AggregationFactor. In one particular implementation, there is a parameternumberOfRepetitionsin a resource assignment table, the length of the OCC sequence is equal tonumberOfRepetitions. In one particular implementation,pusch-AggregationFactoris configured for the UE, a value ofpusch-AggregationFactormay be n2, n4, n8, n16, n32, and if the value ofpusch-AggregationFactoris n2, the length of the OCC sequence is 2, if the value ofpusch-AggregationFactoris n4, the length of the OCC sequence is 4, and if the value ofpusch-AggregationFactoris one of n8, n16, n32, the length of the OCC sequence is 8. In one particular implementation, there is the parameternumberOfRepetitionsin the resource assignment table, ifnumberOfRepetitions= 2, the length of the OCC sequence is 2, ifnumberOfRepetitions= 4, the length of the OCC sequence is 4, ifnumberOfRepetitionsis greater than or equal to 8, the length of the OCC sequence is 8.

[0323] ●The information for indicating the OCC sequence applied to the PUSCH

[0324] ◆The UE may determine the OCC sequence applied on the PUSCH through this information, for example, the first information contains a (high-level) parameterPUSCH-OCCsequence. In one particular implementation, for the transmission of the PUSCH, if the parameterPUSCH-OCCsequenceis configured, the OCC sequence for the transmission of the PUSCH is indicated by the parameterPUSCH-OCCsequence. For example, a value of the parameterPUSCH-OCCsequencemay bea,b. If the value of thePUSCH-OCCsequenceisa, the OCC sequence for the transmission of the PUSCH is {+1 +1}; if the value of thePUSCH-OCCsequenceisb, the OCC sequence for the transmission of the PUSCH is {+1 -1}.

[0325] ◆Alternatively, the UE may determine a candidate set of OCC sequences applied on the PUSCH through this information, for example, the first information contains a (high-level) parameterPUSCH-OCCsequenceList. The UE may determine the OCC sequence applied on the PUSCH based on the candidate set of the OCC sequences applied on the PUSCH Sequence, according to other information or a rule predefined by the protocol;

[0326] An example ofPUSCH-OCCsequenceListmay be

[0327] Row indexOCC sequence1Sequence 1, e.g., {+1 +1}2Sequence 2, e.g., {+1 -1}3Sequence 3, e.g., {+1 +1 +1 +1}4Sequence 4, e.g., {+1 +1 -1 -1}5Sequence 5, e.g., {+1 -1 -1 +1}6Sequence 6, e.g., {+1 -1 +1 -1}

[0328] ◆It is to be noted that the information for indicating the OCC sequence applied to the PUSCH may be information for indicating an OCC sequence of P PUSCH transmission occasions, wherein a value of P may be less than or equal to the number N of all PUSCH transmission occasions corresponding to the TB, and related to time corresponding to one OCC group. In one particular implementation, the first information contains the (high-level) parameterPUSCH-OCCsequenceList, and the UE, based on the parameterPUSCH-OCCsequenceList, determines the OCC sequence for the PUSCH, the number N of all PUSCH transmission occasions corresponding to the TB, wherein a transmission signal corresponding to a n-th PUSCH transmission occasion the is denoted as , then a transmission signal corresponding to the n-th PUSCH transmission occasion after the time-domain expansion is denoted as Whereinamodbdenotes a modulo operation onbbya.

[0329] ◆Alternatively, the information for indicating the OCC sequence applied to the PUSCH may be information for indicating the OCC sequence applied to all PUSCH transmission occasions corresponding to the TB. For example, in one particular implementation, the first information contains the (high-level) parameterPUSCH-OCCsequenceList, the UE, based on the parameterPUSCH-OCCsequenceList, determines the OCC sequence for the PUSCH, the number N of all PUSCH transmission occasions corresponding to the TB, wherein a transmission signal corresponding to the n-th PUSCH transmission occasion is denoted as , then a transmission signal corresponding to the n-th PUSCH transmission occasion after the time-domain expansion is denoted as

[0330] ◆Alternatively, the information for indicating the OCC sequence applied to the PUSCH may further include information for grouping the transmission occasions of the PUSCH. For example, in one particular implementation, the first information contains the (high-level) parameterPUSCH-OCCsequenceList, the UE determines the OCC sequence for the PUSCH based on the parameterPUSCH-OCCsequenceList, wherein is the number of corresponding transmission occasions of the PUSCH in a m-th OCC group, and .

[0331] ●The information for indicating the number of the OCC groups

[0332] ◆The UE may determine the number of the OCC groups applied on the PUSCH through this information, for example, the first information contains a (high-level) parameterPUSCH-OCCnumberofgroup. In one particular implementation, for the transmission of the PUSCH, if the parameterPUSCH-OCCnumberofgroupis configured, the number of the OCC groups for the transmission of the PUSCH is indicated by the parameterPUSCH-OCCsequence. For example, if a value ofPUSCH-OCCsequenceisa, the number of the OCC groups for the transmission of the PUSCH isa.

[0333] ●The information for indicating the OCC occasion (also referred to as the “OCC window”)

[0334] ◆The UE may determine a time unit corresponding to the OCC occasion through this information, wherein the OCC occasion may appear periodically. For example, the UE may determine a first slot or first symbol in the OCC occasion through the information. For example, the information for indicating the OCC occasion may be used to indicate an offset between a starting location of the OCC occasion and a reference time, wherein the reference time may be a sub frame number (SFN), and the reference time may be configured by high-level signaling. In one particular implementation, the first information may include parametersPUSCH-OCC-timeReferenceSFNandPUSCH-OCC-timeDomainOffset, as well as an indexSof a starting symbol of the transmission of the PUSCH in one slot, then wihinin a n-th period, a configured first OCC occasion (or a start of the OCC occasion) appears in the following symbols:

[0335] [(SFN * numberOfSlotsPerFrame * numberOfSymbolsPerSlot)+ (slot number in the frame * numberOfSymbolsPerSlot) + symbol number in the slot] =(timeReferenceSFN * numberOfSlotsPerFrame * numberOfSymbolsPerSlot+ timeDomainOffset * numberOfSymbolsPerSlot + S + N * periodicity) modulo (1024 * numberOfSlotsPerFrame * numberOfSymbolsPerSlot)

[0336] wherein SFN denotes the sub frame number,numberOfSlotsPerFramedenotes the number of slots in each frame,numberOfSymbolsPerSlotdenotes the number of symbols in each slot,periodicitydenotes a period of the OCC occasion, and any one or more of the above parameters may be configured by the network,modulodenotes the modulo operation.

[0337] ◆In one particular implementation, the first information includes a parameterPUSCH-Occ-Length, the UE determines the number of time units corresponding to one OCC occasion based on the parameterPUSCH-Occ-Length, e.g., the number of slots corresponding to one OCC occasion, or the number of symbols corresponding to one OCC occasion.

[0338] ◆Alternatively, if a parameter related to CG-PUSCH is configured for the UE, within the n-th period, a symbol corresponding to a configured uplink grant or a first configured uplink grant in a multi-PUSCH configuration grants is a symbol corresponding to the first OCC occasion (or the starting of the OCC occasion) configured within the n-th period.

[0339] ◆Alternatively, if a parameter related to the repetition of the PUSCH is configured for the UE, the number of time units corresponding to the OCC occasion may be related to the parameter related to the repetition of the PUSCH. For example, if the parameternumberOfRepetitionsorpusch-AggregationFactor, orrepKis configured for the UE, the number of time units corresponding to the OCC occasion is related to at least one of the parameternumberOfRepetitions, orpusch-AggregationFactor, orrepK. In one particular implementation, ifnumberOfRepetitionsis configured for the UE, the number of time units corresponding to one OCC occasion is equal tonumberOfRepetitions. In one particular implementation, ifpusch-AggregationFactoris configured for the UE, the number of slots corresponding to one OCC occasion is equal topusch-AggregationFactor. In one particular implementation, ifrepKis configured for the UE, the number of slots corresponding to one OCC occasion is equal torepK.

[0340] ●The information for indicating the number of PUSCH transmission occasions corresponding to a transmission block (TB);

[0341] ◆The UE may determine the number of the transmission occasions of the PUSCH corresponding to the TB based on this information. For example, the first information contains the information for indicating the number of the transmission occasions of the PUSCH corresponding to the TB, which may be a parameterPUSCH-OCCnumberofoccassion(which indicates the number of OCC occasions), in this case, the number of the transmission occasions of the PUSCH corresponding to the TB is equal toPUSCH-OCCnumberofoccassion. As another example, the first information contains a parameterPUSCH-OCCnumberofoccassionList, the UE may determine the number of the transmission occasions of the PUSCH corresponding to the TB based on the parameterPUSCH-OCCnumberofoccassionList, according to other information or a rule predefined by the protocol. In one particular implementation, if the parameterPUSCH-OCCnumberofoccassionListis configured for the UE, the UE, based on other information or a rule predefined by the protocol, determines a row index, determines the number of the transmission occasions of the PUSCH corresponding to the TB based on the row index and the parameterPUSCH-OCCnumberofoccassionList, one example of the parameterPUSCH-OCCnumberofoccassionListmay be the following table 4:

[0342] Row indexThe number of the transmission occasions of the PUSCH corresponding to the TB11223448

[0343] ◆Alternatively, if the parameter related to the repetition of the PUSCH is configured for the UE, the number of the transmission occasions of the PUSCH corresponding to the TB is related to the parameter related to the repetition of the PUSCH. For example, if the parameternumberOfRepetitionsis configured for the UE for indicating the number of times of the repetition, the number of the transmission occasions of the PUSCH corresponding to the TB may be equal tonumberOfRepetitions.

[0344] ◆Alternatively, if Parameter related to the OCC is configured for the UE, the number of the transmission occasions of the PUSCH corresponding to the TB is related to the parameter related to the OCC. In one particular implementation, the first information may contain the length of the OCC sequence, and the number of the OCC groups, then the number of the transmission occasions of the PUSCH corresponding to the TB may be determined jointly by the length of the OCC sequence and the number of the OCC groups, e.g., the number of the transmission occasions of the PUSCH corresponding to the TB is equal to a product of the length of the OCC sequence and the number of the OCC groups. In one particular implementation, the first information contains the length of the OCC sequence, and the number of the OCC groups, the UE may determine the number of the transmission occasions of the PUSCH corresponding to the TB based on other information or a manner predefined by the protocol, as well as the length of the OCC sequence and the number of the OCC groups, e.g., the first information contains a parameterPUSCH-OCCList, the UE determines the number of the transmission occasion of the PUSCH corresponding to the TB based on a row index in the DCI and the parameterPUSCH-OCCList, one example of thePUSCH-OCCListmay be following table 5:

[0345] Row indexLength of OCC sequenceThe number of OCC groups121222341442………

[0346] ●The information for indicating the starting time unit for the initial transmission of the TB

[0347] ◆The UE may determine the starting time unit (e.g., a slot at which the first PUSCH transmission occasion corresponding to the TB is located, or a symbol at which the first PUSCH transmission occasion corresponding to the TB is located) for the transmission of the PUSCH corresponding to the TB through this information. For example, the first information contains a parameterPUSCH-OCCstart, then the slot at which the first PUSCH transmission occasion corresponding to the TB is located is a next available slot having an index ofPUSCH-OCCstart. For another example, the first information contains parametersPUSCH-OCCstartandPUSCH-OCCstartS, then the slot at which the first PUSCH transmission occasion corresponding to the TB is located is a next available first slot having an index ofPUSCH-OCCstart, and the symbol at which the first PUSCH transmission occasion corresponding to the TB is located is a symbol having a symbol index ofPUSCH-OCCstartSin the first slot.

[0348] ◆Alternatively, if the parameter related to the CG-PUSCH is configured for the UE, the starting time unit of the transmission of the PUSCH corresponding to the TB is related to the parameter related to the CG-PUSCH. For example, the parameterrelated to the CG-PUSCHrepKis configured for the UE and the length of the OCC sequencePUSCH-OCClengthis configured for the UE, then the starting time unit of the transmission of the PUSCH corresponding to the TB is related torepKandPUSCH-OCClength. In one particular implementation, the parameterrepKrelated to the CG-PUSCHis configured for the UE and the length of the OCC sequencePUSCH-OCClengthis configured for the UE, then the starting time unit of the transmission of the PUSCH corresponding to the TB is a (n*PUSCH-OCClength+1)-th transmission occasion ofrepKtransmission occasions within one period corresponding to the CG-PUSCH, wherein n is an integer greater than or equal to zero, and a value of n needs to satisfy that a value of (n*PUSCH-OCClength+1) cannot exceedrepK.

[0349] According to the embodiment, the elements or parameters contained in the above “information related to the OCC” may be combined arbitrarily, and some examples of such combination are given below:

[0350] ●The “information related to the OCC" contains information for indicating whether to enable the OCC or not and information for indicating the length of the OCC sequence.

[0351] ◆The UE may determine whether to apply the OCC on the PUSCH, and the length of the OCC sequence applied on the PUSCH, through this information. For example, the first information contains a (high-level) parameterPUSCH-OCClengthListcontaining at least one instance, wherein the at least one instance includes at least one of parameters: the length of the OCC sequence and whether to enable the OCC or not. In one particular implementation, one specific example of thePUSCH-OCClengthListis shown in table 6 below:

[0352] Row indexWhether to enable OCC or not and / or length of OCC sequence1Not enabling OCC2Length of OCC sequence is 23Length of OCC sequence is 44Length of OCC sequence is 8

[0353] The UE may determine the OCC sequence applied to the PUSCH based on the parameterPUSCH-OCClengthList, according to other information or a rule predefined by the protocol, e.g., obtain the row index based on the DCI, and then determine the OCC applied to the PUSCH sequence based on the row index and the parameterPUSCH-OCClengthList;

[0354] ●The “information related to the OCC” contains the information for indicating whether to enable the OCC or not, and the information for indicating the OCC sequence applied to the PUSCH, and alternatively, the information for indicating the length of the OCC sequence.

[0355] ◆The UE may determine whether to apply the OCC on the PUSCH, and the length of the OCC sequence applied on the PUSCH, and the OCC sequence applied on the PUSCH, through this information. For example, the first information contains the (high-level) parameterPUSCH-OCClengthListcontaining at least one instance (instance), wherein the at least one instance includes at least one of parameters: the length of the OCC sequence, whether to enable the OCC or not, and the OCC sequence. In one particular implementation, one specific example of thePUSCH-OCClengthListis shown in table 7 below:

[0356] Row indexWhether to enable OCC or not and / or OCC sequence1Not enabling OCC2Sequence 1, e.g., {+1 +1}3Sequence 2, e.g., {+1 -1}4Sequence 3, e.g., {+1 +1 +1 +1}5Sequence 4, e.g., {+1 +1 -1 -1}6Sequence 5, e.g., {+1 -1 -1 +1}7Sequence 6, e.g., {+1 -1 +1 -1}

[0357] In one particular implementation, one specific example of thePUSCH-OCClengthListis shown in table 8 below:

[0358] Row indexWhether to enable OCC or not and / or OCC sequenceLength of OCC sequence1Not enabling OCCDefault2Sequence 1, e.g., {+1 +1}23Sequence 2, e.g., {+1 -1}24Sequence 3, e.g., {+1 +1 +1 +1}45Sequence 4, e.g., {+1 +1 -1 -1}46Sequence 5, e.g., {+1 -1 -1 +1}47Sequence 6, e.g., {+1 -1 +1 -1}4

[0359] The UE may determine the OCC sequence applied to the PUSCH based on the parameterPUSCH-OCClengthList, according to other information or a rule predefined by the protocol, e.g., obtain the row index based on the DCI, and then determine the OCC applied to the PUSCH sequence based on the row index and the parameterPUSCH-OCClengthList;

[0360] ●The “information related to the OCC” contains information for indicating whether to enable the OCC or not, and the information for indicating the OCC sequence applied to the PUSCH and alternatively, the information for indicating the length of the OCC sequence.

[0361] ◆The UE may determine whether to apply the OCC on the PUSCH, and the length of the OCC sequence applied on the PUSCH, and the OCC sequence applied on the PUSCH, through this information. For example, the first information contains the (high-level) parameterPUSCH-OCClengthListcontaining at least one instance (instance), wherein the at least one instance includes at least one of parameters: the length of the OCC sequence, whether to enable the OCC or not, and the OCC sequence. In one particular implementation, one specific example of thePUSCH-OCClengthListis shown in table 9 below

[0362] Row indexWhether to enable OCC or not and / or OCC sequence1Not enabling OCC2Not enabling OCC, deactivating redundancy version rotation3Sequence 1, e.g., {+1 +1}4Sequence 2, e.g., {+1 -1}5Sequence 3, e.g., {+1 +1 +1 +1}6Sequence 4, e.g., {+1 +1 -1 -1}7Sequence 5, e.g., {+1 -1 -1 +1}8Sequence 6, e.g., {+1 -1 +1 -1}

[0363] In one particular implementation, one specific example of thePUSCH-OCClengthListis shown in table 10 below:

[0364] Row indexWhether to enable OCC or not and / or OCC sequenceLength of OCC sequence1Not enabling OCCDefault2Not enabling OCC, deactivating redundancy version rotationDefault3Sequence 1, e.g., {+1 +1}24Sequence 2, e.g., {+1 -1}25Sequence 3, e.g., {+1 +1 +1 +1}46Sequence 4, e.g., {+1 +1 -1 -1}47Sequence 5, e.g., {+1 -1 -1 +1}48Sequence 6, e.g., {+1 -1 +1 -1}4

[0365] The UE may determine the OCC sequence applied to the PUSCH based on the parameterPUSCH-OCClengthList, according to other information or a rule predefined by the protocol, e.g., obtain the row index based on the DCI, and then, based on the row index and the parameterPUSCH-OCClengthList, determine the OCC applied to the PUSCH sequence, or determine whether to enable the OCC or not, or determine a redundancy version of the transmission occasion applied to the PUSCH.

[0366] According to an embodiment of the present disclosure, information for indicating the OCC sequence includes at least one of:

[0367] information for indicating whether to enable the OCC or not;

[0368] information for indicating the length of the OCC sequence;

[0369] information for indicating the OCC sequence applied to the PUSCH;

[0370] information for indicating the number of OCC groups;

[0371] information for indicating the OCC occasion;

[0372] information for indicating the number of the time units corresponding to the transmission of the PUSCH;

[0373] information for indicating the time unit at which the PUSCH should be transmitted.

[0374] However, the information for indicating the OCC sequence is not limited to the above items. In the followings, each of the above information is described, respectively.

[0375] ●The Information for indicating whether to enable the OCC

[0376] ◆The UE may determine whether or not to apply the OCC sequence on the PUSCH through this information, the particular implementation is the same as the manner as described above for determining whether or not to apply the OCC sequence on the PUSCH based on the information for indicating whether to enable the OCC or not in the information related to the OCC, and it will not be repeated herein.

[0377] ◆Alternatively, in a case where the second information is the downlink control information, the UE may determine whether to apply the OCC sequence on the PUSCH by a value of a domain for indicating whether to enable the OCC in the DCI. In one particular implementation, the DCI includes a domainPUSCH-OCCenable, the OCC is not enabled if the value ofPUSCH-OCCenableis 0, and the OCC is enabled if the value ofPUSCH-OCCenableis 1.

[0378] ●The information for indicating the length of the OCC sequence

[0379] ◆The UE may determine the length of the OCC sequence applied on the PUSCH through this information, the particular implementation is the same as the manner as described above for determining the length of the OCC sequence applied on the PUSCH based on the information for indicating the length of the OCC sequence in the information related to the OCC.

[0380] ◆Alternatively, in the case where the second information is the downlink control information, the UE may determine the length of the OCC sequence applied to the PUSCH by the value of the domain for indicating the length of the OCC sequence in the DCI. In one particular implementation, the DCI includes the domainPUSCH-OCClength, and the length of the OCC sequence applied to the PUSCH is 2 if the value ofPUSCH-OCClengthis 01, the length of the OCC sequence applied to the PUSCH is 4 if the value ofPUSCH-OCClengthis 10, and the length of the OCC sequence applied to the PUSCH is 8 if the value ofPUSCH-OCClengthis 11.

[0381] ◆Alternatively, the UE may determine whether to enable the OCC, and the length of the OCC sequence applied to the PUSCH, by the value of the domain for indicating the length of the OCC in the DCI. In one particular implementation, the DCI includes the domainPUSCH-OCClength, the OCC is not enabled if the value ofPUSCH-OCClengthis 00, the length of the OCC sequence applied to the PUSCH is 2 if the value ofPUSCH-OCClengthis 01, the length of the OCC sequence applied to the PUSCH is 4 if the value ofPUSCH-OCClengthis 10, and the length of the OCC sequence applied to the PUSCH is 8 if the value ofPUSCH-OCClengthis 11.

[0382] ●Information for indicating the OCC sequence applied to the PUSCH

[0383] ◆The UE may determine the OCC sequence applied to the PUSCH through this information, the particular implementation is the same as the manner as described above for determining the OCC sequence applied to the PUSCH based on the information for indicating the OCC sequence applied to the PUSCH in the information related to the OCC.

[0384] ◆Alternatively, in the case where the second information is the downlink control information, the UE may determine the OCC sequence applied to the PUSCH by the value of the domain for indicating the OCC sequence in the DCI. In one particular implementation, the DCI includes the domainPUSCH-OCCsequence, and one table for determining the OCC sequence applied to the PUSCH by the value ofPUSCH-OCCsequenceis shown in table 11 below:

[0385] PUSCH-OCCSequenceOCC sequence applied to PUSCH00Sequence 101Sequence 210Sequence 311Sequence 4

[0386] In one particular implementation, the DCI includes a domainPUSCH-OCCSequenceassignmentthat provides one row index, the UE determines the OCC sequence for the PUSCH based on the row index and other information (e.g., a table related to the OCC). Wherein, the table related to the OCC may be a table containing row indexes as enumerated in the present disclosure.

[0387] ●The information for indicating the number of the OCC groups

[0388] ◆The UE may determine the OCC sequence applied to the PUSCH through this information, the particular implementation is the same as the manner as described above for determining the OCC sequence applied to the PUSCH based on the information for indicating the OCC sequence applied to the PUSCH in the information related to the OCC.

[0389] ●The Information for indicating the OCC occasion (also known as “OCC window”)

[0390] ◆The UE may determine the time unit corresponding to the OCC occasion through this information, the particular implementation is the same as the manner as described above for determining the time unit corresponding to the OCC occasion based on the information for indicating the OCC occasion in the information related to the OCC.

[0391] ◆Alternatively, in the case where the second information is the downlink control information, the UE may determine the information related to the OCC occasion by a value of a domain related to the OCC occasion (OCC window) in the DCI. For example, the DCI contains the domain related to the OCC occasion that indicates a location of a starting time unit for a next available OCC occasion. As another example, the DCI contains the domain related to the OCC occasion that indicates an offset between a time unit at which the DCI is located and the starting time unit of the OCC occasion. In one particular implementation, the DCI contains the domain related to the OCC occasion, a physical meaning denoted by the value of the domain related to the OCC occasion indicates an index of the time unit at which the next available OCC occasion is located, e.g., an index of a slot at which the next next available OCC occasion is located, for example, an index of a slot at which the next available OCC occasion is located. The index of the slot at which the next available OCC occasion is located is 0 if the value of the domain related to the OCC occasion is 0000, and the index of the slot at which the next available OCC occasion is located is 1 if the value of the domain related to the OCC occasion is 0001. In one particular implementation, the DCI contains the domain related to the OCC occasion, a physical meaning denoted by the value of the domain related to the OCC occasion indicates an offset between the time unit at which the DCI is located and the starting time unit of the OCC occasion, e.g., an offset between the slot at which the DCI is located and a starting slot of the OCC occasion. The offset between the slot at which the DCI is located and the starting slot of the OCC occasion is 0 slot if the value of the domain related to the OCC occasion is 000, the offset between the slot at which the DCI is located and the starting slot of the OCC occasion is 1 slot if the value of the domain related to the OCC occasion is 001, and the offset between the slot at which the DCI is located and the starting slot of the OCC occasion is -1 slot if the value of the domain related to the OCC occasion is 010. Wherein the offset being equal to zero indicates that the slot at which the DCI is located and the starting slot of the OCC occasion are the same slot. The offset being greater than zero (e.g., being k, wherein k is an integer greater than zero) indicates that the slot at which the DCI is located is a k-th slot subsequent to the starting slot of the OCC occasion, i.e., the slot at which the DCI is located is a n-th slot and then the starting slot of the OCC occasion is a (n+k)-th slot. The offset being less than zero (e.g., being k, wherein k is an integer greater than zero) indicates that the slot at which the DCI is located is the k-th slot prior to the starting slot of the OCC occasion, i.e., if the slot at which the DCI is located is the n-th slot, then the starting slot of the OCC occasion is a (n-k)-th slot. In one particular implementation, the DCI contains the domain related to the OCC occasion, and a physical meaning denoted by the value of the domain related to the OCC occasion indicates an offset between the time unit at which the DCI is located and the starting time unit of the OCC occasion, wherein a granularity of the offset may be a slot, a symbol, or the number of slots corresponding to the length of the OCC sequence, or the number of symbols corresponding to the length of the OCC sequence , or a product of a slot and the number of slots corresponding to the length of the OCC sequence, or a product of a symbol and the number of symbols corresponding to the length of the OCC sequence.

[0392] ◆In one particular implementation, the DCI contains aTime domain resource assignment(referred to as TDRA) domain which is a domain related to time-domain resource assignment, a value of theTime domain resource assignmentdomain indicates information of the OCC occasion, e.g., the value of theTime domain resource assignmentdomain indicating a slot offset K2 which denotes the offset between the slot at which the DCI is located and the starting slot of the OCC occasion. In one particular implementation, K2 takes a value of k, then the starting slot of the OCC occasion is k slots subsequent to the slot at which the DCI is located, e.g., the slot at which the DCI is located is the n-th slot and then the starting slot of the OCC occasion is the (n+k)-th slot. In one particular implementation, K2 takes the value of k, the starting slot of the OCC occasion is kP slots subsequent to the slot at which the DCI is located, e.g., the slot at which the DCI is located is the n-th slot and then the starting slot of the OCC occasion is the (n+kP)-th slot, wherein P is a length of one OCC sequence, e.g., if the OCC sequence is , the length of the OCC sequence is P.

[0393] ●The information for indicating the number of the time units corresponding to the transmission of the PUSCH

[0394] ◆The UE may determine the number of time units corresponding to the transmission of the PUSCH based on this information, for example, the number of slots corresponding to the transmission of the PUSCH. In one particular implementation, the UE determines that P slots are used for the transmission of the PUSCH, wherein P denotes the length of the OCC sequence applied to the PUSCH.

[0395] ◆Alternatively, if the UE is configured for a parameter related to the repetition and / or a parameter related to TBoMS (Transport Block processing over multiple slots), the number of the time units corresponding to the transmission of the PUSCH is determined based on the parameter related to the repetition and / or parameter related to the TBoMS as well as the information for indicating the number of the time units corresponding to the transmission of the PUSCH. In one particular implementation, the UE determines that KP slots are used for the transmission of the PUSCH, wherein K denotes the number of times of the repetition and P denotes the length of the OCC sequence applied to the PUSCH. In one particular implementation, the UE determines NKP slots are used for the transmission of the PUSCH, wherein N denotes the number of slots for determining a transmission block size, K denotes the number of times of the repetition, and P denotes the length of the OCC sequence applied to the PUSCH. In one particular implementation, the UE determines NP slots are used for the transmission of the PUSCH, wherein N denotes the number of slots for determining a transmission block size, P denotes the length of the OCC sequence applied to the PUSCH.

[0396] ●The information for indicating the time unit at which the PUSCH should be transmitted

[0397] ◆The UE may determine, based on this information, the time unit at which the PUSCH should be transmitted, e.g., a slot at which the PUSCH should be transmitted. Alternatively, the UE may determine the starting location of the OCC occasion based on this information of the time unit at which the PUSCH should be transmitted.

[0398] ◆Alternatively, the second information may be the downlink control information. The DCI may contain the domain related to the time-domain resource assignment. The information for indicating the time unit at which a PUSCH should be transmitted may be a value of the domain related to the time-domain resource assignment. The time unit at which the PUSCH should be transmitted may be determined based on the value of the domain related to the time-domain resource assignment and the information related to the OCC in the DCI. According to an embodiment, the value of the domain related to the time-domain resource assignment may indicate a time unit offset between the PUSCH and the DCI, wherein the time unit offset may be determined based on a resource assignment table, the information related to the OCC, and / or information for indicating the OCC sequence. For example, the information related to the OCC may be the length of the OCC sequence applied to the PUSCH. In one particular implementation, the DCI containsTime domain resource assignmentthat is the domain related to the time-domain resource assignment, the value ofTime domain resource assignmentdomain indicates a time unit offset K2, and if the time unit takes a slot as an example, then a slot Ks at which the UE should transmit the PUSCH is determined based on K2. If OCC is configured for the UE, then , wherein n denotes a slot at which the downlink control information is located, and denotes a subcarrier interval type (numerology) of the PUSCH, and denotes a subcarrier interval type (numerology) of the PDCCH, and P is the length of the OCC sequence applied to the PUSCH. According to an embodiment, the resource assignment table may include a time unit offset K2, or may include K2 and the parameter related to the length of the OCC sequence. Alternatively, the UE may determine the starting location of the OCC occasion based on the information of the time unit at which the PUSCH should be transmitted, e.g., the slot Ks determined in the above method is a starting slot of the OCC occasion. In one particular implementation, the DCI containsTime domain resource assignmentthat is the domain related to the time-domain resource assignment, the value ofTime domain resource assignmentdomain indicates a time unit offset K2, and if the time unit take a slot as an example, then a slot Ks at which the UE should transmit the PUSCH is determined based on K2. If the OCC is configured for the UE, the determination of K2 may be related to the parameter related to the OCC. In one implementation, the time unit offset K2 may be defined based on the length of the OCC sequence. For example, a rule predefined by the protocol indicates that the value of K2 is related to the OCC parameter, K2=jP, wherein P denotes the length of the OCC sequence applied to the PUSCH, and j is determined by the rule predefined by the protocol, e.g., when or , j takes the value of 1, and when , j takes the value of 2.

[0399] ◆Alternatively, the second information may be the downlink control information. The DCI contains a domain related to the time-domain resource assignment. The time unit at which the PUSCH should be transmitted may be determined based on the value of the domain related to the time-domain resource assignment, and the information related to the OCC. Wherein the information related to the OCC may be information related to the OCC occasion, for example, a time unit corresponding to the start of the OCC occasion (also referred to as “starting time unit of the OCC occasion”), for example, a slot corresponding to the start of the OCC occasion. According to an embodiment, the second information may be a DCI from the second communication node, and the method performed by the first communication node further includes: when it is determined, based on the information for indicating the OCC sequence included in the DCI, that a starting time unit which is indicated for the transmission of the PUSCH is different from a starting time unit of the OCC occasion, the first communication node ignores scheduling of the PUSCH by the second communication node, or, the first communication node determines a starting time unit at which the PUSCH should be transmitted based on the starting time unit which is indicated for the transmission of the PUSCH and a parameter related to the OCC occasion. In one particular implementation, the information for indicating the OCC sequence may be information for indicating the time unit at which the PUSCH should be transmitted, and the information for indicating the time unit at which the PUSCH should be transmitted may be the value of Time domain resource assignment included in the DCI that is the domain related to the time-domain resource assignment, this value may indicate a time unit offset K2. For example, if the time unit takes a slot as an example, a slot Kd at which the UE should transmit the PUSCH is determined based on K2 and the parameter related to the OCC occasion. In one particular implementation, n denotes a slot at which the downlink control information is located, and the UE determines the slot Ks (Ks is a time unit indicating the start of the transmission of the PUSCH) based on n and K2. The UE ignores this scheduling if the slot Ks is different from the slot corresponding to the start of the OCC occasion. In one particular implementation, n denotes a slot at which the downlink control information is located, the UE determines the slot Ks based on n and K2. If the slot Ks and the slot corresponding to the start of the OCC occasion are different, the UE determines the slot Kd at which the PUSCH should be transmitted based on Ks and the parameter related to the OCC occasion, e.g., the slot Kd is a slot at which the starting location of a next available OCC occasion is located. In one particular implementation, n denotes the slot at which the downlink control information is located, and the UE determines the slot Ks based on n and K2. If the slot Ks and the slot corresponding to the start of the OCC occasion are different: if a value ofOCC-allowearlytransmissiondomain in the DCI is a first value (e.g., 1), the UE determines the slot Kd at which the PUSCH should be transmitted based on the Ks and the parameter related to the OCC occasion, e.g., the slot Kd is a slot at which the starting location of the next available OCC occasion is located, and if the value ofOCC-allowearlytransmissiondomain in the DCI is a second value (e.g., 0), the UE ignores this scheduling. In one particular implementation, n denotes the slot at which the downlink control information is located, the UE determines the slot Ks based on n and K2. If the slot Ks and the slot corresponding to the start of the OCC occasion are different: if the value ofOCC-allowearlytransmissionfield in the DCI is the first value (e.g., 1), the UE determines the slot Kd at which the PUSCH should be transmitted based on the Ks and the parameter related to the OCC occasion, e.g., the slot Kd is a slot between the starting location of the next available OCC occasion and the slot Ks, and if the value ofOCC-allowearlytransmissiondomain in the DCI is the second value (e.g., 0), the UE ignores this scheduling, or the slot Kd is the slot at which the next available OCC occasion is located. Alternatively, the UE determines a OCC sequence applied to a first OCC group (i.e., the PUSCH transmitted in the first OCC occasion occupied by the PUSCH) based on the OCC sequence or a rule predefined by the protocol. For example, if the slot Ks is a slot 5 and the slot corresponding to the start of the next available OCC occasion is a slot 8, i.e., the slot corresponding to the slot Ks and the start of the OCC occasion are different, and if the value ofOCC-allowearlytransmissiondomain in the DCI is the first value (e.g., 1), the UE determines the slot Kd at which the PUSCH should be transmitted is a slot 6, the OCC sequence with the length of 4 is configured for the UE, and the UE determines the OCC sequence applied to the first OCC group (i.e., the PUSCH transmitted in the first OCC occasion occupied by the PUSCH), e.g., based on the OCC sequence.

[0400] Exemplary illustrations of the information related to the OCC and information for indicating the OCC sequence have been made above, however, neither the information related to the OCC nor the information for indicating the OCC sequence is limited to the illustrated examples.

[0401] Alternatively, according to an embodiment, the method shown in FIG. 4 may further include: determining the physical resources for the transmission of the PUSCH based on the information related to the OCC and / or the information for indicating the OCC sequence, wherein the physical resources include at least one of time-domain resources, frequency-domain resources and code-domain resources.

[0402] Alternatively, According to an embodiment, the determining the physical resources for the transmission of the PUSCH includes: determining the code-domain resources, based on the information related to the OCC and / or the information for indicating the OCC sequence, or based on the information related to the OCC and / or the information for indicating the OCC sequence as well as a rule predefined by the protocol, wherein the code-domain resources include the OCC sequence applied to the PUSCH, the OCC sequence is used to perform time-domain extension and / or frequency-domain extension on the PUSCH. According to an embodiment, based on the determined OCC sequence, the time-domain extension and / or frequency-domain extension may be performed on the PUSCH, and thus the time-domain resources and / or frequency-domain resource for the transmission of the PUSCH may also be determined. For example, the PUSCH may be extended by applying one OCC sequence W=[w(0) w(1)…w(L-1)] having a sequence length of L to the transmission of the PUSCH.

[0403] The applying of one OCC sequence W=[w(0) w(1)…w(L-1)] having the sequence length of L to the transmission of the PUSCH may be understood as extending one transmission of the PUSCH into L spreadings of the PUSCH (or repetition transmission or OCC-based repetition transmission), wherein a modulation symbol (or a modulation symbol sequence) carried by each of the L spreadings of the PUSCH may be a modulation symbol (or a modulation symbol sequence) carried by the transmission of the PUSCH multiplied by an element in the corresponding OCC sequence. For example, a modulation symbol (or a modulation symbol sequence) carried by a first spreading of the PUSCH is a modulation symbol (or a modulation symbol sequence) carried by the transmission of the PUSCH multiplied by w(0), ... , a modulation symbol (or a modulation symbol sequence) carried by an L-th spreading of the PUSCH is a modulation symbol (or a modulation symbol sequence) carried by the transmission of the PUSCH multiplied by w(L-1).

[0404] Wherein the length L of the OCC sequence may be determined by a high-level parameter. For example, if a high-level parameterocc-Lengthis configured, the length L of the OCC sequence is determined by the high-level parameterocc-Length. In one particular implementation, if the high-level parameterocc-Lengthis configured, the length of the OCC sequence is given by the high-level parameterocc-Length.

[0405] Wherein the OCC sequence W may be determined by a high-level parameter, e.g., a value of n is determined based on a high-level parameterocc-Index, and a correspondence between n and the OCC sequence may be given in a table 12, for example, one example of a table of the orthogonal sequence when L=2 is:

[0406] n 0[+1 +1]1[+1 -1]

[0407] As another example, one example of a table 13 of the orthogonal sequence when L=4 is:

[0408] n 0[+1 +1 +1 +1]1[+1 -1 +1 -1]3[+1 +1 -1 -1]4[+1 -1 -1 +1]

[0409] According to an embodiment, the rules predefined by the protocol mentioned above may include at least one of:

[0410] a rule for determining whether to enable the OCC or not;

[0411] a rule for determining the length of the OCC sequence;

[0412] a rule for determining the OCC sequence applied to the PUSCH;

[0413] a rule for determining the OCC occasion;

[0414] a rule for determining the number of the PUSCH transmission occasions corresponding to the transmission block (TB);

[0415] a rule for determining the starting time unit for the initial transmission of the TB;

[0416] a rule for determining the number of the time units corresponding to the transmission of the PUSCH;

[0417] a rule for determining the time unit at which the PUSCH should be transmitted.

[0418] For example, the rule predefined by the protocol may be any one table illustrated above which illustrate the above relationships.

[0419] For example, the rule predefined by the protocol may be the rule for determining the length of the OCC sequence, this rule may be, for example, a relationship between a row index and the length of the OCC sequence, and the UE determines the length of the OCC sequence based on the relationship, and the row index provided in the DCI or RRC configuration information. In one particular implementation, the relationship between the row index predefined by the protocol and the length of the OCC sequence may be as shown in the following table 14:

[0420] Row indexLength of OCC sequence122438

[0421] For example, the rule predefined by the protocol may be the rule for determining the OCC sequence applied to the PUSCH, for example, the rule may be a relationship between a row index and the OCC sequence, and the UE determines the OCC sequence based on the relationship, and the row index provided by the DCI or in the RRC configuration information. An example of the relationship between the row index and the OCC sequence is shown in the present disclosure in a form of a table or text in one or more implementations and will not be repeated here.

[0422] Alternatively, According to an embodiment, the determining of the physical resources for the transmission of the PUSCH may include: determining the time-domain resources for transmitting the PUSCH based on the number of time units corresponding to the transmission of the PUSCH and a time unit at which the PUSCH should be transmitted, wherein the number of the time units corresponding to the transmission of the PUSCH and the time unit at which the PUSCH should be transmitted are determined based on the information related to the OCC and / or the information for indicating the OCC sequence; or if a parameter related to repetition of the PUSCH and / or a parameter related to transmission block processing over multiple slots (TBoMS) is configured for the first communication node, determining the time-domain resources for transmitting the PUSCH, based on the parameter related to the repetition of the PUSCH and / or the parameter related to the TBoMS, as well as the information related to the OCC and / or information for indicating the OCC sequence.

[0423] Alternatively, According to an embodiment, the determining of the physical resources for the transmission of the PUSCH may include: if a parameter related to frequency hopping is configured for the first communication node, determining the frequency-domain resources for the transmission of the PUSCH based on the parameter related to the frequency hopping, as well as the information related to the OCC and / or the information for indicating the OCC sequence.

[0424] In one particular implementation, if a high-level parameterOCC-enableis configured for the UE and PUSCH frequency hopping (e.g., inter-slot frequency hopping) is configured for the UE, a starting resource block (RB) for each frequency hopping may be denoted as:

[0425]

[0426] Wherein denotes the number of RBs applied to the frequency hopping, denotes a starting RB in a uplink BWP, may be indicated by the DCI that schedules the PUSCH or the RRC information for configuring uplink grant-free transmission, denotes the number of RBs in the uplink BWP, andi denotes a (i+1)-th frequency hopping. The number of time units corresponding to the i-th frequency hopping is L, wherein L may be a length predefined by the protocol, e.g., 2 or 4, and L may also be determined based on a high-level parameter, e.g., based on a high-level parameter indicating the length of the OCC sequence, e.g., equal to a value of the high-level parameter indicating the length of the OCC sequence.

[0427] According to an embodiment, alternatively, the first information and / or the second information may further include information for indicating a redundancy bersion (RV) applied to a n-th PUSCH transmission occasion, and the method shown in FIG. 4 may further include: determining the redundancy version to be applied to the n-th PUSCH transmission occasion based on the information for indicating the redundancy version to be applied to the n-th PUSCH transmission occasion, wherein n includes an integer greater than or equal to zero. According to an embodiment, the redundancy version to be applied to the n-th transmission occasion is a RV that is applied to the transmission occasion having an index of n in the transmission of the PUSCH, which may be understood as a RV that is applied to the transmission occasion having an index of n in a transmission block (TB), wherein the TB is the TB corresponding to the transmission of the PUSCH.

[0428] In the followings, the information for indicating the redundancy version to be applied to the n-th PUSCH transmission occasion and a manner of determining the redundancy version to be applied to the n-th PUSCH transmission occasion based on this information are described in connection with examples. The UE may determine the redundancy version to be applied to the n-th PUSCH transmission occasion thorugh this information, for example, the first information contains a (high-level) parameterPUSCH-OCCRV, as the information for indicating the redundancy version to be applied to the n-th PUSCH transmission occasion. In one particular implementation, a value of the parameterPUSCH-OCCRVmay be 0, 1, 2, 3. If the value of the parameterPUSCH-OCCRVis 0, the redundancy version to be applied to the n-th PUSCH transmission occasion is RV0, and if the value of the parameterPUSCH-OCCRVis 1, the redundancy version to be applied to the n-th PUSCH transmission occasion is RV1. Wherein n is an integer between 0 and N-1 and N is the number of the transmission occasions of the PUSCH corresponding to the TB. In one particular implementation method, the value of the parameterPUSCH-OCCRVmay be , wherein denotes a corresponding redundancy version to be applied to a (n+1)-th transmission occasion the PUSCH, and may take a value of 0, 1, 2, 3. In one particular implementation method, the value of the parameterPUSCH-OCCRVmay be , wherein denotes a redundancy version corresponding to transmission occasions of the PUSCH corresponding to a (n+1)-th OCC group, wherein n is an integer between 0 and N-1, may take a value of 0, 1, 2, 3, and M denotes the number of OCC groups corresponding to all of transmission occasions of the PUSCH corresponding to the TB, P=N / M denotes the number of transmission occasions of the PUSCH corresponding to one OCC group. For example, in a case where N=4 and P=2, the value ofPUSCH-OCCRVmay be , wherein denotes a redundancy version corresponding to transmission occasions of the PUSCH corresponding to a first OCC group, i.e., a redundancy version corresponding to the first and second transmission occasions of the PUSCH, and denotes a redundancy version corresponding to transmission occasions of the PUSCH corresponding to a second OCC group, i.e., a redundancy version corresponding to the third and fourth transmission occasions of the PUSCH. Alternatively, M may also be smaller than the number of the OCC groups corresponding to all of transmission occasions of the PUSCH corresponding to TB. For example, in a case where N=8 and P=2, the value ofPUSCH-OCCRVmay be , wherein denotes a redundancy version corresponding to transmission occasions of the PUSCH corresponding to the first OCC group and the third OCC group, denotes a redundancy version corresponding to transmission occasions of the PUSCH corresponding to the second OCC group and the fourth OCC group.

[0429] Alternatively, the first information may also contain a (high-level) parameterPUSCH-OCCRVListas information for indicating the redundancy version to be applied to the n-th PUSCH transmission occasion.The UE may determine a candidate set of the redundancy version to be applied to the n-th PUSCH transmission occasion through this information, and the UE may determine the redundancy version to be applied to the n-th PUSCH transmission occasion, based on the parameterPUSCH-OCCRVList, according to other information or on rule predefined by the protocol. In one particular implementation, thePUSCH-OCCRVListmay be given in the form of a table, and the UE determines a row index based on other information or rule predefined by the protocol, determines a redundancy version to be applied to the n-th PUSCH transmission occasion based on the row index and thePUSCH-OCCRVList, wherein n is between 0 and an N-1 integer. An example of thePUSCH-OCCRVListmay be in table 15:

[0430] Row indexRedundancy version set applied to PUSCH transmission occasions1 2 ……

[0431] The process for determining the redundancy version to be applied to the n-th PUSCH transmission occasion based on or is given in the above implementation and will not be repeated here.

[0432] Alternatively, in the case where the second information is the downlink control information, the UE may determine information of the redundancy version to be applied to the n-th PUSCH transmission occasion based on a value of aRedundancy versiondomain in the DCI. For example, the UE determines the redundancy version to be applied to the n-th PUSCH transmission occasion based on a rule predefined by the protocol, and the parameter related to the OCC, and the value of theRedundancy versiondomain in the DCI. Wherein, a physical meaning of the value of theRedundancy versiondomain in the DCI is a redundancy version indicated by the DCI scheduling the PUSCH. In one particular implementation, the redundancy version to be applied to the n-th transmission occasion of the TB is determined according to a table, one example of the table 16 may be:

[0433] Redundancy version indicated by DCI scheduling PUSCHRedundancy version to be applied to n-th PUSCH transmission occasion((n-(n mod P)) / P)mod 4 = 0((n-(n mod P)) / P)mod 4 = 1((n-(n mod P)) / P)mod 4 = 2((n-(n mod P)) / P)mod 4 = 300231223103310211023

[0434] Wherein, P denotes the length of the OCC sequence applied to the PUSCH corresponding to the TB, or the number of transmission occasions of the PUSCH corresponding to ONE OCC group, n denotes an integer between 0 and N, and N is the number of all of transmission occasions of the PUSCH corresponding to the TB.

[0435] Alternatively, According to an embodiment, the method shown in FIG. 4 may further include: transmitting capability information to the second communication node, wherein the capability information indicates whether the first communication node supports applying the OCC sequence to the transmission of the PUSCH or not

[0436] For example, in some implementations, the UE may report the capability information (e.g., a parameterUEcapabilityOCC) to the base station, the capability information indicates whether the UE supports applying the OCC sequence to the transmission of the PUSCH or not.

[0437] Alternatively, the method shown in FIG. 4 may also include the steps included in the method shown in FIG. 5, which will be described below, and the relevant description with respect to FIG. 5 may likewise apply to the method shown in FIG. 4.

[0438] Above, the method performed by a first communication node according to the embodiment of the present disclosure has been described in connection with FIG. 4 and examples, and according to the above method, it is possible to facilitate to flexibly apply the OCC to the PUSCH, so that different communication nodes transmit the PUSCH on the same time-frequency resources, thereby improving the spectral efficiency and reducing the transmission delay. In addition, according to the above method, redundancy versions applied to different transmission occasions can be flexibly transmitted at different transmission occasions of the PUSCH. FIG. 5 is a flowchart illustrating a method performed by a first communication node according to an embodiment of the present disclosure.

[0439] Referring to FIG. 5, at step S510, third information that configures or schedules transmission of a physical uplink shared channel (PUSCH) in K time units is received or detected, wherein the K is an integer greater than 1. At step S520, fourth information that is redundancy version repetition related information is received. At step S530, the PUSCH is transmitted based on the third information and the fourth information, wherein a redundancy version to be applied to a n-th transmission occasion in the transmission of the PUSCH is the redundancy version configured or indicated by the third information, or the redundancy version to be applied to the n-th transmission occasion in the transmission of the PUSCH is determined based on the redundancy version indicated by the third information, and the fourth information, wherein the n is an integer between 0 and K-1. Or, the n is an integer between 1 and K. It is noted that, in the present disclosure, there is no limitation on a reception order of the third information and the fourth information, the first node may receive the third information firstly and then receive the fourth information, or it may receive information containing both the third information and the fourth information, and it may receive the fourth information firstly and then receive the third information.

[0440] According to an embodiment, the fourth information may include at least one of:

[0441] - activating that all of the redundancy versions of the repetition transmission of the PUSCH are the redundancy versions configured or indicated by the third information;

[0442] - deactivating use of different redundancy versions in the repetition transmission of the PUSCH;

[0443] - deactivating redundancy version rotation;

[0444] - redundancy version repetition;

[0445] - activating redundancy version repetition;

[0446] - repetition number of the redundancy version;

[0447] - not activating that all of redundancy versions of repetition transmission of the PUSCH are the redundancy versions configured or indicated by the third information;

[0448] - deactivating that all of the redundancy versions of the repetition transmission of the PUSCH are the redundancy versions configured or indicated by the third information;

[0449] - not deactivating use of different redundancy versions in the repetition transmission of the PUSCH;

[0450] - activating the use of different redundancy versions in the repetition transmission of the PUSCH;

[0451] - the use of different redundancy versions in the repetition transmission of the PUSCH;

[0452] - not deactivating redundancy version rotation;

[0453] - activating the redundancy version rotation;

[0454] - the redundancy version rotation;

[0455] - not activating redundancy version repetition;

[0456] - deactivating the redundancy version repetition

[0457] - an orthogonal Coverage Code (OCC);

[0458] - a length of the orthogonal coverage code (OCC);

[0459] - the number of PUSCH transmission occasions included in a PUSCH transmission occasion group;

[0460] - the number of PUSCH transmission occasion groups;

[0461] In some implementations, the fourth information indicates at least one of:

[0462] - a used redundancy version being the redundancy version indicated by the third information;

[0463] - whether the used redundancy version is the redundancy version indicated by the third information;

[0464] - enabling the redundancy version repetition;

[0465] - enabling the deactivation of the redundancy version rotation;

[0466] - whether to enable the redundancy version repetition;

[0467] - whether to enable the deactivation of redundancy version rotation;

[0468] - the number of times of the repetition of the redundancy version.

[0469] When the fourth information includes at least one of the above, the redundancy version to be applied to the n-th transmission occasion in the transmission of the PUSCH is the redundancy version configured or indicated by the third information, or the redundancy version to be applied to the n-th transmission occasion in the transmission of the PUSCH may be determined based on the redundancy version indicated by the third information, and the fourth information. For example, when the fourth information indicates the repetition number of the redundancy version, the redundancy version to be applied to the n-th transmission occasion in the transmission of the PUSCH may be determined based on the redundancy version indicated by the third information, and the fourth information. As another example, when the fourth information indicates at least one of: the used redundancy version being the redundancy version indicated by the third information, whether the used redundancy version being the redundancy version indicated by the third information, enabling the redundancy version repetition, enabling the deactivation of the redundancy version rotation, whether to enable the redundancy version repetition, whether to enable the deactivation of redundancy version rotation, then the redundancy version to be applied to the n-th transmission occasion in the transmission of the PUSCH may be the redundancy version indicated by the third information. Alternatively, the redundancy version to be applied to the n-th transmission occasion in the transmission of the PUSCH being determined based on the redundancy version indicated by the third information, and the fourth information, may include: the redundancy version to be applied to the n-th transmission occasion in the transmission of the PUSCH is determined based on the redundancy version indicated by the third information and the repetition number of the redundancy version indicated by the fourth information as well as the n.

[0470] Alternatively, in some implementations, the fourth information may indicate at least one of:

[0471] the Orthogonal Coverage Code (OCC);

[0472] the length of the Orthogonal Coverage Code (OCC);

[0473] the number of the PUSCH transmission occasions contained in the PUSCH transmission occasion group, the number of the PUSCH transmission occasion groups, and / or an index of the transmission occasion group at which the n-th transmission occasion is located, wherein the spreading is grouped into one or more PUSCH transmission occasion groups.

[0474] According to an embodiment, the method shown in FIG. 5 may be applicable both in the case where a spreading based on an orthogonal code is configured or indicated for the PUSCH, and in the case where the spreading based on the orthogonal code is not configured or indicated for the PUSCH.

[0475] Alternatively, when the spreading based on the orthogonal code is configured or indicated for the PUSCH, the redundancy version to be applied to the n-th transmission occasion in the transmission of the PUSCH is determined based on the redundancy version indicated by the third information and a parameter related to the orthogonal code; or the redundancy version to be applied to the n-th transmission occasion in the transmission of the PUSCH is the redundancy version configured or indicated by the third information; or the redundancy version to be applied to the n-th transmission occasion in the transmission of the PUSCH is determined based on the redundancy version indicated by the third information, and the fourth information.

[0476] As an example, the redundancy version to be applied to the n-th transmission occasion in the transmission of the PUSCH being determined based on the redundancy version indicated by the third information and the parameter related to the orthogonal code, includes: the redundancy version to be applied to the n-th transmission occasion in the transmission of the PUSCH is determined based on the redundancy version indicated by the third information, and the orthogonal code or the length of the orthogonal code.

[0477] As another example, the redundancy version to be applied to the n-th transmission occasion in the transmission of the PUSCH being determined based on the redundancy version indicated by the third information and the parameter related to the orthogonal code, includes: the redundancy version to be applied to the n-th transmission occasion in the transmission of the PUSCH is determined based on the redundancy version indicated by the third information and the information indicating the number of repetitions of the redundancy version among information for configuring the spreading.

[0478] According to an embodiment, the orthogonal code may include an orthogonal coverage code (OCC).

[0479] According to an embodiment, when the spreading is configured or indicated for the PUSCH, the fourth information may indicate at least one of: the orthogonal coverage code (OCC); the length of the orthogonal coverage code (OCC).

[0480] Further, when the spreading is grouped into one or more PUSCH transmission occasion groups, the fourth information indicates at least one of: the number of PUSCH transmission occasions contained in the PUSCH transmission occasion group; the number of the PUSCH transmission occasion groups. In this case, the redundancy version to be applied to the n-th transmission occasion in the transmission of the PUSCH being determined based on the redundancy version indicated by the third information, and the fourth information, includes: the redundancy version to be applied to the n-th transmission occasion in the transmission of the PUSCH is determined based on the redundancy version indicated by the third information, as well as the number of the PUSCH transmission occasions contained in the PUSCH transmission occasion group or the number of the PUSCH transmission occasion groups. In some implementations, the fourth information indicates at least one of:

[0481] - not activating that all of redundancy versions of repetition transmission of the PUSCH are the redundancy versions configured or indicated by the third information;

[0482] - deactivating that all of the redundancy versions of the repetition transmission of the PUSCH are the redundancy versions configured or indicated by the third information;

[0483] - not deactivating use of different redundancy versions in the repetition transmission of the PUSCH;

[0484] - activating the use of different redundancy versions in the repetition transmission of the PUSCH;

[0485] - the use of different redundancy versions in the repetition transmission of the PUSCH;

[0486] - not deactivating the redundancy version rotation;

[0487] - activating the redundancy version rotation;

[0488] - the redundancy the version rotation;

[0489] - not activating the redundancy version repetition;

[0490] - deactivating the redundancy version repetition

[0491] In this case, the redundancy version to be applied to the n-th transmission occasion in the transmission of the PUSCH being determined based on the redundancy version indicated by the third information, and the fourth information, includes: the redundancy version to be applied to the n-th transmission occasion in the transmission of the PUSCH is determined based on the redundancy version indicated by the third information as well as the n. That is, since the fourth information indicates at least one of the above items, the first communication node may determine the redundancy version to be applied to the n-th transmission occasion in the transmission of the PUSCH based on the redundancy version indicated by the third information as well as n. For example, if the first communication node receives the fourth information, the fourth information includes whether to activate that all of redundancy versions of repetition transmission of the PUSCH are the redundancy versions configured or indicated by the third information, and the fourth information takes a value ofdisable, it donates that the fourth information indicates that it is not activated (or is deactivated) that all of redundancy versions of repetition transmission of the PUSCH are the redundancy versions configured or indicated by the third information, then the UE determines, based on the information indicated by the value of the fourth information, that it is not activated (or is deactivated) that all of redundancy versions of repetition transmission of the PUSCH are the redundancy versions configured or indicated by the third information. A method for determining the redundancy version to be applied to the n-th transmission occasion in the transmission of the PUSCH by the UE may be determining the redundancy version to be applied to the n-th transmission occasion in the transmission of the PUSCH based on the redundancy version indicated by the third information as well as n.

[0492] In some implementations, when the spreading based on the orthogonal code is configured or indicated for the PUSCH, the fourth information may not be configured.

[0493] In some implementations, when the spreading based on the orthogonal code is configured or indicated for the PUSCH, and when the fourth information is configured or the fourth information indicates a first value, the method further includes determining the number of times of the repetition of the redundancy version based on the orthogonal code or code length. For example, the fourth information indicates that the used redundancy version is the redundancy version indicated by the third information, and when the fourth information is configured, the number of times of the repetition of the redundancy version is determined based on the orthogonal code or the code length, e.g., equal to the code length of the orthogonal code. As another example, the fourth information indicates whether the used redundancy version is the redundancy version indicated by the third information, and when the fourth information indicatesenableor 1, the number of times of the repetition of the redundancy version is determined based on the orthogonal code or the code length, e.g., equal to the code length of the orthogonal code. As another example, the fourth information indicates enabling the redundancy version repetition or enabling the deactivation of the redundancy version rotation, and when the fourth information is configured, the number of times of the repetition of the redundancy version is determined based on the orthogonal code or code length, e.g., equal to the code length of the orthogonal code. As another example, the fourth information indicates whether to enable the redundancy version repetition or whether to enable the deactivation of the redundancy version rotation, and when the fourth information indicatesenableor 1, the number of times of the repetition of the redundancy version is determined based on the orthogonal code or code length, e.g., equal to the code length of the orthogonal code.

[0494] In some implementations, when the spreading based on the orthogonal code is configured or indicated for the PUSCH, and when the fourth information is configured or the fourth information indicates a first value, the method further includes determining the number of times of the repetition of the redundancy version to be K. For example, the fourth information indicates that the used redundancy version is the redundancy version indicated by the third information, and when the fourth information is configured, the number of times of the repetition of the redundancy version is determined to be K. As another example, the fourth information indicates whether the used redundancy version is the redundancy version indicated by the third information, and when the fourth information indicatesenableor 1, the number of times of the repetition of the redundancy version is determined to be K. As another example, the fourth information indicates enabling the redundancy version repetition or enabling the deactivation of the redundancy version rotation, and when the fourth information is configured, the number of times of the repetition of the redundancy version is determined to be K. As another example, the fourth information indicates whether to enable the redundancy version repetition or whether to enable the deactivation of the redundancy version rotation, and when the fourth information indicatesenableor 1, the number of times of the repetition of the redundancy version is determined to be K.

[0495] In some implementations, when the spreading based on the orthogonal code is not configured or indicated for the PUSCH, and when the fourth information is configured or the fourth information indicates a first value, the method further includes determining the number of times of the repetition of the redundancy version to be K. For example, the fourth information indicates that the used redundancy version is the redundancy version indicated by the third information, and when the fourth information is configured, the number of times of the repetition of the redundancy version is determined to be K. As another example, the fourth information indicates whether the used redundancy version is the redundancy version indicated by the third information, and when the fourth information indicatesenableor 1, the number of times of the repetition of the redundancy version is determined to be K. As another example, the fourth information indicates enabling the redundancy version repetition or enabling the deactivation of the redundancy version rotation, and when the fourth information is configured, the number of times of the repetition of the redundancy version is determined to be K. As another example, the fourth information indicates whether to enable the redundancy version repetition or whether to enable the deactivation of the redundancy version rotation, and when the fourth information indicatesenableor 1, the number of times of the repetition of the redundancy version is determined to be K.

[0496] In some implementations, when the fourth information indicates whether the used redundancy version is the redundancy version indicated by the third information, or when the fourth information indicates whether to enable the redundancy version repetition or whether to enable the deactivation of the redundancy version rotation, the method further includes that: when the third information indicates a first value, the redundancy version to be applied to the n-th transmission occasion in the transmission of the PUSCH is the redundancy version indicated by the third information version; when the third information indicates a second value, the redundancy version to be applied to the n-th transmission occasion in the transmission of the PUSCH is related to the redundancy version indicated by the third information as well as n;

[0497] In some implementations, the transmission block processing over multiple slots (TBoMS) may be configured or indicated for the PUSCH, wherein the redundancy version to be applied to the n-th transmission occasion in the transmission of the PUSCH being determined based on the redundancy version indicated by the third information, and the fourth information, includes that:

[0498] the redundancy version to be applied to the n-th transmission occasion in the transmission of the PUSCH is determined based on the redundancy version indicated by the third information, the fourth information, as well as the number of time units for determining a transmission block size. In the description of embodiments of the present disclosure, “redundancy version" and “redundancy version index" are interchangeable.

[0499] According to an embodiment, the third information may be indicated by one DCI format. The DCI format schedules the transmission of the PUSCH. Alternatively, the third information may also be configured by higher level signaling, the transmission of the PUSCH is a transmission of a configured grant PUSCH (CG PUSCH).

[0500] The transmission of the PUSCH is scheduled by the DCI format, it indicates that the transmission of the PUSCH is a DG PUSCH (dynamic grant physical uplink shared channel), and the case where the transmission of the PUSCH is a DG PUSCH is described below.

[0501] For example, in the case where the third information is indicated by one DCI format and the fourth information indicates that all of redundancy versions of repetition transmission of the PUSCH are the redundancy versions configured or indicated by the third information, or it is activated that all of the redundancy versions of the repetition transmission of the PUSCH are the redundancy versions configured or indicated by the third information, in some implementations, the first communicating node (e.g., the UE) receives the fourth information, transmits the PUSCH, wherein the redundancy version to be applied to the n-th transmission occasion in the transmission of the PUSCH is (or, is set to be) a redundancy version index ( ) indicated by a value of a redundancy version domain in the DCI format. In one particular implementation, the value of the redundancy version domain in the DCI format that schedules the PUSCH is 00, it indicates that the value of the applied indicated by the DCI is 0. In this case, the UE receives the fourth information, transmits the PUSCH, wherein the redundancy version to be applied to the n-th transmission occasion in the transmission of the PUSCH is , wherein the value of n may be an integer between 0 and K-1 , or may be an integer between 1 and K.

[0502] For another example, in the case where the third information is indicated by one DCI format and the fourth information indicates the number of times of the repetition of the redundancy version, in some implementations, the UE receives the fourth information, transmits the PUSCH, wherein the redundancy version to be applied to the n-th transmission occasion in the transmission of the PUSCH is determined based on the redundancy version index ( ) indicated by the value of the redundancy version domain in the DCI format and the number of times of the repetition of the redundancy version. For example, the redundancy version to be applied to the n-th transmission occasion in the transmission of the PUSCH may be determined based on the redundancy version index indicated by the value of the redundancy version domain in the DCI format, the number of times of the repetition of the redundancy version, and n. In one particular implementation, the value of the redundancy version domain in the DCI format that schedules the PUSCH is 00, it indicates that the value of the applied indicated by the DCI is 0, the UE receives a fourth information indicating that the number of times of the repetition ofRVis , and the UE transmits the PUSCH, wherein the redundancy version to be applied to the n-th transmission occasion in the transmission of the PUSCH is determined based on and the value of the applied indicated by the DCI. Wherein the value of n may be an integer between 0 and K-1 or an integer between 1 and K. One table, which is predefined by the protocol, representing a relationship between the redundancy version to be applied to the n-th transmission occasion in the transmission of the PUSCH, and and the value of the applied indicated by the DCI is shown in table 17 below:

[0503] Redundancy version indicated by DCI that schedules PUSCHRedundancy version to be applied to n-th PUSCH transmission occasion((n-(n mod )) / )mod 4 = 0((n-(n mod )) / )mod 4 = 1((n-(n mod )) / )mod 4 = 2((n-(n mod )) / )mod 4 = 300231223103310211023

[0504] In some embodiments, in the case where the third information is indicated by one DCI format, when the transmission block processing over multiple slots (TBoMS) is configured for the transmission of the PUSCH, the redundancy version to be applied to the n-th transmission occasion in the transmission of the PUSCH may be determined based on the redundancy version index indicated by the value of the redundancy version domain in the DCI format that schedules the PUSCH and the number of times of the repetition of the redundancy version. For example, the redundancy version to be applied to the n-th transmission occasion in the transmission of the PUSCH is determined based on the redundancy version index indicated by the value of the redundancy version domain in the DCI format, n, and N, wherein the N is the number of time units for determining the transmission block size. For example, the redundancy version to be applied to the n-th transmission occasion in the transmission of the PUSCH is determined based on the redundancy version index ( ) indicated by the value of the redundancy version domain in the DCI format and the value of , wherein the N is the number of time units for determining the transmission block size.

[0505] In some implementations, in the case where the third information is indicated by one DCI format, when a spreading based on the OCC is configured or indicated for the PUSCH, the fourth information may indicate a length of the OCC. For example, in some implementations, when the spreading based on the OCC is configured or indicated for the PUSCH, the UE receives the fourth information, transmits the PUSCH, wherein the redundancy version to be applied to the n-th transmission occasion in the transmission of the PUSCH is determined based on a redundancy version index ( ) indicated by a value of the redundancy version domain in the DCI format and the length of the OCC. For example, when the spreading based on the OCC is configured or indicated for the PUSCH, the redundancy version to be applied to the n-th transmission occasion in the transmission of the PUSCH may be determined based on the redundancy version index indicated by the value of the redundancy version domain in the DCI format, the length of the OCC and n. In one particular implementation, the value of the redundancy version domain in the DCI format that schedulesa PUSCH is 00, it indicates that the value of the applied indicated by the DCI is 0, the UE receives the fourth information indicating that the length of the OCC is , the UE transmits the PUSCH, wherein the redundancy version to be applied to the n-th transmission occasion in the transmission of the PUSCH is determined based on and the value of the applied indicated by the DCI. Wherein the value of n may be an integer between 0 and K-1 or an integer between 1 and K.

[0506] In some implementations, when the spreading based on the OCC is configured or indicated for the PUSCH, and the spreading is grouped into one or more PUSCH transmission occasion groups, the fourth information may indicate the number of PUSCH transmission occasions contained in the PUSCH transmission occasion group, the number of PUSCH transmission occasion groups, and / or an index of the transmission occasion group at which the n-th transmission occasion is located.

[0507] In some implementations, in the case where the third information is indicated by one DCI format, when a spreading is configured or indicated for the PUSCH and the spreading of the PUSCH is grouped into one or more PUSCH groups, the redundancy version to be applied to the n-th transmission occasion in the transmission of the PUSCH is determined based on a redundancy version index ( ) indicated by a value of a redundancy version domain in the DCI that schedules the PUSCH and an index m of a transmission occasion group at which the n-th transmission occasion is located, wherein the m is an integer between 0 and M-1 (or, m is an integer between 1 and M), and M is the number of PUSCH transmission occasion groups. For example, when the spreading is configured or indicated for the PUSCH, and the spreading is grouped into one or more PUSCH groups, the redundancy version to be applied to the n-th transmission occasion in the transmission of the PUSCH is determined based on the redundancy version index indicated by the value of the redundancy version domain in the DCI format, and an modulo operation related to m. In one specific example, when the spreading is configured or indicated for the PUSCH, and the spreading is grouped into one or more groups, the redundancy version to be applied to the n-th transmission occasion in the transmission of the PUSCH is determined based on the redundancy version index ( ) indicated by the value of the redundancy version domain in the DCI format and a value of

[0508] In some implementations, in the case where the third information is indicated by one DCI format, when the spreading is configured or indicated for the PUSCH and the PUSCH spreading is grouped into one or more PUSCH transmission occasion groups, the redundancy version to be applied to the n-th transmission occasion in the transmission of the PUSCH is determined based on the redundancy version index indicated by the value of redundancy version domain in the DCI that schedules the PUSCH, n, as well as the number of PUSCH transmission occasions contained in the PUSCH transmission occasion group or the number of PUSCH transmission occasion groups. In one particular implementation, the value of the redundancy version domain in the DCI format that schedules the PUSCH is 00, it indicates that the applied indicated by the DCI is 0, and the UE receives the fourth information indicating that the number of PUSCH transmission occasions contained in the PUSCH transmission occasion group at is , or the third information indicates that the number of PUSCH transmission occasion groups is , the UE transmits the PUSCH, wherein the redundancy version to be applied to the n-th transmission occasion in the transmission of the PUSCH is based on a value of (or a value of ) and is related to the applied indicated by the DCI. Wherein the value of the n may be an integer between 0 and K-1 or an integer between 1 and K. One table representing a relationship between the redundancy version to be applied to the n-th transmission occasion in the transmission of the PUSCH and and the applied indicated by the DCI is shown in table 18 below:

[0509] Redundancy version indicated by DCI that schedules PUSCHRedundancy version to be applied to n-th PUSCH transmission occasion((n-(n mod )) / )mod 4 = 0((n-(n mod )) / )mod 4 = 1((n-(n mod )) / )mod 4 = 2((n-(n mod )) / )mod 4 = 300231223103310211023

[0510] In some embodiments, when the transmission block processing over multiple slots (TBoMS) is configured or indicated for the PUSCH, the redundancy version to be applied to the n-th transmission occasion in the transmission of the PUSCH may be determined based on the redundancy version indicated by the third information, the fourth information, and the number of time units for determining the transmission block size. For example, in the case where the third information is indicated by one DCI format, when the transmission block processing over multiple slots (TBoMS) is configured for the transmission of the PUSCH, the redundancy version to be applied to the n-th transmission occasion in the transmission of the PUSCH is determined, based on the redundancy version index indicated by the value of the redundancy version domain in the DCI format that schedules the PUSCH, as well as the number of PUSCH transmission occasions contained in the PUSCH transmission occasion group, the number of PUSCH transmission occasion groups, and / or an index m of the transmission occasion group at which the n-th transmission occasion is located. For example, the redundancy version to be applied to the n-th transmission occasion in the transmission of the PUSCH is determined based on the redundancy version index indicated by the value of the redundancy version domain in the DCI format, m, and N, wherein the N is the number of time units for determining the transmission block size. For example, when the TBoMS is configured for the transmission of the PUSCH, the redundancy version to be applied to the n-th transmission occasion in the transmission of the PUSCH is determined based on the redundancy version index ( ) indicated by the value of the redundancy version domain in the DCI format and , wherein the N is the number of time units for determining the transmission block size.

[0511] The above describes some examples of cases where the transmission of the PUSCH is the DG PUSCH. Alternatively, the transmission of the PUSCH may be the transmission of the CG PUSCH. Some examples of the case where the transmission of the PUSCH may be the transmission of the CG PUSCH are described below.

[0512] According to an embodiment, the third information may be configured by higher level signaling and the transmission of the PUSCH may be a transmission of the CG PUSCH.

[0513] In some implementations, the high-level signaling (e.g.,repK-RV) defines a redundancy version pattern applied to the transmission of the PUSCH (or repetition transmission or repetition of the PUSCH). In some implementations, the high-level signaling (e.g.,repK-RV) indicates a redundancy version sequence used by the UE. In some implementations, the n-th transmission occasion among K repetitions is related to a (mod(((n-mod(n, N)) / N)-1,4)+1)-th value in the configured redundancy version sequence, wherein the N is a predefined value, e.g., N=1.

[0514] In some implementations, the fourth information may indicate all of redundancy versions of repetition transmission of the PUSCH being the redundancy version configured or indicated by the third information, or activating that all of the redundancy versions of the repetition transmission of the PUSCH are the redundancy versions configured or indicated by the third information. In this case, the redundancy version to be applied to the n-th transmission occasion in the transmission of the PUSCH may be (or be set to be) the redundancy version defined or indicated by the high-level signaling for configuring the PUSCH. In some implementations, the UE receives the fourth information, transmits the PUSCH, wherein the redundancy version to be applied to the n-th transmission occasion in the transmission of the PUSCH is determined based on the configured redundancy version sequence. In one particular implementation, the high-level signaling (e.g., the high-level parameterrepK-RV) defines a redundancy version pattern, and the n-th transmission occasion among the K repetitions (or K transmission occasions) is related to the configured RV sequence. For example, the high-level parameterrepK-RVindicates the redundancy version sequence to be used by the UE. For example, the high-level parameter indicates that the redundancy version sequence to be used by the UE is {0, 2, 3, 1}, and the redundancy version to be applied to the n-th transmission occasion in the transmission of the PUSCH may be a first redundancy version (i.e., redundancy version 0) of the configured redundancy version sequence. In some implementations, the UE receives the fourth information, transmits the PUSCH, wherein the redundancy version to be applied to the n-th transmission occasion in the transmission of the PUSCH is determined based on the redundancy version defined or indicated by the high-level signaling for configuring CG PUSCH, and the number of times of the repetition of the redundancy version. For example, the redundancy version to be applied to the n-th transmission occasion in the transmission of the PUSCH is determined based on the configured redundancy version sequence and the number of times of the repetition of the redundancy version. In one particular implementation, the high-level parameterrepK-RVdefines a redundancy version pattern, and the n-th transmission occasion among the K repetitions (or K transmission occasions) is related to the configured RV sequence. Wherein the high-level parameterrepK-RVindicates the redundancy version sequence to be used by the UE. For example, the high-level parameter indicates that the redundancy version sequence to be used by the UE is {0, 2, 3, 1}, K is 8, and the redundancy versions applied to the first to the eighth transmission occasions in the transmission of the PUSCH are determined as {0, 0, 2, 2, 3, 3, 1, 1}, respectively. In another particular implementation, the redundancy version to be applied to the n-th transmission occasion in the transmission of the PUSCH is determined based on the configured redundancy version sequence, the number of times of the repetition of the redundancy version, and n. For example, the redundancy version to be applied to the n-th transmission occasion in the transmission of the PUSCH is determined based on the configured redundancy version sequence and a value of (mod(((n-mod(n, )) / )-1,4)+1), wherein is the repetition number of the redundancy version.

[0515] In some implementations, in the case where the third information is configured by higher level signaling, the transmission of the PUSCH is the transmission of the CG PUSCH, and the fourth information indicates the number of times of the repetition of the redundancy version, when the transmission block processing over multiple slots (TBoMS) is configured for the transmission of the PUSCH, the redundancy version to be applied to the n-th transmission occasion in the transmission of the PUSCH may be determined based on the configured redundancy version sequence and the number of times of the repetition of the redundancy version. For example, the redundancy version to be applied to the n-th transmission occasion in the transmission of the PUSCH may be determined based on the configured redundancy version sequence, the number of times of the repetition of the redundancy version, n, and N, wherein the N is the number of time units for determining the transmission block size. For example, when the TBoMS is configured for the transmission of the PUSCH, the redundancy version to be applied to the n-th transmission occasion in the transmission of the PUSCH is determined based on the configured redundancy version sequence and a value of (mod(((n-mod(n,NP2)) / NP2)-1,4)+1), wherein the N is the number of time units for determining the transmission block size, is the number of times of the repetition of the redundancy version.

[0516] In some implementations, in the case where the third information is configured by the higher level signaling, the transmission of the PUSCH is the transmission of the CG PUSCH, and the fourth information indicates a length of an OCC, when a spreading based on the OCC is configured or indicated for the PUSCH, the redundancy version to be applied to the n-th transmission occasion in the transmission of the PUSCH may be determined based on the configured redundancy version sequence and the length of the OCC. For example, in one particular implementation, the high-level parameterrepK-RVdefines a redundancy version pattern, the n-th transmission occasion among the K repetitions (or K transmission occasions) is related to the configured RV sequence. Wherein the high-level parameterrepK-RVindicates the redundancy version sequence to be used by the UE. For example, the high-level parameter indicates that the redundancy version sequence to be used by the UE is {0, 2, 3, 1}, the length of the OCC is 8, and the redundancy versions applied to the first to the eighth transmission occasions in the transmission of the PUSCH are determined as {0, 0, 2, 2, 3, 3, 1, 1}, respectively. In another particular implementation, the redundancy version to be applied to the n-th transmission occasion in the transmission of the PUSCH is determined based on the configured redundancy version sequence, the length of the OCC, and n. For example, the redundancy version to be applied to the n-th transmission occasion in the transmission of the PUSCH is determined based on the configured redundancy version sequence and the value of (mod(((n-mod(n, )) / )-1,4)+1), wherein is the length of the OCC.

[0517] In some implementations, in the case where the third information is configured by the higher level signaling, the transmission of the PUSCH is the transmission of the CG PUSCH, and the fourth information indicates the length of the OCC, when the transmission block processing over multiple Slots (TBoMS) is configured for the transmission of the PUSCH, the redundancy version to be applied to the n-th transmission occasion in the transmission of the PUSCH may be determined based on the configured redundancy version and the length of the OCC, includes: the redundancy version to be applied to the n-th transmission occasion in the transmission of the PUSCH is determined based on the configured redundancy version sequence, the length of the OCC, n, and N, wherein N is the number of time units for determining the transmission block size. For example, when the TBoMS is configured for the transmission of the PUSCH, the redundancy version to be applied to the n-th transmission occasion in the transmission of the PUSCH is determined based on the configured redundancy version sequence and a value of (mod(((n-mod(n,NP2)) / NP2)-1,4)+1), wherein the N is the number of time units for determining the transmission block size, and is the length of the OCC.

[0518] In some implementations, in the case where the third information is configured by the higher level signaling and the transmission of the PUSCH is the transmission of the CG PUSCH, when the spreading is configured or indicated for the PUSCH, and the PUSCH spreading is grouped into one or more PUSCH transmission occasion groups, the redundancy version to be applied to the n-th transmission occasion in the transmission of the PUSCH may be determined based on the configured redundancy version sequence, as well as the number of the PUSCH transmission occasions contained in the PUSCH transmission occasion group, the number of PUSCH transmission occasion groups and / or an index m of the transmission occasion group at which the n-th transmission occasion is located, for example, the redundancy version to be applied to the n-th transmission occasion in the transmission of the PUSCH is determined based on the configured redundancy version sequence, m, and N, wherein N is a predetermined value. For example, the redundancy version to be applied to the n-th transmission occasion in the transmission of the PUSCH is determined based on the configured redundancy version sequence and a value of (mod(((m-mod(m, N)) / N)-1,4)+1), wherein N=1.

[0519] In one particular implementation, the high-level parameterrepK-RVdefines a redundancy version pattern, the n-th transmission occasion among the K repetitions (or K transmission occasions) is related to the configured RV sequence. Wherein the high-level parameterrepK-RVindicates the redundancy version sequence to be used by the UE. For example, the high-level parameter indicates that the redundancy version sequence to be used by the UE is {0, 2, 3, 1}, K is 8, the third information indicates that the number of PUSCH transmission occasions contained in the PUSCH transmission occasion group is 2, or the third information indicates that the number of the PUSCH transmission occasion groups is 4, the redundancy versions applied to the first to the fourth transmission occasion groups in the transmission of the PUSCH are {0, 2, 3, 1}, respectively, i.e., the redundancy versions applied to the first to eighth transmission occasions in the transmission of the PUSCH are determined to be {0, 0, 2, 2, 2, 3, 3, 3, 1, 1}, respectively.

[0520] In some implementations, when the transmission block processing over multiple Slots (TBoMS) is configured for the transmission of the PUSCH, the redundancy version to be applied to the n-th transmission occasion in the transmission of the PUSCH being determined based on the configured redundancy version sequence, as well as the number of PUSCH transmission occasions contained in the PUSCH transmission occasion group, the number of PUSCH transmission occasion groups, and / or an index m of the transmission occasion group at which the the n-th transmission occasion is located, includes: the redundancy version to be applied to the n-th transmission occasion in the transmission of the PUSCH is determined based on the configured redundancy version sequence, m, and N, wherein the N is the number of time units for determining the transmission block size. For example, the redundancy version to be applied to the n-th transmission occasion in the transmission of the PUSCH is determined based on the configured redundancy version sequence and a value of(mod(((m-mod(m, N)) / N)-1,4)+1, wherein the N is the number of time units for determining the transmission block size. The method for determining the redundancy version of the n-th transmission occasion applied to the PUSCH based on the number of time units for determining the transmission block size is given in one or more embodiments above and will not be repeated herein.

[0521] Alternatively, the method described in FIG. 5 further includes: transmitting second capability information to the second communication node, wherein the second capability information indicates whether the UE supports one of: all of the redundancy versions of the repetition transmission of the PUSCH being the redundancy versions configured or indicated by the third information; determining the redundancy version to be applied to the n-th transmission occasion based on the redundancy version repetition related information. Alternatively, determining the redundancy version to be applied to the n-th transmission occasion based on the redundancy version repetition related information may include: determining the redundancy version to be applied to the n-th transmission occasion based on the third information and the redundancy version repetition related information, for example, determining the redundancy version to be applied to the n-th transmission occasion based on the redundancy version indicated by the third information and the redundancy version repetition related information. Alternatively, the second capability information may also indicate at least one of: all of redundancy versions of repetition transmission of the PUSCH being the redundancy version configured or indicated by the third information, activating that all of the redundancy versions of the repetition transmission of the PUSCH are the redundancy versions configured or indicated by the third information, deactivating use of different redundancy versions in the repetition transmission of the PUSCH, deactivating redundancy version rotation, redundancy version repetition, activating redundancy version repetition, not activating that all of redundancy versions of repetition transmission of the PUSCH are the redundancy versions configured or indicated by the third information, deactivating that all of the redundancy versions of the repetition transmission of the PUSCH are the redundancy versions configured or indicated by the third information, not deactivating use of different redundancy versions in the repetition transmission of the PUSCH, activating the use of different redundancy versions in the repetition transmission of the PUSCH, the use of different redundancy versions in the repetition transmission of the PUSCH, not deactivating redundancy version rotation, activating the redundancy version rotation, the redundancy version rotation, not activating redundancy version repetition, deactivating the redundancy version repetition.

[0522] Alternatively, the method described in FIG. 5 further includes the steps included in the method shown in Fig. 4, and the description of the relevant steps in FIG. 4 are all adapted to the method shown in Fig. 5 and will not be repeated here. According to an embodiment, as mentioned in the description above with respect to FIG. 4, the first information and / or the second information may include the information for indicating the redundancy version to be applied to the n-th PUSCH transmission occasion. As an example, the fourth information may be the information itself for indicating the redundancy version to be applied to the n-th PUSCH transmission occasion, or may also be information determined based on the information for indicating the redundancy version to be applied to the n-th PUSCH transmission occasion.

[0523] According to the method shown in FIG. 5, even if the first communication node does not support an OCC function, it is capable of realizing the transmission of the PUSCH on the same time-frequency resources as the other communication node, so that the spectral efficiency may be improved and the transmission delay may be reduced.

[0524] FIG. 6 is a flowchart illustrating a method performed by a second communication node according to an embodiment of the present disclosure.

[0525] Referring to FIG. 6, at step S610, information related to an orthogonal coverage code (OCC) and / or information for indicating an OCC sequence is transmitted. For example, the second communication node transmits the information related to the orthogonal coverage code (OCC) and / or the information for indicating the OCC sequence to the first communication node. Alternatively, According to an embodiment, step S610 may include: transmitting first information including the information related to the orthogonal coverage code (OCC); and / or transmitting second information including the information for indicating the OCC sequence. Alternatively, the first information is first radio resource control (RRC) configuration information, the second information is second RRC configuration information or downlink control information (DCI).

[0526] According to an embodiment, the information related to OCC includes at least one of: information for indicating whether to enable the OCC or not; information for indicating the length of the OCC sequence; information for indicating the OCC sequence applied to the PUSCH; information for indicating the number of OCC groups; information for indicating an OCC occasion; information for indicating the number of PUSCH transmission occasions corresponding to a transmission block (TB); information for indicating a starting time unit for an initial transmission of the TB, but not limited to this.

[0527] According to an embodiment, the information for indicating the OCC sequence may include at least one of: information for indicating whether to enable the OCC or not; information for indicating the length of the OCC sequence; information for indicating the OCC sequence applied to the PUSCH; information for indicating the number of OCC groups; information for indicating the OCC occasion; information for indicating the number of the time units corresponding to the transmission of the PUSCH; information for indicating the time unit at which the PUSCH should be transmitted, but not limited to this.

[0528] The details related to the information related to the orthogonal coverage code (OCC) and the information for indicating the OCC sequence have been described above in the description of the method performed by the first communicating node and will not be repeated here.

[0529] At step S620, a physical uplink shared channel (PUSCH) is received, wherein physical resources for the transmission of the PUSCH are determined based on the information related to the OCC and / or the information for indicating the OCC sequence. For example, the second communication node may receive the PUSCH from the first communication node. In the above description, a manner of determining the physical resources for the transmission of the PUSCH based on the information related to the OCC and / or the information for indicating the OCC sequence have been described and will not be repeated herein.

[0530] According to an embodiment, alternatively, as mentioned above, the first information and / or the second information may further include information for indicating a redundancy version to be applied to a n-th PUSCH transmission occasion, wherein the redundancy version to be applied to the n-th PUSCH transmission occasion is determined based on the information for indicating the redundancy version to be applied to the n-th PUSCH transmission occasion, wherein the n includes an integer greater than or equal to 0 an integer.

[0531] According to an embodiment, alternatively, the method shown in FIG. 6 may further include: receiving first capability information from the first communication node, wherein the first capability information indicates whether the first communication node supports applying the OCC sequence to the transmission of the PUSCH or not.

[0532] According to an embodiment, alternatively, the method shown in FIG. 6 may further include the steps included in the method to be described below with reference to FIG. 7, and the description of the steps included in the method to be described with reference to FIG. 7 may be similarly adapted to the method shown in FIG. 6.

[0533] FIG. 7 is a flowchart illustrating a method performed by a second communication node according to an embodiment of the present disclosure.

[0534] Referring to FIG. 7, at step S710, third information is transmitted, wherein the third information configures or schedules transmission of a physical uplink shared channel (PUSCH) in K time units, wherein the K is an integer greater than 1. At step S720, fourth information is transmitted, wherein the fourth information is redundancy version repetition related information. At step S730, the PUSCH transmitted based on the third information and the fourth information is received, wherein a redundancy version to be applied to a n-th transmission occasion in the transmission of the PUSCH is the redundancy version configured or indicated by the third information, or the redundancy version to be applied to the n-th transmission occasion in the transmission of the PUSCH is determined based on the redundancy version indicated by the third information, and the fourth information, wherein the n is an integer between 0 and K-1.

[0535] According to an embodiment, alternatively, the method shown in FIG. 7 may further include: receiving second capability information from the first communication node, wherein the second capability information indicates whether a UE supports one of: all of the redundancy versions of the repetition transmission of the PUSCH being the redundancy versions configured or indicated by the third information; determining the redundancy version to be applied to the n-th transmission occasion based on the redundancy version repetition related information.

[0536] Any content related to the fourth information and the manner of determining the redundancy version to be applied to the n-th transmission occasion in the transmission of the PUSCH mentioned in the above description of FIG 5 is applicable to the method of FIG. 7, therefore, it will not be repeated herein.

[0537] Alternatively, the method described in FIG. 7 further includes the steps included in the method shown in FIG. 6, and the description of the relevant steps in FIG. 6 are all adapted to the method shown in FIG. 7 and will not be repeated herein.

[0538] Above, the methods performed by the first communication node and the second communication node have been described with reference to FIGS. 4 to 7. According to the above method, the first communication node is able to transmit the PUSCH on the same time-frequency resources as the other communication node, regardless of whether the first communication node supports the OCC or not, thereby improving the spectral efficiency and reducing the transmission delay.

[0539] In the followings, a brief description of the first communication node and the second communication node will be described with reference to FIGS. 8 and 9.

[0540] FIG. 8 is a block diagram illustrating a first communication node according to an embodiment of the present disclosure. Referring to FIG. 8, the first communication node 800 may include a transceiver 810 and a processor 820, wherein the processor 820 is coupled to the transceiver 810 and configured to control the transceiver 810 to perform the method performed by the first communication node described above.

[0541] As an example, the first communication node may be a user equipment. For example, the user equipment may be a PC computer, a tablet device, a personal digital assistant, a smartphone, or other apparatuses capable of executing the above set of instructions. In addition, the user equipment does not have to be a single user equipment, but may also be any collection of devices or circuits capable of executing the instructions (or the set of instructions) individually or jointly. The user equipment may also be a part of an integrated control system or system manager, or may be any portable electronic apparatus.

[0542] In the user equipment, the processor 820 may include a central processing unit (CPU), a graphics processing unit (GPU), a programmable logic device, a dedicated processor system, a microcontroller, or a microprocessor, and the like. By way of example and not limitation, the processor may also include an analog processor, a digital processor, a microprocessor, a multi-core processor, a processor array, and the like.

[0543] FIG. 9 is a block diagram illustrating a second communication node according to an embodiment of the present disclosure. Referring to FIG. 9, the second communication node 900 may include a transceiver 910 and a processor 920, wherein the processor 920 is coupled to the transceiver 910 and configured to control the transceiver 910 to perform the method performed by the second communication node described above.

[0544] As an example, the second communication node may be any network entity, such as a base station, or may be any network functional entity. Alternatively, the second communication node may also be a user equipment, e.g., a bypass apparatus.

[0545] In addition, according to an embodiment of the present disclosure, there may be provided a computer-readable storage medium storing instructions, the instructions, when executed by at least one processor, cause the at least one processor to perform any of the methods mentioned above. An example of the computer-readable storage medium herein includes: a read-only memory (ROM), a random-access programmable read-only memory (PROM), an electrically erasable programmable read-only memory (EEPROM), a random-access memory (RAM), a dynamic random-access memory (DRAM), a astatic random-access memory (SRAM), a flash memory, a non-volatile memory, a CD- ROM, a CD-R, CD+R, a CD-RW, a CD+RW, a DVD-ROM, a DVD-R, a DVD-R, a DVD+R,a DVD-RW, a DVD+RW, a DVD-RAM, a BD-ROM, a BD-R, a BD-R LTH, a BD-RE, a Blu-Ray or optical disc memory, a hard disk drive (HDD), a solid state disk (SSD), a card memory (such as, a multimedia card, a secure digital (SD) card, or an extremely fast digital (XD) card), a magnetic tape, a floppy disk, a magneto-optical data storage device, an optical data storage device, a hard disk, a solid state disk, and any other device, the any other device is configured to store, in a non-transitory manner, computer programs as well as any associated data, data file, and data structures and to provide the computer programs as well as any associated data, data file, and data structures to a processor or computer to enable the processor or computer to execute the computer programs. The instructions or computer programs in the above computer-readable storage medium may be run in an environment deployed in a computer device such as a client, a host, an agent device, a server, and the like, and furthermore, in one example, the computer programs and any associated data, data file, and data structure are distributed across a networked computer system, such that the computer programs and any associated data, data file, and data structure are distributed are stored, accessed, and executed in a distributed manner through one or more processors or computers.

[0546] Those skilled in the art will easily think of other embodiments of the present disclosure after considering the specification and practicing the invention disclosed herein. The present application is intended to cover any variation, use, or adaptive change of the present disclosure that follow the general principle of the present disclosure and include common knowledge or commonly-used technical means in the art which are not disclosed herein. The specification and embodiments are to be regarded as exemplary only, and the true scope and spirit of the present disclosure is limited by the claims.

Claims

1.A method performed by a user equipment (UE) in a wireless communication system, comprising:identifying first information that configures or schedules transmission of a physical uplink shared channel (PUSCH);identifying second information which is redundancy version repetition related information;transmitting the PUSCH based on the first information and the second information,wherein the second information indicates a length of an orthogonal coverage code (OCC).2.The method of claim 1, wherein the second information is indicated in case that a spreading is configured or indicated for the PUSCH.3.The method of claim 2, wherein, in case that the spreading is grouped into one or more PUSCH transmission occasion groups, the second information further indicates at least one of:a number of PUSCH transmission occasions contained in the PUSCH transmission occasion group;a number of the PUSCH transmission occasion groups.4.The method of claim 3, wherein the number of the PUSCH transmission occasion groups is determined by dividing a number of the transmission occasions of the PUSCH corresponding to a transmission block (TB) by the number of PUSCH transmission occasions contained in the PUSCH transmission occasion group.5.The method of claim 2, wherein a redundancy version to be applied to a n-th transmission occasion in the transmission of the PUSCH is determined based on a redundancy version index indicated by a value of a redundancy version domain in the downlink control information (DCI) format and a value of m mod 4.6.The method of claim 1, wherein one OCC sequence related to the second information is applied to the transmission of the PUSCH, andwherein each spread of the transmission of the PUSCH is multiplied by a corresponding modulation symbol of one OCC sequence.7.The method of claim 1,wherein a redundancy version to be applied to a n-th transmission occasion in the transmission of the PUSCH is the redundancy version configured or indicated by the first information,or the redundancy version to be applied to the n-th transmission occasion in the transmission of the PUSCH is determined based on the redundancy version indicated by the first information, and the second information,wherein the n is an integer between 0 and K-1.8.The method of claim 1, wherein the second information configures or further indicates at least one of:all of redundancy versions of repetition transmission of the PUSCH being the redundancy version configured or indicated by third information;activating that all of the redundancy versions of the repetition transmission of the PUSCH are the redundancy versions configured or indicated by the third information;deactivating use of different redundancy versions in the repetition transmission of the PUSCH;deactivating redundancy version rotation;redundancy version repetition;activating redundancy version repetition;repetition number of the redundancy version.9.The method of claim 8, wherein the redundancy version to be applied to the n-th transmission occasion in the transmission of the PUSCH being determined based on the redundancy version indicated by the third information, and fourth information, comprising:the redundancy version to be applied to the n-th transmission occasion in the transmission of the PUSCH is determined based on the redundancy version indicated by the third information and the repetition number of the redundancy version indicated by the fourth information as well as the n.10.The method of claim 1, wherein the second information further indicates at least one of:not activating that all of redundancy versions of repetition transmission of the PUSCH are the redundancy versions configured or indicated by third information;deactivating that all of the redundancy versions of the repetition transmission of the PUSCH are the redundancy versions configured or indicated by the third information;not deactivating use of different redundancy versions in the repetition transmission of the PUSCH;activating the use of different redundancy versions in the repetition transmission of the PUSCH;the use of different redundancy versions in the repetition transmission of the PUSCH;not deactivating redundancy version rotation;activating the redundancy version rotation;the redundancy version rotation;not activating redundancy version repetition;deactivating the redundancy version repetition, andwherein the redundancy version to be applied to the n-th transmission occasion in the transmission of the PUSCH being determined based on the redundancy version indicated by the third information, and fourth information, comprising: the redundancy version to be applied to the n-th transmission occasion in the transmission of the PUSCH is determined based on the redundancy version indicated by the third information as well as the n.11.The method of claim 1, wherein transmission block over multiple slots (TBoMS) is configured or indicated for the PUSCH,wherein the redundancy version to be applied to the n-th transmission occasion in the transmission of the PUSCH being determined based on the redundancy version indicated by third information, and fourth information, comprising:the redundancy version to be applied to the n-th transmission occasion in the transmission of the PUSCH is determined based on the redundancy version indicated by the third information, the fourth information, as well as the number of time units for determining a transmission block size.12.The method of claim 1, wherein the first information is configured by higher level signaling, and the transmission of PUSCH is the transmission of a configured grant PUSCH (CG PUSCH).13.A method performed by a communication node in a wireless communication system, comprising:transmitting first information that configures or schedules transmission of a physical uplink shared channel (PUSCH);transmitting second information that is redundancy version repetition related information;wherein,a redundancy version to be applied to a n-th transmission occasion in the transmission of the PUSCH is the redundancy version configured or indicated by the first information,or the redundancy version to be applied to the n-th transmission occasion in the transmission of the PUSCH is determined based on the redundancy version indicated by the first information, and the second information, andwherein the n is an integer between 0 and K-1.14.A user equipment (UE) in a wireless communication system, the UE comprising:a transceiver;a processor coupled to the transceiver, and configured to:identify first information that configures or schedules transmission of a physical uplink shared channel (PUSCH);identify second information which is redundancy version repetition related information;transmit the PUSCH based on the first information and the second information,wherein the second information indicates a length of an orthogonal coverage code (OCC).15.A communication node in a wireless communication system, the communication node comprising:a transceiver;a processor coupled to the transceiver, and configured to:transmit first information that configures or schedules transmission of a physical uplink shared channel (PUSCH);transmit second information that is redundancy version repetition related information;wherein,a redundancy version to be applied to a n-th transmission occasion in the transmission of the PUSCH is the redundancy version configured or indicated by the first information,or the redundancy version to be applied to the n-th transmission occasion in the transmission of the PUSCH is determined based on the redundancy version indicated by the first information, and the second information, andwherein the n is an integer between 0 and K-1.

Images